You are not logged in.
Pages: 1
After last night's pacman -Syu I get this kernel panic message when I boot my PC -> http://imageshack.us/photo/my-images/14 … 60024.jpg/
Any idea what caused it and how to fix it?
Thanks in advance.
Last edited by Aventinus (2011-08-22 11:39:35)
"Somewhere, something incredible is waiting to be known." - Carl Sagan
Offline
it looks like initrd is missing from grub or grub2.
I use grub2, so in /boot/grub/grub.cfg i would need this line; (the starred one)
menuentry 'Arch Linux, with Linux rt' --class archlinux --class gnu-linux --class gnu --class os {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 85c30fe7-09dc-40b3-8210-3e0b5ebf9e9f
echo 'Loading Linux rt ...'
linux /boot/vmlinuz-linux-rt root=UUID=85c30fe7-09dc-40b3-8210-3e0b5ebf9e9f ro quiet threadirqs force=hpet init=/sbin/e4rat-preload elevator=bfq
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-rt.img *****
in grub, i would expect to see this line;
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz-linux root=/dev/sda3 ro
initrd /initramfs-linux.img ****
I don't know what the deal is, but it would seem as of late, kernel updates / installations are creating initramfs - but they are not being added to grub/grub2. I recently installed linux-rt - and had to add initrd manually, after. Your error message also suggests that you are having the same problem.
adding initrd should fix the problem
EDIT: Obviously, you need to look at your own kernel's initrd for the proper file name
Last edited by triplesquarednine (2011-08-21 20:05:55)
Offline
just reading through threads, you're not the only one with this issue.
Although, this thread was closed/dustbin, as the OP didn't give any information about his problem, and rather than figuring it out he just re-installed Arch (ouch, for a problem that takes to seconds to fix);
https://bbs.archlinux.org/viewtopic.php?id=124953
he says
I do not remember the error messages ... something about init. Afterwards the system got a panic in early kernel user space, and so was not able to boot.
probably the same problem that both you and i encountered. I'm going to read through some more threads, and see if this problem is being addressed. This appears to be a bug, unless i am missing something here?
cheerz
Offline
That did the trick, thank you so much for your time! For now I put linux on the ignorepkg so I won't have similar problems when upgrading.
"Somewhere, something incredible is waiting to be known." - Carl Sagan
Offline
hey no problem
as soon as i saw that screenshot, i knew what was up.
glad i could help
Offline
Pages: 1