Jump to content

Mac App Store access with NullEthernet.kext

mac app store NullEthernet Ethernet

  • Please log in to reply
123 replies to this topic

#21
RehabMan

RehabMan

    InsanelyMacaholic

  • Coders
  • 2,597 posts
  • Gender:Male
  • Location:Bellingham, WA
  • Interests:skiing, software, classic cars

@RehabMan,
 
Would you kindly review my report regarding App Store verification problem in the following link:
http://www.insanelym...verified/page-4
 
Do you think your Null Ethernet kext has good chance may work in my situation?


If your issue is that you have no working built-in Ethernet (only USB WiFi), this solution should work.

#22
Phil511

Phil511

    InsanelyMac Protégé

  • Members
  • PipPip
  • 98 posts
  • Gender:Male
  • Location:USA

Thanks for your reply. 

In the same computer, ML 10.8.5 worked with the airport card without a hitch. In Mavericks, weird stuff happened. I tried importing my ML Networking Interface into Mavericks with proper terminal commands from eep. It installed correctly but it shuts off Wi-Fi function. In Mavericks, I can only have either Wi-Fi or Marvell Yukon Lan. If Both kexts are loaded, only LAN works and Wi-Fi showed up in network setting and I could not turn it on through network setting. Going through my DSDT.aml, I could not locate the Airpot Atheros 9380 at all. Yet, it clearly displayed in the IORegistry. I was hoping that if it showed up in DSDT.aml, maybe some patch might work. WOuld changing SMBios to MacPro 3.1 make a difference? 

 

If I try your NullEthernet Kext with SSDT, if it does not work, can I just uninstall the kext and delete the SSDT and back to square one? I am desperate to try anything as long as it does not give me serious KP that I cannot fix it myself. 



#23
RehabMan

RehabMan

    InsanelyMacaholic

  • Coders
  • 2,597 posts
  • Gender:Male
  • Location:Bellingham, WA
  • Interests:skiing, software, classic cars

Thanks for your reply. 
In the same computer, ML 10.8.5 worked with the airport card without a hitch. In Mavericks, weird stuff happened. I tried importing my ML Networking Interface into Mavericks with proper terminal commands from eep.


ML and Mavericks have the same support for WiFi cards. I don't know what you mean by "importing my ML Networking Interface into Mavericks," but it doesn't sound a like a good idea.

It installed correctly but it shuts off Wi-Fi function. In Mavericks, I can only have either Wi-Fi or Marvell Yukon Lan. If Both kexts are loaded, only LAN works and Wi-Fi showed up in network setting and I could not turn it on through network setting.


Key is not messing with the system kexts IO80211Family.kext or IONetworkingFamily.kext as it is unnecessary to replace/patch these kexts and doing so just leads to problems.

Going through my DSDT.aml, I could not locate the Airpot Atheros 9380 at all. Yet, it clearly displayed in the IORegistry. I was hoping that if it showed up in DSDT.aml, maybe some patch might work.


Use the information in the ioreg to find it in your DSDT (eg. node in ioreg corresponds to node in DSDT).

WOuld changing SMBios to MacPro 3.1 make a difference?


I don't think smbios matters for your case.

If I try your NullEthernet Kext with SSDT, if it does not work, can I just uninstall the kext and delete the SSDT and back to square one? I am desperate to try anything as long as it does not give me serious KP that I cannot fix it myself.


Yes. And BTW, there is no such thing as a "serious KP" that cannot be fixed provided you know what you changed to cause it.

#24
Phil511

Phil511

    InsanelyMac Protégé

  • Members
  • PipPip
  • 98 posts
  • Gender:Male
  • Location:USA

@ RehabMan,

 

You just hit the nail's head right on. I truly believed in my case, the Atheros Airport card registered under IEEE80211 and Marvell Yukon Kext is installed through modified IONetworking family kext. Somehow it messed up there. 

Is there a way to fix this? I will try your Null Ethernet with SSDT and report back to you. I am sure there won't be any serious KP that cannot be fix as I am not doing something crazy here. 

 

Thanks and have a nice weekend! Congrats to Seahawks winning the Super Bowl.



#25
RehabMan

RehabMan

    InsanelyMacaholic

  • Coders
  • 2,597 posts
  • Gender:Male
  • Location:Bellingham, WA
  • Interests:skiing, software, classic cars

@ RehabMan,
 
You just hit the nail's head right on. I truly believed in my case, the Atheros Airport card registered under IEEE80211 and Marvell Yukon Kext is installed through modified IONetworking family kext. Somehow it messed up there. 
Is there a way to fix this?


No need to install a replacement IONetworkingFamily.kext to install support for a network driver. You can fix it by restoring to vanilla (you made a backup, right?).

Thanks and have a nice weekend! Congrats to Seahawks winning the Super Bowl.


Go Hawks!

#26
Phil511

Phil511

    InsanelyMac Protégé

  • Members
  • PipPip
  • 98 posts
  • Gender:Male
  • Location:USA

No need to install a replacement IONetworkingFamily.kext to install support for a network driver. You can fix it by restoring to vanilla (you made a backup, right?).


Go Hawks!

I saved the Vanilla IONetworking family kext and has since re-installed (replacing the modified IONetworkingFamily kext.). I  have no Marvell Yukon Lan kext No Ethernet. That is why I cannot sign into App Store. Any suggestion how to fix it. Mavericks read the Airport Card correctly and registered en0 but I cannot sign into APp Store. 



#27
RehabMan

RehabMan

    InsanelyMacaholic

  • Coders
  • 2,597 posts
  • Gender:Male
  • Location:Bellingham, WA
  • Interests:skiing, software, classic cars

I saved the Vanilla IONetworking family kext and has since re-installed (replacing the modified IONetworkingFamily kext.). I  have no Marvell Yukon Lan kext No Ethernet. That is why I cannot sign into App Store. Any suggestion how to fix it. Mavericks read the Airport Card correctly and registered en0 but I cannot sign into APp Store.


One way would be install a kext for your Marvel Yukon, so you have working Ethernet and access to the Mac App Store. When you install the kext, make sure you do not install the entire IONetworkingFamily.kext, just install the single PlugIn that is likely patched (just guessing this is a patched kext situation). Take a look at the structure of IONetworkingFamily.kext (eg. Contents/PlugIns). What you don't want to do is install some random version of IONetworkingFamily.kext as doing so will likely break your WiFi.

The other way, would be to use NullEthernet. You could use the injector method of installation (to have it attach to your actual Ethernet PCI device), as described in the readme: https://github.com/R...X-Null-Ethernet

#28
Phil511

Phil511

    InsanelyMac Protégé

  • Members
  • PipPip
  • 98 posts
  • Gender:Male
  • Location:USA

One way would be install a kext for your Marvel Yukon, so you have working Ethernet and access to the Mac App Store. When you install the kext, make sure you do not install the entire IONetworkingFamily.kext, just install the single PlugIn that is likely patched (just guessing this is a patched kext situation). Take a look at the structure of IONetworkingFamily.kext (eg. Contents/PlugIns). What you don't want to do is install some random version of IONetworkingFamily.kext as doing so will likely break your WiFi.

The other way, would be to use NullEthernet. You could use the injector method of installation (to have it attach to your actual Ethernet PCI device), as described in the readme: https://github.com/R...X-Null-Ethernet

Thank you very much. By your analysis, it is clear to me that Marvell Yukon LAN kext was installed via patched IONetworkingFamily.kext that messed up the the genuine airport wifi card. I had tried before just Marvell Yukon kext and it does not work.  Therefore, the only possible way is to try your NullEthernet with injector method of installation hopefully it will attach to actual PCIE Ethernet. I will report back to you. I will write back if I have any question regarding the injector method.

 

Thank you very much for your help.



#29
Gringo Vermelho

Gringo Vermelho

    The Jan Bird fix

  • Supervisors
  • 6,224 posts
  • Gender:Male
  • Location:Brazil

What model is your Marvell ethernet? I had the 88E8056 for years, it always worked perfectly with a Legacy (plist only) Kext. I never needed to modify anything.



#30
RehabMan

RehabMan

    InsanelyMacaholic

  • Coders
  • 2,597 posts
  • Gender:Male
  • Location:Bellingham, WA
  • Interests:skiing, software, classic cars

What model is your Marvell ethernet? I had the 88E8056 for years, it always worked perfectly with a Legacy (plist only) Kext. I never needed to modify anything.


Yes, I should have mentioned this... If the only "patch" to a kext is editing the plist to add an extra device-id, then you should use an injector kext as Gringo mentions (Apple calls them "codeless kexts"), instead of modifying the actual kext. If there is a binary patch involved, then that is a different situation. But doing the "right thing" depends on having an understanding as to what is required.

#31
Phil511

Phil511

    InsanelyMac Protégé

  • Members
  • PipPip
  • 98 posts
  • Gender:Male
  • Location:USA

What model is your Marvell ethernet? I had the 88E8056 for years, it always worked perfectly with a Legacy (plist only) Kext. I never needed to modify anything.

My Marvell Ethernet is 88E8056. Where can i get Marvell 88E8056 Ethernet Legacy (plist) only kext? 

I got mine from the following:

 

http://www.insanelym...e8056-108-1085/

 

Marvell 88E8056 kext from above  worked perfectly. But it turned off my Atheros (9380) wi-fi card. I can see Wifi int the network set up but it's  shut-off permanently. I click turn wifi on nothing happened. Network name is grayed out. In my ML 10.8.5, Ethernet and Atheros wifi card coexists nicely and worked perfectly. 



#32
Phil511

Phil511

    InsanelyMac Protégé

  • Members
  • PipPip
  • 98 posts
  • Gender:Male
  • Location:USA

@Gringo Vermelho & @RehabMan,

 

Thanks for your guys help by pointing to Legacy Yukon kext.. I used Legacy yukon kext by Styrian from the following:

 

http://www.insanelym...ks-i-need-help/

 

Everything is fixed and no more App Store Problem. Legacy (Info plist or code-less kext) worked as it does not messed up IONetworkingFamily.kext. 



#33
kingvidiot

kingvidiot

    InsanelyMac Protégé

  • Members
  • Pip
  • 1 posts

Thank you RehabMan!  Awesome kext work!  So grateful for this.  I was pulling my hair out trying to get access to the App Store before I stumbled upon your kext.

 

Here is a bit of background on what I did and something I noticed along the way that may help the next poor hackintosh n00b like myself.  I started with a pre-built Dell XPS 8000 (yes I know, I was asking for it).  I started with a retail SL disk.  I ran into more problems than I care to enumerate here so I'll just tell ya about what pertains to your kext.  I finally ended up with a booting 10.6.8 w/App store but could not log in.  The XPS 8000 has a builtin ethernet that is not supported and I have yet to find someone that has gotten it working.  I was able to use internet and update to 10.6.8 via the builtin WIFI that did work OOB (go figure that a WIFI works but not ethernet).

 

The problem then was I could not log in to the App store because the only network device OS X registered was the wifi and it assigned it to en0 but everything I tried could not force it to built in.  So I bought a USB ethernet dongle that is supported in OS X but still, neither this or the wifi would register as builtin regardless of what I did (pulled out WIFI and just had the USB dongle... plenty of plist updates and boot parameters tests...).

 

I then found your kext when I felt I was out of options (aside from buying a new PCI ethernet NIC).  I followed your instructions (DSDT method) but when I boot it said it failed to load your kext because it could not find the IONetworkingFamily dependency.  What I found was that I had version 1.1.0 of IONetworkingFamily installed with OS X 10.6.8 and your NullEthernet.kext required version 1.5.0 (or greater?).  So as a last resort I went into the Info.plist file for NullEthernet.kext and modified the version number for com.apple.iokit.IONetworkingFamily from 1.5.0 to 1.1.0.  I then was able to boot, remove NetworkInterfaces.plist and preferences.plist (/Library/Preferences/SystemConfiguration/) to ensure this NullEthernet was en0... because it was eth1 on first boot due to USB ethernet dongle already set to en0, reboot again and App Store Login goodness!!!!!

 

Im now running Mavericks thanks to you!  I do still have to use this kext to access the App Store in Mavericks but it works just fine.



#34
RehabMan

RehabMan

    InsanelyMacaholic

  • Coders
  • 2,597 posts
  • Gender:Male
  • Location:Bellingham, WA
  • Interests:skiing, software, classic cars

Thank you RehabMan!  Awesome kext work!  So grateful for this.  I was pulling my hair out trying to get access to the App Store before I stumbled upon your kext.
 
Here is a bit of background on what I did and something I noticed along the way that may help the next poor hackintosh n00b like myself.  I started with a pre-built Dell XPS 8000 (yes I know, I was asking for it).  I started with a retail SL disk.  I ran into more problems than I care to enumerate here so I'll just tell ya about what pertains to your kext.  I finally ended up with a booting 10.6.8 w/App store but could not log in.  The XPS 8000 has a builtin ethernet that is not supported and I have yet to find someone that has gotten it working.  I was able to use internet and update to 10.6.8 via the builtin WIFI that did work OOB (go figure that a WIFI works but not ethernet).
 
The problem then was I could not log in to the App store because the only network device OS X registered was the wifi and it assigned it to en0 but everything I tried could not force it to built in.  So I bought a USB ethernet dongle that is supported in OS X but still, neither this or the wifi would register as builtin regardless of what I did (pulled out WIFI and just had the USB dongle... plenty of plist updates and boot parameters tests...).
 
I then found your kext when I felt I was out of options (aside from buying a new PCI ethernet NIC).  I followed your instructions (DSDT method) but when I boot it said it failed to load your kext because it could not find the IONetworkingFamily dependency.  What I found was that I had version 1.1.0 of IONetworkingFamily installed with OS X 10.6.8 and your NullEthernet.kext required version 1.5.0 (or greater?).  So as a last resort I went into the Info.plist file for NullEthernet.kext and modified the version number for com.apple.iokit.IONetworkingFamily from 1.5.0 to 1.1.0.  I then was able to boot, remove NetworkInterfaces.plist and preferences.plist (/Library/Preferences/SystemConfiguration/)

 to ensure this NullEthernet was en0... because it was eth1 on first boot due to USB ethernet dongle already set to en0, reboot again and App Store Login goodness!!!!!
 
Im now running Mavericks thanks to you!  I do still have to use this kext to access the App Store in Mavericks but it works just fine.

Weird. I based this off my fork of Mieze's RealtekRTL8111.kext sources... (just stripped everything away). And my build of RealtekRTL8111.kext, AFAIK, works on SL 10.6.8... although I haven't tested it in a while (maybe it doesn't anymore?). I'll do some more testing and see if changing the dependency to 1.1.0 is harmless on Lion/ML/Mavs.

#35
yeris

yeris

    InsanelyMac Protégé

  • Members
  • Pip
  • 4 posts
  • Gender:Male
  • Location:The Netherlands

Hello all :)

 

First I would like to thank RehabMan for making my laptop work very good on a not to be named forum, but as I am new to all this, I don't understand all the technical details of how to do this.

 

Would it maybe be possible if someone give me and others a more simplified explanation of how to do this?

 

Thank you in advance.



#36
Onixs

Onixs

    Since 2007

  • Members
  • PipPipPipPipPipPipPip
  • 821 posts
  • Gender:Male

Weird. I based this off my fork of Mieze's RealtekRTL8111.kext sources... (just stripped everything away). And my build of RealtekRTL8111.kext, AFAIK, works on SL 10.6.8... although I haven't tested it in a while (maybe it doesn't anymore?). I'll do some more testing and see if changing the dependency to 1.1.0 is harmless on Lion/ML/Mavs.

still works :)

lowering down dependency will do no harm.



#37
ninhvanthang

ninhvanthang

    InsanelyMac Protégé

  • Members
  • Pip
  • 1 posts

Someone please help,

i tried install nullethernet and i can login to appstore, but when login to icloud it said error "Accout limit reached"

 

I'm using USB WIFI to connect to internet

 

Attached File  iMac_and_sheet_45B1FB0B-69E0-40AB-B580-67356574E8BF.jpg   88.03KB   4 downloads

Attached File  iMac_and_Network.jpg   62.36KB   4 downloads


still works :)

lowering down dependency will do no harm.

 

is your icloud work, and how to ?



#38
juanchif

juanchif

    InsanelyMac Protégé

  • Members
  • Pip
  • 1 posts

Hi, I installed NullEthernet kext and I can confirm that is working perfectly, It solved my App Store problem

 

To fully resolve the App Store problem I also needed to remove any interfaces and then adding them up so that the Ethernet is bound to the interface en0

 

Thank you



#39
bjadams

bjadams

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts

@yeris I installed mine through the Slytherin tool as it does it automatically, even though it unfortunately did not work



#40
bjadams

bjadams

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts

i had to install it manually step by step!

worked perfectly!







Also tagged with one or more of these keywords: mac app store, NullEthernet, Ethernet


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2016 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy