I am trying to solve two problems:
1. Load my sound-card module ("snd_via_82xx") before "snd_usb_audio" (I
have a webcam with integrated mike); for some reason, sound won't work
if they are loaded in the opposite order;
2. Avoid to load the "floppy" module at each boot, since I do not have a
floppy drive.

What is the proper way to load sound-card modules at boot? I have read
somewhere on this list that alsaconf is no longer recommended. Is udev
supposed to handle everything now? What should I have in /etc/modules
then? Most importantly, how do I configure udev to get the modules in
the right order and to prevent "floppy" from being loaded (if it is
actually udev's fault...)?

Thanks for reading.
Davide

--
A tautology is a thing which is tautological.
--
Time flies like an arrow. Fruit flies like a banana.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sat, Sep 08, 2007 at 05:05:08PM +0200, Davide Mancusi wrote:
> I am trying to solve two problems:
> 1. Load my sound-card module ("snd_via_82xx") before "snd_usb_audio" (I
> have a webcam with integrated mike); for some reason, sound won't work if
> they are loaded in the opposite order;
> 2. Avoid to load the "floppy" module at each boot, since I do not have a
> floppy drive.
>
> What is the proper way to load sound-card modules at boot? I have read
> somewhere on this list that alsaconf is no longer recommended. Is udev
> supposed to handle everything now? What should I have in /etc/modules then?
> Most importantly, how do I configure udev to get the modules in the right
> order and to prevent "floppy" from being loaded (if it is actually udev's
> fault...)?

See 'man modprobe.conf'. There is an example for just what you need for
1. For 2. a simple 'blacklist' should be enough, but post back if it
doesn't work (some modules are a bit stubborn).

Regards,
Andrei
P.S. My recommendation is to create a file /etc/modprobe.d/00local for
all your customizations
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG4soYqJyztHCFm9kRAinxAKCBxRQ37iA9XMAtrHfD3B 0gHigDtwCfYMe8
ccheYAUG/nulyZKqm/M8Ios=
=/AMv
-----END PGP SIGNATURE-----

Andrei Popescu ha scritto:
> See 'man modprobe.conf'.

So, that's where the man page for modprobe.d is...

> There is an example for just what you need for
> 1. For 2. a simple 'blacklist' should be enough, but post back if it
> doesn't work (some modules are a bit stubborn).

I have already a file in modprobe.d that blacklists floppy. Now it
contains also the line

install snd-usb-audio /sbin/modprobe snd-via82xx && /sbin/modprobe \
--ignore-install snd-usb-audio

However, floppy is still loaded, little stubborn module. What happens,
really? Why is it loaded anyway? Perhaps it is inserted from the initrd?

Davide

--
A tautology is a thing which is tautological.
--
Time flies like an arrow. Fruit flies like a banana.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sat, Sep 08, 2007 at 07:03:09PM +0200, Davide Mancusi wrote:

> I have already a file in modprobe.d that blacklists floppy. Now it contains
> also the line
>
> install snd-usb-audio /sbin/modprobe snd-via82xx && /sbin/modprobe \
> --ignore-install snd-usb-audio
>
> However, floppy is still loaded, little stubborn module. What happens,
> really? Why is it loaded anyway? Perhaps it is inserted from the initrd?

The pcspkr module needs this:

install pcspkr /bin/true

HTH,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG4vFcqJyztHCFm9kRAvCRAKCNyjmuTS2xdM+4tXEsd+ gCZrrHRACgko3B
16GS0L/JDAWitgNtKCxiLIM=
=U+ID
-----END PGP SIGNATURE-----

Andrei Popescu ha scritto:
> The pcspkr module needs this:
>
> install pcspkr /bin/true
>
> HTH,
> Andrei

That didn't . However, adding a "blacklist=floppy" option to kernel
boot did the trick. I think "floppy" is included in the initrd image and
is loaded by the kernel in the early phases of boot; I also suspect this
happens because I let the Debian installer load "floppy" when I set up
my system.

Thank you for the .

Davide

--
A tautology is a thing which is tautological.
--
Time flies like an arrow. Fruit flies like a banana.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

>That didn't . However, adding a "blacklist=floppy"
>option to kernel boot did the trick. I think "floppy" is
>included in the initrd image and is loaded by the kernel
>in the early phases of boot; I also suspect this happens
>because I let the Debian installer load "floppy" when I
>set up my system.

That is (somewhat) correct; the scripts which create the initrd image will normally (in the default install) put all framebuffer, acpi, filesystem, and hard disk drivers into the image. Have a look in /etc/initramfs-tools/initramfs.conf to get some idea what goes on. I had problems a few months ago when I changed my kernel and discovered that the scripts included (but didn't load) the 'md' driver.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

pinniped ha scritto:
> That is (somewhat) correct; the scripts which create the initrd image
> will normally (in the default install) put all framebuffer, acpi,
> filesystem, and hard disk drivers into the image. Have a look in
> /etc/initramfs-tools/initramfs.conf to get some idea what goes on.

I did, but the only way I found to control modules included in the
initrd is the MODULES option in initramfs.conf (presently set to
MODULES=most). I can't see any way to exclude "floppy" (I could specify
a list, of course, but how do I know what modules are included by "most"?).

I wonder what you get in initramfs.conf if you do not select to load
"floppy" when installing. Does it get loaded anyway?

Davide

--
A tautology is a thing which is tautological.
--
Time flies like an arrow. Fruit flies like a banana.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sun, Sep 09, 2007 at 01:40:11PM +0200, Davide Mancusi wrote:
> pinniped ha scritto:
>> That is (somewhat) correct; the scripts which create the initrd image
>> will normally (in the default install) put all framebuffer, acpi,
>> filesystem, and hard disk drivers into the image. Have a look in
>> /etc/initramfs-tools/initramfs.conf to get some idea what goes on.
>
> I did, but the only way I found to control modules included in the initrd
> is the MODULES option in initramfs.conf (presently set to MODULES=most). I
> can't see any way to exclude "floppy" (I could specify a list, of course,
> but how do I know what modules are included by "most"?).

you can look in the initrd itself, google for instructions on
unpacking it, or wait for madduck (and others) to notice this thread
and pipe up about it.

You can mess around with initrd all you want without serious
risk. Just rename the current working initrd to something sensible;
mess around with the configs and build a new one and try it on a
reboot. If it fails, reboot again and select the known working one by
editing your grub parameters and try again.

You certainly won't go very far wrong by selecting MODULES=dep or
whatever it is. That will then only insert the modules that are
required to boot the system based on the current hardware (not sure
what foo it uses to do this) requirements. But it will certainly get
you a smaller initrd and may with certain persistently loaded
modules (like floppy).

>
> I wonder what you get in initramfs.conf if you do not select to load
> "floppy" when installing. Does it get loaded anyway?
>

I suspect that these are completely seperate processes.

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG5DaNaIeIEqwil4YRAqUvAKCxJklO1VnlcK1sM/i/8NnyMyV0JwCgka63
8iNQn6VnB+G5TkBvZg5uzRw=
=Aw73
-----END PGP SIGNATURE-----