Chip model thinkpad x60s

[Tim Zander]

Dear Corebooters,

I want to flash coreboot onto my x60s.
Is the only way to find out the chip model of my x60s by disassembling 
and inspecting?
If I have the data written on my chip, what I have to then to find the 
information necessary to do the first part of the flashing instruction of
http://www.coreboot.org/Lenovo_x60x ?
What do I need to change in the patch then?
Or don't I need to find out about the chip: 
http://www.coreboot.org/pipermail/coreboot/2013-January/073801.html?
You see I'm totally confused thanks for enlightment.

Best wishes,

Tim

http://www.coreboot.org/Lenovo_x60x

[Peter Stuge]

Tim Zander wrote:
> I want to flash coreboot onto my x60s.

Note that the wiki page you refer to does *NOT* include any
instructions for building coreboot itself. If you want SeaBIOS for
BIOS compatibility and graphics during booting then you must make
sure to build a coreboot.rom file which includes the correct VGA BIOS
blob for your machine. After you've made a backup of your factory
BIOS you can use bios_extract to take the backup apart, and one of
the oprom files will be the correct VGA BIOS.
> Is the only way to find out the chip model of my x60s by
> disassembling and inspecting?

Likely SST25VF016B.
> what I have to then to find the information necessary to do the
> first part of the flashing instruction of
> http://www.coreboot.org/Lenovo_x60x ?
> What do I need to change in the patch then?

Try this patch on top of current flashrom svn: http://dpaste.com/1216583/

//Peter

[Tim Zander]

On 06/07/2013 12:22 PM, Peter Stuge wrote:
> Tim Zander wrote:
> > I want to flash coreboot onto my x60s.
>
> Note that the wiki page you refer to does *NOT* include any
> instructions for building coreboot itself. If you want SeaBIOS for
> BIOS compatibility and graphics during booting then you must make
> sure to build a coreboot.rom file which includes the correct VGA BIOS
> blob for your machine. After you've made a backup of your factory
> BIOS you can use bios_extract to take the backup apart, and one of
> the oprom files will be the correct VGA BIOS.

I'm aware of this. Without the VGA BIOS Blob I just would have no 
monitor output in boot, right?
> > Is the only way to find out the chip model of my x60s by
> > disassembling and inspecting?
>
> Likely     SST25VF016B
> .
> > what I have to then to find the information necessary to do the
> > first part of the flashing instruction of
> > http://www.coreboot.org/Lenovo_x60x ?
> > What do I need to change in the patch then?
>
> Try this patch on top of current flashrom svn: http://dpaste.com/1216583/

I did this, patching and installing of flashrom went fine.
But now I have the following:

tim@tim-ThinkPad-X60s:~/flash$ sudo flashrom -p internal -r factory.bin
flashrom v0.9.6.1-r1675 on Linux 3.2.0-38-generic-pae (i686)
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... delay loop is unreliable, trying to continue OK.
Found chipset "Intel ICH7M". Enabling flash write... WARNING: SPI 
Configuration Lockdown activated.

[Tim Zander]

On 06/07/2013 02:02 PM, Tim Zander wrote:
> On 06/07/2013 12:22 PM, Peter Stuge wrote:
> > Tim Zander wrote:
> > > I want to flash coreboot onto my x60s.
> >
> > Note that the wiki page you refer to does *NOT* include any
> > instructions for building coreboot itself. If you want SeaBIOS for
> > BIOS compatibility and graphics during booting then you must make
> > sure to build a coreboot.rom file which includes the correct VGA BIOS
> > blob for your machine. After you've made a backup of your factory
> > BIOS you can use bios_extract to take the backup apart, and one of
> > the oprom files will be the correct VGA BIOS.
>
> I'm aware of this. Without the VGA BIOS Blob I just would have no 
> monitor output in boot, right?
> > > Is the only way to find out the chip model of my x60s by
> > > disassembling and inspecting?
> >
> > Likely        SST25VF016B
> > .
> > > what I have to then to find the information necessary to do the
> > > first part of the flashing instruction of
> > > http://www.coreboot.org/Lenovo_x60x ?
> > > What do I need to change in the patch then?
> >
> > Try this patch on top of current flashrom svn: 
> > http://dpaste.com/1216583/
>
> I did this, patching and installing of flashrom went fine.
> But now I have the following:
>
> tim@tim-ThinkPad-X60s:~/flash$ sudo flashrom -p internal -r factory.bin
> flashrom v0.9.6.1-r1675 on Linux 3.2.0-38-generic-pae (i686)
> flashrom is free software, get the source code at http://www.flashrom.org
>
> Calibrating delay loop... delay loop is unreliable, trying to continue 
> OK.
> Found chipset "Intel ICH7M". Enabling flash write... WARNING: SPI 
> Configuration Lockdown activated.

I accidentally emailed this to Peter's email address.
He responded that this is probably because I have another chip then the 
SST25VF016B.
and told me to look at the output of flashrom -p internal -V:

flashrom v0.9.6.1-r1675 on Linux 3.2.0-38-generic-pae (i686)
flashrom is free software, get the source code at http://www.flashrom.org

flashrom was built with libpci 3.1.8, GCC 4.6.3, little endian
Command line (3 args): flashrom -p internal -V
Calibrating delay loop... OS timer resolution is 1 usecs, 962M loops per 
second, delay more than 10% too short (got 88% of expected delay), 
recalculating... 967M loops per second, delay more than 10% too short 
(got 89% of expected delay), recalculating... 966M loops per second, 
delay more than 10% too short (got 88% of expected delay), 
recalculating... 960M loops per second, delay more than 10% too short 
(got 88% of expected delay), recalculating... 977M loops per second, 
delay loop is unreliable, trying to continue 10 myus = 10 us, 100 myus = 
104 us, 1000 myus = 1029 us, 10000 myus = 9766 us, 4 myus = 5 us, OK.
Initializing internal programmer
No coreboot table found.
DMI string system-manufacturer: "LENOVO"
DMI string system-product-name: "1703Y66"
DMI string system-version: "ThinkPad X60s"
DMI string baseboard-manufacturer: "LENOVO"
DMI string baseboard-product-name: "1703Y66"
DMI string baseboard-version: "Not Available"
DMI string chassis-type: "Notebook"
Laptop detected via DMI.
Whitelisted laptop detected.
Found chipset "Intel ICH7M" with PCI ID 8086:27b9. Enabling flash write...
0xfff80000/0xffb80000 FWH IDSEL: 0x0
0xfff00000/0xffb00000 FWH IDSEL: 0x0
0xffe80000/0xffa80000 FWH IDSEL: 0x1
0xffe00000/0xffa00000 FWH IDSEL: 0x1
0xffd80000/0xff980000 FWH IDSEL: 0x1
0xffd00000/0xff900000 FWH IDSEL: 0x2
0xffc80000/0xff880000 FWH IDSEL: 0x4
0xffc00000/0xff800000 FWH IDSEL: 0x4
0xff700000/0xff300000 FWH IDSEL: 0x4
0xff600000/0xff200000 FWH IDSEL: 0x5
0xff500000/0xff100000 FWH IDSEL: 0x6
0xff400000/0xff000000 FWH IDSEL: 0x7
0xfff80000/0xffb80000 FWH decode enabled
0xfff00000/0xffb00000 FWH decode enabled
0xffe80000/0xffa80000 FWH decode enabled
0xffe00000/0xffa00000 FWH decode enabled
0xffd80000/0xff980000 FWH decode enabled
0xffd00000/0xff900000 FWH decode enabled
0xffc80000/0xff880000 FWH decode enabled
0xffc00000/0xff800000 FWH decode enabled
0xff700000/0xff300000 FWH decode disabled
0xff600000/0xff200000 FWH decode disabled
0xff500000/0xff100000 FWH decode disabled
0xff400000/0xff000000 FWH decode disabled
Maximum FWH chip size: 0x100000 bytes
BIOS_CNTL = 0x01: BIOS Lock Enable: disabled, BIOS Write Enable: enabled
Root Complex Register Block address = 0xfed1c000
GCS = 0x200460: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 
0x1 (SPI)
Top Swap : not enabled
SPIBAR = 0xfed1c000 + 0x3020
0x00: 0x8004     (SPIS)
0x02: 0x4040     (SPIC)
0x04: 0x00000000 (SPIA)
0x08: 0x00141414 (SPID0)
0x0c: 0x00000000 (SPID0+4)
0x10: 0x00000000 (SPID1)
0x14: 0x00000000 (SPID1+4)
0x18: 0x00000000 (SPID2)
0x1c: 0x00000000 (SPID2+4)
0x20: 0x00000000 (SPID3)
0x24: 0x00000000 (SPID3+4)
0x28: 0x00000000 (SPID4)
0x2c: 0x00000000 (SPID4+4)
0x30: 0x00000000 (SPID5)
0x34: 0x00000000 (SPID5+4)
0x38: 0x00000000 (SPID6)
0x3c: 0x00000000 (SPID6+4)
0x40: 0x00000000 (SPID7)
0x44: 0x00000000 (SPID7+4)
0x50: 0x00000000 (BBAR)
0x54: 0x0606     (PREOP)
0x56: 0x163b     (OPTYPE)
0x58: 0x05d80302 (OPMENU)
0x5c: 0x0001d8ab (OPMENU+4)
0x60: 0x80fff1f0 (PBR0)
0x64: 0x00000000 (PBR1)
0x68: 0x00000000 (PBR2)
WARNING: SPI Configuration Lockdown activated.
Reading OPCODES... done
SPI Read Configuration: prefetching disabled, caching enabled, OK.
The following protocols are supported: SPI.
Probing for AMIC A25L05PT, 64 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L05PU, 64 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L10PT, 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L10PU, 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L20PT, 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L20PU, 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L40PT, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L40PU, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L80P, 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L16PT, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L16PU, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L512, 64 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L010, 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L020, 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L040, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L080, 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L016, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25L032, 4096 kB: Invalid OPCODE 0x9f, will not execute.
Probing for AMIC A25LQ032, 4096 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT25DF021, 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT25DF041A, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT25DF081, 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT25DF081A, 1024 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Atmel AT25DF161, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT25DF321, 4096 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT25DF321A, 4096 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Atmel AT25DF641(A), 8192 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Atmel AT25DQ161, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT25F512, 64 kB: Invalid OPCODE 0x15, will not execute.
Probing for Atmel AT25F512A, 64 kB: Invalid OPCODE 0x15, will not execute.
Probing for Atmel AT25F512B, 64 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT25F1024(A), 128 kB: Invalid OPCODE 0x15, will not 
execute.
Probing for Atmel AT25F2048, 256 kB: Invalid OPCODE 0x15, will not execute.
Probing for Atmel AT25F4096, 512 kB: Invalid OPCODE 0x15, will not execute.
Probing for Atmel AT25FS010, 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT25FS040, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT26DF041, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT26DF081A, 1024 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Atmel AT26DF161, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT26DF161A, 2048 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Atmel AT26F004, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT45CS1282, 16896 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Atmel AT45DB011D, 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT45DB021D, 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT45DB041D, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Atmel AT45DB081D, 1024 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Atmel AT45DB161D, 2048 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Atmel AT45DB321C, 4224 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Atmel AT45DB321D, 4096 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Atmel AT45DB642D, 8192 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for ESMT F25L008A, 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B05, 64 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B05T, 64 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B10, 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B10T, 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B20, 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B20T, 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B40, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B40T, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B80, 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B80T, 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B16, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B16T, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B32, 4096 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B32T, 4096 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B64, 8192 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25B64T, 8192 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25F05, 64 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25F10, 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25F20, 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25F40, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25F80, 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25F16, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25F32, 4096 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25F64, 8192 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25Q40, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25Q80(A), 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25Q16, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25Q32(A/B), 4096 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Eon EN25Q64, 8192 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25Q128, 16384 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25QH16, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Eon EN25QH32, 4096 kB: Invalid OPCODE 0x9f, will not execute.
Probing for GigaDevice GD25Q20, 256 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for GigaDevice GD25Q40, 512 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for GigaDevice GD25Q80(B), 1024 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for GigaDevice GD25Q16, 2048 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for GigaDevice GD25Q32(B), 4096 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for GigaDevice GD25Q64(B), 8192 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for GigaDevice GD25Q128B, 16384 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for GigaDevice GD25LQ32, 4096 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Intel 25F160S33B8, 2048 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Intel 25F160S33T8, 2048 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Intel 25F320S33B8, 4096 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Intel 25F320S33T8, 4096 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Intel 25F640S33B8, 8192 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Intel 25F640S33T8, 8192 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: Invalid OPCODE 
0x9f, will not execute.
Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: Invalid OPCODE 
0x9f, will not execute.
Probing for Macronix MX25L2005(C), 256 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Macronix MX25L4005(A/C), 512 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for Macronix MX25L8005/MX25V8005, 1024 kB: Invalid OPCODE 0x9f, 
will not execute.
Probing for Macronix MX25L1605, 2048 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Macronix MX25L1605A/MX25L1606E, 2048 kB: Invalid OPCODE 
0x9f, will not execute.
Probing for Macronix MX25L1605D/MX25L1608D, 2048 kB: Invalid OPCODE 
0x9f, will not execute.
Probing for Macronix MX25L1635D, 2048 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Macronix MX25L1635E, 2048 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Macronix MX25L3205(A), 4096 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: Invalid OPCODE 
0x9f, will not execute.
Probing for Macronix MX25L3206E, 4096 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Macronix MX25L3235D, 4096 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Macronix MX25L6405(D), 8192 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for Macronix MX25L6406E/MX25L6436E, 8192 kB: Invalid OPCODE 
0x9f, will not execute.
Probing for Macronix MX25L6445E, 8192 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Macronix MX25L12805(D), 16384 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for Macronix MX25U1635E, 2048 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Macronix MX25U3235E/F, 4096 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for Macronix MX25U6435E/F, 8192 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for Numonyx M25PE10, 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Numonyx M25PE20, 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Numonyx M25PE40, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Numonyx M25PE80, 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Numonyx M25PE16, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Numonyx N25Q016, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Numonyx N25Q032..1E, 4096 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Numonyx N25Q032..3E, 4096 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Numonyx N25Q064..1E, 8192 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Numonyx N25Q064..3E, 8192 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for PMC Pm25LD256C, 32 kB: Invalid OPCODE 0x9f, will not execute.
Probing for PMC Pm25LD512(C), 64 kB: Invalid OPCODE 0x9f, will not execute.
Probing for PMC Pm25LD010(C), 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for PMC Pm25LD020(C), 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for PMC Pm25LD040(C), 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res3: id1 0x1414, id2 0x14
Probing for PMC Pm25LV010, 128 kB: probe_spi_res3: id1 0x1414, id2 0x14
Probing for PMC Pm25LV010A, 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for PMC Pm25LV020, 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for PMC Pm25LV040, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for PMC Pm25LV080B, 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for PMC Pm25LV016B, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Sanyo LF25FW203A, 2048 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Spansion S25FL004A, 512 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Spansion S25FL008A, 1024 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Spansion S25FL016A, 2048 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Spansion S25FL032A/P, 4096 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Spansion S25FL064A/P, 8192 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x14, id2 0x14
Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x14, id2 0x14
Probing for SST SST25VF010, 128 kB: Invalid OPCODE 0x90, will not execute.
Probing for SST SST25VF016B, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Invalid OPCODE 0x90, will not execute.
probe_spi_res1: id 0x14
Probing for SST SST25VF032B, 4096 kB: Invalid OPCODE 0x9f, will not execute.
Probing for SST SST25VF064C, 8192 kB: Invalid OPCODE 0x9f, will not execute.
Probing for SST SST25VF040, 512 kB: Invalid OPCODE 0x90, will not execute.
Probing for SST SST25VF040B, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for SST SST25VF040B.REMS, 512 kB: Invalid OPCODE 0x90, will not 
execute.
Probing for SST SST25VF080B, 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for SST SST25WF512, 64 kB: Invalid OPCODE 0x9f, will not execute.
Probing for SST SST25WF010, 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for SST SST25WF020, 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for SST SST25WF040, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for ST M25P05-A, 64 kB: Invalid OPCODE 0x9f, will not execute.
Probing for ST M25P05, 64 kB: Invalid OPCODE 0x9f, will not execute.
Invalid OPCODE 0x90, will not execute.
probe_spi_res1: id 0x14
Probing for ST M25P10-A, 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for ST M25P10, 128 kB: Invalid OPCODE 0x9f, will not execute.
Invalid OPCODE 0x90, will not execute.
probe_spi_res1: id 0x14
Probing for ST M25P20, 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for ST M25P20-old, 256 kB: Invalid OPCODE 0x9f, will not execute.
Invalid OPCODE 0x90, will not execute.
probe_spi_res1: id 0x14
Probing for ST M25P40, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for ST M25P40-old, 512 kB: Invalid OPCODE 0x9f, will not execute.
Invalid OPCODE 0x90, will not execute.
probe_spi_res1: id 0x14
Probing for ST M25P80, 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for ST M25P16, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for ST M25P32, 4096 kB: Invalid OPCODE 0x9f, will not execute.
Probing for ST M25P64, 8192 kB: Invalid OPCODE 0x9f, will not execute.
Probing for ST M25P128, 16384 kB: Invalid OPCODE 0x9f, will not execute.
Probing for ST M25PX16, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for ST M25PX32, 4096 kB: Invalid OPCODE 0x9f, will not execute.
Probing for ST M25PX64, 8192 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Winbond W25Q80, 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Winbond W25Q16, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Winbond W25Q32, 4096 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Winbond W25Q64, 8192 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Winbond W25Q128, 16384 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Winbond W25X10, 128 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Winbond W25X20, 256 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Winbond W25X40, 512 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Winbond W25X80, 1024 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Winbond W25X16, 2048 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Winbond W25X32, 4096 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Winbond W25X64, 8192 kB: Invalid OPCODE 0x9f, will not execute.
Probing for Unknown SFDP-capable chip, 0 kB: Invalid OPCODE 0x5a, will 
not execute.
Receiving SFDP signature failed.
Probing for AMIC unknown AMIC SPI chip, 0 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for Atmel unknown Atmel SPI chip, 0 kB: Invalid OPCODE 0x9f, 
will not execute.
Probing for Eon unknown Eon SPI chip, 0 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for Macronix unknown Macronix SPI chip, 0 kB: Invalid OPCODE 
0x9f, will not execute.
Probing for PMC unknown PMC SPI chip, 0 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for SST unknown SST SPI chip, 0 kB: Invalid OPCODE 0x9f, will 
not execute.
Probing for ST unknown ST SPI chip, 0 kB: Invalid OPCODE 0x9f, will not 
execute.
Probing for Sanyo unknown Sanyo SPI chip, 0 kB: Invalid OPCODE 0x9f, 
will not execute.
Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: Invalid 
OPCODE 0x9f, will not execute.
Probing for Generic unknown SPI chip (RDID), 0 kB: Invalid OPCODE 0x9f, 
will not execute.
Probing for Generic unknown SPI chip (REMS), 0 kB: Invalid OPCODE 0x90, 
will not execute.
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
Restoring MMIO space at 0xb77c0070

Now we have somthing going on here:

Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res3: id1 0x1414, id2 0x14
Probing for PMC Pm25LV010, 128 kB: probe_spi_res3: id1 0x1414, id2 0x14

Probing for SST c, 512 kB: probe_spi_res2: id1 0x14, id2 0x14
Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x14, id2 0x14

Which one is now my chip?/I guess I have to replace / SST25VF016B by 
//SST25LF040A or SST25LF080(A) in the patch.
Do I have to change anything else in the patch? Probably .total_size and 
other things, how do I find that out?

thanks

Tim

[Peter Stuge]

Tim Zander wrote:
> Probing for SST SST25VF016B, 2048 kB: Invalid OPCODE 0x9f, will not 
> execute.
> Invalid OPCODE 0x90, will not execute.
> probe_spi_res1: id 0x14

So you have the MX25L1605D instead. Changing 0xbf in flashchips.c to 0x14
will make it work.

//Peter

[Peter Stuge]

Tim Zander wrote:
> I'm aware of this.

Great!
> Without the VGA BIOS Blob I just would have no monitor output in boot, right?

And no monitor output in the operating system, if the operating
system relies on a VGA BIOS.

//Peter

Flash succeed, but after bucts 0 x60s doesn't start.

[Tim Zander]

Dear Corebooters,

I flashed my x60s as described in the wiki.
I had the same output as similar result as in here
http://www.flashrom.org/pipermail/flashrom/2012-April/009124.html
first boot succeed (I had no vga output in boot (probably did something 
wrong with vga rom) but system came up).
Result were as shaky as described in here
http://www.flashrom.org/pipermail/flashrom/2012-April/009127.html
but things seemed to work

Now I thought things wouldn't be critical anymore...
Then I run bucts 0, didn't save the output (damm).
then I shut down the system
then pressing of the power button result in endless beeping
stop that the first time quiet early...
Do I have a beeping brick now?

Best wishes,
Tim

Flash succeed, but after bucts 0 x60s doesn't start.

[Denis 'GNUtoo' Carikli]

On Fri, 07 Jun 2013 22:14:42 +0200
Tim Zander  wrote:
> Dear Corebooters,
>
> I flashed my x60s as described in the wiki.
> I had the same output as similar result as in here
> http://www.flashrom.org/pipermail/flashrom/2012-April/009124.html
> first boot succeed (I had no vga output in boot (probably did
> something wrong with vga rom) but system came up).

Today I just switched from the BIOS to coreboot again and the screen
brightness was very low...try increasing that trough the keyboard
buttons.
> Result were as shaky as described in here
> http://www.flashrom.org/pipermail/flashrom/2012-April/009127.html
> but things seemed to work
>
> Now I thought things wouldn't be critical anymore...
> Then I run bucts 0, didn't save the output (damm).
> then I shut down the system
> then pressing of the power button result in endless beeping
> stop that the first time quiet early...
> Do I have a beeping brick now?

Maybe bucts didn't work? like if you did it not as root.
In that case that produces that beeping(I had the same issue)
a quick solution is to remove all the powers(including the CMOS
battery) to clear the bucts register.

Denis.

Flash succeed, but after bucts 0 x60s doesn't start.

[Peter Stuge]

Tim Zander wrote:
> things seemed to work

Sure, at this point you had completed step 8 at
http://www.coreboot.org/Lenovo_x60x
> Now I thought things wouldn't be critical anymore...
> Then I run bucts 0, didn't save the output (damm).
> then I shut down the system

So you skipped step 9 and went straight to step 10.
> then pressing of the power button result in endless beeping
> stop that the first time quiet early...
> Do I have a beeping brick now?

Yes. Since you skipped step 9 the last 64kb of the flash chip are
still from the factory BIOS.

Disassemble the machine and use an external flash programmer to
write a full coherent image to the flash chip, either your factory
BIOS backup or the full coreboot image.

//Peter

gratis bricked x60s

[Tim Zander]

Since I got confused by starting counting at 1 I bricked my x60s
if you have an external flashrom programmer, you can get my x60s and 
unbrick it.
I would send it at my costs (best uk or germany). reasonable donation to 
the FSF (or likely) considered. I would keep my flash drive and could 
send you a 60gb hdd with it if you want to.

tim

gratis bricked x60s

[David Hubbard]

Hi Tim,

I would hope there is a way you could get your x60s working again. Perhaps
the next time there is a coreboot get together you could bring it, and
arrange for someone to bring a flashrom programmer.

Yes, I am mildly interested in saving the x60s from the rubbish heap. But I
live in the US.

David

On Fri, Jun 7, 2013 at 5:28 PM, Tim Zander  wrote:
> Since I got confused by starting counting at 1 I bricked my x60s
> if you have an external flashrom programmer, you can get my x60s and
> unbrick it.
> I would send it at my costs (best uk or germany). reasonable donation to
> the FSF (or likely) considered. I would keep my flash drive and could send
> you a 60gb hdd with it if you want to.
>
> tim

gratis bricked x60s

[Tim Zander]

On 06/08/2013 01:28 AM, Tim Zander wrote:
> Since I got confused by starting counting at 1 I bricked my x60s
> if you have an external flashrom programmer, you can get my x60s and 
> unbrick it.
> I would send it at my costs (best uk or germany). reasonable donation 
> to the FSF (or likely) considered. I would keep my flash drive and 
> could send you a 60gb hdd with it if you want to.
>
> tim

Too late, bought a programmer... just 30$. Thought it would cost way more.

gratis bricked x60s

[Iurie]

excuse-me but i dont understan properly ur email. do u have something to
sell?

On 8 June 2013 13:32, Tim Zander  wrote:
> On 06/08/2013 01:28 AM, Tim Zander wrote:
> > Since I got confused by starting counting at 1 I bricked my x60s
> > if you have an external flashrom programmer, you can get my x60s and
> > unbrick it.
> > I would send it at my costs (best uk or germany). reasonable donation to
> > the FSF (or likely) considered. I would keep my flash drive and could send
> > you a 60gb hdd with it if you want to.
> >
> > tim
> >
> > Too late, bought a programmer... just 30$. Thought it would cost way
>
> more.

Flash succeed, but after bucts 0 x60s doesn't start.

[Andreas Wagner]

On Fri, Jun 7, 2013 at 7:05 PM, Peter Stuge  wrote:
> So you skipped step 9 and went straight to step 10.

I successfully booted a few times with coreboot on my Lenovo x60 tablet
(the first few times I didn't know to up the screen brightness but I saw
the disk activity light blinking). I then ran steps 9 and 10 and the same
thing happened on the next boot: a cycle of
long-beep..short-beep..short-beep...

I then opened up my computer and tried unplugging the power, removing the
battery pack and unplugging the CMOS battery. I plugged them back in and
tried booting: same symptoms as before.

After this I decided to try flashing to the BIOS chip with my buspirate and
pomona clip. If my memory is correct the output of flashing with the
buspirate was the same as flashing in step 9: something about the EEPROM
not being recognized.

I won't have access to my x60 tablet for a few days (it's spread out at
home) but any ideas would be much appreciated.

Thank you,

Andreas