I tried to get my brother's Nforce 4 PC up and going with OSx yesterday and ran into an issue not only with forcedeth, but with other drivers (Azalia Audio, etc) as well.

I kept getting something to the effect of:

IONetworkingFamily version 1.0.5 used in driver does not match the loaded version, could not load kext.

When looking at the verbose mode on boot, I got the same error about IOPCIFamily (or whatever the PCI driver is, etc..)

I loaded up his system using Uphuck's v1.3 universal.

Do I have to revert to an older ionetworkingfamily/iopcifamily/etc version? If so, what version ? (10.4.5, 10.4.6, 10.4.7) ??

Any help would be greatly appreciated.

Thanks in advance!

ECS C19-A SLI
Nforce4 Intel SLI XE chipset

Uses Marvell 88E1115 Gigabit LAN

I installed colonel's forcedeth-nockd.kext WITHOUT modifying.

When I first installed, log shows massive amounts of posts.
Ethernet is recognized by the OS but could not get an IP or connect to router.

This is what fixed it for me:

I powered off....
unplugged power from computer...
unplugged ethernet cable...
took a piss (approximately two minutes)...
plugged POWER ONLY in...
booted OS X...
plugged in ethernet cable... (still no signs of life)...
followed install steps from post 1, except changed commands for colonel's forcedeth-nockd.kext...
Internet is a GO.

hope this helps.

Hi, this is my first post. And as I see I am not the only one with the nforce4 MCP61 (device ID 03EF) network driver problem. I will tell what I discovered so far and the way I solved this to get the network card work like a charm. First of all the version I used of the OS is 10.4.10. Well, first of all is of course download the file with the driver from Linux, windows becausse It is needed to edit the .plist file and the MacOSX itself consider read only that file (even as root) so It is much easier to use a windows or a linux. Also If you use a Windows you better will need an editor with support for unix files (like freeware notepad++). Next is open the info.plist file inside "forcedeth\build\Release\forcedeth-nockd.kext\Contents" directory and go to the longest line of the file where the cards IDs are (0x003710DE, etc) under the "IOPCIPrimaryMatch" key section, and change one of them to the ID of MCP61 (03EF) for example the last one changing only the second 2 digits of it (0x037310DE) this way it will be 0x03EF10DE. Next is to copy it to anywhere you can then read from MacOSX (usb pendrive, partition, cd, etc) and copy it to the desktop (easiest place) and run the proper commands from the first post but using the forcedeth-nockd.kext of course. It will detect the card and telling it is not supported but it will continue to load and it will work. And the last thing is to go to system preferences and the network configuration and create a new location in case you use static IPs. One thing I did and I am not sure if it's mandatory is change the advanced configuration section of the card where you change manually the network speed and so on (i use the manual system). Try that if doesn't work on automatic mode.

I hope this helps all the people with same card as me with no luck using the forcedeth driver.

VERY IMPORTANT NOTE: Remember to use ONLY the forcedeth-nockd.kext version becausse is the only one working with this network card, all the others detect it but it doesn't work.

Working here!!! I'm typing from Safari.
-OSX 10.4.9
-mobo: ASROCK K8NF6G-VSTA
-PHY RTL8201CL (MCP61). Id's: 0x10de:0x03ef / SubId's: 0x1849:0x03ef

I've used forcedeth-nockd.kext. Raw forcedeth.kext doesn't work. Also, when i try to load forcedeth-nock.kext, the console throws this message:
Can't add Kernel extension forcedeth-nock.kext (not a bundle) (run kextload on this kext with -t for diagnostic output)
With -t I've got the same error message.

Thank you Planetbeing for your efforts.
Regards.

I had that error once, after i had installed and uninstalled the .kext or modified it or something, i just redownloaded it and installed it without error.

I discover some weird behaviour since I got working the mcp61 lan, sometimes it says it is connected but really it doesn't work, but those times if i reboot (or poweroff) the computer and boot from a linux distribution (sysrescd for example) and configure the LAN and use it (just a ping to google) and then reboot directly to the MACOSX ALWAYS works. So people with similar problem about the 03ef LAN take care of this.

Success report!
Hi, this is my first post.
Athlon64 3500 2.2Ghz
nForce 430 (ID0269)
mobo: GA-K8N51GMF-9
Tubgirl 10.4.10 AMD SSE3 Test1

worked with forcedeth-nockd.kext posted in the middle of this thread (the one with 6100 in the name). After initial install ethernet card was identified and active but I couldn't connect. Only after unplugging the power cable for 30 secs and powering back, internet connected. Yay!

A big thanks to all who made this possible!

Anyone wanna help me with getting my internet to work in Tiger...?
Im totaly new at mac, just installd the jas 10.4.8 amd thingy and everything seems to be working, but not the internet/network.
My Mobo is a Abit K9 with Nvidia gigabyte built-in network card.
Ive been reading for lite 10 hours on this site about how to get it to work but i gess im totally stupid .

My computer.
Amd processor x2 64 3600+
Abit k9s
2 gig ram
Geforce 7600
soundblaster superdisaster

I gess the problem with my network is my tiger os, when its booting up it cant "find" PHY when it comes to loading the Forcedeth. I tried writing sudo -s, then, loadkext -v .....forcedeth.kext but it said i didnt have permission-??
Please help me get my tiger connected to the internet
Im really starting to get at my First and maybe only mac.....

well, you should see first the ID of your card and if it is not inside the .plist you should add it.

hey folks, i added my MCP67 (i think its nForce5) card to the info.plist and it kinda worked... it read the mac address out of the card backwards and it didn't get a real connection but it was able to find the device and get something right =)

i got my nforce4 lan up.. but it can't get an IP from my DSL Modem (my isp is on pure dhcp).. i always get an invalid IP (169.254.x.x).. any workarounds? thanks in advance..

Have you guys tried using the forcedeth drivers? They're specifically for nForce LAN. The drivers work great for me and I'm getting speeds that I never even achieved on windows. Especially for upload.

Same thing happens on my nForce lan... same IP address prefix too o.O another thing I saw was my mac address was totally backwards...

edit: actually it looks more like it rearranged the mac address to sort large -> small....

windows mac: 00-1B-24-90-7A-E6
forcedeth mac: e6:90:7a:24:1b:00

this just seems wrong o.O

Hello all!This is my first post and I`m happy to report that with a little modification I got forcedeth to work on my onboard ethernet.I was having a problem that my MAC address was appearing inverted (I think other people had this problem too). So I made a small modification to forcedeth to un-invert the MAC address.So, if you have a nNvidia MCP 61 card (device id 03EF) AND are getting inverted MAC address (type "ifconfig" in the terminal to check, then compare in windows - the command in windows is "ipconfig /all" or something like that).I am uploading only forcedeth.kext, because it`s the only thing I changed.I`m typing this on Safari :-))Motherboard: ASRock 939NF6GAthlon 64 X2 4200+ (oc@2.85)GeForce 8600GT (the next step in tweaking my hackintosh)Good luck you all and above all, thanks to the guys who made this possible PlanetBeing, and Alandor who inspired me to tweak the files...Hi.Try my forcedeth.kext below. Hope it helps, it certainly did for me D.

heh, this thread is all about forcedeth unfortunately it doesn't cooperate with my nForce MCP67 card (0x054C, anyone? eh?)

ObsidianX: Have you tried my forcedeth.kext? I understand from your previous post that planetbeing's forcedeth loaded successfully on your system, but the MAC address was backwards. It just so happens that in my computer the MAC address was also backwards so I modified planetbeing's driver and recompiled it making the MAC address correct and it finally worked on my computer.

You'll have to add your device ID to the plist.info file inside the 'forcedeth.kext/Contents' folder.

Please, give it a try and let me know the result.

D.

Well holy {censored}! How did I miss your earlier post?! It works beautifully! Thank you!

I'm glad it worked. Could you post your system specs (esp. motherboard model) for future reference?

yeah im gunna open a new thread with all my working hardware+driver combos once i get the sound and (hopefully) video working

but for the sake of this thread:

HP Pavilion dv6605us (dv6500us)
MCP67 hardware
Ethernet - dev 0x054C vend 0x10de (obviously )

I tried the new driver and my MAC is still backwards. Any ideas?

This is an Asus M2N-E with
PCI 0x0373

heh, have you tried the old driver?

8ender: If you had your MAC backwards with the old driver, it must be correct with my driver because I hardcoded the inversion in the MAC address.

So, if you had the old driver installed, don't forget to 'kextunload' it and ideally delete any files from the old kext (don't forget the extensions folder).

Finally, I forgot to mention that all instructions in the original post apply to my driver.

Good luck.

D.

Which files do I put my PCI ID into inside the kext? I notice that my ID is in the noCK and noCK debug kexts but not the two others. I edited them to add my PCI ID. I'll try reinstalling the driver tonight.

Thanks for this, great timing
Its works with my Asrock AliveNF6G-DVI board (mcp61p - lan 03ef).
I have to do cold start (power off / on) to see the network.

Before this I changed my mac in hardver to reverse order with a dos util
http://www.asrock.com/support/Download/K7V...K7VM3%20MAC.asp
Now I can use without this trick with original mac

Hi, for those who, like me, got an mcp61 eth (0x03EF/0x10DE) and can't get it to work, i've patched the original forcedeth source code to correctly grep mac address from the card. Also, i've changed some code in order to get the eth working without cold/soft boot, re-boot in linux, windows etc. I'm sure this WORK on an ASRock 939NF6G-VSTA motherboard.
In the attachment there is the source code and in the Build/Debug/ you should find the forcedeth-nockd.kext ready for use (well, you should change ownership and permission, but that is common routine )

Note: code is a real mess . Clean-up & update to the latest version is needed.

Regards, Domenico.

Well guys I have read all the 3d but I couldn't find a solution. This is the log of the operation. My hardware is in the signature. Thanks to all. Hope u can help me.

kernel[0]: forcedeth: Initializing.

kernel[0]: forcedeth: Probing.

kernel[0]: forcedeth: Starting.

kernel[0]: forcedeth: PCI system 0x10DE:0x0057, subsystem 0x1043:0x812A opened.

kernel[0]: forcedeth: Mapped from 0xFE02A000 of length 4096.

kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x3b68b000, tx at 0x3b68b400, wired at 0x12f46000.

kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:1B:FC:36:84:E3.

kernel[0]: forcedeth: Could not find a valid PHY.

kernel[0]: forcedeth: Stopping


Why the hell couldn't it find a valid PHY??? It's driving me crazy

@MeDevil: thanks for the heads up. I wish you did that 2 days ago Anyway, could you point me to what methods are responsible for the boot thing? I never had that problem, but since I am using this driver and had also produced my own "flavor" of it (to solve the backwards MAC problem), I'd like to know. Also, to avoid confusion, maybe we should only have one version of this driver (I don't mind removing mine from the thread)...

The source code is attached in my previous post.
Following, a list of change i've made to the original source code (the one in the first page of the post):


(file: forcedeth.cpp, line: 998)


(file: forcedeth.cpp, line: 1046)


(file: forcedeth.cpp, line: 1086)


(file: forcedeth.h, line: 187)

Also, i should notice you that i never got any kextd to work... (but i think that this is related to the powerstate...).
I'll be very happy if you take these mods and merge them into a future release of the forcedeth driver.
I just had to get my nic working asap (beacuse i didn't had a secondary pci eth) so i can concentrate on other projects

A final note: i used my device id to enable the nic, but other nforce nic uses the same powerstate method. A further look into the linux forcedeth driver can help you to understand what i mean

Best regards, Domenico.

I hope someone can help me here, here's what happens when I try to use ANY version of the drivers found on this thread (I've spent 2 hours reading over everything here... )

I have a single ethernet port built into my logic board, nforce4 chipset, forcedeth works awesome in linux of course, as well as in windows... I'm running tubgirl 10.4.10 on amd, with sse3.

Here's what I get:

sudo kextload -v forcedeth.kext:


tail -f /var/log/system.log:


system profiler:


I've never gotten the driver to locate a valid PHY.

Thanks for any advice, pointers in advance!!

@MeDevil: I'm happy to help maintain the driver in my free time.

@testeroni: I'll take a look at this problem in the weekend, but I can't give you much hope right now as I am not very familiar with programming drivers...

@testeroni: I've done some searching and found this: http://forum.applesana.com/47/5613/fallo-c...red-nforce.html

There's a driver for download there; If you download it, please post it here for me to learn how to fix this;

Thanks.

I just want to say thanks to both MeDevil and monseiur D for all their work on this We nForce folk would be in a very lonely osx86 without you!

It works, even in Leopard... thanks!!! Same mobo than yours!!!

@tomnic: Please, let us know what hardware you're using and what version of Leopard.

Thanks.

D.

HI all,

Trying to put the networkcard to work, but with no luck. I have a nForce 410/430 series id:0x296. I have tried all foredeth version and the best i got resembles this:

Nov 2 03:02:27 kernel[0]: forcedeth: Initializing.
Nov 2 03:02:27 kernel[0]: forcedeth: Probing.
Nov 2 03:02:27 kernel[0]: forcedeth: WARNING - your nVidia device 0x10DE:0x0269 is not known to work, but it could be supported in the future. Please contact the coder. Continuing anyway...
Nov 2 03:02:27 kernel[0]: forcedeth: Starting.
Nov 2 03:02:27 kernel[0]: forcedeth: PCI system 0x10DE:0x0269, subsystem 0x1734:0x10D3 opened.
Nov 2 03:02:27 kernel[0]: forcedeth: Mapped from 0xC0007000 of length 4096.
Nov 2 03:02:27 kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x23b28000, tx at 0x23b28400, wired at 0xbf70000.
Nov 2 03:02:27 kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:14:0B:02:2A:C0.
Nov 2 03:02:27 kernel[0]: forcedeth: Found PHY 0x5040:0x0003 at address 1.
Nov 2 03:02:38 kernel[0]: forcedeth: PHY reset failed.
Nov 2 03:02:38 kernel[0]: forcedeth: Failed to initialize PHY.
Nov 2 03:02:38 kernel[0]: forcedeth: Stopping

I've searched all over this thread for the "PHY reset failed.", but again, with no luck. It seems I'm the only one with this error.

Any ideas, anyone?

Thanks

I can't make forcedeth work. I tried the one in the first post, colonel's forcedeth, but none of them worked.

Log:

Nov 2 07:45:17 victhor-fosters-computer kernel[0]: forcedeth: Initializing.
Nov 2 07:45:17 victhor-fosters-computer kernel[0]: forcedeth: Probing.
Nov 2 07:45:17 victhor-fosters-computer kernel[0]: forcedeth: WARNING - your nVidia device 0x10DE:0x0269 is not known to work, but it could be supported in the future. Please contact the coder. Continuing anyway...
Nov 2 07:45:17 victhor-fosters-computer kernel[0]: forcedeth: Starting.
Nov 2 07:45:17 victhor-fosters-computer kernel[0]: forcedeth: PCI system 0x10DE:0x0269, subsystem 0x1043:0x816A opened.
Nov 2 07:45:17 victhor-fosters-computer kernel[0]: forcedeth: Mapped from 0xFE02D000 of length 4096.
Nov 2 07:45:17 victhor-fosters-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x27c46000, tx at 0x27c46400, wired at 0x2b9e4000.
Nov 2 07:45:17 victhor-fosters-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:1A:92:C1:BD:EB.
Nov 2 07:45:17 victhor-fosters-computer kernel[0]: forcedeth: Found PHY 0x5040:0x0003 at address 1.
Nov 2 07:45:17 victhor-fosters-computer kernel[0]: com_triton_forcedeth: Ethernet address 00:1a:92:c1:bd:eb
Nov 2 07:45:17 victhor-fosters-computer kernel[0]: forcedeth: Enabling... 1 2 3 4 5 6 7
Nov 2 07:45:17 victhor-fosters-computer kernel[0]: forcedeth: Starting transmit/receive engines
Nov 2 07:45:17 victhor-fosters-computer kernel[0]: forcedeth: Network link down.


MAC is displayed correctly, dev/ven ids are: 0269/10de.


I have a Asus M2NPV-VM board, Nforce 430(why i bought that mobo... )

If there is a way of enabling QE/CI/GL on the built-in Geforce 6150 please PM me.
EDIT: forcedeth6100 also won't work. Looks like i will have to use this Realtek card for infinity...

is there someone?
I do remember why i bought that mobo:Because it was cheapo full of features.

works fine under leopard with an msi k8n neo4 mobo here. thx guys

i had the problem that i couldn't d/l (big) files (would result into crash/freeze), but normally browsing websites worked. i fixed it by disabling the "lan option rom" in bios.

Hi there! Same problem as yours with Device ID 0269 (Asus M2NPV-VM).
My network card seem to work with the forcedeth-nockd.kext (it shows in the network section in the system preferences panel), but it phisically hangs, and then I must turn off the computer to have it back.
No success with the normal forcedeth.kext.
Any suggestion to make it work other than buying a cheap realtek 81xx???

Thanks.
Madn3ss

My config: Uphuck 1.4a + AMD Update to 1.4.10
M2NPV-VM Mobo
AMD Athlon 64 X2 6000+ (for the moment it shows only one cpu)
Azalia audio working (only out)
Macvida 1.8.1 working (no QE/IC)
Internal LAN NOT working
I'm going to install tubegirl 1.4.10 very soon...

Guys,

I don't know what is going on with your onboard LAN, but there's a very simple thing to try given the following conditions:

- The driver loads AND you can see the ethernet interface in network properties.
- The MAC address shows correctly (compare with windows or linux).

If the two conditions above are met and still your network doesn't work, then turn off your computer and disconnect the power cable for 30 seconds.

I don't know why, but it does work for me. After a fresh install of MAC OS, I installed the forcedeth driver that I had been using for a while but the LAN didn't work. Then I tried this and it worked.

Hope it helps.

D.

@monsieur D: thanx very much for your modified driver (and of course credit me, something I think I don't deserve but thanx very much). I realize that the MAC changed but really doesn't look more about it so I didn´t realize it was reversed, I always reset the cable modem. So thanx again.



Oh, about the applesana forums, becausse spanish is my native language if anyone have any question or problem related to any thread that don't understand becausse of the language I am glad to help.

having problems to make it work on leopard

my mobo is a A8N-E

i used the kexts from the first post

my logs :



on the tail terminal window i saw this :



what the hell am i doing wrong? im going crazy :S

i just need this to get Leo Fully working...

thanks in advance

@Roike: It seems to be loading correctly. What do you get if you type 'ifconfig' in the terminal?

Did you configure your IP address (choose DHCP with manual address)?

Did you reset the LAN (turn off the computer and disconnect power cable for 30 seconds)?

Since I don't have Leopard here, I can't say much more right now. Please, post the output of 'ifconfig'.

D.

Osx10410_AMDVM_SSE3

Motherboard: Gigabyte n-Force405 GA-M61SME-S2


I`m so tired, please help me. Always I have the same...

kextload: kext /System/Library/Extensions/AppleThermal.kext is not valid
kextload: extension forcedeth.kext appears to be valid
kextload: loading extension forcedeth.kext
kextload: forcedeth.kext loaded successfully
kextload: loading personalities named:
kextload: nForce 4 LAN
kextload: sending 1 personality to the kernel
kextload: matching started for forcedeth.kext

What the hell is wrong?

1. What driver are you using? In this thread there are a few different versions.
2. The messages show that the driver is loading, but you have to send the relevant lines in the system log (see original post and the command 'tail -f /var/......'), you only sent the ouput of the terminal.

Then maybe we can help.

I've got nforce 650i and when I try the driver, I get nothing in the log showing it working. All I get is the kextload stuff, and nothing in the tail log.

flibblesan: I'm in the same boat. P5N32-E SLI PLUS, so it's a 680i, but same sort of thing. I see both the interfaces and mac adresses in the Network properties, but nothing works.

I did notice that when kextloading, it did throw a message saying this specific deviceID (can't remember what mine is offhand), is known not to work, so prehaps there needs to be a bit of modification done for us with newer boards? It seems like it's *almost* working, so perhaps I'll take a look at it later....I'm by no means a programmer or anything, so don't expect much.

Just tried that PHY fix file from that Spanish forum, and the driver loads if I use the forcedeth.kext

It finds the correct MAC address, and finds the PHY but it thinks the cable is unplugged. I've tried unplugging it and plugging it back in, but it doesn't make a difference.

What is the forcedeth-nock file for?

hi there.
i don't know if you already treated the problem, but i can't figure out how to write in the search.

i'm using you method and it works, i've got some boot errors, but maybe i'll write them later.
2 things:

- network speed isn't that much (much more fast on vista)
- i've got a lot of messages on the console.

i've red another topic written by a guy with my exact barebone (asus). so i decided to follow him.
he stated that using your method hadn't work, so he was using the forcedeth-nockd.kext file, instead of the one you posted (well, this is also in your package). adding my (and his) vendor and device ID to the info.plist file, the lan card works.
the problem, according to that guy, is that in the console we get a lot of garbage messages, here's an example (system.log)



this is nothig to worry about, but my system.log file would assume godzilla dimension !
then, i think this has something to do with the network speed.

any ideas ?

Right click on the kext that works, select "show package content" then into the folder Contents, open the file "Info.plist" with the texteditor. find the line "<key>Debug</key>", below there should be the tag "<true/>", rename that to "<false/>".
Then reload the kext (by kextload or by rebooting) and you're done.