#15798 closed bug (duplicate)
Black screen on boot on Lenovo Thinkpad X220
Reported by: | jscipione | Owned by: | PulkoMandy |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Drivers/Graphics/intel_extreme/sandybridge | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | #15626 | Blocking: | |
Platform: | All |
Description
Breakage occurred somewhere between hrev53938 and hrev53962.
Steps to reproduce: Buy a Lenovo Thinkpad X220 laptop
Download the hrev53962 nightly image from https://download.haiku-os.org/nightly-images/x86_gcc2h/
Image the download to a USB stick. https://www.haiku-os.org/guides/installing/making_haiku_usb_stick
Boot from USB and install.
Reboot and remove USB stick (or set BIOS option to boot from disk)
Black screen.
syslog and listdev are attached.
Attachments (2)
Change History (9)
by , 5 years ago
Attachment: | listdev.txt added |
---|
comment:1 by , 5 years ago
KERN: intel_extreme: compute_dpll_g4x: required MHz: 101.841, reference clock: 120
This is strange, on my machine a different dot clock is used (74.673MHz). There is not much logging in that area unfortunately so I'll have to add a bit more. It's getting a bit late here but I'll look into this tomorrow.
comment:2 by , 5 years ago
Apparently Step 1 is not good enough to reproduce this bug, you have to pony up for the quad-core i7 model to reproduce this bug with the above steps.
comment:3 by , 5 years ago
Wait, did the initial USB boot work? If that's the case, it could be only a problem with an old settings file on the target partition.
Can you try deleting ~/config/settings/system/app_server/workspaces? Does it work better after doing that?
I looked at the syslog and our machines have different LCD panels (mine has a Samsung one, yours is LG) but that should not make much of a difference (they have similar timigs, pixel clock should be around 74 to 76MHz).
comment:4 by , 5 years ago
The initial usb boot did work so that must be it... yeah I deleted that file and updated and now I'm able to boot hrev43967 without a problem. I didn't realize that there were app_server settings files that could get messed up, maybe that's what's going on in my BeOS font patch too.
Not to make this any more confusing but I’ve replaced the panel since I made that bug report with a different LG panel, an IPS LG LP125WH2-SLT1.
comment:5 by , 5 years ago
Component: | Drivers/Graphics/intel_extreme → Drivers/Graphics/intel_extreme/sandybridge |
---|
comment:6 by , 5 years ago
Blocked By: | 15626 added |
---|---|
Resolution: | → duplicate |
Status: | assigned → closed |
comment:7 by , 5 years ago
Milestone: | Unscheduled |
---|
Remove milestone for tickets with status = closed and resolution != fixed
listdev