Opened 12 years ago
Closed 11 years ago
#9308 closed bug (fixed)
Intel Extreme Graphics (SandyBridge) loaded, but not working
| Reported by: | bradh | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Drivers/Graphics/intel_extreme | Version: | R1/alpha4.1 |
| Keywords: | Cc: | harryn@… | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Hi there, I have a Samsung Notebook. It has an integrated Intel graphics card which appears to be loading, but not actually working. According to Screen it's using VESA with the typical 3 resolutions available - the highest being 1024x768
Some info for you:
General
Haiku version R1/alpha4 (Revision hrevr1 alpha4-44702) Laptop Model Samsung Notebook - NP300E5A
Graphics Info:
Device/vendor 0x8086 Device/id 0x116
Pastes
-> listimage | grep intel_e
897 /boot/system/add-ons/kernel/drivers/dev/graphics/intel_extreme 0x81135000 0x81139000 0 0
(From the syslog) KERN: intel_extreme: init_hardware() KERN: intel_extreme: init_driver() KERN: intel_extreme: (0) SandyBridge Mobile GT2, revision = 0x9 KERN: intel_extreme: publish_devices() KERN: intel_extreme: find_device() KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/graphics/intel_extreme KERN: intel_extreme: open(name = graphics/intel_extreme_000200)
Everything is pointing to the driver being loaded, but doesn't seem present in Screen. AIf you need any more information please let me know, but I am completely at a loss.
Thanks
Oddly enough the graphics look slightly cleaner, while still offering the same limited resolutions, in Safe Mode. I figured perhaps because it was using primarily VESA drivers instead of the intel ones that weren't working properly.. so, I backed up the 3 references to intel_extreme, removed the originals and reboot as normal. My graphics look slightly better in straight VESA mode, but obviously it would still be nice to have my Intel graphics supported with the correct resolution. Just thought I would share that experience in case it helps. I should also note I had a similar problem with FreeBSD. The newer intel graphics weren't really supported in FreeBSD at the time, so the only way around it was a manual kernel patch. I don't remember exactly where it was, though.