Conversation
Edited 5 days ago

I tried booting my ThinkPad P51 coreboot port (for the first time) today, and it reached ramstage, but seems to be hanging somewhere in post_mp_init for some reason. The last lines in the flashconsole log are:

bsp_do_flight_plan done after 15 msecs.
CPU: frequency set to 4000 MHz
Enabling SMIs.
Locking SMM.
VMX status: enabled
VMX status: enabled
IA32_FEATURE_CONTROL status: locked
VMX status: enabled
1
0
0
inteltool didn't support dumping GPIOs on the Intel CM238 chipset so I just modified it to treat it the same was as CM236 (and other non-LP sunrise point chipsets), hopefully that's correct (I think it should be, but I have no idea and can't actually find the CM238 datasheet (the 100-series and C230 series datasheet mentions it but doesn't list it in the SKU definition section at the beginning)

I also just commented out the dGPU initialization sequence since the one for the ThinkPad T480 uses GPIO pins that don't exist on the P51 (I have no idea how to find the correct one)

Initially I completely forget to configure GPIOs and didn't notice that my dumps were missing GPIOs so I had to return to stock firmware to re-run inteltool after modifying it
1
0
0
I nearly did the very stupid mistake of accidentally flashing my laptop (the one I'm actually using, not the P51) internally with the P51's firmware instead of using my USB flasher (a pi pico 2), but was luckily prevented from doing so by /dev/mem protection
2
0
0

my pico 2 can’t reliably write to the flash chip, sometimes it fails with an error like

Verifying flash... FAILED at 0x00823901! Expected=0xfa, Found=0xff, failed byte count from 0x00000000-0x00ffffff: 0x1

maybe the drive strength is insufficient (even though I have it set to the maximum the pico 2 can provide (12mA))

it’s not really a big problem though since I can just retry and it usually succeeds

1
0
0

@noisytoot > USB flasher (a pi pico 2)

wait you van just do that with a pico???

(of course I realize this right after I buy a ch341a... though tbf it is still probably useful regardless)

1
0
1
@hexaheximal yes, and it's better than ch341a because it's fully 3.3V
1
0
1
I disabled flashconsole and it boots to linux! apparently flashconsole is buggy and doesn't work past early boot
1
0
0
dgpu init doesn't work unfortunately and I have no idea how to make it work. the initialization sequence for the T480 (which isn't reliable anyway) doesn't even compile because it uses several GPIOs that don't exist on the P51

and unlike on the T480, having the dgpu working is actually important (even though with nouveau performance is worse than the igpu) because the external display outputs are connected to it without a mux (so external display outputs won't work if the dgpu doesn't)
1
0
0
video with flickery graphical glitches
Show content
first attempt at dgpu init (it took me several tries to record this video thanks to autofocus deciding to defocus partway through recording (fuck autofocus))
1
0
1
@hexaheximal you'd need a logic level converter, but I haven't flashed any 1.8V boards yet. ch341a has 5V data lines so it's certainly not better for 1.8V
1
0
1
@hexaheximal https://libreboot.org/docs/install/spi.html#do-not-buy-ch341a describes the problem in more detail. it's possible to fix it apparently, but I haven't really looked into it since it's easier to just use a pico
2
0
1

@noisytoot odd! mrchomebox wiki *recommends* ch341a

0
0
0

@noisytoot since I already bought a ch341a, do you think I could just use the clips and 1.8v converter from it with a pico?

I have a pico h lying around that I could easily use for this

1
0
0
@hexaheximal possibly, but if you're using a 1.8v converter anyway the ch341a data lines being natively 5v might not be an issue?
1
0
1

@noisytoot I'm still not going to use it without checking the voltage first (and I don't have any tools for measuring voltage at the moment) if I can use a pico h I already have

1
0
1

@noisytoot the hardware I'm going to flash the bios of is a few historically interesting chromebook models. as such I absolutely do NOT want to risk it

0
0
1
uhh it just did this even with the dgpu disabled. it doesn't do it consistently and sometimes there's also another graphical glitch causing a single horizontal line to appear near the bottom of the screen (which disappears after launching a graphical environment, it only appears in the tty)

also all of this only happens shortly after booting (for a few seconds to minutes) then stops, and only in the linux tty (never in edk2)
1
0
0
I got the dGPU to enumerate! I just had to power it on before FSP-S runs. nouveau crashes and fails to load for some reason, however
0
0
0