Debian Developers - Bug#240125: The new broken world of 2.6, ALSA, and hotplug.

This is Interesting: Free IT Magazines  
Home > Archive > Debian Developers > March 2004 > Bug#240125: The new broken world of 2.6, ALSA, and hotplug.





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Bug#240125: The new broken world of 2.6, ALSA, and hotplug.
Scott Robinson

2004-03-31, 3:38 pm

* Matt Zimmerman translated into ASCII [Wed, Mar 31, 2004 at 11:09:48AM -0800][<20040331190948.GI7200@alcor.net>]
[..]
> I don't see why hotplug should explicitly load the OSS drivers. If they are
> desired, they should either be loaded by ALSA's init script, or (probably
> better) set up to load automatically by an /etc/modutils file.
>


I am not impling hotplug should load the OSS drivers. I agree with the
latter solution of setting up a proper modutils dependency - something
alsa-base should be doing.

However, I do have a problem with hotplug doing PCI enumeration. Certainly,
I think it is something Linux has been missing. But, indiscriminately
loading the drivers for all hardware on a computer is the wrong behavior, as
has been demonstrated by multiple people.

I'm not totally convinced the option enabling/disabling PCI enumeration is
the solution either.

Where is a Device Manager when you need it? ;-)

[..]
> These mixer settings are notoriously fragile. They break with a new release
> of ALSA. They break *horribly* when you upgrade from 2.4 to 2.6.
>


I have not found them fragile.

Furthermore, if they are so, then why is this being done?

>
> As far as I know, this doesn't cause any harm. The message is misleading,
> but the conclusion that it draws from this is OK.
>


No, the conclusion it draws is wrong. The entire ALSA subsystem has _not_
been loaded. It thus skips the rest of its initialization because of this
incorrect assumption.

>
> udev *is* the solution to this particular problem, and personally, it
> doesn't bother me much if all of these fragile workarounds break in orderto
> make way for the correct solution.
>


udev is not the solution at this time. The package isn't not at a complete
state (README.Debian), the upstream software is still severely alpha
(0.023), and there are race conditions involving driver loading...

.. and let's not forget that udev currently causes another layer of
brokeness with ALSA (#240594) and LVM. (#236346 ?)

The fact is udev is not an upgrade path yet for 2.6 users. If it was, and it
is required, where are the Depends?

Scott.

--
http://quadhome.com/ - Personal webpage
http://tranzoa.net/ - Corporate webpage

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com