pass options to modules in mkinitrd.conf

bonaire · 07-20-2009, 02:48 PM

Hello,

my /etc/mkinitrd.conf:

Code:

SOURCE_TREE="/boot/initrd-tree"
CLEAR_TREE="1"
OUTPUT_IMAGE="/boot/initrd.gz"
KERNEL_VERSION="2.6.30.2-smp"
KEYMAP="de-latin1-nodeadkeys"
MODULE_LIST="ehci_hcd:uhci_hcd:usb_storage:xfs:ext2:i915 modeset=1:intel_agp"
LUKSDEV="/dev/mapper/vg-root"
ROOTDEV="crypt-vg-root"
ROOTFS="xfs"
LVM="1"

If i call this via mkinitrd -F, i get these messages:

Code:

/sbin/mkinitrd: line 376: [: ehci_hcd:uhci_hcd:usb_storage:xfs:ext2:i915: binary operator expected
/sbin/mkinitrd: line 400: [: ehci_hcd:uhci_hcd:usb_storage:xfs:ext2:i915: binary operator expected
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/usb/host/ehci-hcd.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/usb/host/uhci-hcd.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/usb/storage/usb-storage.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/fs/exportfs/exportfs.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/fs/xfs/xfs.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/fs/ext2/ext2.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/i2c/i2c-core.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/video/output.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/hwmon/hwmon.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/thermal/thermal_sys.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/acpi/video.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/i2c/algos/i2c-algo-bit.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/char/agp/agpgart.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/gpu/drm/drm.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/gpu/drm/i915/i915.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/char/agp/agpgart.ko added.
OK: /lib/modules/2.6.30.2-smp/kernel/drivers/char/agp/intel-agp.ko added.
11484 blocks

If i don't pass the modeset option to the i915 module, all is fine. Is there something wrong with my syntax or is it a bug?
The man page man mkinitrd.conf says, that my syntax is ok:

Code:

       MODULE_LIST
            This  should  be a colon-separated list of modules you wish to be included in the initrd
            image.
            Example: MODULE_LIST="ext3:mbcache:jbd"

            If you have loadtime options that you need to specify when loading kernel modules, those
            can be added here as well.
            Example: MODULE_LIST="module1:module2 option=1:module3"

cu

Edit:
I forgot, my system is slackware-current

rg3 · 07-20-2009, 03:55 PM

I think this is a bug in mkinitrd. Open /sbin/mkinitrd as root and, in lines 376 and 400, write double quotes around ${MODULE_LIST}, so it looks "${MODULE_LIST}". That should probably solve the problem. Please report success.

bonaire · 07-20-2009, 04:16 PM

That helped, thanks.

Shall i write an email, or is it enough, that this is written here?

cu

rg3 · 07-20-2009, 04:43 PM

I just wrote P. Volkerding an email about this.

bonaire · 07-20-2009, 04:44 PM

Ok, thanks again

rg3 · 08-03-2009, 04:09 PM

There have been quite a few upgrades since I wrote the email but no reply from PV and no fixed package. I'm just bumping the thread so this gets attention by any member of the Slackware team and the problem is fixed before Slackware 13.0 is released.

bonaire · 08-14-2009, 09:18 PM

Thanks a lot

rworkman · 08-14-2009, 09:36 PM

@bonaire: I tried to reply to your email inquiring about this, but here's what I received in reply to it:

Code:

From postmaster@goodmails.de Fri Aug  7 12:05:44 2009
Date: Fri,  7 Aug 2009 21:02:01 +0200 (CEST)
From: Mail Delivery System <postmaster@goodmails.de>
To: rworkman@slackware.com
Subject: Returned mail: see mail body for details

The original message was received at Fri, 07 Aug 2009 21:02:01 +0200 from rworkman@slackware.com by b1gMail/6.3.0.

Error: Your mail was blocked by a filter

bonaire · 08-14-2009, 11:09 PM

Ah, ok. The provider gets an unfriendly email

cu

rworkman · 08-14-2009, 11:15 PM

Quote:

Originally Posted by bonaire

Ah, ok. The provider gets an unfriendly email

Just so you know, I'm going to laugh if it gets "blocked by a filter" too. ;-)