Desktop doesn't render properly with intel_extreme (regression)

[jadedctrl]

I'm having new problems booting as of hrev55144― the desktop renders strangely and usuably with intel_extreme on a screen at 1280x1024@60Hz.

Everything displays normally in hrev55143 and below, but anything after 55144 (including booting from USB on 55149) has the same problem.

[jadedctrl]

listdev run from 55143

[jadedctrl]

syslog from hrev55149

[jadedctrl]

drivers from hrev55143

[jadedctrl]

Picture of desktop rendering "strangely" (hrev55144)

[rudolfc]

Thank you. Your bootmode is below 1280 mode so your cardbios programs just 1 lane for the analog connected screen. Hence the distortion you are seeing (2 lanes needed for this mode). If you set 1024x768 desktop mode it should display OK. If you would set any mode of 1280 or higher before boot, the higher resolution modes should be set correctly.

What you are seeing is actually improvement of the driver although it seems a regression. We need FDI train programming to overcome the current limitation you are seeing. Or you could connect that screen via HDMI/dvi if possible as probably 2 lanes will be set by default by your card BIOS, independent of the set bootmode.

[rudolfc]

Hi again, it would be nice btw if you could confirm the story I wrote above. I just saw for instance that with 64bit Haiku I get much less boot resolution options than in 32bit mode, and the highest for 64bit mode for me is 1024x768: which means that for now, using an analog screen, that's the max mode the driver can do. Digitally connected though all resolutions work, keeping the FDI lanes story in mind.

[jadedctrl]

Thanks for the poke!

Just gave everything a try, and you got it― 1024x768 and below works as expected, and manually setting 1280x1024 from the boot menu leads to no output. I haven't been able to try HDMI or DVI yet, I'd have to get a converter.

[rudolfc]

Thank you for the confirmation!

[rudolfc]

Hi, for your infoL hrev55189 or later contains an update that should make the driver work (much) better with all kinds of screens, even two at the same time.. The lane issue it the same of course,so I guess you'd have to use an adapter or other digital cable to see improvements. I would expect the driver to behave the same on your analog connection. If you would test that, I'd love a confirmation it indeed does work the same.

Thank you!

[jadedctrl]

Still haven't had a chance to test with digital, but I can confirm it's the same with VGA, yea.

[jadedctrl]

Finally got that display port→VGA connector― everything's working as you said, thanks for the info. :)

[rudolfc]

Hi, so that's an adapter cable which has a displayport input, and a VGA connector output? Wow, AFAIK nobody tested that yet. If this is the case, can you please upload a syslog? And: what modes could you set approx? Thanks for the feedback!

[jadedctrl]

syslog with a DP→VGA cord

[jadedctrl]

Yea, that's the one! Just added the syslog, and I had no trouble setting any mode under 1280x1024 32 bits/pixel.

[rudolfc]

Thank you! Interesting, apparantly the driver does not even see this thing.. So it does not really actively set modes at all. Looks like you're better of without it. Hmm.

Can you tell me what this adapter is? do you have a link to a sales page or something, or just a brandname and a type number, and/or a photo?

Maybe, if it's not too expensive, I can buy one myself for a test or two..

[e3bc54b2]

I added a syslog in #17354 and I could be facing the same issue. Currently booting with fail-safe graphics drivers. I can test more if needed.

[rudolfc]

Hi Jadedctrl, could you retest the current nightly (​https://git.haiku-os.org/haiku/tag/?h=hrev55639 or later) to see how the driver behaves now? For skylake I added recognition of the DP to VGA adapter sitting on the mainboard there, and it might well be that your adapter is now seen by the driver as well..

Please let me know and also upload a syslog again if possible.. Thanks!

[korli]

jadedctrl, any chance to test on a recent nightly?

[jadedctrl]

syslog w DP→VGA cord, hrev56106

[jadedctrl]

Just attached, sorry about the wait!

[korli]

Thanks. Please update to hrev56113 and attach a new syslog, it should only make a difference for EFI booting.