Intel Extreme Graphics recognized as VESA in recent nightly

[un_spacyar]

Since upgraded to hrev50258 x86_gcc2 (from a previous nightly from March 30), my video card is identified as "VESA" instead of "Intel Extreme Graphic" in the monitor settings.

I attach my syslog.

[kallisti5]

You didn't provide much info here... however it is expected behavior. Anything SandyBridge or later was flagged as experimental in the driver. A major rewrite is underway to better support Ivy Bridge+ and later cards have some bugs still. A few machines Ivy Bridge or later worked as a fluke. (most didn't work however) Thus I flagged SandyBridge or later experimental to force usage of VESA (which likely works)

For now, to activate these cards for testing you need to re-enable them in the driver sources and recompile. If you have any Sandy Bridge systems, testing help would be appreciated!

[pulkomandy]

I think this makes testing the driver on new cards more annoying for users. Maybe a driver settings file to force extra PCI IDs to be allowed by the driver would be useful?

I think Sandy Bridge was at least modesetting in the driver (other things were possibly broken, such as the wait_for_retrace). I don't know which way is better between that and VESA, however.

[jua]

Duplicate of #12714

[un_spacyar]

kallisti5, Pulkomandy: thanks for your answers. I dont have problem in testing the driver. The only way to get it is to compile the entire Haiku source tree? (sorry for the dumb question, but I not have much experience compiling apps).

[pulkomandy]

You can compile only the driver (jam -q intel_extreme) but it is a bit annoying to install it in an existing install. So yes, the easiest way is compiling a complete haiku install (unless you have a very slow CPU).

Ideally we could use network booting for easier testing of changes in drivers, but this is currently broken.