FS#3402 - KERNEL 2.6.14 INITRD

Attached to Project: Arch Linux
Opened by Tobias Powalowski (tpowa) - Sunday, 30 October 2005, 08:30 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity Critical
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi feel free to post your problems/suggestions here,
greetings
tpowa
This task depends upon

Closed by  Judd Vinet (judd)
Thursday, 15 December 2005, 22:21 GMT
Reason for closing:  Fixed
Comment by Claudio Riva (Firetux) - Sunday, 30 October 2005, 12:16 GMT
I get the error in the image... I don't understand what I have to do
I use grub and in the menu.lst I wrote:

# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd0,0)
kernel /vmlinuz26 root=/dev/hda6 ro devfs=nomount vga=773 apm=power-off
initrd /initrd26.img

and these are my partitions (get from /etc/fstab):
/dev/discs/disc0/part5 swap swap defaults 0 0
/dev/discs/disc0/part1 /boot ext3 defaults 0 1
/dev/discs/disc0/part6 / ext3 defaults 0 1
/dev/discs/disc0/part7 /home ext3 defaults 0 1

I don't change /etc/mkinitrd.conf, I only run "mkinitrd auto"
   00001.jpg (1.97 MiB)
Comment by Dale Blount (dale) - Sunday, 30 October 2005, 13:41 GMT
tpowa,

I think it needs to replace=('kernel26-scsi')

Comment by Dale Blount (dale) - Sunday, 30 October 2005, 13:51 GMT
Other than my last comment, the new kernel works fine on my SATA system.
Comment by Jaroslaw Swierczynski (swiergot) - Sunday, 30 October 2005, 14:17 GMT
Claudio, I think you need to change device paths in your /etc/fstab to udev-like, eg. /dev/discs/disc0/part5 -> /dev/hda5.
Comment by Tobias Powalowski (tpowa) - Sunday, 30 October 2005, 14:21 GMT
Claudio try adding (hd?,?)/boot/initrd26.img
Comment by Leonard Ritter (paniq) - Sunday, 30 October 2005, 16:31 GMT
i was one of the lucky guys who read the news only when something goes wrong - thank you for the smooth transition (not)!

im now stuck with a 0.7 boot cd and a chrooted environment, where mkinitrd auto tells me

All of your loopback devices are in use!

yes, of course dammit. i have to mount my root dir somewhere?

$%&
Comment by Leonard Ritter (paniq) - Sunday, 30 October 2005, 16:41 GMT
allright, solved this by installing the old kernel and starting again from there...
Comment by Jason Carr (jason2) - Sunday, 30 October 2005, 16:51 GMT
Are you going to be enabling the hostap drivers? I'd have to compile my own kernel again, which would blow.

CONFIG_HOSTAP=y|m

You know you want to.
Comment by Leonard Ritter (paniq) - Sunday, 30 October 2005, 17:04 GMT
god dammit! it uses my fstab which used to work although i never changed the devfs entries to something udev compatible - i have to do the whole thing all over again!!!
Comment by Leonard Ritter (paniq) - Sunday, 30 October 2005, 17:30 GMT
allright... so people dont forget to change your fstab as well... NO DEVFS ENTRIES! (/dev/discs/disc0/part1 => /dev/hda1 and so on)
Comment by Claudio Riva (Firetux) - Sunday, 30 October 2005, 17:56 GMT
yes, you have to change fstab as explained above! (/dev/discs/disc0/part1 => /dev/hda1)
Comment by Eugenia Loli-Queru (Eugenia) - Sunday, 30 October 2005, 21:46 GMT
Please make sure that the new kernel package files as a dependency the new mkinitrd package. People already don't know what they have to pull that package manually (check that person on the forums for example who got in the trap).
Comment by Charles Mauch (xterminus) - Monday, 31 October 2005, 03:41 GMT
You might want to include some documentation indicating that you must fill in the HOSTCONTROLLER value in /etc/mkinitrd.conf. I couldn't get my system past the busybox failure prompt until i added.

HOSTCONTROLLER_IDE="ide-core ide-generic ide-disk"

Comment by kronin (kronin) - Tuesday, 01 November 2005, 22:27 GMT
i have a lot of modules loaded:

$ lsmod |wc -l
118

this modules are loaded auto-magically!
maybe the initrd load the modules.

how i can fix this?

Comment by Jaroslaw Swierczynski (swiergot) - Wednesday, 02 November 2005, 08:11 GMT Comment by Tobias Powalowski (tpowa) - Wednesday, 02 November 2005, 15:36 GMT
ok updated kernel+mkinitrd, new features can be found at blog or ML.
greetings
tpowa
Comment by Indan Zupancic (i3839) - Thursday, 01 December 2005, 23:53 GMT
You really should use initramfs instead of initrd. Either immediately before the initrd is in base, or some months when everything is more stable.

Very informative read:

linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt

Note that this file is only very recently added (7 November or so). I've attached it.
Comment by Judd Vinet (judd) - Thursday, 15 December 2005, 22:21 GMT
I'm going to close this bug now.

If there are further initrd issues, we can re-open it.

The plan is to stick with the initrd for 0.7.1 -- we will examine initramfs sometime after Noodle's release.

Loading...