Jump to content
InsanelyMac Forum

eno

Members
  • Content count

    187
  • Joined

  • Last visited

  1. eno

    nForce LAN driver

    Just a heads-up. My nForce motherboard fried itself awhile ago so I have no way to test nForceLAN anymore. I will shortly post the latest code on github so that it will be readily available to anyone who wants to fix any of the remaining issues. Just send me a pull request once the repository is up. Repository: http://www.github.com/hjelmn/nForceLAN
  2. eno

    nForce LAN driver

    It looks like another driver might be interfering (no DMA interrupts). Can you check if any of the following are installed (and remove them): nvenet.kext forcedeth.kext forcedeth-d.kext nforce4lan.kext
  3. eno

    nForce LAN driver

    Didn't know about that kext. I will update the pkg later this week to remove that one as well.
  4. eno

    Driver for nForce4 LAN

    forcedeth.kext is obsolete. Try nForceLAN.
  5. eno

    nForce LAN driver

    That shouldn't be possible! The packet is checksummed by the either the os or the nic (depending on what nic you are using). Is there any sort of pattern to the bit errors? Are they really only single bit and not a byte (or multiple byes) or perhaps missing bytes? The only way nForceLAN could be corrupting the data is if the outgoing packet is clobbered before it is checksummed. Is nForceLAN being used on the send or the receive side? Most kernel panics are caused by nvenet.kext being installed (which usually happens during an update). Check if it is installed in /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns and blow it away (it only works properly with the MCP79 anyway).
  6. eno

    nForce LAN driver

    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. -------------------------------------- @ferro 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.
  7. eno

    nForce LAN driver

    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.
  8. eno

    nForce LAN driver

    I must have forgotten to update the plist. If you downloaded and installed the 0.64.5 pkg then you have 0.64.5. Not sure why it would show a different connection on each boot. Maybe it is a problem with the pseudo-random MAC generator (runs when the device has an invalid MAC). Is the device's MAC address the same on each boot?
  9. eno

    nForce LAN driver

    Opps, I found a typo. Not sure why setting the MAC address worked for me when I tested it. Fixed in 0.64.5.
  10. eno

    nForce LAN driver

    Finally finished the update. To turn on the MAC override set MACOverride to true (the key is already in the plist but it is set to false by default) and set a string for OverrideMAC1 and/or OverrideMAC2 to the MAC address. Ex: <key>OverrideMAC1</key> <string>01:23:45:67:89:ab</string>
  11. eno

    nForce LAN driver

    This option I have in mind would be something like: <key>MACOverride</key> <true/> <key>OverrideMAC1</key> <string>00:aa:bb:cc:dd:ee</string> <key>OverrideMAC2</key> <string>00:aa:bb:cc:dd:ef</string> And nForceLAN would set the MAC on initialization (where it is setting the random MAC).
  12. eno

    nForce LAN driver

    Yeah, it involves editing and flashing a new BIOS image. Would a plist option to override the hardware MAC be useful?
  13. eno

    nForce LAN driver

    Or your could just give the card a proper MAC . If you google the MAC there are instructions on how to fix it. I am sure the motherboard came with a label showing the proper MAC (or you could make one up).
  14. eno

    nForce LAN driver

    Cool, thanks. I will update nForceLAN to take the link down before setting the MAC. Expect the update on Wednesday.
  15. eno

    nForce LAN driver

    Thats because that MAC is invalid (MAC addresses should start with 00:). The 04:4B:80:80:80:03 MAC is the default for all nVidia NICs. If you see that MAC it means the true MAC is missing (the manufacturer screwed up) or it is corruptted in the BIOS. You might want to take a look on google and see how to fix the MAC on your motherboard, correct the MAC, then call your ISP and give them the correct MAC. Alternatively, if you want to keep the bad MAC you can download the source code and remove the MAC address check. As for why you are having trouble setting the MAC. I will have to look into that.
×