You are not logged in.
Hi guys!
Some days ago I updated my Archlinux...
Pacman installs the new kernel, then reboot and... There's a wonderful Kernel Panic!
/initrd: 36: replace: not found
/initrd: 36: replace: not found
export: 36: bad variable name
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.30-ARCH #1
Call Trace:
[<c03d0b54>] ? panic+0x5b/0xff
[<c013f884>] ? do_exit+0x614/0x6f0
[<c13fa70>] ? complete_and_exit+0x0/0x30
[<c0103d54>] ? sys_call+0x7/0xb
So I tried to find a solution to the problem chrooting to my Arch partition from Ubuntu, and then I:
1) erased the Pacman cache
2) reinstalled klibc (I ignored some of its dependencies some days before (pacman -Syud))
3) reinstalled kernel26
4) gave the command mkinitcpio -p kernel26
These operations ended flawlessy but, when I rebooted my machine, there was the same Kernel Panic waiting for me, again...
Please help me!!!!!
Thank you for your support
Offline
Downgrade your kernel26 package.
"I'm Winston Wolfe. I solve problems."
~ Need moar games? [arch-games] ~ [aurcheck] AUR haz updates? ~
Offline
Mh...
I don't understand why is this kernel panic supposed to happen, is it because of a reported bug??? Should I report this???
Offline
hi!
when you reinstall kernel26, it will generate initram. so it is not necessary to run mkinitcpio as a separate command. plus, i am not sure that that is the proper mkinitcpio command in your case. the chrooted environment probably has other kernel than for what you want the initrd generated. than the syntax is different for mkinitcpio. you can check proper options for it on wiki, or watch it on screen while installing kernel26 in chroot. so in this case with the 4th step of yours you might generate an improper initrd overwriting the proper one.
Offline
Well, yesterday I succeded to access the system using the old kernel and its failsafe image (it could not find any module, no X at all etc...), and I tried to reinstall kernel26 and regenerate the image with mkinitcpio -p kernel26, but nothing! There's always the same kernel panic waiting for me!
Maybe the problem is in mkinitcpio, is it possible? What should I do?
Thank you for your support!
Offline