Opened 4 years ago
Last modified 3 years ago
#16170 assigned bug
[intel_extreme] HD4000 not detected
Reported by: | diver | Owned by: | pulkomandy |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/Graphics/intel_extreme/ivybridge | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
This is haiku-r1beta2-hrev54154_31-x86_64-anyboot.iso running on MacBook Pro (Retina, 15-inch, Early 2013).
In UEFI mode Haiku hangs at boot at the rocket icon. Surprisingly, In BIOS mode it is not detected.
Intel HD Graphics 4000: Chipset Model: Intel HD Graphics 4000 Type: GPU Bus: Built-In VRAM (Dynamic, Max): 1536 MB Vendor: Intel Device ID: 0x0166 Revision ID: 0x0009 Automatic Graphics Switching: Supported gMux Version: 3.2.19 [3.2.8] Metal: Supported, feature set macOS GPUFamily1 v4 Displays: Colour LCD: Display Type: Built-In Retina LCD Resolution: 2880x1800 Retina Framebuffer Depth: 24-Bit Colour (ARGB8888) Main Display: Yes Mirror: Off Online: Yes Rotation: Supported Automatically Adjust Brightness: No
Attachments (2)
Change History (10)
by , 4 years ago
Attachment: | macbookpro-syslog added |
---|
by , 4 years ago
Attachment: | macbookpro-listdev.log added |
---|
comment:1 by , 4 years ago
Description: | modified (diff) |
---|
comment:2 by , 4 years ago
This MacBook Pro has 2 graphic cards: Intel HD 4000 Built-in and NVIDIA GeForce GT 650M PCIe. Maybe this is somehow related?
comment:3 by , 4 years ago
MacBook Pro with dual cards will by default disable the Intel Iris integrated GPU when booting non-OSX systems, and only enable the discrete nVidia GPU. You need a utility like set-os.efi (https://github.com/0xbb/apple_set_os.efi) to trick the firmware to enable the intel GPU, which only lasts for the next session. Sadly, Haiku will stop at the rocket icon in this configuration, so you’ll also be stuck with the VESA driver.
My experience with MBP 11.3 (2014 with nVidia GT750M) is a bit weird. There was a time where I only had 2880x1800@32 bits via EFI boot, but for the last 8 months (thanks Linux Mint for breaking EFI boot and trashing Win10), I now get legacy BIOS boot which gives many VESA resolutions up to 2880x1800@16 bits (notice the different colour depths, but more resolutions). This is all due to MBP firmware exporting VESA settings differently in EFI modes vs legacy BIOS modes (exposed via bootcamp settings, and Linux Mint did something weird that I was unable to restore or reinstall Win10 ever since). I’ve given up on Win10 and Linux, use OSX only when I need wi-fi, and 90% of the remaining time (wired network) is Haiku exclusively.
comment:4 by , 4 years ago
Thanks for the info! How do you load set-os.efi before haiku_loader.efi? I will check what colour depth i get in BIOS boot. I have the same resolution. How do you have network in Haiku on you MacBook? Mine doesn't have ethernet port and there is no driver for wifi card.
comment:5 by , 4 years ago
I use thunderbolt -> ethernet rj45 adapter, and use the broadcom 570x ethernet driver which is in default Haiku image. Works better than Win10 actually since Win10 wont hotplug.
comment:6 by , 4 years ago
Regarding set-os.efi, I use rEFIt and just add it to Fat32 EFI partition. You dont need it though since Haiku doesn’t support Intel Iris driver anyway, so you’re still reliant on VESA so might as well run nVidia hardware and avoid the boot dance.
comment:8 by , 3 years ago
Not yet, will try to find some time to check that with current nightly and set-os.efi.
BIOS boot