Difference between revisions of "Xonar EEPROM Failure"
(→Xonar EEPROM Failure) |
(→Booting Linux) |
||
Line 104: | Line 104: | ||
===Booting Linux=== | ===Booting Linux=== | ||
− | The Linux Xonar driver has the EEPROM restoring tool integrated since kernel 2.6.30 (which was released June 2009).<br>Just boot your installed Linux, or any recent Linux live CD. | + | The Linux Xonar driver has a simple version of the EEPROM restoring tool integrated since kernel 2.6.30 (which was released June 2009).<br>Just boot your installed Linux, or any recent Linux live CD.<br>However, this simple version is not able to correct all possible errors. |
===Feedback=== | ===Feedback=== |
Revision as of 14:05, 19 June 2013
Contents |
Xonar EEPROM Failure
Sometimes, Xonar PCI/PCI-E cards randomly fail to be recognized.
The driver refused to load or to install, and in Device Manager, the card is shown as an unknown sound card or as "C-Media Oxygen audio device". Putting the card into another slot or another computer does not help.
This happens when the EEPROM on the card gets overwritten.
(This EEPROM stores the PCI subsystem vendor and product IDs;
when it gets overwritten, the main chip cannot read the subsystem IDs
and uses a default ID (13F6:8788) which is not recognized by the Xonar driver.)
To reliably detect whether the EEPROM was overwritten, go into Device Manager, show the properties page of the device, go to the "Details" tab, and select the property "Hardware IDs", and look at the values after "SUBSYS_":
PCI\VEN_13F6&DEV_8788&SUBSYS_82691043 | OK (Xonar D2) |
PCI\VEN_13F6&DEV_8788&SUBSYS_82751043 | OK (Xonar DX) |
PCI\VEN_13F6&DEV_8788&SUBSYS_82B71043 | OK (Xonar D2X) |
PCI\VEN_13F6&DEV_8788&SUBSYS_83141043 | OK (Xonar HDAV1.3) |
PCI\VEN_13F6&DEV_8788&SUBSYS_83271043 | OK (Xonar DX) |
PCI\VEN_13F6&DEV_8788&SUBSYS_834F1043 | OK (Xonar D1) |
PCI\VEN_13F6&DEV_8788&SUBSYS_835C1043 | OK (Xonar Essence STX) |
PCI\VEN_13F6&DEV_8788&SUBSYS_835D1043 | OK (Xonar Essence ST) |
PCI\VEN_13F6&DEV_8788&SUBSYS_835E1043 | OK (Xonar HDAV1.3 Slim) |
PCI\VEN_13F6&DEV_8788&SUBSYS_838E1043 | OK (Xonar DS) |
PCI\VEN_13F6&DEV_8788&SUBSYS_84281043 | OK (Xonar Xense) |
PCI\VEN_13F6&DEV_8788&SUBSYS_84671043 | OK (Xonar DG) |
PCI\VEN_13F6&DEV_8788&SUBSYS_85211043 | OK (Xonar DGX) |
PCI\VEN_13F6&DEV_8788&SUBSYS_85221043 | OK (Xonar DSX) |
PCI\VEN_13F6&DEV_8788&SUBSYS_878813F6 PCI\VEN_13F6&DEV_8788&SUBSYS_434D1043 |
overwritten EEPROM |
Causes
The exact cause is unknown.
It seems that the problem occurs only with certain computers or motherboards,
and after booting from a CD (i.e., (re)installation of an operating system, or using a live CD).
Restoring the EEPROM
I have written a tool that can restore the original contents of the EEPROM.
It needs direct access to the hardware, therefore, it can not be run inside Windows.
In DOS
If you have a working DOS, you can use this method. (This tool is run in the same way as Asus' xee01.bat.)
- Download restoree.exe;
- boot DOS;
(this works only with a real DOS such as MS-DOS or DR-DOS or FreeDOS; an emulated DOS such as the DOS box of Windows or the DOS in an emulated computer (e.g. VMWare) will not work) - run restoree.exe.
(source code: restoree.c)
Booting from a floppy
- Download this floppy image: floppy.img (1.44 MB);
- write it to a floppy with rawrite.exe (which you can get somewhere on the Internet);
- boot from the floppy.
Booting from a CD
- Download this ISO file: restore_eeprom.iso (1.8 MB);
- burn it to a blank CD-R;
- boot from the CD.
Booting from a USB memory stick/flash disk
- Make a bootable USB flash disk (see this description), but do not put the xee01 files on the disk;
- download restoree.exe and put in on the flash disk;
- boot from the flash disk and run restoree.exe.
Booting Linux
The Linux Xonar driver has a simple version of the EEPROM restoring tool integrated since kernel 2.6.30 (which was released June 2009).
Just boot your installed Linux, or any recent Linux live CD.
However, this simple version is not able to correct all possible errors.
Feedback
Warranty
none
Bug Reports
Many users have reported this problem:
http://vip.asus.com/forum/view.aspx?board_id=21&id=20080308014957187
http://vip.asus.com/forum/view.aspx?board_id=21&id=20080815123512921
http://vip.asus.com/forum/view.aspx?board_id=21&id=20081109201810093
http://vip.asus.com/forum/view.aspx?board_id=21&id=20090108020749752
http://vip.asus.com/forum/view.aspx?board_id=21&id=20090211084749940
http://vip.asus.com/forum/view.aspx?board_id=21&id=20090212184022002
http://vip.asus.com/forum/view.aspx?board_id=21&id=20090417024503409
http://vip.asus.com/forum/view.aspx?board_id=21&id=20090424193309127
http://vip.asus.com/forum/view.aspx?board_id=21&id=20090719054139406
http://vip.asus.com/forum/view.aspx?board_id=21&id=20100510174004218
http://vip.asus.com/forum/view.aspx?board_id=21&id=20100828085839182
http://vip.asus.com/forum/view.aspx?board_id=21&id=20110120170223383
http://vip.asus.com/forum/view.aspx?board_id=21&id=20110318045748367
http://vip.asus.com/forum/view.aspx?board_id=21&id=20120505102639207
http://vip.asus.com/forum/view.aspx?board_id=21&id=20130128083647397
http://vip.asus.com/forum/view.aspx?board_id=21&id=20130506122138947
http://bugzilla.novell.com/show_bug.cgi?id=462365
(and private e-mail)
