nForce LAN driver

[verdant]

@ joel you have a 780i nForce chipset MOBO, so recommend you use the Voodoo 9.5.0 kernel......see here.....

 

@ lushen124 you have a MSI nForce4 650i SLI P6N Platinum MOBO.....so recommend you use a modded BIOS if you are not doing so already from here.....

 

@ gsx118, shiftypl Check out my Pre-Series 7 nForce chipset MOBO thread and my blog install guides......

 

Initially, read post #1 in the thread.......and install without video, network and audio drivers selected from the Install DVD Customize menu.......concentrate on getting the basic OS X system running, as the correct video, network and audio drivers can be installed afterwards.......

[eno]

@ joel you have a 780i nForce chipset MOBO, so recommend you use the Voodoo 9.5.0 kernel......see here.....

 

@ lushen124 you have a MSI nForce4 650i SLI P6N Platinum MOBO.....so recommend you use a modded BIOS if you are not doing so already from here.....

 

@ gsx118, shiftypl Check out my Pre-Series 7 nForce chipset MOBO thread and my blog install guides......

 

Initially, read post #1 in the thread.......and install without video, network and audio drivers selected from the Install DVD Customize menu.......concentrate on getting the basic OS X system running, as the correct video, network and audio drivers can be installed afterwards.......

 

Thank you much for posting verdant. Its difficult to keep track of which problems may be due to my driver and which are caused by other parts of the os. I hope 0.62.13n is working well for most!

[jasx]

idk about others, but i've been up 5 days now without a single problem, i'm 99% sure theres something nforcelan doesnt like with my setup, but forcedeth 0.2 is still working for me, only downside is, its half-duplex, and 10Mbps max, and fails if the MTU is over 1000... still better than nothing though.

[eno]

idk about others, but i've been up 5 days now without a single problem, i'm 99% sure theres something nforcelan doesnt like with my setup, but forcedeth 0.2 is still working for me, only downside is, its half-duplex, and 10Mbps max, and fails if the MTU is over 1000... still better than nothing though.

 

Have you tried disabling the timer IRQ in nForceLAN? That sometimes helps when there are IRQ conflicts with other devices. Set DisableTimerIRQ to true in the Info.plist

[jasx]

Have you tried disabling the timer IRQ in nForceLAN? That sometimes helps when there are IRQ conflicts with other devices. Set DisableTimerIRQ to true in the Info.plist

 

just tried that right now, still produced a crash within first 5 minutes of boot

[mcboobalot]

I'm on a GA-M57SLI (88e1116) and I have the cable unplugged issue. I saw others with this mobo got it going on first try - any ideas?

[rggj]

Thanks for this excellent driver.

 

Works like a charm on my P5N-E SLI.

 

 

Same for me. Same mobo. ALL works perfect fine with ideneb 10.5.6. Even the ati wonder usb 2.

I never have a problem installing programs or wathever. It´s my first experience with macs and i love them.

[mcboobalot]

Here's my log output, looks like I never get a MAC addy:

 

Mar 26 00:13:25 localhost kernel[0]: nForceLAN: found nVidia MCP55 Ethernet Controller device 10de:0373 with flags 0x000935ff

Mar 26 00:13:25 localhost kernel[0]: nForceLAN: Version 0.62.13 starting

Mar 26 00:13:28 localhost kernel[0]: nForceLAN: Ethernet address 00:1a:4d:91:9d:70

Mar 26 00:13:29 localhost kernel[0]: nForceLAN(en1): Network link down.

Mar 26 00:26:19 localhost kernel[0]: nForceLAN: found nVidia MCP55 Ethernet Controller device 10de:0373 with flags 0x000935ff

Mar 26 00:26:19 localhost kernel[0]: nForceLAN: Version 0.62.13 starting

Mar 26 00:26:23 localhost kernel[0]: nForceLAN: Ethernet address 00:1a:4d:91:9d:70

Mar 26 00:26:23 localhost kernel[0]: nForceLAN(en1): Network link down.

Mar 26 08:54:47 taylors kernel[0]: nForceLAN(en1): Network link down.

Mar 26 20:16:47 taylors kernel[0]: nForceLAN(en1): Network link down.

Mar 26 20:19:49 localhost kernel[0]: nForceLAN: found nVidia MCP55 Ethernet Controller device 10de:0373 with flags 0x000935ff

Mar 26 20:19:49 localhost kernel[0]: nForceLAN: Version 0.62.13 starting

Mar 26 20:19:53 localhost kernel[0]: nForceLAN: Ethernet address 00:1a:4d:91:9d:70

Mar 26 20:19:53 localhost kernel[0]: nForceLAN(en1): Network link down.

Mar 26 20:30:37 localhost kernel[0]: nForceLAN: found nVidia MCP55 Ethernet Controller device 10de:0373 with flags 0x000935ff

Mar 26 20:30:37 localhost kernel[0]: nForceLAN: Version 0.62.13 starting

Mar 26 20:30:41 localhost kernel[0]: nForceLAN: Ethernet address 00:1a:4d:91:9d:70

Mar 26 20:30:41 localhost kernel[0]: nForceLAN(en1): Network link down.

Mar 26 20:44:25 localhost kernel[0]: nForceLAN: found nVidia MCP55 Ethernet Controller device 10de:0373 with flags 0x000935ff

Mar 26 20:44:25 localhost kernel[0]: nForceLAN: Version 0.62.13 starting

Mar 26 20:44:29 localhost kernel[0]: nForceLAN: Ethernet address 00:1a:4d:91:9d:70

Mar 26 20:44:29 localhost kernel[0]: nForceLAN(en1): Network link down.

Mar 26 20:52:14 localhost kernel[0]: nForceLAN: found nVidia MCP55 Ethernet Controller device 10de:0373 with flags 0x000935ff

Mar 26 20:52:14 localhost kernel[0]: nForceLAN: Version 0.62.13 starting

Mar 26 20:52:18 localhost kernel[0]: nForceLAN: Ethernet address 00:1a:4d:91:9d:70

Mar 26 20:52:19 localhost kernel[0]: nForceLAN(en1): Network link down.

Mar 26 21:02:42 localhost kernel[0]: nForceLAN: setting log verbosity to 3

Mar 26 21:02:42 localhost kernel[0]: nForceLAN: disabling Message Signaled Interrupts (MSI)

Mar 26 21:02:42 localhost kernel[0]: nForceLAN: setting optimization mode: throughput

Mar 26 21:02:42 localhost kernel[0]: nForceLAN: probing...

Mar 26 21:02:42 localhost kernel[0]: nForceLAN: found nVidia MCP55 Ethernet Controller device 10de:0373 with flags 0x000935ff

Mar 26 21:02:42 localhost kernel[0]: nForceLAN: Version 0.62.13 starting

Mar 26 21:02:43 localhost kernel[0]: nForceLAN: supported media: 10BaseT(half) 10BaseT(full) 100BaseTX(full) 100BaseTX(half) 1000BaseT

Mar 26 21:02:43 localhost kernel[0]: nForceLAN: creating link timer.

Mar 26 21:02:43 localhost kernel[0]: nForceLAN: registerWithPolicyMaker: entering ...

Mar 26 21:02:43 localhost kernel[0]: nForceLAN(en0): setPowerState: old state: 1, new state: 1

Mar 26 21:02:46 localhost kernel[0]: nForceLAN: Ethernet address 00:1a:4d:91:9d:70

Mar 26 21:02:46 localhost kernel[0]: nForceLAN(en1): Network link down.

Mar 26 21:11:53 localhost kernel[0]: nForceLAN: setting log verbosity to 2

Mar 26 21:11:53 localhost kernel[0]: nForceLAN: disabling Message Signaled Interrupts (MSI)

Mar 26 21:11:53 localhost kernel[0]: nForceLAN: setting optimization mode: throughput

Mar 26 21:11:53 localhost kernel[0]: nForceLAN: probing...

Mar 26 21:11:53 localhost kernel[0]: nForceLAN: found nVidia MCP55 Ethernet Controller device 10de:0373 with flags 0x000935ff

Mar 26 21:11:53 localhost kernel[0]: nForceLAN: Version 0.62.13 starting

Mar 26 21:11:54 localhost kernel[0]: nForceLAN: supported media: 10BaseT(half) 10BaseT(full) 100BaseTX(full) 100BaseTX(half) 1000BaseT

Mar 26 21:11:54 localhost kernel[0]: nForceLAN: creating link timer.

Mar 26 21:11:54 localhost kernel[0]: nForceLAN: registerWithPolicyMaker: entering ...

Mar 26 21:11:54 localhost kernel[0]: nForceLAN: setPowerState: old state: 1, new state: 1

Mar 26 21:11:57 localhost kernel[0]: nForceLAN: Ethernet address 00:1a:4d:91:9d:70

Mar 26 21:11:58 localhost kernel[0]: nForceLAN(en1): Network link down.

[Matthew L.]

Well, eno, after a long time I've installed OS X on my PC again, and you know what? Your kext works flawlessly, system runs great all the day w/o USB going wierd and connection dropping with HPET and SpeedStep! (v0.62.13) Very big thanks!

[Andy Vandijck]

I rebuilt this for Leopard...

Have fun guys...

Did it for the same friend as the AppleNForceATA driver.

nForceLAN_0.62.13.zip

[quazzar]

m... sorry, I'm sure that this question had already been asked, but still I hope to have some help here...

 

my mobo is Gygabyte GA-N650I-DS4  on nForce 650 chipset, and after installing kext that uploaded here hackintosh (iDeneb Leo 10.5.5) has random freezes... btw, I do have access to the internet (and most part of freezes appears when downloading etc.)

 

without this kext everything works fine.

 

could you advice, what's the reason for it and how to solve this problem?

 

Thank you!!

[Maniac10]

Andy, I've tried your version and got an instant kp. Tried clearing cache and even the "touch thing" but same result. Later I'll take a picture so you can take a look at the problem.

[Nohimn]

I have a P5N-D nForce 750i mobo. I installed from iPC, and the version of this driver included on the disk doesn't seem to work, but the latest does. One thing I will note is that the P5N-D is one of the few nForce 7 boards that is able to run the Vanilla 9.6 kernel. However, the kernel panics when it uses this driver. Otherwise, it seems to run fine. Right now, I'm just using StageXNU 9.4, since that kernel seems compatible with this driver. If you need help testing this driver on a Vanilla 9.6 kernel, I'd be happy to lend a hand! Otherwise, it doesn't really matter. I don't really know how many nForce mobos actually can run the Vanilla 9.6 kernel, so I don't really see an immediate need to get this kext to work with it.

[eno]

I rebuilt this for Leopard...

Have fun guys...

Did it for the same friend as the AppleNForceATA driver.

 

Does it make much of a difference if nForceLAN is linked to the 10.5 sdk?

 

I have a P5N-D nForce 750i mobo. I installed from iPC, and the version of this driver included on the disk doesn't seem to work, but the latest does. One thing I will note is that the P5N-D is one of the few nForce 7 boards that is able to run the Vanilla 9.6 kernel. However, the kernel panics when it uses this driver. Otherwise, it seems to run fine. Right now, I'm just using StageXNU 9.4, since that kernel seems compatible with this driver. If you need help testing this driver on a Vanilla 9.6 kernel, I'd be happy to lend a hand! Otherwise, it doesn't really matter. I don't really know how many nForce mobos actually can run the Vanilla 9.6 kernel, so I don't really see an immediate need to get this kext to work with it.

 

It would be nice to know where the crash is occurring but at this point I assume that the vanilla kernel does not work perfectly with anything other than MCP79 nForce chipsets. I know it works with a vanilla kernel on a Macbook Pro.

 

If you are getting a crash log I am happy to look at it. Who knows maybe some changes to nForceLAN will help stabilize the system.

[Matthew L.]

It would be nice to know where the crash is occurring but at this point I assume that the vanilla kernel does not work perfectly with anything other than MCP79 nForce chipsets. I know it works with a vanilla kernel on a Macbook Pro.

 

If you are getting a crash log I am happy to look at it. Who knows maybe some changes to nForceLAN will help stabilize the system.

I would like to inform you, that I'm using vanilla kernel and the same mobo, same distro used to install, and no panics appear even after over 12 hours of uptime. (If you would like to know the non-apple kexts loaded on my system: AppleDecrypt and Disabler of course, AppleNForceATA test, AppleSMBIOSEFI, your nForceLAN (v0.62.13) and VoodooPower (v1.2.3))

[lftjeep53]

For some reason with the nForceLAN_0.62.13.kext I can surf the web with no problem I can also DL torrents and any other large file from the internet but if I try to transfer any data more then 1.5gb across my network I get a kernel panic at any where between 1.5-2gb transfered. Any Ideas and does any one know where I can find how to uninstall a kext file so that way I can try and role back to the 0.62.12 kext for the nforce lan with out restoreing the os again

[verdant]

For some reason with the nForceLAN_0.62.13.kext I can surf the web with no problem I can also DL torrents and any other large file from the internet but if I try to transfer any data more then 1.5gb across my network I get a kernel panic at any where between 1.5-2gb transfered. Any Ideas and does any one know where I can find how to uninstall a kext file so that way I can try and role back to the 0.62.12 kext for the nforce lan with out restoreing the os again

 

Go to Terminal and type the ollowing followed by Enter/Return key press

 

cd /System/Library/Extensions
sudo mv nForceLAN_0.62.13.kext nForceLAN_0.62.13.kext.disabled
exit

 

Then use Kext Helper b7 to install the nForceLAN_0.62.12.kext

[lftjeep53]

Ok I was able to role back the driver and am now able to transfer data across my network but now It will freeze randomly.

 

System:

q6700

EVGA 780i

8800gt

 

Install

Voodoo kernal

seat belt

nvinjeckt 512mb

nforce 62.12n

 

Also if some one could point me to the link for the 780i thread that would be awsome

[std04003]

Just installed the 0.62.13n driver but I am experiencing the same crashes..How can I post the info about my device so to find out what is happening?

[verdant]

Ok I was able to role back the driver and am now able to transfer data across my network but now It will freeze randomly.

 

System:

q6700

EVGA 780i

8800gt

 

Install

Voodoo kernal

seat belt

nvinjeckt 512mb

nforce 62.12n

 

Also if some one could point me to the link for the 780i thread that would be awsome

 

Check out my nForce Series 7 chipset thread.......

[Matthew L.]

Well, I'm still not the lucky one. I'm still catching some bad interrupts (killing practically everything in my system: ATA, USB, Network) while the network interface is under heavy usage by Transmission and Safari (torrent with over 100 peers, and quickly refreshing pages in Safari), but this is still not a recipe to get interrupted, because it doesn't happen always, and the uptime and transferred data is completely irrelevant. If you've got any ideas, I'd love to hear!

 

P.S.: I don't know if it's caused by HPET and not being DSDT-patched, but I can't reproduce the interrupt anytime, it just happens. (Maybe not, but I don't know the answer for sure.)

[jasx]

figured out what causes the lockups

 

go hit up verdants series 7 nforce thread and do the geforce/nvda* kext mods

the reason is to prevent the nVidia GFX driver kexts from loading as drivers for the wrong i.e. different MOBO components (eg, chipset, network, memory controller etc...)

 

my geforce.kext did not have the "<key>IOPCIPrimaryMatch</key>" (other nvdaresman/NVDANVxxHAL kexts did)

but looks like this:

			<key>IOPCIClassMatch</key>
		<string>0x03000000&0xff000000</string>
		<key>IOPCIMatch</key>
		<string>0x000010de&0x0000ffff</string>

 

dont need to mod every NVDANVxxHAL kext, see what your system uses

sudo dmesg | grep "loaded and registered"

 

resists crash during heavy io/usage

[Matthew L.]

figured out what causes the lockups

 

go hit up verdants series 7 nforce thread and do the geforce/nvda* kext mods

the reason is to prevent the nVidia GFX driver kexts from loading as drivers for the wrong i.e. different MOBO components (eg, chipset, network, memory controller etc...)

 

my geforce.kext did not have the "<key>IOPCIPrimaryMatch</key>" (other nvdaresman/NVDANVxxHAL kexts did)

but looks like this:

			<key>IOPCIClassMatch</key>
		<string>0x03000000&0xff000000</string>
		<key>IOPCIMatch</key>
		<string>0x000010de&0x0000ffff</string>

 

dont need to mod every NVDANVxxHAL kext, see what your system uses

sudo dmesg | grep "loaded and registered"

 

resists crash during heavy io/usage

 

Thanks, will try for sure tomorrow, and report if things went better! By the way, how on Earth can a graphics driver load for Chipset and etc? It should cause instant KP as it tries to load on it, or not?

[verdant]

Thanks, will try for sure tomorrow, and report if things went better! By the way, how on Earth can a graphics driver load for Chipset and etc? It should cause instant KP as it tries to load on it, or not?

 

It frequently does........

[Matthew L.]

It frequently does........

Well, I don't get any, I just can't use my PC anymore because just the graphics driver stays alive. (I see the clock moving.) Maybe I've never ever had a kernel panic on this PC.