Issue #412 has been updated by Josh R.

File cbmem.20221019200724.from_suspend.log added
File cbmem.20221019195923.normal_boot.log added

Carson A. wrote in #note-6:
> Angel Pons wrote in #note-5:
> > I concur with Nico's assessment. I imagine you changed the "ROM chip size" 
> > option to get a 4 MiB file to flash to the second flash chip (4 MiB).
> > 
> > Instead of doing that, 
> > https://doc.coreboot.org/mainboard/lenovo/Ivy_Bridge_series.html#splitting-the-coreboot-rom
> >  provides the commands to split a 12 MiB image into 8 MiB and 4 MiB parts. 
> > You'd want to use `dd of=top.rom bs=1M if=build/coreboot.rom skip=8` to 
> > obtain a 4 MiB image.
> > 
> > As you've already installed coreboot, you can also flash internally with 
> > `sudo flashrom -p internal --ifd -i bios -w build/coreboot.rom 
> > --noverify-all`. This tells flashrom to write `build/coreboot.rom` to the 
> > flash chip(s) using the internal programmer, but only the "bios" region as 
> > described by the IFD of the system. The `--noverify-all` option tells 
> > flashrom to not verify the entire flash chip (to make sure other regions 
> > did not change), but only the written regions. This is needed when flashrom 
> > cannot read the entire flash chip, and the ME region is not readable by 
> > default.
> 
> Yep, that worked, suspend works now. I've been having this issue for so long 
> but didn't know exactly why.  Thanks everyone for your help!
> 
> Edit: well it worked in linux, at least.  Resuming S3 in windows flashes the 
> power and mic LEDs, indicating a fatal error.  I've attached the boot log 
> (12mb_boot.txt) in case anyone has any ideas. 
> 
> Edit 2: Nevermind, I figured it out. Just had to uncheck "rerun VGA option 
> roms on S3 resume".

Can you clarify which method you used to resolve this?

I am having a similar issue with my t440p. It already has coreboot installed, 
but my attempt at running the `sudo flashrom -p internal --ifd -i bios -w 
the_full_coreboot_rom.rom --noverify-all` did not seem to do the trick (still 
"restarts" without resuming from RAM).

Note that I am using the "full" 12MB coreboot.rom (not split by 4MiB and 8MiB, 
as that seemed intended for the hardware flashing instructions).

coreboot version looks like 4.15.204, and flashrom version 1.2-640.

If it helps, attached `cbmem -1` output with a "normal boot" followed by a 
later resume from suspend (that resulted in a restart).

Thanks in advance. I guess you don't realize how much you use suspend until it 
doesn't work anymore :)

----------------------------------------
Bug #412: x230 reboots on suspend
https://ticket.coreboot.org/issues/412#change-1203

* Author: Carson A.
* Status: New
* Priority: Normal
* Target version: none
* Start date: 2022-09-02
* Affected versions: master
* Related links: https://ticket.coreboot.org/issues/393
* Affected hardware: x230
* Affected OS: windows/arch linux
----------------------------------------
Very similar to issue 393 where the x230 reboots when suspended to RAM. Seems 
to be an issue with coreboot v4.16 & 4.17 or something is missing in the config 
(attached). Any insight on this would be appreciated!

---Files--------------------------------
coreboot_config.txt (18.8 KB)
normal_boot.txt (48.1 KB)
suspend_boot.txt (48 KB)
12mb_boot.txt (47.6 KB)
cbmem.20221019200724.from_suspend.log (36.3 KB)
cbmem.20221019195923.normal_boot.log (36.2 KB)


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
https://ticket.coreboot.org/my/account
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to