PDA

View Full Version : My toshiba laptop don' boot with kernel 2.6.34



chepioq
16th June 2010, 10:03 AM
I want test rawhide F14, that work with kernel 2.6.33, but when I update with a 2.6.34 fc14, my laptop don't boot.
And problem: I have no log for this boot...
My laptop is an toshiba X200 with an nvidia card (and the kmod nvidia work fine with the 2.6.33)

glennzo
16th June 2010, 10:24 AM
Boot with a working kernel and post grub.conf and fdisk -l. Maybe someone can help sort it out.

chepioq
16th June 2010, 10:35 AM
grub.conf

# 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,7)
# kernel /vmlinuz-version ro root=/dev/sda9 rdblacklist=nouveau rdblacklist=nouveau rdblacklist=nouveau
# initrd /initrd-version.img
#boot=/dev/sda8
default=0
timeout=10
splashimage=(hd0,7)/grub/splash.xpm.gz
hiddenmenu

title Fedora (2.6.34-38.fc14.x86_64)
root (hd0,7)
kernel /vmlinuz-2.6.34-38.fc14.x86_64 ro root=UUID=215e72f1-9f2d-4940-96d8-f0f28c3854a3 rhgb vga=0x365 quiet LANG=fr_FR.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=fr-latin9 rd_plytheme=charge rdblacklist=nouveau
initrd /initramfs-2.6.34-38.fc14.x86_64.img

title Fedora (2.6.34-20.fc14.x86_64)
root (hd0,7)
kernel /vmlinuz-2.6.34-20.fc14.x86_64 ro root=UUID=215e72f1-9f2d-4940-96d8-f0f28c3854a3 rhgb vga=0x365 quiet LANG=fr_FR.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=fr-latin9 rd_plytheme=charge rdblacklist=nouveau
initrd /initramfs-2.6.34-20.fc14.x86_64.img

title Fedora (2.6.33.4-95.fc13.x86_64)
root (hd0,7)
kernel /vmlinuz-2.6.33.4-95.fc13.x86_64 ro root=UUID=215e72f1-9f2d-4940-96d8-f0f28c3854a3 rhgb vga=0x365 quiet LANG=fr_FR.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=fr-latin9 rd_plytheme=charge rdblacklist=nouveau
initrd /initramfs-2.6.33.4-95.fc13.x86_64.img



fdisk -l

[root@localhost ~]# fdisk -l

Disque /dev/sda: 120.0 Go, 120034123776 octets
255 têtes, 63 secteurs/piste, 14593 cylindres
Unités = cylindres de 16065 * 512 = 8225280 octets
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identifiant de disque : 0x00092119

Périphérique Amorce Début Fin Blocs Id Système
/dev/sda1 * 1 64 514048 83 Linux
La partition 1 ne se termine pas sur une frontière de cylindre.
/dev/sda2 65 1466 11261565 83 Linux
/dev/sda3 1467 1568 819315 82 Linux swap / Solaris
/dev/sda4 1569 14593 104623312+ 5 Etendue
/dev/sda5 1569 11441 79304841 83 Linux
/dev/sda6 12730 12793 514048+ 82 Linux swap / Solaris
/dev/sda7 12794 14593 14458468+ 83 Linux
/dev/sda8 11442 11505 511999+ 83 Linux
/dev/sda9 11505 12729 9833859 83 Linux

Les entrées de la table de partitions ne sont pas dans l'ordre du disque
[root@localhost ~]#

when I boot on a 2.6.34 kernel it's hang at:
configuration du nom d’hôte localhost.localdomain: OK

I stay for 15 minutes but nothing after...

Zanpactou
16th June 2010, 11:58 AM
I want test rawhide F14, that work with kernel 2.6.33, but when I update with a 2.6.34 fc14, my laptop don't boot.
And problem: I have no log for this boot...
My laptop is an toshiba X200 with an nvidia card (and the kmod nvidia work fine with the 2.6.33)
Stick with 2.6.33 then.
Change :


default=0
To :


default=2
In grub.conf and when you update (In future, until you can confirm it's fixed) Use :


sudo yum --skip-broken upgrade -x kernel*
Which will skip any broken packages and avoid anything kernel related.

Look in the file /var/log/dmesg as root, to see if anything there helps you spot the regression.

Thanks,
Zanpactou

rockdoctor
16th June 2010, 06:27 PM
My experience has been that I can't compile the nvidia driver with the current Fedora Rawhide kernels, so I'm running with the nouveau driver. With the nouveau driver, that infamous bad benchmark, glxgears, runs at about 1/4 the framerate I was getting with the nvidia driver, but I can live with it. No problems running compiz.

Without a valid nvidia driver, and (presumably) with nouveau blacklisted, Xorg isn't going to be too happy.

Zanpactou
17th June 2010, 01:36 AM
My experience has been that I can't compile the nvidia driver with the current Fedora Rawhide kernels, so I'm running with the nouveau driver. With the nouveau driver, that infamous bad benchmark, glxgears, runs at about 1/4 the framerate I was getting with the nvidia driver, but I can live with it. No problems running compiz.

Without a valid nvidia driver, and (presumably) with nouveau blacklisted, Xorg isn't going to be too happy.
Ah, I see. So kmod nvidia black lists nouveau. Ha, ha. I love the way that nvidia are still trying to hold on to their idea that they have any value in creating their own closed source driver instead of contributing to the open source nouveau project or making their proprietary extensions available for the nouveau drivers as modules.
Maybe one day they'll wake up.

So from what you say rockdoctor, it could well be that chepioq must uninstall kmod nvidia to use the latest rawhide kernels, however that means nouveau drivers, which work with some indifference on some hardware. Or chepioq can just stick with 2.6.33 and not update the kernel, for which kmod nvidia is known to work for.

chepioq, what you need to understand is that nvidia's proprietary gpu driver is bad for Linux development because they struggle to keep it current. That's why we have nouveau because nvidia are stalling everyone in the distribution chain because they can't push their code out in time and they don't want to (Or have put themselves in a position where they can't) Share the source code with people who have offered to help them.

So in short, nvidia's proprietary gpu driver won't always work with the latest kernel releases (And history so far has shown that it never has, you wait about a month or two usually for the update.) You must use the nouveau drivers in rawhide if you want to track the latest kernel releases and that means uninstalling kmod nvidia.
Your alternative is to stick with the kernel that works with kmod nvidia and just don't update the kernel when you use yum to do a software update from the rawhide repos.
That way, you'll still be testing rawhide but without the latest kernel available in rawhide.

Thanks,
Zanpactou

chepioq
17th June 2010, 05:39 AM
So in short, nvidia's proprietary gpu driver won't always work with the latest kernel releases (And history so far has shown that it never has, you wait about a month or two usually for the update.) You must use the nouveau drivers in rawhide if you want to track the latest kernel releases and that means uninstalling kmod nvidia.
Your alternative is to stick with the kernel that works with kmod nvidia and just don't update the kernel when you use yum to do a software update from the rawhide repos.
That way, you'll still be testing rawhide but without the latest kernel available in rawhide.

Thanks,
Zanpactou

But leigh, in this thread http://forums.fedoraforum.org/showthread.php?t=239527&page=3 post#32, say that nvidia driver work with a 2.6.34 kernel...

Does anyone has managed to install nvidia drivers with 2.6.34 kernel?

Zanpactou
17th June 2010, 11:16 AM
in this thread http://forums.fedoraforum.org/showthread.php?t=239527&page=3 post#32, say that nvidia driver work with a 2.6.34 kernel...
It doesn't say if that patch was tested against the 64 bit or the 32 bit version of the driver.
It maybe that you have found another bug and you may find better help on the nvidia forums.
The Fedora community is more concerned with nouveau because anyone can try to fix the source code for that.

You probbably just need to re-build the kmod yourself for the kernel you want to use. But you'll be doing that almost every time you update in rawhide, as kernels change quite frequently in the development repo.

Thanks,
Zanpactou