kernel panic

lumiwa · 2006-12-01 19:21:34

Few minutes ago I update my system - kernel 2.6.9 from testing and I cannot boot anymore"

ERROR: Failed to parse block device name for 'dev/hda3' unknown
ERROR: root fs cannot be detected. Try using rootfstype=kernel parameter
::initframps completed - control passing to kinit
IF-config: no devices to configure
kinit:: Unable to mount root fs on device dev (0,0)
kinit: init not found
Kernel panic not syncig: Attempted to kill init!

Thanks

phrakture · 2006-12-01 19:24:42

Well, it seems there was no upgrade message in the kernel package... there was a news article, but that is not sufficient... your fix is here, though:
http://archlinux.org/news/272/

lumiwa · 2006-12-01 20:19:57

phrakture wrote:

Well, it seems there was no upgrade message in the kernel package... there was a news article, but that is not sufficient... your fix is here, though:
http://archlinux.org/news/272/

Thank you very much, phrakture .

----
http://www.flickr.com/photos/starikarp

neodreams · 2006-12-01 21:06:59

Work good here.

But my camera and mp3 player was mounted on sda ...and now hda become sda, how do I access them now, where they are ?

lumiwa · 2006-12-01 21:30:23

neodreams wrote:

Work good here.
But my camera and mp3 player was mounted on sda ...and now hda become sda, how do I access them now, where they are ?

My usb memory reader was sde now is sdf.

I don't know why I have so many messages in the /var/log/everything.log:
Dec 1 15:34:35 athena sr0: CDROM not ready. Make sure there is a disc in the d
rive.
Dec 1 15:34:36 athena sr0: CDROM not ready. Make sure there is a disc in the d
rive.
Dec 1 15:34:37 athena sr0: CDROM not ready. Make sure there is a disc in the d....
....

Thanks.

neodreams · 2006-12-01 21:50:51

Thanks for the tip lumiwa, work great !

xerverius · 2006-12-01 23:07:29

This warning can also be caused by multiple harddisk drivers in your initrd file. If you have for example the ide, sata, pata and scsi hooks enabled in mkinitcpio.conf, it's better to remove the ide, pata and scsi hook when your /boot and /lib directories are on a sata disk.
You can then load the other drivers (if needed) with the modules line in rc.conf.

:!: Before you're going to try this, make sure the fallback initrd is added to the lilo/grub config.

lumiwa · 2006-12-02 00:14:32

xerverius wrote:

This warning can also be caused by multiple harddisk drivers in your initrd file. If you have for example the ide, sata, pata and scsi hooks enabled in mkinitcpio.conf, it's better to remove the ide, pata and scsi hook when your /boot and /lib directories are on a sata disk.
You can then load the other drivers (if needed) with the modules line in rc.conf.
:!: Before you're going to try this, make sure the fallback initrd is added to the lilo/grub config.

I use KDE and KsCD. If I start a program KsCD I get immediately warnings. When I turn KsCD off then is okay, I don't I get messages. On kernel 2.6.18 was okay.
In mkinitcpio.conf I have:
HOOKS="base udev autodetect pata scsi sata filesystems"

mcrae · 2006-12-02 00:49:35

This freaked me out at first. I didn't notice it came from testing :oops:
changed hooks, regenerated image and it's working well on my laptop.

Thanks,
McRae

baze · 2006-12-02 00:59:58

btw, what are those known issues mentioned with the testing nvidia driver? it works fine here..

tpowa · 2006-12-02 08:28:03

that your hda becomes sda shouldn'T happen, if you haven't enabled pata in HOOKS=
please tell me what your exact setup is, what controllers you have inside and what modules are used in your initrd?
thanks
greetings
tpowa

tpowa · 2006-12-02 08:58:46

also you guys with problems please post your HOOKS= that we know what you have enabled for initcpio

tpowa · 2006-12-02 09:55:01

Hi
i'm just wating for some feedback but i think we have found a troublemaker,
the ata_piix module in .19 series

major problem:
old ata_piix module from .18 series still did the hdx scheme for ide devices

new ata_piix module from .19 series:
ata_piix takes care of both ide and sata devices.
It seems it gives the names like the bios order is.
example:
one guy had 2 ide disks on controller and 1 sata disk.
He had only sata in HOOKS= the .19 kernel now shifts the 2 ide disks before
the sata disk, means hda -> sda, hdb -> sdb, his old sda -> sdc

Conclusion:

Affected ppl with ata_piix controller:
all that changed their mkinitcpio.conf to not use ide hook anymore.
all that use ata_piix in MODULES= in mkinitcpio.conf before piix could be
loaded.

3 Solutions:
1) Keep using the default mkinitcpio.conf
2) add MODULES="piix ata_piix" to mkinitcpio.conf
3) switch GRUB/LILO configs and fstab to new sdx layout.

Not affected ppl with ata_piix controller:
If a user havent modified mkinitcpio.conf yet it should everything work as it did before.

could you guys with problems confirm this?

brain0 · 2006-12-02 10:08:18

Again, to clarify what tpowa wrote:

If you don't include "pata" in your mkinitcpio.conf, nothing will change. Everything will still be hda. One exception (the only exception) is if your ide controller is a piix controller. As ata_piix is an sata module and an ide module, it will be included in the initramfs even with pata disabled, when sata is enabled. Now ata_piix is loaded automatically instead of piix and your hda becomes sda.

So if you keep getting kernel panics, boot with "disablemodules=ata_piix". That will give you your hda back. Then rebuild your initramfs image with the sata hook removed. The "piix" module will be used again instead of ata_piix and everything will be the way you are used to.

IsSuE · 2006-12-02 12:00:25

I still dont get it.
I got an ata_piix and an sata_sil inside my rig. My current HOOKS line looks as following: HOOKS="base udev autodetect ide scsi sata filesystems"

when i try to boot, I get the error message posted in the first post here. So what to change?

noriko · 2006-12-02 12:19:16

works perfectly ok here ... and almost feels slightly more responsive than the k26.18 or even .18ck but that's prolly just my imagination x)
my HOOKS="base udev autodetect pata filesystems keymap usbinput"

btw, the note in the news update suggested there was a problem with the nvidia drivers in testing... with a link to another distro of the drivers..
that distro (1.8*) failed to load for me with errors,
API mismatch ; with driver version and module both bearing different version numbers.. can't remember which way round they were, however they have teh version numbers on the nvidia and nvidia-beta pkgs.
nvidia from testing works for me [ XFX 5200 ]

IsSuE · 2006-12-02 12:29:07

okay, now i figured it! i removed sata and it works. But now i cant start my Xserver, due to missing modules. I use 8776 nvidia modules. But actually they wont install into the 2.6.19-ARCH dir.

tpowa · 2006-12-02 12:52:19

noriko the problem is that your nvidia-utils package is also from testing, those packages must have the same version then it works

noriko · 2006-12-02 16:08:33

aha x) wotta noob i am lol ... will try it later see if they both work x)

tpowa · 2006-12-02 16:11:08

nvidia 1.9xxx driver have issues with gf 3 and gf 4 cards, also heard of other issues, i hope they release a new driver soon, else 1.8xx will stay in extra.

solstice · 2006-12-03 18:58:09

which issues ?

i use nvidia-beta 1.0.9626-1 and a geforce 4 MX 440 and i did not see any pb yet.

by the way, why there is no package for the 9629 (notice the 9 at the end instead of the 6 !) which are not beta anymore. the beta are now 9742

http://www.nvidia.com/object/linux_disp … -9629.html

rztka · 2006-12-04 16:30:30

brain0 wrote:

So if you keep getting kernel panics, boot with "disablemodules=ata_piix". That will give you your hda back....

i think this dosn't help in my case :cry: actually i'm not sure i'm doing it right (i'm still more or less a linux newbie):

so i just added the disablemodules=ata_piix to the kernel command line, but i still get kernel panic... i also tried to change root=/dev/hda3 to /dev/sda3 but the result is still the same

i'm also not sure what's in my HOOKS="" i'll try livecd to find out

can anyone please help me? i'll try to post here any additional information you need.. just tell me where to find them.

BIG THANKS in advance!

edit:
well these are my HOOKS="base udev autodetect ide scsi sata resume filesystems"

so you said sata should not be there but how will i rebuild the image if i cannot boot?

lumiwa · 2006-12-04 23:25:38

tpowa wrote:

also you guys with problems please post your HOOKS= that we know what you have enabled for initcpio

I wrote my "problem" before and I have it still.

First, I don't have a problem with boot and everything works as before very good.
If I hand KsCD in the Panel I have in /var/log/everything.log:
r0: CDROM not ready. Make sure there is a disc in the drive.
CD plays okay as before, I didn't try to burn yet.
On previous kerels I didn't have this.

In mkinitcpio.conf I have:
modules=""
HOOKS="base udev autodetect pata scsi sata filesystems"

In the rc.conf in modules section I have just for network card and sound card.

And the third one is which I describe befor and I had also under kernel 2.6.18, this is in the /var/log/errors.log:
intel_rng: FWH not detected

Thank you.

BTW: Arch is better than when I started to use it.

tpowa · 2006-12-05 06:07:02

i don' t think you have a bug it's just a kernel warning audio cds cannot be mounted so probably the sr_mod module tries to access the cd when you play it and the kernel gives you that warning

djclue917 · 2006-12-05 16:47:12

lumiwa wrote:

I don't know why I have so many messages in the /var/log/everything.log:
Dec 1 15:34:35 athena sr0: CDROM not ready. Make sure there is a disc in the d
rive.
Dec 1 15:34:36 athena sr0: CDROM not ready. Make sure there is a disc in the d
rive.
Dec 1 15:34:37 athena sr0: CDROM not ready. Make sure there is a disc in the d....
...
CD plays okay as before, I didn't try to burn yet.
On previous kerels I didn't have this.

Have you added 'sg' to MODULES=() in /etc/rc.conf? Basing from the device name, yung CDROM is now under the SCSI subsystem. Load the sg kernel module to create the device nodes /dev/sg?.

Arch Linux

#1 2006-12-01 19:21:34

kernel panic

#2 2006-12-01 19:24:42

Re: kernel panic

#3 2006-12-01 20:19:57

Re: kernel panic

#4 2006-12-01 21:06:59

Re: kernel panic

#5 2006-12-01 21:30:23

Re: kernel panic

#6 2006-12-01 21:50:51

Re: kernel panic

#7 2006-12-01 23:07:29

Re: kernel panic

#8 2006-12-02 00:14:32

Re: kernel panic

#9 2006-12-02 00:49:35

Re: kernel panic

#10 2006-12-02 00:59:58

Re: kernel panic

#11 2006-12-02 08:28:03

Re: kernel panic

#12 2006-12-02 08:58:46

Re: kernel panic

#13 2006-12-02 09:55:01

Re: kernel panic

#14 2006-12-02 10:08:18

Re: kernel panic

#15 2006-12-02 12:00:25

Re: kernel panic

#16 2006-12-02 12:19:16

Re: kernel panic

#17 2006-12-02 12:29:07

Re: kernel panic

#18 2006-12-02 12:52:19

Re: kernel panic

#19 2006-12-02 16:08:33

Re: kernel panic

#20 2006-12-02 16:11:08

Re: kernel panic

#21 2006-12-03 18:58:09

Re: kernel panic

#22 2006-12-04 16:30:30

Re: kernel panic

#23 2006-12-04 23:25:38

Re: kernel panic

#24 2006-12-05 06:07:02

Re: kernel panic

#25 2006-12-05 16:47:12

Re: kernel panic

Board footer