ASRock Z77E-ITX | Core i7-3770K | EVGA GTX 570HD

[Buckeyes1995]

Are you sure it was exactly the same driver as in the 1st post? (you know how these things get switched) I'd love to try the beta 8.5 driver you were using from your /s/l/e just in case.

In the mean time I've ordered a [ASIX AX88179] based USB3 dongle for emergencies such as this. At least there is active support because of macbook air etc. The wifi's not enough for my purposes & I don't have the luxury of using any external cards for this particular system, since the whole idea was to have an (i7-iMac) in a tiny box running <90w which it's been doing, admirably for a year now.

Ok very odd.. just updated to 10.8.5 (using the Combo update, NOT the app store).. and ethernet is working fine.

Attached is the kext I used.. I can't recall changing.. but maybe I did at one point.. give it a shot and let me know.

 

[eontech]

Ok very odd.. just updated to 10.8.5 (using the Combo update, NOT the app store).. and ethernet is working fine.

Attached is the kext I used.. I can't recall changing.. but maybe I did at one point.. give it a shot and let me know.

Cheers Buck, tried the kext but it's behaving as the original kext for me. (ie. 169.254...) but since it's still working for you, my problem is elsewhere. This is what may be different with my sys:

1.90 patched bios
PJALM vanilla-ish Asrock Z77E-ITX dsdt (+HD4000)
Revogirl script's generated ssdt (for my cpu)
iMac 13,2 smbios

I have new log entries complaining about BCM5701Enet::setPowerLevels - failing to get ACPI dev handle from registry. So I'll try substituting back what I can to see what changes.

This is an improvement, since we know at least one config that's working with the old driver.

 

[Buckeyes1995]

Cheers Buck, tried the kext but it's behaving as the original kext for me. (ie. 169.254...) but since it's still working for you, my problem is elsewhere. This is what may be different with my sys:

1.90 patched bios
PJALM vanilla-ish Asrock Z77E-ITX dsdt (+HD4000)
Revogirl script's generated ssdt (for my cpu)
iMac 13,2 smbios

I have new log entries complaining about BCM5701Enet::setPowerLevels - failing to get ACPI dev handle from registry. So I'll try substituting back what I can to see what changes.

This is an improvement, since we know at least one config that's working with the old driver.

Yeah, probably something to do with that.

As I just rebuilt it this morning, I'm not running a DSDT yet (nor ssdt).

Vanilla install with the attached chameleon boot file. I need to "clean" up the build, as I hate using the EFI injection string. .but was having some issues with IGPEnabler.

I'm also on 1.80 Bios still.. will probably update that this afternoon.

 

[Buckeyes1995]

I've updated to 1.90 and built a DSDT. I've attached all my "stuff" for you to look at. I'm not using a SMBIOS at the moment.

Note my DSDT is set up for Discrete Graphics HDMI. I have not installed any other kexts (besides FakeSMC & the ALC898 kext).

 

[eontech]

Yeah, probably something to do with that.

As I just rebuilt it this morning, I'm not running a DSDT yet (nor ssdt).

Vanilla install with the attached chameleon boot file. I need to "clean" up the build, as I hate using the EFI injection string. .but was having some issues with IGPEnabler.

I'm also on 1.80 Bios still.. will probably update that this afternoon.

Man I feel stupid I restored a previous backup that I knew worked to a spare partition and saw the same default 169.254.xx dhcp, meaning it must be outside this system. swapping cables, checking connections and unplugging/rebooting the switch/router resulted in everything working a 100%

The above lan driver is still fine for 10.8.5 I'm also no longer using the EFI injection string. Here's what's I've done:

• Bios 1.90 patched
• PJALM Z77-ITX + HD4000 patch (altered to IntelCapriFB=5 for the ig-platform-id) + ESB2 SATA
• ssdt from Revogirl's script
• iMac 13,2 SMbios
• Chameleon v2.2svn r2263

as an aside: the ig-platform-id that I altered when patching the dsdt corresponds to the values below in both EFI injection strings from before

be00000001000000020000003f0000000100000002010c00d0 41030a0000000001010600031c0101060000007fff04001600 00006200750069006c0074002d0069006e0000000500000001 730000000200000002010c00d041030a000000000101060000 027fff04002c0000004100410050004c002c00690067002d00 70006c006100740066006f0072006d002d0069006400000008 00000005006201140000006800640061002d00670066007800 00000d0000006f6e626f6172642d31

let me know if you wish to try any of the above bits.

Cheers

 

[sdwoods34]

First post here (typing it on my newly built hackintosh) and I just wanted to say thanks for the guide. This was my first hackintosh build and it was a great success! I even have my 7950 running after updating to 10.8.5.

Thanks

 

[Buckeyes1995]

Man I feel stupid I restored a previous backup that I knew worked to a spare partition and saw the same default 169.254.xx dhcp, meaning it must be outside this system. swapping cables, checking connections and unplugging/rebooting the switch/router resulted in everything working a 100%

The above lan driver is still fine for 10.8.5 I'm also no longer using the EFI injection string. Here's what's I've done:

• Bios 1.90 patched
• PJALM Z77-ITX + HD4000 patch (altered to IntelCapriFB=5 for the ig-platform-id) + ESB2 SATA
• ssdt from Revogirl's script
• iMac 13,2 SMbios
• Chameleon v2.2svn r2263

as an aside: the ig-platform-id that I altered when patching the dsdt corresponds to the values below in both EFI injection strings from before

be00000001000000020000003f0000000100000002010c00d0 41030a0000000001010600031c0101060000007fff04001600 00006200750069006c0074002d0069006e0000000500000001 730000000200000002010c00d041030a000000000101060000 027fff04002c0000004100410050004c002c00690067002d00 70006c006100740066006f0072006d002d0069006400000008 00000005006201140000006800640061002d00670066007800 00000d0000006f6e626f6172642d31

let me know if you wish to try any of the above bits. Now onto Mavericks

Cheers

haha.. awesome.. I can't count the number of times I've felt stupid building this

I'd love to get away from the EFI string and would love your SSDT.

 

[eontech]

haha.. awesome.. I can't count the number of times I've felt stupid building this

I'd love to get away from the EFI string and would love your SSDT.

NP! Sorry for the delay, in the interest of cleaning up I wanted to do a full compare of IONetworkingFamily.kext(s) My original from the thread a year ago, The one in the 1st post's packages & the last one you sent yesterday ARE 100% text & binary identical file for file.

below find the dsdt.dsl source + my ssdt_pr.aml (although this was generated for a i7-3770s) I include the app that installs Revogirls script locally from this link. after install if you issue

~/ssdtPRGen.[sh/command] i7-3770K

that should generate a stock ssdt for your cpu. Other frequency options are possible. also my smBios + Org.Cham.plist altered for your Big A$S monitor No EFI injection.

 

[Buckeyes1995]

NP! Sorry for the delay, in the interest of cleaning up I wanted to do a full compare of IONetworkingFamily.kext(s) My original from the thread a year ago, The one in the 1st post's packages & the last one you sent yesterday ARE 100% text & binary identical file for file.

below find the dsdt.dsl source + my ssdt_pr.aml (although this was generated for a i7-3770s) I include the app that installs Revogirls script locally from this link. after install if you issue

~/ssdtPRGen.[sh/command] i7-3770K

that should generate a stock ssdt for your cpu. Other frequency options are possible. also my smBios + Org.Cham.plist altered for your Big A$S monitor No EFI injection.

Thanks.. compared our DSDTs.. pretty similar.. how old is yours?

Tried to put in the HD4000 injection and correct the device ID.. system won't boot.. wonder if it's because I have the GFX0 stuff in there for my Nvidia?

To be continued...

 

[eontech]

Thanks.. compared our DSDTs.. pretty similar.. how old is yours? Anyways, I see where you did the HD4000 injection.. why did you alter the ID again? Is the one in PJALMs library not valid for our board? Looks like you changed 0x62 to 0x66.

dsdt was gen'd 4 days ago, actually it's 0x66 to 0x62. tbh I think it makes little difference, since it now boots just fine with the old dsdt too! I guess it's because before I remembered to turn of vt-d the only times I managed to boot was with IntelCapriFB=5 (new Chameleon feature) which matches my cpu dev-id as well as the old EFI string. I'm limited to HD4000 and it seems pretty happy so..

One thing about the ssdtGen script it prompts to download/install (iasl) in /usr/local/bin for compiling the ssdt.dsl This is mentioned in the link, but it did perturb me slightly. I guess the whole thing can be setup to run locally as I usually do in a ~/.bin folder. depending on how much of a ctrl-freak you are!

Let me know if you manage to ditch that EFI injection