I don't know. I already did that in the NetworkInterfaces.plist (I think) and still nothing. Also added the card id in the Info.plist of the kext. Still no go.Yeah, it involves editing and flashing a new BIOS image.
Would a plist option to override the hardware MAC be useful?
#641
Posted 01 February 2010 - 07:11 PM
#642
Posted 01 February 2010 - 07:35 PM
I don't know. I already did that in the NetworkInterfaces.plist (I think) and still nothing. Also added the card id in the Info.plist of the kext. Still no go.
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).
#643
Posted 01 February 2010 - 07:46 PM
#644
Posted 07 February 2010 - 05:45 PM
#645
Posted 09 February 2010 - 02:03 AM
Did you manage to create that plist file eno?
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>
#646
Posted 09 February 2010 - 01:18 PM
#647
Posted 09 February 2010 - 02:34 PM
Thanks eno, it works now, with the override key.
Just a small thing: before I modified the plist file, I tried changing the mac address again. With this new kext, right after I type the password and hit ok in the "Change MAC" application, the PC freezes completely and I have to restart. So it doesn't work like that anymore. Good thing the override solution works.
Opps, I found a typo. Not sure why setting the MAC address worked for me when I tested it. Fixed in 0.64.5.
#648
Posted 24 February 2010 - 03:33 AM
This is from the Info.plist file:
<key>CFBundleVersion</key>
<string>0.64.2</string>
Am I somehow getting the wrong version on the download? What I have sort of works. I have to go into network settings each boot and enable the ethernet. It creates a new connection each time, so I have "Ethernet, Ethernet 2, Ethernet 3..." to the number of times I have booted and enabled it. Had a similar problem when running 10.5.6, but upgrading to 0.64.3 seemed to solve the problem. (kextstat shows 0.64.3 on my 10.5.6 install) I'm now running 10.6.0 trying to run nForceLAN 0.64.5 and the problem is back. Any ideas?
Thanks,
Norm
#649
Posted 24 February 2010 - 11:35 PM
Downloaded and installed 0.64.5, and kextstat still shows it at 0.64.2. Removed nForceLAN completely, and reinstalled and it still says 0.64.2.
This is from the Info.plist file:
<key>CFBundleVersion</key>
<string>0.64.2</string>
Am I somehow getting the wrong version on the download? What I have sort of works. I have to go into network settings each boot and enable the ethernet. It creates a new connection each time, so I have "Ethernet, Ethernet 2, Ethernet 3..." to the number of times I have booted and enabled it. Had a similar problem when running 10.5.6, but upgrading to 0.64.3 seemed to solve the problem. (kextstat shows 0.64.3 on my 10.5.6 install) I'm now running 10.6.0 trying to run nForceLAN 0.64.5 and the problem is back. Any ideas?
Thanks,
Norm
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?
#650
Posted 26 February 2010 - 01:58 AM
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?
I installed from the 0.64.5 package.
mac address is the same every boot. Tried to go to 0.64.3 (copied from my 10.5.6 install) and it doesn't work either. In fact it disconnects after a few mins of browsing.
Thanks,
Norm
#651
Posted 13 March 2010 - 09:08 AM
edit: nvm it works!!!
#652
Posted 15 March 2010 - 07:45 PM
#653
Posted 22 March 2010 - 04:30 PM
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.
#654
Posted 05 April 2010 - 05:00 PM
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
P.S. on Linux/Win LAN works fine
#655
Posted 13 April 2010 - 08:48 AM
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.
Attached Files
#656
Posted 13 April 2010 - 06:10 PM
#657
Posted 13 April 2010 - 11:23 PM
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?
#658
Posted 14 April 2010 - 02:47 AM
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.
@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.plist13.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.
#659
Posted 14 April 2010 - 09:29 AM
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.
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?
#660
Posted 16 April 2010 - 05:27 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users



Sign In
Create Account







