Opened 3 years ago
Last modified 3 years ago
#17771 new bug
intel_extreme unsupported mode since hrev55991
Reported by: | dsjonny | Owned by: | pulkomandy |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/Graphics/intel_extreme/broadwell | Version: | R1/beta3 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86-64 |
Description
I have a Lenovo T450 laptop with HD Graphics 5500 (Broadwell GT2) and the intel_extreme driver was last worked on hrev55969. Since hrev55991 after the boot icons I have only blank screen. When I use external monitor it also blank but show an error: "unsupported mode". The lastest nighty also tried (hrev56156). I can only boot with safe video mode. I have attached the latest log.
Attachments (6)
Change History (20)
by , 3 years ago
comment:1 by , 3 years ago
comment:2 by , 3 years ago
The only thing I see in the logs that looks like it could be a problem is:
KERN: intel_extreme: SetPipe: Assuming pipe is assigned by BIOS (fixme)
Otherwise I'm not sure what the problem might be. Hopefully korli might have an idea?
comment:3 by , 3 years ago
As I remember before this commit the I always got black screen during boot, but after this I could load Haiku with Intel graphic instead of VESA:
https://cgit.haiku-os.org/haiku/commit/?id=ec3df54304a52f0b27334dc098a0f79fab31e3eb
comment:4 by , 3 years ago
I am confused. Do you mean it only boots when you use VESA/framebuffer (failsafe) driver, or when you select a specific mode you can boot and use the intel_extreme driver?
Or, do you mean that you always got a black screen during boot *before* the change you mention, and now you get something different?
comment:5 by , 3 years ago
So before the mentioned commit I was only able to boot in VESA (selected from boot menu), because if I not selected it I got always black screen after the last icon. After this update with the next nightly build I booted successfully without setting anything in boot menu. But after 1-2 nightly I need to set the VESA mode in boot menu because I got the black screen again.
comment:6 by , 3 years ago
Hmm, that's strange.
When you have a nightly that "works", can you reboot a number of times and it always works? Or, does it sometimes give a black screen, too?
Perhaps it is an intermittent problem in general?
comment:7 by , 3 years ago
the eDP port tries to get the EDID on the DP AUX, but the hw_cdclk isn't set for Broadwell. this is added by https://review.haiku-os.org/c/haiku/+/5355
comment:8 by , 3 years ago
It was always worked with hrev55969. I just plugged in the USB stick and boot it without user intervention. I got the desktop and everything was worked. Since I next updated the Haiku it is not working, I need to select the VESA mode in boot menu to be able to boot the desktop.
comment:9 by , 3 years ago
Sorry, I was wrong with the hrev55969, I found the ticket where comfirmed the intel_extreme update was worked on my laptop. So now I found the working version: hrev56093. I freshly installed it to an USB drive and booted successfully with intel driver (however during boot I enabled the onscreen logging). Please check the attached syslog and screenshot.
by , 3 years ago
Attachment: | hrev56093.png added |
---|
by , 3 years ago
Attachment: | syslog_hrev56093 added |
---|
comment:10 by , 3 years ago
In hrev56093, the DP aux Ctrl was still hardcoded to a value related to 450MHz. Following revisions changed it to have it dynamic based on hw_cdclk, which wasn't set for broadwell. Please try the following anyboot image with EFI: https://haiku.movingborders.es/testbuild/I4bdcca1fdc05294fb5b56c5c96164b6936a5881e/1/hrev56156/x86_64/
by , 3 years ago
Attachment: | hrev56156-test.png added |
---|
by , 3 years ago
Attachment: | syslog-hrev56165-test added |
---|
comment:11 by , 3 years ago
Hi korli I tested it and it is working, thank you. I attached the screenshot and the syslog also. 1 note: working only with internal laptop display, but not with DisplayPort-connected monitor.
comment:12 by , 3 years ago
Thanks for the test, merged in hrev56158.
Can you confirm, in the syslog the first boot is with the external display connected, and the second without? The DisplayPort-connected monitor setup isn't tested on my side (only with DVI/HDMI adapter).
comment:13 by , 3 years ago
Yes, 1st I tried with external display with mini display port.
And is it possible to change the display between internal and external in runtime? Or is it not possible yet?
comment:14 by , 3 years ago
I have updated and tested hrev56158 nightly x86_64 and with laptop/internal display it is working fine, but external monitor on display port still has a problem. I attached the syslog of booting with external display.
by , 3 years ago
Attachment: | syslog-hrev56158 added |
---|
Probably it never worked, because the change of relevance in that range is the adding of the Broadwell device IDs in hrev55988.
Interestingly I have the same device and it works for me, hence why I added the IDs. Maybe it was a bit premature...