https://bugzilla.novell.com/show_bug.cgi?id=327157#c5
--- Comment #5 from Michael Matz 2007-09-21 10:55:06 MST ---
Yast logs from what? The problem is already perfectly clear. Our current
system doesn't allow sound devices which aren't configured with yast. As soon
as one device is configure with yast all devices must be. That is because
yast assign indexes to the configured devices. But as udev loads drivers for
_all_ devices (even the unconfigured ones) at which points the indexes
actually are assigned (when no other is given explicitely, i.e. for the
unconfigured devices), the explicit index (for the configured yast devices)
might not be free anymore leading to this bug (driver refusing to register
the device). So with the current system we can't allow yast to leave some
sound devices "unconfigured".
FWIW this situation can occur quite easily: for me it is simply the mainboard
having built-in sound, but me also using the SBLive! PCI card. As soon
as I just configure the mainboard device too (with simple quick setup in yast)
it will also get assigned an index, and hence the confusion doesn't arise,
so everything works.
I'm not sure what to suggest. Probably that the yast sound module simply
forcefully configures every detected sound device (in the sense of at least
assigning an index to each of them in /etc/modprobe.d/sound ).
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.