alsa setup too agressive

[Jan]

My box REQUIRES the module sb.ko to produce any usable sound hence I
certainly did not enjoy it could not be loaded after recent kernel update
in Hoary. Note the 'descriptive' error message:

me@ubuntu:~ $ modprobe sb
FATAL: Module off not found.
me@ubuntu:~ $

Dear ALSA maintainers: I know you are running a difficult mission. But please
keep you sledgehammers out of our systems. Linus still includes oss modules
into mainline kernel and does it on purpose. They are people using them !

[Thomas Hood (jdthood-aglu)]

severity 287499 minor
thanks

I am rating this "minor" because it's a documentation issue, not
necessarily because I think it's a minor documentation issue. :)

On Tue, 2004-12-28 at 11:27 +0100, Bernhard Reiter wrote:
> While blacklisting the oss modules in several ways seems to be the right
> thing to do to avoid strange situations, I suggest that you bring
> up a warning for system administrators when you install or upgrade alsa-base
> with this blacklisting in place so that they are warned and know what
> do to (undo the blacklisting in discover, modutils or hotplug)
> before they start looking into modutils or other packages which they
> suspect to be broken.

The package description already mentions this issue. I could discuss it
further in README.Debian I suppose.

--
Thomas Hood <email address hidden>

[Thomas Hood (jdthood-yahoo)]

# Automatically generated email from bts, devscripts version 2.8.5
tags 287499 confirmed

[Bernhard Reiter (bernhard-intevation)]

On Thu, Dec 30, 2004 at 10:01:45PM +0100, Thomas Hood wrote:
> I am rating this "minor" because it's a documentation issue, not
> necessarily because I think it's a minor documentation issue. :)

Because it leads to modules not being loaded
and a hard to diagnose situation in other modulues only be upgrading,
I would say it is more then "minor" or documentation only:
It breaks real installations and eats up system administrator's time.

> On Tue, 2004-12-28 at 11:27 +0100, Bernhard Reiter wrote:
> > While blacklisting the oss modules in several ways seems to be the right
> > thing to do to avoid strange situations, I suggest that you bring
> > up a warning for system administrators when you install or upgrade alsa-base
> > with this blacklisting in place so that they are warned and know what
> > do to (undo the blacklisting in discover, modutils or hotplug)
> > before they start looking into modutils or other packages which they
> > suspect to be broken.
>
>
> The package description already mentions this issue. I could discuss it
> further in README.Debian I suppose.

On a regular upgrade, people will not inspect README.Debian
or the packages description of a package, this does not ease the problem.

 Bernhard

[Thomas Hood (jdthood-aglu)]

> On a regular upgrade, people will not inspect README.Debian

OK, how 'bout a NEWS item?
--
Thomas Hood <email address hidden>

[Bernhard Reiter (bernhard-intevation)]

On Mon, Jan 03, 2005 at 01:30:32PM +0100, Thomas Hood wrote:
> > On a regular upgrade, people will not inspect README.Debian
>
> OK, how 'bout a NEWS item?

The only think that I will notice on an upgrade will be
if debconf stops and asks me or I get an email to root.

[Jan De Luyck (jan-bugs)]

Package: alsa-base
Version: 1.0.7-2
Followup-For: Bug #287499

I just got bitten by this particular bug on a sarge system, after
spending nearly two hours digging throug every single aspect of the system
(except this). It should _definitely_ be marked more visible than just
the README.Debian file.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages alsa-base depends on:
ii alsa-utils 1.0.7-2 ALSA utilities
ii debconf 1.4.41 Debian configuration management sy
ii debianutils 2.11.2 Miscellaneous utilities specific t
ii lsof 4.73-1 List open files.
ii module-init-tools 3.1-rel-2 tools for managing Linux kernel mo

-- debconf information excluded

[Daniel T Chen (crimsun)]

--- Jan De Luyck <email address hidden> wrote:
> Package: alsa-base
> Version: 1.0.7-2
> Followup-For: Bug #287499
>
> I just got bitten by this particular bug on a sarge
> system, after
> spending nearly two hours digging throug every
> single aspect of the system
> (except this). It should _definitely_ be marked more
> visible than just
> the README.Debian file.

I agree with Thomas's proposal of a NEWS item. I
presume both you and Bernhard use apt-listchanges and apt-listbugs?

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[Bernhard Reiter (bernhard-intevation)]

On Tue, Jan 04, 2005 at 05:33:08PM -0800, Dan Chen wrote:
> --- Jan De Luyck <email address hidden> wrote:
> > Package: alsa-base
> > Version: 1.0.7-2
> > Followup-For: Bug #287499
> >
> > I just got bitten by this particular bug on a sarge
> > system, after
> > spending nearly two hours digging throug every
> > single aspect of the system
> > (except this). It should _definitely_ be marked more
> > visible than just
> > the README.Debian file.
>
> I agree with Thomas's proposal of a NEWS item. I
> presume both you and Bernhard use apt-listchanges and apt-listbugs?

So far I don't, thanks for the hint, I will check out those tools.
As for the NEWS item: When upgrading several hunderet packages,
I will not browse through the news of each of them.

The specific problem with this bug is,
that you are easily misslead where to search for the problem.
If I had known that the problem is within the alsa-base,
there would not have been so much wasted time.

Unless the average use behaves completely different then I do,
a NEWS item is not enough for this change.

 Bernhard

[Thomas Hood (jdthood-aglu)]

tags 287499 pending
thanks
--
Thomas Hood <email address hidden>

[Jan (debian-gepro)]

My box REQUIRES the module sb.ko to produce any usable sound hence I
certainly did not enjoy it could not be loaded after recent kernel update
in Hoary. Note the 'descriptive' error message:

me@ubuntu:~ $ modprobe sb
FATAL: Module off not found.
me@ubuntu:~ $

Dear ALSA maintainers: I know you are running a difficult mission. But please
keep you sledgehammers out of our systems. Linus still includes oss modules
into mainline kernel and does it on purpose. They are people using them !

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Tue, 28 Dec 2004 11:27:35 +0100
From: Bernhard Reiter <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: alsa-base: causing confusion on systems with oss

Package: alsa-base
Version: 1.0.7-2
Severity: normal

When I upgraded to alsa-base 1.0.7-2
the alias off lines in /etc/modutils/alsa-base caused me trouble by confusion.

Due to several reasons I have a bunch of kernels configured on my system
and some need to load oss sound modules. With them being "off"ed
it took me a long while to find out why it seems that my modutils were broken.
This problem is aggravated by modutils not reporting the situation
correctly when run verbosely.

I suspect that #286116 shows that several people have run into
similiar problems.

While blacklisting the oss modules in several ways seems to be the right
thing to do to avoid strange situations, I suggest that you bring
up a warning for system administrators when you install or upgrade alsa-base
with this blacklisting in place so that they are warned and know what
do to (undo the blacklisting in discover, modutils or hotplug)
before they start looking into modutils or other packages which they
suspect to be broken.

Best,
 Bernhard

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux 2.4.24-powerpc
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages alsa-base depends on:
ii alsa-utils 1.0.7-2 ALSA utilities
ii debconf 1.4.30.11 Debian configuration management sy
ii debianutils 2.8.4 Miscellaneous utilities specific t
ii lsof 4.71-1 List open files.
ii module-init-tools 3.1-rel-2 tools for managing Linux kernel mo
ii modutils 2.4.26-1.2 Linux module utilities

-- debconf information excluded

[Debian Bug Importer (debzilla)]

Message-Id: <1104440505.15291.66.camel@thanatos>
Date: Thu, 30 Dec 2004 22:01:45 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: Re: [Pkg-alsa-devel] Bug#287499: alsa-base: causing confusion on
 systems with oss

severity 287499 minor
thanks

I am rating this "minor" because it's a documentation issue, not
necessarily because I think it's a minor documentation issue. :)

On Tue, 2004-12-28 at 11:27 +0100, Bernhard Reiter wrote:
> While blacklisting the oss modules in several ways seems to be the right
> thing to do to avoid strange situations, I suggest that you bring
> up a warning for system administrators when you install or upgrade alsa-base
> with this blacklisting in place so that they are warned and know what
> do to (undo the blacklisting in discover, modutils or hotplug)
> before they start looking into modutils or other packages which they
> suspect to be broken.

The package description already mentions this issue. I could discuss it
further in README.Debian I suppose.

--
Thomas Hood <email address hidden>

[Debian Bug Importer (debzilla)]

Message-Id: <20041231001010.6D29410E151@localhost>
Date: Fri, 31 Dec 2004 01:10:10 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: tagging 287499

# Automatically generated email from bts, devscripts version 2.8.5
tags 287499 confirmed

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 2 Jan 2005 21:01:27 +0100
From: Bernhard Reiter <email address hidden>
To: Thomas Hood <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#287499: [Pkg-alsa-devel] Bug#287499: alsa-base: causing confusion on systems with
 oss

--ZoaI/ZTpAVc4A5k6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Dec 30, 2004 at 10:01:45PM +0100, Thomas Hood wrote:
> I am rating this "minor" because it's a documentation issue, not
> necessarily because I think it's a minor documentation issue. :)

Because it leads to modules not being loaded
and a hard to diagnose situation in other modulues only be upgrading,=20
I would say it is more then "minor" or documentation only:
It breaks real installations and eats up system administrator's time.

> On Tue, 2004-12-28 at 11:27 +0100, Bernhard Reiter wrote:
> > While blacklisting the oss modules in several ways seems to be the right
> > thing to do to avoid strange situations, I suggest that you bring
> > up a warning for system administrators when you install or upgrade alsa=
-base
> > with this blacklisting in place so that they are warned and know what
> > do to (undo the blacklisting in discover, modutils or hotplug)
> > before they start looking into modutils or other packages which they
> > suspect to be broken.
>=20
>=20
> The package description already mentions this issue. I could discuss it
> further in README.Debian I suppose.

On a regular upgrade, people will not inspect README.Debian
or the packages description of a package, this does not ease the problem.

 Bernhard

--ZoaI/ZTpAVc4A5k6
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFB2FMXh9ag3dpKERYRAoNKAJ9xOTsleUZ22sA5wVOr9BHfZ0R0tgCgoMoI
FV56/wzVlp+XQHDIH0AW7sA=
=TAxR
-----END PGP SIGNATURE-----

--ZoaI/ZTpAVc4A5k6--

[Debian Bug Importer (debzilla)]

Message-Id: <1104755432.10061.63.camel@thanatos>
Date: Mon, 03 Jan 2005 13:30:32 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: NEWS item, then?

> On a regular upgrade, people will not inspect README.Debian

OK, how 'bout a NEWS item?
--
Thomas Hood <email address hidden>

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 3 Jan 2005 15:46:29 +0100
From: Bernhard Reiter <email address hidden>
To: Thomas Hood <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#287499: NEWS item, then?

--WIyZ46R2i8wDzkSu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 03, 2005 at 01:30:32PM +0100, Thomas Hood wrote:
> > On a regular upgrade, people will not inspect README.Debian
>=20
> OK, how 'bout a NEWS item?

The only think that I will notice on an upgrade will be=20
if debconf stops and asks me or I get an email to root.

--WIyZ46R2i8wDzkSu
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQBB2VrFh9ag3dpKERYRAm9YAKDccilrqb+S4UtghXoTQE2i+eYrHwCgwkHi
gexbKmHFVsucHQeBJwI427w=
=BLjn
-----END PGP SIGNATURE-----

--WIyZ46R2i8wDzkSu--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 04 Jan 2005 14:57:46 +0100
From: Jan De Luyck <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: Bug#287499: alsa-base: causing confusion on systems with oss

Package: alsa-base
Version: 1.0.7-2
Followup-For: Bug #287499

I just got bitten by this particular bug on a sarge system, after
spending nearly two hours digging throug every single aspect of the system
(except this). It should _definitely_ be marked more visible than just
the README.Debian file.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages alsa-base depends on:
ii alsa-utils 1.0.7-2 ALSA utilities
ii debconf 1.4.41 Debian configuration management sy
ii debianutils 2.11.2 Miscellaneous utilities specific t
ii lsof 4.73-1 List open files.
ii module-init-tools 3.1-rel-2 tools for managing Linux kernel mo

-- debconf information excluded

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 4 Jan 2005 17:33:08 -0800 (PST)
From: Dan Chen <email address hidden>
To: <email address hidden>
Subject: Re: [Pkg-alsa-devel] Bug#287499: alsa-base: causing confusion on systems with oss

--- Jan De Luyck <email address hidden> wrote:
> Package: alsa-base
> Version: 1.0.7-2
> Followup-For: Bug #287499
>
> I just got bitten by this particular bug on a sarge
> system, after
> spending nearly two hours digging throug every
> single aspect of the system
> (except this). It should _definitely_ be marked more
> visible than just
> the README.Debian file.

I agree with Thomas's proposal of a NEWS item. I
presume both you and Bernhard use apt-listchanges and apt-listbugs?

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 5 Jan 2005 11:41:19 +0100
From: Bernhard Reiter <email address hidden>
To: Dan Chen <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#287499: [Pkg-alsa-devel] Bug#287499: alsa-base: causing confusion on systems with
 oss

--6v9BRtpmy+umdQlo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 04, 2005 at 05:33:08PM -0800, Dan Chen wrote:
> --- Jan De Luyck <email address hidden> wrote:
> > Package: alsa-base
> > Version: 1.0.7-2
> > Followup-For: Bug #287499
> >=20
> > I just got bitten by this particular bug on a sarge
> > system, after=20
> > spending nearly two hours digging throug every
> > single aspect of the system=20
> > (except this). It should _definitely_ be marked more
> > visible than just=20
> > the README.Debian file.
>=20
> I agree with Thomas's proposal of a NEWS item. I
> presume both you and Bernhard use apt-listchanges and apt-listbugs?

So far I don't, thanks for the hint, I will check out those tools.
As for the NEWS item: When upgrading several hunderet packages,
I will not browse through the news of each of them.

The specific problem with this bug is,=20
that you are easily misslead where to search for the problem.
If I had known that the problem is within the alsa-base,
there would not have been so much wasted time.

Unless the average use behaves completely different then I do,
a NEWS item is not enough for this change.

 Bernhard

--6v9BRtpmy+umdQlo
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQBB28RPh9ag3dpKERYRAvXAAKCM9+SuxUFLAVVoy9usQAXKJbYJMACdEW9/
Rr6FCFjCBH2YW02D0E4T66g=
=l1fK
-----END PGP SIGNATURE-----

--6v9BRtpmy+umdQlo--

[Debian Bug Importer (debzilla)]

Message-Id: <1104943108.10099.95.camel@thanatos>
Date: Wed, 05 Jan 2005 17:38:28 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: pending

tags 287499 pending
thanks
--
Thomas Hood <email address hidden>

[Jordi Mallach (jordi)]

Source: alsa-driver
Source-Version: 1.0.8-1

We believe that the bug you reported is fixed in the latest version of
alsa-driver, which is due to be installed in the Debian FTP archive:

alsa-base_1.0.8-1_all.deb
  to pool/main/a/alsa-driver/alsa-base_1.0.8-1_all.deb
alsa-driver_1.0.8-1.diff.gz
  to pool/main/a/alsa-driver/alsa-driver_1.0.8-1.diff.gz
alsa-driver_1.0.8-1.dsc
  to pool/main/a/alsa-driver/alsa-driver_1.0.8-1.dsc
alsa-driver_1.0.8.orig.tar.gz
  to pool/main/a/alsa-driver/alsa-driver_1.0.8.orig.tar.gz
alsa-headers_1.0.8-1_all.deb
  to pool/main/a/alsa-driver/alsa-headers_1.0.8-1_all.deb
alsa-source_1.0.8-1_all.deb
  to pool/main/a/alsa-driver/alsa-source_1.0.8-1_all.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jordi Mallach <email address hidden> (supplier of updated alsa-driver package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 16 Jan 2005 19:59:02 +0100
Source: alsa-driver
Binary: alsa-source alsa-headers alsa-base
Architecture: source all
Version: 1.0.8-1
Distribution: unstable
Urgency: low
Maintainer: Jordi Mallach <email address hidden>
Changed-By: Jordi Mallach <email address hidden>
Description:
 alsa-base - ALSA driver configuration files
 alsa-headers - transitional package that can be safely removed
 alsa-source - ALSA driver sources
Closes: 279325 281546 287010 287499 288423 288706 289533 290663
Changes:
 alsa-driver (1.0.8-1) unstable; urgency=low
 .
   * New upstream release
     - (Closes: #281546 "volume control crash on ICH6 + CMI9880")
     - (Closes: #287010 "Modules fail to build with Linux 2.6.9-pre3")
     - Create control device last rather than first
       (Closes: #279325 "mixer levels are not restored on system with udev")
   * Thomas Hood
     - patches:
       + 11_fix_context_of_vxpocket-patch remove (applied upstream)
       + 12_fix_context_of_pdaudiocf-patch remove (applied upstream)
       + 14_irqreturn_fix remove (fixed upstream)
       + 15_fix_configure_sparc_code remove (fixed upstream)
       + 18_core_init_index.dpatch add
         (Treat negative sound card index as index mask)
     - ALSA-card-list
       + Sync with upstream configure script, source files, INSTALL,
         doc/* and Documentation/ALSA-Configuration.txt files
       + Tag dummy and virtual cards as [UNREAL]
     - Start alsa at 12 rather than at 20, following Ubuntu's lead
     - Add /lib/alsa/modprobe-post-install to replace the script of the
       same name in /usr/lib/alsa/ in the alsa-utils package; modify
       /etc/mod(utils|probe.d)/alsa-base so that modprobe runs the
       former rather than the latter which isn't on the root filesystem
       (Closes: #288706)
     - Add /lib/alsa/dev...

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Sun, 16 Jan 2005 14:32:04 -0500
From: Jordi Mallach <email address hidden>
To: <email address hidden>
Subject: Bug#287499: fixed in alsa-driver 1.0.8-1

Source: alsa-driver
Source-Version: 1.0.8-1

We believe that the bug you reported is fixed in the latest version of
alsa-driver, which is due to be installed in the Debian FTP archive:

alsa-base_1.0.8-1_all.deb
  to pool/main/a/alsa-driver/alsa-base_1.0.8-1_all.deb
alsa-driver_1.0.8-1.diff.gz
  to pool/main/a/alsa-driver/alsa-driver_1.0.8-1.diff.gz
alsa-driver_1.0.8-1.dsc
  to pool/main/a/alsa-driver/alsa-driver_1.0.8-1.dsc
alsa-driver_1.0.8.orig.tar.gz
  to pool/main/a/alsa-driver/alsa-driver_1.0.8.orig.tar.gz
alsa-headers_1.0.8-1_all.deb
  to pool/main/a/alsa-driver/alsa-headers_1.0.8-1_all.deb
alsa-source_1.0.8-1_all.deb
  to pool/main/a/alsa-driver/alsa-source_1.0.8-1_all.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jordi Mallach <email address hidden> (supplier of updated alsa-driver package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 16 Jan 2005 19:59:02 +0100
Source: alsa-driver
Binary: alsa-source alsa-headers alsa-base
Architecture: source all
Version: 1.0.8-1
Distribution: unstable
Urgency: low
Maintainer: Jordi Mallach <email address hidden>
Changed-By: Jordi Mallach <email address hidden>
Description:
 alsa-base - ALSA driver configuration files
 alsa-headers - transitional package that can be safely removed
 alsa-source - ALSA driver sources
Closes: 279325 281546 287010 287499 288423 288706 289533 290663
Changes:
 alsa-driver (1.0.8-1) unstable; urgency=low
 .
   * New upstream release
     - (Closes: #281546 "volume control crash on ICH6 + CMI9880")
     - (Closes: #287010 "Modules fail to build with Linux 2.6.9-pre3")
     - Create control device last rather than first
       (Closes: #279325 "mixer levels are not restored on system with udev")
   * Thomas Hood
     - patches:
       + 11_fix_context_of_vxpocket-patch remove (applied upstream)
       + 12_fix_context_of_pdaudiocf-patch remove (applied upstream)
       + 14_irqreturn_fix remove (fixed upstream)
       + 15_fix_configure_sparc_code remove (fixed upstream)
       + 18_core_init_index.dpatch add
         (Treat negative sound card index as index mask)
     - ALSA-card-list
       + Sync with upstream configure script, source files, INSTALL,
         doc/* and Documentation/ALSA-Configuration.txt files
       + Tag dummy and virtual cards as [UNREAL]
     - Start alsa at 12 rather than at 20, following Ubuntu's lead
     - Add /lib/alsa/modprobe-post-install to replace the script of the
       same name in /usr/lib/alsa/ in the als...

[Mantas Kriaučiūnas (mantas)]

Hi,

I just got bitten by this alsa-base bug on a sarge system, after
spending about 3 hours digging throug /etc folder :(
(My friend's laptop has both - 2.4 and 2.6 kernels and most of the time he
uses 2.4 because suspend doesn't work on 2.6 :( )

On 16 Jan 2005, Jordi Mallach <email address hidden> wrote:
> Changes:
> alsa-driver (1.0.8-1) unstable; urgency=low
[..]
> - /etc/mod(utils|probe.d)/alsa-base
> + Don't alias OSS module names to "off". This was creating
> too much confusion. (Closes: #287499, #290663)
[..]

Thanks for removing these evil aliases - they couse only hard to find
problems on systems with 2.4 kernels :(
In future make at least a debconf prompt for changes like this, because
now after upgrade my friend got system with not working sound (sound
modules were specified in /etc/modules ) and it was very hard to find
why modprobe i810_audio doesn't work :(

The best solution in this case would be runtime autodetecting if alsa
modules for booting kernel exit and disable oss modules only in such
a case.

--
Good luck,
Mantas Kriaučiūnas <email address hidden> Jabber ID: <email address hidden>
Public organization "Open Source for Lithuania" - www.akl.lt

[Matt Zimmerman (mdz)]

alsa-driver | 1.0.8-1 | http://archive.ubuntu.com hoary/main Sources

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 19 Jan 2005 20:29:58 +0200
From: "AKL. Mantas Kriauciunas" <email address hidden>
To: <email address hidden>
Subject: Thanks for improving the usability of alsa-base debian package

Hi,

I just got bitten by this alsa-base bug on a sarge system, after
spending about 3 hours digging throug /etc folder :(
(My friend's laptop has both - 2.4 and 2.6 kernels and most of the time h=
e
uses 2.4 because suspend doesn't work on 2.6 :( )

On 16 Jan 2005, Jordi Mallach <email address hidden> wrote:
> Changes:
> alsa-driver (1.0.8-1) unstable; urgency=3Dlow
[..]
> - /etc/mod(utils|probe.d)/alsa-base
> + Don't alias OSS module names to "off". This was creating
> too much confusion. (Closes: #287499, #290663)
[..] =20

Thanks for removing these evil aliases - they couse only hard to find
problems on systems with 2.4 kernels :(
In future make at least a debconf prompt for changes like this, because
now after upgrade my friend got system with not working sound (sound
modules were specified in /etc/modules ) and it was very hard to find
why modprobe i810_audio doesn't work :(

The best solution in this case would be runtime autodetecting if alsa=20
modules for booting kernel exit and disable oss modules only in such
a case.

--=20
Good luck,
Mantas Kriau=C4=8Di=C5=ABnas <email address hidden> Jabber ID: <email address hidden>=
t
Public organization "Open Source for Lithuania" - www.akl.lt