Hi Michael, On Thu, 27 Jun 2013 21:22:25 +0200, "Michael Hatzold" <m.hatz...@web.de> wrote: > Am 27.06.2013, 20:21 Uhr, schrieb Stephen Kitt <sk...@debian.org>: > > Could you possibly try the following? > > * re-install oss-compat 3 > > * reboot (with the timeout) > > * run > > sudo udevadm --debug trigger --verbose > > to re-attempt to load the sound modules and trace what is attempted > > As root in a VT I did run: > > "udevadm --debug trigger --verbose" > > Output in attachement. If it's not what you wanted pls let me know what to > do exactly.
Thanks, that is what I wanted although it's not enough to figure out the
problem - but Sven provided the missing info (thanks!).
If you don't mind, could you try the following workarounds?
The first is to drop the last softdep from oss-compat.conf (v3):
softdep snd-pcm post: snd-pcm-oss
softdep snd-mixer post: snd-mixer-oss
That's the workaround provided by Sven, so it should work just fine.
The second is to add a variant of the last softdep:
softdep snd-pcm post: snd-pcm-oss
softdep snd-mixer post: snd-mixer-oss
softdep snd-seq post: snd-seq-oss
This will help determine whether the initialisation lock-up is related to
loading snd-seq-midi... (Incidentally, the Debian kernels don't ship
snd-seq-oss.)
Thanks,
Stephen
signature.asc
Description: PGP signature
