Kernel 2.6.18 and mkinitcpio coming soon

dtw · 2006-08-07 08:15:29

phrakture wrote:

This is an announcement for those of you still using mkinitrd to boot your machines.
For some time now there has been a notice upon kernel install that mkinitrd will be replaced by mkinitcpio once the 2.6.18 series is released. That time is quickly approaching. To anyone who has not at least tried mkinitcpio (/boot/kernel26.img) is advised to try it and report any issues on the bug tracker before this goes live.
Thank you

You've been more than warned - lets not have another udev/initrd fiasco!

fk · 2006-08-09 16:07:33

Hi

I have set up my Arch system with this How To

http://wiki.archlinux.org/index.php/Ins … her_distro

I go step by step, and after chroot I would like to generate my mkinitcpio.

I write piix and ext3 in the Modules Araay in /etc/mkinitcpio.conf
(piix is for my ICH controller).

After this I run mkinitcpio -g /boot/kernel26.img
But it's fail about that "modul piix is not found"

Ok I use mkinitrd and after the first reboot I try again and run
mkinitcpio -g /boot/kernel26.img.

The mkinitcpio was created withount problems.

Is this a bug , or do I something false?

Edit: typo

sebcactus · 2006-08-09 16:19:59

You have to edit /etc/mkinitcpio.conf, not /etc/mkinitrd.conf

fk · 2006-08-09 16:22:08

You have to edit /etc/mkinitcpio.conf, not /etc/mkinitrd.conf

Yes , this was a typo sry

baze · 2006-08-09 17:27:32

mkinitcpio 0.5.0 from testing gives me a "stdin: error 0"during the autodetection hook.

phrakture · 2006-08-09 17:55:46

baze wrote:

mkinitcpio 0.5.0 from testing gives me a "stdin: error 0"during the autodetection hook.

Hmmm, thanks for that. I changed the way filesystem autodetection works, so it may be screwed up. Can you post the verbose output (-v) for me?

baze · 2006-08-09 18:03:04

HOOKS="base udev autodetect sata filesystems"

mkinitcpio -v -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
adding dir /proc
adding dir /sys
adding dir /dev
adding node /dev/null
adding node /dev/zero
adding node /dev/console
adding dir /lib
adding file /lib/klibc-u5tK0EIDXMXcX6WWDRrnsKG-fVk.so
adding dir /bin
adding file /bin/cat
adding file /bin/chroot
adding file /bin/dd
adding file /bin/false
adding file /bin/fstype
adding file /bin/gunzip
adding file /bin/gzip
adding file /bin/insmod
adding file /bin/ipconfig
adding file /bin/kill
adding file /bin/kinit
adding file /bin/ln
adding file /bin/losetup
adding file /bin/mdassemble
adding file /bin/minips
adding file /bin/mkdir
adding file /bin/mkfifo
adding file /bin/mknod
adding file /bin/modinfo
adding file /bin/modprobe
adding file /bin/mount
adding file /bin/nfsmount
adding file /bin/nuke
adding file /bin/parseblock
adding file /bin/pivot_root
adding file /bin/replace
adding file /bin/run-init
adding file /bin/sh
adding file /bin/sleep
adding file /bin/split
adding file /bin/true
adding file /bin/umount
adding file /bin/uname
adding file /bin/zcat
adding file /init
adding file /config
:: Parsing hook [udev]
adding dir /sbin
adding file /sbin/udevd
adding file /sbin/udevtrigger
adding file /sbin/udevsettle
adding dir /etc
adding dir /etc/udev
adding dir /etc/udev/rules.d
adding file /etc/udev/rules.d/udev.rules
adding file /etc/start_udev
adding dir /lib/udev
adding file /lib/udev/firmware.sh
adding file /lib/udev/cdrom_id
adding file /etc/udev/udev.conf
adding dir /hooks
adding file /hooks/udev
:: Parsing hook [autodetect]
stdin: error 0
:: Parsing hook [sata]
adding dir /lib/modules
adding dir /lib/modules/2.6.17-ARCH
adding dir /lib/modules/2.6.17-ARCH/kernel
adding dir /lib/modules/2.6.17-ARCH/kernel/drivers
adding dir /lib/modules/2.6.17-ARCH/kernel/drivers/scsi
adding file /lib/modules/2.6.17-ARCH/kernel/drivers/scsi/libata.ko
adding file /lib/modules/2.6.17-ARCH/kernel/drivers/scsi/ata_piix.ko
adding file /lib/modules/2.6.17-ARCH/kernel/drivers/scsi/sd_mod.ko
adding dir /lib/modules/2.6.17-ARCH/kernel/drivers/cdrom
adding file /lib/modules/2.6.17-ARCH/kernel/drivers/cdrom/cdrom.ko
adding file /lib/modules/2.6.17-ARCH/kernel/drivers/scsi/sr_mod.ko
:: Parsing hook [filesystems]
adding dir /lib/modules/2.6.17-ARCH/kernel/fs
adding dir /lib/modules/2.6.17-ARCH/kernel/fs/jbd
adding file /lib/modules/2.6.17-ARCH/kernel/fs/jbd/jbd.ko
adding dir /lib/modules/2.6.17-ARCH/kernel/fs/ext3
adding file /lib/modules/2.6.17-ARCH/kernel/fs/ext3/ext3.ko
adding dir /lib/modules/2.6.17-ARCH/kernel/fs/reiserfs
adding file /lib/modules/2.6.17-ARCH/kernel/fs/reiserfs/reiserfs.ko
adding file /hooks/filesystems
:: Generating module dependancies
adding file /lib/modules/2.6.17-ARCH/modules.dep
adding file /lib/modules/2.6.17-ARCH/modules.alias
adding file /lib/modules/2.6.17-ARCH/modules.symbols
:: Generating image '/boot/kernel26.img'...SUCCESS

phrakture · 2006-08-09 19:34:16

Well, hey at least it appears to have worked. It's just an extraneous error message - does this image actually boot OK?

baze · 2006-08-09 19:57:32

phrakture wrote:

Well, hey at least it appears to have worked. It's just an extraneous error message - does this image actually boot OK?

yep. i only get this error message but the image boots just fine.

fk · 2006-08-09 20:47:39

fk wrote:

Hi
I have set up my Arch system with this How To
http://wiki.archlinux.org/index.php/Ins … her_distro
I go step by step, and after chroot I would like to generate my mkinitcpio.
I write piix and ext3 in the Modules Araay in /etc/mkinitcpio.conf
(piix is for my ICH controller).
After this I run mkinitcpio -g /boot/kernel26.img
But it's fail about that "modul piix is not found"
Ok I use mkinitrd and after the first reboot I try again and run
mkinitcpio -g /boot/kernel26.img.
The mkinitcpio was created withount problems.
Is this a bug , or do I something false?

Edit: typo

And what is with this?

phrakture · 2006-08-09 20:58:10

If you're running from a non-arch system, you need to first, chroot into your arch partitions, and second, pass the correct -k KERNEL VERSION.

This should all be covered in the wiki page here: http://wiki.archlinux.org/index.php/Mkinitcpio

fk · 2006-08-09 21:02:59

Hm ok, then it was my mistake sry

thorstenhirsch · 2006-08-11 14:17:05

How can I resuce-boot now?

When using /boot/initrd.img I could simply boot a crashed archlinux by providing some kernel parameters, like "arch initrd=/boot/initrd.img init=/bin/bash root=/dev/hde2", but when I do this with the new stuff ("arch initrd=/boot/kernel26.img init=/bin/bash root=/dev/hde2") the kernel panics because it can't sync the root fs. Seems like the module for my IDE controller is missing ...or XFS support - but wait, why is it not missing when I do a regular boot (...where kernel26.img is also used)?

phrakture · 2006-08-11 14:24:18

thorstenhirsch wrote:

How can I resuce-boot now?
When using /boot/initrd.img I could simply boot a crashed archlinux by providing some kernel parameters, like "arch initrd=/boot/initrd.img init=/bin/bash root=/dev/hde2", but when I do this with the new stuff ("arch initrd=/boot/kernel26.img init=/bin/bash root=/dev/hde2") the kernel panics because it can't sync the root fs. Seems like the module for my IDE controller is missing ...or XFS support - but wait, why is it not missing when I do a regular boot (...where kernel26.img is also used)?

initrd /boot/kernel26-fallback.img should always work (if it doesn't then you should report that case so I can fix it). As for rescue booting when the image itself fails... well, there's not much you can do. init=/bin/bash *should* work. If anything you can pass "break=y" to the kernel, and get dropped into dash (which sucks compared to bash).

tpowa · 2006-08-11 14:51:41

mkinitcpio 0.5.1 now fully supports blacklisting of modules with disablemodules=moduleA,moduleB for emergency cases.

we would need a cryptsetup tester with legacy crypt.
the rest seems to work now

phrakture · 2006-08-11 14:54:13

tpowa wrote:

we would need a cryptsetup tester with legacy crypt.
the rest seems to work now

last I checked, the hooks for lvm2 and cryptsetup still needed to be updated and put into testing - was this done already?

tpowa · 2006-08-11 14:58:14

i put in new cryptsetzup with brain0 changes, ok also checked in now lvm2 to testing

phrakture · 2006-08-11 15:37:38

tpowa wrote:

i put in new cryptsetzup with brain0 changes, ok also checked in now lvm2 to testing

I had changed the application which handles argument splitting... it should now be:

$(/bin/replace ${something} ':')

tpowa · 2006-08-11 16:10:56

0.5.1 already includes this change i think i fixed your syntax that it finally works

baze · 2006-08-11 19:35:13

mkinitcpio 0.5.1 still gives the "stdin: error 0" message.

phrakture · 2006-08-11 20:18:49

baze wrote:

mkinitcpio 0.5.1 still gives the "stdin: error 0" message.

Yeah, I didn't get a chance to mess with that - can you run the following:

for x in /sys/block/*/*/dev; do
   echo -n $x
   x=$(echo $x | cut -d/ -f5)
   if [ -f "/dev/$x" ]; then
      echo " exists"
   else
      echo " does not exist"
   fi
done

baze · 2006-08-11 20:24:12

$ for x in /sys/block/*/*/dev; do
>    echo -n $x
>    x=$(echo $x | cut -d/ -f5)
>    if [ -f "/dev/$x" ]; then
>       echo " exists"
>    else
>       echo " does not exist"
>    fi
> done
/sys/block/hda/hda1/dev does not exist
/sys/block/hdb/hdb1/dev does not exist
/sys/block/sda/sda1/dev does not exist
/sys/block/sda/sda10/dev does not exist
/sys/block/sda/sda11/dev does not exist
/sys/block/sda/sda12/dev does not exist
/sys/block/sda/sda2/dev does not exist
/sys/block/sda/sda3/dev does not exist
/sys/block/sda/sda4/dev does not exist
/sys/block/sda/sda5/dev does not exist
/sys/block/sda/sda6/dev does not exist
/sys/block/sda/sda7/dev does not exist
/sys/block/sda/sda8/dev does not exist
/sys/block/sda/sda9/dev does not exist

phrakture · 2006-08-11 21:19:10

Erm... I think I did that wrong... wait until I get home and I'll repost this...

straydog · 2006-08-13 04:18:42

I think I got everything right. My only possible goof is installing the updated GRUB in the wrong place (/dev/hda on a default install) in which case I'm still running on the old image. How can I confirm I'm running on the right image? Everything looks the same.

Thanks,
Bill

twiistedkaos · 2006-08-15 01:55:06

Hmm? Alright, time for me to ask a noob question, how do I know what I am using? I believe its mkinitcpio because I think I changed to it before to prepare but I can't rmemeber .

Arch Linux

#1 2006-08-07 08:15:29

Kernel 2.6.18 and mkinitcpio coming soon

#2 2006-08-09 16:07:33

Re: Kernel 2.6.18 and mkinitcpio coming soon

#3 2006-08-09 16:19:59

Re: Kernel 2.6.18 and mkinitcpio coming soon

#4 2006-08-09 16:22:08

Re: Kernel 2.6.18 and mkinitcpio coming soon

#5 2006-08-09 17:27:32

Re: Kernel 2.6.18 and mkinitcpio coming soon

#6 2006-08-09 17:55:46

Re: Kernel 2.6.18 and mkinitcpio coming soon

#7 2006-08-09 18:03:04

Re: Kernel 2.6.18 and mkinitcpio coming soon

#8 2006-08-09 19:34:16

Re: Kernel 2.6.18 and mkinitcpio coming soon

#9 2006-08-09 19:57:32

Re: Kernel 2.6.18 and mkinitcpio coming soon

#10 2006-08-09 20:47:39

Re: Kernel 2.6.18 and mkinitcpio coming soon

#11 2006-08-09 20:58:10

Re: Kernel 2.6.18 and mkinitcpio coming soon

#12 2006-08-09 21:02:59

Re: Kernel 2.6.18 and mkinitcpio coming soon

#13 2006-08-11 14:17:05

Re: Kernel 2.6.18 and mkinitcpio coming soon

#14 2006-08-11 14:24:18

Re: Kernel 2.6.18 and mkinitcpio coming soon

#15 2006-08-11 14:51:41

Re: Kernel 2.6.18 and mkinitcpio coming soon

#16 2006-08-11 14:54:13

Re: Kernel 2.6.18 and mkinitcpio coming soon

#17 2006-08-11 14:58:14

Re: Kernel 2.6.18 and mkinitcpio coming soon

#18 2006-08-11 15:37:38

Re: Kernel 2.6.18 and mkinitcpio coming soon

#19 2006-08-11 16:10:56

Re: Kernel 2.6.18 and mkinitcpio coming soon

#20 2006-08-11 19:35:13

Re: Kernel 2.6.18 and mkinitcpio coming soon

#21 2006-08-11 20:18:49

Re: Kernel 2.6.18 and mkinitcpio coming soon

#22 2006-08-11 20:24:12

Re: Kernel 2.6.18 and mkinitcpio coming soon

#23 2006-08-11 21:19:10

Re: Kernel 2.6.18 and mkinitcpio coming soon

#24 2006-08-13 04:18:42

Re: Kernel 2.6.18 and mkinitcpio coming soon

#25 2006-08-15 01:55:06

Re: Kernel 2.6.18 and mkinitcpio coming soon

Board footer