kernel not booting

[milomak]

i did a f13 to rawhide update. It seems to have taken.

# cat /etc/*release
Fedora release 15 (Finian)
Fedora release 15 (Finian)
Fedora release 15 (Finian)


# yum list fedora-release
Loaded plugins: presto, protectbase
0 packages excluded due to repository protections
Installed Packages
fedora-release.noarch 15-0.2 @rawhide/13

The above I get when I chroot into the system.

When I boot the kernel 2.6.36-0.4.rc1.git1.fc15.x86_64, the screen just remains blank. The only other kernel choice is the last f13 kernel I had (2.6.33.6-147.2.4.fc13.x86_64). It starts to boot and then just stops


Welcome to Fedora release 15 (Finian)!
Starting Supports the direct execution of binary formats....
Starting System Initialization...
Starting jexec servicesStarting Arbitrary Executable File Formats File System...
Welcome to Fedora
Starting udev: Starting Huge Pages File System...
Starting POSIX Message Queue File System...
[ OK ]
Setting hostname jongi-main: [ OK ]
Setting up Logical Volume Management: 1 logical volume(s) in volume group "Data" now active
[ OK ]
Checking filesystems
fedora: clean, 226140/1310720 files, 2085137/5242880 blocks
home: clean, 43512/981120 files, 1717777/3921860 blocks
[ OK ]
Remounting root filesystem in read-write mode: [ OK ]
Mounting local filesystems: [ OK ]
Enabling local filesystem quotas: [ OK ]
Enabling /etc/fstab swaps: [ OK ]
ip6tables: Applying firewall rules: Starting monitoring for VG Data: Checking kmods exist for 2.6.33.6-147.2.4.fc13.x86_64[ OK ]
1 logical volume(s) in volume group "Data" monitored
[ OK ]
[ OK ]
Checking for module nvidia.ko: [ OK ]
Enabling the nvidia driver: Traceback (most recent call last):
File "/usr/sbin/nvidia-config-display", line 28, in <module>
import livnaConfigDisplay.ConfigDisplay
File "/usr/lib/python2.7/site-packages/livnaConfigDisplay/ConfigDisplay.py", line 29, in <module>
import xf86config
File "/usr/lib64/python2.7/site-packages/xf86config.py", line 1, in <module>
import ixf86config
ImportError: /usr/lib64/python2.7/site-packages/ixf86configmodule.so: undefined symbol: xstrtokenize
[FAILED]
Starting portreserve: Starting auditd: [ OK ]
[ OK ]
Starting system logger: Starting irqbalance: [ OK ]
[ OK ]
Starting rpcbind: [ OK ]
Enabling ondemand cpu frequency scaling: [ OK ]
Starting NFS statd: Retrigger failed udev events[ OK ]
Starting cups: Starting RPC idmapd: Initializing OpenCT smart card terminals: [ OK ]
[ OK ]

[ OK ]
[ OK ]
Starting HAL daemon: Starting lm_sensors: loading module coretemp w83627ehf [ OK ]
[ OK ]
Enabling Bluetooth devices:Starting crond:
Starting ntpd: Starting PC/SC smart card daemon (pcscd): [ OK ]
[ OK ]
Starting sshd: Starting sendmail: [ OK ]
[ OK ]
[ OK ]
Starting sm-client: [ OK ]
Enabling monthly Smolt checkin: [ OK ]
[ OK ] atd: [ OK ]


Any ideas what could be causing the boot failure?

[GoinEasy9]

I'll take a stab at it ... you had Nvidia proprietary graphics running and there are no blobs in rawhide rpmfusion to replace them? You'll have to remove all the files for the Nvidia graphics driver and use nouveau, unless you want to try and build one, but, I don't know if that's possible yet with the 2.6.36 kernel. I'm using nouveau, so I haven't tried the Nvidia blobs. I don't know what ixfconfigmodule does, I'm guessing it has to do with setting up the Nvidia graphics.
The older kernel may be having problems with the new systemd, maybe something didn't come in with the upgrade. Try adding "init=/sbin/upstart" to the older kernel line and see if you can make it boot. If that works, remove the Nvidia graphics files and try booting the 2.6.36 kernel again.

---------- Post added at 06:19 PM CDT ---------- Previous post was at 06:15 PM CDT ----------

If you have an AMD processor, there have been problems booting with the most recent 2.6.36 kernels. See the other thread.

[andrewthomas]

Grab kernel-2.6.36-0.0.rc0.git1.fc15 from koji

http://koji.fedoraproject.org/koji/buildinfo?buildID=188293

all of the newer versions do not boot for me

[jvillain]

My experience is the same as andrewthomas. I read some where that it is AMD related. I am now up to rc4 and still no action. The patch set couldn't have been tht big between rc0 and rc1 I have to wonder why they are having so much trouble hunting it down.

[milomak]

Grab kernel-2.6.36-0.0.rc0.git1.fc15 from koji

http://koji.fedoraproject.org/koji/buildinfo?buildID=188293

all of the newer versions do not boot for me

That's the trick. Thanks.

[andrewthomas]

kernel-2.6.36-0.6.rc1.git3.fc15 works here

[milomak]

if i don't want the koji kernel removed, will adding the below to /etv/yum.conf keep it?

keep=kernel-2.6.36-0.0.rc0.git1.fc15.x86_64

[andrewthomas]

if i don't want the koji kernel removed, will adding the below to /etv/yum.conf keep it?

keep=kernel-2.6.36-0.0.rc0.git1.fc15.x86_64

or
yum erase kernel-2.6.36-0.1.rc1.git0.fc15.x86_64for all the specific kernels that don't work

[jvillain]

I did a
an upgrade with kernel-2.6.36-0.6.rc1.git3.fc15

it wiped my grub.conf and all my previous kernels and now it can't find my raid partitions. Looks like I am going to be busy this afternoon.

[kurtdriver]

I did a
an upgrade with kernel-2.6.36-0.6.rc1.git3.fc15

it wiped my grub.conf and all my previous kernels and now it can't find my raid partitions. Looks like I am going to be busy this afternoon.

I guess it's nice to know that I'm not the only one.:)
I think I need a little help, frankly I'm confused about where to point grub, I have a partition for /boot, do I point it to /boot (the partition) or to the drive it's on? Actually my grub.conf is messed up more than that. Here's the two I've been playing with

#title Fedora 2.6.36-0.6
# root (hd0,1)
# kernel /boot/vmlinuz-2.6.36-0.6.rc1.git3.fc15.x86_64 ro root=UUID=300e0c8b-5ff5-4fca-b90d-b0c3ab4ee27c rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb
# initrd /boot/initramfs-2.6.36-0.6.rc1.git3.fc15.x86_64.img

title Fedora 2.6.36-0.6
root (hd0,0)
kernel /vmlinuz-.6.36-0.6.rc1.git3.fc15.x86_64 ro root=UUID=300e0c8b-5ff5-4fca-b90d-b0c3ab4ee27c rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet quiet
initrd /initramfs 2.6.36-0.6.rc1.git3.fc15.x86_64.img



Basically, I've tried each possibility, and neither works, neither did using the oldstyle /dev/sdax

Boy do I wish I'd backed it up first. A big thanks to anyone can help me figure this thing out (or tries). Kurt

[jvillain]

Boot to grub and hit the space bar to stop it from booting.

Hit the 'c' key to get to the command line

type in

root (hd0,0)

Then type in

kernel /

then hit the tab key. If you have your kernels and initramfs's listed after hitting the tab key then your root line was correct. If not then try

root (hd0,1)

etc, etc till you find your kernels and initramfs.

You can then pick a kernel with

kernel /<somekernename> ro root=UUID=300e0c8b-5ff5-4fca-b90d-b0c3ab4ee27c

where <somekernelname> is one of your existing kernels

then

initrd /

hit the tab key and select the initramfs that matches the kernel you chose

Then hit the 'b' key to boot.


after that boot. If it doesn't boot go back and choose a different kernel and matching ramfs if you have one.


If that doesn't do it we need more 'fo

[kurtdriver]

Thanks, but it doesn't even find grub. Just a little white cursor flashing in the upper left hand corner.


Edit: The livcd's "boot from local drive" option just reboots the computer.

[andrewthomas]

Boot to a live-CD and go to http://bootinfoscript.sourceforge.net/ follow the instructions and paste the content of RESULTS.txt into your next post

[kurtdriver]

Boot to a live-CD and go to http://bootinfoscript.sourceforge.net/ follow the instructions and paste the content of RESULTS.txt into your next post

Thanks, but it's a little late, I'm afraid. I ended up putting the F13 DVD in and attempting to "Install or update and existing system". Choosing "Update existing system", updated it all right, with LVMs in place of my partitions. This morning has been spent starting over, testing my setup script, and finding bugs in the latter. I'm going to file a bug with Anaconda, twice I chose update existing systems, while it turns out that only the custom layout option allows that (if it does). I did stop a bunch of fonts from going in.!!!!!!:D
I'm looking at that script and learning from it. Thanks, anyway. Kurt

[andrewthomas]

I'm looking at that script and learning from it. Thanks, anyway. Kurt

That boot info script is great for any grub problems

[kurtdriver]

Actually, I was looking at the way they set up the -v option towards the beginning, as I've been wondering how to do options in a shell script. There are other goodies in there for a scripting noob.:)
Insanity prevails, rawhide is going back onto my laptop at this moment.