When I mount Debian 8 live into VMWare Player 7.1.2 64bit, it works awesome with and without graphics acceleration enabled i.e I can get into the desktop and all that.
But, when I installed it, the reboot is just a blank screen. I am not sure how I can proceed from now.
I am on Windows 7, 64bit Ultimate.
I was able to get Fedora 10 to run on VirtualBox. Since the system wouldn't let me set the resolution to anything bigger than 800 x 600, I decided to get the nVidia driver (I'm running the nVidia 8400m G). I did it through this guy's tutorial: [URL]... After rebooting, I see the loading bars and everything, but I get a blank screen with a cursor. After pressing ctrl+alt+F3, I was able to log in to the root and execute the "akmod builds the required kmod on bootup" under the "For GeForce 8 series" [URL]... After a reboot, I still get the same thing. Will I have to reinstall Fedora 10 and just not update the nVidia graphics drivers? I have a 20" monitor that has a resolution of 1600 x 1050 and I would really like to take advantage of that.
View 14 Replies View RelatedI am able to get fglrx driver to work with 10.10, but as soon as I change my displays settings to have my good old dual screen setup, I get a blank screen when I reboot the system.
View 9 Replies View RelatedI Just installed OpenSuse 11.4-32 bit with KDE 4.6 on my PC. At first boot everything was working, then I added the community ATI/AMD repository to get the drivers for my ATI 5570, but after reboot i got a blank screen. So I ran the "failsafe mode" in the boot menu, it worked (3D accel. as well), but just for the root user. To make it work for the non-root user had to set the setuid bit for /usr/bin/Xorg. (is it ok to run xorg with superuser privileges?) Then I tryed to understand wich is the kernel option actually needed for X to start, and after a few attempts I realized the only option really needed is the "nomodeset". what is the nomodeset option for? and why I need it to run in the graphic mode?
View 9 Replies View RelatedI had ubuntu running just fine on another computer, but had to move things around to make Windows7 run better. So after backing up Home, I switched hard drives, pulled the video card, and adjusted RAM, I tried booting up. The computer found all the changes and did its thing. But then it hung with a blank screen. I figured that it didn't recongnize the video driver for this computer, or something, so I did a fresh install with 9.10 to start over from scratch. The boot up went great, and finished completely. I made a few changes to the desktop, and loaded in my archived firefox bookmarks and evolution files. After rebooting, the first ubuntu logo came up, but then the blank screen, with no drum sounds. I tried a few more times rebooting and hitting esc, but I don't know what I am doing at that menu. I also tried the F1 option, but again, I don't know anything. One other time I was able to boot into ubuntu all the way when I was hitting esc slowing (waiting) and somehow was able to get the login and the desktop just fine. I haven't been able to get that to happen again.
Can someone walk me through the steps to troubleshoot this? I don't know any terminal jargon or commands, and haven't really got a clue, but I really want to learn and figure this out. I don't even know how to go in from the command line to see what my system specs or video specs are to tell you.
i wonder if any one can help me, i have just installed 9.10 on my Dell Optiplex P4 2.0GHz 512MB RAM 200 g hd.install went well up till i eject cd at the end,when it try to reboot all i get is a blank screen ?
View 2 Replies View RelatedI recently got a new laptop and am trying to install Ubuntu 9.10 on it. I have installed it on my two other computers without any problems, but there seems to be a hitch with my new one. So I boot up using the live CD and then am presented with the option to test Ubuntu or install it. If I choose either of these the screen just goes blank. If I go with the first option of testing Ubuntu before installing, I can hear the intro drumbeats but the screen is still blank.
I have searched in some forums and tried some people's advice, like pressing Ctrl+Alt+- or trl+Alt+Backspace to change the resolution and restart X windows, respectivley. But it doesn't seem to work.
I'll list my laptops specs just in case my problem has anything to do with them:
MSi
Windows 7 Home Premium 32 bit
Intel Core i3 M 330 2.13GHz
4GB DDR3 RAM
Intel Graphics Media Accelerator HD
The wubi installer copied files successfully and asked for reboot. After booting into Xubuntu the flashing logo appeared for a minute. And then the screen looked as if it was trying to show something but could not and flickered and then became dark this continued till half an hour and then I pressed Alt+Ctrl+Del.I tried all the modes but to no avail, only the last mode with command line was working. But it was not helpful for me becoz I dont know most of the commands.When I tried "Verbose Mode" as directed by the WubiGuide - Ubuntu Wiki, CTRL+ALT+F2 did not work when the installer stopped.The computer I use is assembled with Intel pentium 4, VIA chipset and Mercury(Kobian) motherboard.
View 3 Replies View Relatedi have installed ubuntu 9.10 on my hp nx6325 notebook, and everything was working just fine, then it updated and problem started coming up. First the computer wouldn't reboot after the update, blank screen, then i manually reboted and now some programs don't work (ubuntu software center, update maneger, avant window navigator)
i assume the update did some damage, so how can i repair this, is there a recovery tool or something.
ive downloaded the Ubuntu CD from the official website and burned it twice, once one a dvd and the other on a normal 700MB CD-RW.in both, the screen went blank after the loading part before the main menu (installation, try it blah blah..)what should i do?btw i use a windows XP and here is my hardware details...sapphire hd 5770 1gb, 4 gb of ram,Intel Core i5- P55 .5 ghz, i think that its enough for the minimum of the ubuntu isnt it?
View 4 Replies View RelatedI have tried the tips, and to the best of my ability understand the later posts from the sticky post "Graphics Resolution" however I seem to keep reverting back to the blank screen. I did this:
Quote: ATI TIPS: Note that some ATI cards need flgrlx and some do not... If not then this workaround sometimes works: (Found this in another thread / credit to Quote: Originally Posted by surgus View Post
Steps for ATI users:
1. When the boot hangs, press ctrl+alt+f1.
2. Login as user with root privileges.
3. Type "cd /usr/share/ati" and press enter.
4. Type "sudo sh ./fglrx-uninstall.sh" and press enter.
5. Type "sudo reboot".
The above only works for some but not all, depending on what card you have and whether it actually is supported by additional drivers (proprietary). All at the moment, mostl seem to need "nomodeset radeon mode=X", where x= 0 or 1... Some ATI cards are not working with the current natty kernel, but are working with the older 2.6.37 kernel or the proposed 2.6,38.9 kerne (please see post 2)l Sometimes (rarely) it'll work but more often it won't, and in the two times it's worked I haven't known how to get it to remember the setting permanently- keep in mind I have no idea what that last paragraph about x= 0 or 1 means.
I've been trying for some time to install Ubuntu 10.10 or variant on my Toshiba C660 with ATI graphics card.I seem to keep hitting a brick wall when attempting to run a live disc and end up at a blank screen. I get this result despite tryingots of different installation discs. Ubuntu 10.04 seems to run with no problems.I believe the problem is to do with the graphics card from googling and have tried various changes to the live cd/dvd boot options (set nomodeset & radeon.modeset=0) but with no success
View 1 Replies View RelatedI have install fedora11 live and the mouse work well when installing.When you reboot the mouse works ok until the welcome screen apears then the mouse stops working and I cannot continue with the postinstall. I have a 1TB usb externalHD that I am installing fedora11 and have partitioned it so that I have 500Gb free for fedora, system is doucore 2.4,4gb RAm, I tryed doing this with three differend mice and connectting the mouse to different usb ports
View 4 Replies View RelatedI'm trying to test out using xubuntu 10.04 on my one computer and keep getting a black/blank screen after selecting the 'try' menu option.Is there a way to fix this?I have tried some of settings via F6 with no luck.
FYI -The CD works fine as I have tested it on other machines.The version I am trying is xubuntu x86 (although I have tried ubuntu 10.04 x86 with similar results).I can Alt+Ctrl+F1 fine and get to the cmd prompt
I am having the same problem, as soon as X tries to load my screen just goes blank. I have an ATI Radeon 9550. At first I tried switching between VGA and DVI as well but upon ruling that out, I switch to my on-board video card and that is working thus far, but I'm trying very hard to figure out a way to be able to switch back. Anyways I'll check back in later on if I have any new information I will post.
View 3 Replies View RelatedI tried to upgrade Fedora 13 to Fedora 14 using preupgrade. The upgrade seem to go OK, I didn't see any errors. But when it did the final reboot all I get is a blank screen. I rebooted in single user mode and saw that /etc/rc5.d/S99local -> ../rc.local is the last script executed. I edited rc.local and added 'echo "got here"' at the end and rebooted. It did print "got here" so I know all scripts were executed for init 5, it didn't get hung anywhere along the bootup. Why I'm not getting the login screen?
View 1 Replies View RelatedNatty install -- ATI 9800 is the video board.
I installed Natty on it with the machine hooked up to a Samsung LCD with a 1680x1050 resolution over DVI. No problems at all. I want the box to pretty much output MP3s and web video, so I'm not needing much. When I take the box and hook it via DVI to my LCD, I get a blank screen on boot up. I try sticking the natty CD in it, and I get a blank screen trying to live boot it too. The LCD doesn't do 1680x1050, so I brought it back to my Samsung and set the default resolution to something nice and safe: 1280x1024. Still the same behavior. When I take splash mode off, I see a "load fallback graphics devices fail" error as it is booting up. Hard for me to think the driver is the fault here when it works on my over LCD just fine.
This is probably not possible, but just wondering, restarted centos 5.2 remotely, hung at shutdown, kvm'ed to see what was hanging it up, control c'ed and then ctl alt del, just trying to kill the process, was brought back to the login screen, but unable to type anything. Alt-f1 switched to a different virtual console, which was just a blank screen and a blinking cursor, but now able to type things. Want to avoid hard shutdown. Is there anyway to force shutdown/reboot the machine from this console?
View 1 Replies View RelatedI've been trying to install 5.5 here for the past few days, first from USB and now from the CDs, with no success. The problem occurs when I reboot after installing. After the BIOS has done it's thing I'm faced with a blank screen with a blinking cursor at the top left of the screen.
Initially I assumed that this was due to the intel driver problem which is reported in the release notes as a known issue, and the PC I'm installing on has intel graphics. However I have now done a text install and still have the same issue. I'm able to boot up the system using the CentOS live CD, which encounters no issues, and it mounts the local system no problem. After unmounting and remounting to get write access I'm able to change the device entry in /etc/X11/xorg.conf to have the Option "DDC" "false" entry. I can also see that the runlevel is set to 3 in /etc/inittab, still I get the blank screen on attempting to boot.
Any ideas on what might be wrong here? It really sounds like the intel driver problem people have described, and yet I can't even boot in text mode so that doesn't seem to be the case here. Could there be something wrong with the bootloader?
I have an Acer Aspire One AOA110 (SSD version that came w/ Linpus Lite) that my brother gave to me several months back when it stopped working. I've been trying various ways to revive it or make it useable, but haven't had any luck so I figure it's time to look to the community for ideas. I have already updated the BIOS to the latest (v3310) version, so I don't think it's the common issue these netbooks have where they don't even post. I'm kind of thinking the GPU died halfway or something. If I could just get it to work in a command line only mode, I'd be happy.
The netbook will post fine, but when I try to boot into Linux, the screen will go blank part way through the boot process. I don't ever remember hearing sound afterwards so I don't know if just the screen is blank or if the computer is locked up as well. I have tried several distros, but all of them seem to run into the same issue. Some with text based installers (Debian) get all the way through the install, but won't get all the way through the boot process. I'm only trying to get to a command line, not into X or anything graphical. Arch Linux also uses a text based installer, but I couldn't even get into the installer before the screen goes blank. I've tried changing some of the kernel options such as nomodeset, vesa and framebuffers options, but didn't have much luck with them either. I've also tried some older versions of Ubuntu (I think back to either 8.04 or 8.10) and tried the text installs, but I can't remember if I couldn't get into the installer or if I just couldn't boot, I want to say I couldn't even install. Mind you it's not random, it's always at the same point for a particular distro.
So the other small twist to this all is that FreeDOS works fine, besides not being able to get the sound card or network card working. I can play games, set different resolutions in ZSNES, etc. This seems a little odd to me, but I'm hoping it makes perfect sense to someone reading this.
I want to be able to run Linux with a command line interface, but I can't find the right distro/settings/whatever that it stays in the video mode (vesa?/framebuffer only?/I'm not even sure what to search for) where I keep the display and get to a command line. Any thoughts on what's happening when the screen goes blank or what I can do to get Linux working on here again?
I have an system that d8.2 appears to install correctly. On first (or subsequent) boot, I get the DB8 load screen, then a quick fsck, then nothing. I appear to have some sort of environment running as I can move a mouse pointer, but nothing else.
CTRL-ALT-F2 results in the mouse pointer vanishing, but nothing else. I expected to end up at the CLI.
I have tried different installs and options, always the same result. This machine ran an earlier version with issues.
I have Fedora12 and it was working fine all through. I Installed Skype yesterday and since it was working, I installed the following using instructions from a blog. These were to install
yum install libXv.i686*
yum install libXScrnSaver.i686*
yum install qt.i686
yum install qt-x11*.i686
yum install libsigc++ libsigc++.i686 qt.i686 qt
Skype started to work well. However, after I rebooted the system, all I get is a blank screen with a blinking cursor. I am able ot get to tty by doing ctrl+alt+f2 but am not sure how to proceed from the above. I also erased the above packages thinking that that might solve. But it hasnot solved the issue.
I've run into a strange problem with GDM that I haven't managed to find a solution for yet, either by trying myself or googling, and I have run out of good ideas. I'll just infodump here about the problem and what I've tried etc;
I installed Ubuntu on a new PC a few weeks ago, setting it up with autologin for my mom and a separate user for myself, using the on/off-icon menu in the top-right corner to switch to my own user and back as needed, and logging the user out when done. This worked quite well.
However, a few days ago, this stopped working; logging out or trying to switch now leaves me with a blank black screen, without even a mouse pointer (but not off, the backlight is on).
EDIT: To clarify, this is an issue that only affects the GDM login screen, but that affects it whenever it is used, wether it is on boot (when not set to autologin), after logging out, or when trying to switch user.
At this point, I can usually use Ctrl-Alt-F1 to get a textmode login, and Ctrl-Alt-F7 to get back to the auto-logged in session (assuming I tried to switch, not logout).
I can't think of anything specific I did or installed around then that should be related in any way...
I tried disabling autologin and restarting gdm, which left me with the same black screen (which is still there after rebooting), instead of the expected login window. I managed to re-enable autologin by manually editing the /etc/gdm/custom.conf file, so that it would at least work for mom.
I've also tried to change which user is auto-logged in, thinking it might be a problem with my user account, but both users get an automatic session just fine when I restart gdm.
I thought it might be a problem with the video driver, but that's not the case - if I run zenity --info as root with DISPLAY set correctly, the dialog box appears on the screen just fine. It has no borders or titlebar (there's no windowmanager), and is apparently without keyboard focus, so since there's no visible mouse pointer I can't click the OK button... But since it appears, X is apparently up and running just fine, just has nothing to display other than a black background.
I tried purging and reinstalling gdm and gnome-session(-bin|-common), but that didn't help any.
Running ck-list-sessions after trying to switch indicates that there's a new session there, with session-type = 'LoginWindow', so it appears to think everything's fine.
Enabling debug output in the /etc/gdm/custom.conf file did get me some more debug output in the gdm logs, but it didn't really tell me anything, there weren't any obvious problems that I could see.
After some looking around, I've guessed that it's supposed to be running gdm-simple-greeter, which I assume would display a login box; trying to run it manually doesn't work though (it's missing some environment variables, and trying to add them based on the abovementioned debug output doesn't really help).
I have just installed Debian 7.8.0 powerpc on my imac G3 (400Mhz, 256Mb Ram). I had repartitioned the drive with the view of having a dual boot machine, had OS9 installed on partition 1, linux installed on partition 2 and a ext4 data partition and a 1Gb swap partition. After I installed OS9, I ran Debian Installation CD and was successfully installed. Rebooted, got through the on screen text past file system check, then screen went blank. I searched Google and forund that if I ran ctrl+alt+f1 and logged in, then ran lspci, I could get the ID of the graphics. So I did, and:
Code: Select alllspci
...
0000:00:10 Display Controller: Advanced Micro Devices [AMD] nee ATI Rage 128 RL/VR AGP
It seems I am having the same problem, but on a Toughbook CF-28. I tried searching the forum for a solution, and Google, but to no avail. Here is the run down:Installed Debian 6.0 from the NetInst (i386) CD, and all went well. Re-started the laptop, and all booted up fine (got the code lines). When the login screen should appear, all I get ilackscreen.CF-28 Hardware:RAM: 512MB. CPU: Pentium III Mobile 800 MHz (Im guessing from Google) Searches) Not sure what else it has, no information came with the laptop. I do know it has an ethernet port, which worked durininstall, has no wireless, does have a touch screen.I apologize for my noobness, but I am uber new to Linux. Any ideas on how to resolve this issue?
View 14 Replies View RelatedI installed Debian squeeze on my old Dell Latitude C600 laptop. I Installed it from a cd that worked to a friend of mine. I finished the installation successfully. After booting the computer I can get to the grub screen and after choosing the OS (Debian GNU/LINUX, with linx 2.6.32-5-686) I see the computer loading and running command lines, but after few lines, I get black screen and I hear the computer "working" but can't see anything and it doesn't react to anything that I do.
View 9 Replies View RelatedI have problem with my Debian. Sometimes after reboot I can see only mouse cursor (moveable) and black screen with command prompt in top -left corner. I don't know how to fix it...
Code: Select allroot@debian:/home/rafal# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.1 (jessie)
Release: 8.1
Codename: jessie
[code]....àwwwwwwwwwwwwwwwwwwww~s
I have just installed OpenSUSE 11.2 on an Intel DQ35JO motherboard and XFX 9500GT 512MB video card. After installation the desktop looked fine on the Sony LCD TV I have connected to the 9500GT via a DVI to HDMI cable.
After the first reboot after installation I added the Nvidia repository via the add community repository function in the software sources option in YaST2. I then proceeded to install the Nvidia G02 drivers and the nvidia-settings package. At this point after a reboot I would get a blank screen. Hitting ctrl-alt-F1/F2/F3/F4/F5/F6 has no effect, I could not get any of the virtual consoles to appear. I had to SSH into the box and reboot into runlevel 3.
Once I had rebooted into runlevel 3 I logged in as root and executed "sax2 -r -m 0=nvidia" and got an error message that the configuration server could not be started. I tried executing "sax2 -r -m 0=vesa" and received the same error:
[Code]....
I've just put a fresh install of 64 bit Lenny on my new HP server. All went well so I thought to install KDE. On reboot, the screen just goes black.Could I have some helpful suggestions on how to start working out what the problem could be?
View 7 Replies View RelatedI have been trying to install openSUSE on a dell Latitude XT all day, and every time I tried to live boot, I got a blank screen. I finally decided to do a text install and I got it installed, but now I get the same result from booting off of the splash screen.
I can boot into text mode fine (still) but for whatever reason, it bombs as soon as I tell it to load the GUI. I have a 1.2 GHz Core 2 Duo, 3GB RAM, and an ATI mobility chip (2000 series, maybe?) I had the same problem with Ubuntu, and since I like openSUSE just as well, I figured I'd try it because I at least could do a text install from my liveCD.