Jump to content

Intel HD 3000 no graphics


bbm21
 Share

156 posts in this topic

Recommended Posts

Hi

 

should it be Device (MEI), instead of Device (IMEI) ?

 

in

 

Device (IMEI)

            {

                Name (_ADR, 0x00160000)

                Method (_DSM, 4, NotSerialized)

                {

                    If (LEqual (Arg2, Zero))

                    {

                        Return (Buffer (One)

                        {

                            0x03

                        })

                    }

 

                    Return (Package (0x04)

                    {

                        "device-id", 

                        Buffer (0x04)

                        {

                            0x3A, 0x1C, 0x00, 0x00

                        }, 

 

                        "name", 

                        "pci8086,1c3a"

                    })

                }

No. Apple uses IMEI.

 

I am trying to get QE/CI to work on Acer W700 iconia tablet with sandybridge and HD 3000, so far same problems as those reported above :-(

 

Details of my attempts and the specs of the tablet are in the Tablet thread Acer W700.

 

http://www.insanelymac.com/forum/topic/299346-acer-iconia-w700/

What is the output of 'lspci -nn' in Linux Terminal?

  • Like 1
Link to comment
Share on other sites

No. Apple uses IMEI.

 

 

What is the output of 'lspci -nn' in Linux Terminal?

Thanks, but there is also a Device MEI section, no?

or does it have to be called Device IMEI?

 

I will get you the output later.

 

I am using a DSDT of iMac 12 from a peep, it allows me to get audio, and he uses Device MEI, I will attach it too.

 

By the way, the MEI ID for the Acer W700 i3 is 0x1E3A8086 and not 0x1C3A8086, FBCapri uses 0x1E3A8086, and the other FB uses 0x1C3A8086, maybe each kext just caters for each chip?

No. Apple uses IMEI.

 

 

What is the output of 'lspci -nn' in Linux Terminal?

Here goes:

 

00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09)
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09)
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
00:1f.0 ISA bridge [0601]: Intel Corporation HM77 Express Chipset LPC Controller [8086:1e57] (rev 04)
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04)
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04)
01:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01)
 
and the dsdt I am using as a base, attached.

DSDT.aml.zip

Link to comment
Share on other sites

Thanks, but there is also a Device MEI section, no?

or does it have to be called Device IMEI?

I believe OS X matches specifically against IMEI. I can't remember what driver looks for it, but it has come up a few times... whatever the issue was, it was fixed by adding IMEI or renaming existing device to IMEI.

 

By the way, the MEI ID for the Acer W700 i3 is 0x1E3A8086 and not 0x1C3A8086, FBCapri uses 0x1E3A8086, and the other FB uses 0x1C3A8086, maybe each kext just caters for each chip?

Generally you see HD4000 on 7-series (MEI is 1e3a). HD3000 on 6-series (MEI 1c3a). The problems come in when you have a mixed system (HD3000 on 7-series, or HD4000 on 6-series). OS X was not designed for that configuration as real Apple hardware would never have it.

 

Here goes:

 

00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09)

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09)

00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)

00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)

...

Clearly HD3000 on 7-series. Which is why you need the device-id injection to inject 1c3a.

  • Like 1
Link to comment
Share on other sites

Thanks,

 

so you suggest I change Device (MEI) to Device (IMEI) in the DSDT.aml?

 

and leave 1c3a as is?

 

I believe OS X matches specifically against IMEI. I can't remember what driver looks for it, but it has come up a few times... whatever the issue was, it was fixed by adding IMEI or renaming existing device to IMEI.


Generally you see HD4000 on 7-series (MEI is 1e3a). HD3000 on 6-series (MEI 1c3a). The problems come in when you have a mixed system (HD3000 on 7-series, or HD4000 on 6-series). OS X was not designed for that configuration as real Apple hardware would never have it.


Clearly HD3000 on 7-series. Which is why you need the device-id injection to inject 1c3a.

Link to comment
Share on other sites

My patch is here: https://github.com/RehabMan/Laptop-DSDT-Patch, "HD3000 on 7-series"

You mean this:

 

Device (MEI)
           {
               Name (_ADR, 0x00160000)  // _ADR: Address
               Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
               {
                   Store (Package (0x0C)
                       {
                           "device-id", 
                           Buffer (0x02)
                           {
                                0x3A, 0x1C
                           }, 
 
                           "IOName", 
                           Buffer (0x0D)
                           {
                               "pci8086,1c3a"
                           }, 
 
                           "name", 
                           Buffer (0x0D)
                           {
                               "pci8086,1c3a"
                           }, 
 
                           "revision-id", 
                           Buffer (0x04)
                           {
                                0x04, 0x00, 0x00, 0x00
                           }, 
 
                           "subsystem-vendor-id", 
                           Buffer (0x04)
                           {
                                0x86, 0x80, 0x00, 0x00
                           }, 
 
                           "vendor-id", 
                           Buffer (0x04)
                           {
                                0x86, 0x80, 0x00, 0x00
                           }
                       }, Local0)
                   DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                   Return (Local0)
               }
           }

My patch is here: https://github.com/RehabMan/Laptop-DSDT-Patch, "HD3000 on 7-series"

or this, or both?

 

#Maintained by: RehabMan for: Laptop Patches
#graphics_MEI_sandy.txt
 
# For Sandy Bridge CPU on 7-series board
 
into device label IMEI parent_label PCI0 remove_entry;
into device label PCI0 insert
begin
Device (IMEI)\n
{\n
    Name (_ADR, 0x00160000)\n
    Method (_DSM, 4, NotSerialized)\n                
    {\n
        If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n
        Return (Package()\n
        {\n
            "device-id", Buffer() { 0x3A, 0x1C, 0x00, 0x00 },\n
            "name", "pci8086,1c3a",\n
        })\n
    }\n
}\n
end;
Link to comment
Share on other sites

No. I mean what I wrote. Be certain to read the README so you're using MaciASL as intended.

 

There are two patches, one with Device (MEI) and the other with Device (IMEI), 

 

which one shall I use?

 

The DSDT I have has only an entry with Device (MEI)like this:

 

 Device (MEI)
            {
                Name (_ADR, 0x00160000)
                Method (_DSM, 4, NotSerialized)
                {
                    Store (Package (0x0E)
                        {
                            "compatible", 
                            Buffer (0x2C)
                            {
                                "pci8086,7270, pci8086,1c3a, pciclass,078000"
                            }, 
 
                            "device-id", 
                            Buffer (0x02)
                            {
                                0x3A, 0x1C
                            }, 
 
                            "IOName", 
                            Buffer (0x0D)
                            {
                                "pci8086,1c3a"
                            }, 
 
                            "name", 
                            Buffer (0x0D)
                            {
                                "pci8086,1c3a"
                            }, 
 
                            "revision-id", 
                            Buffer (0x04)
                            {
                                0x04, 0x00, 0x00, 0x00
                            }, 
 
                            "subsystem-vendor-id", 
                            Buffer (0x04)
                            {
                                0x86, 0x80, 0x00, 0x00
                            }, 
 
                            "vendor-id", 
                            Buffer (0x04)
                            {
                                0x86, 0x80, 0x00, 0x00
                            }
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }
            }

No. I mean what I wrote. Be certain to read the README so you're using MaciASL as intended.

I think I finally got you, you want me to use the app macIASL to do the patching automatically, silly me ;-)

Link to comment
Share on other sites

@RehabMan

 

I like your MacIASL, very nice streamline of patches, and very easy to use.

 

I did as you suggested in the Readme, and patched the DSDT, but no luck, still getting the

SNB framebuffer didn't show up, unload.

 

I reverted to almost complete vanilla 10.9.0 install, still same.

 

I cannot get into the GUI if the SNB framebuffer kext has the plists inside.

 

The 10.9.0 is like that.

 

If I upgrade to 10.9.x, it breaks, and I have to remove Info.plist of SNBF* to get into the GUI.

 

The DSDT patch did not help.

 

Any other suggestions?

Link to comment
Share on other sites

Giving up, I don't think it is possible to get QE/CI on Intel hybrids.

 

All is to do with the Info.plist into the kext AppleIntelSNBGraphicsFB.kext, the DSTD patch cannot override it,  and it fails to load the GUI.

 

If the Info.plist is removed, then the GUI loads but without QE/CI.

Link to comment
Share on other sites

@RehabMan

 

 

I like your MacIASL, very nice streamline of patches, and very easy to use.

 

I did as you suggested in the Readme, and patched the DSDT, but no luck, still getting the

SNB framebuffer didn't show up, unload.

 

I reverted to almost complete vanilla 10.9.0 install, still same.

 

I cannot get into the GUI if the SNB framebuffer kext has the plists inside.

 

The 10.9.0 is like that.

 

If I upgrade to 10.9.x, it breaks, and I have to remove Info.plist of SNBF* to get into the GUI.

 

The DSDT patch did not help.

 

Any other suggestions?

No idea without photo of verbose boot.

 

Why 10.9.0? Where are you getting your 10.9.0 image?

Giving up, I don't think it is possible to get QE/CI on Intel hybrids.

Definitely possible.
Link to comment
Share on other sites

No idea without photo of verbose boot.

 

Why 10.9.0? Where are you getting your 10.9.0 image?

Definitely possible.

 

not much on verbose boot, all is normal apart from before loading graphics I get, twice:

 

SNB Framebuffer didn't show up, unload.

 

then the graphics loads.

 

10.9.0 is the official version from Apple Store I got off a friend who has a real Mac, when it was first available back when it was released.

 

Then I use Apple Automated Updates to bring me to 10.9.5, which I do with my Dell Dimension 9200 PC which works perfectly with my mods (I wrote about it here)

 

The GUI is nice on Acer W700, just no CI, maybe QE I am not sure.

 

It does load AppleIntelHD3000Graphics.kext though.

 

Strangely, if I upgrade to 10.9.4 or 10.9.5, the Video RAM reduces from 64 MB shared memory to 7 MB.

Link to comment
Share on other sites

not much on verbose boot, all is normal apart from before loading graphics I get, twice:

 

SNB Framebuffer didn't show up, unload.

 

then the graphics loads.

 

10.9.0 is the official version from Apple Store I got off a friend who has a real Mac, when it was first available back when it was released.

 

Then I use Apple Automated Updates to bring me to 10.9.5, which I do with my Dell Dimension 9200 PC which works perfectly with my mods (I wrote about it here)

 

The GUI is nice on Acer W700, just no CI, maybe QE I am not sure.

 

It does load AppleIntelHD3000Graphics.kext though.

 

Strangely, if I upgrade to 10.9.4 or 10.9.5, the Video RAM reduces from 64 MB shared memory to 7 MB.

No idea without a photo and/or system.log.

 

You forgot to answer a couple of my questions...

Link to comment
Share on other sites

No idea without a photo and/or system.log.

 

You forgot to answer a couple of my questions...

I think to have answered your questions, maybe you mean how I installed Mavericks?

 

This particular one for the Acer, I used the myHack 3.3 app, and I use chameleon, not clover, with Acer booted in legacy mode.

Link to comment
Share on other sites

I think to have answered your questions, maybe you mean how I installed Mavericks?

 

This particular one for the Acer, I used the myHack 3.3 app, and I use chameleon, not clover, with Acer booted in legacy mode.

You should do a vanilla install instead. Make sure you download Mavericks from the Mac App Store.

Link to comment
Share on other sites

You should do a vanilla install instead. Make sure you download Mavericks from the Mac App Store.

Sure,

 

instructions on how to make a bootable usb or dvd to do so?

 

PS. As I said, I have the original downloaded installation app downloaded from the Mac App Store.

 

I think I got it:

 

http://www.insanelymac.com/forum/topic/289062-109-mavericks-simple-vanilla-hackintosh-install-guide/

Link to comment
Share on other sites

Sure,

 

instructions on how to make a bootable usb or dvd to do so?

 

PS. As I said, I have the original downloaded installation app downloaded from the Mac App Store.

 

I think I got it:

 

http://www.insanelymac.com/forum/topic/289062-109-mavericks-simple-vanilla-hackintosh-install-guide/

 

we don´t care how you get the .app

 

don´t worry.

  • Like 1
Link to comment
Share on other sites

hd 3000 work well 

Good for you.

 

Not working on the Acer W700 hybrid Intel i3.

 

Well not yet for me, anyway.

I'm sure you'll find a guide here if you search...

OK, I reinstalled from scratch, using a fresh download from the App Store.

 

Vanilla, modulo having to remove Intel graphics kexts and AppleIntelCPUPowerManagement.kext, and adding fakesmc.kext and nullcpupowermanagement.kext, the last not averting the kernel panic I got.

 

It gives 10.9.4 by the way.

 

Still same problem, 

 

SNB Framebuffer didn't show up, unload

 

with a DSDT.aml with your patch injected.

 

I think I need to get a MacBook Pro 8,1 or 8,2 DSDT as this is the smbios.plist I am using, the combo from iMac 12,2 is not lucky, and extracting directly the DSDT vanilla gives me errors :(

Link to comment
Share on other sites

Good for you.

 

Not working on the Acer W700 hybrid Intel i3.

 

Well not yet for me, anyway.

 

OK, I reinstalled from scratch, using a fresh download from the App Store.

 

Vanilla, modulo having to remove Intel graphics kexts and AppleIntelCPUPowerManagement.kext, and adding fakesmc.kext and nullcpupowermanagement.kext, the last not averting the kernel panic I got.

 

It gives 10.9.4 by the way.

 

Still same problem, 

 

SNB Framebuffer didn't show up, unload

 

with a DSDT.aml with your patch injected.

 

I think I need to get a MacBook Pro 8,1 or 8,2 DSDT as this is the smbios.plist I am using, the combo from iMac 12,2 is not lucky, and extracting directly the DSDT vanilla gives me errors :(

Mac App Store download will provide 10.9.5.

 

You need to use your own DSDT, not some DSDT from another computer. If there are errors in the native DSDT, you'll need to fix them. There are some very common errors that are easily fixed with patches in my repo.

 

If you need further help, post your /Extra/smbios.plist, /Extra/org.chameleon.Boot.plist, native DSDT.aml, and patched /Extra/DSDT.aml and also a photo of verbose boot.

  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...