FS#24807 - [mkinitcpio-0.6.15-1] - typeo in line 56

Attached to Project: Arch Linux
Opened by John (graysky) - Monday, 20 June 2011, 21:45 GMT
Last edited by Thomas Bächler (brain0) - Wednesday, 22 June 2011, 11:53 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version 3.5.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info: minor error at boot up due to the -q switch in /lib/initcpio/init on line 56.

As it stands, this is what happens at boot up just after the boot logo is displayed:

Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]

This is due to the aforementioned error on line 56: /sbin/modprobe -qab $MODULES
This task depends upon

Closed by  Thomas Bächler (brain0)
Wednesday, 22 June 2011, 11:53 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#24766 
Comment by Dave Reisner (falconindy) - Tuesday, 21 June 2011, 03:10 GMT
Not an error, persay. Just a lack of arguments when the MODULES= variable is empty in mkinitcpio.conf. Patch was submitted to fix this last week.

http://mailman.archlinux.org/pipermail/arch-projects/2011-June/001081.html
Comment by John (graysky) - Tuesday, 21 June 2011, 08:33 GMT
falconindy - My variable is !null and I still get the error....

$ grep MOD /etc/rc.conf
MODULES=(acpi-cpufreq)
Comment by Dave Reisner (falconindy) - Tuesday, 21 June 2011, 10:02 GMT
Note that I said mkinitcpio.conf, not rc.conf.
Comment by John (graysky) - Tuesday, 21 June 2011, 20:13 GMT
My bad - you are right: my MODULES variable in /etc/mkinitcpio.conf is indeed null.

Loading...