siefer Posted March 13, 2010 Share Posted March 13, 2010 My card is detected now and it recognizes that a cable is attached, however no matter what I do the IP stays at 169.xxx.xx.xx. This is a MCP77 card, 10de:0760 on a 780a chipset running 10.5.8. The router is SMCD3GN and other computers have internet connectivity through it. The MAC address of the card starts with 00. edit: nvm it works!!! i turned on disable msi and powered the computer off for a minute Link to comment Share on other sites More sharing options...
ferro Posted March 15, 2010 Share Posted March 15, 2010 it doesn't work on asus m4n82 with nforce 890i. it gets wrong address from dhcp. does anybody know are there any normal drivers for this motherboadr or not? Link to comment Share on other sites More sharing options...
eno Posted March 22, 2010 Author Share Posted March 22, 2010 it doesn't work on asus m4n82 with nforce 890i. it gets wrong address from dhcp. does anybody know are there any normal drivers for this motherboadr or not? PEBKAC! Seriously, don't post to this forum just to complain. If you want help getting it to work please give a little more information so I (or others) can figure out if there is a problem with the driver or if there is something wrong with your setup. Useful information: driver version, did you attempt to use forcedeth.kext before installing nForceLAN, did you install the kext by hand or did you use the package, have you tried changing the drivers setting (turing of msi, etc). BTW, there are no official (I take by "normal" you mean official) driver for any nVidia hardware outside the MCP89 chipset (macbook/mac mini chipset). The nForceLAN driver is based on the open-source Linux driver. If your motherboard's chipset works under Linux it works with nForceLAN otherwise there is no way I can support it. Link to comment Share on other sites More sharing options...
ferro Posted April 5, 2010 Share Posted April 5, 2010 PEBKAC! Seriously, don't post to this forum just to complain. If you want help getting it to work please give a little more information so I (or others) can figure out if there is a problem with the driver or if there is something wrong with your setup. Useful information: driver version, did you attempt to use forcedeth.kext before installing nForceLAN, did you install the kext by hand or did you use the package, have you tried changing the drivers setting (turing of msi, etc). BTW, there are no official (I take by "normal" you mean official) driver for any nVidia hardware outside the MCP89 chipset (macbook/mac mini chipset). The nForceLAN driver is based on the open-source Linux driver. If your motherboard's chipset works under Linux it works with nForceLAN otherwise there is no way I can support it. okay. i've tried some ways to install it: by hand and by OS setup. forcedeth.kext doesn't work at all. nForceLAN driver works, but only on localhost :censored2:. for example it gets mask 255.255.0.0. can it depends on chipset driver? P.S. on Linux/Win LAN works fine Link to comment Share on other sites More sharing options...
e60 Posted April 13, 2010 Share Posted April 13, 2010 @eno First of all, I want to thank you for your amazing job on the nForce Lan! unfortunately I still have some problems installing and using your kext. Here are my System spects: - Mac OS 10.6.3 - AsereBLN booter - Mainborad: Gigabyte GA-E7AUM-DS2H - Ethernet: nVidia MCP79 Ethernet Controller / Realtek 8211CL chip (10/100/1000 Mbit) Before I use your installer, I delete the "nvnet.kext" located in IONetWorlingFamily.kext -> Content -> Plugins. The installation it self seems to be successful but after restarting my Machine I get no connection to the Internet and sleep won't work any more. Ok, to be honest, sleep don't works correctly without the nForceLAN.kext too. If I resume from sleep, my Network connection is broken. Here are the nForceLAN logs: \f0\fs24 \cf0 12.04.10 22:54:30 Installer[192] nForceLAN Installation Log\ 12.04.10 22:54:30 Installer[192] Opened from: /Users/e60/Desktop/Drivers/nForceLAN_0.64.5.mpkg\ 12.04.10 22:54:43 Installer[192] Aktualisieren: "nForceLAN"\ 12.04.10 22:54:43 Installer[192] Aktualisieren: "nForceLAN (10.6)"\ 12.04.10 22:55:17 kernel nForceLAN: found nVidia MCP79 Ethernet Controller device 10de:0ab0 with flags 0x017cdf5e\ 12.04.10 22:55:17 kernel nForceLAN: Version 0.64.5 starting\ 12.04.10 22:55:17 kernel nForceLAN: failed to open PCI device.\ 12.04.10 22:55:24 installd[198] Installed "nForceLAN" ()\ 12.04.10 22:56:10 kernel nForceLAN: found nVidia MCP79 Ethernet Controller device 10de:0ab0 with flags 0x017cdf5e\ 12.04.10 22:56:10 kernel nForceLAN: Version 0.64.5 starting\ 12.04.10 22:56:11 kernel nForceLAN: Ethernet address 00:1f:d0:a6:df:9c\ 12.04.10 22:56:11 kernel nForceLAN(en0): enabling interrupts with mask: 0x000000df and msiEnable: 0x00000000\ 12.04.10 22:56:11 kernel nForceLAN(en0): Network link down.\ 12.04.10 22:56:12 kernel nForceLAN(en0): Link speed now 100Mbps(duplex = Full, flow control = Yes), code 0x10064.\ And last but not least, here some screenshots. I realy hope you can help me to solve the problem! *Edit* Here are some more logs with LogLevel=1 set in Info.plist 13.04.10 18:58:34 kernel nForceLAN: log verbosity to 1 13.04.10 18:58:34 kernel nForceLAN: message signaled interrupts (MSI): disabled (if available) 13.04.10 18:58:34 kernel nForceLAN: optimization mode: throughput 13.04.10 18:58:34 kernel nForceLAN: timer IRQ: enabled 13.04.10 18:58:34 kernel nForceLAN: probing... 13.04.10 18:58:34 kernel nForceLAN: found nVidia MCP79 Ethernet Controller device 10de:0ab0 with flags 0x017cdf5e 13.04.10 18:58:34 kernel nForceLAN: Version 0.64.5 starting 13.04.10 18:58:34 kernel nForceLAN: supported media: 10BaseT(half) 10BaseT(full) 100BaseTX(full) 100BaseTX(half) 1000BaseTnForceLAN: creating link timer. 13.04.10 18:58:35 kernel nForceLAN: Ethernet address 00:1f:d0:a6:df:9c 13.04.10 18:58:35 kernel Sound assertion ""ERROR: EFI ROM did not publish 'hda-gfx' associative property!\n"" failed in "/SourceCache/AppleHDA/AppleHDA-184.4.3/AppleHDA/AppleHDACodecGeneric.cpp" at line 340 goto ExitErrornForceLAN(en0): enabling interrupts with mask: 0x000000df and msiEnable: 0x00000000 13.04.10 18:58:35 kernel nForceLAN(en0): Network link down. 13.04.10 18:58:36 kernel nForceLAN(en0): Link speed now 100Mbps(duplex = Full, flow control = Yes), code 0x10064. Link to comment Share on other sites More sharing options...
Martijntjuh Posted April 13, 2010 Share Posted April 13, 2010 Great! Thanks, this is the one i'm looking for Link to comment Share on other sites More sharing options...
Skijumper Posted April 13, 2010 Share Posted April 13, 2010 Hi all. Sorry for my English and know about MAC OS, iam from Czech and iam in MAC world new . I have one question about LAN nForce - Forcedeth. I installed now MAC OS Kalyway 10.5.2 and selected Force, my motherboard is MSI P7N-SLI Zilent (Platinum). After start MAC OS, ethernet are work - showing my MAC adress. But if i click to connnect and select "Using DHCP" - OS say me "internet has a self assigned IP may not be able to connect". So i dont understand whats a problem. On the Windows XP is all working normally. Can anybody help me? Link to comment Share on other sites More sharing options...
eno Posted April 14, 2010 Author Share Posted April 14, 2010 I find it a bit troubling that you are having sleep issues with a 9400M chipset. That is the same chipset as in the mac mini and the previous iteration of the Macbook Pro line. This chipset is also one of the most tested with nForceLAN (I have a Macbook Pro). Have you looked at this forum? http://www.insanelymac.com/forum/index.php...48#entry1128917 Edit: Just noticed you are active in that thread... Have you tried turing up the log level and looked at the messages that appear after resuming from sleep? The LAN on my Macbook Pro comes back every time. One comment: With the MCP79 I recommend leaving MSI on. @enoFirst of all, I want to thank you for your amazing job on the nForce Lan! unfortunately I still have some problems installing and using your kext. Here are my System spects: - Mac OS 10.6.3 - AsereBLN booter - Mainborad: Gigabyte GA-E7AUM-DS2H - Ethernet: nVidia MCP79 Ethernet Controller / Realtek 8211CL chip (10/100/1000 Mbit) Before I use your installer, I delete the "nvnet.kext" located in IONetWorlingFamily.kext -> Content -> Plugins. The installation it self seems to be successful but after restarting my Machine I get no connection to the Internet and sleep won't work any more. Ok, to be honest, sleep don't works correctly without the nForceLAN.kext too. If I resume from sleep, my Network connection is broken. Here are the nForceLAN logs: \f0\fs24 \cf0 12.04.10 22:54:30 Installer[192] nForceLAN Installation Log\ 12.04.10 22:54:30 Installer[192] Opened from: /Users/e60/Desktop/Drivers/nForceLAN_0.64.5.mpkg\ 12.04.10 22:54:43 Installer[192] Aktualisieren: "nForceLAN"\ 12.04.10 22:54:43 Installer[192] Aktualisieren: "nForceLAN (10.6)"\ 12.04.10 22:55:17 kernel nForceLAN: found nVidia MCP79 Ethernet Controller device 10de:0ab0 with flags 0x017cdf5e\ 12.04.10 22:55:17 kernel nForceLAN: Version 0.64.5 starting\ 12.04.10 22:55:17 kernel nForceLAN: failed to open PCI device.\ 12.04.10 22:55:24 installd[198] Installed "nForceLAN" ()\ 12.04.10 22:56:10 kernel nForceLAN: found nVidia MCP79 Ethernet Controller device 10de:0ab0 with flags 0x017cdf5e\ 12.04.10 22:56:10 kernel nForceLAN: Version 0.64.5 starting\ 12.04.10 22:56:11 kernel nForceLAN: Ethernet address 00:1f:d0:a6:df:9c\ 12.04.10 22:56:11 kernel nForceLAN(en0): enabling interrupts with mask: 0x000000df and msiEnable: 0x00000000\ 12.04.10 22:56:11 kernel nForceLAN(en0): Network link down.\ 12.04.10 22:56:12 kernel nForceLAN(en0): Link speed now 100Mbps(duplex = Full, flow control = Yes), code 0x10064.\ And last but not least, here some screenshots. I realy hope you can help me to solve the problem! *Edit* Here are some more logs with LogLevel=1 set in Info.plist 13.04.10 18:58:34 kernel nForceLAN: log verbosity to 1 13.04.10 18:58:34 kernel nForceLAN: message signaled interrupts (MSI): disabled (if available) 13.04.10 18:58:34 kernel nForceLAN: optimization mode: throughput 13.04.10 18:58:34 kernel nForceLAN: timer IRQ: enabled 13.04.10 18:58:34 kernel nForceLAN: probing... 13.04.10 18:58:34 kernel nForceLAN: found nVidia MCP79 Ethernet Controller device 10de:0ab0 with flags 0x017cdf5e 13.04.10 18:58:34 kernel nForceLAN: Version 0.64.5 starting 13.04.10 18:58:34 kernel nForceLAN: supported media: 10BaseT(half) 10BaseT(full) 100BaseTX(full) 100BaseTX(half) 1000BaseTnForceLAN: creating link timer. 13.04.10 18:58:35 kernel nForceLAN: Ethernet address 00:1f:d0:a6:df:9c 13.04.10 18:58:35 kernel Sound assertion ""ERROR: EFI ROM did not publish 'hda-gfx' associative property!\n"" failed in "/SourceCache/AppleHDA/AppleHDA-184.4.3/AppleHDA/AppleHDACodecGeneric.cpp" at line 340 goto ExitErrornForceLAN(en0): enabling interrupts with mask: 0x000000df and msiEnable: 0x00000000 13.04.10 18:58:35 kernel nForceLAN(en0): Network link down. 13.04.10 18:58:36 kernel nForceLAN(en0): Link speed now 100Mbps(duplex = Full, flow control = Yes), code 0x10064. -------------------------------------- @ferro okay. i've tried some ways to install it: by hand and by OS setup. forcedeth.kext doesn't work at all. nForceLAN driver works, but only on localhost . for example it gets mask 255.255.0.0. can it depends on chipset driver?P.S. on Linux/Win LAN works fine If your network card works under Linux it should work with nForceLAN. The hard part is tracking down which os component is causing the problem :-/. Can you post anything in the system log that contains the text nForceLAN. The fastest way to get this is to type the following in a console: grep nForceLAN /var/log/system.log Ack, stupid post merging. Link to comment Share on other sites More sharing options...
e60 Posted April 14, 2010 Share Posted April 14, 2010 @eno Tahnk you very mutch for the fast replay! I find it a bit troubling that you are having sleep issues with a 9400M chipset. That is the same chipset as in the mac mini and the previous iteration of the Macbook Pro line. This chipset is also one of the most tested with nForceLAN (I have a Macbook Pro). Very strange. Unfortunately I don't have a clue what is causing these problems. If I install nForceLan and try to go to sleep, it seems that my machine is "shutiung down" but the HDD don't turns off and I can hear that all fans are still active. Trying to resume from "sleep" isn't possible. I always have to turn the computer off and have to restart. After doing so, I can't find any nForceLan related logs from this procedure. The only logs I can find are the startup logs. Furthermore I'm not able to establish a Internet connection if nForceLan is installed, although the network adapter is showing "connected" Without instaling nForceLan and just using IONetworkingFamily.kext (nvnet.kext) sleep works propably, but afer resuming from it Lan is broken. Are there maby any Ethernet relating DSDT edits I have to do to get sleep working? Have you tried turing up the log level and looked at the messages that appear after resuming from sleep? The LAN on my Macbook Pro comes back every time. What do you mean with turing up the log level? I have set the log level to 1. Is there another option? Link to comment Share on other sites More sharing options...
ctheanh Posted April 16, 2010 Share Posted April 16, 2010 After installing your 0.64.5 package.I can see computers (Windows PC) on Network but I can't connect (nothing happen when click "Connect as" in Finder) Link to comment Share on other sites More sharing options...
rafafre Posted April 24, 2010 Share Posted April 24, 2010 Ha! That thing worked for my MCP55 motherboard with Lawless 10.5.4! I'll try with Snow when (if) I get it running... Link to comment Share on other sites More sharing options...
karamat Posted May 2, 2010 Share Posted May 2, 2010 working for me jus a littlr but time wastage broblem every time i restart my pc the exiting connection wont work and new interface detects... so i hav to do again all ip setings after every reboot plzz help Link to comment Share on other sites More sharing options...
shang_2000 Posted May 6, 2010 Share Posted May 6, 2010 thanks! Link to comment Share on other sites More sharing options...
concord Posted May 10, 2010 Share Posted May 10, 2010 this works on Zotec 9300 ITX With Snow you have to move the nvenet.kext from IONetworkwork..... Plugins nvenet really caused issues with my board , even when booted in Linux , it would not work again until I pulled power from box thanks !!! weird, my post didnt take properly?? anyways.. I just found Don Carrolls post today, after I've been banging my head agains the wall with the same issue. so now, I have the same issue as karamat, after reboot I need to re-add the interface after deleting the current one for the NIC to start working... I guess I'll bump up the logging on nForceLAN.kext and post what I find. Link to comment Share on other sites More sharing options...
TennisGeek Posted May 21, 2010 Share Posted May 21, 2010 Very strange. Unfortunately I don't have a clue what is causing these problems. If I install nForceLan and try to go to sleep, it seems that my machine is "shutiung down" but the HDD don't turns off and I can hear that all fans are still active. Trying to resume from "sleep" isn't possible. I always have to turn the computer off and have to restart. I second this. Exact same situation. I have a Zotac GF9300. When it sleeps, it looks like it's hanging. On USB port, I have a USB bluetooth dongle and it stops blinking. So, the USB port with the bluetooth is off at least. The screen goes blank. Everything else is still up and running. My guess is that, the nForceLAN driver gets called to change the power state and it hangs in the nForceLAN driver. The machine sleeps and wakes up fine when the Apple's driver (nvenet.kext in IONetworkFamily) is loaded instead. (Of course it does not activate the Phy and says "inactive" after sleep.) I've briefly googled to see the Linux has the similar problem but I cannot find any. Is there anything I can help? -- TG Link to comment Share on other sites More sharing options...
savage190 Posted May 26, 2010 Share Posted May 26, 2010 I have a mcp78s and it doesn't work....Can someone help me? My board is a K9N2 SLI Platinum with a phenom processor. Is there any kext or anything that it might keep it from working? I am new to the osx86 thing but I am trying. Modified Ikatos v7(with my bought copy of 10.5.7 and voodoo's xnu kernel) Link to comment Share on other sites More sharing options...
kobbyattrams Posted May 27, 2010 Share Posted May 27, 2010 nForceLAN is a recent development which used planetbeing's nForce4 0.3c driver as a framework to port the forcedeth 0.64 driver from linux 2.6.31 to OS X. nForceLAN should support all of the network adapters supported by the forcedeth 0.64 driver (listed below) and is a replacement for both forcedeth.kext and nForceEthernetController.kext. Please remove all installed versions of forcedeth.kext and nForceEthernetController.kext from your system if you are manually installing nForceLAN (not using the pkg). It is recommended, but not required, that all users upgrade to at least 10.5.5 (preferably 10.5.6) and AMD users install the Voodoo XNU kernel. Please post comments in this thread on how well this works (or doesn't work for that matter) for various configurations. The source code for this driver is released under the GPL. The original nForce4 driver is posted here: nForce4 LAN driver Features: - Support for nForce NICs from the nForce1 to the MCP89. - Sleep/wake functionality. - Supports message signalled interrupts (MSI), line interrupts (Legacy), and multiple MSI interrupts. - Supports manual selection of the network medium and max transfer unit (MTU). - Supports hardware VLAN tagging. Supported PCI ids: 0x01c310de, 0x006610de, 0x00d610de, 0x008610de, 0x008c10de, 0x00e610de, 0x00df10de, 0x005610de, 0x005710de, 0x003710de, 0x003810de, 0x026810de, 0x026910de, 0x037210de, 0x037310de, 0x03e510de, 0x03e610de, 0x03ee10de, 0x03ef10de, 0x045010de, 0x045110de, 0x045210de, 0x045310de, 0x054c10de, 0x054d10de, 0x054e10de, 0x054f10de, 0x07dc10de, 0x07dd10de, 0x07de10de, 0x07df10de, 0x076010de, 0x076110de, 0x076210de, 0x076310de, 0x0ab010de, 0x0ab110de, 0x0ab210de, 0x0ab310de, 0x0d7d10de Recent updates: - [0.64.0]Maintenance update (updated to match 2.6.31 forcedeth driver). New device support (MCP89). - [0.64.2]Fixed 10.6 sleep/unload bug. - [0.64.3]Some code cleanup. Rebuilt with 64-bit support. - [0.64.4]Fixed setting the lladdr with ifconfig. Added an option to override the built-in or random MAC. To use the MAC override set (in the plist) MACOverride to true and add a string for OverrideMAC1 and/or Override MAC2. The string should be a standard IPv4 MAC in hexadecimal with pairs of digits separated by colons (ex. 01:23:45:67:89:ab). - [0.64.5]Fixed a typo in nForceLAN::setHardwareAddress(); enjoy! -Nate Kernel extension: 0.64.5 (Snow Leopard + Leopard/Tiger) nForceLAN_0.64.5.mpkg.zip Source: 0.64.2 Source nForceLAN_0.64.2.zip nate im using an hp laptop g60 but i tried installing but it is not working i have problems with graphics too any help plz really need it and i installed iatkos 10.5.5 thank u very much Link to comment Share on other sites More sharing options...
Chad l Posted May 28, 2010 Share Posted May 28, 2010 nForceLAN is a recent development which used planetbeing's nForce4 0.3c driver as a framework to port the forcedeth 0.64 driver from linux 2.6.31 to OS X. nForceLAN should support all of the network adapters supported by the forcedeth 0.64 driver (listed below) and is a replacement for both forcedeth.kext and nForceEthernetController.kext. Please remove all installed versions of forcedeth.kext and nForceEthernetController.kext from your system if you are manually installing nForceLAN (not using the pkg). It is recommended, but not required, that all users upgrade to at least 10.5.5 (preferably 10.5.6) and AMD users install the Voodoo XNU kernel. Please post comments in this thread on how well this works (or doesn't work for that matter) for various configurations. The source code for this driver is released under the GPL. The original nForce4 driver is posted here: nForce4 LAN driver Features: - Support for nForce NICs from the nForce1 to the MCP89. - Sleep/wake functionality. - Supports message signalled interrupts (MSI), line interrupts (Legacy), and multiple MSI interrupts. - Supports manual selection of the network medium and max transfer unit (MTU). - Supports hardware VLAN tagging. Supported PCI ids: 0x01c310de, 0x006610de, 0x00d610de, 0x008610de, 0x008c10de, 0x00e610de, 0x00df10de, 0x005610de, 0x005710de, 0x003710de, 0x003810de, 0x026810de, 0x026910de, 0x037210de, 0x037310de, 0x03e510de, 0x03e610de, 0x03ee10de, 0x03ef10de, 0x045010de, 0x045110de, 0x045210de, 0x045310de, 0x054c10de, 0x054d10de, 0x054e10de, 0x054f10de, 0x07dc10de, 0x07dd10de, 0x07de10de, 0x07df10de, 0x076010de, 0x076110de, 0x076210de, 0x076310de, 0x0ab010de, 0x0ab110de, 0x0ab210de, 0x0ab310de, 0x0d7d10de Recent updates: - [0.64.0]Maintenance update (updated to match 2.6.31 forcedeth driver). New device support (MCP89). - [0.64.2]Fixed 10.6 sleep/unload bug. - [0.64.3]Some code cleanup. Rebuilt with 64-bit support. - [0.64.4]Fixed setting the lladdr with ifconfig. Added an option to override the built-in or random MAC. To use the MAC override set (in the plist) MACOverride to true and add a string for OverrideMAC1 and/or Override MAC2. The string should be a standard IPv4 MAC in hexadecimal with pairs of digits separated by colons (ex. 01:23:45:67:89:ab). - [0.64.5]Fixed a typo in nForceLAN::setHardwareAddress(); enjoy! -Nate Kernel extension: 0.64.5 (Snow Leopard + Leopard/Tiger) nForceLAN_0.64.5.mpkg.zip Source: 0.64.2 Source nForceLAN_0.64.2.zip This is also working on 10/100M LAN by Broadcom® AC131 on a Foxconn M61PMV AM2+ Dial up worked OOB Distro used: ideneb 10.5.5 LEOPARD updated to ideneb 10.5.8 combo Kernel: Voodoo 9.5.0 with seatbelt.kext CPU/MEM: AMD Athlon x2 2.21Ghz Dual-Core / 2 2GB Kingston 644 DIDNT TEST ON SNOW LEOPARD, no clue if its the same results One thing i did notice is a speed cap? Ive got a beautiful cable line with 100mb download 5mb upload (im in canada, we dont get nice upload speeds here) Im only ever able to reach 15mb Download and all my upload... I also have a belkin wireless g usb f5d7050 i used before i got my lan working and i got full download speed. Used ralink software and drivers. HOPE THIS HELPS ANYONE OUT THERE Link to comment Share on other sites More sharing options...
chewara Posted May 29, 2010 Share Posted May 29, 2010 thanks! working great with MCP 77 Nforce Ethernet on ECS GF8100VM-M3 Link to comment Share on other sites More sharing options...
TennisGeek Posted June 3, 2010 Share Posted June 3, 2010 Hello, eno. As I reported before, nForceLAN.kext does hang when the machine goes to sleep on Zotac GF9300. The chipset is MCP79. Here is the /var/log/kernel.log, and I set the log level to 100 in nForceLAN. First, the onboard ethernet was unplugged. I loaded the kext by hand. When it's unplugged, the machine did sleep and come back fine. Once I plug in the cable (Jun 2 22:25:05). The device recognizes it, and the link is now up. (It did DHCP packet, I guess.) Then, I do the sleep again. The machine gets hang. Unfortunately, the log from nForceLAN does not show up in the /var/log/kernel.log, so it's hard to tell where it's hang. But only difference is, once I plug in the cable to the onboard ethernet, it did hang. I built the kext from source, 0.64.2, and using the debug build of x86_64. I'd really appriciate if you could help me to debug this thing. -- TG Jun 2 22:23:45 tut kernel[0]: nForceLAN: log verbosity to 100 Jun 2 22:23:45 tut kernel[0]: nForceLAN: message signaled interrupts (MSI): enabled (if available) Jun 2 22:23:45 tut kernel[0]: nForceLAN: optimization mode: throughput Jun 2 22:23:45 tut kernel[0]: nForceLAN: timer IRQ: enabled Jun 2 22:23:45 tut kernel[0]: nForceLAN: probing... Jun 2 22:23:45 tut kernel[0]: nForceLAN: found nVidia MCP79 Ethernet Controller device 10de:0ab0 with flags 0x017cdf5e Jun 2 22:23:45 tut kernel[0]: nForceLAN (deviceSetup:336) DEBUG: Physical memory mask = 0x016llx Jun 2 22:23:45 tut kernel[0]: nForceLAN: Version 0.64.2 starting Jun 2 22:23:45 tut kernel[0]: nForceLAN (initPCIConfigSpace:1162) DEBUG: found power management capability at 68 Jun 2 22:23:45 tut kernel[0]: nForceLAN (start:189) DEBUG: PCI system 0x10DE:0x0AB0, subsystem 0x19DA:0x0AE5 revision 0xB1 opened. Jun 2 22:23:45 tut kernel[0]: nForceLAN (mapMemoryRegisters:919) DEBUG: mapped from 0xFE02B000 of length 4096. Jun 2 22:23:45 tut kernel[0]: nForceLAN (getMACAddressFromHardware:999) DEBUG: found nForce LAN with MAC: 00:01:2E:2C:7D:8F. Jun 2 22:23:45 tut kernel[0]: nForceLAN (start:208) DEBUG: taking PHY and NIC out of low power mode Jun 2 22:23:45 tut kernel[0]: nForceLAN (getAndInitializePhy:1055) DEBUG: found PHY 0x0700:0x0032 at address 3. Jun 2 22:23:45 tut kernel[0]: nForceLAN: Oui = 732, Model = 110, Revision = 1 Jun 2 22:23:45 tut kernel[0]: nForceLAN: Dumping contents of lower mii registers before initialization Jun 2 22:23:45 tut kernel[0]: nForceLAN: 0000: 00001140 00007949 0000001c 0000c912 000001e1 00000000 00000004 00002001 Jun 2 22:23:45 tut kernel[0]: nForceLAN: 0008: 00000000 00000300 00000000 00000000 00001006 0000f880 00000000 00003000 Jun 2 22:23:45 tut kernel[0]: nForceLAN: 0010: 000001ee 0000401c 00000000 00000044 00000040 00000000 00004100 00002109 Jun 2 22:23:45 tut kernel[0]: nForceLAN: 0018: 00002740 00008c00 00000040 00004003 00008409 00008fb0 00000123 00000000 Jun 2 22:23:45 tut kernel[0]: nForceLAN (phyInit:145) DEBUG: skipping physical reset for RTL8211C Jun 2 22:23:45 tut kernel[0]: nForceLAN: supported media: 10BaseT(half) 10BaseT(full) 100BaseTX(full) 100BaseTX(half) 1000BaseTnForceLAN: no DMA interrupts found. using legacy interrupt. Jun 2 22:23:45 tut kernel[0]: nForceLAN: creating link timer. Jun 2 22:23:45 tut kernel[0]: nForceLAN (getMaxPacketSize:1417) DEBUG: reporting max packet size as: 9100 Jun 2 22:23:45 tut kernel[0]: nForceLAN (getMinPacketSize:1426) DEBUG: reporting min packet size as: 1500 Jun 2 22:23:45 tut kernel[0]: nForceLAN (registerWithPolicyMaker:97) DEBUG: registerWithPolicyMaker: entering ... Jun 2 22:23:45 tut kernel[0]: nForceLAN(en0) (setPowerState:124) DEBUG: setPowerState: old state: 1, new state: 1 Jun 2 22:23:45 tut kernel[0]: nForceLAN: Ethernet address 00:01:2e:2c:7d:8f Jun 2 22:24:09 tut kernel[0]: FakeSMC: key info not found CLWK, length - 6 Jun 2 22:24:11 tut kernel[0]: nForceLAN(en1) (setPowerState:124) DEBUG: setPowerState: old state: 1, new state: 0 Jun 2 22:24:11 tut kernel[0]: nForceLAN(en1) (setPowerState2:158) DEBUG: setting power state to D3cold (Off) Jun 2 22:24:11 tut kernel[0]: AppleYukon2: 00000000,00000000 Yukon2Power - SetWolEnableGPIO - Failed to get ACPI device Jun 2 22:24:13 tut kernel[0]: System Sleep Jun 2 22:24:24 tut kernel[0]: Wake reason = OHC2 Jun 2 22:24:24 tut kernel[0]: System Wake Jun 2 22:24:24 tut kernel[0]: Previous Sleep Cause: 0 Jun 2 22:24:24 tut kernel[0]: FakeSMC: key info not found CLWK, length - 6 Jun 2 22:24:24 tut kernel[0]: nForceLAN(en1) (setPowerState:124) DEBUG: setPowerState: old state: 0, new state: 1 Jun 2 22:24:24 tut kernel[0]: nForceLAN(en1) (setPowerState2:162) DEBUG: setting power state to D0 (On) Jun 2 22:24:24 tut kernel[0]: nForceLAN(en1) (enable:256) DEBUG: enabling NIC (Power State Change = True)... Jun 2 22:24:24 tut kernel[0]: nForceLAN(en1) (resume:504) DEBUG: resuming after sleep Jun 2 22:24:24 tut kernel[0]: nForceLAN(en1) (phyInit:145) DEBUG: skipping physical reset for RTL8211C Jun 2 22:24:24 tut kernel[0]: nForceLAN(en1): supported media: 10BaseT(half) 10BaseT(full) 100BaseTX(full) 100BaseTX(half) 1000BaseTnForceLAN(en1) (setBufSize:158) DEBUG: setBufSize/Setting with regards to mtu(1500) -- 1582 bytes Jun 2 22:24:24 tut kernel[0]: nForceLAN(en1): enabling interrupts with mask: 0x000000df and msiEnable: 0x00000000 Jun 2 22:24:24 tut kernel[0]: nForceLAN(en1) (enable:400) DEBUG: starting transmit/receive engines Jun 2 22:24:24 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:24:24 tut kernel[0]: nForceLAN(en1): Network link down. Jun 2 22:24:24 tut kernel[0]: FakeSMC: key info not found CLWK, length - 6 Jun 2 22:24:24 tut kernel[0]: The USB device IOUSBHubDevice (Port 6 of Hub at 0x6000000) may have caused a wake by issuing a remote wakeup Jun 2 22:24:24 tut kernel[0]: The USB device USB-PS/2 Optical Mouse (Port 3 of Hub at 0x6600000) may have caused a wake by issuing a remote wakeup Jun 2 22:24:26 Tut kernel[0]: Ethernet [AppleYukon2]: Link up on en0, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,ac4c,0de1,0200,c5e1,2c00] Jun 2 22:24:27 Tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:24:27 Tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:24:30 Tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:24:30 Tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:24:33 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:24:33 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:24:36 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:24:36 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:24:39 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:24:39 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:24:42 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:24:42 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:24:45 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:24:45 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:24:48 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:24:48 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:24:51 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:24:51 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:24:54 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:24:54 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:24:57 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:24:57 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:25:00 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:25:00 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:25:03 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:25:03 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 7949 Jun 2 22:25:05 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 796d Jun 2 22:25:05 tut kernel[0]: nForceLAN(en1): Link speed now 1000Mbps(duplex = Full, flow control = Yes), code 0x10032. Jun 2 22:25:05 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 796d Jun 2 22:25:08 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:25:08 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 796d Jun 2 22:25:09 tut kernel[0]: nForceLAN(en1) (rxProcessOptimized:602) DEBUG: packet appears ok. processing packet with flags: 3800805c, txvlan: 00000000, Buffer: 00000000 17192010... Jun 2 22:25:09 tut kernel[0]: nForceLAN(en1) (rxProcessOptimized:602) DEBUG: packet appears ok. processing packet with flags: 3800805c, txvlan: 00000000, Buffer: 00000000 346e8010... Jun 2 22:25:09 tut kernel[0]: nForceLAN(en1) (rxProcessOptimized:602) DEBUG: packet appears ok. processing packet with flags: 3800805c, txvlan: 00000000, Buffer: 00000000 34565010... Jun 2 22:25:11 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:25:11 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 796d Jun 2 22:25:11 tut kernel[0]: nForceLAN(en1) (rxProcessOptimized:602) DEBUG: packet appears ok. processing packet with flags: 3800805c, txvlan: 00000000, Buffer: 00000000 34ba2010... Jun 2 22:25:11 tut kernel[0]: nForceLAN(en1) (rxProcessOptimized:602) DEBUG: packet appears ok. processing packet with flags: 3800805c, txvlan: 00000000, Buffer: 00000000 17dde010... Jun 2 22:25:11 tut kernel[0]: nForceLAN(en1) (rxProcessOptimized:602) DEBUG: packet appears ok. processing packet with flags: 38008113, txvlan: 00000000, Buffer: 00000000 33904010... Jun 2 22:25:11 tut kernel[0]: nForceLAN(en1) (rxProcessOptimized:602) DEBUG: packet appears ok. processing packet with flags: 3800805c, txvlan: 00000000, Buffer: 00000000 174de010... Jun 2 22:25:14 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:25:14 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 796d Jun 2 22:25:14 tut kernel[0]: nForceLAN(en1) (rxProcessOptimized:602) DEBUG: packet appears ok. processing packet with flags: 38008272, txvlan: 00000000, Buffer: 00000000 33a87010... Jun 2 22:25:16 tut kernel[0]: nForceLAN(en1) (rxProcessOptimized:602) DEBUG: packet appears ok. processing packet with flags: 3800803c, txvlan: 00000000, Buffer: 00000000 17db3010... Jun 2 22:25:17 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:25:17 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 796d Jun 2 22:25:19 tut kernel[0]: nForceLAN(en1) (rxProcessOptimized:602) DEBUG: packet appears ok. processing packet with flags: 38008072, txvlan: 00000000, Buffer: 00000000 35118010... Jun 2 22:25:20 tut kernel[0]: nForceLAN(en1) (doLinkTimer:274) DEBUG: link timer expired. checking link status. Jun 2 22:25:20 tut kernel[0]: nForceLAN(en1) (updateLinkSpeed:207) DEBUG: updating link speed. BMSR status: 796d Jun 2 22:27:20 localhost kernel[0]: npvhash=4095 nForceLAN is a recent development which used planetbeing's nForce4 0.3c driver as a framework to port the forcedeth 0.64 driver from linux 2.6.31 to OS X. nForceLAN should support all of the network adapters supported by the forcedeth 0.64 driver (listed below) and is a replacement for both forcedeth.kext and nForceEthernetController.kext. Please remove all installed versions of forcedeth.kext and nForceEthernetController.kext from your system if you are manually installing nForceLAN (not using the pkg). It is recommended, but not required, that all users upgrade to at least 10.5.5 (preferably 10.5.6) and AMD users install the Voodoo XNU kernel. Please post comments in this thread on how well this works (or doesn't work for that matter) for various configurations. The source code for this driver is released under the GPL. The original nForce4 driver is posted here: nForce4 LAN driver Features: - Support for nForce NICs from the nForce1 to the MCP89. - Sleep/wake functionality. - Supports message signalled interrupts (MSI), line interrupts (Legacy), and multiple MSI interrupts. - Supports manual selection of the network medium and max transfer unit (MTU). - Supports hardware VLAN tagging. Supported PCI ids: 0x01c310de, 0x006610de, 0x00d610de, 0x008610de, 0x008c10de, 0x00e610de, 0x00df10de, 0x005610de, 0x005710de, 0x003710de, 0x003810de, 0x026810de, 0x026910de, 0x037210de, 0x037310de, 0x03e510de, 0x03e610de, 0x03ee10de, 0x03ef10de, 0x045010de, 0x045110de, 0x045210de, 0x045310de, 0x054c10de, 0x054d10de, 0x054e10de, 0x054f10de, 0x07dc10de, 0x07dd10de, 0x07de10de, 0x07df10de, 0x076010de, 0x076110de, 0x076210de, 0x076310de, 0x0ab010de, 0x0ab110de, 0x0ab210de, 0x0ab310de, 0x0d7d10de Recent updates: - [0.64.0]Maintenance update (updated to match 2.6.31 forcedeth driver). New device support (MCP89). - [0.64.2]Fixed 10.6 sleep/unload bug. - [0.64.3]Some code cleanup. Rebuilt with 64-bit support. - [0.64.4]Fixed setting the lladdr with ifconfig. Added an option to override the built-in or random MAC. To use the MAC override set (in the plist) MACOverride to true and add a string for OverrideMAC1 and/or Override MAC2. The string should be a standard IPv4 MAC in hexadecimal with pairs of digits separated by colons (ex. 01:23:45:67:89:ab). - [0.64.5]Fixed a typo in nForceLAN::setHardwareAddress(); enjoy! -Nate Kernel extension: 0.64.5 (Snow Leopard + Leopard/Tiger) nForceLAN_0.64.5.mpkg.zip Source: 0.64.2 Source nForceLAN_0.64.2.zip Link to comment Share on other sites More sharing options...
paulwhalley Posted June 15, 2010 Share Posted June 15, 2010 I have a working osx86 installation. I have instructions on how to install ".kext" packages. Can you explain, in simple terms, how to install the nforcelan ".mpkg" package? I am new to macs. Thank you. Link to comment Share on other sites More sharing options...
Miguel Carrera Posted June 28, 2010 Share Posted June 28, 2010 nForceLAN is a recent development which used planetbeing's nForce4 0.3c driver as a framework to port the forcedeth 0.64 driver from linux 2.6.31 to OS X. nForceLAN should support all of the network adapters supported by the forcedeth 0.64 driver (listed below) and is a replacement for both forcedeth.kext and nForceEthernetController.kext. Please remove all installed versions of forcedeth.kext and nForceEthernetController.kext from your system if you are manually installing nForceLAN (not using the pkg). It is recommended, but not required, that all users upgrade to at least 10.5.5 (preferably 10.5.6) and AMD users install the Voodoo XNU kernel. Please post comments in this thread on how well this works (or doesn't work for that matter) for various configurations. The source code for this driver is released under the GPL. The original nForce4 driver is posted here: nForce4 LAN driver Features: - Support for nForce NICs from the nForce1 to the MCP89. - Sleep/wake functionality. - Supports message signalled interrupts (MSI), line interrupts (Legacy), and multiple MSI interrupts. - Supports manual selection of the network medium and max transfer unit (MTU). - Supports hardware VLAN tagging. Supported PCI ids: 0x01c310de, 0x006610de, 0x00d610de, 0x008610de, 0x008c10de, 0x00e610de, 0x00df10de, 0x005610de, 0x005710de, 0x003710de, 0x003810de, 0x026810de, 0x026910de, 0x037210de, 0x037310de, 0x03e510de, 0x03e610de, 0x03ee10de, 0x03ef10de, 0x045010de, 0x045110de, 0x045210de, 0x045310de, 0x054c10de, 0x054d10de, 0x054e10de, 0x054f10de, 0x07dc10de, 0x07dd10de, 0x07de10de, 0x07df10de, 0x076010de, 0x076110de, 0x076210de, 0x076310de, 0x0ab010de, 0x0ab110de, 0x0ab210de, 0x0ab310de, 0x0d7d10de Recent updates: - [0.64.0]Maintenance update (updated to match 2.6.31 forcedeth driver). New device support (MCP89). - [0.64.2]Fixed 10.6 sleep/unload bug. - [0.64.3]Some code cleanup. Rebuilt with 64-bit support. - [0.64.4]Fixed setting the lladdr with ifconfig. Added an option to override the built-in or random MAC. To use the MAC override set (in the plist) MACOverride to true and add a string for OverrideMAC1 and/or Override MAC2. The string should be a standard IPv4 MAC in hexadecimal with pairs of digits separated by colons (ex. 01:23:45:67:89:ab). - [0.64.5]Fixed a typo in nForceLAN::setHardwareAddress(); enjoy! -Nate Kernel extension: 0.64.5 (Snow Leopard + Leopard/Tiger) nForceLAN_0.64.5.mpkg.zip Source: 0.64.2 Source nForceLAN_0.64.2.zip First thanks a lot for this development! I am a newbie and just installed iAtkos S3 V2 successfully in my system, but I am having problems with the Ethernet, for iAtkos I chose nforce ethernet drivers and it worked apparently well but it disconnected me at random times and everytime I restarted my computer it would bring up the connection as ethernet 2, and the next time eth3 and so on, I had to restart my system to get it working again. I used the drivers you provided and now it stays as a single ethernet interface with every boot and it no longer disconnects as long as I don't try to upload a bunch of data (ie. uploading a photo to facebook, login to msn messenger, share a torrent) I've proved this using speedtest.net, the download test works fine but as soon as the upload test begins it disconnects me, OSX Network Diagnostics tells me the connection and settings are correct but ISP, Internet and Server are shown in red or yellow but never come back to green. Sometimes OSX will assign a random IP address but it won't work and if I put a static address matching the settings of my router after it disconnects it wont work either. Again if I restart everything is normal and the internet works as long as I don't try to upload more than 100kb. I tried to search in the forum and on google extensively but to no avail, do you have any tips for me? or does someone who read this has had a similar problem? I read somewhere that Firewire networking could interfere with it so I deleted firewire from OSX networks devices, they also said to allow magic packets and ethernet to boot from lan in windows, this I also did. Thanks to anyone who reads this! -Miguel PS. my system specs are in my signature... Link to comment Share on other sites More sharing options...
ph222 Posted July 1, 2010 Share Posted July 1, 2010 hi, i just updated to 10.6.4 and noticed that i get single bit copy errors, especially in files over 1gb. it might have been so for some time because it only seems to happen in large files and not every time. any hints/ideas ? driver version is the latest version. Link to comment Share on other sites More sharing options...
pyrates Posted July 1, 2010 Share Posted July 1, 2010 hi,i just updated to 10.6.4 and noticed that i get single bit copy errors, especially in files over 1gb. it might have been so for some time because it only seems to happen in large files and not every time. any hints/ideas ? driver version is the latest version. If you loaded in the nforce driver that fixed the ability to read from dvd's that's why. The previous version with the fix for the 2 GB ram limit is what you should be using. But then you can't read dvd's. So pick one. Either have corrupted files and a dvd drive that works, or no corrupted files and don't have a dvd drive that works. Link to comment Share on other sites More sharing options...
ph222 Posted July 1, 2010 Share Posted July 1, 2010 thank you very much for your reply but im unsure if we are talking about the same issue. which version of nforcelan i should try and i am not aware of any ata issues since the drives seem to be handled by ahci default drivers. my errors occur while copying files over the network with nforcelan. single bits in files change in random, maybe 2 or 3 bits in a 1 GB file that was copied. system memory is 4gb if this depends. If you loaded in the nforce driver that fixed the ability to read from dvd's that's why. The previous version with the fix for the 2 GB ram limit is what you should be using. But then you can't read dvd's. So pick one. Either have corrupted files and a dvd drive that works, or no corrupted files and don't have a dvd drive that works. Link to comment Share on other sites More sharing options...
Recommended Posts