Re: latest kernel boots to a blank screen

As a general rule, I would reccomend removing 'rhgb' and 'quiet' from your
kernel parameters in grub.conf. This will show more info during boot, and
possibly aid in diagnostics.

I'm following this thread with interest after giving up on my own battle
with the same issue. After adjusting grub.conf as above, I did note that I
could boot further if I added 'vga=34A' ('34a' being what was right for
me) to the kernel parameters, but I'm not sure what this signifies.

I'm able to run this kernel without kmod-nv idia, so I've decided to use
nouveau drivers until the next update.

Thanks for the info. I'll be sure to post a SOLVED message to the list if I
get it working...



Sorry I can't offer more help...

Pete
-----Original Message-----
From: Michael Miles <mmamiga6@xxxxxxxxx>
Date: Tue, 23 Mar 2010 15:03:22
To: Community support for Fedora users<users@xxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: latest kernel boots to a blank screen

On 03/23/2010 01:52 PM, Kevin Kempter wrote:
You must blacklist nouveau in the edit /etc/grub.conf and add the
following to the end of the line(s) starting with 'kernel':

rdblacklist=nouveau



Before using the driver, you need to lower your system protection so
SElinux doesn't prevent the driver to load.

setsebool -P allow_execstack on


http://rpmfusion.org/Howto/nVidia#head-205aab6f190d363e3915c0fa2e0681fc3
92a aeb6


Make sure the kernel extensions are intalled with the Nvidia Driver

That's it

Michael Miles

On 03/23/2010 09:52 AM, Kevin Kempter wrote:
Hi all;

I've updated to the latest kernel and it boots to a blank screen,
nvidia does not start.

Here's what I have installed:

[/root]
root@Issac # rpm -qa | grep kernel | sort
abrt-addon-kerneloops-1.0.8-2.fc12.x86_64
kernel-2.6.31.12-174.2.19.fc12.x86_64
kernel-2.6.31.12-174.2.22.fc12.x86_64
kernel-2.6.32.9-70.fc12.x86_64
kernel-devel-2.6.31.12-174.2.19.fc12.x86_64
kernel-devel-2.6.31.12-174.2.22.fc12.x86_64
kernel-devel-2.6.32.9-70.fc12.x86_64
kernel-firmware-2.6.32.9-70.fc12.noarch
kernel-headers-2.6.32.9-70.fc12.x86_64

[/root]
root@Issac # rpm -qa | grep nvidia | sort
akmod-nvidia-190.53-3.fc12.x86_64
kmod-nvidia-190.53-3.fc12.x86_64
kmod-nvidia-2.6.31.12-174.2.19.fc12.x86_64-190.53-1.fc12.4.x86_64
kmod-nvidia-2.6.31.12-174.2.22.fc12.x86_64-190.53-3.fc12.x86_64
kmod-nvidia-2.6.32.9-70.fc12.x86_64-190.53-3.fc12.x86_64
nvidia-settings-1.0-3.4.fc12.x86_64
nvidia-xconfig-1.0-2.fc12.x86_64
xorg-x11-drv-nvidia-190.53-4.fc12.x86_64
xorg-x11-drv-nvidia-libs-190.53-4.fc12.x86_64


f I boot into the 2.6.31.12 kernel all is fine.

Any help, advice, thoughts?


Thanks in advance

I did the following but still no joy:

changed my /etc/grub.conf file to have the rdblacklist=nouveau :

root@Issac # cat /etc/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file # NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,0)
# kernel /boot/vmlinuz-version ro root=/dev/sda1
# initrd /boot/initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.32.9-70.fc12.x86_64)

root (hd0,0)
kernel /boot/vmlinuz-2.6.32.9-70.fc12.x86_64 ro

root=UUID=91673aa6-9636-4490-af4e-3c79a684a2d9 nomodeset LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
rdblacklist=nouveau

initrd /boot/initramfs-2.6.32.9-70.fc12.x86_64.img

title Fedora (2.6.31.12-174.2.22.fc12.x86_64)

root (hd0,0)
kernel /boot/vmlinuz-2.6.31.12-174.2.22.fc12.x86_64 ro

root=UUID=91673aa6-9636-4490-af4e-3c79a684a2d9 nomodeset LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet

initrd /boot/initramfs-2.6.31.12-174.2.22.fc12.x86_64.img

title Fedora (2.6.31.12-174.2.19.fc12.x86_64)

root (hd0,0)
kernel /boot/vmlinuz-2.6.31.12-174.2.19.fc12.x86_64 ro

root=UUID=91673aa6-9636-4490-af4e-3c79a684a2d9 nomodeset LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet

initrd /boot/initramfs-2.6.31.12-174.2.19.fc12.x86_64.img
>
> Before using the driver, you need to lower your system protection
> so

SElinux doesn't prevent the driver to load.

setsebool -P allow_execstack on

I have SE-Linux disabled

Make sure the kernel extensions are intalled with the Nvidia Driver

not sure what this means, are you referring to the kmod-nvidia packages?
If so I do have 'em installed - see my listing above.


Am I missing something else? I still boot to a blank screen.

Thanks in advance

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/mapper/VolGroup-lv_root
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=0
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.32.9-70.fc12.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32.9-70.fc12.x86_64 ro
root=/dev/mapper/VolGroup-lv_root nomodeset LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
rdblacklist=nouveau
initrd /initramfs-2.6.32.9-70.fc12.x86_64.img
title Fedora (2.6.32.9-67.fc12.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32.9-67.fc12.x86_64 ro
root=/dev/mapper/VolGroup-lv_root nomodeset LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
rdblacklist=nouveau
initrd /initramfs-2.6.32.9-67.fc12.x86_64.img
title Fedora (2.6.31.5-127.fc12.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.31.5-127.fc12.x86_64 ro
root=/dev/mapper/VolGroup-lv_root nomodeset LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
rdblacklist=nouveau
initrd /initramfs-2.6.31.5-127.fc12.x86_64.img
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Relevant Pages

  • RE: fedora-list Digest, Vol 70, Issue 59
    ... Latest Kernel causes reboot hell ... Subject: Fedora on Macbook Air? ... Chad>When it comes to booting from a disk drive, I believe the Air only boot OS's ... someone decided to set up grub by default to hide its ...
    (Fedora)
  • Re: Etch on USB-HD wont boot - race condition?
    ... notebook but the kernel cannot find the root filesystem. ... I had an initial problem that I think I got solved: On boot, ... Begin: Mounting root file system... ... SCSI device sda: 78140159 512-byte hdwr sectors ...
    (Debian-User)
  • Re: install woes
    ... looking at the Fedora 9 64bit DVD: ... I'd try the acpi=off, but I didn't need any boot options, as far as I remember ... appended the kernel, probably post-install. ... but on attempting to install, it freezes up at the test media screen. ...
    (Fedora)
  • Re: 2.6.9-rc2-mm1
    ... Fails to boot on my Altix. ... diff between 2.6.9-rc1-mm4 and 2.6.9-rc2 indicates some kind of PCI, ... Mounted root readonly. ... -doneshowconsole: Warning: the ioctl TIOCGDEV is not known by the kernel ...
    (Linux-Kernel)
  • Re: Will FC8 be getting the 2.6.24-2 kernel?
    ... You don't want this kernel to be introduced into this version of Fedora. ... I did have to do a hardware reset early this morning, my boot drive was reporting a tummy ache that has me worried about its health. ...
    (Fedora)