[coreboot] Coreboot Support for MSI KT4 Ultra (MS-6590)

Sean Nelson audiohacked at gmail.com
Sun Nov 15 01:38:45 CET 2009


Sadly, We don't have access to the Programming Documentation needed
for the KT4 Chipset. Until VIA releases the required chipset docs, we
can't write support for your motherboard.

I, too, would like to see support for it, since I have the same board
sitting useless somewhere around here.

On Sat, Nov 14, 2009 at 4:29 PM, freeman2411 <freeman2411 at gmail.com> wrote:
> Hi Guys!
>
> Could you please help me with my MSI Mainboard. I would really like to get
> it running on this Mainboard.
>
> 1.)
> MSI KT4 Ultra (MS-6590)
> AMD Athlon XP 2200+
>
> 2.)
> -[0000:00]-+-00.0  VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host
> Bridge [1106:3189]
>            +-01.0-[0000:01]--
>            +-0a.0  Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
> [10ec:8139]
>            +-0c.0  C-Media Electronics Inc CM8738 [13f6:0111]
>            +-10.0  VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
> [1106:3038]
>            +-10.1  VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
> [1106:3038]
>            +-10.2  VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
> [1106:3038]
>            +-10.3  VIA Technologies, Inc. USB 2.0 [1106:3104]
>            +-11.0  VIA Technologies, Inc. VT8235 ISA Bridge [1106:3177]
>            \-11.1  VIA Technologies, Inc.
> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571]
>
>
> 3.)
> superiotool r3695
> Probing for ALi Super I/O at 0x3f0...
>   Failed. Returned data: id=0xffff, rev=0xff
> 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=0x50fe, id=0x1660
> 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...
>   Failed. Returned data: id=0xffff, rev=0xf
> Probing for ITE Super I/O (init=0x87,0x87) at 0x2e...
>   Failed. Returned data: id=0x6016, rev=0xf
> Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x4e...
>   Failed. Returned data: id=0xffff, rev=0xf
> Probing for ITE Super I/O (init=0x87,0x87) at 0x4e...
>   Failed. Returned data: id=0xffff, rev=0xf
> Probing for ITE Super I/O (init=legacy/it8661f) at 0x370...
>   Failed. Returned data: id=0xffff, rev=0xf
> Probing for ITE Super I/O (init=legacy/it8671f) at 0x370...
>   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 NSC Super I/O at 0x15c...
>   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=0xff, rev=0xff
> Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x3f0...
>   Failed. Returned data: id=0xff, rev=0xff
> 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...
> Found Winbond W83697HF/F/HG (id=0x60, rev=0x16) at 0x2e
> Register dump:
> idx 20 21 22 23 24 25 26 28  29 2a
> val 60 16 ff fe 50 00 00 00  00 ff
> def 60 NA ff 00 00 00 00 00  00 MM
> LDN 0x00 (Floppy)
> idx 30 60 61 70 74 f0 f1 f2  f4 f5
> val 01 03 f0 06 02 0e 00 ff  00 00
> def 01 03 f0 06 02 0e 00 ff  00 00
> LDN 0x01 (Parallel port)
> idx 30 60 61 70 74 f0
> val 01 03 78 07 03 3a
> def 01 03 78 07 04 3f
> LDN 0x02 (COM1)
> idx 30 60 61 70 f0
> val 01 03 f8 04 00
> def 01 03 f8 04 00
> LDN 0x03 (COM2)
> idx 30 60 61 70 f0 f1
> val 01 02 f8 03 00 40
> def 01 02 f8 03 00 00
> LDN 0x06 (Consumer IR)
> idx 30 60 61 70
> val 00 00 00 00
> def 00 00 00 00
> LDN 0x07 (Game port, GPIO 1)
> idx 30 60 61 62 63 f0 f1 f2
> val 00 00 00 00 00 ff ff ff
> def 00 02 01 00 00 ff 00 00
> LDN 0x08 (MIDI port, GPIO 5)
> idx 30 60 61 62 63 70 f0 f1  f2 f3 f4 f5
> val 00 00 00 00 00 00 ff ff  ff 00 00 00
> def 00 03 30 00 00 09 ff 00  00 00 00 00
> LDN 0x09 (GPIO 2, GPIO 3, GPIO 4)
> idx 30 60 61 f0 f1 f2 f3 f4  f5 f6 f7 f8 f5
> val 00 00 00 ff ff ff ff ff  ff ff ff ff ff
> def 00 00 00 ff 00 00 ff 00  00 ff 00 00 00
> LDN 0x0a (ACPI)
> idx 30 70 e0 e1 e2 e5 e6 e7  f0 f1 f3 f4 f6 f7 f9
> val 00 00 00 00 ff 00 00 00  00 8f 0f 00 00 00 00
> def 00 00 00 00 NA 00 00 00  00 00 00 00 00 00 00
> LDN 0x0b (Hardware monitor)
> idx 30 60 61 70
> val 01 02 90 00
> def 00 00 00 00
> 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=0xff/0x0f, rev=0xff
> Probing for Winbond Super I/O (init=0x89) at 0x3f0...
>   Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff
> Probing for Winbond Super I/O (init=0x86,0x86) at 0x3f0...
>   Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff
> Probing for Winbond Super I/O (init=0x87,0x87) at 0x3f0...
>   Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff
> 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
>
> 4.)
> Calibrating delay loop... 620M loops per second, 100 myus = 200 us. OK.
> No coreboot table found.
> Found chipset "VIA VT8235", enabling flash write... 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: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT25DF041A, 512 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT25DF081, 1024 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT25DF161, 2048 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT25DF321, 4096 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT25DF321A, 4096 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT25DF641, 8192 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT25F512B, 64 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT25FS010, 128 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT25FS040, 512 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT26DF041, 512 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT26DF081A, 1024 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT26DF161, 2048 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT26DF161A, 2048 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT26F004, 512 KB: spi_command called, but no SPI
> chipset/strapping detected
> 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: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT45DB011D, 128 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT45DB021D, 256 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT45DB041D, 512 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT45DB081D, 1024 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT45DB161D, 2048 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT45DB321C, 4224 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT45DB321D, 4096 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Atmel AT45DB642D, 8192 KB: spi_command called, but no SPI
> chipset/strapping detected
> 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: 4b ID not supported on this SPI controller
> 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 0xff, id2 0xff
> Probing for Macronix MX25L512, 64 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Macronix MX25L1005, 128 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Macronix MX25L2005, 256 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Macronix MX25L4005, 512 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Macronix MX25L8005, 1024 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Macronix MX25L1605, 2048 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Macronix MX25L3205, 4096 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Macronix MX25L6405, 8192 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0xff, id2 0xff
> Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0xff, id2 0xff
> Probing for Macronix MX29LV040C, 512 KB: probe_29f002: id1 0xff, id2 0xff
> Probing for Numonyx M25PE10, 128 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Numonyx M25PE20, 256 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Numonyx M25PE40, 256 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Numonyx M25PE80, 1024 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Numonyx M25PE16, 2048 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for PMC Pm25LV010, 128 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for PMC Pm25LV016B, 2048 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for PMC Pm25LV020, 256 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for PMC Pm25LV040, 512 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for PMC Pm25LV080B, 1024 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for PMC Pm25LV512, 64 KB: spi_command called, but no SPI
> chipset/strapping 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/strapping detected
> Probing for SST SST25VF016B, 2048 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for SST SST25VF032B, 4096 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for SST SST25VF040B, 512 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for SST SST25VF080B, 1024 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0xff, id2 0xff
> Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0x1b, id2 0xf0, id1
> parity violation
> Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0x1b, id2 0xf0, 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 0x1b, id2 0xf0, 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 0xe8, id2 0x2f, id1
> parity violation
> Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0x1b, id2 0xf0, 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/strapping detected
> Probing for ST M25P10-A, 128 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for ST M25P20, 256 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for ST M25P40, 512 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for ST M25P40-old, 512 KB: spi_command called, but no SPI
> chipset/strapping detected
> spi_command called, but no SPI chipset/strapping detected
> Probing for ST M25P80, 1024 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for ST M25P16, 2048 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for ST M25P32, 4096 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for ST M25P64, 8192 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for ST M25P128, 16384 KB: spi_command called, but no SPI
> chipset/strapping 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 0x1b, id2 0xf0, 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 M50FW002, 256 KB: probe_49lfxxxc: 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 0x1b, id2 0xf0, 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/strapping detected
> Probing for Winbond W25x20, 256 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Winbond W25x40, 512 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Winbond W25x80, 1024 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Winbond W29C011, 128 KB: probe_jedec: id1 0x1b, id2 0xf0, 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 W39V040C, 512 KB: probe_w39v040c: 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 Atmel unknown Atmel SPI chip, 0 KB: spi_command called, but no
> SPI chipset/strapping detected
> Probing for EON unknown EON SPI chip, 0 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for Macronix unknown Macronix SPI chip, 0 KB: spi_command called,
> but no SPI chipset/strapping detected
> Probing for PMC unknown PMC SPI chip, 0 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for SST unknown SST SPI chip, 0 KB: spi_command called, but no SPI
> chipset/strapping detected
> Probing for ST unknown ST SPI chip, 0 KB: spi_command called, but no SPI
> chipset/strapping 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.
>
> 5.)
> http://www.msi-computer.de/index.php?func=proddesc&maincat_no=1&cat2_no=&cat3_no=&prod_no=502#
>
> 6.)
> Sorry I can't give more hints at this time. :-(
>
> Thank you for your help!
>
> Greetings
>
>
> Freeman
>
> --
> coreboot mailing list: coreboot at coreboot.org
> http://www.coreboot.org/mailman/listinfo/coreboot
>




More information about the coreboot mailing list