new initramfs, testers welcome

_Gandalf_ · 2006-05-10 00:42:05

@phrakture, in udev install, <code>/lib/udev/modalias_ieee1394</code> is copied two times in FILES section and as norman add_file ...

phrakture · 2006-05-10 02:53:48

Thanks, changing in svn

_Gandalf_ · 2006-05-10 03:33:50

Don't mention it

iphitus · 2006-05-10 05:37:56

for fbsplash, maybe make an /etc/fbsplash.conf or put a config in /etc/splash somewhere.

as for the script, pass it onto dibble, he still owns gensplashutils, he hasn't given it to me yet.

James

phrakture · 2006-05-10 15:26:09

iphitus wrote:

for fbsplash, maybe make an /etc/fbsplash.conf or put a config in /etc/splash somewhere.

The only thing I don't like about using extra external configs is that, potentially, one needs to keep track of a handful of config files that require a new image generated. Those unfamiliar with the internals of things may thing it works simply by editing the config file. And no one wants to auto-generate a new image on shutdown or something like that.

I may add some extension functionality so that one can easilly require config settings in mkinitcpio.conf if a given hook is added. I'll think about it.

_Gandalf_ · 2006-05-10 16:20:47

That would be a cool idea and user will not have his conf file bloated, maybe we add a /etc/mkinitcpio.d and add all extra configs there, no ?

phrakture · 2006-05-10 17:12:58

Hmm, sounds like a decent idea.

I'll think about it. However, at this point, I'd really like to freeze features as much as possible, and move to a more stable test-cycle.

Please report any and all errors/annoyances in this thread. I will release newer versions tonight, when I'm sure I've fixed things.

_Gandalf_ · 2006-05-11 03:06:29

The below patch should be applied to keymap install hook otherwize if the user have quoted his keymap it won't work ( like keymap='fr' or keymap="fr" it will fail)

Index: keymap.install
===================================================================
--- keymap.install      (revision 454)
+++ keymap.install      (working copy)
@@ -41,7 +41,7 @@
     [ "$CONSOLEMAP" != "" ] && add_file /usr/share/kbd/unimaps/$(grep "CONSOLEMAP=" /etc/rc.conf | awk -FCONSOLEMAP= '{print $2}')*
     if [ "$KEYMAP" != "" ]; then
         for i in $(find /usr/share/kbd/ -name "$(grep "KEYMAP=" /etc/rc.conf |
-            awk -FKEYMAP= '{print $2}' | awk -F- '{print $1}')*.map.gz"); do
+            awk -FKEYMAP= '{print $2}' | awk -F- '{print $1}' | sed -e "s@["']*@@g")*.map.gz"); do
             add_file $i
         done
         for i in $(echo /usr/share/kbd/keymaps/include/*); do

dtw · 2006-05-14 11:58:27

fbsplash & mkinitcpio [split]

mouse256 · 2006-05-17 09:24:52

It works fine here using mkinitcpio from testing.

Using software raid0 for booting with kernel26-beyond
Mkinitramfs won't work on my system, so mkinitcpio works defenitely better for me :-)

phrakture · 2006-05-17 15:31:40

I see lots of positive responses, which is great. I'd like to begin a feature freeze cycle here, with a shade more agressive testing.

To all you who haven't tested this stuff out, please do so, as I'd like to squash any remaining bugs so we can move closer to making this the official, and unified way to boot an arch system.

Any bugs can be reported here. Feel free to contact me via email, forums PM, or IRC if you need any help with this.

lilsirecho · 2006-05-17 15:37:45

Kernel panic on all attempts even with latest upgrades.

phrakture · 2006-05-17 15:41:40

lilsirecho wrote:

Kernel panic on all attempts even with latest upgrades.

I'm going to need more information than that. I'm not psychic.
Were there any "ERROR:" lines reported? What are the last 5 or so lines before the kernel panic? What boot loader, kernel params, hooks, modules, etc

Bug reporting is much more beneficial when you assume I have no knowledge of your system (I don't) - it's better to provide too much info.

lilsirecho · 2006-05-17 15:49:48

My previous posts list all info..................

phrakture · 2006-05-17 16:00:39

lilsirecho wrote:

My previous posts list all info..................

So I guess we have to play the guessing game? Where I ask you questions and you say yes or no?
*sigh*

Is this still the issue?

lilsirecho wrote:

:: Loading root filesystem module..attempting to create root device '303'
/init : 28 : Cannot open 303 : No such device or address

If that still appears, have you updated your system recently? The new filesystem hook should take care of that. Also, I had given you a possible solution to this problem.... and heard no response from you.

Please, this will be far easier if you provide information for me. There are alot of posts here, and alot of your posts have been responded to. It is impossible to determine what is still and issue and what has changed - there are too many variables.

I am not asking for information just to bother you. I am not asking for information because I'm lazy. I'm asking for information because there is too much involved, and the _only_ way to know the problem is to know exactly what is going on right now.

Cerebral · 2006-05-17 17:10:14

I'll give this a shot tonight once I get home after supper, see what happens.

lilsirecho · 2006-05-17 17:24:44

Have tried all suggestions you have presented and have upgraded to the latest klibc and mkinitcpio and latest kernel in arch.
Modules autodetected:
cdrom
ide-cd
ide-core
ide-disk
generic
via82cxxx
ieee1394
ohci1394
8390
via-ircc
ne2k-pci
usbcore
ehci-hcd
uhci-hcd
usbhid
irda
snd-usb-audio
snd-usb-lib
ext2
jbd
ext3
jfs
reiserfs
xfs
zlib_inflate
cramfs
fat
vfat
[root@n6re ~]#

#
# /etc/lilo.conf
#

boot=/dev/hda
# This line often fixes L40 errors on bootup
# disk=/dev/hda bios=0x80

default=arch
timeout=50
lba32
prompt

image=/boot/vmlinuz26
label=arch
root=/dev/hda3
initrd=/boot/initrd26-full.img
read-only
image=/boot/vmlinuz26archck
label=archck
root=/dev/hda3
initrd=/boot/initramfs-2.6.15-archck.img
read-only
image=/boot/vmlinuz26beyond
label=2.6.16-beyond
root=/dev/hda3
initrd=/boot/initramfs-beyond.img
read-only
image=/boot/vmlinuz26beyond
label=cpio
root=/dev/hda3
initrd=/boot/ray.img

read-only
image=/boot/vmlinuz26archck
label=cpio1
root=/dev/hda3
initrd=/boot/ray.img
read-only
#other=/dev/hda1
# label=dos

====================================================================
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""

# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT ovedev/hda3

# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mki ctcpio -H <hook>' for
# help on a given hook.e
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm, or encrypted root is needed.ras
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
HOOKS="base udev ide scsi sata usb filesystems"
#
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide filesystems raid encrypt"
#
# This setup loads an LVM volume group on a usb device.
# HOOKS="base udev usb filesystems lvm"
#HOOKS="base udev autodetect ide usb usbinput filesystems"

lilsirecho · 2006-05-17 17:42:20

Additional info: Kernel panic data
kinit: do mounts
Waiting 0 secs before mounting root device
kinit: name_to_dev_t (/dev/root) =dev(3,3)

kinit: trying to mount /dev/root on /root with type ext2

knit: cannot open root device dev(3,3)

kinit: init not found

Kernel panic: attemting to kill init !
====================================================================
I just finished downloading the latest klibc and mkinitcpio data(repeat of previous post).

I seem to be able to break everything I try...that is the object of testing !!

Just do things out of order I guess, not knowing the correct order!

phrakture · 2006-05-17 17:59:17

lilsirecho wrote:

kinit: trying to mount /dev/root on /root with type ext2
knit: cannot open root device dev(3,3)

What filesystem is on this partition? Does it say the right type when it tries to detect the filesystem (filesystems hook)?

lilsirecho · 2006-05-17 18:09:21

The filesystem is ext3 on this HDD...

sputnik · 2006-05-17 18:28:17

Works fine here, just waiting for gensplash stuff now

Cerebral · 2006-05-17 18:56:03

lilsirecho wrote:

image=/boot/vmlinuz26beyond
        label=cpio
        root=/dev/hda3
        initrd=/boot/ray.img
        read-only
image=/boot/vmlinuz26archck
        label=cpio1
        root=/dev/hda3
        initrd=/boot/ray.img
        read-only

I just noticed this - you use the same image for multiple kernels. Will this work? I mean, inside the image there are actual kernel modules, right? I think the kernel will only allow modules that were built at the same time as that kernel to be loaded - so if beyond modules are inside the image, your archck kernel won't be able to load them, will it?

Please correct me if I'm way off base here.

brain0 · 2006-05-17 19:24:57

@Cerebral: A separate images is needed for every kernel.

@lilsirecho: In lilo.conf, instead of

root=/dev/hdXY

try

append="root=/dev/hdXY"

@phrakture: Even if we fix this in mkinitcpio, there would be much less problems if we recommended using this lilo.conf syntax. For grub this isn't an issue anyway.

lilsirecho · 2006-05-17 20:02:34

Braino;

Tried that already with no help....

lilsirecho · 2006-05-18 00:09:43

Perhaps my problem is related to Cerebral's remark about separate images for each kernel.

I have generated all elements of the system, klibc,mkinitcpio, and mkinitcpio.conf. while in arch kernel. I saw not requirement to load these elements into beyond or archck but only to ID the label and change the initrd to enable autodetect via mkinitcpio image. This all makes sense to me but mebbe its wrong?

Arch Linux

#76 2006-05-10 00:42:05

Re: new initramfs, testers welcome

#77 2006-05-10 02:53:48

Re: new initramfs, testers welcome

#78 2006-05-10 03:33:50

Re: new initramfs, testers welcome

#79 2006-05-10 05:37:56

Re: new initramfs, testers welcome

#80 2006-05-10 15:26:09

Re: new initramfs, testers welcome

#81 2006-05-10 16:20:47

Re: new initramfs, testers welcome

#82 2006-05-10 17:12:58

Re: new initramfs, testers welcome

#83 2006-05-11 03:06:29

Re: new initramfs, testers welcome

#84 2006-05-14 11:58:27

Re: new initramfs, testers welcome

#85 2006-05-17 09:24:52

Re: new initramfs, testers welcome

#86 2006-05-17 15:31:40

Re: new initramfs, testers welcome

#87 2006-05-17 15:37:45

Re: new initramfs, testers welcome

#88 2006-05-17 15:41:40

Re: new initramfs, testers welcome

#89 2006-05-17 15:49:48

Re: new initramfs, testers welcome

#90 2006-05-17 16:00:39

Re: new initramfs, testers welcome

#91 2006-05-17 17:10:14

Re: new initramfs, testers welcome

#92 2006-05-17 17:24:44

Re: new initramfs, testers welcome

#93 2006-05-17 17:42:20

Re: new initramfs, testers welcome

#94 2006-05-17 17:59:17

Re: new initramfs, testers welcome

#95 2006-05-17 18:09:21

Re: new initramfs, testers welcome

#96 2006-05-17 18:28:17

Re: new initramfs, testers welcome

#97 2006-05-17 18:56:03

Re: new initramfs, testers welcome

#98 2006-05-17 19:24:57

Re: new initramfs, testers welcome

#99 2006-05-17 20:02:34

Re: new initramfs, testers welcome

#100 2006-05-18 00:09:43

Re: new initramfs, testers welcome

Board footer