haiku-nightly-r41272-x86gcc4hybrid-anyboot doesn't boot on acer netbook aO532h

[threarth]

This nightly build fails to boot with acer ao532h; it only works with failsafe video mode, 800x600; video card is an intel GMA 3150.

[threarth]

/var/log/syslog, booting in vesa mode

[threarth]

lspci with ubuntu

[kallisti5]

interesting bits of intelextreme load. DDC read errors

[kallisti5]

It looks as though the Intel extreme driver is having problems reading EDID modeline information from the LCD/monitor.. or it is just ungracefully failing on ports with no monitor attached...

KERN: DDC: ddc2_read(): DDC information read failure
KERN: Last message repeated 3 times.
KERN: intel_extreme: getting EDID on port A (analog) failed : No Error (8). Trying on port C (lvds)
KERN: DDC: ddc2_read(): DDC information read failure
KERN: Last message repeated 3 times.
KERN: intel_extreme: getting EDID on port C failed : No Error (8)

It does set a resolution though of 1024x600, does this sound like the correct native resolution of your built-in lcd?

Could you try powering on/booting Haiku with an external monitor attached to the system without any safe video modes?

[threarth]

Yes, it appears to set a resolution of 1024x600 and this is the correct native resolution, but when I'm on i have a 800x600 desktop, cannot set to 1024x600. Few minutes ago I tried powering on with an external monitor and it works perfectly, at the correct resolution of that monitor that i think is 1024x768 because it's not like an lcd netbook; i can also see the top right corner of the screen which I couldn't see before. How can I get my built-in lcd working?

[threarth]

syslog with external monitor, full working system

[sotrud_nik]

You may want to take a look at ticket number 7441 https://dev.haiku-os.org/ticket/7441

I have the same netbook, and the only way I could make it work - recompile the intel extreme accelerant with hardcoded reference clock.

[umccullough]

Removing mention of "i915" from this ticket, the GMA 3150 does not use the i915 chipset - it's possible that this misunderstanding is due to various drivers (i.e. linux) being referred to as the "i915 driver".