Jump to content
InsanelyMac Forum
eno

nForce LAN driver

Recommended Posts

Thanks eno!

 

My dual gigabit lan now finally works!

 

MSI k9N SLI AM2 Board with Vitesse chipset: 10de:0373 nVidia Corporation MCP55 Ethernet

Share this post


Link to post
Share on other sites
Advertisement

This works great for my Evga nForce 650i Ultra (after so many failed attempts with other drivers). My system's freezing every 15 minutes or so (have to reboot every time), but I'm thinking that might be due to the kernel I'm using.

Share this post


Link to post
Share on other sites
everytime I load the nforcelan kext the kernel_task hogs my pc, it uses +50% of the cpu constantly. I've tried without cpu optimization, it seems better but kernel_task still uses 10% of the cpu.

 

So, I'm back to classic forcedeth for now, but I'm willing to test anything you can tell me.

 

Fixed int 0.61.4alpha_osx. The driver will now longer take 20+% of the cpu. It looks like the original coder was off by a factor of 10^3 on the timer.

 

Let me know if the latest version works better for you.

Share this post


Link to post
Share on other sites
Please help, I installed your kext on my Acer Aspire 7520G, no effect though :(.

Kalyway 10.5.2

 

Can you send me any lines from your /var/log/system.log that begin with com_triton_forcedeth (.3 and older) or nForceLAN (.4)? I will look and see what might be going on.

Share this post


Link to post
Share on other sites

Now (with 0.61.4) it shows at boot 10mps, but in Leo the speed is like Gigabit (30 to 45 mb/sec).

 

No freeze - no kernel panic. Good work !

Share this post


Link to post
Share on other sites
Now (with 0.61.4) it shows at boot 10mps, but in Leo the speed is like Gigabit (30 to 45 mb/sec).

 

No freeze - no kernel panic. Good work !

 

What code follows "nForceLAN: Link speed now 10 Mbps"?

Share this post


Link to post
Share on other sites

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Version 0.61.4alpha_osx initializing

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: setting optimization mode: cpu

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Probing.

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: found nVidia CK804 Ethernet Controller device 10de:0057 with flags 0x0008021f

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Starting.

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: found power management capability at 68

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: PCI system 0x10DE:0x0057, subsystem 0x147B:0x1C12 revision 0xA3 opened.

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Mapped from 0xFE02F000 of length 4096.

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Found nForce LAN with MAC: 00:50:8D:49:B9:1E.

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Link speed now 10Mbps(full-duplex = 0), code 0x103e8.

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Found PHY 0x03c0:0x0031 at address 1.

Sep 30 19:32:13 localhost kernel[0]: NVDA::probe(display)

 

 

 

I think this doesnt matter, a few lines down i can see

 

Sep 30 17:32:00 localhost kernel[0]: nForceLAN: setBufSize/Apple wants 1500 bytes

Sep 30 17:32:00 localhost kernel[0]: nForceLAN: setBufSize/We can give them 1500 bytes

Sep 30 17:32:00 localhost kernel[0]: nForceLAN: setBufSize/Setting with regards to kIOEthernetMaxPacketSize(1518) -- 1582 bytes

Sep 30 17:32:00 localhost kernel[0]: nForceLAN: Enabling... 1 2 3 4 5 6 7

Sep 30 17:32:00 localhost kernel[0]: nForceLAN: Starting transmit/receive engines

Sep 30 17:32:00 localhost kernel[0]: nForceLAN: Link speed now 1000Mbps(full-duplex = 1), code 0x10032.

 

 

so maybe only a cosmetic issue

Share this post


Link to post
Share on other sites
Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Version 0.61.4alpha_osx initializing

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: setting optimization mode: cpu

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Probing.

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: found nVidia CK804 Ethernet Controller device 10de:0057 with flags 0x0008021f

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Starting.

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: found power management capability at 68

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: PCI system 0x10DE:0x0057, subsystem 0x147B:0x1C12 revision 0xA3 opened.

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Mapped from 0xFE02F000 of length 4096.

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Found nForce LAN with MAC: 00:50:8D:49:B9:1E.

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Link speed now 10Mbps(full-duplex = 0), code 0x103e8.

Sep 30 19:32:12 localhost kernel[0]: nForceLAN: Found PHY 0x03c0:0x0031 at address 1.

Sep 30 19:32:13 localhost kernel[0]: NVDA::probe(display)

 

 

 

I think this doesnt matter, a few lines down i can see

 

Sep 30 17:32:00 localhost kernel[0]: nForceLAN: setBufSize/Apple wants 1500 bytes

Sep 30 17:32:00 localhost kernel[0]: nForceLAN: setBufSize/We can give them 1500 bytes

Sep 30 17:32:00 localhost kernel[0]: nForceLAN: setBufSize/Setting with regards to kIOEthernetMaxPacketSize(1518) -- 1582 bytes

Sep 30 17:32:00 localhost kernel[0]: nForceLAN: Enabling... 1 2 3 4 5 6 7

Sep 30 17:32:00 localhost kernel[0]: nForceLAN: Starting transmit/receive engines

Sep 30 17:32:00 localhost kernel[0]: nForceLAN: Link speed now 1000Mbps(full-duplex = 1), code 0x10032.

 

 

so maybe only a cosmetic issue

 

Looks like it is working :thumbsup_anim:. The connection does get detected as 1000Mbps after the adapter gets enabled. Let me know if you have any other issues.

Share this post


Link to post
Share on other sites
Fixed int 0.61.4alpha_osx. The driver will now longer take 20+% of the cpu. It looks like the original coder was off by a factor of 10^3 on the timer.

 

Let me know if the latest version works better for you.

 

 

It's working great now!!! I'll test it further to check it's stability and report back.

 

Thanks a lot emo!!!

Share this post


Link to post
Share on other sites
It's working great now!!! I'll test it further to check it's stability and report back.

 

Thanks a lot emo!!!

 

Can you also give OptimizationMode 0 a try? On my box OptimizationMode 0 hogs less cpu and is just as fast as OptimizationMode 1 when browsing but it makes short distance ping times fluctuate wildly (might be my x2's fault).

Share this post


Link to post
Share on other sites

Thanks Thanks!!

 

the nForceLAN.kext made my M2N-VM HDMI recognize its integrated LAN!

 

I tried several forcedeth versions, without any previous success.

 

But... it's quite unstable. Im gonna try the 0.6 versions.

 

-Gr-

Share this post


Link to post
Share on other sites

0.61.4alpha_osx seems to have resolved the slight CPU hogging on my machine, however, I will also try OptimizationMode=0 too.

Share this post


Link to post
Share on other sites
Anyone managed to get RTL8201N working?

Device id 0x07dc10de.

 

Sais cable is not in.

 

Did you have an older version of the forcedeth driver loaded before trying nForceLAN? The older driver can cause some NICs to power down requiring a reboot before the new driver will work. You can tell if the NIC is powered down if the link lights on the adapter are off.

Share this post


Link to post
Share on other sites
Did you have an older version of the forcedeth driver loaded before trying nForceLAN? The older driver can cause some NICs to power down requiring a reboot before the new driver will work. You can tell if the NIC is powered down if the link lights on the adapter are off.

 

No eno, I always delte immediatelly non-working .kexts.

But I will give it another shot, thanks.

 

 

 

EDIT: Ok I tried again and I realized that nForceLAN.kext, doesn't even detect the interface i add it myself?

nForceEthernetDriver.kext presents me the interface but still sais cable is not in.

 

I don't know if it matters that I have another NIC on my computer RTL8139 while testing the nForce LAN. Does it?

 

 

 

Also... correct me if i'm wrong but there is no match for my RTL8201N on your source:

 

if (_phyModel == PHY_MODEL_REALTEK_8201) {

if (_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_32 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_33 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_34 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_35 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_36 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_37 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_38 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_39) {

phyReserved = miiRW(_physicalAddress, PHY_REALTEK_INIT_REG6, MII_READ);

phyReserved |= PHY_REALTEK_INIT7;

if (miiRW(_physicalAddress, PHY_REALTEK_INIT_REG6, phyReserved)) {

IOLog ("%s: phy init failed.\n", getName ());

return PHY_ERROR;

}

}

}

 

...because my NIC is PCI_DEVICE_ID_NVIDIA_NVENET_28:

 

#define PCI_DEVICE_ID_NVIDIA_NVENET_28 0x07DC

Share this post


Link to post
Share on other sites
No eno, I always delte immediatelly non-working .kexts.

But I will give it another shot, thanks.

EDIT: Ok I tried again and I realized that nForceLAN.kext, doesn't even detect the interface i add it myself?

nForceEthernetDriver.kext presents me the interface but still sais cable is not in.

 

I don't know if it matters that I have another NIC on my computer RTL8139 while testing the nForce LAN. Does it?

Also... correct me if i'm wrong but there is no match for my RTL8201N on your source:

 

if (_phyModel == PHY_MODEL_REALTEK_8201) {

if (_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_32 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_33 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_34 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_35 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_36 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_37 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_38 ||

_deviceID == PCI_DEVICE_ID_NVIDIA_NVENET_39) {

phyReserved = miiRW(_physicalAddress, PHY_REALTEK_INIT_REG6, MII_READ);

phyReserved |= PHY_REALTEK_INIT7;

if (miiRW(_physicalAddress, PHY_REALTEK_INIT_REG6, phyReserved)) {

IOLog ("%s: phy init failed.\n", getName ());

return PHY_ERROR;

}

}

}

 

...because my NIC is PCI_DEVICE_ID_NVIDIA_NVENET_28:

 

#define PCI_DEVICE_ID_NVIDIA_NVENET_28 0x07DC

 

Have you tried adding 0x07dc10de to the Info.plist? What messages do you see in /var/log/messages that begin with nForceLAN:?

Share this post


Link to post
Share on other sites

Yes i tried adding directly 0x07dc10de.

Enabled show hidden files, went to /var/log and i didn't see any logs about this.

Share this post


Link to post
Share on other sites
Yes i tried adding directly 0x07dc10de.

Enabled show hidden files, went to /var/log and i didn't see any logs about this.

 

Sorry about that. I meant /var/log/system.log. Been using linux too much lately.

Share this post


Link to post
Share on other sites
Sorry about that. I meant /var/log/system.log. Been using linux too much lately.

 

Ok :D

i am posting this from RTL8201N :(

What happened was that i entered only my id 0x07dc10de in .plist, optimization mode 0 and then i loaded the .kext.

Then it worked. As soon as i restarted it didn't work "cable not in". (i was restarting all the other times i tried, but immediately).

Then i left the cable plugged in, let the computer shut down for 1 minute, re-booted and it is working now every time.

 

If i have anymore problems i will post here, "eno" thanks for all the help and bravo on the .kext.

 

 

 

Oct 3 15:32:22 localhost kernel[0]: nForceLAN: Version 0.61.4alpha_osx initializing

Oct 3 15:32:22 localhost kernel[0]: nForceLAN: setting optimization mode: cpu

Oct 3 15:32:22 localhost kernel[0]: nForceLAN: Probing.

Oct 3 15:32:22 localhost kernel[0]: nForceLAN: found nVidia MCP73 Ethernet Controller device 10de:07dc with flags 0x0011f54b

Oct 3 15:32:22 localhost kernel[0]: nForceLAN: Starting.

Oct 3 15:32:22 localhost kernel[0]: nForceLAN: found power management capability at 68

Oct 3 15:32:22 localhost kernel[0]: nForceLAN: PCI system 0x10DE:0x07DC, subsystem 0x1458:0xE000 revision 0xA2 opened.

Oct 3 15:32:22 localhost kernel[0]: nForceLAN: Mapped from 0xE4108000 of length 4096.

Oct 3 15:32:22 localhost kernel[0]: nForceLAN: Found nForce LAN with MAC: 00:1D:7D:D1:76:7F.

Oct 3 15:32:22 localhost kernel[0]: nForceLAN: Taking PHY and NIC out of low power mode

Oct 3 15:32:22 localhost kernel[0]: nForceLAN: Found PHY 0x0000:0x0020 at address 1.

.

.

.

Oct 3 15:32:23 localhost kernel[0]: nForceLAN: registerWithPolicyMaker: entering ...

Oct 3 15:32:23 localhost kernel[0]: nForceLAN: setPowerState: old state: 1, new state: 1

.

.

.

Oct 3 15:32:26 localhost kernel[0]: nForceLAN: Ethernet address 00:1d:7d:d1:76:7f

.

.

.

Oct 3 19:16:42 localhost kernel[0]: nForceLAN: setBufSize/Apple wants 1500 bytes

Oct 3 19:16:42 localhost kernel[0]: nForceLAN: setBufSize/We can give them 1500 bytes

Oct 3 19:16:42 dennis-kozlowskis-macpro31-2 kernel[0]: nForceLAN: setBufSize/Setting with regards to mtu(1500) -- 1564 bytes

Oct 3 19:16:42 dennis-kozlowskis-macpro31-2 configd[49]: setting hostname to "dennis-kozlowskis-macpro31-2.local"

Oct 3 19:16:42 dennis-kozlowskis-macpro31-2 kernel[0]: nForceLAN: Enabling... 1 2 3 4 5 6 7

Oct 3 19:16:42 dennis-kozlowskis-macpro31-2 kernel[0]: nForceLAN: Starting transmit/receive engines

Oct 3 19:16:42 dennis-kozlowskis-macpro31-2 kernel[0]: nForceLAN: Network link down.

Oct 3 19:16:42 dennis-kozlowskis-macpro31-2 kernel[0]: nForceLAN: setMode (true, false)

Oct 3 19:16:42 dennis-kozlowskis-macpro31-2 kernel[0]: nForceLAN: setMode (false, false)

.

.

.

Share this post


Link to post
Share on other sites

just AMAZING!!!! you are the best dude!

 

0.61.4alpha_osx - nForceLAN.kext.zip installed with kextHelper

 

working perfect without cpus=1, and the unplugg things on a marvell 88E1116

 

My mobo info (desktop pc) Gigabyte GA-M57SLI-S4

 

well done!! and please post it this topic, or post it on Guides ;)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.



×