On Thu, 10 Mar 2005 22:00:15 +0100, Thomas Hood wrote:
Here is another idea. We create a new binary package
sound-system-chooser which contains blacklists for both OSS and ALSA and
provides a debconf interface that the administrator can use to disable
either or both of the sound systems.
Le jeudi 10 mars 2005 à 08:17 +0100, Goswin von Brederlow a écrit :
The kernel could blacklist alsa modules by default and the alsa-base
would divert that to blacklist oss. That sounds the simplest.
It isn't possible to divert files in /etc.
--
.''`. Josselin Mouette/\./\
:
Thomas Hood [EMAIL PROTECTED] writes:
If a fresh sarge/2.6 system lacks alsa-base then this would seem to be a
problem because in that case nothing enforces the mutual exclusion of OSS
and ALSA modules. If linux26 doesn't install alsa-base then perhaps it
should do so. Even better,
On Wed, Mar 09, 2005 at 05:46:22PM -0800, Steve Langasek [EMAIL PROTECTED]
wrote:
Considering you're talking about solutions that require updates to
kernel-image packages *anyway*, why has no one suggested adding the
necessary blacklist entries to these packages? Far better than removing a
[EMAIL PROTECTED] writes:
Thomas Hood [EMAIL PROTECTED] writes:
If a fresh sarge/2.6 system lacks alsa-base then this would seem to be a
problem because in that case nothing enforces the mutual exclusion of OSS
and ALSA modules. If linux26 doesn't install alsa-base then perhaps it
Goswin Brederlow writes:
Thomas Hood [EMAIL PROTECTED] writes:
So to be clear the alternatives suggested so far are:
1. The two-package approach
* oss blacklists ALSA modules
* alsa-base blacklists OSS modules
* alsa-base Conflicts with oss
* kernel-image Depends on
On Thu, 10 Mar 2005 02:50:04 +0100, Steve Langasek wrote:
Considering you're talking about solutions that require updates to
kernel-image packages *anyway*, why has no one suggested adding the
necessary blacklist entries to these packages?
k-i packages aren't the right place to put the
On Thu, Mar 10, 2005 at 11:57:11AM +0100, Mike Hommey wrote:
On Wed, Mar 09, 2005 at 05:46:22PM -0800, Steve Langasek [EMAIL PROTECTED]
wrote:
Considering you're talking about solutions that require updates to
kernel-image packages *anyway*, why has no one suggested adding the
necessary
On Thu, 10 Mar 2005 01:10:12 +0100, Josselin Mouette wrote:
Davide, would you agree with making gnome-media depend on something like
alsa-base | kernel-image-2.4, to ensure sound is working properly upon
installation?
I don't see why gnome-media should be involved. This problem has nothing
On Mon, 07 Mar 2005 00:10:12 +0100, Christoph Hellwig wrote:
It's not a depency in any way. I play sound just fine with OSS drivers
without the ALSA mess getting in my way anywhere.
On Mon, 07 Mar 2005 13:50:10 +0100, Josselin Mouette wrote:
Without alsa-base installed, hotplug and discover
On Mon, 07 Mar 2005 20:40:40 +0100, Josselin Mouette wrote:
Actually, the proposed solution that raised some approval was to split
out the ALSA modules, just like the pcmcia modules.
I raised this idea on #debian-kernel and it was shot down.[0]
Le mercredi 09 mars 2005 20:33 +0100, Thomas Hood a crit :
In theory I guess there should be an oss package that was the homologue of
the alsa-base package. It would include files that would blacklist ALSA
modules, just as alsa-base blacklists OSS modules. These packages would
Conflict with
Le jeudi 10 mars 2005 00:12 +0100, Thomas Hood a crit :
On Mon, 07 Mar 2005 20:40:40 +0100, Josselin Mouette wrote:
Actually, the proposed solution that raised some approval was to split
out the ALSA modules, just like the pcmcia modules.
I raised this idea on #debian-kernel and it was
On Thu, Mar 10, 2005 at 12:12:37AM +0100, Thomas Hood wrote:
On Mon, 07 Mar 2005 20:40:40 +0100, Josselin Mouette wrote:
Actually, the proposed solution that raised some approval was to split
out the ALSA modules, just like the pcmcia modules.
I raised this idea on #debian-kernel and it was
Thomas Hood [EMAIL PROTECTED] writes:
On Mon, 07 Mar 2005 20:40:40 +0100, Josselin Mouette wrote:
Actually, the proposed solution that raised some approval was to split
out the ALSA modules, just like the pcmcia modules.
I raised this idea on #debian-kernel and it was shot down.[0]
On Mon, 07 Mar 2005 13:50:10 +0100, Josselin Mouette wrote:
Without alsa-base installed, hotplug and discover will load both
modules, resulting in various disasters depending on the hardware. It's
not because things work with your setup that they are suitable for a
stable Debian release.
Le lundi 07 mars 2005 à 00:03 +0100, Christoph Hellwig a écrit :
On Fri, Mar 04, 2005 at 02:41:27PM +0100, Josselin Mouette wrote:
When you install an alsa-modules package for the 2.4 kernel, you get
alsa-base per the dependencies. However, when you install sarge with a
2.6 kernel,
On 07-Mar-05, 06:23 (CST), Josselin Mouette [EMAIL PROTECTED] wrote:
Le lundi 07 mars 2005 ? 00:03 +0100, Christoph Hellwig a ?crit :
It's not a depency in any way. I play sound just fine with OSS drivers
without the ALSA mess getting in my way anywhere.
Without alsa-base installed,
Le lundi 07 mars 2005 à 07:26 -0600, Steve Greenland a écrit :
Without alsa-base installed, hotplug and discover will load both
modules, resulting in various disasters depending on the hardware. It's
not because things work with your setup that they are suitable for a
stable Debian
On 07-Mar-05, 11:06 (CST), Josselin Mouette [EMAIL PROTECTED] wrote:
And the workaround we use for this bug is to blacklist one module when
two of them provide the same functionality. The blacklists are in the
alsa-base package, which should then be installed when ALSA modules are
present.
Le lundi 07 mars 2005 12:53 -0600, Steve Greenland a crit :
On 07-Mar-05, 11:06 (CST), Josselin Mouette [EMAIL PROTECTED] wrote:
And the workaround we use for this bug is to blacklist one module when
two of them provide the same functionality. The blacklists are in the
alsa-base package,
Josselin Mouette wrote:
When you install an alsa-modules package for the 2.4 kernel, you get
alsa-base per the dependencies. However, when you install sarge with a
2.6 kernel, alsa-base doesn't end up being installed. The result is that
for most sound cards, both OSS and ALSA modules end up
On Sun, 06 Mar 2005 00:20:13 +0100, Paul Hampson wrote:
Hmm. I would think that the better solution (the less surprising
solution) would be to leave out the ALSA modules from the Debian
kernel package, since we have a seperate package of ALSA modules
which _does_ depend on alsa-base.
That's
Le dimanche 06 mars 2005 11:53 +0100, Thomas Hood a crit :
On Fri, 04 Mar 2005 20:20:10 +0100, Josselin Mouette wrote:
As long as the linux26 installation ends up with both sound modules
loaded, that's a bug that needs to be fixed, though. Another option
would be to put the alsa modules in
On Fri, Mar 04, 2005 at 02:41:27PM +0100, Josselin Mouette wrote:
When you install an alsa-modules package for the 2.4 kernel, you get
alsa-base per the dependencies. However, when you install sarge with a
2.6 kernel, alsa-base doesn't end up being installed.
It's not a depency in any way. I
Le samedi 05 mars 2005 à 00:44 +0100, Goswin von Brederlow a écrit :
Exactly. I don't have alsa-base installed on any of my 2.6.x systems
and some of them have sound and some don't. None of them have
problems.
A depends would be too strong. A recommends/suggests should be there.
I'm only
On Sat, Mar 05, 2005 at 12:01:47PM +0100, Josselin Mouette wrote:
Le samedi 05 mars 2005 à 00:44 +0100, Goswin von Brederlow a écrit :
Exactly. I don't have alsa-base installed on any of my 2.6.x systems
and some of them have sound and some don't. None of them have
problems.
A depends
Hi.
Josselin Mouette wrote:
As long as the linux26 installation ends up with both sound modules
loaded, that's a bug that needs to be fixed, though. Another option
would be to put the alsa modules in separate packages, just like pcmcia
modules.
That definetly sounds much better ;).
Kind regards
When you install an alsa-modules package for the 2.4 kernel, you get
alsa-base per the dependencies. However, when you install sarge with a
2.6 kernel, alsa-base doesn't end up being installed. The result is that
for most sound cards, both OSS and ALSA modules end up installed,
resulting in
Josselin Mouette wrote:
2.6 kernel, alsa-base doesn't end up being installed. The result is that
for most sound cards, both OSS and ALSA modules end up installed,
resulting in various and random problems. To avoid that, shouldn't the
kernel-image packages for 2.6 depend on alsa-base?
Please not.
Le vendredi 04 mars 2005 à 15:29 +0100, Thomas Viehmann a écrit :
Josselin Mouette wrote:
2.6 kernel, alsa-base doesn't end up being installed. The result is that
for most sound cards, both OSS and ALSA modules end up installed,
resulting in various and random problems. To avoid that,
When you install an alsa-modules package for the 2.4 kernel, you get
alsa-base per the dependencies. However, when you install sarge with a
2.6 kernel, alsa-base doesn't end up being installed. The result is that
for most sound cards, both OSS and ALSA modules end up installed,
resulting in
[Nikita V. Youshchenko]
Maybe it's better just not to provide oss drivers for chips supported
by alsa? AFAIK OSS will be removed from kernel soon...
It may or may not be removed soon - I note that it isn't listed in
Documentation/feature-removal-schedule.txt in kernel 2.6.11 yet.
Anyway, two
Thomas Viehmann [EMAIL PROTECTED] writes:
Josselin Mouette wrote:
2.6 kernel, alsa-base doesn't end up being installed. The result is that
for most sound cards, both OSS and ALSA modules end up installed,
resulting in various and random problems. To avoid that, shouldn't the
kernel-image
34 matches
Mail list logo
