You are not logged in.

#1 2011-06-26 14:50:35

Master One
Member
From: Europe
Registered: 2007-01-21
Posts: 249

Call for /sbin/modprobe without argument in initrd?

I just did a new install and when booting the new system I discovered, that /sbin/modprobe seems to be executed without argument in initrd, because it prints the "Usage" message right after starting udevd before running the udev hook. So the output on screen looks like this:

.
.
.
:: Starting udevd...
done.
Usage: /sbin/modprobe [-v] [-V] [-C config-file .....
:: Running Hook [udev]
.
.
.

It's not a real problem, but looks annoying since I use the "quiet" kernel argument and system encryption, which makes that "Usage: /sbin/modprobe ..." message pop up right above the "enter passphrase" line each time I boot that machine.

Offline

#2 2011-06-26 14:59:11

Clouseau
Member
Registered: 2010-12-24
Posts: 112

Re: Call for /sbin/modprobe without argument in initrd?

Also happening to me...

Offline

#3 2011-06-26 15:00:22

JokerBoy
Member
From: România
Registered: 2009-09-24
Posts: 641

Re: Call for /sbin/modprobe without argument in initrd?

Offline

#4 2011-06-26 15:00:49

litemotiv
Forum Fellow
Registered: 2008-08-01
Posts: 5,026

Re: Call for /sbin/modprobe without argument in initrd?

That might be a bug in the rc-script, trying to load an empty module name. Could you open a bug report for this and provide as much information as possible?

Edit: thanks JokerBoy. Please use that other thread and bugreport, closing this one to avoid duplication.

Last edited by litemotiv (2011-06-26 15:02:32)


ᶘ ᵒᴥᵒᶅ

Offline

Board footer

Powered by FluxBB