Slackware :: 13.1 Nvidia Framebuffer Woes - Blank Screen After Lilo
Jun 9, 2010
Just upgraded my system from 13.0 to 13.1 Most things went pretty smoothly, but I tried 'startx' before the post-upgrade/config reboot and the system hung - "time to upgrade my video drivers", I thought. Upgraded to Nvidia 195.36.15*. X works perfectly, and a modprobe shows the 'nvidia' module loaded. So far so good.
However, when I try to use any vesa modes in lilo, I get a blank screen after the BIOS check and the system hangs - even toggling numlock on or off won't work... So I can only boot up in text mode. This makes me unhappy, partially because I like penguins, but also because it is an absolute insult to my new (old) monitor. I thought this could be to do with the nouveau conflicts reported by -current users some days ago, but the respective blacklist file is present so I'm stuck as to what to do... *I've tried 195.36.15, 195.36.24 and the latest 2xx beta drivers. All exhibit the same behaviour.
EDIT - forgot to post my video card specs. It's an 8500gt w/ 256mb, 128-bit DDR3.
Got an Asus eeepc 900a. Runs Intel 915 graphics. Upgraded to slackware current last week. X would not start. Based on info here, I reverted back to earlier libdrm and xf86-video-intel. That got it working again.
Updated Slackware current again today. I think I got a new kernel. Now, halfway through boot time, the screen goes blank, then comes back and the font is tiny. Gone into framebuffer mode. If I start X, it just freezes. Nothing but a reboot will get out of it.
I have vga=normal in lilo.conf, but I read that this is no longer used. I can find no way to turn off framebuffer mode. From other threads here, I have tried append="i915.modeset=1" in lilo.conf. Has no effect.
I could revert Slackware to 13.0 from current, and that would make the eeepc useful again. Is there anything else I should try?
I just went out and bought a 19" flat screen LCD monitor. Plugged it in and it is not working correctly. When I start the computer the bios info will show up on the screen, then it goes to the screen that let's you choose an O/S if you were to dual boot. After clicking "enter" it will show the first line of the boot then it goes off into horizontal colors then goes black. I have search many different posts and googled but nothing is giving me a hint at this.I changed the xorg.conf to match the refresh rates to match the monitor but that did not work, and did not really think it would considering the point this monitor goes out on me. running: 2.6.27.7-smp 01:00.0 VGA compatible controller:
Silicon Integrated Systems [SiS] 315PRO PCI/AGP VGA Display Adapter
My F11 system display goes blank after some time of inactivity and I cannot see how to disable it. It does not appear to t eht screen savers (all turned off). I have an NVIDIA card,, is it in the card?
I did a fresh install of 8.04 alternate disk with LVM then updraded to 10.04 (due to lack of any spare CDs around).
Everything was working fine but wanted to try to get the nvidia-173 drivers installed (I have an old FX5200). Can't start into X now as my plasma says mode unsupported.
At one point I managed to boot into recovery mode then root terminal and removed all nvidia packages and reinstalled nvidia-173 only and followed the instructions listed on the 10.04 release candidate page. Still stuck with the unsupported modes error on my TV though. I have a 720p plasma display (1366x76, I usually run 1280x768 without issues. I'm guessing it is the refresh rate set in the new xorg.conf that is throwing me off, how to adjust this?
An issue that's complicating things however is that when I try to boot into recovery mode I get an error stating 'pcspkr' driver already registered, aborting... then it hangs there until I ctrl-alt-delete and force a restart. This is preventing me from getting to the point where I can select a a root terminal to try to fix my errors.
I have used 8.04 exclusively for a few years and wanted to try something new (still not all that adept at linux setup).
EDIT: I managed to get to root again and just removed the xorg.conf file and that seems to work somewhat. Except now I can't boot as I get a looping mountall: Plymouth command failed that hangs up the process.
I have just bought a Dell Optiplex 960 with a NVIDIA Quadro NVS 450. Everything works out of the box with the 10.04.1 Live CD. It suggests to install and activate NVIDIA proprietary drivers, but you need to restart the machine afterwards. The problem is that, after that, all what you get is a blank screen, with not even a cursor. The same happens when you install Lucid: blank screen with no cursor. Ctrl+F1 does not show anything, but Ctrl+Alt+Prnt Scrn+REISUB works and the PC is reset. In the var directory the logs show that the NVIDIA module is not loaded.
Running 2.6.33.3-85.fc13.i686 and just purchased a AGP 7600GT 512 video card. Searched around and found:I did the rpm, yum, sed, mv & dracut as directed. Then I rebooted. When it starts up (all the normal bios messages) and then I 1/2" bar across the bottom of the screen with Fedora 13 on the right end and .... nothing. Just sits there. I've used my Live-13 disk and tried to reverse the procedure but I'm starting to think it's the video drivers.
I installed OpenSuse Gnome version 64 bit on a HP laptop DV7 Intel Dual Core with nVidia 9600 GM cardAll went well, until after I had installed the nVidia drivers from this page: NVIDIA drivers - openSUSEI selected the Geforce 1-click install and Yast went on to installl all the packages (a lot of 32-bit),took about half an hour.I logged out/in, and could work as normal, until I rebooted. Maybe I waited not long enough (5 minutes), but the screen was blank, then I gave up.Anyone has an explanation. I can always re-install everything, but then what went wrong with the nVidia package
I ran the latest updates this week (including the new kernel and the new kmod-nvidia update) and I got a blank screen when I rebooted. (I get the Fedora bar across the bottom of the screen, then after that the screen goes blank) I assume this is when the xorg server is trying to start..
I went into single user mode , backed up and then removed the xorg.conf file but still got a blank screen upon reboot.
I rebooted into single user mode, copied the /var/log/Xorg.0.log file to a safe location, and then restored the system back to its original state.
I've since rsync'd my system back to where it was before the update.
I've posted this to the fedora mailing list with no response, my apologies if it's been addressed here...
I have an IBM Thinkpad with an Nvidia card ( nVidia Corporation GT218 [NVS 3100M] (rev a2) )
I currently have the nouveau driver black listed in my grub.conf setup: rhgb quiet nouveau.modeset=0 rdblacklist=nouveau
I did the update which installed/updated the following:
---> Package kernel.i686 0:2.6.35.14-95.fc14 set to be installed ---> Package kernel-devel.i686 0:2.6.35.14-95.fc14 set to be installed ---> Package kernel-headers.i686 0:2.6.35.14-95.fc14 set to be updated ---> Package kmod-nvidia.i686 1:280.13-2.fc14 set to be updated
However when I reboot the system boots to a blank screen, and even the previous kernel boots to a blank screen. I tried installing akmod-nvidia but get the same results
I've restored the system back to before the update for now..
I have just performed an upgrade from OpenSUSE 11.2 to 11.3. My Machine is a Lenovo W701DS laptop which uses an NVIDIA FX3800M graphics card. The system was working fine under 11.2 before the upgrade.
After upgrading to 11.3 the splash screen after GRUB comes up for about 1 second before the screen goes blank. After about 5 mins I am able to SSH to the Laptop and access the system. Doing this I created an xorg file using "X -configure" and copied the new file to the /etc/X11 directory and renamed to xorg.conf.
If I SSH to the laptop change run levels to init 3 then init 5 the Gnome comes up and I have graphics the system works However I am unable to access the text consoles using alt+f1, f2 etc. If I restart the system it is back to the blank screen.
I have attempted to install the NVIDIA drivers however the installation fails due to an error with gcc or kernel source versions. Error log reports that the kernel was complied using a different version of gcc.
I have installed Ubuntu Maverick 10.10 RC in my PC, everything works fine, but after install Nvidia proprietary Graphics driver it boot up on a blank screen (I can hear the login sounds, etc) but screen is absolutely black.
I try to login in recovery mode and check if something is wrong but nothing happens (even adding noveau driver to a blacklist (editing grub)) Now I have re installed Ubuntu 10.04.1 and works fine but I would like to install the 10.10 version, since I have this inconvenience, I cant do it.
My graphic card: Nvidia Gforce 8400GS 256MB Pci Express
i did yum -y install akmod-nvidia and then type xconfig-nvidia on the terminal,and after logging off i confront with a blank screen,so i remove akomd-nvidia [yum remove akomd-nvidia] and also yum erase xorg-x11-drv-nouveau [yum erase xorg-x11-drv-nouveau]but still no gui,i think i should install:
yum install kmod-nvidia xorg-x11-drv-nvidia-libs.i686 xorg-x11-drv-nvidia-libs.x86_64 [but i didn't] so how can i have my gui back?
I got the nVidia driver and Compiz installed. Everything's running fine . But then I tried crtl+alt+F1 - which worked though the font was way too big - and then crtl+alt+F7 to get back to the Desktop but it went to a black screen and blinking cursor instead. I searched a bit and it seems this was a problem a few years back but nothing recent. FWIW, I don't have this problem with Hardy/nVidia/Compiz on another drive in this same machine. Is there a way to fix this?
I recently followed instructions to enable the nvidia driver. run the following commands:
[Code]....
then rebooted, a tricoloured loading bar appeared and finished, then all i got was a blank screen with flashing cursor. I don't get a prompt to login and can't access my account. I am dual booting on this machine with ubuntu, is there anyway i can restore my fedora partition and enable my nvidia graphics
I have just bought a Dell Optiplex 960 with a NVIDIA Quadro NVS 450. Everything works out of the box with the 10.04.1 Live CD. It suggests to install and activate NVIDIA proprietary drivers, but you need to restart the machine afterwards.The problem is that, after that, all what you get is a blank screen, with not even a cursor.The same happens when you install Lucid: blank screen with no cursor.
Ctrl+F1 does not show anything, but Ctrl+Alt+Prnt Scrn+REISUB works and the PC is reset.In the var directory the logs show that the NVIDIA module is not loaded.
I'm installing 10.10 on a desktop with Nvidia 6150 that needs nomodeset on boot or i get the blank screen upon boot. I had to force the live CD to nomodeset when booting from the CD. I was finally able to install, but upon the first boot from the hard drive I'm getting the blank screen again. How do I boot with nomodeset and get to my installed ubuntu. Once I get there i can edit my grub settings.
After installing debian squeeze I tried installing a nvidia driver. I had to type: /etc/init.d/gdm3 stop The nvidia driver wouldn't install because the 'make' command was missing in a path or something. Now I cannot get the GUI anymore. startx gives me a blank screen rebooting the computer gives me a blank screen. I can only boot in recovery mode. but the nic doesnt work so no internet connection.
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:
I have a clean install of slackware 13.37, downloaded today from slackware64current. On boot, I get a black screen - not just black, but no video signal out of the video card, or at least nothing that the monitor recognizes. Fortunately, I can ssh into the box from another machine. If I do, I can startx and xfce starts up and appears as expected. lspci shows:
01:05.0 VGA compatible controller: ATI Technologies Inc Device 9714 02:00.0 VGA compatible controller: ATI Technologies Inc Device 6898
I have an onboard video chipset with a monitor connected to it, and an ATI 5970 in a pcie slot with a monitor also connected to it. xfce appears on the pcie card (the 5970) as expected, as this is (supposedly) the primary monitor, and the monitor connected to the onboard video output is blank - no signal, also as expected as I have not yet installed the ATI drivers. So the question is - how do I get the terminal output on bootup to appear on one of my monitors? I'm not sure where it is going, and this is out out of my area of expertise.
After all the package upgrading, removing obsolete packages, running lilo etc, I rebooted and I was really taken by surprise. Apparently, this certain intel graphics card doesn't work right with KMS. The boot process starts, I get to see the two tux twins and a few lines of boot messages, but as soon as KMS kicks in, everything goes completely blank. It doesn't crash or freeze or anything, the boot process continues, but it's all blank.
What's completely weird is that I have another laptop, which reports exactly the same graphics card, but KMS works fine there with current!
Anyway, I did some google search and I found that it's a common problem. There was a suggestion to remove any vga=... lines from lilo.conf, but that didn't help at all. Adding nomodeset to my boot options, disabled KMS, and I was able to boot to init 3, just like in 13.0. The problem was that then, it wasn't possible to launch X, because the intel driver that is included in current requires KMS to work!
So, after trying out a few different versions of the intel driver, I found that anything from 2.8.x and down wouldn't compile and that anything after and including 2.10.x require KMS. The only versions that would work are 2.9.0 and 2.9.1, which seem to have an identical effect here. They both work, but I have artifacts using my favorite mouse cursor theme, I get a black box instead of the mouse cursor. Not a big deal and choosing another theme fixed that too.
What I'm thinking is that probably more people will have the same problem and nothing is more frustrating than a completely blank screen. Maybe it would be a good idea to keep the 2.9.x versions of the driver in /extra. That and perhaps also add a note in the UPGRADE docs about adding nomodeset if you have an intel graphics card and you get a blank screen.
When she wants to log into xfce, there is only a blank screen. The cursor shows, but there is no way to go any further. No panel, buttons or background.
However, she is able to log in using XDMPC from a local computer without a problem.
There are the processes active under both settings.
Questions: What may have caused xfce not to load some modules on log in? How to fix it, to allow a normal login? How to prevent this problem in the future?
I'm using the 270.41.19 nvidia properietary driver for my Geforce GTX460 graphics card. I have a Sony TV connected to my HDMI and I know it supports the 1920x1080 resolution. Yes it works after gnome or other DE loads up.
But during the GRUB screen and the bootup console - It defaulted to a 640x480 resolution (as it always does with the nvidia prop driver). I usually used to check the output of hwinfo --framebuffer and choose the resolution by appending the right vga=0xabc parameter.
But now I have a problem since hwinfo says the best widescreen 16:10 framebuffer resolution that my card supports is 1280x800. Here is the output from hwinfo --vbe which should give the info about both my gfx card and my TV.
The initial nouveau driver was able to output native 1920x1080 during the bootup on the console without issues, so I guess even the properietary driver should be able to output (If my understanding is right the nvidia module loads later during the bootup and only is required for the X but not for the console itself).
I've just installed Slackware 13.37 x64.Right now, everything is fine! All hardware OK, sound OK, Network/WiFi OK, nVIDIA Proprietary drivers OK, KDE Composite OK, Desktop effects OK.But when initializing, the messages pass very slow!My lilo framebuffer settings are 1024x768x64 (Code 791, 317 in Hex), my Graphics card is an nVIDIA GeForce 9100 M G (256Mb), but yet, I can see it refreshing like an image loading in 56Kbps connection. I really would like to use framebuffer during boot (Oh, come on... The little penguin is kinda neat :-), so I'll ask... Is there a way to use my graphic driver in framebuffer, or make it faster?
Slack 13.0 X sometimes fails to start after boot about 50% of the time. linux says "starting X11 session" then I get a blank screen with a flashing cursor and absolutely nothing else. I can <ctrl>-<alt>-<F7> and get a text prompt, log in, and startx from a command prompt. After that, I can reboot once or twice and still get a graphic login, but will soon revert to the dumped condition. I have reinstalled X and KDE twice now as well as deleting my .kde folder. This condition started when I inadvertently ran out of disk space on my /home drive. Since then I have migrated /home to a larger drive and watch it's disk space very carefully.
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.
I am using the most recent -current (that fixes the libpng "ratness" described in the ChangeLog 8-) and the Intel Framebuffer setup is annoying me. I specify vga=normal in LILO and to my knowledge I am not asking Intel Framebuffer modules to load at boot (and intelfb is blacklisted).
It's annoying because it makes the text microscopic. However, the machine works great in -Current so I can't complain. Graphics work fine and so does X, it's just annoying.
This is my Sony Vaio VGN-C140G detailed here: url
I had tried previously blacklisting inteldrmfb as well (the -Current release right before the libpng fix) and that made no difference.
I found all binaries with "intel" in their name and read the manual pages but didn't find anything useful for possibly manually setting the mode back to something equivalent to vga=normal.
I'm trying to install Puppy 525 on my Slackware 13.37 PC as a dual-boot using LILO. Puppy is living, all on it's own, in sda6, a 6 GiB partition. It got there by using the Puppy Universal Installer and selecting a 'Full' install, not a 'Frugal' install. I cannot find 'LILO' type instructions, only 'GRUB' type instructions.
Has anyone succeeded in doing a hard drive install of Puppy with the LILO boot loader?
Edit: I'll probably regret it, but I used Puppy's GRUB installer.
I'm fairly new to Linux so I'm going to need a step-by-step guide to get me out of this rut. The install of Linux was fine but when I booted up I got this error. VFS: Cannot open root device "302" or unknown-block (3,2) append a correct "root=" boot option;here are the available partitions;
0800 78150744 sda driver:sd 0801 47428608 sda1 <-- this is my Windows partition 0802 30719552 sda2 <-- this is my Linux partition 0b00 1048575 sr0 driver:sr 0b01 1048575 sr1 driver:sr
Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (3,2) I guessed from reading this error Lilo isn't pointing to the right partition to boot from? How will I fix this? I read another thread about boot problems on these forums and a guy said to do this:
#mkdir /slacktemp #mount /dev/device /slacktemp #chroot /slacktemp #cd /slacktemp/etc <-- for me it told me that doesn't exist #vi lilo.conf <-- couldn't do nothing and was frozen #lilo -v -t -b /dev/device #lilo -v -b /dev/device
The above solution did not work for me. Can anyone shed a light on a Linux rookie?
I just did a fresh install of slack 13.1 on a separate drive to the one I was previously using. I've been having trouble getting lilo to work, so that I can choose between either drive. Lilo is currently installed to /dev/sda, with the old system on /dev/sda1 and the new installation on /dev/sdb1. I keep getting errors like these:
Code: Fatal: Trying to map files from unnamed device 0x0011 (NFS/RAID mirror down ?) I managed to install lilo from the old system by copying the kernel image from the new system into the /boot/ directory and running lilo. I am now on the new system and trying the same thing in reverse but it isn't working. I have searched around a bit and there's a lot of talk of chroot-ing into the other partition to run lilo. I don't understand why the process isn't working both ways though. I can't run lilo on my new installation even with the two kernel images in the local /boot/ folder. Is this something to do with btrfs or am I missing something to do with lilo? This is my lilo.conf file. I am trying to run lilo using this file from my new installation on /dev/sdb1 and getting the error given above.
