flashrom

flashrom@flashrom.org

1 participants
9182 discussions

[Fwd: Re: Is K7S6A supported by flashrom? 2nd Reply.]
by Carl-Daniel Hailfinger 15 Oct '09

15 Oct '09

forwarded. -------- Original Message -------- Subject: Re: [flashrom] Is K7S6A supported by flashrom? 2nd Reply. Date: Wed, 14 Oct 2009 19:33:44 +0100 From: spirals <spirals(a)eircom.net> To: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> References: <4AD4DABF.8050509(a)eircom.net> <4AD4EF17.80507(a)gmx.net> Hi Carl-Daniel, Have just restarted after a full covers off eye-ball of the board is definatly is the K&S6A (v1.0) board, pene also looked (my eyes are not as good as they were) and she confirmed 1.0 and _/*not 1.0A*/_ regards, (dja.) Carl-Daniel Hailfinger wrote: > Hi Dave, > > On 13.10.2009 21:53, David J Aldridge wrote: > >> Ran flashrom and it reports "No EEPROM/flash device found", same with >> -m ecs:k7s5a. >> > > Please send the output of "flashrom -V", "lspci -nnvvvxxx", "superiotool > -dV" and if tell us if your board is > K7S6A (V1.0) > or > K7S6A (V1.0A) > > Luc: BIOS downloads are here (not sure which PCB is the one Dave has): > http://www.ecs.com.tw/ECSWebSite/Products/ProductsDetail.aspx?detailid=77&C… > http://www.ecs.com.tw/ECSWebSite/Products/ProductsDetail.aspx?detailid=238&… > > Regards, > Carl-Daniel > > -- Developer quote of the week: "We are juggling too many chainsaws and flaming arrows and tigers."

1 0

[Fwd: Re: Is K7S6A supported by flashrom?]
by Carl-Daniel Hailfinger 15 Oct '09

15 Oct '09

forwarded. -------- Original Message -------- Subject: Re: [flashrom] Is K7S6A supported by flashrom? Date: Wed, 14 Oct 2009 11:08:42 +0100 From: spirals <spirals(a)eircom.net> To: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> References: <4AD4DABF.8050509(a)eircom.net> <4AD4EF17.80507(a)gmx.net> Hi Carl-Daniel, Thank you for the reply, I have attached the output from the 3 tools and as as far as I know I have the K7S6A (V1.0) board. I will do a full shutdown tonight and eye ball the board again but that's what my notebook says. In the release notes for the updated patch it states the ROM type as W49F002U12BN not certain if the extra bicharacters on the end beyondW49F002U of the type number relate to its capacity (256K*8) as I am a bit rusty having been been retired for some 10 years now. I have now downloaded the source code and compiled it as check I have all the headers etc. That works but same symptoms. Thank you for your help, regards (dja.) Carl-Daniel Hailfinger wrote: > Hi Dave, > > On 13.10.2009 21:53, David J Aldridge wrote: > >> Ran flashrom and it reports "No EEPROM/flash device found", same with >> -m ecs:k7s5a. >> > > Please send the output of "flashrom -V", "lspci -nnvvvxxx", "superiotool > -dV" and if tell us if your board is > K7S6A (V1.0) > or > K7S6A (V1.0A) > > Luc: BIOS downloads are here (not sure which PCB is the one Dave has): > http://www.ecs.com.tw/ECSWebSite/Products/ProductsDetail.aspx?detailid=77&C… > http://www.ecs.com.tw/ECSWebSite/Products/ProductsDetail.aspx?detailid=238&… > > Regards, > Carl-Daniel > > -- Developer quote of the week: "We are juggling too many chainsaws and flaming arrows and tigers." superiotool r3125 Probing for ALi Super I/O at 0x3f0... Failed. Returned data: id=0x7373, rev=0x73 Probing for ALi Super I/O at 0x370... Failed. Returned data: id=0xffff, rev=0xff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x2e... Found ITE IT8705F/AF / IT8700F (id=0x8705, rev=0x2) at 0x2e Register dump: idx 07 20 21 22 23 24 val 08 87 05 02 00 f1 def NA 87 05 00 00 NA LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 val 01 03 f0 06 02 00 80 def 00 03 f0 06 02 00 00 LDN 0x01 (COM1) idx 30 60 61 70 f0 val 01 03 f8 04 00 def 00 03 f8 04 00 LDN 0x02 (COM2) idx 30 60 61 70 f0 f1 f2 f3 val 01 02 f8 03 00 10 00 7f def 00 02 f8 03 00 50 00 7f LDN 0x03 (Parallel port) idx 30 60 61 62 63 64 65 70 74 f0 val 01 03 78 07 78 00 80 07 03 0a def 00 03 78 07 78 00 80 07 03 03 LDN 0x04 (Environment controller) idx 2b 30 60 61 62 63 70 f0 f1 f2 f3 f4 f5 f6 val 00 01 02 90 00 00 00 80 00 0a 00 c0 00 ff def 00 00 02 90 02 30 09 00 00 00 00 00 NA NA LDN 0x05 (GPIO) idx 25 26 27 28 29 2a 60 61 62 63 64 65 70 71 72 b0 b1 b2 b3 b4 b5 b8 b9 ba bb bc bd c0 c1 c2 c3 c4 c5 c8 c9 ca cb cc cd d0 d1 d2 d3 d4 d5 d6 d8 d9 da f0 f1 f2 f5 f6 f7 f8 f9 fa fb fc fd fe ff val 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0f 00 def 00 00 00 ff e0 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 NA 00 LDN 0x06 (Game port) idx 30 60 61 val 01 02 01 def 00 02 01 LDN 0x07 (Consumer IR) idx 30 60 61 70 f0 val 00 03 10 0b 06 def 00 03 10 0b 00 LDN 0x08 (MIDI port) idx 30 60 61 70 f0 val 01 03 30 0a 00 def 00 03 00 0a 00 Probing for ITE Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x4e... Found ITE IT8705F/AF / IT8700F (id=0x8705, rev=0x2) at 0x4e Register dump: idx 07 20 21 22 23 24 val 08 87 05 02 00 f1 def NA 87 05 00 00 NA LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 val 01 03 f0 06 02 00 80 def 00 03 f0 06 02 00 00 LDN 0x01 (COM1) idx 30 60 61 70 f0 val 01 03 f8 04 00 def 00 03 f8 04 00 LDN 0x02 (COM2) idx 30 60 61 70 f0 f1 f2 f3 val 01 02 f8 03 00 10 00 7f def 00 02 f8 03 00 50 00 7f LDN 0x03 (Parallel port) idx 30 60 61 62 63 64 65 70 74 f0 val 01 03 78 07 78 00 80 07 03 0a def 00 03 78 07 78 00 80 07 03 03 LDN 0x04 (Environment controller) idx 2b 30 60 61 62 63 70 f0 f1 f2 f3 f4 f5 f6 val 00 01 02 90 00 00 00 80 00 0a 00 c0 00 ff def 00 00 02 90 02 30 09 00 00 00 00 00 NA NA LDN 0x05 (GPIO) idx 25 26 27 28 29 2a 60 61 62 63 64 65 70 71 72 b0 b1 b2 b3 b4 b5 b8 b9 ba bb bc bd c0 c1 c2 c3 c4 c5 c8 c9 ca cb cc cd d0 d1 d2 d3 d4 d5 d6 d8 d9 da f0 f1 f2 f5 f6 f7 f8 f9 fa fb fc fd fe ff val 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0f 00 def 00 00 00 ff e0 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 NA 00 LDN 0x06 (Game port) idx 30 60 61 val 01 02 01 def 00 02 01 LDN 0x07 (Consumer IR) idx 30 60 61 70 f0 val 00 03 10 0b 06 def 00 03 10 0b 00 LDN 0x08 (MIDI port) idx 30 60 61 70 f0 val 01 03 30 0a 00 def 00 03 00 0a 00 Probing for ITE Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for NSC Super I/O at 0x2e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x4e... Failed. Returned data: port=0xff, port+1=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x3f0... Failed. Returned data: id=0x73, rev=0x73 Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x3f0... Failed. Returned data: id=0x73, rev=0x73 Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x3f0... Failed. Returned data: id/oldid=0x73/0x03, rev=0x73 Probing for Winbond Super I/O (init=0x89) at 0x3f0... Failed. Returned data: id/oldid=0x73/0x03, rev=0x73 Probing for Winbond Super I/O (init=0x86,0x86) at 0x3f0... Failed. Returned data: id/oldid=0x73/0x03, rev=0x73 Probing for Winbond Super I/O (init=0x87,0x87) at 0x3f0... Failed. Returned data: id/oldid=0x73/0x03, rev=0x73 Probing for Winbond Super I/O (init=0x88) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Calibrating delay loop... 321M loops per second. OK. No coreboot table found. WARNING: No chipset found. Flash detection will most likely fail. Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff Probing for ASD AE49F2008, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT49F002(N), 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT25DF321, 4096 KB: spi_command called, but no SPI chipset detected Probing for AMIC Technology A25L40P, 512 KB: spi_command called, but no SPI chipset detected Probing for AMIC Technology A49LF040A, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMIC Technology A29040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff Probing for EMST F49B002UA, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for EON EN29F002(A)(N)B, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0xff, id2 0xff Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for Macronix MX25L4005, 512 KB: spi_command called, but no SPI chipset detected Probing for Macronix MX25L8005, 1024 KB: spi_command called, but no SPI chipset detected Probing for Macronix MX25L1605, 2048 KB: spi_command called, but no SPI chipset detected Probing for Macronix MX25L3205, 4096 KB: spi_command called, but no SPI chipset detected Probing for Macronix MX29F002, 256 KB: probe_29f002: id1 0xff, id2 0xff Probing for PMC Pm25LV010, 128 KB: spi_command called, but no SPI chipset detected Probing for PMC Pm25LV016B, 2048 KB: spi_command called, but no SPI chipset detected Probing for PMC Pm25LV020, 256 KB: spi_command called, but no SPI chipset detected Probing for PMC Pm25LV040, 512 KB: spi_command called, but no SPI chipset detected Probing for PMC Pm25LV080B, 1024 KB: spi_command called, but no SPI chipset detected Probing for PMC Pm25LV512, 64 KB: spi_command called, but no SPI chipset detected Probing for PMC Pm49FL002, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0xff, id2 0xff Probing for Spansion S25FL016A, 2048 KB: spi_command called, but no SPI chipset detected Probing for SST SST25VF016B, 2048 KB: spi_command called, but no SPI chipset detected Probing for SST SST25VF040B, 512 KB: spi_command called, but no SPI chipset detected Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0xff, id2 0xff Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0x42, id2 0xb1, id1 parity violation Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0x42, id2 0xb1, id1 parity violation Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0x42, id2 0xb1, id1 parity violation Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0x42, id2 0xb1, id1 parity violation Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF008A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation 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 SST49LF020A, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for ST M25P05-A, 64 KB: spi_command called, but no SPI chipset detected Probing for ST M25P10-A, 128 KB: spi_command called, but no SPI chipset detected Probing for ST M25P20, 256 KB: spi_command called, but no SPI chipset detected Probing for ST M25P40, 512 KB: spi_command called, but no SPI chipset detected Probing for ST M25P40-old, 512 KB: spi_command called, but no SPI chipset detected Probing for ST M25P80, 1024 KB: spi_command called, but no SPI chipset detected Probing for ST M25P16, 2048 KB: spi_command called, but no SPI chipset detected Probing for ST M25P32, 4096 KB: spi_command called, but no SPI chipset detected Probing for ST M25P64, 8192 KB: spi_command called, but no SPI chipset detected Probing for ST M25P128, 16384 KB: spi_command called, but no SPI chipset detected Probing for ST M29F002B, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff Probing for ST M29W010B, 128 KB: probe_jedec: id1 0x42, id2 0xb1, id1 parity violation Probing for ST M29W040B, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0xff, id2 0xff 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 Probing for SyncMOS S29C31004T, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0x42, id2 0xb1, id1 parity violation Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W25x10, 128 KB: spi_command called, but no SPI chipset detected Probing for Winbond W25x20, 256 KB: spi_command called, but no SPI chipset detected Probing for Winbond W25x40, 512 KB: spi_command called, but no SPI chipset detected Probing for Winbond W25x80, 1024 KB: spi_command called, but no SPI chipset detected Probing for Winbond W29C011, 128 KB: probe_jedec: id1 0x42, id2 0xb1, id1 parity violation Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation 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 0xff, id2 0xff, id1 parity violation Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W49F002U, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: vid 0xff, did 0xff Probing for Winbond W39V080FA (dual mode), 512 KB: probe_winbond_fwhub: vid 0xff, did 0xff Probing for EON unknown EON SPI chip, 0 KB: spi_command called, but no SPI chipset detected Probing for Macronix unknown Macronix SPI chip, 0 KB: spi_command called, but no SPI chipset detected Probing for PMC unknown PMC SPI chip, 0 KB: spi_command called, but no SPI chipset detected Probing for SST unknown SST SPI chip, 0 KB: spi_command called, but no SPI chipset detected Probing for ST unknown ST SPI chip, 0 KB: spi_command called, but no SPI chipset detected No EEPROM/flash device found. If you know which flash chip you have, and if this version of flashrom supports a similar flash chip, you can try to force read your chip. Run: flashrom -f -r -c similar_supported_flash_chip filename Note: flashrom can never write when the flash chip isn't found automatically. 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 745 Host [1039:0745] (rev 01) 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 Region 0: Memory at e0000000 (32-bit, non-prefetchable) [size=64M] Capabilities: [c0] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none> Kernel driver in use: agpgart-sis Kernel modules: sis-agp 00: 39 10 45 07 07 00 10 22 01 00 00 06 00 20 80 00 10: 00 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 00 00 00 00 30: 00 00 00 00 c0 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: 07 e4 77 f7 aa d4 e8 f0 46 79 08 03 12 d5 03 00 60: 6b 6b 6d 6d 03 00 00 00 01 50 18 22 00 81 3f 00 70: 04 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 02 40 30 03 85 00 80 01 20 0c 00 04 00 00 00 00 90: 00 00 19 37 43 01 00 05 00 2e b3 40 00 00 00 20 a0: 42 cb 34 01 aa 00 00 00 00 00 00 00 00 00 00 04 b0: 00 00 00 00 7b 02 6f 6b 5a 1a 49 fa 15 f5 00 4a c0: 02 00 20 00 17 02 00 1f 00 00 00 00 00 00 00 00 d0: 02 40 31 00 09 ff ff 00 60 60 aa 00 00 80 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:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP) [1039:0001] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 99 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: 0000c000-0000cfff Memory behind bridge: e4000000-e6ffffff Prefetchable memory behind bridge: 50000000-500fffff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR- BridgeCtl: Parity- SERR+ NoISA+ VGA+ MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Kernel modules: shpchp 00: 39 10 01 00 07 01 00 00 00 00 04 06 00 63 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 20 c0 c0 00 20 20: 00 e4 f0 e6 00 50 00 50 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0e 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: 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:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge) [1039:0018] 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: i2c-sis630 00: 39 10 18 00 0f 00 00 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: da 89 80 05 0b 22 31 0d 10 00 00 00 11 20 04 01 50: 11 28 02 01 61 0a 66 00 00 00 12 00 a6 0b b6 00 60: 80 80 80 0b 40 c1 0a 10 09 80 00 02 d0 00 00 00 70: 00 00 00 00 00 50 00 ec 00 00 00 00 06 00 01 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: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:02.1 SMBus [0c05]: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller [1039:0016] 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 B routed to IRQ 0 Region 4: I/O ports at 5080 [size=32] Kernel driver in use: sis96x_smbus Kernel modules: i2c-sis96x 00: 39 10 16 00 01 00 00 02 00 00 05 0c 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 81 50 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 02 00 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 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:02.2 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 07) (prog-if 10 [OHCI]) Subsystem: Elitegroup Computer Systems Device [1019:0a41] 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 (20000ns max), Cache Line Size: 32 bytes Interrupt: pin D routed to IRQ 11 Region 0: Memory at e8002000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00: 39 10 01 70 07 00 80 02 07 10 03 0c 08 20 00 00 10: 00 20 00 e8 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 19 10 41 0a 30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 04 00 50 40: 00 00 00 00 54 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: 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:02.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 07) (prog-if 10 [OHCI]) Subsystem: Elitegroup Computer Systems Device [1019:0a41] 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 (20000ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 11 Region 0: Memory at e8000000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00: 39 10 01 70 07 00 80 02 07 10 03 0c 08 20 00 00 10: 00 00 00 e8 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 19 10 41 0a 30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 50 40: 00 00 00 00 54 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: 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:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 [IDE] [1039:5513] (rev d0) (prog-if 80 [Master]) Subsystem: Elitegroup Computer Systems Device [1019:0a41] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 128 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 4000 [size=16] Kernel driver in use: SIS_IDE Kernel modules: sis5513 00: 39 10 13 55 07 00 00 00 d0 80 01 01 00 80 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 40 00 00 00 00 00 00 00 00 00 00 19 10 41 0a 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 31 81 31 81 31 85 31 85 28 01 e6 ff 00 02 00 02 50: 01 00 01 06 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:02.7 Multimedia audio controller [0401]: Silicon Integrated Systems [SiS] AC'97 Sound Controller [1039:7012] (rev a0) Subsystem: Elitegroup Computer Systems Device [1019:0a41] 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 (13000ns min, 2750ns max) Interrupt: pin C routed to IRQ 5 Region 0: I/O ports at d800 [size=256] Region 1: I/O ports at dc00 [size=64] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: Intel ICH Kernel modules: snd-intel8x0 00: 39 10 12 70 05 00 90 02 a0 00 01 04 00 20 00 00 10: 01 d8 00 00 01 dc 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 41 0a 30: 00 00 00 00 48 00 00 00 00 00 00 00 05 03 34 0b 40: 04 00 00 00 00 00 00 00 01 00 42 c0 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: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:0c.0 Ethernet controller [0200]: 3Com Corporation 3c905C-TX/TX-M [Tornado] [10b7:9200] (rev 74) Subsystem: 3Com Corporation 3C905CX-TX/TX-M Fast Etherlink for PC Management NIC [10b7:1000] 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 (2500ns min, 2500ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 5 Region 0: I/O ports at e000 [size=128] Region 1: Memory at e8001000 (32-bit, non-prefetchable) [size=128] [virtual] Expansion ROM at 50100000 [disabled] [size=128K] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=2 PME- Kernel driver in use: 3c59x Kernel modules: 3c59x 00: b7 10 00 92 07 00 10 02 74 00 00 02 08 20 00 00 10: 01 e0 00 00 00 10 00 e8 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 b7 10 00 10 30: 00 00 00 00 dc 00 00 00 00 00 00 00 05 01 0a 0a 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: 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 01 00 02 fe e0: 00 40 00 b7 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:0d.0 SCSI storage controller [0100]: Initio Corporation INI-935 Fast Wide SCSI Adapter [1101:9401] (rev 01) Subsystem: Device [9292:0202] 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 11 Region 0: I/O ports at e400 [size=256] Region 1: Memory at e8003000 (32-bit, non-prefetchable) [size=4K] [virtual] Expansion ROM at 50120000 [disabled] [size=32K] Kernel driver in use: initio Kernel modules: initio 00: 01 11 01 94 07 00 00 02 01 00 00 01 08 20 00 00 10: 01 e4 00 00 00 30 00 e8 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 92 92 02 02 30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 00 40: f7 3f ff ff ff ff ff ff 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 01 01 00 00 00 00 04 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 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc 3D Rage Pro AGP 1X/2X [1002:4742] (rev 5c) (prog-if 00 [VGA controller]) Subsystem: ATI Technologies Inc Rage Pro Turbo AGP 2X [1002:0084] 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 (2000ns min), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 9 Region 0: Memory at e4000000 (32-bit, non-prefetchable) [size=16M] Region 1: I/O ports at c000 [size=256] Region 2: Memory at e6000000 (32-bit, non-prefetchable) [size=4K] [virtual] Expansion ROM at 50000000 [disabled] [size=128K] Capabilities: [50] AGP version 1.0 Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none> 00: 02 10 42 47 87 00 90 02 5c 00 00 03 08 20 00 00 10: 00 00 00 e4 01 c0 00 00 00 00 00 e6 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 02 10 84 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 09 01 08 00 40: 0c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 02 00 10 00 03 02 00 ff 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

1 0

flashe réussie sur carte asus
by rvb 12 Oct '09

12 Oct '09

carte asus : P4C800-E Deluxe chipset : intel 875P + ICH5R bios : 1023.001 (asus) flashe réussie

1 0

Successfully erased and flashed my GIGABYTE GA-G33M-DS2R
by Benjamin BELLEC 11 Oct '09

11 Oct '09

Hi, I used flashrom to flash my motherboard : a GIGABYTE GA-G33M-DS2R. Here is the needed log. One core of my CPU during the flash was at 100% and a very fat log was created (95 Mio) due to this line repeated roughtly 2 millions times: *Invalid OPCODE 0x06 due to SPI master limitation, ignoring and hoping it will be run as PREOP* And lspci indicate (in the Ethernet section) a "GA-EP45-DS5 Motherboard" but it's wrong. If you need more information just ask me, but write to my private email address since I don't subscribe to the mailing list. Thanks to flashrom team, Benjamin BELLEC

1 0

Successfully erased and flashed my GIGABYTE GA-MA78G-DS3H
by yulrottmann＠bitel.net 11 Oct '09

11 Oct '09

Hi, I used flashrom to flash my new OEM BIOS. My board is a GIGABYTE GA-MA78G-DS3H (Revision 1). Thanks for this really nice tool. :) Flashrom told me that I should confirm on this list if I successfully erased the BIOS: "This flash part has status UNTESTED for operations: ERASE Please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash part. Please include the flashrom output with the additional -V option for all operations you tested (-V, -rV, -wV, -EV), and mention which mainboard you tested. Thanks for your help!" That is what I'm doing here, the log file is attached. I erased my flash, then read out and it was deleted. Then I flashed a new BIOS and rebooted my system. Now I use the new BIOS, F8 instead of F6. There are two things I noticed: - Flashrom tells: "Disabling flash write protection for board "GIGABYTE GA-MA78GM-S2H"... Serial flash segment 0xfffe0000-0xffffffff enabled" This is not my mainboard, I have a DS3H, but it works anyway. - When writing to the chip, there is a break where it is not clear what flashrom does: "[...] Writing flash chip... Erasing flash before programming... Erasing flash chip... Looking at blockwise erase function 0... trying... SUCCESS. done. [HERE IS A CA. 3 MINUTES BREAK] COMPLETE. Verifying flash... VERIFIED." Maybe you should add a "still in progress" or similar. "Done" looks like it has completed the whole process. Also the CPU uses 100% while flashing/erasing/verifying, I don't know it this is normal. If you need more information just ask me, but write to my private email address since I don't subscribe to the mailing list. Thanks, Yul Rottmann

1 0

[commit] r750 - trunk
by svn＠flashrom.org 06 Oct '09

06 Oct '09

Author: uwe Date: 2009-10-06 22:25:48 +0200 (Tue, 06 Oct 2009) New Revision: 750 Modified: trunk/print_wiki.c Log: Add missing NVIDIA PCI IDs to wiki output. Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/print_wiki.c =================================================================== --- trunk/print_wiki.c 2009-10-06 20:23:29 UTC (rev 749) +++ trunk/print_wiki.c 2009-10-06 20:25:48 UTC (rev 750) @@ -547,6 +547,9 @@ #if NIC3COM_SUPPORT == 1 print_supported_pcidevs_wiki(nics_3com); #endif +#if GFXNVIDIA_SUPPORT == 1 + print_supported_pcidevs_wiki(gfx_nvidia); +#endif #if DRKAISER_SUPPORT == 1 print_supported_pcidevs_wiki(drkaiser_pcidev); #endif

1 0

[commit] r749 - trunk
by svn＠flashrom.org 06 Oct '09

06 Oct '09

Author: uwe Date: 2009-10-06 22:23:29 +0200 (Tue, 06 Oct 2009) New Revision: 749 Modified: trunk/board_enable.c trunk/print.c trunk/print_wiki.c Log: Mark the following boards as supported (no board-enable needed): - MSI MS-6153 (reported by Uwe Hermann <uwe(a)hermann-uwe.de>) Tested by me on hardware. The board decodes max. 256 KB. - MSI MS-6156 (reported by Uwe Hermann <uwe(a)hermann-uwe.de>) Tested by me on hardware. The board decodes max. 256 KB. Also, fix Dell PowerEdge 1850 name and add some more board URLs. Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/board_enable.c =================================================================== --- trunk/board_enable.c 2009-10-06 13:00:00 UTC (rev 748) +++ trunk/board_enable.c 2009-10-06 20:23:29 UTC (rev 749) @@ -617,10 +617,10 @@ } /** - * Suited for the Dell S1850. All parameters except the last one are documented - * in the public Intel 82801EB ICH5 / 82801ER ICH5R Datasheet. The last - * parameter (GPIO number) has to be in the range [16,31] according to said - * Intel Datasheet and was found by exhaustive search. + * Suited for the Dell PowerEdge 1850. All parameters except the last one are + * documented in the public Intel 82801EB ICH5 / 82801ER ICH5R datasheet. The + * last parameter (GPIO number) has to be in the range [16,31] according to + * said Intel datasheet and was found by exhaustive search. */ static int ich5_gpio23_raise(const char *name) { @@ -1058,7 +1058,7 @@ {0x10B9, 0x1541, 0, 0, 0x10B9, 0x1533, 0, 0, "asus", "p5a", "ASUS", "P5A", board_asus_p5a}, {0x10DE, 0x0030, 0x1043, 0x818a, 0x8086, 0x100E, 0x1043, 0x80EE, NULL, NULL, "ASUS", "P5ND2-SLI Deluxe", board_asus_p5nd2_sli}, {0x1106, 0x3149, 0x1565, 0x3206, 0x1106, 0x3344, 0x1565, 0x1202, NULL, NULL, "Biostar", "P4M80-M4", it8705_rom_write_enable}, - {0x8086, 0x3590, 0x1028, 0x016c, 0x1000, 0x0030, 0x1028, 0x016c, NULL, NULL, "Dell", "S1850", ich5_gpio23_raise}, + {0x8086, 0x3590, 0x1028, 0x016c, 0x1000, 0x0030, 0x1028, 0x016c, NULL, NULL, "Dell", "PowerEdge 1850", ich5_gpio23_raise}, {0x1106, 0x3038, 0x1019, 0x0996, 0x1106, 0x3177, 0x1019, 0x0996, NULL, NULL, "Elitegroup", "K7VTA3", it8705f_write_enable_2e}, {0x1106, 0x3177, 0x1106, 0x3177, 0x1106, 0x3059, 0x1695, 0x3005, NULL, NULL, "EPoX", "EP-8K5A2", board_epox_ep_8k5a2}, {0x10EC, 0x8139, 0x1695, 0x9001, 0x11C1, 0x5811, 0x1695, 0x9015, NULL, NULL, "EPoX", "EP-8RDA3+", board_epox_ep_8rda3plus}, Modified: trunk/print.c =================================================================== --- trunk/print.c 2009-10-06 13:00:00 UTC (rev 748) +++ trunk/print.c 2009-10-06 20:23:29 UTC (rev 749) @@ -270,6 +270,8 @@ { "GIGABYTE", "GA-MA770T-UD3P", }, { "Intel", "EP80759", }, { "Jetway", "J7F4K1G5D-PB", }, + { "MSI", "MS-6153", }, + { "MSI", "MS-6156", }, { "MSI", "MS-6570 (K7N2)", }, { "MSI", "MS-7065", }, { "MSI", "MS-7168 (Orion)", }, Modified: trunk/print_wiki.c =================================================================== --- trunk/print_wiki.c 2009-10-06 13:00:00 UTC (rev 748) +++ trunk/print_wiki.c 2009-10-06 20:23:29 UTC (rev 749) @@ -142,6 +142,8 @@ { "GIGABYTE", "GA-MA770T-UD3P", "http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ProductI…" }, { "Intel", "EP80759", NULL }, { "Jetway", "J7F4K1G5D-PB", "http://www.jetway.com.tw/jetway/system/productshow2.asp?id=389&proname=J7F4…" }, + { "MSI", "MS-6153", "http://www.msi.com/index.php?func=proddesc&maincat_no=1&cat2_no=&cat3_no=&p…" }, + { "MSI", "MS-6156", "http://uk.ts.fujitsu.com/rl/servicesupport/techsupport/boards/Motherboards/…" }, { "MSI", "MS-6570 (K7N2)", "http://www.msi-computer.de/index.php?func=proddesc&prod_no=519&maincat_no=1" }, { "MSI", "MS-7065", "http://browse.geekbench.ca/geekbench2/view/53114" }, { "MSI", "MS-7168 (Orion)", "http://support.packardbell.co.uk/uk/item/index.php?i=spec_orion&pi=platform…" }, @@ -190,6 +192,7 @@ { "VIA", "VB700X", "http://www.via.com.tw/en/products/mainboards/motherboards.jsp?motherboard_i…" }, /* Verified working boards that DO need write-enables. */ + { "Abit", "IP35", "http://www.abit.com.tw/page/en/motherboard/motherboard_detail.php?fMTYPE=LG…" }, { "Acorp", "6A815EPD", "http://web.archive.org/web/20021206163652/www.acorp.com.tw/English/default.…" }, { "agami", "Aruma", "http://web.archive.org/web/20080212111524/http://www.agami.com/site/ais-600…" }, { "Albatron", "PM266A Pro", "http://www.albatron.com.tw/English/Product/MB/pro_detail.asp?rlink=Overview…" }, /* FIXME */ @@ -197,13 +200,17 @@ { "Artec Group", "DBE61", "http://wiki.thincan.org/DBE61" }, { "Artec Group", "DBE62", "http://wiki.thincan.org/DBE62" }, { "ASUS", "A7V600-X", "http://www.asus.com/product.aspx?P_ID=L2XYS0rmtCjeOr4k" }, + { "ASUS", "A7V8X", "http://www.asus.com/product.aspx?P_ID=qfpaGrAy2kLVo0f2" }, { "ASUS", "A7V8X-MX SE", "http://www.asus.com/product.aspx?P_ID=1guVBT1qV5oqhHyZ" }, { "ASUS", "P4B266", "http://www.ciao.co.uk/ASUS_Intel_845D_Chipset_P4B266__5409807#productdetail" }, { "ASUS", "P4P800-E Deluxe", "http://www.asus.com/product.aspx?P_ID=INIJUvLlif7LHp3g" }, + { "ASUS", "P5ND2-SLI Deluxe", "http://www.asus.com/product.aspx?P_ID=WY7XroDuUImVbgp5" }, { "ASUS", "P5A", "ftp://ftp.asus.com.tw/pub/ASUS/mb/sock7/ali/p5a/" }, { "Biostar", "P4M80-M4", "http://www.biostar-usa.com/mbdetails.asp?model=p4m80-m4" }, + { "Dell", "PowerEdge 1850", "http://support.dell.com/support/edocs/systems/pe1850/en/index.htm" }, { "Elitegroup", "K7VTA3", "http://www.ecs.com.tw/ECSWebSite/Products/ProductsDetail.aspx?detailid=264&…" }, { "EPoX", "EP-8K5A2", "http://www.epox.com/product.asp?ID=EP-8K5A2" }, + { "EPoX", "EP-8RDA3+", "http://www.epox.com/product.asp?ID=EP-8RDA3plus" }, { "EPoX", "EP-BX3", "http://www.epox.com/product.asp?ID=EP-BX3" }, { "GIGABYTE", "GA-2761GXDK", "http://www.computerbase.de/news/hardware/mainboards/amd-systeme/2007/mai/gi…" }, { "GIGABYTE", "GA-7VT600", "http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ProductI…" },

1 0

6A815EPD lspci
by Jonathan A. Kollasch 06 Oct '09

06 Oct '09

Hi, Attached is lspci -vvnnxxxx output for a Acorp 6A815EPD. The 3Com NIC and ATI video are not part of the motherboard. Jonathan Kollasch

1 0

[Patch] Board enable for Asus P4B266LM.
by Luc Verhaegen 06 Oct '09

06 Oct '09

Allan, please try this patch. If this works, please reply with: Acked-by: Allan Bjorklund <abjork(a)speakeasy.net> Thanks, Luc Verhaegen.

2 1

Tightening up the board enable table.
by Luc Verhaegen 06 Oct '09

06 Oct '09

We have had board enable routines and our board enable table for more than two years now. And thanks to the good work of carldani and uwe and the release(s) (one done, one pending) this list is growing fast. We have 47 boards in our board enable table today. Board enables have the following format today: <pci id set 1> <pci id set 2> <coreboot name> <pretty print name> <board enable callback> one pci id set is the following: <vendor> <device> <card/subsystem vendor> <card/subsystem device> While most of the time, the vendor and device ids are fixed, the subsystem pair is set by the bios. It can be write-once or it can be locked by some other bit in the device config space. Because subsystem ids are relatively new to the pci spec (second half of the 90s iirc), not all vendors have been using them. Most last-millenium boards will not have them filled in. Or often vendor bioses just copy main ids over. Many consumer board makers today do their job really well while embedded board makers tend to ignore subsystem ids. Because of what i saw in my unichrome graphics driver (where i started using subsystem ids in 2004 to see which outputs were wired up), i knew that matching a single device was never going to work. So two were added here, but we only require a single set to be filled in. There is a situation with some gigabyte boards for which carldani suggested to add a third set, which is imho a good solution, but we are trying to hold this one off until we really need it. After the pair of pci ids, there are the board names. The coreboot name is used two-fold. On a coreboot rom, this name is matched to the coreboot info. On a legacy bios, the user can provide the board name on the command line and therefor force flashrom to use a specific board enable. In both cases, the device and vendor ids of pci devices are matched as well as a safeguard. So, three ways of matching boards: * main ids + subsystem ids. * legacy bios + command line name + main ids (ignoring subsystem ids). * coreboot + coreboot name + main ids (ignoring subsystem ids). Now that we have a more sizable table and a bigger and quickly growing userbase, i believe that we should look into tightening this up. We are no longer part of the main coreboot project and are reaching a changed public now with the exposure we are getting. Average Joe User might end up abusing our board enable table and land himself in trouble and then will blame us. While we of course are not liable, it is still bad publicity and something we should try to avoid. We also can see how board matches have been written over time, and i believe that we should be stricter about them. Quite a few people have just added a single main pci id, and then added a coreboot name to the table as this was the absolute minimal effort required to make it work for them. This is how humans are, and how humans will continue to be, so we should make it harder for this to happen. So in order to make it safer for Average Joe User, and in order to force developers to be less lazy here, i propose some changes; * require 2 sets of pci-ids. Can anyone name a motherboard which has only a single pci device that even comes close to our target hardware (in as far as we have target hardware). By requiring 2 sets, we improve safety and we force developers to be less lazy. * if one value of any of the 4 subsystem ids is filled in, assume that the rest should be matched as is. When subsystem ids are not filled in correctly, they sometimes remain null. Null values should not mean "match anything" they should mean null when even one of the value is valid. I am a bit weary of adding a #define for 0xFFFF (the pciid "match anything"). I do not wish to encourage people to create an entry like: blah, blah, 0xFFFF, 0xFFFF, blah, blah, 0xFFFF, 0xFFFF and get away with it. Multiple similar boards should be matched separately. And, since we usually have more than just a few pci devices in our device tree, chances are extremely good that at least two of them can be matched in some way or another, without a catchall. * on legacy bioses, do not allow both pci subsystem ids and a name. The most efficient way to do this seems the following: If a name is provided, we should go over the table, checking for devices with both subsystem id sets nulled, and try to match the name. If the name matches, try to match main pci ids. * Add separate logic for coreboot name matching. This to still allow subsystem ids to be present, and thus to offset the previous point. We really will end up with three different ways of matching boards. Apart from actual code changes, we should apply the following: * Be extremely weary of patches. * We need at least an lspci -vvnnxxxx. We have started to do this anyway now, collecting info for our current table, while retaining info for future table alteration. * Do not accept missing subsystem ids for recent boards. Motherboards of this millenium tend to have subsystem ids filled in. * Usage of a coreboot name when coreboot is supported. Why would a coreboot developer set a separate write protect on the rom? The board enable could be valid though, but not for flash write protection. If developers want to bring up a board, and have this write protection disabling as a todo, then they can hack their own code into flashrom. Even if we only apply some of the above, we still need to clean up our board enable table. Here is a list of boards with questionable matching, as a quick list. I will be digging each of them out properly and try to contact the original authors for more information. If you are the original author and happen to be reading this, then by all means, feel free to contact us right away. Acorp 6A815EPD agami Aruma Artec Group DBE61 Artec Group DBE62 GIGABYTE GA-2761GXDK GIGABYTE GA-M57SLI-S4 GIGABYTE GA-M61P-S3 GIGABYTE GA-MA790FX-DQ6 HP DL145 G3 IBM x3455 IWILL DK8-HTX Kontron 986LCD-M Kontron 986LCD-M (yes, twice) MSI MS-6590 (KT4 Ultra) MSI MS-6712 (KT4V) MSI MS-7135 (K8N Neo3) VIA EPIA-N/NL VIA PC3500G The following two devices are known to be valid, as they predate pci subsystem ids: the ASUS P5A (which i own) and the EPoX EP-BX3. Luc Verhaegen.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom