[coreboot] GA-P35-DS3L - supported? (Console output included)
Harald Gutmann
harald.gutmann at gmx.net
Sun Jun 21 12:23:15 CEST 2009
On Sunday 21 June 2009 07:23:53 Drew Diller wrote:
> My system sits on a Gigabyte GA-P35-DS3L mainboard with an Intel Core
> 2 Duo E6750 CPU. I am wondering if you think it will work /
> anecdotally know it will work with coreboot, as I did not see the
> model on the "supported mainboards" page.
>
> Specs are down a ways, after my three questions:
>
> First: What's a guy to do if I screw the BIOS up? The BIOS chip is a
> SOP8 (I think?). It's soldered on, at any rate. I don't have a
> floppy drive. Searching (broader internet) has yielded varied and
> questionable results.
That's always the most interesting part. You NEED to have a good backup
solution, if something fails.
My recommendation on your mainboard would be to remove the original bios chip,
and put a soket for soic8 chips on the pads.
Then go and check out some soic8 chips, flash a new one (hot-swapping) with a
working (vendor) bios to get a bios chip which you can replace when something
goes wrong on the other part.
> Second: I am aware from prior experience that I have to set the RAM
> voltage to something other than the mainboard's factory default. I am
> confused where in the process of installing coreboot this sort of
> customization ability is afforded. A "newb, here's a link you
> overlooked" will suffice.
No idea on that, but I think that this can be done.
> Third: I see a lot more support for AMD than Intel. I didn't know
> about coreboot when purchasing parts two years ago. Should I
> generally be buying AMD hardware if I want to use coreboot in the long
> run? I don't have brand loyalty.
My way on buying the hardware was to look first @ coreboot and then buy.
AMD has friendly approach to coreboot and also commits to the project.
How the behavior of Intel is in that case? - I don't know.
> I apologize up front that "I only know what I know", so I might ask
> some stupid questions. I'm a Javascript author by trade (I wrote the
> DD_belatedPNG library, for example), I can read documentation... I
> just feel like I've missed something, as there is a _lot_ of it
> available on coreboot.org.
Doesn't matter, I have e.g no idea on JavaScript & DD_belatedPNG libraries.
> My motivation for using coreboot is (1) Ubuntu 9.04 boots in less time
> than my default BIOS routine takes, as a 10,000 RPM hard drive is
> pretty snappy and (2) I'll be buying a Sandisk G3 when they're finally
> available, which will make the default BIOS routine look even MORE
> ridiculous, and (3) I turn off power strips on a nightly basis.
>
> That said,
>
> Manufacturer's information:
> http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?Prod
>uctID=2599
>
> ~# lspci -tvnn
> -[0000:00]-+-00.0 Intel Corporation 82G33/G31/P35/P31 Express DRAM
> Controller [8086:29c0]
> +-01.0-[0000:01]----00.0 nVidia Corporation GeForce 8800
> GT [10de:0611]
> +-1a.0 Intel Corporation 82801I (ICH9 Family) USB UHCI
> Controller #4 [8086:2937]
> +-1a.1 Intel Corporation 82801I (ICH9 Family) USB UHCI
> Controller #5 [8086:2938]
> +-1a.2 Intel Corporation 82801I (ICH9 Family) USB UHCI
> Controller #6 [8086:2939]
> +-1a.7 Intel Corporation 82801I (ICH9 Family) USB2 EHCI
> Controller #2 [8086:293c]
> +-1b.0 Intel Corporation 82801I (ICH9 Family) HD Audio
> Controller [8086:293e]
There are 82801 southbridges in coreboot, but I don't know if any of those
will cover the 82801I.
> +-1c.0-[0000:02]--
> +-1c.3-[0000:03]----00.0 JMicron Technologies, Inc. JMB368
> IDE controller [197b:2368]
> +-1c.4-[0000:04]----00.0 Realtek Semiconductor Co., Ltd.
> RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168]
> +-1d.0 Intel Corporation 82801I (ICH9 Family) USB UHCI
> Controller #1 [8086:2934]
> +-1d.1 Intel Corporation 82801I (ICH9 Family) USB UHCI
> Controller #2 [8086:2935]
> +-1d.2 Intel Corporation 82801I (ICH9 Family) USB UHCI
> Controller #3 [8086:2936]
> +-1d.7 Intel Corporation 82801I (ICH9 Family) USB2 EHCI
> Controller #1 [8086:293a]
> +-1e.0-[0000:05]--
> +-1f.0 Intel Corporation 82801IB (ICH9) LPC Interface
> Controller [8086:2918]
> +-1f.2 Intel Corporation 82801IB (ICH9) 2 port SATA IDE
> Controller [8086:2921]
> +-1f.3 Intel Corporation 82801I (ICH9 Family) SMBus
> Controller [8086:2930]
> \-1f.5 Intel Corporation 82801I (ICH9 Family) 2 port SATA
> IDE Controller [8086:2926]
Hmm? Does Intel not show up northbridge devices in lspci?
> ~# superiotool -dV
> Found ITE IT8718F (id=0x8718, rev=0x4) at 0x2e
> Register dump:
> idx 20 21 22 23 24 2b
> val 87 18 04 10 00 00
> def 87 18 01 00 00 00
> 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 f1 f2 f3
> val 01 03 f8 04 00 50 00 7f
> def 00 03 f8 04 00 50 00 7f
> LDN 0x02 (COM2)
> idx 30 60 61 70 f0 f1 f2 f3
> val 00 00 00 00 00 50 00 7f
> def 00 02 f8 03 00 50 00 7f
> LDN 0x03 (Parallel port)
> idx 30 60 61 62 63 70 74 f0
> val 01 03 78 00 00 07 04 08
> def 00 03 78 07 78 07 03 03
> LDN 0x04 (Environment controller)
> idx 30 60 61 62 63 70 f0 f1 f2 f3 f4 f5 f6
> val 01 02 90 00 00 00 80 00 0a 00 a0 00 ff
> def 00 02 90 02 30 09 00 00 00 00 00 NA NA
> LDN 0x05 (Keyboard)
> idx 30 60 61 62 63 70 71 f0
> val 01 00 60 00 64 01 02 68
> def 01 00 60 00 64 01 02 00
> LDN 0x06 (Mouse)
> idx 30 70 71 f0
> val 01 0c 02 00
> def 00 0c 02 00
> LDN 0x07 (GPIO)
> idx 25 26 27 28 29 2a 2c 60 61 62 63 64 65 70 71 72 73 74 b0 b1 b2
> b3 b4 b5 b8 b9 ba bb bc bd c0 c1 c2 c3 c4 c5 c8 c9 ca cb cc e0 e1
> e2 e3 e4 e5 e6 e7 f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff
> val 41 df 00 03 88 01 1d 00 00 08 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 81 c0 00 00 01 00 40 1f 00 03 08 00 00 11 00 03 08 00 00
> 00 00 00 00 00 00 10 40 00 00 00 00 08 00 00 00 00 00 2a 00 00 00
> def 01 00 00 40 00 00 00 00 00 00 00 00 00 00 00 20 38 00 00 00 00
> 00 00 00 00 00 00 00 00 00 01 00 00 40 00 00 01 00 00 40 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 NA 00 00 00
> LDN 0x0a (Consumer IR)
> idx 30 60 61 70 f0
> val 00 03 10 0b 06
> def 00 03 10 0b 00
>
>
> ~# flashrom -V
> Calibrating delay loop... 760M loops per second, 100 myus = 200 us. OK.
> No coreboot table found.
> Found chipset "Intel ICH9", enabling flash write...
> BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x0
>
> Root Complex Register Block address = 0xfed1c000
> GCS = 0x464: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x1
> (SPI) Top Swap : not enabled
> SPIBAR = 0xfed1c000 + 0x3800
> 0x00: 0x1fff (HSFS)
> FLOCKDN 1, FDV 1, FDOPSS 0, SCIP 0, BERASE 0, AEL 0, FCERR 0, FDONE 0
> 0x50: 0x00000202 (FRAP)
> BMWAG 0, BMRAG 0, BRWA 2, BRRA 2
> 0x54: 0x00001fff (FREG0)
> 0x58: 0x00001fff (FREG1)
> 0x5C: 0x00001fff (FREG2)
> 0x60: 0x00001fff (FREG3)
> 0x64: 0x00001fff (FREG4)
> 0x74: 0x00000000 (PR0)
> 0x78: 0x00000000 (PR1)
> 0x7C: 0x00000000 (PR2)
> 0x80: 0x00000000 (PR3)
> 0x84: 0x00000000 (PR4)
> 0xB0: 0x00000000 (FDOC)
> Programming OPCODES... done
> SPI Read Configuration: prefetching disabled, caching enabled, OK.
> Probing for AMD Am29F002(N)BB, 256 KB: probe_jedec: id1 0xff, id2
> 0xff, id1 parity violation
> Probing for AMD Am29F002(N)BT, 256 KB: probe_jedec: id1 0xff, id2
> 0xff, id1 parity violation
> 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 AT25DF021, 256 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT25DF041A, 512 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT25DF081, 1024 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT25DF161, 2048 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT25DF321, 4096 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT25DF321A, 4096 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT25DF641, 8192 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT25F512B, 64 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT25FS010, 128 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT25FS040, 512 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT26DF041, 512 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT26DF081A, 1024 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT26DF161, 2048 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT26DF161A, 2048 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT26F004, 512 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> 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 AT45CS1282, 16896 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT45DB011D, 128 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT45DB021D, 256 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT45DB041D, 512 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT45DB081D, 1024 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT45DB161D, 2048 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT45DB321C, 4224 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT45DB321D, 4096 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Atmel AT45DB642D, 8192 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> 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 AMIC A25L40P, 512 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0xff, id2 0xff
> Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0xff, id2 0xff
> Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
> Probing for AMIC A49LF040A, 512 KB: probe_jedec: id1 0xff, id2 0xff,
> id1 parity violation
> 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 MBM29F004BC, 512 KB: probe_jedec: id1 0xff, id2
> 0xff, id1 parity violation
> Probing for Fujitsu MBM29F004TC, 512 KB: probe_jedec: id1 0xff, id2
> 0xff, id1 parity violation
> Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0xff, id2
> 0xff 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 0x24, id2 0x89
> Probing for Macronix MX25L512, 64 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Macronix MX25L1005, 128 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Macronix MX25L2005, 256 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Macronix MX25L4005, 512 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Macronix MX25L8005, 1024 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Chip status register is 00
> Chip status register: Status Register Write Disable (SRWD) is not set
> Chip status register: Bit 6 is not set
> Chip status register: Bit 5 / Block Protect 3 (BP3) is not set
> Chip status register: Bit 4 / Block Protect 2 (BP2) is not set
> Chip status register: Bit 3 / Block Protect 1 (BP1) is not set
> Chip status register: Bit 2 / Block Protect 0 (BP0) is not set
> Chip status register: Write Enable Latch (WEL) is not set
> Chip status register: Write In Progress (WIP/BUSY) is not set
> Found chip "Macronix MX25L8005" (1024 KB) at physical address 0xfff00000.
Here is the chip you've. This is nearly the same which I've here, just the 1Mb
version of it.
> Probing for Macronix MX25L1605, 2048 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Macronix MX25L3205, 4096 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Macronix MX25L6405, 8192 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0x24, id2 0x89
> Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0x24, id2 0x89
> Probing for Macronix MX29LV040C, 512 KB: probe_29f002: id1 0x24, id2 0x89
> Probing for Numonyx M25PE10, 128 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Numonyx M25PE20, 256 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Numonyx M25PE40, 256 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Numonyx M25PE80, 1024 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Numonyx M25PE16, 2048 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for PMC Pm25LV010, 128 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for PMC Pm25LV016B, 2048 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for PMC Pm25LV020, 256 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for PMC Pm25LV040, 512 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for PMC Pm25LV080B, 1024 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for PMC Pm25LV512, 64 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for PMC Pm49FL002, 256 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0x24, id2 0x89
> Probing for Spansion S25FL016A, 2048 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for SST SST25VF016B, 2048 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for SST SST25VF032B, 4096 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for SST SST25VF040B, 512 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for SST SST25VF080B, 1024 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0x24, id2 0x89
> Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0x24, id2
> 0x89, id1 parity violation
> Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0x24, id2
> 0x89, id1 parity violation
> Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0x24, id2
> 0x89, id1 parity violation
> Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0x24, id2 0x89
> Probing for SST SST49LF008A, 1024 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0x24, id2 0x89
> Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0x24, id2 0x89
> Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST49LF080A, 1024 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0x24, id2 0x89
> Probing for ST M25P05-A, 64 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for ST M25P10-A, 128 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for ST M25P20, 256 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for ST M25P40, 512 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for ST M25P40-old, 512 KB: RDID returned c2 20 14.
> Probing for ST M25P80, 1024 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for ST M25P16, 2048 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for ST M25P32, 4096 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for ST M25P64, 8192 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for ST M25P128, 16384 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for ST M29F002B, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1
> parity violation
> Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0x24, id2 0x89
> Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0x24, id2 0x2d
> Probing for ST M29W010B, 128 KB: probe_jedec: id1 0x24, id2 0x89, id1
> parity violation
> Probing for ST M29W040B, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1
> parity violation
> Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0x24, id2 0x89
> Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0x24, id2 0x89
> Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0x24, id2 0x89
> Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0x24, id2 0x89
> Probing for ST M50FW002, 256 KB: probe_49lfxxxc: id1 0x24, id2 0x89
> Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0x24, id2 0x89
> Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x24, id2 0x89
> Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0x24, id2 0x89
> Probing for ST M50LPW116, 2048 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for SyncMOS S29C31004T, 512 KB: probe_jedec: id1 0x24, id2
> 0x89, id1 parity violation
> Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0x24, id2
> 0x89, id1 parity violation
> Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0x24, id2
> 0x89, id1 parity violation
> Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0x24, id2
> 0x89, id1 parity violation
> Probing for Winbond W25x10, 128 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Winbond W25x20, 256 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Winbond W25x40, 512 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Winbond W25x80, 1024 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Winbond W29C011, 128 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0x24, id2 0x89,
> 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 0x24, id2 0x89,
> id1 parity violation
> Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0x24, id2
> 0x89, id1 parity violation
> Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0x24, id2
> 0x89, id1 parity violation
> Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0x24, id2
> 0x89, id1 parity violation
> Probing for Winbond W49F002U, 256 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0x24, id2 0x89,
> id1 parity violation
> Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0x24, id2
> 0x89, id1 parity violation
> Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: vid 0x24, did
> 0x89 Probing for Winbond W39V080FA (dual mode), 512 KB:
> probe_winbond_fwhub: vid 0x24, did 0x89
> Probing for Atmel unknown Atmel SPI chip, 0 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for EON unknown EON SPI chip, 0 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for Macronix unknown Macronix SPI chip, 0 KB: RDID returned c2 20
> 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for PMC unknown PMC SPI chip, 0 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for SST unknown SST SPI chip, 0 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> Probing for ST unknown ST SPI chip, 0 KB: RDID returned c2 20 14.
> probe_spi_rdid_generic: id1 0xc2, id2 0x2014
> No operations were specified.
Flashrom would work out of the box for your board, that's a good starting
point.
Kind regards,
Harald
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20090621/971455f9/attachment.sig>
More information about the coreboot
mailing list