https://bugzilla.novell.com/show_bug.cgi?id=462365
User clemens@ladisch.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=462365#c28
Clemens Ladisch
BTW, how is the impact of this bug? That is, what action does trigger? From your explanation, even changing the mixer value may cause the problem...
Yes. DAC registers are written when the driver is initialized, when volume/mute mixer values are changed, and when a stream is opened (hw_params). The EEPROM chip does need a signal on its chip select line (which is _not_ shared) to trigger a write command, but it seems that sometimes, such a signal does occur by itself, either due to noise or because of some other, unknown reason. Apparently, this is more likely to happpen on certain computers. When the EEPROM thinks that it has been selected, every complete DAC write command is also interpreted as one 0 bit for the EEPROM; a complete EEPROM write command needs about 24 bits (1 bit command, 7(?) bits address, 16 bits data). According to comment #6, the Linux installation itself (loading the driver, setting mixer values, probably a test sound) was enough to trigger it. -- 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.