PDA

View Full Version : Kernel Panic



Wagners
11th April 2007, 08:47 AM
Hi,

I have successfully installed ferora 6 and am having trouble getting my 3d acceleration working. I have followed the yum method to get all the drivers etc

http://news.softpedia.com/news/How-to-Install-Video-Drivers-on-Fedora-Core-6-38740.shtml

I then get a kernel panic when I reboot.

What now. Can I fix this?? :confused:

Thanks,
Simon

kurzer
11th April 2007, 09:01 AM
1st question: did you install the Nvidia or the ATI driver? I assume you installed the right one for your hardware.
2nd question: for the ATI driver your tutorial says to add "iommu=off" to the line in /etc/grub.conf. the kernel version in your grub.conf must match the kernel version you've installed.

Wagners
11th April 2007, 09:08 AM
Thanks for the reply. I installed the Nvidia drivers

when I execute "yum install kmod-nvidia" yum downloads and sets up a new kernel in grub for me. I then try to boot this kernel and I get a kernel panic.

Hlingler
11th April 2007, 09:15 AM
The latest kernel (see my signature) caused a kernel-panic for me, too, but I saw the line "try booting with apic=debug", so I did and that fixed the problem. Reboot, and when grub comes up with the boot choices screen, enter the appropriate keystroke so that you can edit the boot line (p=>password, c=>command line, a=>alter boot line, etc.); add apic=debug to the end of the line, then continue by pressing enter.

Wagners
12th April 2007, 08:07 AM
enter the appropriate keystroke so that you can edit the boot line (p=>password, c=>command line, a=>alter boot line, etc.); add apic=debug .

I tried entering that in my grub.conf and I still get a kernel panic. Here is my grub.comf

title Fedora Core (2.6.20-1.2933.fc6)
root (hd0,0)
kernel /vmlinuz-2.6.20-1.2933.fc6 ro apic=debug root=/dev/VolGroup00/Lo$ quiet
initrd /initrd-2.6.20-1.2933.fc6.img

Any suggestions How I can get my kernel to boot?? Thx

Hlingler
12th April 2007, 04:45 PM
Yes: you MUST enter the command at the END of the line. You can alter/append the commands there now for one-time changes, or to permanently change the arguments, edit grub.conf . Here's my grub.conf (irrelevant lines removed):


default=0
timeout=8
splashimage=(hd0,4)/grub/splash.xpm.gz
#hiddenmenu
title Fedora Core (2.6.20-1.2933.fc6)
root (hd0,4)
kernel /vmlinuz-2.6.20-1.2933.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb selinux=off agp=off apic=debug
initrd /initrd-2.6.20-1.2933.fc6.img
title Fedora Core (2.6.20-1.2925.fc6)
root (hd0,4)
kernel /vmlinuz-2.6.20-1.2925.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb selinux=off agp=off
initrd /initrd-2.6.20-1.2925.fc6.img
title initng boot
root (hd0,4)
kernel /vmlinuz-2.6.19-1.2911.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb selinux=off agp=off init=/sbin/initng
initrd /initrd-2.6.19-1.2911.fc6.img
title Fedora Core (2.6.19-1.2911.fc6)
root (hd0,4)
kernel /vmlinuz-2.6.19-1.2911.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb selinux=off agp=off
initrd /initrd-2.6.19-1.2911.fc6.img
title Memtest86+ (1.65)
root (hd0,4)
kernel /memtest86+-1.65 ro root=/dev/VolGroup00/LogVol00 rhgb
title Windows XP Media Center Edition
rootnoverify (hd0,0)
chainloader +1Notice that the first entry (my default) has "apic=degug" at the end of the kernel argument line.

lmo
12th April 2007, 06:52 PM
I tried entering that in my grub.conf and I still get a kernel panic. Here is my grub.comf

title Fedora Core (2.6.20-1.2933.fc6)
root (hd0,0)
kernel /vmlinuz-2.6.20-1.2933.fc6 ro apic=debug root=/dev/VolGroup00/Lo$ quiet
initrd /initrd-2.6.20-1.2933.fc6.img

Any suggestions How I can get my kernel to boot?? ThxEither you mistyped root=/dev/VolGroup00/Lo$ in your post, or that entry is probably corrupted.

nybigjet
16th April 2007, 03:06 AM
I'm also getting a kernel panic from 2944.fc6, which yum installed yesterday on an unusually large (1.2 gig) update; the first update after an fc5 --> fc6 upgrade. The good news is I can boot into 2933.fc6 and everything works remarkably well. I tried the grub "a --> apic=debug" Boot Line entry, but it had no effect, still got a kernel panic. Just rebooted into 2933.fc6 and the system went right up. Strange problem, I'll watch this tread. If anyone solves, please post.

regards --nybigjet

Wagners
19th April 2007, 11:20 AM
It is strange that the kernel on the cd works fine on both fc6 & fc7 test 3 but not when you update a kernel using yum. I have reformatted my machine to a dual boot now as I cant get 3d acceleration happening. Back to windoze. Sigh. :( My kernel crashes at the VolGroup00/LogVol00 part of the boot.

Does anyone know where the kernel logs are so I can post my kernel panic.

Hlingler
19th April 2007, 01:59 PM
You should also update the kmod-nvidia driver after updating a kernel: "yum update kmod-nvidia". You should have more than one version of kmod-nvidia on your system, one for each kernel. It is highly recommended that you get the nvidia drivers from livna.org - the files supplied by nvidia itself will replace critical redhat system files, and this may cause you no end of grief later on. The generic nv driver supplied with FC does not support direct rendering, and other repository's drivers simply don't work as good as livna's. It is also possible that you got a corrupt kernel file during the download - perhaps try un-installing then re-installing? You have to install the kernel-debug package which matches a kernel to get debug info. I believe the log file is either /var/log/dmesg or /var/log/messages - there are a number of other logs available in that folder. I am assuming that you edited your grub.conf as posted above? Post it here if you're not sure it's 100% correct. Hang in there, I am sure this can be solved. If you can get 3D acceleration working on any of the recent kernels, it's not necessary to have the very latest kernel.

kernel-devel should read kernel-debug

Wagners
19th April 2007, 03:27 PM
Is there anyway I can install the nvdia drivers for an old kernel using yum install kmod-nvidia??

Hlingler
19th April 2007, 07:19 PM
Yes, so: First, find out what kernel versions are installed:
[root@presario ~]# rpm -q kernel
kernel-2.6.20-1.2933.fc6
kernel-2.6.20-1.2944.fc6
kernel-2.6.20-1.2925.fc6
[root@presario ~]#Note that I have three kernels installed, the default is two (you're not the only one who's been bitten). In fact, make double-sure that you have the i686 kernels installed, not the i586 kernels, which fc6 is famous for (mis)installing:
[root@presario ~]#[root@presario ~]# rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n"|grep kernel|sort
kernel-2.6.20-1.2925.fc6.i686
kernel-2.6.20-1.2933.fc6.i686
kernel-2.6.20-1.2944.fc6.i686
kernel-devel-2.6.20-1.2925.fc6.i686
kernel-devel-2.6.20-1.2933.fc6.i686
kernel-devel-2.6.20-1.2944.fc6.i686
kernel-doc-2.6.20-1.2944.fc6.noarch
kernel-headers-2.6.20-1.2944.fc6.i386
yum-kernel-module-1.0.3-1.fc6.noarch
[root@presario ~]#There should be no "i586" in the above output (unless you're running a really old CPU). See
http://forum.fedoraforum.org/showthread.php?t=139751for more info on this. Then see what kmod-nvidia packages you have installed:
[root@presario ~]# rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n"|grep kmod-nvidia|sort
kmod-nvidia-1.0.9755-2.2.6.20_1.2925.fc6.i686
kmod-nvidia-1.0.9755-2.2.6.20_1.2933.fc6.i686
kmod-nvidia-1.0.9755-2.2.6.20_1.2944.fc6.i686
[root@presario ~]#If all versions of kmod-nvidia matching all of your kernels are installed (as in mine above), you're good to go. Note that the actual driver package is xorg-x11-drv-nvidia, which should already be installed (only one version) automatically because the kmod-nvidia packages (all recent versions) depend on it:
[root@presario ~]# rpm -q xorg-x11-drv-nvidia
xorg-x11-drv-nvidia-1.0.9755-3.lvn6
[root@presario ~]#If not, then you must fetch the missing kmod-nvidia package for the kernel in question:
[root@presario ~]# wget http://rpm.livna.org/fedora/6/i386/kmod-nvidia-1.0.9755-2.2.6.20_1.XXXX.fc6.i686.rpmwhere XXXX is the number of the kernel in question. You may have to massage some of the other numbers to match your installation, but I will assume you're smart enough to figure out the number-naming scheme. You'll have to force the install of a kmod-nvidia package that's older than your latest kernel, for example:
[root@presario ~]# rpm -ivh --force kmod-nvidia-1.0.9755-2.2.6.20_1.2925.fc6.i686.rpm
Preparing... ########################################### [100%]
1:kmod-nvidia ########################################### [100%]
[root@presario ~]#Personally, I prefer GUI apps, like kyum, yumex, or my favorite, smart-package-manager, for playing with packages. I would use smart-package-manager exclusively, but it does not log it's actions. Also, you must never run yum/kyum/yumex and smart-package at the same time, including auto and cron jobs, or you'll wreck your database.

Hlingler
19th April 2007, 08:01 PM
Um....I just noticed that we're in the x86_64-bit forum :eek: , so make sure you substitute x86_64 for i386/i686 where applicable, if you are running the x86_64 kernel or you installed that flavor of FC6. Otherwise, the procedure should be the same.