Jump to content
InsanelyMac Forum
All Kand

[FIXED] Intel GMA HD 5700MHD

Recommended Posts

@Duncan Leo the values depends on your panels properties and to know those values you should have ur EDID and or have a program to interpret it " it will give you all that values the priview should be like this from linux

 

 

[ 92.907] (II) intel(0): Supported detailed timing:

[ 92.907] (II) intel(0): clock: 69.3 MHz Image Size: 344 x 193 mm

[ 92.907] (II) intel(0): h_active: 1366 h_sync: 1398 h_sync_end 1422 h_blank_end 1432 h_border: 0

[ 92.907] (II) intel(0): v_active: 768 v_sync: 771 v_sync_end 775 v_blanking: 806 v_border: 0

 

 

or like this

 

[ 92.908] (II) intel(0): Printing probed modes for output LVDS1

[ 92.908] (II) intel(0): Modeline "1366x768"x60.0 69.30 1366 1398 1422 1432 768 771 775 806 -hsync -vsync (48.4 kHz)

[ 92.908] (II) intel(0): Modeline "1360x768"x59.8 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsync (47.7 kHz)

[ 92.908] (II) intel(0): Modeline "1360x768"x60.0 72.00 1360 1408 1440 1520 768 771 781 790 +hsync -vsync (47.4 kHz)

[ 92.908] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)

[ 92.908] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)

[ 92.908] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)

[ 92.908] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)

Share this post


Link to post
Share on other sites
Advertisement

So, is this finally working??? I dont get it!!!... why is the topic named as [FIXED]???/... thnx to all that are working on it... GOOD LUCK!!! :)

Share this post


Link to post
Share on other sites

So, is this finally working??? I dont get it!!!... why is the topic named as [FIXED]???/... thnx to all that are working on it... GOOD LUCK!!! :)

 

Read the first post

Share this post


Link to post
Share on other sites

Sorry, but still dont get it... i did that guide a long time ago, and yes i get some acceleration but no custom res, but without it i cant work as i would like to, and erase my partition.

 

So, i read the entire post and what i understood was that G62 is still working on a framebuffer to get custom res, so we have to wait to our genius get it... if im wrong let me know please, also if need tester or if you make a complete guide, thnx once again :)

Share this post


Link to post
Share on other sites

Sorry, but still dont get it... i did that guide a long time ago, and yes i get some acceleration but no custom res, but without it i cant work as i would like to, and erase my partition.

 

Yes. You need to do that first. Then, what you do is, like the post says, set up screen sharing (through VNC), and use Chicken of the VNC on the same computer to view your hackintosh. After that, you can minimize the window and watch all former problems with QE/CI disappear (like distortions using Finder, Kernel Panics when loading full screen in applications, etc.) This fix does NOT enable custom resolution.

 

So, i read the entire post and what i understood was that G62 is still working on a framebuffer to get custom res, so we have to wait to our genius get it... if im wrong let me know please, also if need tester or if you make a complete guide, thnx once again :)

Yes, G62 is working on a framebuffer. He has made great progress in enabling our Graphics Card (still with 64 mb of shared VRAM) and getting it to our custom resolution. Using a newer version with my EDID information, I got the kext to work. The problem: Mac OS X doesn't know our graphics card has a new resolution, and it still is outputing 1024x768. And before you ask, SwitchResX doesn't work.

 

However, I do have something new to report: When using this card with all fixes above, I was able to extend the amount of VRAM from 64 MB to 1280 MB!! Here's what I did. I did all fixes I mentioned (QE/CI fix, Chicken of the VNC fix, AppleSamplePCI.kext by G62), HOWEVER, instead of enabling Chameleon's GraphicsEnabler, I used manor's EFI string in my com.apple.Boot.plist. This got it up to 1280 MB of RAM and getting the card name right in System Profiler. I think it saying "IntelHDGraphics" in System Profiler is only a cosmetic fix; I'm not sure if the GPU is detected by OS X. How can I know for sure? And is anyone able to replicate my result?

Share this post


Link to post
Share on other sites

Wow... thanx for the long explanation, it seems that there is a huge progress about it, i will try the Chiken fix, and the kext from g62, i hope to get same results as you, (better would be awesome), and then wait to G62 to his miracle kext or fix!!!.../

 

Thanx again to all of you for all your effort!!!

Share this post


Link to post
Share on other sites

Guys, i need your input!

 

I'm trying to get Intel HD Graphics to work with a DSDT injection.

I tried to inject it and now with original kexts i got a KP, so it does not hang on boot.

 

I need someone with a MBP6,1 or MBP6,2 to get this infos: (about HD Graphics)

  • Device ID
  • Vendor ID
  • Subsystem Vendor ID
  • Subsystem Device ID
  • Revision

 

Thanks to all in advance!

Share this post


Link to post
Share on other sites

Guys, i need your input!

 

I'm trying to get Intel HD Graphics to work with a DSDT injection.

I tried to inject it and now with original kexts i got a KP, so it does not hang on boot.

 

I need someone with a MBP6,1 or MBP6,2 to get this infos: (about HD Graphics)

  • Device ID
  • Vendor ID
  • Subsystem Vendor ID
  • Subsystem Device ID
  • Revision

Thanks to all in advance!

 

Whoa!! Slow down. First, how are you trying to get DSDT injection to enable the Intel HD Graphics? What is your reasoning, and what are you changing? Second, is the KP early in the boot stage like "Could not find driver for this platform: ACPI" or is it something else? Because in my earlier attempts to use a DSDT, I got that kernel panic. I eventually gave up using it because I found out I was only using a version that would be read from my computer directly, anyway, and unless I had something to change for something to work (which I didn't), there was no need for a DSDT.aml file.

Share this post


Link to post
Share on other sites

I tried to inject the GFX0 Device with _DSM Method (changing infos of GFX). I can boot with original kexts with "GE=Yes -v" but the screen is:

20r2ouv.jpg

Strange :| . I need more info about injecting the display into DSDT.

 

These values are picked up from IORegistryExplorer (on SL 10.6.7 w/ Partial QE/CI)

 

 

Other useful Info:

 

Chipset Model: Intel HD Graphics

Type: GPU

Bus: Built-In

VRAM (Total): 288 MB

Vendor: Intel (0x8086)

Device ID: 0x0046

Revision ID: 0x0012

gMux Version: 1.9.21

Displays:

Display Connector:

Status: No Display Connected

 

So, the new DSDT Code will be like: (add in Device (GFX0))

			Method (_DSM, 4, NotSerialized)
			{
				Store (Package (0x12)
					{
						"model",
						Buffer (0x11)
						{
							"Intel HD Graphics"
						},
						"built-in",
						Buffer (One)
						{
							0x01
						},
						"device-type",
						Buffer (0x08)
						{
							"display"
						},
						"device-id",
						Unicode ("F"),
						"vendor-id",
						Buffer (0x04)
						{
							 0x86, 0x80, 0x00, 0x00
						},
						"subsystem-vendor-id",
						Buffer (0x04)
						{
							 0x6B, 0x10, 0x00, 0x00
						},
						"subsystem-id",
						Buffer (0x04)
						{
							 0x3A, 0x14, 0x00, 0x00 <--- THIS IS WRONG!
						},
						"revision-id",
						Buffer (0x04)
						{
							 0x12, 0x00, 0x00, 0x00
						},
						"VRAM,totalsize",
						Buffer (0x04)
						{
							0x00, 0x00, 0x00, 0x12
						}
					}, Local0)
				DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
				Return (Local0)
			}

 

I think if we can grab the right values, we can have fully QE/CI.

Share this post


Link to post
Share on other sites

I have been trying to get the 10.7.4 lion kexts to work for a while now. From what I can see the frame buffer is needed as it looks like this does the VRAM allocation and many other things. On mine with only the AppleIntelHDGraphics kext loaded I get the screen scrambled, via screen sharing there are ways I can get it to show the correct Graphics type but I think these are only cosmetic. I can get the Lion frame buffer to load on mine but have to add the following to the graphics card section of the DSDT using the above method in giofrida's post.

"AAPL,os-info",
Buffer (0x14)
{
/* 0000 */   0x30, 0x49, 0x01, 0x11, 0x01, 0x10, 0x08, 0x00,
/* 0008 */   0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
/* 0010 */   0xFF, 0xFF, 0xFF, 0xFF
},

 

I can see a section in the kext which looks for this value, without the os-info addition and the frame buffer I get the spinning thingy continually at startup, with the os-info addition I get a grey screen eventually, and a lot more promising entries in the registry when viewed via screen sharing and it shows 768Mb of video memory. When I tried injecting the VRAM size as above this caused me problems, one of the kexts would not load, can't remember which, but with the frame buffer loaded it shows this value anyway.

 

I think the problem I have is it is now not detecting the screen at all to get the size and timing information, display information is blank which without the intel frame buffer shows at least some information even if wrong. I tried many ways to try and inject display EDID information without success. What I did wonder is if the default NDRIV framebuffer on a real Mac gets this information, on our systems with a single graphics card because the Intel frame buffer has grabbed the card, the NDriv framebuffer can't get any information out of the display. I know without the Intel FB the Ndriv FB loads and shows in ioregistryexplorer against the Intel graphics. If this is the case perhaps someone could write a fake ndriv frame buffer that just reads the information, I believe the source code is available for this frame buffer?

 

Hope this helps someone get a little further, unfortunately I have made many changes to my DSDT to get it nearer to a real MacBookPro 6.2 so not sure if there are any other changes that have helped my intel framebuffer kext to load.

Share this post


Link to post
Share on other sites
I have been trying to get the 10.7.4 lion kexts to work for a while now.

Just a quick question. Did you try this with Snow Leopard? I would try Lion, but until I get graphics working, I only have an old version of iMovie that requires Rosetta to run.

Share this post


Link to post
Share on other sites

Just a quick question. Did you try this with Snow Leopard? I would try Lion, but until I get graphics working, I only have an old version of iMovie that requires Rosetta to run.

 

No unfortunately only have Lion around these days, bit of a pain to install on my laptop and get running.

Share this post


Link to post
Share on other sites

I decided to cave in and give Lion a shot, but:

I can get the Lion frame buffer to load on mine but have to add the following to the graphics card section of the DSDT using the above method in giofrida's post.

"AAPL,os-info",
Buffer (0x14)
{
/* 0000 */   0x30, 0x49, 0x01, 0x11, 0x01, 0x10, 0x08, 0x00,
/* 0008 */   0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
/* 0010 */   0xFF, 0xFF, 0xFF, 0xFF
},

 

I'm confused as to WHERE in the DSDT this should go. You mention giofordia's post, but can't find exactly where to put it. Googling around didn't help at all. Can you help me?

Share this post


Link to post
Share on other sites

You need to find the Graphics section of your DSDT, probably called GFX0 or IGPU then add this code under it

Method (_DSM, 4, NotSerialized)
		    {
					    Store (Package (0x0A)
						    {
							    "hda-gfx",
							    Buffer (0x0A)
							    {
								    "onboard-1"
							    },
							    "device_type",
							    Buffer (0x08)
							    {
								    "display"
							    },
							    "model",
							    Buffer (0x12)
							    {
								    "Intel HD Graphics"
							    },
							    "built-in",
							    Buffer (One)
							    {
									 0x01
							    },
							    "AAPL,os-info",
							    Buffer (0x14)
							    {
								    /* 0000 */   0x30, 0x49, 0x01, 0x11, 0x01, 0x10, 0x08, 0x00,
								    /* 0008 */   0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
								    /* 0010 */   0xFF, 0xFF, 0xFF, 0xFF
							    }
						    }, Local0)
					    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					    Return (Local0)
   }

 

You will also need to add the DTGP method in not already included in your DSDT, this is a fairly common method of injecting stuff, used to trick kexts into think the hardware is something other than it is and used a lot in fixes, if you look at some of the standard hacks in DSDTSE you will see it frequently used.

Share this post


Link to post
Share on other sites

Thanks for the help, ebmesnow, and now I'm getting these errors in compiling the DSDT.aml.

 

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20100331 [Mar 31 2010]
Copyright (c) 2000 - 2010 Intel Corporation
Supports ACPI Specification Revision 4.0
dsdt.dsl  5284:					 Name (NBTT, Package (0x08)
Remark   5048 -											 ^ Initializer list shorter than declared package length
dsdt.dsl  6327:					 Method (BINI, 0, NotSerialized)
Warning  1088 -								^ Not all control paths return a value (BINI)
dsdt.dsl  7056:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  7060:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  7119:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  7123:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  7188:							 Name (_PLD, Buffer (0x10)
Error	4080 -			  Invalid object type for reserved name ^  (found BUFFER, requires Package)
dsdt.dsl  7205:							 Name (_PLD, Buffer (0x10)
Error	4080 -			  Invalid object type for reserved name ^  (found BUFFER, requires Package)
dsdt.dsl  7275:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  7279:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  7338:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  7342:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  7453:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  7457:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  7516:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  7520:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  7631:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  7635:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  7694:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  7698:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  7809:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  7813:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  7872:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  7876:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  7987:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  7991:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  8050:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  8054:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  8165:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  8169:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  8228:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  8232:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  8343:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  8347:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  8406:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  8410:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  8521:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  8525:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  8584:								 Name (_T_0, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_0)
dsdt.dsl  8588:									 Name (_T_1, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_1)
dsdt.dsl  9671:				 Method (_WED, 1, NotSerialized)
Warning  1099 -	  Unknown reserved name ^  (_WED)
dsdt.dsl  9671:				 Method (_WED, 1, NotSerialized)
Warning  1099 -	  Unknown reserved name ^  (_WED)
dsdt.dsl  9671:				 Method (_WED, 1, NotSerialized)
Warning  1099 -	  Unknown reserved name ^  (_WED)
dsdt.dsl  9671:				 Method (_WED, 1, NotSerialized)
Warning  1099 -	  Unknown reserved name ^  (_WED)
dsdt.dsl  9671:				 Method (_WED, 1, NotSerialized)
Warning  1099 -	  Unknown reserved name ^  (_WED)
dsdt.dsl  9731:					 Name (_T_0, Zero)
Remark   5111 -							  ^ Use of compiler reserved name (_T_0)
dsdt.dsl  9944:					 Name (_T_0, Zero)
Remark   5111 -							  ^ Use of compiler reserved name (_T_0)
dsdt.dsl 10505:							 Name (_T_0, Zero)
Remark   5111 -		Use of compiler reserved name ^  (_T_0)
dsdt.dsl 10601:					 Name (_T_0, Zero)
Remark   5111 -							  ^ Use of compiler reserved name (_T_0)
dsdt.dsl 10669:					 Name (_T_0, Zero)
Remark   5111 -							  ^ Use of compiler reserved name (_T_0)
dsdt.dsl 10728:					 Name (_T_0, Zero)
Remark   5111 -							  ^ Use of compiler reserved name (_T_0)
dsdt.dsl 11192:						 Name (_T_0, Zero)
Remark   5111 -	Use of compiler reserved name ^  (_T_0)
dsdt.dsl 11196:							 Name (_T_1, Zero)
Remark   5111 -		Use of compiler reserved name ^  (_T_1)
dsdt.dsl 11220:								 Name (_T_2, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_2)
dsdt.dsl 11242:									 Name (_T_3, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_3)
dsdt.dsl 11267:										 Name (_T_4, Zero)
Remark   5111 -					Use of compiler reserved name ^  (_T_4)
dsdt.dsl 11306:											 Name (_T_5, Zero)
Remark   5111 -						Use of compiler reserved name ^  (_T_5)
dsdt.dsl 11348:						 Name (_T_6, Zero)
Remark   5111 -	Use of compiler reserved name ^  (_T_6)
dsdt.dsl 11352:							 Name (_T_7, Zero)
Remark   5111 -		Use of compiler reserved name ^  (_T_7)
dsdt.dsl 11372:								 Name (_T_8, Zero)
Remark   5111 -			Use of compiler reserved name ^  (_T_8)
dsdt.dsl 11394:									 Name (_T_9, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_9)
dsdt.dsl 11419:										 Name (_T_A, Zero)
Remark   5111 -					Use of compiler reserved name ^  (_T_A)
dsdt.dsl 11454:											 Name (_T_B, Zero)
Remark   5111 -						Use of compiler reserved name ^  (_T_
dsdt.dsl 11503:					 Name (_T_0, Zero)
Remark   5111 -							  ^ Use of compiler reserved name (_T_0)
dsdt.dsl 11508:						 Name (_T_1, Zero)
Remark   5111 -	Use of compiler reserved name ^  (_T_1)
dsdt.dsl 11562:					 Name (_T_0, Zero)
Remark   5111 -							  ^ Use of compiler reserved name (_T_0)
dsdt.dsl 11618:						 Name (_T_1, Zero)
Remark   5111 -	Use of compiler reserved name ^  (_T_1)
dsdt.dsl 11658:									 Name (_T_2, Zero)
Remark   5111 -				Use of compiler reserved name ^  (_T_2)
dsdt.dsl 11720:				 Name (_WDG, Buffer (0xF0)
Warning  1099 -	Unknown reserved name ^  (_WDG)
dsdt.dsl 13491:						 Subtract (Local0, 0x03)
Warning  1106 -										^ Result is not used, operator has no effect
ASL Input:  dsdt.dsl - 14562 lines, 538932 bytes, 6032 keywords
Compilation complete. 2 Errors, 8 Warnings, 60 Remarks, 8 Optimizations
[Completed]

Can you help me, please? Thanks in advanced!

Share this post


Link to post
Share on other sites

Thanks for the help, ebmesnow, and now I'm getting these errors in compiling the DSDT.aml.

Can you attach your DSDT and I will have a look, have you done this before? Some of the DSDT compilations are known to be full of errors before, does not look like anything we have introduced.

Share this post


Link to post
Share on other sites

I have a question...

 

What is AAPL,os-info? What does it do?

 

Also the FB detects my screen properly just that the screen would have a backlight with no image...

 

I also get a screwed up graphics if I boot with the display on VGA. My laptop is Lenovo T410. The DSDT I can try to edit... Any way for DSDT to get the image displayed?

 

My screen is 1280x800 btw

Share this post


Link to post
Share on other sites

Can you attach your DSDT and I will have a look, have you done this before? Some of the DSDT compilations are known to be full of errors before, does not look like anything we have introduced.

Sorry I didn't reply sooner, but I managed to use a different DSDT editor and compiler to compile the source code created by DSDTDE. I managed to install Lion with it just fine, but I get this kernel panic when trying to boot the installation:

post-529889-0-15235700-1344880105_thumb.jpg

 

I also have attached my compiled DSDT.aml as well as my error-filled DSDT source code. Please take a look at it. And yes, this is the first time I am using DSDT fixes.

my-dsdt.zip

Share this post


Link to post
Share on other sites

I recently found a link to this useful open source tool on Apple's User forums (of all places), where a user of a real Macbook Pro (I think with the same Graphics card as us) wanted to use the integrated Graphics. Here is what one user said to use:

http://codykrieger.com/gfxCardStatus

 

If we use this tool (starting it by screen sharing), we may be able to use Vanilla Kexts (with or without DSDT?) to switch to the Intel HD Graphics card without kext modding, etc.

Share this post


Link to post
Share on other sites

I recently found a link to this useful open source tool on Apple's User forums (of all places), where a user of a real Macbook Pro (I think with the same Graphics card as us) wanted to use the integrated Graphics. Here is what one user said to use:

http://codykrieger.com/gfxCardStatus

 

If we use this tool (starting it by screen sharing), we may be able to use Vanilla Kexts (with or without DSDT?) to switch to the Intel HD Graphics card without kext modding, etc.

 

dont waste Time on this application its a nogo

tryed this 2 years ago

 

Sorry for the bad news

 

read the original thread of GMA 5700

 

 

kind regards

fmac

Share this post


Link to post
Share on other sites

dont waste Time on this application its a nogo

tryed this 2 years ago

 

Sorry for the bad news

 

read the original thread of GMA 5700

 

 

kind regards

fmac

 

I read the original thread, and the reason it DIDN'T Work was because of 4 screens without being able to see the menu bar. I suggested trying to enable screen sharing, but I can't test this out (as of now) because of network issues. Specifically, my built in wi-fi is unsupported, my built in ethernet is supported, but I can't get the kexts to enable it for the life of me. And I have the infamous Netgear WG111v3, and as many of you know, it doesn't save profiles (where WiFi default network configuration is stored) in lion, so I'll go start a thread to see if I can get Ethernet to work. I will say, though, for those that CAN get networking to work, try enabling the vanilla HD Graphics kexts, and start the program through screen sharing. We'll see what we can do if this program works.

 

P.S. If you are so convinced that it won't work, than why not modify the code to help us? After all, it's open source!!

Share this post


Link to post
Share on other sites

I read the original thread, and the reason it DIDN'T Work was because of 4 screens without being able to see the menu bar. I suggested trying to enable screen sharing, but I can't test this out (as of now) because of network issues. Specifically, my built in wi-fi is unsupported, my built in ethernet is supported, but I can't get the kexts to enable it for the life of me. And I have the infamous Netgear WG111v3, and as many of you know, it doesn't save profiles (where WiFi default network configuration is stored) in lion, so I'll go start a thread to see if I can get Ethernet to work. I will say, though, for those that CAN get networking to work, try enabling the vanilla HD Graphics kexts, and start the program through screen sharing. We'll see what we can do if this program works.

 

P.S. If you are so convinced that it won't work, than why not modify the code to help us? After all, it's open source!!

 

I had email the owner of the gfxcardstatus and the owner himself does not even know how the mechanism works. it is a work from another people.

Share this post


Link to post
Share on other sites

I have a developer-based idea on how to fix resolution on Intel HD Graphics. The problem: I'm only a beginner in developing. So, here is my idea:

 

If I understand G62's kext correctly, it is enabling the graphics card and extending the display to our EDID's resolution. However, OS X is still outputing 1024x768 because it doesn't have a framebuffer. However, if my idea is right, a framebuffer won't be needed.

 

I tried to use the VBIOS dump earlier in this post, but I couldn't get it to work. According to Slice (the developer of Clover on Project OS X forums), the reason is Chameleon has poor support of Intel VBIOS ROM files. Clover has better support for the use of Intel ROMs with its GraphicsInjector. However, the problem is that Clover is based off of UEFI firmware, so without a graphics driver for the firmware, it can only output three resolutions: 640x480, 800x600, and 1024x768. This is true for those who are even lucky that their VBIOS has their custom resolution and Chameleon picks it up: if those lucky people boot with Clover, OS X will only output 1024x768; switch back to Chameleon, and their custom resolution can be used.

 

I have two ideas: one Chameleon-based (which may or may not work), and one for Clover. First, the Clover one (because it needs to be based heavily off of G62's AppleSamplePCI.kext). Before Clover loads the boot menu, it loads EFI drivers. My idea is to port G62's kext to an EFI driver. Any driver, in theory, can be ported to EFI, but without knowing a good deal on how the driver works, it can be difficult. That's where G62's kext comes in. He knows how to code the driver. I think that if the kext is used before the OS is loaded, OS X may load our correct resolution (especially since the driver would enable the Graphics Card and have it output our correct resolution in EFI).

 

And as for a Chameleon fix, I'm not sure how we would start this one (other than looking at how 915resolution loads VBIOS info). We would need to have an external tool (perhaps a Grub2 module?) copy a patched VBIOS (or the VBIOS in the forum) into memory, and then chainload Chameleon from there. The idea here is to override the VBIOS by loading a different one into memory before Chameleon loads. This would enable Mac OS X to load a different resolution.

 

Anyways, those are my ideas. Like I said up above, I'm not a skilled developer, so if those are concepts that you think you can use, than feel free to try them out. I'd also like feedback: would these ideas even work at a first glance?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.



  • Similar Content

    • By MaLd0n
      Nehalem, SandyBridge, IvyBridge, Haswell, Broadwell     Skylake, Kabylake and Coffeelake is here http://www.insanelymac.com/forum/topic/321872-guide-sierra-on-gigabyte-mobos-serie-200-kabylake-dsdt/   First...   ***Update bios to last available version!***   If you need a full patched DSDT...  -Extract tables with F4 key in Clover boot screen! -Run it and send me files! RunMe.app   Installation   --Create a bootable copy of macOS Sierra Check out the link http://www.insanelymac.com/forum/files/file/559-flash-drive-maker/   --Create a bootable copy of macOS HighSierra Check out the link http://diskmakerx.com/   --Install Clover in USB stick https://sourceforge.net/projects/cloverefiboot/files/Installer/   --Replace with my Clover folder CLOVER Install.zip   --Install Sierra/High Sierra and boot into system!   Post Installation --Install Clover and replace with my folder CLOVER Post Install.zip   --Reboot and activate video!   Bingo!   Now you need a fine tune! DSDT time!   --DSDT   Patches -FIX ERRORS AND WARNINGS -HPET -SATA -DMAC -SLPB -DARWIN -LPC -XHCI -PLUGIN TYPE -XXXX to HDEF -HDEF -RTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -USBX -PMCR -EC -PNLF -HDMI
       
      --Power Management
      - 1 Generation Intel Processors, use Generate P and C States in config.plist
      - 2 and 3 Generations Intel Processors, Generate SSDT with Piker script and drop CpuPm and Cpu0Ist SSDTs
      ssdtPRGen.command.zip
      Credits-https://github.com/Piker-Alpha/ssdtPRGen.sh
      - 4 Generation+ Intel Processors, use PluginType=1 in DSDT, SSDT or Clover config.plist
       
      for check Power, Frequency, Temperature and Utilization, use it
      Install Intel Power Gadget.pkg.zip
       
      --Brightness
      Install .app, select the required permission and reboot. Work in F1 / F2 keys!
      NativeDisplayBrightness.app.zip


      https://github.com/Bensge/NativeDisplayBrightness/releases
      *in some cases .app don't work, check patches in config.plist inside Clover folder Post Install
       
      --Clover
       
      https://sourceforge.net/projects/cloverefiboot/files/Installer/
       
      --AUDIO
       
      Use DSDT + AppleAlc
       
      --install Lan driver by Mieze
        -Atheros http://www.insanelymac.com/forum/files/file/313-atherose2200ethernet/   -Intel http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/   -Realtek http://www.insanelymac.com/forum/files/file/88-realtekrtl8111-binary/   --Links   -FakeSMC https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek   -Audio https://github.com/vit9696/AppleALC http://www.insanelymac.com/forum/topic/314406-voodoohda-289/   -USB https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads   It's time to Rock   -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!   Apple, Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!   We're all here to have fun and learn from each other!  
    • By MaLd0n
      First... If you need DSDT edits... -Extract tables with F4 key in Clover boot screen! -Run it and send me files! RunMe.app   Installation --Create a bootable copy of El Capitan and Sierra Check out the link http://www.insanelymac.com/forum/files/file/559-flash-drive-maker/   --Create a bootable copy of macOS HighSierra Check out the link http://diskmakerx.com/   --Install Clover in USB stick https://sourceforge.net/projects/cloverefiboot/files/Installer/   --Replace with my Clover folder CLOVER Install.zip   --Install EL Capitan / Sierra / High Sierra and boot into system! for Sierra/High Sierra you need a Processor with SSE4.1 instruction   Post Installation --Install Clover and replace with my folder CLOVER Post Install.zip   --Reboot and activate video!   Bingo! Now you need a fine tune! DSDT Time! -Post your full Clover folder with original tables in Origin folder(Extract with F4 in Clover boot screen) and tell me what your hardware! -Post Ioreg, extract with Ioreg Explorer http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=222606 -Run it, post files generate in your desktop http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=222609    My DSDT GA P35-DS3 DSDT.MaLd0n LGA775.zip   Patches -FIX ERRORS AND WARNINGS -HPET -SATA -SLPB -DARWIN -LPC -HDEF -RTC -EHCI -UHCI -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -EC -PNLF --Native Power Management
       
      Use Clover, check Generate P and C States
       
      --Brightness
      Install .app, select the required permission and reboot. Work in F1 / F2 keys!
      NativeDisplayBrightness.app.zip


      https://github.com/Bensge/NativeDisplayBrightness/releases
      *in some cases .app don't work, check patches in config.plist inside Clover folder Post Install
       
      --AUDIO
       
      Device HDEF + AppleAlc + Lilu
       
      --install Lan driver by Mieze
        -Atheros http://www.insanelymac.com/forum/files/file/313-atherose2200ethernet/   -Intel http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/   -Realtek http://www.insanelymac.com/forum/files/file/88-realtekrtl8111-binary/   --Links   -FakeSMC https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek   -Audio https://github.com/vit9696/AppleALC http://www.insanelymac.com/forum/topic/293863-applehda-patch-requests/   -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!   Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!   We're all here to have fun and learn from each other!   ENJOY!  
    • By Gymnae
      This guide guide is a work in progress
       
      Introduction
      The H370 chipset powers 8th generation Core-i CPUs by Intel and is actually much newer than the Z370, even though it name implies otherwise. The H370 requires new approaches compared to the Z370, since it includes newer or different components. An example would be on-die USB 3.1 and WiFi support.
      Since this guide is not a "hold-your-hand-every-step" guide, I assume you know:
      Clover installation and configuration How to create an install medium BIOS configuration and access Have heard of ACPI patching (I'm a newb at this myself)  
      What works
      Sleep (via DSDT edits and emulated NVRAM) on-board Audio (via CloverALC script) Native PM (without any kext or patch) All USB ports iGPU for both acceleration and display dGPU (I'm running an Nvidia GTX 1080)  
      Untested
      NIC --> I'm using WiFi only  
      What doesn't work
      Native NVRAM via AptioMemoryFix.efi DMVT Pre-alloc higher than 64MB (but not necessary)  
      1. Installation
      This guide heavy inspired by the work of /u/corpnewt of /r/hackintosh and his (sorta) Vanilla guide
       
      1.1 Create the install media for MacOS
      Follow this, if you are using a Mac to start off with. If you are totally new to MacOS, then please check the basic guide Creation of an installer media in windows or linux
       
      1.2 Install Clover on the install media
      Using the Clover installer, ensure you are installing to the USB medium you are using for the installer.
      Chose the following options:
      AptioMemoryFix UEFI booting only Install to ESP You have to get your hands on an apfs.efi. A google search can help, or extracting it from the Installer package. Make sure you procure a version matching the MacOS version you are about to install. Place the apfs.efi in drivers64UEFI.
       
      1.2 Adjust the config.plist for the installer
      You can use the config.plist attached as a guideline, but take a look at it before and at least adjust the SMBIOS - otherwise it won't boot.
      Attention: The attached plist contains audio patches introduced by a post-install step. If you run into problems, you might remove those. It also contains a manual slide value, which should normally not be needed, but works fine for me. It is also tuned for usage with an Nvidia Pascal dGPU as main GPU.
       
      The config you create now should serve you nicely for install and running the system.
       
      Take care of adding the following basics:
      SMBIOS: iMac18,3 - You can generate a serial number via Clover Configurator. The creation of a proper SMBIOS is covered in many guides to good extend Look at the graphics section and adjust the injection for Intel to your situation  
      Fixes

      Patches

      Devices

      Graphics

      Kernel and Kext patches
       
      1.3 kexts and friends
      Add the supplied SSDT-UAIC.aml to "patched" - it limits the injected USB Ports to the actual number and ports valid for this board.
       
      Required kexts on "Other":
      FakeSMC.kext IntelGraphicsFixup.kext Lilu.kext When having an Nvidia card: NvidiaGraphicsFixup.kext IntelMausiEthernet.kext in case you're running Ethernet USBInjectAll.kext with the HCI-300-series-injector.kext --> These two should be installed to /L/E after install  
      We are leaving sound out at the moment, this is something for post-install. Please note the absence of Shiki, I don't find it necessary. Video material I tried made use of the iGPU without shiki.
       
      1.4 Check BIOS and install
      You should be ready for install. But before you reboot, please take a look at your BIOS and set it up accordingly (copied from the aforementioned guide and adapted):
      Load Optimized Defaults Disable VT-d setting If your system has Secure Boot Mode, disable it Set OS Type to Windows 8/10 or OtherOS - I have not seen a difference Turn off internal Serial and Parallel port Turn off Network stack for boot Turn off wake-on-lan (for now) Set XHCI Handoff to Enabled Don't enable decode over 4G Depending on your GPU, set priority for boot Set internal GPU to enable Set DMVT pre-alloc to 64MB Set USB legacy to enabled Activate XMP profile 1 f your Ram has it (mine doesn't and I added the timings manually) Set ERP to enable, disable platform power management (I need to do more research if this could be enabled)  
      I've attached my current BIOS config "hack2". You can place that on a fat32 drive (the EFI partition of your install USB drive might be an idea) and see if it loads. It's made for and with the F2 BIOS.
       
      The install itself should be like other MacOS Hackintosh installs with it several reboots and ensuring to select the correct boot device in Clover.
       
      2. Post-install
       
      2.1 Install clover on target
      This is a no-brainer, but install a fresh copy of Clover on your target medium.
       
      During install select again AptioMemoryFix but also additionally
      EmuVariableUefi-64.efi Install RC scripts on target volume because otherwise NVRAM doesn't seem to work
       
      After the install, copy
      config.plist contents of "Other" content of "patched" apfs.efi from drivers64UEFI to your new clover install.
       
      2.1 Edit DSDT for slumber
      This is necessary only once on initial install and every time, you edit or upgrade the BIOS. The DSDT.aml attached to this post might work for your system or give you a file to compare to. Don't expect it to work for you, though.
      I won't go into the details of DSDT extraction and patching. There are better guides (the linked guide is a rip-off of rehabman's guide from a different forum). Please follow such a guide to extract your ACPI data.
       
      Locate and disassemble the DSDT with the newest iasl binary you can put your hands on, then open it with MacIASL in its newest version you can find (Hint: Here is a good source) You can check if the version is new enough if MacIASL doesn't throw error upon compiling a freshly extracted DSDT.aml or DSDT.dst
       
      Add rehabmans repo (as per linked guide) and apply the following patches:
      Rename _DSM to _XDSM Fix _WAK Arg0 v2 USB3 _PRW 0x6D Skylake (instant wake) Find the CNVW device and remove the _PWR function there.
       
      Compile the DSDT and place it in "patched".
       
      2.2 Install kexts to system
      As mentioned in the install section, it's better to follow rehabman's instruction and install USBinjectAll.kext to /L/E:
      sudo cp -R Release/USBInjectAll.kext /Library/Extensions sudo touch /System/Library/Extensions && sudo kextcache -u / 2.3 Enable onboard Audio
      This is where I'm not so happy currently, I'd like it to work without altering AppleHDA. But currently I find no other way.
       
      2.3.1 Install FakePCIID & FakePCIID_Intel_HDMI_Audio
      Rehabman tells us to use a kext installer to install it to /S/L/E. Chose the RELEASE folder
       
      2.3.2 Run CloverALC command
      Ensure your EFI partition is mounted before running this command
      Get the newest version of CloverALC command (audio_cloverALC-xxx.sh) and run it. Our Audio codec is RTL887 and I'm running with layout ID 1
       
      2.4 Optional steps
      If you have a dGPU, now it's the time to install its drivers and adjust the config.plist for it.
      This is out of scope of this guide. Yet, my supplied config.plist is ready to be used with Nvidia Pascal cards and using the Nvidia web driver.
       
      3. ToDo
      Move away from static DSDT patching to SSDT hotpatching --> requires my work Native NVRAM --> requires developer work Audio without AppleHDA patching --> requires developer work  
      4. Thanks to
      @MaLd0nfor helping finding the right way with the DSDT
      @RehabMan, for being a legend and helping me out patching
      @toleda, for audio patches for the 300 series
      /u/corpnewt, for his superb vanilla guide
      @wmchris for his super XPS 9550 guide and introducing me to hot-patching
      all the developers of clover and it's awesomeness
       
      SSDT-UIAC.aml
      config.plist
      DSDT.aml
      hack2
    • By zcmckenna
      I have been having a pretty major issue with my new Hackintosh lately. It has been displaying broken link images in safari (See image 1). It has also had certain areas of artifacting such as the storyboard in Xcode (See image 2). and finally PDFs have been showing up completely blacked out (See image 3). This has been a big issue for me and I was wondering if any of you have had the same problem and have had any luck fixing it. I have already tried display calibration and switching to integrated graphics. Thanks in advance!
      (See attached for config.plist)
      Specs:
      CPU: i5-8600k
      MB: Gigabyte Z370XP SLI
      GPU: ASUS 1070 Dual
      RAM: 16GB Ballistix (8GB x 2)
      HDD: WD Blue 1TB



      config.plist
    • By Mieze
      This project is dedicated to the memory of Mausi, the cat I loved more than anybody else.
       

       
      A few days before Christmas I started my latest project, a new driver for recent Intel onboard LAN controllers. My intention was not to replace hnak's AppleIntelE1000e.kext completely but to deliver best performance and stability on recent hardware. That's why I dropped support for a number of older NICs. Currently the driver supports:
       
      5 Series
      82578LM 82578LC 82578DM 82578DC 6 and 7 Series
      82579LM 82579V 8 and 9 Series
      I217LM I217V I218LM I218V I218LM2 I218V2 I218LM3 100 Series (since V2.1.0d0)
      I219LM I219V 200 Series (since V2.3.0d0)
      I219LM I219V 300 Series (since V2.4.0d0)
      I219LM I219V Key Features of the Driver
      Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). Support for TCP/IPv6 and UDP/IPv6 checksum offload. Makes use of the chip's TCP Segmentation Offload (TSO) feature with IPv4 and IPv6 in order to reduce CPU load while sending large amounts of data (disabled). Fully optimized for Sierra (64bit architecture) but should work with older 64bit versions of macOS too, provided you build from source with the appropriate SDK for the target OS. Support for Energy Efficient Ethernet (EEE). VLAN support is implemented but untested as I have no need for it. The driver is published under GPLv2. Current Status
      The driver has been tested successfully with I217V, I218V and 82579V under 10.9.5 and above. The attached archive includes source code as well as a prebuilt binary (debug version) for Mavericks and Yosemite. Known Issues
      There seem to be problems while using VMware with version 1.x.x of the driver. In case you are affected use version 2.0.0 or newer. FAQ
      Could you add support of for...? Well, you are probably asking me to add support for one of the older NICs like the 82571/2/3/4L or 82583 and the answer will be no as I dropped support for these chips intentionally. They are broken and I lost more than 2 weeks trying to make it work on the 82574L without success. I was asked to add support for I210, I211 and I350 but as these chips have a completely different architecture, which isn't supported by the underlying Linux driver, this is impossible, sorry. Does it work with Snow Leopard or 32 bit kernels? No and I have no plans to make a version for 32 bit kernels or anything older than Lion. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5. Installation
      Goto /S/L/E and delete AppleIntelE1000e.kext. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface. Troubleshooting
      Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me.  Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any AppleIntelE1000e.kext from your system because it could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000.  In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable. Changelog
      Version 2.4.0 (2018-04-14) Added support for 300 series versions of I219LM and I219V. Updated underlying Linux source code. Version 2.3.0 (2017-06-20) Added support for 200 series versions of I219LM and I219V. Version 2.2.0 (2016-09-23) Disabled TSO to work around a hardware bug. Version 2.1.0 (2016-05-24) Added support for I219LM and I219V Version 2.0.0 (2015-04-22) First official release which is identical to 2.0.0d2 (only the version number has been changed). Version 2.0.0d2 (2015-04-04) Changed the tx descriptor write back policy for 82579, I217 and I218 to prevent random tx deadlocks. Version 2.0.0d1 (2015-03-14) Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ Solves the VMware issue. Version 1.0.0d6 (2015-03-04) Reworked TSO6 support to avoid problems with VMware. Wake-on-LAN now working. Version 1.0.0d5 (2015-02-27) Reworked TSO4 support to eliminate the bug of 1.0.0d4. Added some debug code in order to collect information about the VMware related issue. Version 1.0.0d4 (2015-02-25) Set total length field of the IP-header to zero for TSO4 operations. Report EEE activation state in kernel log message when the link has been established. Version 1.0.0d3 (2015-02-11) Reworked media selection and EEE support (EEE is now activated when both link partners support it. It can be disabled selecting the medium manually). Duplex setting for 10/100 MBit connections is now reported correctly. The number of tx descriptors has been reduced from 2048 to 1024. The code has been cleaned up and obsolete files have been removed. Version 1.0.0d2 (2015-01-31) First development release. Getting the Driver
      The source code can be found on GitHub: https://github.com/Mieze/IntelMausiEthernet There is also a prebuilt binary for 10.11 and above in the download section: http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/ Build from Source for 10.8
      Register as a developer on Apple's developer website. A free membership is sufficient. Download a copy of Xcode 5.1.1 and install it on your machine. In the project select 10.8 as the "Base SDK" and the "Deployment Target". Call "Archive" from the menu "Product" and save the built driver. Credits
      Thanks to RehabMan and Yung Raj for running tests and pointing me in the right direction while I was trying to fix TSO. Special thanks to Yung Raj for motivating me when I was about to give up.
×