Well, that’s cleaner I guess design wise. For the not-so-complete intel driver I would not recommend it though.
Still, if someone likes to do it fully, it’s nice to have it I guess. That probably means you have to checkout all hardware versions, all possible pipes, scalers, cross-connections possible and come up with the right readout. And, while at it, if all this has become fully clear, it will be also possible largely to actively program all that same stuff, which will be needed anyway if this driver has to support multiple independant heads. Currently it has clone at best, since in that case the exact readout is less important…
For me this is not something I am going to put effort in for the extreme driver, my goal is/was to get as much systems at least a single screen that can set modes, compared to what it did before. Looks like this attempt is succeeding indeed. If someone else wants to jump in, thats perfectly OK, I’ll just rethink what I want to do next then.
@rudolfc Thank you so much for your work on this front.
My Lenovo Yoga 2 Pro 13’’ graphic card is now detected as Intel Haswell mobile and I think the monitor as well (I am writing from my Thinkpad now). All available resolutions are displayed correctly and I have a brightness bar ! I am using it currently at 1600 x 900, half of his native (3200 x 1800). The screen really looks amazing. This is a machine that has some motherboard heat issues that prevent CPUs to reach high frequency. But, as I said in an older thread, it’s pretty much working with lightweight Haiku. Need to try to play 1080p video to encounter the problem…
Need to update our hardware database with the info…
Due to the above problem, my main machine is a Thinkpad T450s.
Its graphic card is an HD Graphics 5500 but framebuffer is used with Haiku (EFI boot), although in correct resolution: 1920x1080.
Is it supposed to work? If yes, is there a difference for the driver between legacy and EFI boot?
BTW, my Yoga 2 above boots in legacy mode. But the Thinkpad cannot, because of 12Gb memory it boots only in EFI mode (I think I had created a ticket for that in the past).
Please let me know if you need more info or if I should create any ticket.
Thanks again
Hi fkap, so on the Lenovo, does GLteapot spin at 60Hz as well? (checking if interrupts for blanking works there).
For the other system: what’s the card’s ID? if it’s not in the driver you could create a ticket for it indeed.
The difference between EFI boot and legacy boot on some systems is that during boot EDID info might not be fetched in EFI mode (depending on specific BIOS implementation though, so depends on the specific system setup). Since for some screentypes (DP) the driver might still rely on the EDID from boot, this would indeed mean there’s a difference in how the driver would behave between the two boot types.
On most laptops I guess it will be OK anyway though since there the panel info is fetched from the ROM (or via ACPI, using Intel’s OpRegion function) and the driver will use that instead then.
I saw KabyLake mentioned in a few posts. Has there been more progress on it?
That ended up being why I was having to boot in VESA mode…I have KabyLake and a 4K monitor, and it was attempting 4K native resolution but resulted in a black screen (ctrl+alt+shift+esc worked great to move down to a working resolution). Changing the Screen resolution to 1920x1068x32 60Hz works fine, so I don’t need to use VESA in that case. Thanks for all the hard work!
I think my issue actually turned out that the driver was trying either 2560x1440@60Hz or 3840x2160@60Hz, but my 4K display (an LG TV) only supports a maximum refresh of 30Hz for resolutions higher than 1920x1080. Windows correctly detects all the possible resolutions and refresh rates for the TV. I can post the resources reported by Windows (Memory ranges, I/O ranges, and IRQ) if that would help.
@rudolfc hi, after a year, i still have the exact same problem, if i try to change resolution or frequency i get black screen…
the only difference is that now next to the name of the monitor I get the message “do not use” next to the name of the monitor
could you please take a look at my systemlog?
I’m also attaching the unpacked dump of my bios settings, maybe you can figure out what’s going on… syslog sonyvaio_bios_text_Dump
Currently korli is working on the driver afaik, and looking at ticket 17205 he requested a syslog from a current nightly. Please post the syslog there? (I was unable to open the link you just now posted btw).
As for me working on this driver I’m afraid my knowledge on it is currently a bit outdated due to the large amount of ‘fresh’ work that has been done on it the larger part of this year after februari or so. So I am mostly reading along and when I have more time again I can maybe jump in again…
@rudolfc the pastebin site i used deleted the two files i posted earlier, i didn’t know it was temporary, if you are interested you can take a look at the ticket i updated, especially my bios dump unpacked with amisetupIFRextractor , i use it to see and potentially change the hidden functions of my bios via the amisetupwriter tool, take a look, I saw that the gpu is called “igpu” you can quickly find it with a search and see how it is set by default
, now i update the syslog