Issue #538 has been updated by Brian L.

File cbmem.log added

Nico Huber wrote in #note-15: 
> Well, these are two things, saying that only SeaBIOS can do it and saying 
> coreboot can do it with the `0106`.  

Correct, they are 2 separate things, I thought this was clear I apologize if it 
wasnt.

> 
> > ```
> > ls -l /sys/class/drm/card0
> > lrwxrwxrwx 1 root root 0 May 19 13:17 /sys/class/drm/card0 -> 
> > ../../devices/pci0000:00/0000:00:02.0/drm/card0
> > ```
> 
> Is this the working case? Do both card0 and card1 point to the same PCI 
> device? It's not important I guess. Only interesting if you want to figure 
> out what the second card is about.  

What I have actually found is if:  

1) SeaBios loads the option rom (working config)
  - card0 doesnt exist
  - card1 does exist and edid is properly found there
  - resolution on boot detects proper monitor resolution (1024x600)  

2) Coreboot loads the option rom (working config)  
  - card1 doesnt exist
  - card0 does exist and edid is properly found there
  - resolution on monitor is 1024x768 on boot and then properly adjusts to 
1024x600 when OS takes over  

3) Coreboot is misconfigured/does not load option rom OR coreboot configured to 
use libgfxinit (non-working config)
  - card1 doesnt exist
  - card0 does exist, but edid is empty
  - no display on boot and then adjusts to 1024x768 once OS takes over  

This is maybe expected outcome, or interesting, I am not sure

> Btw. did you give the physical connections a look? After all it might also be 
> coincidence, e.g. if something got loose during the docking.  

I've inspected the motherboard side of the connection and it's fine, I havent 
looked behind the panel, maybe at some point I will. 

> If you want to get libgfxinit working again, a log would really be the next 
> best step.
See attached full ADA debug log, thanks

----------------------------------------
Bug #538: [Soft Brick] x230 Dock Causes Internal Display to "Permanently" 
Malfunction
https://ticket.coreboot.org/issues/538#change-1847

* Author: Brian L
* Status: New
* Priority: High
* Target version: none
* Start date: 2024-05-14
* Affected hardware: Lenovo x230
----------------------------------------
Environment:  
  - Lenovo x230
  - Stock screen replaced with Pixel Qi (not sure if relevant) (plug & play 
LVDS)
  - Coreboot using Heads (coreboot + linuxboot)
  - Official lenovo docking station connected to external monitor via 
DisplayPort

Bug Trigger:  
Using Heads/coreboot fine for years with my Pixel Qi screen modded x230. I then 
bought a Lenovo docking station. Booted up, everything worked fine.  
Disconnected from dock, booted up, and there was no bios screen. Screen did not 
turn on until taken over by Linux Kernel. Once in userspace, wayland could no 
longer identify the monitor as a Pixel Qi or its proper resolution. EDID is 
blank. 
Booting with docking station allows bios to show on external display.

Restarting did *not* fix the issue, reflashing heads did *not* fix the issue, 
flashing skulls (coreboot + seabios) did *not* fix the issue.

Flashing stock bios *did fix* the issue. I can now see BIOS screen and get 
proper EDID in userspace whether on the dock or not. 
*However* reflashing coreboot again, even coming from stock bios working state, 
and I immediately now no longer get a BIOS screen or EDID, even without ever 
introducing the dock again. Essentially now bricked with anything but stock 
bios.

---Files--------------------------------
cbmem.log (62.6 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