Difference between revisions of "Xonar EEPROM Failure"

From AlsaProject
Jump to: navigation, search
m (grammar)
(update link for creating USB boot drive)
Line 98: Line 98:
===Booting from a USB memory stick/flash disk===
===Booting from a USB memory stick/flash disk===
# Make a bootable USB flash disk (see [http://vip.asus.com/forum/view.aspx?id=20081009200304311&board_id=21&model=Xonar+DX&SLanguage=en-us&page=1#20081011060714859 this description]), but do not put the xee01 files on the disk;
# Make a bootable USB flash disk (see [http://www.sevenforums.com/tutorials/46707-ms-dos-bootable-flash-drive-create.html this description]), but do not put the xee01 files on the disk;
# download [http://www.alsa-project.org/~clemens/restoree.exe restoree.exe] and put in on the flash disk;
# download [http://www.alsa-project.org/~clemens/restoree.exe restoree.exe] and put in on the flash disk;
# boot from the flash disk and run restoree.exe.
# boot from the flash disk and run restoree.exe.

Revision as of 16:56, 6 January 2013


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 overwritten EEPROM


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.


If you have a working DOS, you can use this method. (This tool is run in the same way as Asus' xee01.bat.)

  1. Download restoree.exe;
  2. 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)
  3. run restoree.exe.

(source code: restoree.c)

Booting from a floppy

  1. Download this floppy image: floppy.img (1.44 MB);
  2. write it to a floppy with rawrite.exe (which you can get somewhere on the Internet);
  3. boot from the floppy.

Booting from a CD

  1. Download this ISO file: restore_eeprom.iso (1.8 MB);
  2. burn it to a blank CD-R;
  3. boot from the CD.

Booting from a USB memory stick/flash disk

  1. Make a bootable USB flash disk (see this description), but do not put the xee01 files on the disk;
  2. download restoree.exe and put in on the flash disk;
  3. boot from the flash disk and run restoree.exe.

Booting Linux

The Linux Xonar driver has 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.





Bug Reports

Many users have reported this problem:

(and private e-mail)

Custom Search
Personal tools