Hi,

finally I found a solution for the Marvell Yukon 2 88E8040 Fast Ethernet Device.
The key is Leopard 10.5.7 9J22. In this build there's an updated version of the IONetworkingFamily.kext exactly like in Snow Leopard 10A261 , but the Snow Leopard kernel extension DOESN'T work in Leopard.

And yesterday,I installed Leopard 10.5.7 9J22 and tada... my Ethernet port works.

Please report if the 9J22 kext works in older stable releases and if all dependencies are covered.
If not please tell me and I'll add the missing kernel extension(s).

Here's the proof:


Sorry,the screenshot is in German , even though I'm not German,but it's the language I speak the best.

Hope it works. The kernel extension is attached here. Click to view attachment

UPDATE: Here's a new modified kext including 88E8040T support and corrected Info.plist device name Click to view attachment

UPDATE 2:The Marvell Yukon 2 88E8040 is working perfectly (excl. MAC address) in 10.5.7 9J61.
The 88E8040T doesn't work OOTB,but works with using the Info.plist from my AppleYukon2.kext
(the updated one).

For a correct MAC address follow Slice instructions :

MAC address fix - thx to Slice

I'm very happy about any feedback.

Greetings from Czech Republic,

Adam

I can report success on my inspiron 1525 running 10.5.6 i am typing this post from my inspiron whilst connected via ethernet.

thanks adam

E2A done a couple of reboots - still seems to be working fine though it does seem to boot noticeably slower. anyone else's thoughts/experiences would be appreciated.

Well strange...

On my native install of 10.5.7 9J22 it runs perfectly without any slowdown.
What does it show regarding this kext in verbose mode?
Any errors or retries of something?

Adam

Actually, lol i done a few more reboots (shutdown not working correctly) and it seems to have settled down.

maybe it was just my imagination........

Like to hear what anyone else has got to say.

anyway Adam what is this 10.5.7 9J22 that you speak of? a prerelease of the same?

ah after googling i see it's a beta release

Hi ,

at least it works for you, but feedback from some more people would be great.

Adam

unfortunately it didnt work for me on 10.5.6 ...

maybe it was because i had slices beta driver installed , i will investigate that later, hopefully i will get it to work as well, would be great

Edit:
Okay, so i looked through the info.plist and it seems that my device id is not in there , so i will try to edit the plist.

Hi YannickD,

could you post your device ID?
I could edit the plist and upload a modified kernel extension.

EDIT: not sure if it will work for you , as according to Slice the 88E8040 is b8 chip and 88E8040T is b9.
but anyway,try it,who knows?

Adam

Hi Adam,


at first, THANKS A LOT for that finding. Really, I was up to go to the Apple shop and buy the USB Ethernet dongle. However, for me the solution did not work from the scratch.

The release is XxX 10.5.6, 88E8040, and the Device ID is 4354.

To be honest, I did not check the plist, I'm going to that right away.

If it'll not work, I still have some other 10.5.6 and 10.5.5 to test. Sleepless night... Again But at least there's a hope!



Cheers!

A thanks for the effort , i was going to do it myself but if you want to do it , i wont complain



my device id is 4355 ... so i was thinking about editing the 80E804Z entry since its closest (4354 i think).



@danubletta

yours is in the plist and should work normally!

Nice find adamsalac! I was hoping 10.5.7 might have support. Working perfectly here on an XPS M1530 apart from the issue I noted before about the MAC address not being detected.



As you can see it assigns it a generic one. This of course is only a problem if two or more network cards end up on the same network with the same MAC address. It could happen so I'm going to look into a fix.

EDIT: A temporary fix should you encounter problems is to 'spoof' the MAC address by using ifconfig in Terminal

yay , mine is working as well!

i edited the info.plist and inserted my device id so now it shows up and is fully working! I didnt check the generic mac adress thing , i will look at it now! maybe i will post a screenshot later, for now i have uploaded the modified kext, which should only be used if you have a
88E8040T , all other models might or might not work with this!
Use at your own risk!

EDIT: I looked the mac adress up in system profiler and it says: "00:1e:68:6e:d1:08" ... so i think its not generic , right?


Another Edit: heres my screenshot 

No that's not generic. Seems to work with your card. I noticed booting in verbose this message:



Looks like on the 88E8040 it can't read the ROM to get the MAC address. I don't know how to go about fixing that, maybe Slice can take a look.

Ok update, 'acid test' just remotely installed (from another hackintosh) about 3 gig of software so i reckon it's definitely working on an inspiron 1525

Thank you adamsalac for the find!
The driver don't work for me but I will to patch it. Now I have

And no link.
Why Gigabit? It is only Fast Ethernet!
The ethernet address is wrong but my driver (Marvell.kext) has no problem with getting it. I will try to apply my solution to the binary file.
Development must continue!

Dell 1525
Marvell 88E8040 devID=4354
MacOSX 10.5.6

yay, nice
works fine on XPS M1530 @ Leopard 10.5.6

When you look at the supported modes though it dodesn't show gigabit, it's just cosmetic, you could change the device name in the Info.plist if you wish though.

Works great on my XPS m1530! Unfortunately my dsl expires any day now and ill have to cough up another 6months service fee
P.S. thanks a bunch for testing 10.5.7 and finding this solution!

I've uploaded a edited version of AppleYukon2.kext.

Click to view attachment

It includes YannickD's Device ID for the 88E08040T (in this case even the MAC adress is recognized correctly).
I've also changed the device name from Yukon Gigabit 88E804Z Singleport .... to Yukon Fast 88E8040 Singleport...
(just cosmetical edit).
Still working around with all the kext (also with Slice's kernel extensions).
The combination of Marvell.kext and 9J22 AppleYukon2.kext causes a kernel panic.
Will try some more modifying.Come on,we're very near!

Slice: It would great if you could help finding a solution for our MAC adress problem as I appreciate your work and your driver recognizes the MAC adress perfectly as you already mentioned and I know that you're a good developer.

@YannickD:

Can you confirm that my updated kext also works for you. It actually should as I only added the Device ID you told me ,but just to be sure.....

Adam

@adamsalac

i will check later

on compaq mini 700, with PCIID: ab11:5443 aka Yukon-88E8040 got following error:

AppleYukon2 - RomlessInit - getProperty failed
AppleYukon2 - RomlessInit - getProperty failed
AppleYukon2: 00000000,00000000 sk98osx_dnet - AllocIOInterruptHandler - Failed to allocate MSI interrupt

AppleYukon2: RxRingSize 256, TxRingSize 256, RX_MAX_LE 256, TX_MAX_LE 768, ST_MAX_LE 1024

any ideas, why MSI isn't allocated?

My Dell XPS M5130 shows that error on boot. But it seems the network card works fine with the error.

do you have MSI allocation failure too?

Hey guys great work! How do i find out what device id my ethernet is?

good catch guys, working on Samsung NC10 confirmed, didnt check in dept details as MAC address or others, but it is recognized and working fine...

1st do following command
sudo ioreg -lxw 1024 |less
2nd inside less, input /thernet
3rd look after
device id and vendor id nearby

the "AppleYukon2 - RomlessInit - getProperty failed" error occurs because the driver cant read the rom from the card to show the right mac adress. This shouldnt be any problem as long as you dont have 2 cards with this driver in the same network as neonkoala pointed out.

So the error you should search for is "AppleYukon2: 00000000,00000000 sk98osx_dnet - AllocIOInterruptHandler - Failed to allocate MSI interrupt". this is most possibly why your card isn't working.

that's exactly why, I'm asking if anybody know, how to fix MSI interrup allocation failure?

Great Work, working fine here on samsung NC10
only mac address is 11:22:33:44:55 instead of real mac address.

Other than that works fine , thanks very much adamsalac.

Regards

Niteman1969

Working on NC10, confirmed. No modifications necessary, same issue as niteman (mac add).

Thank you adamsalac!

It Works!!!! I love you!!! lol

i installed the kext on my samsung nc10 but in network i can's see anything how is it possible??? my ethernet is marvell yukon 88e8048......someone can help me thanks...

@ole2: Your device ID(5443) isn't even in the plist! I'll edit it and upload a new version.
Are you using any alternative drivers for Ethernet?

AppleYukon2: 00000000,00000000 sk98osx_dnet - AllocIOInterruptHandler - Failed to allocate MSI interrupt

This line seems as you'd using Slice's driver as that one has sk98 linux base (correct me if I'm wrong, I haven't got much experience with Kernel Extension Development).

@palomu: Tell me your Device ID.

Adam

device id is 435A

Well, my theory is wrong as today I saw in verbose mode an error with sk98osx_dnet and I have vanilla drivers.

Adam

@palomu: Here it is. Tell me if it works. Is MAC adress correctly recognized? Anything special when booting in verbose mode?

Download : Click to view attachment


Adam

I installed it but in system prefernces i can't see ethernet....

Go to System Profiler and Software and Extensions.
Is there a AppleYukon2.kext?

Adam

no there isn't

Ok then there's a problem with your device ID...
Is it really 435A?

Adam

it very very strange now in windows it recognize my ethernet card as marvell 88E8040 and id 4354

Very strange. both Device IDs are included in the kext I gave you!

Adam

Here's another kext.Go to /System/Extensions/IONetworkingFamily.kext (show package contents) then Contents/Plugins and remove AppleYukon2.kext. Also remove the (if there's any) AppleYukon2.kext in the /System/Extensions folder
Then install normally my kext with OSx86Tools,Kext Helper or manually into the Extensions folder.
Before booting,in Darwin bootloader press F8 and enter -v
If there's anything Yukon 2 relevant,post it.
Try it. It simply must work. There're other Samsung NC10 and it's working for them.
I hope it will work for you ,too.



Click to view attachment

Adam

no, no, it's in plist, of course, otherwise I'd mention that
it's 11ab 4354, or something, it's always swapped in ioreg and in plist, so maybe I've misplaced digit pairs a bit

i get this error Apple Yukon2 romlessinit get property failed

You can ignore that error usually. Try going to System Preferences > Network and see if it detects a new network device.

i can't find anything.....



i've the same error in verbose mode

Thank you Adamsalac! The driver is working. This is a present to my birthday.
The small problem with Mac-address. I had
Click to view attachment
this address 00:11:22:33:44:55 is not good. What to do?
1. Kextload my beta driver Marvell.kext and look into system log

This is actual Mac address.
2. Open AppleYukon2.kext/Contents/MacOS/AppleYukon2 with HexEdit 2.0 (freeware).
Click to view attachment
At the picture you can see what and where
1AF20: C6 45 E2 00 C6 45 E3 11 C6 45 E4 22 C6 45 E5 33 C6 45 E6 44 C6 45 E7 55
Change these digits to your Mac-address, save and reboot. Now I see
Click to view attachment
I am happy!

Have you found any solutions?

in windows the ethernet card is sometimes 88e8048 and sometimes 88e8040 and both with different id is possible that this is the reason why my ethernet doesn't work?

Hello,

I have exactly the same problem as Palomu.
Ethernet card is Marvell Yukon 88E8048 Device ID 435A.

In System Profiler >> Software >> Extensions, AppleYukon2.kext is not displayed.
When I boot in verbose mode, there is an error: AppleYukon2 - RomlessInit - getProperty failed

I have now tried all different kext-versions Adam has provided but unfortunately same result with all of them.
All ideas to solve this issue are more than welcome.

Thanks and Regards,
Rooster

Thanks for this slice, worked a treat here. Do you reckon there's any way of using your working code to detect the MAC address and patching it in? Would be nice to save just changing the default MAC. If not this seems to be a good enough solution anyway.