https://bugzilla.novell.com/show_bug.cgi?id=462365 User holotropium@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c1 --- Comment #1 from Babak Zadeh 2008-12-24 04:48:17 MST --- My hardware is: Motherboard: Asus P5N-D CPU: Intel Core 2 Quad Q6600 Memory: 4 x 2GB OCZ DDR2-800 Graphiccard: Asus EN8600GTS 256MB HDD: 1x IDE (boot HDD) Seagate 120GB 4x SATA WD 250GB 7200 rpm 16mb cache in RAID 0 array -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User holotropium@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c3 Babak Zadeh changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Blocker Priority|P5 - None |P2 - High --- Comment #3 from Babak Zadeh 2008-12-24 06:46:09 MST --- MoBo BIOS version is 0302. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User stbinner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c4 Stephan Binner changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Critical Priority|P2 - High |P5 - None --- Comment #4 from Stephan Binner 2008-12-28 01:43:18 MST --- Please read http://en.opensuse.org/Bugs/Definitions#Setting_and_Changing_Priorities_and_... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User holotropium@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c6 --- Comment #6 from Babak Zadeh 2009-01-05 03:09:22 MST --- sorry for answering that late. i was ill last week and couldn't do anything. i've read the link above. sorry for that mistake. i will never do it again. i'm not sure the card is damaged. i think the firmware is been changed. windows recognizes an audio card but not the asus xonar d2. the original driver tells to install an asus xonar d2 (can't find any). i've shut down the pc, plugged off the power cable, waited a minute, used the power button 2 times, waited some minutes, plugged in the power cable again, startet the pc. same thing in another slot and other pc. the dealer didn't tell anything about it. they gave the card to asus and asus changed it for a new one. i think it's reproducable. the problem appeared directly after installing opensuse 11.0 x86_64 for 2 times. a've told the dealer about this thing but there's no answer cause i didn't send in the hardware yet. but i'll do today or tomorrow. asus just sais that the audio card officially isn't released for linux. i asked for a firmware tool but they don't offer any support. seems like they don't care about it. i'm not angry about it since i can get a new hardware. but i want to use opensuse somehow without to change anything to the audio card. kind regards holotropium -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User holotropium@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c8 --- Comment #8 from Babak Zadeh 2009-01-05 14:11:59 MST ---

is that really all what they tell about this?

i can post the message from asus here. but it is in german. if i can do anything let me know. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User holotropium@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c10 --- Comment #10 from Babak Zadeh 2009-01-07 07:13:41 MST ---

Xonar D2 should have been supported for long time, and I'm pretty surprised by this kind of bug. I'll forward the bug to the author. for sure. thanks!

BTW, stopping the auto-probing is easy. Just add a line blacklist snd_virtuoso to a module config file. can i do this before the setup? or as a parameter?

It'd be of course helpful for us if you can try the latest driver version it would not be useful yet. cause i can't test if the hardware works fine in windows after that, cause the hardware has the failure now and i still have no way to restore the damaged hardware by myself. i sent it to the vendor anyway. also i tried other bios versions. it didn't help. but i did not re-initialize the BIOS. perhaps this'd be a temporary solution. BTW i don't need the card under linux. i just use it for cubase (the only reason why i'll still be using windows in the next years). i can use my old audigy 2 zs for cubase for a while, till the bug is cleared.

-- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User holotropium@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c12 --- Comment #12 from Babak Zadeh 2009-01-07 12:35:36 MST --- i can boot in the live system after rebooting the first time and modify the module config file and boot in to the installed system again. but are you sure that's not too late? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User holotropium@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c14 --- Comment #14 from Babak Zadeh 2009-01-08 09:54:57 MST --- do you mean when i boot into the setup-dvd and choose "repair system"? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User holotropium@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c16 --- Comment #16 from Babak Zadeh 2009-01-08 10:34:55 MST --- thanks for the explaination. i think this will be easy. the bios doesn't have a pci setup. that's in all versions i saw. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User clemens@ladisch.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c18 Clemens Ladisch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clemens@ladisch.de --- Comment #18 from Clemens Ladisch 2009-01-12 05:38:07 MST --- (I'm the driver author; sorry for the delay)

windows recognizes an audio card but not the asus xonar d2.

This would indicate that some PCI device ID of the card has changed. Please show, if you're in Linux, the output of "lspci -v", or in Windows, in the Device Manager, in the card's properties, on the page "Details", the value of "Hardware IDs". -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User clemens@ladisch.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c20 --- Comment #20 from Clemens Ladisch 2009-01-12 11:31:58 MST ---

i can post the original id.

Well, I already know that one. :-) Did this card ever work in Linux? (I guess you didn't try ...) It seems you have the same problem as this guy: http://vip.asus.com/forum/view.aspx?board_id=21&id=20080815123512921 Since you are the only Linux user where this problem occurs, and since it apparently also happens without Linux, I'm not quite sure that the OpenSUSE install itself caused the damage. How long did your first card and your replacement card work in Windows? How often did you (re)boot your computer in this time?

what about asus? will they do anything?

They cannot do anything, except replace the card. The PCI subdevice ID is stored in an EEPROM. Neither the Windows driver nor the Linux driver ever try to access it, so I don't think that it got reprogrammed by accident. Probably the EEPROM chip itself or its connection to the main chip somehow broke. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User clemens@ladisch.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c22 --- Comment #22 from Clemens Ladisch 2009-01-13 07:39:59 MST ---

is there a way to correct the eeprom?

If the data in the EEPROM were somehow overwritten with wrong values, it would be possible to write the original IDs back. However, the subdevice IDs of "true"'s card are the values used by the chip when it cannot read from the EEPROM at all. In other words, it's not the contents of the EEPROM that are wrong, the EEPROM chip itself is broken. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User holotropium@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c24 --- Comment #24 from Babak Zadeh 2009-01-15 02:56:53 MST --- i'll try to get a different card from the vendor. if the vendor isn't willing to change the card for a different one i'll be depending on another solution. in that case this would be gret. but i'm absolutely a beginner in c++ and for me it's impossible to write such a tool. i'd have to wait till someone other does this. and of course till the patch is integrated in the kernel. thanks for the research!! -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User tiwai@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c26 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |clemens@ladisch.de --- Comment #26 from Takashi Iwai 2009-01-15 03:32:37 MST --- Thanks for tracking this! 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...

-- 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.

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 changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|clemens@ladisch.de | --- Comment #28 from Clemens Ladisch 2009-01-15 04:55:49 MST ---

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.

https://bugzilla.novell.com/show_bug.cgi?id=462365 User clemens@ladisch.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462365#c30 --- Comment #30 from Clemens Ladisch 2009-01-16 02:41:13 MST --- For the EEPROM restoring tool, see http://www.alsa-project.org/main/index.php/Xonar_D2(X)_EEPROM_Failure -- 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.