This guide is for use with Leopard only! It will work with the following Marvell ethernet cards:
SK-9E21, SK-9E22, SK-9E81, SK-9E82, SK-9E91, SK-9E92, SK-9S21, SK-9S22, SK-9S81, SK-9S82, SK-9S91, SK-9S92, 88E8053, 88E8055, 88E8055-B0, 88E8061, 88E8062 (88E8061 Dualport)

1.) Find your vendor ID and device ID. I don't know what yours is, but it should look something like this:

Vendor 11AB
Device 4351

Write this down, you will need it to continue past step 3.

2.) Open terminal and type the following:



3.) Scroll down and find the ethernet card you are using, for example, if you are using Marvell Yukon 88E8053, it would show up as:

<key>Yukon-88E8053</key>

Below your ethernet card look for IOPCIPrimaryMatch, for Yukon 88E8053 it looks like this:

<key>IOPCIPrimaryMatch</key>
<string>0x436211AB</string>

After the 0x is the 4 digit Device ID, replace it with yours, and the 4 digits after that is the Vendor ID, replace it with yours also. For mine, I replaced 62 with 51 so it looked like:

<key>IOPCIPrimaryMatch</key>
<string>0x435111AB</string>

When finished, overwrite and exit the file.

4.) Type the following command into terminal:



5.) Repair permissions by typing the following:



6.) Reboot using -x -v flags

7.) Reboot again and your ethernet should work



PLEASE POST ANY QUESTIONS, COMMENTS, AND PROBLEMS HERE AND I WILL HELP YOU ALL!

HOw do i find my vendor id?

To find your Vendor ID and Device ID in Windows 2000/XP, you open up device manager, right click on the device, click properties. Goto the details tab and you should see a string of characters like the following:

PCI\VEN_11AB&DEV_4351&SUBSYS_FF001179&REV_10\4&111A1FD8&0&00E0
(VEN_11AB)(DEV_4351)

So the Vendor ID for me is 11AB, and the Device ID is 4351.

what if I have just Mac OS X and not windows? Is their anyway i could do it under Mac? or maybe a live cd of Ubuntu?

You can't do it under Mac as it is right now because it won't even recognize it, thats why you have to type it in. I can provide very limited support for Ubuntu so your best bet would be to go on Ubuntu's IRC channel (if you dont know what server its on, you can probably find it via google), and ask someone with Linux skills about finding your Device ID through Ubuntu Live CD. Your Vendor ID should, by default, be 11AB because it is a Marvell product. I'm sorry I couldn't provide better assistance and I wish you luck with your Marvell product.

Ok thanks. Ill try a Ubuntu Live CD.

From what I understand, the 53 model is covered by the apple yukon kext already, or should be. Does this mean that this piece of the kext is not there, or leopard does not use it?

Yes, Apple uses the "53" model. Also, if you stripped a MacBook down to the minimum you would notice that most of its parts are made by Apple, so really, Apple makes these Marvell cards but redisigns them for their computers; if the Device ID is different, it just means Apple altered the part to make it more compatible with their line of systems. So yes, Leopard uses it, and everything is there, you just have to change it so that the system knows its dealing with an unaltered part. Apple tries their best to modify their hardware as firmware.

Alright, I see now. It's there, but leopard on a pc doesn't know how to use it right basically. Did I get it right?

Yes, even though the drivers are there, Leopard can't connect it with PC because the kext and product were both designed by Apple.

How to find your vendor and device ID/name:

Download the Hirens Boot CD (for example version 9.3), unrar, burn it, boot on it and select the 7th option - System Info Tools. Choose the second one in the list - PCI and AGP info Tool. Press any key to scroll. Everything you need should be written in yellow. Good luck!

Thanks for that!

Can anyone tell me if this trick works for the 88E8050 model card? Thanks

No I can't because I don't have an 88E8050 to test it with. However, I do have word that it does. Try putting your Device ID into the section for the 88E8053, it should work.

Thank you for this great article, but unfortunately it doesn't work or me.
I have an ASUS P5GDC-V Deluxe with a P4 630 processor and I used Kalyway leo 10.5.1.
It took me a while to get it installed. For those interested I used MBR and stayed away vrom the vanilla kernals. GUID didn't work for me. Audio works, but no volume controle, just like in tiger. Sleep doesn't work as in tiger.
The Marvel Yukon 88E8053 on my P5GDC-V has Vendor ID 11AB and Device ID 4362, so it should basically work without making any changes, however it doesn't.
I see the following related messages in the boot log:

For my Vaio SZ-240, Marvel Yukon 88E8053 does not work even after editing the info file inside the AppleYukon2.kext.

All I see under Network is some firewire connection. I don't even know why this firewire connection has mac address.

Did you restart using -x -v?

thanx for the info!!!
I got my Marvell Yukon 88e8036 to work with the above method!!!

however, since my 8036 was not listed in the info.plist...I had to modify the the 8053 to 8036.

I changed all "8053" to "8036"
and my 8036 happens to have the same vendor 11ab and device 4351 as your 8053.
so I changed that also.

now I have fully working ethernet on SONY VAIO FZ240e installed with iATKOS r2 Leopard.

now all I need is sound from the sigmatel 7662 and intel wireless 4965AGN, then my hackintosh will be complete!

thanx again!!!

Hi,

Can someone please answer this? I have the same problem (same hardware, too).

In Tiger I used to load a third party kext (skge.kext), but that does not seem to work anymore. After some fiddling, I got it to show an Ethernet Controller in the Network panel, but it always says "Network cable unplugged". I get the same messages at boot as tiger294. Any ideas, please?

Hi,
Thanks for the guide p3t3rZ, but I have a problem. When I try to restart with -x -v I type "sudo reboot -x -v" into the terminal, but it says "reboot: illegal option -- x".

What am I doing wrong?

Not working. My VEN ID and DEV ID are alredy writed in AppleYoukon2.kext but ethernet not work, and it's not appeared in Networking, but the leds on it's led's. When I using 10.4.8 and not editing AppleYuokon.kext lan not work, not apeare in Networking and lights not led, but if i edit AppleYuokon.kext it's begin work, apeare in Networking and lights led.
Any one had ideas how to make it work?

It seems like some laptop had problems with these LAN adapter, for some reason the kext loaded but the ethernet does not work. The kext probably loaded (and for it to be loaded, the Dev/Ven Id had to be correct) but there is something else preventing the LAN from working. I put the blame on PCI connectors/bridging and .

http://forum.insanelymac.com/index.php?sho...mp;#entry568957

it's work

i have same promble under Kalyway1.5.1, i try all method i can find at forum , BUT it can not work!!!!! please help me!!!

Hi guys

I also got the same problem with my P5GDC-V. But I try by do the modification to Info.Plist inside AppleYukon.kext and it works for me now. I can make my LAN works. What I did are

Change from

<key>Yukon-88E8056</key> to --> <key>Yukon-88E8053</key>
<string>0x436511AB</string> to --> <string>0x436211AB</string>
<string>Yukon Gigabit Adapter 88E8056</string> to --> <string>Yukon Gigabit Adapter 88E8053</string>

and then

rm /System/Library/Extensions.mkext
diskutil repairPermissions /

reboot the system with -x

and then reboot again normally.

Hope that can make you guys system works too.

Thanks!

Unfortunately for me though, when I go into the plist as described to correct the vendor ID and device ID, they are already correct... i.e. "0x43611AB", which for me is right.

I'm dual-booting from two separate hdd's, one XP one OSX-Leo. In device properties in XP: VEN 11AB DEV 4362.

Peter, how do you do this exactly, I can't get it to work.

Thanks

If your device is 436* you need AppleYukon.kext not AppleYukon2.kext. AppleYukon.kext is missing in Leo, but you can dig it out of Tiger, as I did.

To save you from hard work here it is. Just change my 0x436411AB into yours.

Wow, thanks a million. You were right, it works now.

But, *those damn buts!* unfortunately, i'm having issues now with the system hanging, and the funny thing is, I think it has something to do with the ethernet device... For whatever reason I can reproduce the hang everytime by going int Sys. Prefs. > Network > choose Eth0 or Eth1 > Advanced > then click Ethernet, and POOF! System hangs, can't even CMD - OPT - ESC, have to hard reboot...

Do you think I need to remove the AppleYukon2.kext? If so, how's that done exactly? Thanks again for you great help.

-Nuck

For me I use Kalaway version and it already include AppleYukon.kext in the installation. I attach my AppleYukon.kext here. Please try this one, it works perfectly on my system.

Peter

Thanks a bunch, but I'm still having the "Network Lockup" problem, do you think it is because of the previous AppleYukon2.kext still hanging out in there? If so, how do I remove it?


-Nuck

I'm not sure about that. But you can try by edit the file Info.plist in the AppleYukon2.kext to make it not recognize your LAN. You can do that by remove the whole <key> section of "Yukon-88E8053". But don't forget to backup AppleYukon2.kext before you do the modfication.

If you want to know which extensions is loaded, you can use SystemProfiler utility. It's under Software/Extensions section. If you see only "AppleYukon" in the list, it means your system load only AppleYukon.kext extension.

- Pichai

I have a 88E8040 Ethernet. can I use your trick?
If I can, then how to perform it?
Thanks so much

Yes, thanks Pichai, AppleYukon is the only one in the SystemProfiler. I wonder why then the lockups... I'm just going to have to try some other things out. By the way, I'm running an Asus P5W DH Delux board, it does have 2 ethernet ports, is it possible you think that I need to add another "Yukon-888E8053" to the kext?


Thanks,

Nuck

i tryed what you said but my device id is already listed in /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleYukon2.kext/Contents/Info.plist and my network adapter isnt detected, does anyone know how to fix this.
Ive attached the 2 pictures of the info from linux device manager if it helps.

Regards,
uk_rules_ok
Click to view attachment Click to view attachment

anyone any idea, would like to get this working.

Tried all kinds of methods but didn't work for me.

1st try: Did a change using the Yukon.kext as i did with Tiger. After clear Extension.mkext & repair permission, upon reboot, it promted IONetwork.kext error (something to that nature), can't run or load it.

2nd try: Did a change using the Yukon2.kext. Follow all intructions meticulously & nothing happens (incl reboot with -x -v). Notice there are many IOPrimaryMatch down the whole list inside Yukon2. Do i change every single one?

Check Network in Preference & Ethernet didn't show up at all, only Bluetooth & Firewire, no other options. This is becoming a big pain in the butt.


I have a 8055 chip & ID is 4363 & running Kalyway 10.5.1.

Thanks for any tips Greatly appreciated

Weird, I got the network interfaces for the Marvell to show up, when I boot, the lights on the nic come on and everything, I can connect to internet, and... I don't get lockups anymore, well, none that have anything to do with the networking, BUT.

Internet, and file transfers are P A I N fu l l y S l o o o w.

I have exactly the same issue, can't get this damn network to work... I tried renaming the car in Yukon2.kext but the vendorID and deviceID are correct from start. I tried to download the kext available here on the forum and it does not work either.
I have a 965P DS4 motherboard with the controller intregrated... any help would be appreciated..

Hi
Can somebody tell me y my Yukon 88E8053 doesn't work?
i checked the vendor and device id, they were both right, restarted with -x-v
restarted again
it shows Cable Unplugged but it is working fine in win XP, changed with another working cable, same thing
Any advice?
Thanks!

I figure it out myself.
Check the mac address of your card, if is not the right one just add another ethernet connection with the mac coresponding your network card.

Restart and than at the boot menu hit "F8" than type "-x -v".

i have a strange encounter.

when i boot with -x (safe mode) the networking works fine, i get internet connection. But when i boot normally, the network error message appears & no connection at all.

i suspect some drivers conflict. anyone with any troubleshooting tips?

thanks again.

Would anyone with the 88E8050 be willing to post their files? I've tried to manually edit the files several times with no success.

THANKS P3t3rz,

I use SONY VAIO VGN-AR51SU.
And I have the same problem.

At first Ethernet didn't work at all.
I used file AppleYukon.kext.zip withc was posted above by Darth Toplicius

And now Networking works only when I boot in safe mod. (-x)

Any suggestions how that problem can be fixed?

Thank You.

Ok I havent a clue what going on... I have some exprence with a few different versions of linux and it always works out there; however under terminal in mac i get crappy outputs.
For example:



I have also tried going diretly to the file and opening it. Once edited I then realize I can't save it as is.




Does any one have any idea for the screwed up blank result i get.

I have the 8036.. followed the instructions and got it to work

1. changed 8051 i believe to 8036 two spots
2. changed the primary to 435111ab
3. removed extension.mkext
4. restarted the computer when it got to the part where it says root: i typed in -x -v
5. rebooted again

now i have the internet!!!

I tried everything mentioned in this thread and i could not make my 8053 show up the ethernet...
I can't even see in the system profiler the AppleYukon2.kext loaded now.. Although there was no difference when it was there..

Please if there is someone more advanced mac user , help us out with this one.

I am getting desperate here...

Os X Masters pls heeelp!

Ok I got mine prob solved by putting an external PCI lan card - some old 3com. I plugged the cable and it started working without any driver. So for those who are having difficulties with their On Board Lan cards, just buy one cheap PCI card and put all your worries away...

Cheers!