scififan68 Posted November 22, 2008 Share Posted November 22, 2008 Mine has the exact same issue. Hate to say it, but I am glad I'm not alone. See my sig for my hardware. Eno....any ideas on this one? I'm also having this same issue... Link to comment Share on other sites More sharing options...
eno Posted November 23, 2008 Author Share Posted November 23, 2008 Mine has the exact same issue. Hate to say it, but I am glad I'm not alone. See my sig for my hardware. Eno....any ideas on this one? Its hard to say what might be happening. Can you turn up the log level (set it to 4) and send me the contents of your /var/log/system.log after the network drops. I will want to know the approximate time that the network went down. Link to comment Share on other sites More sharing options...
icedtrip Posted November 25, 2008 Share Posted November 25, 2008 See attached. Not sure what all the "nForceLAN: IRQ event:" are, but it made it difficult to land the exact time of the drop. I did a test network drop, then brought down en0, clipped the system.log at that point, and brought en0 back up. This is the log that is attached, from when I brought en0 back up till when it went down again. It went down around the 22:55 mark. Hope this helps. system.txt Link to comment Share on other sites More sharing options...
ffogel Posted November 25, 2008 Share Posted November 25, 2008 a huge thank you network and internet work like a charm. However, still i can only boot with the cpus=1 option. this wasn't necessary before the install.... (0.62.3n beta_osx) any help/idea? thanks again! ffogel My Hackintosh: Intel Quad Q6600 2.4GHz 8mb Cache LGA775, ASUS p5n32-e sli plus xfx GeForce 8800gts 640mb (g80), dualscreen working with 1900x1200 and 1280x1024 2x Samsung 500gb SATA HD Jas OSX86 10.5.4 client/server patched with nforce kext Link to comment Share on other sites More sharing options...
eno Posted November 25, 2008 Author Share Posted November 25, 2008 See attached. Not sure what all the "nForceLAN: IRQ event:" are, but it made it difficult to land the exact time of the drop. I did a test network drop, then brought down en0, clipped the system.log at that point, and brought en0 back up. This is the log that is attached, from when I brought en0 back up till when it went down again. It went down around the 22:55 mark. Hope this helps. Odd. It looks like your card stops setting the TX Done/RX Received flags in the interrupt status. This may be why these flags are not checked by the linux driver :-/. Do you know how to compile the source code? If so you can make and test the changes I have in mind. If not I will build a test version later today. a huge thank you network and internet work like a charm.However, still i can only boot with the cpus=1 option. this wasn't necessary before the install.... (0.62.3n beta_osx) any help/idea? thanks again! ffogel My Hackintosh: Intel Quad Q6600 2.4GHz 8mb Cache LGA775, ASUS p5n32-e sli plus xfx GeForce 8800gts 640mb (g80), dualscreen working with 1900x1200 and 1280x1024 2x Samsung 500gb SATA HD Jas OSX86 10.5.4 client/server patched with nforce kext Have you tried the Voodoo XNU kernel? Link to comment Share on other sites More sharing options...
ffogel Posted November 25, 2008 Share Posted November 25, 2008 Have you tried the Voodoo XNU kernel? i used the stageXNU kernel which came with the installer. and it worked till the lan driver was installed. still everything works excellent except the cpus, so i am a bit reluctant.... Link to comment Share on other sites More sharing options...
eno Posted November 25, 2008 Author Share Posted November 25, 2008 i used the stageXNU kernel which came with the installer. and it worked till the lan driver was installed. still everything works excellent except the cpus, so i am a bit reluctant.... Stage + nforce lan is a combination which doesn't work well. There is no telling where the problem is with Stage but system calls as simple as replaceOrCopyPacket seem to fail to work properly on some kernels. Voodoo does not appear to have near as many problems as some of the other kernels. It is the first stable non-vanilla kernel I have used so far. Link to comment Share on other sites More sharing options...
icedtrip Posted November 25, 2008 Share Posted November 25, 2008 Odd. It looks like your card stops setting the TX Done/RX Received flags in the interrupt status. This may be why these flags are not checked by the linux driver :-/. Do you know how to compile the source code? If so you can make and test the changes I have in mind. If not I will build a test version later today. My "skills" in this area are very limited, but I'll see what I can do when I get home tonight if I don't see that you have put together a test build. Compiling, no problem. Finding and making the necessary changes before I get to compiling may be were I fail. Link to comment Share on other sites More sharing options...
ffogel Posted November 25, 2008 Share Posted November 25, 2008 sweet mother of god, i heard this ffogel is some stupid idiot. he forgot to turn of hpet. tar and feathers please. :wallbash: again: praise and glory to eno for this nice and great driver Link to comment Share on other sites More sharing options...
Envying Posted November 25, 2008 Share Posted November 25, 2008 Eno, I just noticed that if I am using Adium, it may cause nforcelan drop the connection from time to time. Not sure if anyone else here has same deal. I will dig it out my system.log to see if I can post some log here. Now I am trying to avoid using Adium current release, may try any later version. Link to comment Share on other sites More sharing options...
Maniac10 Posted November 26, 2008 Share Posted November 26, 2008 I've been using your kext for a month now and I haven't had any kind of problem with the lan controller. It worked flawlessly from the first time.. Thanks a lot eno and congrats for the sticky Link to comment Share on other sites More sharing options...
eno Posted November 26, 2008 Author Share Posted November 26, 2008 My "skills" in this area are very limited, but I'll see what I can do when I get home tonight if I don't see that you have put together a test build. Compiling, no problem. Finding and making the necessary changes before I get to compiling may be were I fail. 0.62.4n includes my "fix". It may or may not fix your issue. Please let me know. Link to comment Share on other sites More sharing options...
douggy12345 Posted November 26, 2008 Share Posted November 26, 2008 Hi I have the driver installed and internet is working really flawlessly. However, when I try to transfer files with my macbook, it is EXTREMELY slow!! I am not particularly knowledgeable when it comes to getting this stuff to work, could anyone walk me through what might be causing this problem? Cheers DOugie Link to comment Share on other sites More sharing options...
ed8888 Posted November 26, 2008 Share Posted November 26, 2008 My RTL8139 card bit the dust this past weekend so I have been stuck without a working ethernet card. I had been using the RTL8139 because the built-in network adapter is a nForce 590i MCP55. The MCP55 ethernet adapter has up until now not worked at all under osx (at least with my gigabyte motherboard). The attached driver is a combination of planetbeing's nForce4 0.3c driver and the forcedeth 0.61 driver from linux 2.6.27. In theory the attached driver should work with any of the network adapters supported by the forcedeth 0.61 driver (from the nForce1 to the MCP79) but it has so far only been tested with my MCP55. This driver can be considered a replacement for both forcedeth.kext and nForceEthernet.kext. Please let me know how well this works (or doesn't work for that matter). WARNING: TURN OFF HPET IN BIOS !!!Or it will freeze your system at StartUp!!!!!! This driver is being released under the GPL. The original nForce4 driver is posted here: nForce4 LAN driver Known working physical devices: Realtek 8211, 8211B, 8211C Realtek/Cicada/Vitesse 8201 Marvel 88E1116, 88E3016 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 Updates: - removed rx/tx checksum overrides. Should work with more cards out of the box now. - [0.61.1alpha_osx]added support for sleep/wake functions. - [0.61.2alpha_osx]added OptimizationMode option (0 = throughput, 1 = cpu). CPU optimization is the default since it appears to works better with some devices (my MCP55). The option can be set in the Info.plist. - [0.61.3alpha_osx]renamed to nForceLAN.kext and some small bug-fixes. - [0.61.4alpha_osx]fixed link timer bug. - [0.61.5alpha_osx]fixed multicast bug. - [0.62.0n alpha_osx]merged some of the code from the nVidia 0.62 linux driver into nForceLAN. Also added proper sleep (D3 mode). - [0.62.1n alpha_osx]Macbook support (the MCP79 on the macbook doesn't work with the 8211C initialization code). - [0.62.2n alpha_osx]Fixed media bug. - [0.62.3n beta_osx]Fixed media with 1000BaseT and added autodetection of flow control. Driver appears stable so moved into Beta status. - [0.62.4n beta_osx]Can now manually set the controller's MTU (not fully tested yet). Can now select 1000BaseT manually. Also deleted interrupt flag checking for RX/TX. This change reflects the linux implementation and may fix issues with some adapters. enjoy! -Nate Kernel extension: 0.61.5alpha_osx 0.62.0n alpha_osx 0.62.1n alpha_osx 0.62.2n alpha_osx 0.62.3n beta_osx 0.62.4n beta_osx Source: 0.62.3n beta_osx (source) ENO Place in the first post the big red letters the prevention of that that it is necessary to switch off HPET!!! WARNING: TURN OFF HPET IN BIOS!!! Or it will freeze your system at StartUp!!! Now all perfectly WORKS Respect man!!! Tnx all...great driver!!! Link to comment Share on other sites More sharing options...
ASNNetworks Posted November 27, 2008 Share Posted November 27, 2008 ENO Place in the first post the big red letters the prevention of that that it is necessary to switch off HPET!!! WARNING: TURN OFF HPET IN BIOS!!! Or it will freeze your system at StartUp!!! Now all perfectly WORKS Respect man!!! Tnx all...great driver!!! Using the latest eno driver in combination with your advice...Running Mac OS for 2,5 hours now, without kernel panic or freeze...With 4 cores enabled and 3GB RAM!! Thanks aloooooot...Been trying for months to get it to work, it seems to be stable now:D Hope this continues:) Link to comment Share on other sites More sharing options...
Justin- Posted November 28, 2008 Share Posted November 28, 2008 Happy to report that disabling HPET has solved the freezing issue on my eVGA 680i A1 motherboard. Thanks, eno! Your driver is much appreciated. Link to comment Share on other sites More sharing options...
lpukraine Posted November 29, 2008 Share Posted November 29, 2008 Guys, need your help! motherboard Asus M2N-E nForce 570 Ultra. Don't working onboard LAN. How can I fix this problem? Link to comment Share on other sites More sharing options...
ASNNetworks Posted November 30, 2008 Share Posted November 30, 2008 YEEEEHAAAAAAA IT WORKSSSS!!!!!!!! The latest eno drivers FINALLY WORKS WITH MY ONBOARD LAN, thanks to ed8888 for turning off HPET....NO {censored} KERNEL PANICS/FREEZES ANYMORE!!!! Been on mac for like 8 hours...no probs! So happy right now...been tryin for months after I upgraded from a 100% working hackintosh...So happy I'm back on mac:D:D:D:D THANNKS ENO AND ED8888!! Link to comment Share on other sites More sharing options...
eno Posted December 2, 2008 Author Share Posted December 2, 2008 0.62.5n has been uploaded. This version adds jumbo frame (9000 byte) support. Note: The kext will need to be reloaded each time after setting the mtu. This is a known bug that will be fixed in the next release. Please let me know of any issues. Link to comment Share on other sites More sharing options...
ASNNetworks Posted December 2, 2008 Share Posted December 2, 2008 0.62.5n has been uploaded. This version adds jumbo frame (9000 byte) support. Note: The kext will need to be reloaded each time after setting the mtu. This is a known bug that will be fixed in the next release. Please let me know of any issues. What's jumbo frame? Link to comment Share on other sites More sharing options...
icedtrip Posted December 4, 2008 Share Posted December 4, 2008 0.62.4n includes my "fix". It may or may not fix your issue. Please let me know. I finally got around to testing out your changed kext last night, and it is still doing the same as before. I tried both 0.62.4n and 0.62.5n (I assumed your changed was also in the 0.62.5n build). The connection still drops with uploads and the same messages as before appear when I change the log level to 4. Any more suggestions or any logs needed? Link to comment Share on other sites More sharing options...
Glassman113 Posted December 4, 2008 Share Posted December 4, 2008 Hi i instaled your nForceLAN_0.62.5n.kext , voodoo_kernel 9.5 and system.kext 9.5 on my MSI k9n platinum(Leopard 10.5.5). Works fine for 5 to 10 min and then i loose internet! Any sugestion? SORRY FOR MY BAD ENGLISH Link to comment Share on other sites More sharing options...
one9092002 Posted December 7, 2008 Share Posted December 7, 2008 My RTL8139 card bit the dust this past weekend so I have been stuck without a working ethernet card. I had been using the RTL8139 because the built-in network adapter is a nForce 590i MCP55. The MCP55 ethernet adapter has up until now not worked at all under osx (at least with my gigabyte motherboard). The attached driver is a combination of planetbeing's nForce4 0.3c driver and the forcedeth 0.61 driver from linux 2.6.27. In theory the attached driver should work with any of the network adapters supported by the forcedeth 0.61 driver (from the nForce1 to the MCP79) but it has so far only been tested with my MCP55. This driver can be considered a replacement for both forcedeth.kext and nForceEthernet.kext. Please let me know how well this works (or doesn't work for that matter). This driver is being released under the GPL. The original nForce4 driver is posted here: nForce4 LAN driver Note: Some Core 2 users have noted freezes/crashes when using this driver. The issue appears to be a timer bug in either the nVidia hardware or the XNU kernel. Until a proper solution can be found it is recommended that these users turn off HPET in their BIOS. Known working physical devices: Realtek 8211, 8211B, 8211C Realtek/Cicada/Vitesse 8201 Marvel 88E1116, 88E3016 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 Updates: - removed rx/tx checksum overrides. Should work with more cards out of the box now. - [0.61.1alpha_osx]added support for sleep/wake functions. - [0.61.2alpha_osx]added OptimizationMode option (0 = throughput, 1 = cpu). CPU optimization is the default since it appears to works better with some devices (my MCP55). The option can be set in the Info.plist. - [0.61.3alpha_osx]renamed to nForceLAN.kext and some small bug-fixes. - [0.61.4alpha_osx]fixed link timer bug. - [0.61.5alpha_osx]fixed multicast bug. - [0.62.0n alpha_osx]merged some of the code from the nVidia 0.62 linux driver into nForceLAN. Also added proper sleep (D3 mode). - [0.62.1n alpha_osx]Macbook support (the MCP79 on the macbook doesn't work with the 8211C initialization code). - [0.62.2n alpha_osx]Fixed media bug. - [0.62.3n beta_osx]Fixed media with 1000BaseT and added autodetection of flow control. Driver appears stable so moved into Beta status. - [0.62.4n beta_osx]Can now manually set the controller's MTU (not fully tested yet). Can now select 1000BaseT manually. Also deleted interrupt flag checking for RX/TX. This change reflects the linux implementation and may fix issues experienced with some adapters. - [0.62.5n beta_osx]Added Jumbo frame support. Known bugs: must reload the kext after setting the mtu. enjoy! -Nate Kernel extension: 0.61.5alpha_osx 0.62.0n alpha_osx 0.62.1n alpha_osx 0.62.2n alpha_osx 0.62.3n beta_osx 0.62.4n beta_osx 0.62.5n beta_osx Source: 0.62.3n beta_osx (source) which kext do i use for asus m2n32 ws pro it has mcp 55 My RTL8139 card bit the dust this past weekend so I have been stuck without a working ethernet card. I had been using the RTL8139 because the built-in network adapter is a nForce 590i MCP55. The MCP55 ethernet adapter has up until now not worked at all under osx (at least with my gigabyte motherboard). The attached driver is a combination of planetbeing's nForce4 0.3c driver and the forcedeth 0.61 driver from linux 2.6.27. In theory the attached driver should work with any of the network adapters supported by the forcedeth 0.61 driver (from the nForce1 to the MCP79) but it has so far only been tested with my MCP55. This driver can be considered a replacement for both forcedeth.kext and nForceEthernet.kext. Please let me know how well this works (or doesn't work for that matter). This driver is being released under the GPL. The original nForce4 driver is posted here: nForce4 LAN driver Note: Some Core 2 users have noted freezes/crashes when using this driver. The issue appears to be a timer bug in either the nVidia hardware or the XNU kernel. Until a proper solution can be found it is recommended that these users turn off HPET in their BIOS. Known worki ng physical devices: Realtek 8211, 8211B, 8211C Realtek/Cicada/Vitesse 8201 Marvel 88E1116, 88E3016 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 Updates: - removed rx/tx checksum overrides. Should work with more cards out of the box now. - [0.61.1alpha_osx]added support for sleep/wake functions. - [0.61.2alpha_osx]added OptimizationMode option (0 = throughput, 1 = cpu). CPU optimization is the default since it appears to works better with some devices (my MCP55). The option can be set in the Info.plist. - [0.61.3alpha_osx]renamed to nForceLAN.kext and some small bug-fixes. - [0.61.4alpha_osx]fixed link timer bug. - [0.61.5alpha_osx]fixed multicast bug. - [0.62.0n alpha_osx]merged some of the code from the nVidia 0.62 linux driver into nForceLAN. Also added proper sleep (D3 mode). - [0.62.1n alpha_osx]Macbook support (the MCP79 on the macbook doesn't work with the 8211C initialization code). - [0.62.2n alpha_osx]Fixed media bug. - [0.62.3n beta_osx]Fixed media with 1000BaseT and added autodetection of flow control. Driver appears stable so moved into Beta status. - [0.62.4n beta_osx]Can now manually set the controller's MTU (not fully tested yet). Can now select 1000BaseT manually. Also deleted interrupt flag checking for RX/TX. This change reflects the linux implementation and may fix issues experienced with some adapters. - [0.62.5n beta_osx]Added Jumbo frame support. Known bugs: must reload the kext after setting the mtu. enjoy! -Nate Kernel extension: 0.61.5alpha_osx 0.62.0n alpha_osx 0.62.1n alpha_osx 0.62.2n alpha_osx 0.62.3n beta_osx 0.62.4n beta_osx 0.62.5n beta_osx Source: 0.62.3n beta_osx (source) which kext do i use for asus m2n32 ws pro it has mcp 55 Link to comment Share on other sites More sharing options...
eno Posted December 8, 2008 Author Share Posted December 8, 2008 I finally got around to testing out your changed kext last night, and it is still doing the same as before. I tried both 0.62.4n and 0.62.5n (I assumed your changed was also in the 0.62.5n build). The connection still drops with uploads and the same messages as before appear when I change the log level to 4. Any more suggestions or any logs needed? Try increasing both the RX and TX ring sizes (try RX=2048, TX=4096). The sizes are set in the Info.plist. Let me know if it takes longer for the connection with the increase ring sizes. I have potentially found the problem. Your card also has problems with the linux forcedeth driver. The fix is to disable MSI interrupts. My nForceLAN driver shouldn't be affected by this bug since it doesn't use MSI (or MSI-X) except that I made a mistake when I copied the code to disable HW interrupts. I will correct the mistake and release a new version later today (0.62.6n). Let me know if it resolves your issue. which kext do i use for asus m2n32 ws pro it has mcp 55 Just use the latest version. Hi i instaled your nForceLAN_0.62.5n.kext , voodoo_kernel 9.5 and system.kext 9.5 on my MSI k9n platinum(Leopard 10.5.5). Works fine for 5 to 10 min and then i loose internet! Any sugestion? SORRY FOR MY BAD ENGLISH There are known incompatibilities with your motherboard and the linux forcedeth driver (from which the nForceLAN driver is based). It seems that the Windows driver can leave the LAN in an unusable state. If you dual-boot windows you might want to try turning the machine off and unplugging it for 30 seconds after using windows. You might also want to check if you are running the latest version of your BIOS. Link to comment Share on other sites More sharing options...
Denicio Posted December 10, 2008 Share Posted December 10, 2008 Hi i instaled your nForceLAN_0.62.5n.kext , voodoo_kernel 9.5 and system.kext 9.5 on my MSI k9n platinum(Leopard 10.5.5). Works fine for 5 to 10 min and then i loose internet! Any sugestion? SORRY FOR MY BAD ENGLISH You might wanna lower your MTU to 1350 or even to 1000. I had the same problem before. Link to comment Share on other sites More sharing options...
Recommended Posts