works with a8n-e motherboard.
i love you.
Full Version: Driver for nForce4 LAN
I have searched high and low for an answer to the issues of my nForce4 LAN issues and thought maybe I had found the solution - but I haven't gotten net access yet (am having to boot back into x64 XP to write this).Motherboard is Gigabyte GA-M55SLI-S4. Using latest Jas 10.4.8 with ppf update.
I have followed to the letter the forcedeth instructions - including the options for forcedeth-nockd and forcedeth-nock and still haven't resolved my LAN issues.
According to Windows - my device id is 0057 and vendor id is 10DE - which seems to appear to be on track with what this kext resolves - but still no go.
Here is the log file info for having initialized each kext:
Results - forcedeth.kext (latest release)
Jan 11 06:12:21 my-computer kernel[0]: MMAC: family specific matching fails
Jan 11 06:12:21 my-computer kernel[0]: forcedeth: Initializing.
Jan 11 06:12:21 my-computer kernel[0]: forcedeth: Probing.
Jan 11 06:12:21 my-computer kernel[0]: forcedeth: Starting.
Jan 11 06:12:21 my-computer kernel[0]: forcedeth: PCI system 0x10DE:0x0057, subsystem 0x1458:0xE000 opened.
Jan 11 06:12:21 my-computer kernel[0]: forcedeth: Mapped from 0xF5001000 of length 4096.
Jan 11 06:12:21 my-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x57268000, tx at 0x57268400, wired at 0x31d2e000.
Jan 11 06:12:21 my-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:16:E6:5B:3E:56.
Jan 11 06:12:21 my-computer kernel[0]: forcedeth: Found PHY 0x5040:0x0003 at address 1.
Jan 11 06:12:21 my-computer kernel[0]: com_triton_forcedeth: Ethernet address 00:16:e6:5b:3e:56
Jan 11 06:12:21 my-computer kernel[0]: forcedeth: Enabling... 1 2 3 4 5 6 7
Jan 11 06:12:21 my-computer kernel[0]: forcedeth: Starting transmit/receive engines
Jan 11 06:12:21 my-computer kernel[0]: forcedeth: Network link down.
Results - forcedeth-nock.kext (modified version)
Jan 11 06:09:19 my-computer kernel[0]: MMAC: family specific matching fails
Jan 11 06:09:19 my-computer kernel[0]: forcedeth: Initializing.
Jan 11 06:09:19 my-computer kernel[0]: forcedeth: Probing.
Jan 11 06:09:19 my-computer kernel[0]: forcedeth: Starting.
Jan 11 06:09:19 my-computer kernel[0]: forcedeth: PCI system 0x10DE:0x0057, subsystem 0x1458:0xE000 opened.
Jan 11 06:09:19 my-computer kernel[0]: forcedeth: Mapped from 0xF5001000 of length 4096.
Jan 11 06:09:19 my-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x57268000, tx at 0x57268400, wired at 0x23499000.
Jan 11 06:09:19 my-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:16:E6:5B:3E:56.
Jan 11 06:09:19 my-computer kernel[0]: forcedeth: Found PHY 0x5040:0x0003 at address 1.
Jan 11 06:09:20 my-computer kernel[0]: com_triton_forcedeth: Ethernet address 00:16:e6:5b:3e:56
Jan 11 06:09:20 my-computer kernel[0]: forcedeth: Enabling... 1 2 3 4 5 6 7
Jan 11 06:09:20 my-computer kernel[0]: forcedeth: Starting transmit/receive engines
Jan 11 06:09:20 my-computer kernel[0]: forcedeth: Network link down.
I do not ever acquire an IP address - I have tried dhcp as well as manual ip address per what I have entered in windows - still no luck.
What am I missing - this is literally the only thing not working - I really need net access but if this isn't resolvable, I guess I scrap the work and go back to windoz...
Peace...
Well it seems this is an inactive thread. I have given up on this and will wait to see what 10.4.9 brings to the table.
IF anyone can find a solution, PM me on this. Here is my last attempt with the forcedeth.kext:
Log File:
Jan 14 07:23:04 my-computer sudo: freediver : TTY=ttyp2 ; PWD=/Users/freediver/Desktop/forcedeth/build/Release ; USER=root ; COMMAND=/usr/
sbin/chown -R root:wheel forcedeth.kext
Jan 14 07:23:11 my-computer sudo: freediver : TTY=ttyp2 ; PWD=/Users/freediver/Desktop/forcedeth/build/Release ; USER=root ; COMMAND=/bin/
chmod -R 755 forcedeth.kext
Jan 14 07:23:19 my-computer sudo: freediver : TTY=ttyp2 ; PWD=/Users/freediver/Desktop/forcedeth/build/Release ; USER=root ; COMMAND=/sbin/
kextload -v forcedeth.kext
Jan 14 07:23:21 my-computer kernel[0]: MMAC: family specific matching fails
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Initializing.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Probing.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Starting.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: PCI system 0x10DE:0x0057, subsystem 0x1458:0xE000 opened.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Mapped from 0xF5001000 of length 4096.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x5df7a000, tx at 0x5df7a400, wired at 0x21405000.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:16:E6:5B:3E:56.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Found PHY 0x5040:0x0003 at address 1.
Jan 14 07:23:21 my-computer kernel[0]: com_triton_forcedeth: Ethernet address 00:16:e6:5b:3e:56
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Enabling... 1 2 3 4 5 6 7
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Starting transmit/receive engines
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Network link down.
Jan 14 07:25:01 my-computer mDNSResponder: mDNSPlatformRawTime: last_mach_absolute_time 3ECF23530000004B
Jan 14 07:25:01 my-computer mDNSResponder: mDNSPlatformRawTime: this_mach_absolute_time 3EC643700000004B
ifconfig -a Results:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
fw0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 2030
lladdr 00:16:e6:00:00:b5:d8:07
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:16:e6:5b:3e:56
media: autoselect (<unknown type>) status: inactive
supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 100baseTX <full-duplex> 100baseTX <half-duplex> 1000baseT
Kextload results:
\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
Ping to 192.168.0.1 Results:
PING 192.168.0.1 (192.168.0.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
Maybe something will pop up - now to get some work done.
IF anyone can find a solution, PM me on this. Here is my last attempt with the forcedeth.kext:
Log File:
Jan 14 07:23:04 my-computer sudo: freediver : TTY=ttyp2 ; PWD=/Users/freediver/Desktop/forcedeth/build/Release ; USER=root ; COMMAND=/usr/
sbin/chown -R root:wheel forcedeth.kext
Jan 14 07:23:11 my-computer sudo: freediver : TTY=ttyp2 ; PWD=/Users/freediver/Desktop/forcedeth/build/Release ; USER=root ; COMMAND=/bin/
chmod -R 755 forcedeth.kext
Jan 14 07:23:19 my-computer sudo: freediver : TTY=ttyp2 ; PWD=/Users/freediver/Desktop/forcedeth/build/Release ; USER=root ; COMMAND=/sbin/
kextload -v forcedeth.kext
Jan 14 07:23:21 my-computer kernel[0]: MMAC: family specific matching fails
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Initializing.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Probing.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Starting.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: PCI system 0x10DE:0x0057, subsystem 0x1458:0xE000 opened.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Mapped from 0xF5001000 of length 4096.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x5df7a000, tx at 0x5df7a400, wired at 0x21405000.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:16:E6:5B:3E:56.
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Found PHY 0x5040:0x0003 at address 1.
Jan 14 07:23:21 my-computer kernel[0]: com_triton_forcedeth: Ethernet address 00:16:e6:5b:3e:56
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Enabling... 1 2 3 4 5 6 7
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Starting transmit/receive engines
Jan 14 07:23:21 my-computer kernel[0]: forcedeth: Network link down.
Jan 14 07:25:01 my-computer mDNSResponder: mDNSPlatformRawTime: last_mach_absolute_time 3ECF23530000004B
Jan 14 07:25:01 my-computer mDNSResponder: mDNSPlatformRawTime: this_mach_absolute_time 3EC643700000004B
ifconfig -a Results:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
fw0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 2030
lladdr 00:16:e6:00:00:b5:d8:07
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:16:e6:5b:3e:56
media: autoselect (<unknown type>) status: inactive
supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 100baseTX <full-duplex> 100baseTX <half-duplex> 1000baseT
Kextload results:
\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
Ping to 192.168.0.1 Results:
PING 192.168.0.1 (192.168.0.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
Maybe something will pop up - now to get some work done.
After about 4 hours of trying the different kext packages I finally got it working on my ASUS A8N-VM. I used the kext package that I will attach, with the -nockd kext.
Thank you for all your hardwork!Click to view attachment
Thank you for all your hardwork!Click to view attachment
Well, still no go - I have tried every variation on gettin gmy nForce4 Lan to work - here is the very latest from the startup log:
The light goes off once the forcedeth kext loads so something is happening, but it appears it hangs at a certain point in initialization - I have also tried dhcp and manual settings - System preferences says the cable is unplugged.
Any other suggestions I might try or is this a waste of my time and I just need to get a generic realtek LAN card for my only free PCI slot???
QUOTE
Jan 18 06:30:56 localhost kernel[0]: forcedeth: Initializing.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: Probing.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: Starting.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: PCI system 0x10DE:0x0057, subsystem 0x1458:0xE000 opened.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: Mapped from 0xF5001000 of length 4096.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x66fbf000, tx at 0x66fbf400, wired at 0xe1f000.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:16:E6:5B:3E:56.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: Found PHY 0x5040:0x0003 at address 1.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: Probing.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: Starting.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: PCI system 0x10DE:0x0057, subsystem 0x1458:0xE000 opened.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: Mapped from 0xF5001000 of length 4096.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x66fbf000, tx at 0x66fbf400, wired at 0xe1f000.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:16:E6:5B:3E:56.
Jan 18 06:30:56 localhost kernel[0]: forcedeth: Found PHY 0x5040:0x0003 at address 1.
The light goes off once the forcedeth kext loads so something is happening, but it appears it hangs at a certain point in initialization - I have also tried dhcp and manual settings - System preferences says the cable is unplugged.
Any other suggestions I might try or is this a waste of my time and I just need to get a generic realtek LAN card for my only free PCI slot???
I'm using the TubGirl 10.4.8. I am installing it and receiving the following message when I boot with -v:
forcedeth: Enabling... 1 2 3 4 5 6 7
forcedeth: Starting transmit/receive engines
forcedeth: Network link down.
Booting stops at this point. I've also tried using the JaS release with the same results.
I have an ABIT KN9 with the nForce4 ultra chipset.
Does anyone have any suggestions?
Thanks!
forcedeth: Enabling... 1 2 3 4 5 6 7
forcedeth: Starting transmit/receive engines
forcedeth: Network link down.
Booting stops at this point. I've also tried using the JaS release with the same results.
I have an ABIT KN9 with the nForce4 ultra chipset.
Does anyone have any suggestions?
Thanks!
Hey guys, I'm just dropping in to to tell everyone to stop PM'ing for help on this. School has devoured my life, and I really don't have the time and interest to work very much on stuff like this anymore. And I can't really do much besides, because I don't have access to the many variations on this LAN chipset, only what's on my own computer. I tried to follow the specifications in the Linux version of the driver as much as possible, so I don't know what's wrong.
And to those folks who PM'ed me for download locations or installation instructions. I think other people on the forums could help you more than I can on those issues.
One note. nockd and nock should have the same functionality. The -d part just indicates it outputs debug messages -- and a lot of them. So if you're using nockd and it works for you, you should try to use nock, and it should work just as well, and may save you some CPU cycles.
Also, people who've had recent issues with the whole "Network link down" thing at the end. That indicates initialization has completed successfully, but for some reason, it doesn't think the LAN cable is plugged in. Or the driver hasn't received notification or something like that. I think some of the other versions of the same driver does more CPU-intensive checks for that, so you might want to try nock, or any other version I included. That's the only thing I can think of without going back and refamiliarizing myself with the code and specs.
Thank you all for the support.
And to those folks who PM'ed me for download locations or installation instructions. I think other people on the forums could help you more than I can on those issues.
One note. nockd and nock should have the same functionality. The -d part just indicates it outputs debug messages -- and a lot of them. So if you're using nockd and it works for you, you should try to use nock, and it should work just as well, and may save you some CPU cycles.
Also, people who've had recent issues with the whole "Network link down" thing at the end. That indicates initialization has completed successfully, but for some reason, it doesn't think the LAN cable is plugged in. Or the driver hasn't received notification or something like that. I think some of the other versions of the same driver does more CPU-intensive checks for that, so you might want to try nock, or any other version I included. That's the only thing I can think of without going back and refamiliarizing myself with the code and specs.
Thank you all for the support.
Thanks planet for even taking this on when you did - bummer you're out of the loop now - there are alot of us nForce4 LAN users and having this one thing keeping us from enjoying the ride of OSX on OTS hardware is disappointing - but you gotta take care of the real stuff first
Peace...
Peace...
hey, not to bug anyone, but I just thought I'd ask if anything is happening? I know the original author has no time, but maybe someone else knows. Also to ask, what are the chances that nforce5 will work with a functional nforce4 driver? Are they too different? or could the one driver cover them all like in the linux kernel?
I also have problems with my forcedeth LAN on my M2N4-SLI, I think it's nForce 4 Ultra or nForce 430. The onboard ethernet is detected but cannot connect. While booting it says 'found no valid PHY' or something like this. More people have this problem, look here:
http://forum.insanelymac.com/index.php?sho...mp;hl=forcedeth
On my other nForce 3 and nForce 4 systems everything is working fine.
GreetinX from the Other Side, Naquaada.
http://forum.insanelymac.com/index.php?sho...mp;hl=forcedeth
On my other nForce 3 and nForce 4 systems everything is working fine.
GreetinX from the Other Side, Naquaada.
This may be a bit numb, and or redundant, but I'm sitting over here on Camp Arifjan in Kuwait and we don't have a whole lot to do at the moment. I've been trying to get my Shuttle SN85G4V2 with an AMD A64 3000+ (Yes, I know old and slow -- but we're Army, what do you expect) running in OSX.
For those unaware of this particular system it is NForce3 based.
After quite a bit of swearing, cussing, and threats of a 3 round burst from my rifle I've managed to get this far;
forcedeth: Initializing.
forcedeth: Probing.
forcedeth: WARNING - your nVidia device 0x10DE:0x00D6 is not known to work, but it could be supported in the future. Please contact the coder
forcedeth: Starting.
forcedeth: PCI system 0x10DE:0x00D6, subsystem 0x1297:0xA550 opened.
forcedeth: Allocated 2072 bytes of contiguous memory for DMA: rx at 0x29714000, tx at 0x29714400, wired at 0x13824000.
forcedeth: Found nForce4 LAN with MAC: 00:30:18:b4:85:b8.
forcedeth: Found PHY 0x0000:0x0028 at address 1.
com_triton_forcedeth: Ethernet address 00:30:1b:b4:05:b8
forcedeth: Enabling... 1 2 3 4 5 6 7
forcedeth: Starting transmit/receive engines
forcedeth: Network link down.
forcedeth: Link speed now 100Mbps, code 0x10064
forcedeth: Received irq with events 0x30. Probably TX fail.
forcedeth: Received irq with events 0xx. Probably TX fail.
...
And it continues to throw random event numbers and failing. Not sure what the hell this means, but it's closer than I've gotten yet. In order to get this far I pulled the 0x00D610DE out of windows device manager and threw it in the Info.plist file. Apparently I'm lame though and it doesn't work. If anyone has any suggestions I'll buy you a beer when I get out of this hellhole. Until then,
Thanks,
Dan
For those unaware of this particular system it is NForce3 based.
After quite a bit of swearing, cussing, and threats of a 3 round burst from my rifle I've managed to get this far;
forcedeth: Initializing.
forcedeth: Probing.
forcedeth: WARNING - your nVidia device 0x10DE:0x00D6 is not known to work, but it could be supported in the future. Please contact the coder
forcedeth: Starting.
forcedeth: PCI system 0x10DE:0x00D6, subsystem 0x1297:0xA550 opened.
forcedeth: Allocated 2072 bytes of contiguous memory for DMA: rx at 0x29714000, tx at 0x29714400, wired at 0x13824000.
forcedeth: Found nForce4 LAN with MAC: 00:30:18:b4:85:b8.
forcedeth: Found PHY 0x0000:0x0028 at address 1.
com_triton_forcedeth: Ethernet address 00:30:1b:b4:05:b8
forcedeth: Enabling... 1 2 3 4 5 6 7
forcedeth: Starting transmit/receive engines
forcedeth: Network link down.
forcedeth: Link speed now 100Mbps, code 0x10064
forcedeth: Received irq with events 0x30. Probably TX fail.
forcedeth: Received irq with events 0xx. Probably TX fail.
...
And it continues to throw random event numbers and failing. Not sure what the hell this means, but it's closer than I've gotten yet. In order to get this far I pulled the 0x00D610DE out of windows device manager and threw it in the Info.plist file. Apparently I'm lame though and it doesn't work. If anyone has any suggestions I'll buy you a beer when I get out of this hellhole. Until then,
Thanks,
Dan
Thanks so much!!
my foxconn winfast mainboard c/ chipsep nforce4 running!
good work.
my foxconn winfast mainboard c/ chipsep nforce4 running!
good work.
You're lucky Dan, I only get to the "forcedeth: Network link down." part and then it just sits there...
I've given up.. I've done every option available for this - even gone so far as added an Intel Pro10/100+ NIC card and that even fails with a "Isn't a valid mach-o" message on boot. Too bad - I had one hell of a screaming OSX box - now it's back to the slug known as XP x64
I've given up.. I've done every option available for this - even gone so far as added an Intel Pro10/100+ NIC card and that even fails with a "Isn't a valid mach-o" message on boot. Too bad - I had one hell of a screaming OSX box - now it's back to the slug known as XP x64
I don't know how this happened, but I'm thinking of writing a new version of this thing based on a newer version of this thing based off the source of a newer version of the Linux driver that I based the original off of. It might solve all of our problems. It might solve nothing and generate more problems. But maybe there will be a working solution in a matter of weeks or a month or two.
That tx fail message no one ever gets. That's very odd. You tried nockd? Ordinarily I'd say something is the matter with your hardware, but it still works in Windows, right? Well. I dunno. Maybe I was misconfiguring the network card or something and it was complaining. It might be fixed in a newer version.
By the way, I was working with someone on the "network link down" thing. I think he got me to by accusing me of being mean or something. =P I thought of something that I didn't think of before related to that. If you type ifconfig, you can see the list of media that the ethernet adapter supports. 100BASET, etc. If that list is what it should be (check your brochure =P. I think most of these cards have all the way up to gigabit) instead of just empty, then phyInit() was successful, and the problem can be isolated to updateLinkSpeed.
I may come up with a debug version that will help determining what exactly is going on in updateLinkSpeed --- that is if anyone still cares?
That tx fail message no one ever gets. That's very odd. You tried nockd? Ordinarily I'd say something is the matter with your hardware, but it still works in Windows, right? Well. I dunno. Maybe I was misconfiguring the network card or something and it was complaining. It might be fixed in a newer version.
By the way, I was working with someone on the "network link down" thing. I think he got me to by accusing me of being mean or something. =P I thought of something that I didn't think of before related to that. If you type ifconfig, you can see the list of media that the ethernet adapter supports. 100BASET, etc. If that list is what it should be (check your brochure =P. I think most of these cards have all the way up to gigabit) instead of just empty, then phyInit() was successful, and the problem can be isolated to updateLinkSpeed.
I may come up with a debug version that will help determining what exactly is going on in updateLinkSpeed --- that is if anyone still cares?
You know I still do 
I can't offer much coding support, but I'll be more than happy to test them for you, and I can do minor edits because I still have xcodes.
I can't offer much coding support, but I'll be more than happy to test them for you, and I can do minor edits because I still have xcodes.
I tried all 4 .kexts.. None works on 680i, which is nforce 6 kernel. I wish there was a way to make that one work 
.. sighs
.. sighs
since forcedeth 0.57.. 2.6.17 kernel onwards forcedeth.c has few new lines of code..
It seems that from MCP51 onwards, the LAN controller driver for windows is such that it leaves the LAn card in such a state that it is inaccessible wen rebooting into Linux. So these lines of code reset the LAN card (similar to wat unplugging from the wall does), so that it can be accessed and gets an IP from DHCP/Manually.. planetbeing pls port some new version of forcedeth.. will be of gr8 help to nf 410/430 , 5xx and 6xx users..
ill be only too glad to help in the coding..
It seems that from MCP51 onwards, the LAN controller driver for windows is such that it leaves the LAn card in such a state that it is inaccessible wen rebooting into Linux. So these lines of code reset the LAN card (similar to wat unplugging from the wall does), so that it can be accessed and gets an IP from DHCP/Manually.. planetbeing pls port some new version of forcedeth.. will be of gr8 help to nf 410/430 , 5xx and 6xx users..
ill be only too glad to help in the coding..
Hey you guys.
That's my first reply on that forum.
I can see this driver is a solution for nForce 3/4 onboard eths, but can I ask if it works on nForce 5? Is it working there or is there any solution for that one. My motherboard is ASUS M2N-E.
Thanks a lot
That's my first reply on that forum
.I can see this driver is a solution for nForce 3/4 onboard eths, but can I ask if it works on nForce 5? Is it working there or is there any solution for that one. My motherboard is ASUS M2N-E.
Thanks a lot
Just wanted to let you all know my onboard ethernet on nvidia mcp51 board works by using the forcedeth-nockd driver. I had to add device id to the Info.plist: 0x026910de. With the normal forcedeth kext it would see that it was connected, but dhcp wouldn't work and setting ip manual didn't seem to solve anything either. With forcedeth-nockd everything works fine though! Thanks for all the work you guys did on this driver!
Greetings,
Michael
Greetings,
Michael
QUOTE
Just wanted to let you all know my onboard ethernet on nvidia mcp51 board works by using the forcedeth-nockd driver. I had to add device id to the Info.plist: 0x026910de. With the normal forcedeth kext it would see that it was connected, but dhcp wouldn't work and setting ip manual didn't seem to solve anything either. With forcedeth-nockd everything works fine though! Thanks for all the work you guys did on this driver!
Just tried this, and it does indeed work! Now I can finally use my onboard lan. Thanks!
That's great!!!You help me a lot~ 
Hi doenst work for me 
I have a 939NF4G-SATA2 board with a realtek LAN on a Nforce 410 Southbridge
NVNET_DEV0269
PCI\VEN_10DE&DEV_0269&SUBSYS_02691849&REV_A1
PCI\VEN_10DE&DEV_0269&SUBSYS_02691849
PCI\VEN_10DE&DEV_0269&CC_068000
PCI\VEN_10DE&DEV_0269&CC_0680
Iknow when i installed the forcedeth.kext and put the id : 0x026910DE the card was reconized but i couldnt get a mac adres and could connect to my router when i restarted later my system (OSX) 10.4.8 (kernal 8.8.1) said there was a problem with the forcedeth.kext and i was recomended to uninstall.
Do you know a solution is this a realtek lan?? My specs of my board says so
- Realtek PHY RTL8201CL
- Speed: 10/100 Ethernet
- Supports Wake-On-LAN
link to the site : http://www.asrock.com/mb/overview.asp?Mode...G-SATA2&s=n
Thanx :-)
I have a 939NF4G-SATA2 board with a realtek LAN on a Nforce 410 Southbridge
NVNET_DEV0269
PCI\VEN_10DE&DEV_0269&SUBSYS_02691849&REV_A1
PCI\VEN_10DE&DEV_0269&SUBSYS_02691849
PCI\VEN_10DE&DEV_0269&CC_068000
PCI\VEN_10DE&DEV_0269&CC_0680
Iknow when i installed the forcedeth.kext and put the id : 0x026910DE the card was reconized but i couldnt get a mac adres and could connect to my router when i restarted later my system (OSX) 10.4.8 (kernal 8.8.1) said there was a problem with the forcedeth.kext and i was recomended to uninstall.
Do you know a solution is this a realtek lan?? My specs of my board says so
- Realtek PHY RTL8201CL
- Speed: 10/100 Ethernet
- Supports Wake-On-LAN
link to the site : http://www.asrock.com/mb/overview.asp?Mode...G-SATA2&s=n
Thanx :-)
Hi Planetbeing. Thanks for your attempts. I have an Abit KN9 Ultra (which is listed on the osx86 site as working with this driver?). My problem is that once the physical address is found, the link never activates. I'm not sure why. Anyway, here is what I am getting at best:
That was the most promising bit I got. I never was able to send packets to the router. Not sure why that is.
CODE
Feb 14 15:15:09 adams-computer sudo: Adam : TTY=ttyp2; PWD=/Users/Adam/Desktop/forcedeth/build/Release; USER=root; COMMAND=/sbin/kextload forcedeth-nockd.kext
Feb 14 15:15:10 adams-computer kernel[0]: MMAC: family specific matching fails
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Initializing.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Probing.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: WARNING - your nVidia device 0x10DE:0x0373 is not known to work. Continuing anyway...
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Starting.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: PCI system 0x10DE:0x0373, subsystem 0x147B:0x1C24 opened.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Mapped from 0xFE02A000 of length 4096.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x34ec9000, tx at 0x34ec9400, wired at 0xcf9c000.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:50:8D:93:B1:E6.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Could not find a valid PHY.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Stopping
Feb 14 15:15:10 adams-computer kernel[0]: MAC1: family specific matching fails
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Initializing.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Probing.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: WARNING - your nVidia device 0x10DE:0x0373 is not known to work. Continuing anyway...
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Starting.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: PCI system 0x10DE:0x0373, subsystem 0x147B:0x1C24 opened.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Mapped from 0xFE027000 of length 4096.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x3ab8a000, tx at 0x3ab8a400, wired at 0x160f6000.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: ( omitted ).
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Found PHY 0x5040:0x0003 at address 1.
Feb 14 15:15:10 adams-computer kernel[0]: com_triton_forcedeth: Ethernet address ( omitted )
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: Enabling... 1 2 3 4 5 6 7
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: Starting transmit/receive engines
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: Network link down.
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: output, seg: 1/1, demand ck: 0, start: a0000155, end: a0000155 - 0
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: Done with packet with flags 2000015a
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:10 adams-computer kernel[0]: MMAC: family specific matching fails
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Initializing.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Probing.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: WARNING - your nVidia device 0x10DE:0x0373 is not known to work. Continuing anyway...
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Starting.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: PCI system 0x10DE:0x0373, subsystem 0x147B:0x1C24 opened.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Mapped from 0xFE02A000 of length 4096.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x34ec9000, tx at 0x34ec9400, wired at 0xcf9c000.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:50:8D:93:B1:E6.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Could not find a valid PHY.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Stopping
Feb 14 15:15:10 adams-computer kernel[0]: MAC1: family specific matching fails
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Initializing.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Probing.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: WARNING - your nVidia device 0x10DE:0x0373 is not known to work. Continuing anyway...
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Starting.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: PCI system 0x10DE:0x0373, subsystem 0x147B:0x1C24 opened.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Mapped from 0xFE027000 of length 4096.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x3ab8a000, tx at 0x3ab8a400, wired at 0x160f6000.
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: ( omitted ).
Feb 14 15:15:10 adams-computer kernel[0]: forcedeth: Found PHY 0x5040:0x0003 at address 1.
Feb 14 15:15:10 adams-computer kernel[0]: com_triton_forcedeth: Ethernet address ( omitted )
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: Enabling... 1 2 3 4 5 6 7
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: Starting transmit/receive engines
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: Network link down.
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: output, seg: 1/1, demand ck: 0, start: a0000155, end: a0000155 - 0
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: Done with packet with flags 2000015a
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:11 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Feb 14 15:15:12 adams-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
That was the most promising bit I got. I never was able to send packets to the router. Not sure why that is.
hey,
can someone upload the kext?
so that i dont have to type all those words into the terminal, because i have problems with typing in the password when i type sudo -s. the terminal wants to know the password but i cant type in anything then.
i'd be very thankful,
sebbe
can someone upload the kext?
so that i dont have to type all those words into the terminal, because i have problems with typing in the password when i type sudo -s. the terminal wants to know the password but i cant type in anything then.
i'd be very thankful,
sebbe
I ended up putting a Linksys PCI card in instead. It works in Windows and MacOS, so why not? Sort of disturbing that a card as old as the Linksys is faster than the Nforce 4 though ..
Sort of disturbing that a card as old as the Linksys is faster than the Nforce 4 though ..
QUOTE(Dan Hammans @ Jan 23 2007, 03:17 PM) 
This may be a bit numb, and or redundant, but I'm sitting over here on Camp Arifjan in Kuwait and we don't have a whole lot to do at the moment. I've been trying to get my Shuttle SN85G4V2 with an AMD A64 3000+ (Yes, I know old and slow -- but we're Army, what do you expect) running in OSX.
For those unaware of this particular system it is NForce3 based.
After quite a bit of swearing, cussing, and threats of a 3 round burst from my rifle I've managed to get this far;
forcedeth: Initializing.
forcedeth: Probing.
forcedeth: WARNING - your nVidia device 0x10DE:0x00D6 is not known to work, but it could be supported in the future. Please contact the coder
forcedeth: Starting.
forcedeth: PCI system 0x10DE:0x00D6, subsystem 0x1297:0xA550 opened.
forcedeth: Allocated 2072 bytes of contiguous memory for DMA: rx at 0x29714000, tx at 0x29714400, wired at 0x13824000.
forcedeth: Found nForce4 LAN with MAC: 00:30:18:b4:85:b8.
forcedeth: Found PHY 0x0000:0x0028 at address 1.
com_triton_forcedeth: Ethernet address 00:30:1b:b4:05:b8
forcedeth: Enabling... 1 2 3 4 5 6 7
forcedeth: Starting transmit/receive engines
forcedeth: Network link down.
forcedeth: Link speed now 100Mbps, code 0x10064
forcedeth: Received irq with events 0x30. Probably TX fail.
forcedeth: Received irq with events 0xx. Probably TX fail.
...
And it continues to throw random event numbers and failing. Not sure what the hell this means, but it's closer than I've gotten yet. In order to get this far I pulled the 0x00D610DE out of windows device manager and threw it in the Info.plist file. Apparently I'm lame though and it doesn't work. If anyone has any suggestions I'll buy you a beer when I get out of this hellhole. Until then,
Thanks,
Dan
For those unaware of this particular system it is NForce3 based.
After quite a bit of swearing, cussing, and threats of a 3 round burst from my rifle I've managed to get this far;
forcedeth: Initializing.
forcedeth: Probing.
forcedeth: WARNING - your nVidia device 0x10DE:0x00D6 is not known to work, but it could be supported in the future. Please contact the coder
forcedeth: Starting.
forcedeth: PCI system 0x10DE:0x00D6, subsystem 0x1297:0xA550 opened.
forcedeth: Allocated 2072 bytes of contiguous memory for DMA: rx at 0x29714000, tx at 0x29714400, wired at 0x13824000.
forcedeth: Found nForce4 LAN with MAC: 00:30:18:b4:85:b8.
forcedeth: Found PHY 0x0000:0x0028 at address 1.
com_triton_forcedeth: Ethernet address 00:30:1b:b4:05:b8
forcedeth: Enabling... 1 2 3 4 5 6 7
forcedeth: Starting transmit/receive engines
forcedeth: Network link down.
forcedeth: Link speed now 100Mbps, code 0x10064
forcedeth: Received irq with events 0x30. Probably TX fail.
forcedeth: Received irq with events 0xx. Probably TX fail.
...
And it continues to throw random event numbers and failing. Not sure what the hell this means, but it's closer than I've gotten yet. In order to get this far I pulled the 0x00D610DE out of windows device manager and threw it in the Info.plist file. Apparently I'm lame though and it doesn't work. If anyone has any suggestions I'll buy you a beer when I get out of this hellhole. Until then,
Thanks,
Dan
I have nearly the same system. Nforce3 SN85G4 Athon64 3200
I got also that far by changing the Vendor/Device ID thing. Please help us!!
Feb 22 12:03:23 jerrys-computer kernel[0]: MMAC: family specific matching fails
Feb 22 12:03:23 jerrys-computer kernel[0]: forcedeth: Initializing.
Feb 22 12:03:23 jerrys-computer kernel[0]: forcedeth: Probing.
Feb 22 12:03:23 jerrys-computer kernel[0]: forcedeth: WARNING - your nVidia device 0x10DE:0x00D6 is not known to work, but it could be supported in the future. Please contact the coder. Continuing anyway...
Feb 22 12:03:23 jerrys-computer kernel[0]: forcedeth: Starting.
Feb 22 12:03:23 jerrys-computer kernel[0]: forcedeth: PCI system 0x10DE:0x00D6, subsystem 0x1297:0xA550 opened.
Feb 22 12:03:23 jerrys-computer kernel[0]: forcedeth: Mapped from 0xEC000000 of length 4096.
Feb 22 12:03:23 jerrys-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x2a495000, tx at 0x2a495400, wired at 0x114ff000.
Feb 22 12:03:23 jerrys-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:30:1B:B0:F3:A5.
Feb 22 12:03:23 jerrys-computer kernel[0]: forcedeth: Found PHY 0x0000:0x0020 at address 1.
Feb 22 12:03:24 jerrys-computer kernel[0]: com_triton_forcedeth: Ethernet address 00:30:1b:b0:f3:a5
Feb 22 12:03:24 jerrys-computer kernel[0]: forcedeth: Enabling... 1 2 3 4 5 6 7
Feb 22 12:03:24 jerrys-computer kernel[0]: forcedeth: Starting transmit/receive engines
Feb 22 12:03:24 jerrys-computer kernel[0]: forcedeth: Network link down.
Feb 22 12:03:24 jerrys-computer kernel[0]: forcedeth: Received irq with events 0x8. Probably TX fail.
Feb 22 12:03:25 jerrys-computer kernel[0]: forcedeth: Link speed now 100Mbps, code 0x10064.
Feb 22 12:03:25 jerrys-computer kernel[0]: forcedeth: Received irq with events 0x8. Probably TX fail.
Feb 22 12:03:25 jerrys-computer kernel[0]: forcedeth: Received irq with events 0x8. Probably TX fail.
Feb 22 12:03:25 jerrys-computer kernel[0]: forcedeth: Received irq with events 0x28. Probably TX fail.
Feb 22 12:03:25 jerrys-computer kernel[0]: forcedeth: Received irq with events 0x28. Probably TX fail.
Feb 22 12:03:25 jerrys-computer kernel[0]: forcedeth: Received irq with events 0x8. Probably TX fail.
Feb 22 12:03:25 jerrys-computer kernel[0]: forcedeth: Received irq with events 0x28. Probably TX fail.
Feb 22 12:03:25 jerrys-computer launchd: Server 5147 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[285]: exited abnormally: Hangup
Feb 22 12:03:25 jerrys-computer kernel[0]: forcedeth: Received irq with events 0x28. Probably TX fail.
Feb 22 12:03:25 jerrys-computer kernel[0]: forcedeth: Received irq with events 0x28.
Hello,
I installed osx 10.4.6 on a M2N Deluxe, traied to load de forcedeth driver but it "says" that it is already loaded, how do I unload the driver that comes with 10.4.6 and load the one downloaded from this site ??
thanks
Hugo
I installed osx 10.4.6 on a M2N Deluxe, traied to load de forcedeth driver but it "says" that it is already loaded, how do I unload the driver that comes with 10.4.6 and load the one downloaded from this site ??
thanks
Hugo
I have an onboard Nforce 4 Lan, will give it a try.
QUOTE(twistmyself @ Jan 15 2007, 12:22 AM)
After about 4 hours of trying the different kext packages I finally got it working on my ASUS A8N-VM. I used the kext package that I will attach, with the -nockd kext.
Thank you for all your hardwork!Click to view attachment
Thank you for all your hardwork!Click to view attachment
I am using the version that he attached and whenever I load it I just get this repeated over and over again
kernel[0]: forcedeth: packet 80000000 - 8000062e
Actually my Lan is Nforce 650i SLI, is there anybody ever tried this driver under Nforce 6? I will follow the instruction and try it out tonight again. Thanks in advance.
my nforce4 lan didn't work with the older versions of the nforce driver on linux, I had to upgrade to a newer kernel to get everything to work.
If it was possible could you merge in all the changes from the nforce driver into your driver?
If it was possible could you merge in all the changes from the nforce driver into your driver?
Here is the message after I enter DMESG, Could you please give me some idea why my card is still not working, even though the driver figured out correct physical MAC address.
forcedeth: Initializing.
forcedeth: Probing.
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...
forcedeth: Starting.
forcedeth: PCI system 0x10DE:0x0269, subsystem 0x1043:0x8221 opened.
forcedeth: Mapped from 0xFE02B000 of length 4096.
forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x3cb73000, tx at 0x3cb73400, wired at 0xaa0000.
forcedeth: Found nForce4 LAN with MAC: 00:1A:92:24:A4:CF.
forcedeth: Found PHY 0x5040:0x0003 at address 1.
forcedeth: Enabling... 1 2 3 4 5 6 7
forcedeth: Starting transmit/receive engines
forcedeth: Network link down.
forcedeth: Initializing.
forcedeth: Probing.
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...
forcedeth: Starting.
forcedeth: PCI system 0x10DE:0x0269, subsystem 0x1043:0x8221 opened.
forcedeth: Mapped from 0xFE02B000 of length 4096.
forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x3cb73000, tx at 0x3cb73400, wired at 0xaa0000.
forcedeth: Found nForce4 LAN with MAC: 00:1A:92:24:A4:CF.
forcedeth: Found PHY 0x5040:0x0003 at address 1.
forcedeth: Enabling... 1 2 3 4 5 6 7
forcedeth: Starting transmit/receive engines
forcedeth: Network link down.
QUOTE(envying @ Mar 1 2007, 02:42 PM)
Here is the message after I enter DMESG, Could you please give me some idea why my card is still not working, even though the driver figured out correct physical MAC address.
forcedeth: Initializing.
forcedeth: Probing.
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...
forcedeth: Starting.
forcedeth: PCI system 0x10DE:0x0269, subsystem 0x1043:0x8221 opened.
forcedeth: Mapped from 0xFE02B000 of length 4096.
forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x3cb73000, tx at 0x3cb73400, wired at 0xaa0000.
forcedeth: Found nForce4 LAN with MAC: 00:1A:92:24:A4:CF.
forcedeth: Found PHY 0x5040:0x0003 at address 1.
forcedeth: Enabling... 1 2 3 4 5 6 7
forcedeth: Starting transmit/receive engines
forcedeth: Network link down.
forcedeth: Initializing.
forcedeth: Probing.
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...
forcedeth: Starting.
forcedeth: PCI system 0x10DE:0x0269, subsystem 0x1043:0x8221 opened.
forcedeth: Mapped from 0xFE02B000 of length 4096.
forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x3cb73000, tx at 0x3cb73400, wired at 0xaa0000.
forcedeth: Found nForce4 LAN with MAC: 00:1A:92:24:A4:CF.
forcedeth: Found PHY 0x5040:0x0003 at address 1.
forcedeth: Enabling... 1 2 3 4 5 6 7
forcedeth: Starting transmit/receive engines
forcedeth: Network link down.
I get that error as well, I have tried all the different drivers, from this thread
I also cant get my ASUS P5N-E SLI Ethernet to work when anybody has the right drivers or a tutorial pls let me know !
thanks
I'm sitting here thinking "You've gotta be kidding me"
I have 3 routers sitting in my room so I can test the ethernet. After continuous browsing, it eventually connects! WTF?
OK, what I did, is in EVERY plist file, I change the 0057 to the 0269. I don't care if it was my vendor ID or not. But its working
Biostar 6100-M9 Motherboard
nForce MCP51 Chipset (Nforce 4)
But I cant connect to the router that it's connected to (the GUI of it) Hrm...getting closer
I can't get my LAN to work either. I have an EVGA 680i SLI nForce motherboard with Dual Gigabit ethernet. Any ideas?
Thank you vercy much
Hey Planetbeing, thanks you for work on forcedeth.
However still problems with nForce 430 chipset (Marvell 88e1111/88e1115). Is there possibility to make driver for Mac from *BSD or Linux system? If it exists - can you provide some links how to do this. I really want Mac OS on my x86 and I ready for work on porting newest version of driver from different OS.
However still problems with nForce 430 chipset (Marvell 88e1111/88e1115). Is there possibility to make driver for Mac from *BSD or Linux system? If it exists - can you provide some links how to do this. I really want Mac OS on my x86 and I ready for work on porting newest version of driver from different OS.
Worked like a charm, first try. Many thanks PlanetBeing.
Gigabyte K8N Pro SLI
(posting this from safari, w00t!)
Gigabyte K8N Pro SLI
(posting this from safari, w00t!)
Thans!!!!!!!!!!!!
Thanks!!!!!master!!!!!haha!!!!! 
Thanks!!!!!master!!!!!haha!!!!!
I use Abit KN9 Ultra main board.
It has 2 lan port and I install JaS Mac OS X 10.4.8 ppf1.
I think this version already has forcedeth.kext because when I boot with -v option,
it show following message.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: MAC1: family specific matching fails
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Initializing.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Probing.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: WARNING - your nVidia device 0x10DE:0x0373 is not known to work. Continuing anyway...
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Starting.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: PCI system 0x10DE:0x0373, subsystem 0x147B:0x1C24 opened.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Mapped from 0xFE02A000 of length 4096.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x23d60000, tx at 0x23d60400, wired at 0x13e65000.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:50:8D:93:B5:9A.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Found PHY 0x5040:0x0003 at address 1.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: com_triton_forcedeth: Ethernet address 00:50:8d:93:b5:9a
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Enabling... 1 2 3 4 5 6 7
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Starting transmit/receive engines
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Network link down.
I think forcedeth.kext doesn't support KN9-ultra network hardware.
How can I solve this problem..?
HCL 10.4.8 shows this mainboard is perfect, but I can't solve network problem.
Please help me..!!
It has 2 lan port and I install JaS Mac OS X 10.4.8 ppf1.
I think this version already has forcedeth.kext because when I boot with -v option,
it show following message.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: MAC1: family specific matching fails
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Initializing.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Probing.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: WARNING - your nVidia device 0x10DE:0x0373 is not known to work. Continuing anyway...
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Starting.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: PCI system 0x10DE:0x0373, subsystem 0x147B:0x1C24 opened.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Mapped from 0xFE02A000 of length 4096.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x23d60000, tx at 0x23d60400, wired at 0x13e65000.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:50:8D:93:B5:9A.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Found PHY 0x5040:0x0003 at address 1.
Mar 27 03:29:55 jungho-lees-computer kernel[0]: com_triton_forcedeth: Ethernet address 00:50:8d:93:b5:9a
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Enabling... 1 2 3 4 5 6 7
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Starting transmit/receive engines
Mar 27 03:29:55 jungho-lees-computer kernel[0]: forcedeth: Network link down.
I think forcedeth.kext doesn't support KN9-ultra network hardware.
How can I solve this problem..?
HCL 10.4.8 shows this mainboard is perfect, but I can't solve network problem.
Please help me..!!
has anyone found a solution for this network link down problem yet?
Well, after goofing with too many things, the thing just stopped working. What I did was reinstall the complete OS. Make sure that you enter the commands exactly as written! I goofed up each time I did it. Working late into the night makes it hard to type well.
I got it to work, although it does get a bit picky. Some times it works, but on a reboot it won't.
I got it to work, although it does get a bit picky. Some times it works, but on a reboot it won't.
Well, I'm new to all this... I've got 10.4.1 on here so, no network. So I can't upgrade to 10.4.5 which apparently is what forcedeth wants othewise you get that superclass error.
I've seen a post suggesting rebuilding forcedeth on my own computer. And I'll be happy to, if someone tells me, er. How to do it. When I load the project file into xcode, xcode has no idea what to do with it...
How do I rebuild forcedeth? Or has someone found some other way of doing this?
I've seen a post suggesting rebuilding forcedeth on my own computer. And I'll be happy to, if someone tells me, er. How to do it. When I load the project file into xcode, xcode has no idea what to do with it...
How do I rebuild forcedeth? Or has someone found some other way of doing this?
Looks like alot of people are having the same issues as me. I am getting the "Network link down" message and then it just stays there, no lights on the back of the nick. I am using 10.4.8 JaS and have an Asus M2N-E. I'll watch this topic just in case anything happens and will keep trying. Its the only nic I own that will work with it.
Cheers - worked first time on my AMD machine. Safari took me to apple.com and suddenly I felt a whole lot better for having taken the effort to install Tiger. Thanks again, it's much appreciated.
I have an MSI k9n board, and I get the same message regarding the onboard lan:
0x10DE:0x0373 known not to work...
Yet according to osx86 wiki's HCL for 10.4.8, it appears that some people have it working. Is there something else I should be trying?
I am using the AMD dvd, which came with forcedeth. Is there a newer version of forcedeth I could try?
~S
0x10DE:0x0373 known not to work...
Yet according to osx86 wiki's HCL for 10.4.8, it appears that some people have it working. Is there something else I should be trying?
I am using the AMD dvd, which came with forcedeth. Is there a newer version of forcedeth I could try?
~S
Could someone confirm my Device Id for me from the attached image. I've tried 0x0026910DE but I get Network link down with forcedeth and with forcedeth-nockd I get loads of packet messages but I still can't connect to the Internet. The mobo I'm using is a ASRock K8NF4G-VSTA nForce MCP 410/430.
I need help with getting my Ethernet working properly. I believe I can get it working with forcedeth-nockd.kext, everytime I try it it picks up Network Settings picks up the Built-in Ethernet and Network Settings but not ISP or Internet.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.