You are not logged in.
Pages: 1
I just upgraded to kernel 2.6.18 and Udev 100, and my computer now fails to boot into Arch properly.
I was already using mkinitcpio with 2.6.17, so I left my grub config unchanged.
When I try to boot to kernel26.img, I receive a kernel panic and complains about being unable to mount the root partition. I will gladly post more details if you tell me what to post and how to get it (I'd rather not retype the entire kernel panic screen by hand).
I am still able to boot to kernel26-fallback with no trouble. Everything seems to work exactly as it should,
I don't know what the differences betweek kernel26 and kernel26-fallback are, so if someone could at least explain that, I could do some more troubleshooting on my own.
Here is the significant portion of my menu.lst:
# (0) Arch Linux
title Arch Linux (kernel26)
root (hd0,0)
kernel /vmlinuz26 root=/dev/hda5 ro vga=773
initrd /kernel26.img
title Arch Linux (kernel26-fallback)
root (hd0,0)
kernel /vmlinuz26 root=/dev/hda5 ro vga=773
initrd /kernel26-fallback.imgAny ideas?
EDIT: Also, I'm not sure why I have 'ro' in there. I don't remember if I put it there myself, or if I copied it from somewhere. What's it do?
EDIT2: I also just attempted to sync the spca5xx driver from community, and it placed spca5xx.ko in /lib/modules/2.6.17-ARCH instead of 2.6.18. Could this be a related problem?
Offline
kernel26 is the image generated when you run mkinitcpio, it uses the configuration in /etc/mkinitcpio.conf to only build the proper modules.
kernel26-fallback is the full image with all possible modules on it.
The idea is to configure mkinitcpio.conf and only enable those modules that you need, and if some part of this process went wrong, you can use kernel26-fallback image to boot on your system.
Please take a look at [http://wiki.archlinux.org/index.php/Mkinitcpio] to see how configure it properly.
The "ro" in your menu.lst says to kernel mount the root partition "read only", wich is the default boot configuration. You should not change that.
I hope this can help.
PS: sorry about my bad english.
Offline
I have remedied the problem by adding "ext3" to the MODULES section of mkinitcpio.conf.
The exact lines of interest were this:
::Running Hook [filesystems]
::Loading root filesystem module...-e
Attempting to creat root device /dev/hda5
ERROR: Failed to parse block device name for '/dev/hda5'
unknown
Error: root fs cannot be detected. Try using the rootfstype= kernel parameterNow it runs like:
::Running Hook [filesystems]
::Loading root filesystem module... ext3So, my system is up and running agin, but I wonder if there should be concern that my root partition wasn't autodetected properly?
Offline
hmm you use hda5, could it be that you have 2 harddisk controllers?
Offline
I had the _exact_ same problem, and it turned out that the ide hook was missing from my /etc/mkinitcpio.conf. I'm sure I just deleted it by accident when editing it, but it is something to look for.
Offline
Here's the hook section from mkinitcpio.conf:
HOOKS="base udev autodetect ide sata filesystems"My motherboard is an MSI K8NGM2-FID. It supports four sata drives, and has two ide channels. On the first channel, I have two hard drives (hda, hdb), and on the second, I have a DVD-RW (hdc). I have no sata drives.
hda5 was chosen from me by the arch 0.7.2 installer. Here's what cfdisk looks shows:
cfdisk 2.12r
Disk Drive: /dev/hda
Size: 40020664320 bytes, 40.0 GB
Heads: 16 Sectors per Track: 63 Cylinders: 77545
Name Flags Part Type FS Type [Label] Size (MB)
------------------------------------------------------------------------------
hda1 Boot Primary Linux ext2 64.00
hda2 Primary Linux swap / Solaris 1099.81
hda5 Logical Linux ext3 9999.88
Pri/Log Free Space 28857.00I don't see anything wrong with it, except possibly that I would expect hda5 to be hda3.
Do you guys see anything that should be changed?
Offline
Pages: 1