[Resolved] [Waldorf] Kernel Panic, HELP :(

razzledazzle · 2013-10-29 16:55:39

Hello guys,
I've just recently installed #! on my netbook and it had been running really great, fastest Linux experience ever, really enjoying it.

Although, I kinda think I've sinned. I added local Ubuntu repositories to the sources list and update, I did it for the fact that the downloads from that repository are super fast (10 times faster) while the regular repository downloads are painfully slow.

I already configured many things on this installation, including the fglrx installation successfully, I've even rebooted many times. Things had been going great.

But later I decided to update the whole thing by "sudo apt-get upgrade". It went fine with some exceptions, there was a problem with udev and I modified a script to get it going. It was successful as well. When I rebooted to test, I got these:

/init: line 327: can't create /dev/null : Read-only file system
/init: line 327: can't create /dev/null : Read-only file system
Something went badly wrong in the initramfs.
/init: line 329: can't create /dev/null : Read-only file system
Please file a bug on initramfs-tools
...Some lines relating to USB
...Some lines relating to USB
/init: line 329: can't open /dev/console : no such file
Kernel panic - not syncing : Attempted to kill init!
Pid: 1, comm: init Not tainted 3.2.0-4-686-pae #1 Debian 3.2.51-1
Call Trace:
? panic+0x4d/0x141
? do_exit+0x76/0x60c
? do_group_exit+0x5c/0x7f
? sys_exit_group+0x11/0x11
? sysenter_do_call+0x12/0x20

I've skipped some parts from what has been displayed, I hope someone can help me reverse this and pray what I've explained here is making any sense at all.

Last edited by razzledazzle (2013-10-30 08:11:52)

benginm · 2013-10-29 17:57:30

hi raz, this could be related to many factors .. a bad shutdown, missing Initramfs-tools , dead/unhealthy , undetected HDD, lack of
space in /root , /root encrypted partition , bad memory !

so for starter , please read about it . debug, and see if you're able to recover your kernel .

https://wiki.debian.org/InitramfsDebug

http://lugatgt.org/content/booting.init … tation.pdf

now, you can run recover the your kernel from the livecd in a chroot environment , please make a search on how to chroot properly , you'd probably need to create a mountpoint .. and mount /proc /sys /dev /boot , and finally rebuild the initrd: update-initramfs -u -k all , then you get out of chroot with ' exit ' .

Last edited by benginm (2013-10-29 18:15:19)

razzledazzle · 2013-10-30 02:00:16

Thank you so much for guiding me sary. Its my first time going barebones. It was only yesterday when I had joy having switched the xorg.conf file via the recovery mode and being able to boot in successfully! big_smile Well, that was when I was trying to configure fglrx, now this time its a kernel panic with no access to recovery. So yeah, I'll be attempting fix with your methods.

Just woke up, I hope I can get the system going today.

UPDATE:
So I tried using your method, I set up chroot along with busybox, however, update-initramfs didn't run, it said something like basename was not supplied. I exited chroot and went on to replace the current image with the LiveCD image, and it went fine.

I rebooted and the kernel panic was gone, even could get into recovery nicely. But when the login screen would show up, I can do nothing, can't even access virtual terminal, its as if the system froze. Rebooted, went into recovery and updated with
"update-initramfs -t -u -k all". It generated the image, I rebooted, now I get the same kind of kernel panic. Anything more I can do? I think the updates are conflicting or something.

UPDATE 2:
Is 3.11.0-12-generic supposed to be located in /lib/modules? It isn't there on my desktop.

Last edited by razzledazzle (2013-10-30 06:27:49)

benginm · 2013-10-30 07:22:11

Hi raz,i glad to see you still have the spirit to deal with all of this! I just woke up myself .. rolled up icedove only to see your e-mail response and while attaching screen i noticed my nick was highlighted but i couldn't tell who it was! then saw your last posts in the channel logs, the one about bash !

you'll need to open bash in chroot:

# chroot /mount/point /bin/bash

as for replacing the your current system vmlinuz with the livecd one, i don't believe they match! .. the intramfs filesystem most support and match your installed kernel module/version. The initrd image for each kernel is built at kernel installation time from the modules and applications on the machine.

so, to restore that .. in chroot , you list the contents of /lib/modules to get the correct kernel name-version:

ls /lib/modules

then

subsitute in the appropriate version for your kernel that is listed in /lib/modules, then you can simply build a missing initrd using:

update-initramfs -c -k <version>

# well, i hope it's just an updates conflict and not something else! at this stage .. i really think you should backup your data/ system config files.

Edit: remainder ;/

Last edited by benginm (2013-10-30 07:27:53)

razzledazzle · 2013-10-30 07:50:39

I tried updating with the current kernel version sary, I get the same kernel panic.
I think that upgrade replaced the files with incompatible versions. Should I go on with a fresh installation?

benginm · 2013-10-30 08:07:29

razzledazzle wrote:

I tried updating with the current kernel version sary, I get the same kernel panic.
I think that upgrade replaced the files with incompatible versions. Should I go on with a fresh installation?

probably , if you're all backed up! then go for it, only this time make sure you don't enable Ubu* repos with waldorf/debian ones! and to save you graphic troubles! use the open source driver ' radeon ' instead of the troublesome ' fglrx ' and see how things work, and yes the radeon module does support 3D/opengl , you just need to make sure to install mesa-utils which has glxinfo

https://wiki.debian.org/Mesa#Testingperformance

either driver you go with , make sure you do it the debian way:

https://wiki.debian.org/AtiHowTo

razzledazzle · 2013-10-30 08:11:08

Thank you for the support, learned a lot along the way. I'll bear in mind your suggestions. I think this thread is resolved.

CrunchBang Linux

SEARCH

#1 2013-10-29 16:55:39

[Resolved] [Waldorf] Kernel Panic, HELP :(

#2 2013-10-29 17:57:30

Re: [Resolved] [Waldorf] Kernel Panic, HELP :(

#3 2013-10-30 02:00:16

Re: [Resolved] [Waldorf] Kernel Panic, HELP :(

#4 2013-10-30 07:22:11

Re: [Resolved] [Waldorf] Kernel Panic, HELP :(

#5 2013-10-30 07:50:39

Re: [Resolved] [Waldorf] Kernel Panic, HELP :(

#6 2013-10-30 08:07:29

Re: [Resolved] [Waldorf] Kernel Panic, HELP :(

#7 2013-10-30 08:11:08

Re: [Resolved] [Waldorf] Kernel Panic, HELP :(

Board footer