Re: Devices conflict & modconf
> > This is a mail i posted yesterday to debian-user, about a small bug i
> > found in modconf (Woody version), and a solution proposal. The bug
> > relies on default modules loading order.
>
> Which bug?
Sorry for not being clear enough, i could have been more explicit!
1) Effectively modules where loaded as i asked them to:
i asked for es1371, and for usbaudio. And i had them.
I do not complain on any program loading these modules without being asked
to, modconf does this perfectly. For this reason i am a happy modconf
user!
2) But the default modules order in modules.conf, as generated by modconf,
was not good for me.
Having asked for es1371 and usbaudio, modconf decided arbitrary to place
usbaudio before es1371 in modules.conf.
The trouble is that usbaudio reclaims /dev/audio, if loaded first.
This is why cat file.au>/dev/audio did not work on my machine.
es1371 ends up with poor /dev/audio1, which is uncommon for a sound card.
I think that modconf could be a little smarter, and order things
differently by default (i.e. at least if no --load-before or --load-after
directive is given): OSS and ALSA modules should be loaded before
usbaudio.
This way, most people having a sound card, and buying a webcam with
microphone, would be pleased (if they are modconf users, like me)!
Retrospectively the term "bug" is too strong, i should have written "wish"
or "wishlist bug". I apologize on this.
But i hope you will agree with my point of view :)
Regards,
Xavier de Labouret
--
To UNSUBSCRIBE, email to debian-boot-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: