via epia cn1000eg flash failed.

[Yuri Schaeffer]

Hi,
I tried to flash to the latest BIOS for my board but it failed at
verifying. The backup I made a few minutes earlier has the same problem.
 I did not (dare to) reboot the system. Attached flashrom output and
lspci -vvnnxxx.

board: via epia cn 1000eg
southbr: VT8237R Plus (according to the specs)
flashrom: v0.9.1-r750
bios image: 1.14, 2009/07/31,
http://www.via.com.tw/servlet/downloadSvl?id=400&download_file_id=4942

Currently I have no idea how to repair my system. Folks at #flashrom
pointed me to here.

--
yuri

$ sudo ./flashrom -Vw ../I1300114.BIN
flashrom v0.9.1-r750
No coreboot table found.
Found chipset "VIA VT8237", enabling flash write... OK.
This chipset supports the following protocols: Non-SPI.
Disabling flash write protection for board "VIA EPIA-CN"... OK.
Calibrating delay loop... 263M loops per second, 100 myus = 199 us. OK.
Probing for AMD Am29F010A/B, 128 KB: probe_29f040b: id1 0xff, id2 0xff
Probing for AMD Am29F002(N)BB, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for AMD Am29F002(N)BT, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff
Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0xea, id2 0x56
Probing for AMD Am29F080B, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xea, id2 0x56
Probing for AMD Am29LV081B, 1024 KB: probe_29f040b: id1 0xff, id2 0xff
Probing for ASD AE49F2008, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0x9d, id2 0x6e
Probing for Atmel AT25DF021, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT25DF041A, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT25DF081, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT25DF161, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT25DF321, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT25DF321A, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT25DF641, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT25F512B, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT25FS010, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT25FS040, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT26DF041, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT26DF081A, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT26DF161, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT26DF161A, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT26F004, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT29C512, 64 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Atmel AT29C010A, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Atmel AT45CS1282, 16896 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT45DB011D, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT45DB021D, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT45DB041D, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT45DB081D, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT45DB161D, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT45DB321C, 4224 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT45DB321D, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT45DB642D, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Atmel AT49BV512, 64 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Atmel AT49F002(N), 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for AMIC A25L40P, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0x9d, id2 0x6e
Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0x9d, id2 0x6e
Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0xea, id2 0x56
Probing for AMIC A49LF040A, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for EMST F49B002UA, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Eon EN25B05, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25B10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25B20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25B40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25B80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25B16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25B32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25B64, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25D16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25F05, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25F10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25F20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25F40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25F80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25F16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Eon EN25F32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for EON EN29F002(A)(N)B, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Fujitsu MBM29F004BC, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Fujitsu MBM29F004TC, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0xea, id2 0x00
Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0xea, id2 0x00
Probing for Intel 28F001BX-B, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Intel 28F001BX-T, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0xea, id2 0x56
Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0xff, id2 0xff
Probing for Macronix MX25L512, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Macronix MX25L1005, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Macronix MX25L2005, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Macronix MX25L4005, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Macronix MX25L8005, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Macronix MX25L1605, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Macronix MX25L1635D, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Macronix MX25L3205, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Macronix MX25L3235D, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Macronix MX25L6405, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Macronix MX25L12805, 16384 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Macronix MX29F001B, 128 KB: probe_29f002: id1 0x9d, id2 0x6e
Probing for Macronix MX29F001T, 128 KB: probe_29f002: id1 0x9d, id2 0x6e
Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0x9d, id2 0x6e
Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0x9d, id2 0x6e
Probing for Macronix MX29LV040, 512 KB: probe_29f002: id1 0x9d, id2 0x6e
Probing for Numonyx M25PE10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Numonyx M25PE20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Numonyx M25PE40, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Numonyx M25PE80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Numonyx M25PE16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for PMC Pm25LV010, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for PMC Pm25LV016B, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for PMC Pm25LV020, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for PMC Pm25LV040, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for PMC Pm25LV080B, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for PMC Pm25LV512, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for PMC Pm29F0002T, 256 KB: probe_29f040b: id1 0x81, id2 0xf6
Probing for PMC Pm29F0002B, 256 KB: probe_29f040b: id1 0x81, id2 0xf6
Probing for PMC Pm39LV010, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for PMC Pm49FL002, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Found chip "PMC Pm49FL004" (512 KB, LPC,FWH) at physical address 0xfff80000.
Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0xff, id2 0xff
Probing for Spansion S25FL016A, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for SST SST25VF016B, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for SST SST25VF032B, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for SST SST25VF040B, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for SST SST25VF040.REMS, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for SST SST25VF040B.REMS, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for SST SST25VF080B, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0xea, id2 0x56
Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST39VF080, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0xea, id2 0x56
Probing for SST SST49LF008A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0xff, id2 0xff
Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff
Probing for SST SST49LF020, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SST SST49LF080A, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff
Probing for ST M25P05-A, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for ST M25P05.RES, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for ST M25P10-A, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for ST M25P10.RES, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for ST M25P20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for ST M25P40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for ST M25P40-old, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for ST M25P80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for ST M25P16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for ST M25P32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for ST M25P64, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for ST M25P128, 16384 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for ST M29F002B, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0xea, id2 0x56
Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0xea, id2 0x00
Probing for ST M29W010B, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for ST M29W040B, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for ST M50FLW040A, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0x9d, id2 0x6e
Probing for ST M50FLW040B, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0x9d, id2 0x6e
Probing for ST M50FLW080A, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW080B, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW002, 256 KB: probe_49lfxxxc: id1 0x81, id2 0xf6
Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff
Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0xea, id2 0x56
Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0xff, id2 0xff
Probing for ST M50LPW116, 2048 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SyncMOS S29C31004T, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for TI TMS29F002RB, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for TI TMS29F002RT, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Winbond W25x10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Winbond W25x20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Winbond W25x40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Winbond W25x80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Winbond W25x16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Winbond W29C011, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Winbond W29EE011, 128 KB: Probing disabled for Winbond W29EE011 because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29EE011' if you have a board with this chip.
Probing for Winbond W39V040A, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Winbond W39V040C, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0x9d, id2 0x6e
Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W49F002U, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
Probing for Winbond W39V080FA, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V080FA (dual mode), 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0x9d, id2 0x6e
Probing for Atmel unknown Atmel SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for EON unknown EON SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for Macronix unknown Macronix SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for PMC unknown PMC SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for SST unknown SST SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Probing for ST unknown ST SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible.
Flash image seems to be a legacy BIOS. Disabling checks.
Writing flash chip... Programming page: 0007 at address: 0x00070000
COMPLETE.
Verifying flash... VERIFY FAILED at 0x00005555! Expected=0xff, Read=0xaa, failed byte count from 0x00000000-0x0007ffff: 0x16fd
Your flash chip is in an unknown state.
Get help on IRC at irc.freenode.net (channel #flashrom) or
mail [e-mail]!
-------------------------------------------------------------------------------
DO NOT REBOOT OR POWEROFF!

00:00.0 Host bridge [0600]: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge [1106:0314]
	Subsystem: VIA Technologies, Inc. Device [1106:aa08]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR+ INTx-
	Latency: 8
	Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
	Capabilities: [80] AGP version 3.5
		Status: RQ=8 Iso- ArqSz=0 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3+ Rate=x4,x8
		Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: agpgart-via
	Kernel modules: via-agp
00: 06 11 14 03 06 00 30 a2 00 00 00 06 00 08 80 00
10: 08 00 00 e0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 08 aa
30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00
40: c7 db 10 db 24 00 00 00 00 00 1f c4 00 04 00 01
50: 01 00 02 00 00 00 00 00 08 00 01 80 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 02 50 35 00 0b 0a 00 07 00 00 00 00 00 00 00 00
90: 80 01 00 00 20 0f 01 00 00 00 ca 32 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 03 00 00 00 00 00 00 21 d2 00 8c
c0: 02 02 80 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:00.1 Host bridge [0600]: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge [1106:1314]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
00: 06 11 14 13 06 00 00 02 00 00 00 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:00.2 Host bridge [0600]: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge [1106:2314]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
00: 06 11 14 23 06 00 00 02 00 00 00 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 88 7a 6f 88 1e 16 01 99 00 64 00 00 00 b2 88 c7
60: ff ff 0f ff ff 0f ff 30 00 00 00 00 00 00 00 00
70: 11 11 11 11 35 28 74 00 0a aa 24 aa 00 6d 00 00
80: 1b 0a 0a 0a 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:00.3 Host bridge [0600]: VIA Technologies, Inc. PT890 Host Bridge [1106:3208]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Kernel modules: via-agp
00: 06 11 08 32 06 00 00 02 00 00 00 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 08 10 00 00 00 00 00 00 00 08 00 00 00 00 00 00
50: 20 00 11 1f 89 00 c5 67 00 00 00 00 00 00 00 00
60: 03 94 7a 00 88 d9 80 00 00 83 86 10 c8 c0 89 41
70: 00 06 00 06 06 06 01 9f 87 87 00 20 00 00 00 00
80: aa 0f 00 e0 00 40 29 00 40 00 00 00 00 00 00 00
90: 04 04 06 07 00 00 00 12 33 00 00 00 00 0f 00 00
a0: 41 ef 44 00 10 00 00 00 00 00 00 00 00 00 00 00
b0: 61 aa aa 5a 0f 00 00 00 08 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: aa 79 78 01 80 8a aa 00 01 0a 80 00 50 be 00 00
e0: ee 00 ac 00 66 00 33 00 86 00 00 00 11 10 00 10
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:00.4 Host bridge [0600]: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge [1106:4314]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
00: 06 11 14 43 06 00 00 02 00 00 00 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 80 20 fb ff fe f0 77 80 00 00 00 00 00 00 00 00
b0: 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 08 08 00 00 08 08 00 00 00 09 00 00 00 00 00 00
e0: 22 22 00 00 00 00 00 00 00 03 01 00 80 07 29 00
f0: 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00

00:00.7 Host bridge [0600]: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge [1106:7314]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
00: 06 11 14 73 06 00 00 02 00 00 00 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
40: 14 19 88 80 82 44 00 04 13 b9 88 80 82 44 00 01
50: 00 00 00 00 00 00 01 40 08 00 01 80 00 00 00 00
60: 00 aa 0f e0 00 00 00 00 00 00 00 00 00 00 00 00
70: c2 c8 ee 01 20 0f d0 6e 01 00 00 00 00 00 02 10
80: 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00
90: 00 00 00 00 20 0f 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 05 01 00 a3 55 22 22 44 45 23 33 11 00 00 00 00
c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 40 29 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237/VX700 PCI Bridge [1106:b198]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000b000-0000bfff
	Memory behind bridge: fb000000-fcffffff
	Prefetchable memory behind bridge: f4000000-f7ffffff
	Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR+ <PERR+
	BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel modules: shpchp
00: 06 11 98 b1 07 00 30 02 00 00 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 00 b0 b0 20 e2
20: 00 fb f0 fc 00 f4 f0 f7 00 00 00 00 00 00 00 00
30: 00 00 00 00 70 00 00 00 00 00 00 00 00 00 0c 00
40: 83 43 62 44 34 72 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 01 00 02 02 00 00 00 00 00 00 00 00 00 00 00 00
80: 0e 00 35 00 0b 0a 00 07 00 00 00 00 00 00 00 00
90: 80 00 00 00 00 0f 01 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 80 63 08 00 00 00 00 00 00 00 1f c4 00 04 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:0f.0 IDE interface [0101]: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller [1106:3149] (rev 80) (prog-if 8f [Master SecP SecO PriP PriO])
	Subsystem: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller [1106:3149]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32
	Interrupt: pin B routed to IRQ 11
	Region 0: I/O ports at fc00 [size=8]
	Region 1: I/O ports at f800 [size=4]
	Region 2: I/O ports at f400 [size=8]
	Region 3: I/O ports at f000 [size=4]
	Region 4: I/O ports at ec00 [size=16]
	Region 5: I/O ports at e800 [size=256]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: sata_via
	Kernel modules: sata_via
00: 06 11 49 31 07 00 90 02 80 8f 01 01 00 20 80 00
10: 01 fc 00 00 01 f8 00 00 01 f4 00 00 01 f0 00 00
20: 01 ec 00 00 01 e8 00 00 00 00 00 00 06 11 49 31
30: 00 00 00 00 c0 00 00 00 00 00 00 00 0b 02 00 00
40: 43 03 f1 44 0e af 00 00 00 82 45 03 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 10 10 00 05 00 10 00
60: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 01 00 01 00 10 00 00 00
80: 00 00 00 00 00 00 00 00 00 10 91 36 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 80 02 49 31 06 11 49 31 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:0f.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06) (prog-if 8a [Master SecP PriP])
	Subsystem: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32
	Interrupt: pin A routed to IRQ 0
	Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
	Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
	Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
	Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
	Region 4: I/O ports at e400 [size=16]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: pata_via
00: 06 11 71 05 07 00 90 02 06 8a 01 01 00 20 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 e4 00 00 00 00 00 00 00 00 00 00 06 11 71 05
30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 01 00 00
40: 4b f2 09 05 18 8c c0 00 99 99 99 99 ff 00 a8 a8
50: 07 07 07 07 0c 00 00 00 a8 a8 a8 a8 00 00 00 00
60: 00 02 00 00 00 00 00 00 00 02 00 00 00 00 00 00
70: 82 01 00 00 00 00 00 00 82 01 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 06 00 71 05 06 11 71 05 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 09 00 00 00 00 00 00 00 00 00

00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 81)
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 10
	Region 4: I/O ports at e000 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: uhci_hcd
00: 06 11 38 30 07 00 10 02 81 00 03 0c 08 20 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 e0 00 00 00 00 00 00 00 00 00 00 06 11 38 30
30: 00 00 00 00 80 00 00 00 00 00 00 00 0a 01 00 00
40: 40 12 03 00 00 00 00 00 00 0b a0 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 01 00 c2 ff 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00

00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 81)
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 10
	Region 4: I/O ports at dc00 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: uhci_hcd
00: 06 11 38 30 07 00 10 02 81 00 03 0c 08 20 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 dc 00 00 00 00 00 00 00 00 00 00 06 11 38 30
30: 00 00 00 00 80 00 00 00 00 00 00 00 0a 01 00 00
40: 40 12 03 00 00 00 00 00 00 0b a0 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 01 00 c2 ff 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00

00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 81)
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin B routed to IRQ 11
	Region 4: I/O ports at d800 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: uhci_hcd
00: 06 11 38 30 07 00 10 02 81 00 03 0c 08 20 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 d8 00 00 00 00 00 00 00 00 00 00 06 11 38 30
30: 00 00 00 00 80 00 00 00 00 00 00 00 0b 02 00 00
40: 40 12 03 00 00 00 00 00 00 0b a0 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 01 00 c2 ff 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00

00:10.3 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 81)
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin B routed to IRQ 11
	Region 4: I/O ports at d400 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: uhci_hcd
00: 06 11 38 30 07 00 10 02 81 00 03 0c 08 20 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 d4 00 00 00 00 00 00 00 00 00 00 06 11 38 30
30: 00 00 00 00 80 00 00 00 00 00 00 00 0b 02 00 00
40: 40 12 03 00 00 00 00 00 00 0b a0 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 01 00 c2 ff 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00

00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 86) (prog-if 20)
	Subsystem: VIA Technologies, Inc. USB 2.0 [1106:3104]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin C routed to IRQ 5
	Region 0: Memory at fdfff000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: ehci_hcd
00: 06 11 04 31 17 00 10 02 86 20 03 0c 08 20 80 00
10: 00 f0 ff fd 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 04 31
30: 00 00 00 00 80 00 00 00 00 00 00 00 05 03 00 00
40: 00 00 03 00 00 00 00 00 a8 20 00 09 00 00 00 00
50: 00 5a 00 80 00 00 00 00 04 0b 66 88 03 66 88 00
60: 20 20 01 00 00 00 00 00 01 00 00 00 00 00 08 c0
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 01 00 c2 ff 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 88 00 00 00 00 00 00 00 00 00

00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] [1106:3227]
	Subsystem: VIA Technologies, Inc. Device [1106:aa08]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel modules: i2c-viapro
00: 06 11 27 32 87 00 10 02 00 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 08 aa
30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
40: 54 7f f8 0b 00 00 00 00 0c 20 00 00 04 00 0a 08
50: 80 99 09 00 00 a0 5b 00 02 00 00 09 00 00 00 00
60: 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00
70: 06 11 08 aa 00 00 00 00 00 00 00 00 20 00 00 00
80: 20 84 49 00 1a 70 00 00 01 04 00 00 04 18 00 00
90: f0 11 02 88 a0 c2 06 00 00 82 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 01 05 01 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 03 09 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 0b 00 00 00 00 00 00 00 00 00

00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 60)
	Subsystem: VIA Technologies, Inc. Device [1106:aa08]
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin C routed to IRQ 5
	Region 0: I/O ports at d000 [size=256]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: VIA 82xx Audio
	Kernel modules: snd-via82xx
00: 06 11 59 30 01 00 10 02 60 00 01 04 00 00 00 00
10: 01 d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 08 aa
30: 00 00 00 00 c0 00 00 00 00 00 00 00 05 03 00 00
40: 01 cc 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 01 00 02 06 00 00 00 00 00 00 00 00 00 00 00 00
d0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102 [Rhine-II] [1106:3065] (rev 78)
	Subsystem: VIA Technologies, Inc. Device [1106:0102]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (750ns min, 2000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 10
	Region 0: I/O ports at c800 [size=256]
	Region 1: Memory at fdffe000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [40] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: via-rhine
	Kernel modules: via-rhine
00: 06 11 65 30 87 00 10 02 78 00 00 02 08 20 00 00
10: 01 c8 00 00 00 e0 ff fd 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 02 01
30: 00 00 00 00 40 00 00 00 00 00 00 00 0a 01 03 08
40: 01 00 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:14.0 PCI bridge [0604]: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) [3388:0021] (rev 11)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+ INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
	I/O behind bridge: 0000a000-0000afff
	Memory behind bridge: fde00000-fdefffff
	Prefetchable memory behind bridge: ec000000-f3ffffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
		Bridge: PM- B3+
	Capabilities: [90] CompactPCI hot-swap <?>
	Kernel modules: shpchp
00: 88 33 21 00 07 00 90 82 11 00 04 06 08 20 01 00
10: 00 00 00 00 00 00 00 00 00 02 02 20 a0 a0 80 22
20: e0 fd e0 fd 00 ec f0 f3 00 00 00 00 00 00 00 00
30: 00 00 00 00 80 00 00 00 00 00 00 00 ff 00 04 00
40: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0a
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 01 90 02 f6 00 00 c0 00 00 00 00 00 00 00 00 00
90: 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 [S3 UniChrome Pro] [1106:3344] (rev 01)
	Subsystem: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 [S3 UniChrome Pro] [1106:3344]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (500ns min)
	Interrupt: pin A routed to IRQ 10
	Region 0: Memory at f4000000 (32-bit, prefetchable) [size=64M]
	Region 1: Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
	[virtual] Expansion ROM at fc000000 [disabled] [size=64K]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [70] AGP version 3.0
		Status: RQ=256 Iso- ArqSz=0 Cal=7 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3+ Rate=x4,x8
		Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none>
00: 06 11 44 33 07 00 30 02 01 00 00 03 00 20 00 00
10: 08 00 00 f4 00 00 00 fb 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 44 33
30: 00 00 00 00 60 00 00 00 00 00 00 00 0a 01 02 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 01 70 22 06 00 00 00 00 00 00 00 00 00 00 00 00
70: 02 00 30 00 0b 1e 00 ff 00 02 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

02:08.0 Multimedia video controller [0400]: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder [4444:0016] (rev 01)
	Subsystem: Hauppauge computer works Inc. Device [0070:e807]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 5
	Region 0: Memory at f0000000 (32-bit, prefetchable) [size=64M]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: ivtv
	Kernel modules: ivtv
00: 44 44 16 00 06 00 10 02 01 00 00 04 08 40 00 00
10: 08 00 00 f0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 70 00 07 e8
30: 00 00 00 00 44 00 00 00 00 00 00 00 05 01 80 08
40: ff ff 00 00 01 00 02 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

02:09.0 Multimedia video controller [0400]: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder [4444:0016] (rev 01)
	Subsystem: Hauppauge computer works Inc. Device [0070:e817]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 5
	Region 0: Memory at ec000000 (32-bit, prefetchable) [size=64M]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: ivtv
	Kernel modules: ivtv
00: 44 44 16 00 06 00 10 02 01 00 00 04 08 40 00 00
10: 08 00 00 ec 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 70 00 17 e8
30: 00 00 00 00 44 00 00 00 00 00 00 00 05 01 80 08
40: ff ff 00 00 01 00 02 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[Luc Verhaegen]

On Sat, Oct 17, 2009 at 03:40:43PM +0200, Yuri Schaeffer wrote:
> Hi,
> I tried to flash to the latest BIOS for my board but it failed at
> verifying. The backup I made a few minutes earlier has the same problem.
>  I did not (dare to) reboot the system. Attached flashrom output and
> lspci -vvnnxxx.
>
> board: via epia cn 1000eg
> southbr: VT8237R Plus (according to the specs)
> flashrom: v0.9.1-r750
> bios image: 1.14, 2009/07/31,
> http://www.via.com.tw/servlet/downloadSvl?id=400&download_file_id=4942
>
> Currently I have no idea how to repair my system. Folks at #flashrom
> pointed me to here.

Conclusion for this is that this is most likely a broken flashchip.

Rudolf and Carl-daniel spent a lot of time working with Yuri on irc to 
try to resolve this, to no avail.

Rudolf provided a quick hack to try to at least have the checksum be 
correct and hopefully have the machine boot again.

But the final solution for Yuri is probably getting a new chip from 
somewhere.

Luc Verhaegen.

[Carl-Daniel Hailfinger]

Hi Yuri,

what's the current status of your machine? Please see below for some news.

On 18.10.2009 18:11, Luc Verhaegen wrote:
> On Sat, Oct 17, 2009 at 03:40:43PM +0200, Yuri Schaeffer wrote:
> > Hi,
> > I tried to flash to the latest BIOS for my board but it failed at
> > verifying. The backup I made a few minutes earlier has the same problem.
> >  I did not (dare to) reboot the system. Attached flashrom output and
> > lspci -vvnnxxx.
> >
> > board: via epia cn 1000eg
> > southbr: VT8237R Plus (according to the specs)
> > flashrom: v0.9.1-r750
> > bios image: 1.14, 2009/07/31,
> > http://www.via.com.tw/servlet/downloadSvl?id=400&download_file_id=4942
> >
> > Currently I have no idea how to repair my system. Folks at #flashrom
> > pointed me to here.
>
> Conclusion for this is that this is most likely a broken flashchip.
>
> Rudolf and Carl-daniel spent a lot of time working with Yuri on irc to 
> try to resolve this, to no avail.
>
> Rudolf provided a quick hack to try to at least have the checksum be 
> correct and hopefully have the machine boot again.
>
> But the final solution for Yuri is probably getting a new chip from 
> somewhere.

I found a bug in flashrom which could partially explain what Yuri was
seeing. It was already present in the first revision of flashrom back in
2003 and will only appear in very special circumstances which are very
difficult to hit. I had to read a few datasheets twice before even
seeing what was wrong. "Enable protection" is a command with side
effects on some chips (the side effect is trashing the contents of
address 0x5555 with subsequent commands).
To see the effect, you have to have bad luck with chip timing, exact
chip type, the kernel process scheduler, delay calibration and others.

Anyway, I think I can look at this again and maybe find out what exactly
went wrong.

Regards,
Carl-Daniel

-- 
Developer quote of the week: 
"We are juggling too many chainsaws and flaming arrows and tigers."

[Yuri Schaeffer]

*now to the list as well*
Hello Carl-Daniel,

Carl-Daniel Hailfinger wrote:
> what's the current status of your machine? Please see below for some news.

The machine is still running, didn't try to reboot yet. I'll try to sum
up what we tried with help from you and others on irc / some facts.

- The chip does Erase properly
- When writing a normal image the byte at 0x5555 is incorrect. (0xaa
instead of 0xff)
- When I replace byte at 0x5555 with 0x00 in the image, 0x00 is properly
written but the verification fails at 0x2a000 (if I remember correctly)
which I heard is also a magic address.
- I pulled out the chip in the running system and reinserted it in the
hope to reset byte 0x5555. Did not help. (?conclusion: the wrong value
is actually in memory?)
- I added delay statements in the code in all mmio_readx functions, took
10 minutes to flash, but result was the same.
- writing an all 0xFF file does work correctly.

I hope I remember everything correctly, can't verify right now. Also we
prepped an image which would have a 0 checksum when the 0xaa byte is
written to be sure. Haven't been able to verify that is actually was 0.
> I found a bug in flashrom which could partially explain what Yuri was
> seeing. It was already present in the first revision of flashrom back in
> 2003 and will only appear in very special circumstances which are very
> difficult to hit. I had to read a few datasheets twice before even
> seeing what was wrong. "Enable protection" is a command with side
> effects on some chips (the side effect is trashing the contents of
> address 0x5555 with subsequent commands).
> To see the effect, you have to have bad luck with chip timing, exact
> chip type, the kernel process scheduler, delay calibration and others.

Sounds interesting. You write partially, is there anything you can't
explain yet?

Regards,
Yuri

[Carl-Daniel Hailfinger]

Hi Yuri,

here's the patch I'd like you to try. It will also show up at
http://patchwork.coreboot.org/project/flashrom/list/

Handle LPC mode of Pm49FL004 correctly.

Signed-off-by: Carl-Daniel Hailfinger <[e-mail]>

Index: flashrom-pm49fl004_lpc/pm49fl00x.c
===================================================================
--- flashrom-pm49fl004_lpc/pm49fl00x.c	(Revision 751)
+++ flashrom-pm49fl004_lpc/pm49fl00x.c	(Arbeitskopie)
@@ -53,8 +53,10 @@
 	int page_size = flash->page_size;
 
 	/* unprotected */
+#if 0
 	write_lockbits_49fl00x(flash->virtual_registers,
 			       total_size, 0, page_size);
+#endif
 
 	/*
 	 * erase_chip_jedec() will not work... Datasheet says
@@ -74,8 +76,10 @@
 	printf("\n");
 
 	/* protected */
+#if 0
 	write_lockbits_49fl00x(flash->virtual_registers,
 			       total_size, 1, page_size);
+#endif
 
 	return 0;
 }
@@ -88,29 +92,39 @@
 	chipaddr bios = flash->virtual_memory;
 
 	/* unprotected */
+#if 0
 	write_lockbits_49fl00x(flash->virtual_registers, total_size, 0,
 			       page_size);
+#endif
 
-	printf("Programming page: ");
+	printf("Programming...");
 	for (i = 0; i < total_size / page_size; i++) {
 		/* erase the page before programming */
+#if 0
 		if (erase_block_jedec(flash, i * page_size, page_size)) {
 			fprintf(stderr, "ERASE FAILED!\n");
 			return -1;
 		}
+#endif
 
 		/* write to the sector */
+#if 0
 		printf("%04d at address: 0x%08x", i, i * page_size);
+#endif
 		write_sector_jedec(bios, buf + i * page_size,
 				   bios + i * page_size, page_size);
+#if 0
 		printf("\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b");
 		fflush(stdout);
+#endif
 	}
 	printf("\n");
 
 	/* protected */
+#if 0
 	write_lockbits_49fl00x(flash->virtual_registers, total_size, 1,
 			       page_size);
+#endif
 
 	return 0;
 }


-- 
Developer quote of the week: 
"We are juggling too many chainsaws and flaming arrows and tigers."

[Yuri Schaeffer]

Yuri Schaeffer wrote:
> Currently I have no idea how to repair my system. Folks at #flashrom
> pointed me to here.

Well above desperation is over. Last Friday I traded my chip with one of
Idwer's pre-flashed chips, whom was extremely kind in helping me. Since
a couple of days I inserted the chip and the system woke up like the
sleeping beauty. :)

Many thanks to all helping me via this list, IRC and IRL.

@Idwer: Have you tried my old bioschip yet, did it work on your system?

//yuri (puccha)

[Idwer Vollering]

2009/11/20 Yuri Schaeffer <[e-mail]>
> Yuri Schaeffer wrote:
> > Currently I have no idea how to repair my system. Folks at #flashrom
> > pointed me to here.
>
> Well above desperation is over. Last Friday I traded my chip with one of
> Idwer's pre-flashed chips, whom was extremely kind in helping me. Since
> a couple of days I inserted the chip and the system woke up like the
> sleeping beauty. :)
>
> Many thanks to all helping me via this list, IRC and IRL.
>
> @Idwer: Have you tried my old bioschip yet, did it work on your system?

Hey Yuri,

I finally found (and took) the time to mess with your chip.

Using flashrom r883, probing, reading and writing your chip works; erasing
is work in progress (Sean ?).

Luc: the chip itself doesn't appear to be broken because writing a 512KB
file created with dd from /dev/zero and reading it back, then comparing the
empty and readout file with md5sum shows that the files are identical (ergo
empty) -- yes, I saved the original content.
( http://www.flashrom.org/pipermail/flashrom/2009-October/000777.html )
> //yuri (puccha)

HTH,

Idwer
> _______________________________________________
> flashrom mailing list
> [e-mail]
> http://www.flashrom.org/mailman/listinfo/flashrom

[Luc Verhaegen]

On Wed, Jan 27, 2010 at 12:38:40AM +0100, Idwer Vollering wrote:
> 2009/11/20 Yuri Schaeffer <[e-mail]>
> > Yuri Schaeffer wrote:
> > > Currently I have no idea how to repair my system. Folks at #flashrom
> > > pointed me to here.
> >
> > Well above desperation is over. Last Friday I traded my chip with one of
> > Idwer's pre-flashed chips, whom was extremely kind in helping me. Since
> > a couple of days I inserted the chip and the system woke up like the
> > sleeping beauty. :)
> >
> > Many thanks to all helping me via this list, IRC and IRL.
> >
> > @Idwer: Have you tried my old bioschip yet, did it work on your system?
>
> Hey Yuri,
>
> I finally found (and took) the time to mess with your chip.
>
> Using flashrom r883, probing, reading and writing your chip works; erasing
> is work in progress (Sean ?).
>
> Luc: the chip itself doesn't appear to be broken because writing a 512KB
> file created with dd from /dev/zero and reading it back, then comparing the
> empty and readout file with md5sum shows that the files are identical (ergo
> empty) -- yes, I saved the original content.
> ( http://www.flashrom.org/pipermail/flashrom/2009-October/000777.html )
> > //yuri (puccha)
>
> HTH,
>
> Idwer

Wow, this i had never expected.

There should be no issue with this board; the board enable is the 
chipset enable. There was no issue with previous instances of this 
board.

I am stumped myself, i think carldani had some ideas.

Can you send me, personally, the image that you read from the chip?

Luc Verhaegen.

[Michael Karcher]

Am Mittwoch, den 27.01.2010, 00:38 +0100 schrieb Idwer Vollering:
> Using flashrom r883, probing, reading and writing your chip works;
> erasing is work in progress (Sean ?).
>
> Luc: the chip itself doesn't appear to be broken because writing a
> 512KB file created with dd from /dev/zero and reading it back, then
> comparing the empty and readout file with md5sum shows that the files
> are identical (ergo empty) -- yes, I saved the original content.
> ( http://www.flashrom.org/pipermail/flashrom/2009-October/000777.html )

So, summary: The original problem was a destroyed byte at 0x5555 in the
chip. It contains the magic 0xAA instead of the required 0xFF. This is a
sign of a magic write instruction mistaken as data write instruction. If
the image to write did not have the bits set that get cleared by the
wrong 0xAA write, this location verifies for obvious reasons.

But then you get some clue by looking at further details. If the 5555
location passes, you get verify errors at 2a000. The total count of
failed bytes is 0x16fd, or probably, if we "fix" the 5555 location it is
0x16fc, approximately 1.4 pages of 4KB. The readout you posted to the
channel contained this:

00029ff0  95 04 41 39 2c 41 09 82  e3 a1 17 f4 d0 e2 e1 4a |..A9,A.........J|
0002a000  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff |................|

It shows that the whole area above 0x2a000 is unprogrammed. As we can
exclude a broken chip (it worked on your machine), I suspect a broken
machine flashrom was used on. My current (and quite plausible) working
hypothesis is that the page table entry on yuri's original machine that
should point to 0xfffaa000 (where the flash chip address 2a000) gets
mapped was wrong and didn't really point to 0xfffaa000, but some unused
memory location that always reads as 0xff (making his verify fail with
expected=0xff) and ignores writes (so the chip stays in armed-for-write
mode over the missing access to 0x2a000 and writes the 0xaa to 0x5555)
when sending the write enable instruction again to retry flahsing of
this byte.

It would be interesting to check whether this ffff-area that starts at
2a000 ends at 2afff, which would indicate exactly one machine page
missing (staying deleted from the block erase). As the failed byte count
is more than 0x1000, namely 0x16fd, I suspect a second page to be
broken.

yuri: Please run memtest86 on your machine. You might have memory
problems that cause silent data corruption.

Regads,
  Michael Karcher

[Yuri Schaeffer]

Idwer Vollering wrote:
> Luc: the chip itself doesn't appear to be broken because writing a
> 512KB file created with dd from /dev/zero and reading it back, then
> comparing the empty and readout file with md5sum shows that the files
> are identical (ergo empty)

If I remember correctly erasing the chip would work correctly on my own
machine as well. Ah yes:

(self-quote 2009-10-19)
- The chip does Erase properly
- writing an all 0xFF file does work correctly.

Have you tried to write one of the images?

Michael Karcher wrote:
> yuri: Please run memtest86 on your machine. You might have memory 
> problems that cause silent data corruption.

I sincerely doubt that, but lets rule it out anyway. I'll have
memtest run a couple of hours this week.

//yuri

[Idwer Vollering]

2010/1/27 Yuri Schaeffer <[e-mail]>
> Idwer Vollering wrote:
> > Luc: the chip itself doesn't appear to be broken because writing a
> > 512KB file created with dd from /dev/zero and reading it back, then
> > comparing the empty and readout file with md5sum shows that the files
> > are identical (ergo empty)
>
> If I remember correctly erasing the chip would work correctly on my own
> machine as well. Ah yes:
>
> (self-quote 2009-10-19)
> - The chip does Erase properly
> - writing an all 0xFF file does work correctly.
>
> Have you tried to write one of the images?

I have written I1300114.BIN (
http://www.via.com.tw/servlet/downloadSvl?id=400&download_file_id=4942&outSi...)
a minute ago, read the chip and compared the md5sums of the readout
and
the downloaded file: they match.
> Michael Karcher wrote:
> > yuri: Please run memtest86 on your machine. You might have memory
> > problems that cause silent data corruption.
>
> I sincerely doubt that, but lets rule it out anyway. I'll have
> memtest run a couple of hours this week.

Did memtest report any errors ?
> //yuri

[Yuri Schaeffer]

On Mon, Feb 01, 2010 at 08:44:07PM +0100, Idwer Vollering wrote:
> I have written I1300114.BIN (
> http://www.via.com.tw/servlet/downloadSvl?id=400&download_file_id=4942&outSi...)
> a minute ago, read the chip and compared the md5sums of the readout
> and
> the downloaded file: they match.

Good.
But that's bad news for me.
> > I sincerely doubt that, but lets rule it out anyway. I'll have
> > memtest run a couple of hours this week.
> Did memtest report any errors ?

Haven't got any change to test that yet and will definitly 
not do so this week. But I'm a bit worried about my hardware
now so I will definitly test it next week.

//Yuri

[Yuri Schaeffer]

Op maandag 01-02-2010 om 20:44 uur [tijdzone +0100], schreef Idwer
Vollering:
> Did memtest report any errors ?

I just had it running for 2 hours and 15 minutes (about 1.5 passes) but
no errors where found.

//yuri