https://bugzilla.novell.com/show_bug.cgi?id=462365
User clemens@ladisch.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=462365#c23
--- Comment #23 from Clemens Ladisch 2009-01-15 02:21:15 MST ---
Okay, my last comment is wrong. After some digging in the datasheet, I found a
likely cause of the problem.
The pin used for writing registers in the fourth DAC chip is shared with the
EEPROM chip; if there is even one bit of noise on a certain other pin and if
the driver does lots of register writes to the DAC, the EEPROM can get
overwritten. Since the first word of the EEPROM contains a checksum, the main
chip then thinks that the entire EEPROM is invalid.
The Linux driver does many more DAC register writes than the Windows driver, so
it's more likely that this happens when using Linux.
I have a patch for the driver so that DAC register writes are avoided; this
patch is not yet in any publicly available kernel.
is there a way to correct the eeprom?
Yes, it is possible to write a tool that writes the original values back into
the EEPROM.
--
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.