i'm setting up a new hack: Mountain lion, MSI H61M-P31 with an i3-2125 with HD3000 graphics. using ubuntu, i found that the device ID for this chip's gpu is 0112. doing a minimal install of WinXP, device manager confirms device ID 0112. the PCI Device ID repository website confirms 0112 as a Sandy Bridge HD3000 GPU.
all is well when using a PCI-e graphics card, but not so when trying to use the onboard HD3000 graphics.
starting from scratch:
ML installs fine with a unibeast stick, then rebooting with helper USB to set up ML works fine. graphics are at default resolution. when i inspect system information-->graphics, it shows the HD3000 gpu, with a device ID of 0126 (not 0112), but no kext loaded.
i added device and vendor ID to AppleIntelHD3000Graphics.kext and AppleIntelSNBGraphicsFB.kext, then kext cache rebuild and repair permissions.
upon reboot, still using boot helper, apple/gearwheel screen freezes when it should shift to the desktop (the HD is still being accessed so it's not a hung boot).
has anyone experience this with an HD3000 gpu whose device ID isn't in ML? are there other graphics kexts that i need to edit? some anecdotal posts on other boards say success with 10.7 kexts of the same name, but that didn't work(same symptoms--and upon inspection, found the 10.7 kexts don't have 0112 device ID either.)
> i'm setting up a new hack: Mountain lion, MSI H61M-P31 with an i3-2125 with HD3000 graphics. using ubuntu, i found that the device ID for this chip's gpu is 0112. doing a minimal install of WinXP, device manager confirms device ID 0112. the PCI Device ID repository website confirms 0112 as a Sandy Bridge HD3000 GPU.
> all is well when using a PCI-e graphics card, but not so when trying to use the onboard HD3000 graphics.
> starting from scratch:
> ML installs fine with a unibeast stick, then rebooting with helper USB to set up ML works fine. graphics are at default resolution. when i inspect system information-->graphics, it shows the HD3000 gpu, with a device ID of 0126 (not 0112), but no kext loaded.
> i added device and vendor ID to AppleIntelHD3000Graphics.kext and AppleIntelSNBGraphicsFB.kext, then kext cache rebuild and repair permissions.
Which number did you add, the one found using Linux and Windows or the one under ML?
> upon reboot, still using boot helper, apple/gearwheel screen freezes when it should shift to the desktop (the HD is still being accessed so it's not a hung boot).
> has anyone experience this with an HD3000 gpu whose device ID isn't in ML? are there other graphics kexts that i need to edit? some anecdotal posts on other boards say success with 10.7 kexts of the same name, but that didn't work(same symptoms--and upon inspection, found the 10.7 kexts don't have 0112 device ID either.)
> thanks in advance
> ken
I was going to try this myself, but then realized that buying a cheap supported PCI-e card is cheaper than springing for the cpu with HD3000 support. Of course this would not be helpful is the system you are trying to Hack did not have a PCI-e video card slot.
From the main system of mosslack...
______________________________
Alt-OS <+> GG <+> TBIE <+> Hack List
> i'm setting up a new hack: Mountain lion, MSI H61M-P31 with an i3-2125 with HD3000 graphics. using ubuntu, i found that the device ID for this chip's gpu is 0112. doing a minimal install of WinXP, device manager confirms device ID 0112. the PCI Device ID repository website confirms 0112 as a Sandy Bridge HD3000 GPU.
> all is well when using a PCI-e graphics card, but not so when trying to use the onboard HD3000 graphics.
> starting from scratch:
> ML installs fine with a unibeast stick, then rebooting with helper USB to set up ML works fine. graphics are at default resolution. when i inspect system information-->graphics, it shows the HD3000 gpu, with a device ID of 0126 (not 0112), but no kext loaded.
> i added device and vendor ID to AppleIntelHD3000Graphics.kext and AppleIntelSNBGraphicsFB.kext, then kext cache rebuild and repair permissions.
> upon reboot, still using boot helper, apple/gearwheel screen freezes when it should shift to the desktop (the HD is still being accessed so it's not a hung boot).
> has anyone experience this with an HD3000 gpu whose device ID isn't in ML? are there other graphics kexts that i need to edit? some anecdotal posts on other boards say success with 10.7 kexts of the same name, but that didn't work(same symptoms--and upon inspection, found the 10.7 kexts don't have 0112 device ID either.)
since both kexts included several other device/vendor id's, i decided to add both the 0112 and the 0126 id's.
this was a fry's bundle for $170, for the mobo (series 6 mobo, 1 pci-e x16 and one x1), the cpu and 2X4gb ddr3 1600 memory. i didn't expressly buy the cpu in order to get HD3000 graphics.
so, i have the pci-e x16 slot and a spare card, but i always like to take the difficult path!!
> since both kexts included several other device/vendor id's, i decided to add both the 0112 and the 0126 id's.
> this was a fry's bundle for $170, for the mobo (series 6 mobo, 1 pci-e x16 and one x1), the cpu and 2X4gb ddr3 1600 memory. i didn't expressly buy the cpu in order to get HD3000 graphics.
> so, i have the pci-e x16 slot and a spare card, but i always like to take the difficult path!!
Understood, I would have been the same way, just to see if it worked. Do keep us informed of your progress and you might also check this out too:
i looked at the macbreaker link you sent. it was for HD4000, and i did consider figuring out how to make the changes in chameleon for HD3000 the writer had made for HD4000, but i had no idea where to start.
then i found another macbreaker article about ML and HD3000. the suggestion was to use a macmini smbios. maybe that is the only desktop that apple has used HD3000 graphics in. but, the key item in the article was to use the DVI onboard port, since the mac mini doesn't have a VGA port and osx therefore doesn't have vga support.
before changing the system def from mac pro to mac mini, i first wanted to try the dvi output.
voila--i moved the hack to another room where i have a dvi monitor, and it works!!
(the fine print: this mobo, and maybe other 1155 mobos, have a DVI-D connector, which just outputs digital signals (whereas DVI-I outputs both digital and analog, and will support a DVI to VGA adapter). the "spotting" difference is the DVI-I has two pins on each side of the flat pin (those four pins carry the analog signal), and the DVI-D has no pins in the area of the flat pin. so, a dvi to vga connector can't be used, but a dvi to hdmi connector does work, as of course will a normal dvi monitor cable.)
> i looked at the macbreaker link you sent. it was for HD4000, and i did consider figuring out how to make the changes in chameleon for HD3000 the writer had made for HD4000, but i had no idea where to start.
> then i found another macbreaker article about ML and HD3000. the suggestion was to use a macmini smbios. maybe that is the only desktop that apple has used HD3000 graphics in. but, the key item in the article was to use the DVI onboard port, since the mac mini doesn't have a VGA port and osx therefore doesn't have vga support.
I believe that was the 2nd MacBreaker link I sent. Didn't see it the first time.
> before changing the system def from mac pro to mac mini, i first wanted to try the dvi output.
> voila--i moved the hack to another room where i have a dvi monitor, and it works!!
> (the fine print: this mobo, and maybe other 1155 mobos, have a DVI-D connector, which just outputs digital signals (whereas DVI-I outputs both digital and analog, and will support a DVI to VGA adapter). the "spotting" difference is the DVI-I has two pins on each side of the flat pin (those four pins carry the analog signal), and the DVI-D has no pins in the area of the flat pin. so, a dvi to vga connector can't be used, but a dvi to hdmi connector does work, as of course will a normal dvi monitor cable.)
Funny how the little things seem to make all the difference these days.
From the main system of mosslack...
______________________________
Alt-OS <+> GG <+> TBIE <+> Hack List
