Jump to content

nForce LAN driver

eno

By eno,
in LAN and Wireless

 Share
740 posts in this topic

Recommended Posts

Maniac10
Maniac10
Posted
Posted

Yes eno, that was the question.

@Xander: tienes que eliminar el kext de forcedeth y despues instalar el nforcelan y deberia andar bien. Avisa como te ha salido.

 

@eno: The last (.10) version solved my slowdown problem, thanks a lot!!!

Link to comment
Share on other sites
clonek
clonek
Posted
Posted
I'm not sure what happened, but when I came home tonight both ports were operational. One has a self-assigned address and the other has a dhcp-leased address. It may just be coincidence, but I had booted the system up without having a network cable attached. I have my wireless disabled at the moment and everything seems to be ok. I'll run it for a while and see if I had any problems.

 

 

Upon booting today, it's no longer working. My primary port says cable unplugged again. My second port is still shows a self-assigned IP (which is probably a good thing) I've also rebooted twice and each time a new ethernet device appeared in the network prefs.

 

Here's my output from syslog

 

I noticed en0 listed in here which is my onboard wireless? I'm not sure why that would be there since it doesn't use the driver.

 

Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: Version 0.62.7 initializing
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting log verbosity to 3
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: nForceLANabling Message Signaled Interrupts (MSI)
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting optimization mode: throughput
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: probing...
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: starting...
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: PCI system 0x10DE:0x0370, subsystem 0x0000:0x0000 revision 0xA2 opened.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: cannot map device memory.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: could not map memory registers
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: stopping
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: Version 0.62.7 initializing
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting log verbosity to 3
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: nForceLANabling Message Signaled Interrupts (MSI)
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting optimization mode: throughput
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: probing...
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: found nVidia MCP55 Ethernet Controller device 10de:0373 with flags 0x000935ff
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: starting...
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: found power management capability at 68
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: Version 0.62.7 initializing
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting log verbosity to 3
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: nForceLANabling Message Signaled Interrupts (MSI)
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting optimization mode: throughput
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: probing...
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: found nVidia MCP55 Ethernet Controller device 10de:0373 with flags 0x000935ff
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: starting...
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: found power management capability at 68
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: PCI system 0x10DE:0x0373, subsystem 0x1043:0xCB84 revision 0xA2 opened.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: mapped from 0xFE02A000 of length 4096.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: found nForce LAN with MAC: 04:4B:80:80:80:03.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: taking PHY and NIC out of low power mode
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: fFound PHY 0x5040:0x0003 at address 1.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: PCI system 0x10DE:0x0373, subsystem 0x1043:0xCB84 revision 0xA2 opened.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: mapped from 0xFE027000 of length 4096.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: found nForce LAN with MAC: 04:4B:80:80:80:03.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: taking PHY and NIC out of low power mode
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: fFound PHY 0x5040:0x0003 at address 1.
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: Version 0.62.7 initializing
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting log verbosity to 3
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: nForceLANabling Message Signaled Interrupts (MSI)
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting optimization mode: throughput
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: probing...
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: starting...
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: found power management capability at 68
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: PCI system 0x10DE:0x0371, subsystem 0x1043:0x81F6 revision 0xA2 opened.
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: mapped from 0xFE020000 of length 16384.
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: MAC address 00:00:00:00:00:00 given by device is not valid. Using random MAC.
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: found nForce LAN with MAC: 00:00:00:6C:FB:F2.
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: fFound PHY 0x0000:0x0000 at address 1.
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: supported media: 10BaseT(half) 10BaseT(full) 100BaseTX(full) 100BaseTX(half) 1000BaseT
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: reporting max packet size as: 9100
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: reporting min packet size as: 1500
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: registerWithPolicyMaker: entering ...
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN(en0): setPowerState: old state: 1, new state: 1
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: supported media: 10BaseT(half) 10BaseT(full) 100BaseTX(full) 100BaseTX(half) 1000BaseT
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: reporting max packet size as: 9100
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: reporting min packet size as: 1500
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: registerWithPolicyMaker: entering ...
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN(en0): setPowerState: old state: 1, new state: 1
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: Ethernet address 04:4b:80:80:80:03
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: Ethernet address 04:4b:80:80:80:03
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: supported media:
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: reporting max packet size as: 0
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: reporting min packet size as: 1500
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: registerWithPolicyMaker: entering ...
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN(en0): setPowerState: old state: 1, new state: 1
Tue Jan 13 17:10:44 jays-mac-pro kernel[0] <Debug>: nForceLAN: Ethernet address 00:00:00:6c:fb:f2
Tue Jan 13 17:10:44 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): enabling...
Tue Jan 13 17:10:44 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): failed to open PCI device.
Tue Jan 13 17:10:44 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): setMode (true, false)
Tue Jan 13 17:10:44 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): setting multicast list with 0 items
Tue Jan 13 17:10:44 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): setMode (false, false)
Tue Jan 13 17:10:49 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): setMode (true, false)
Tue Jan 13 17:10:49 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): setting multicast list with 1 items
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): enabling...
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): setBufSize/Apple wants 1500 bytes
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): setBufSize/We can give them 1500 bytes
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): setBufSize/Setting with regards to mtu(1500) -- 1582 bytes
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): starting transmit/receive engines
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): Network link down.
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): setMode (true, false)
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): setting multicast list with 0 items
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): setMode (false, false)
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): IRQ event: 00000010
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): Done with packet with flags 2000015a

 

looking at ifconfig, my second port is now en1 and the first is en5.

Link to comment
Share on other sites
eno
eno
Posted
  • Author
Posted

I see two problems. One is that nForceLAN is trying to start on devices for which probe should return NULL (no match). nForceLAN never tried to open my 0x0370 device so I find this a little puzzling... Anyway, use 0.62.10 to fix the matching problem.

 

The other problem is that both of you actual ethernet ports get the same bad MAC address (04:4b:80:80:80:03). I am not sure what could be causing that problem but you might try removing 0.62.7, deleting all of the ethernet devices in the system preferences (or delete /Library/Preferences/SystemConfiguration/com.apple.network.identification.plist . Then place 0.62.10 in your extensions and shut the machine down and remove the power for 30 seconds.

 

This way we can eliminate all the potential sources of problems at once.

 

Upon booting today, it's no longer working. My primary port says cable unplugged again. My second port is still shows a self-assigned IP (which is probably a good thing) I've also rebooted twice and each time a new ethernet device appeared in the network prefs.

 

Here's my output from syslog

 

I noticed en0 listed in here which is my onboard wireless? I'm not sure why that would be there since it doesn't use the driver.

 

Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: Version 0.62.7 initializing
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting log verbosity to 3
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: nForceLANabling Message Signaled Interrupts (MSI)
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting optimization mode: throughput
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: probing...
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: starting...
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: PCI system 0x10DE:0x0370, subsystem 0x0000:0x0000 revision 0xA2 opened.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: cannot map device memory.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: could not map memory registers
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: stopping
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: Version 0.62.7 initializing
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting log verbosity to 3
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: nForceLANabling Message Signaled Interrupts (MSI)
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting optimization mode: throughput
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: probing...
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: found nVidia MCP55 Ethernet Controller device 10de:0373 with flags 0x000935ff
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: starting...
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: found power management capability at 68
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: Version 0.62.7 initializing
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting log verbosity to 3
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: nForceLANabling Message Signaled Interrupts (MSI)
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting optimization mode: throughput
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: probing...
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: found nVidia MCP55 Ethernet Controller device 10de:0373 with flags 0x000935ff
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: starting...
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: found power management capability at 68
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: PCI system 0x10DE:0x0373, subsystem 0x1043:0xCB84 revision 0xA2 opened.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: mapped from 0xFE02A000 of length 4096.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: found nForce LAN with MAC: 04:4B:80:80:80:03.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: taking PHY and NIC out of low power mode
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: fFound PHY 0x5040:0x0003 at address 1.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: PCI system 0x10DE:0x0373, subsystem 0x1043:0xCB84 revision 0xA2 opened.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: mapped from 0xFE027000 of length 4096.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: found nForce LAN with MAC: 04:4B:80:80:80:03.
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: taking PHY and NIC out of low power mode
Tue Jan 13 17:09:54 jays-mac-pro kernel[0] <Debug>: nForceLAN: fFound PHY 0x5040:0x0003 at address 1.
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: Version 0.62.7 initializing
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting log verbosity to 3
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: nForceLANabling Message Signaled Interrupts (MSI)
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: setting optimization mode: throughput
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: probing...
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: starting...
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: found power management capability at 68
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: PCI system 0x10DE:0x0371, subsystem 0x1043:0x81F6 revision 0xA2 opened.
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: mapped from 0xFE020000 of length 16384.
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: MAC address 00:00:00:00:00:00 given by device is not valid. Using random MAC.
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: found nForce LAN with MAC: 00:00:00:6C:FB:F2.
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: fFound PHY 0x0000:0x0000 at address 1.
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: supported media: 10BaseT(half) 10BaseT(full) 100BaseTX(full) 100BaseTX(half) 1000BaseT
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: reporting max packet size as: 9100
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: reporting min packet size as: 1500
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: registerWithPolicyMaker: entering ...
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN(en0): setPowerState: old state: 1, new state: 1
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: supported media: 10BaseT(half) 10BaseT(full) 100BaseTX(full) 100BaseTX(half) 1000BaseT
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: reporting max packet size as: 9100
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: reporting min packet size as: 1500
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: registerWithPolicyMaker: entering ...
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN(en0): setPowerState: old state: 1, new state: 1
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: Ethernet address 04:4b:80:80:80:03
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: Ethernet address 04:4b:80:80:80:03
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: supported media:
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: reporting max packet size as: 0
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: reporting min packet size as: 1500
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN: registerWithPolicyMaker: entering ...
Tue Jan 13 17:09:55 jays-mac-pro kernel[0] <Debug>: nForceLAN(en0): setPowerState: old state: 1, new state: 1
Tue Jan 13 17:10:44 jays-mac-pro kernel[0] <Debug>: nForceLAN: Ethernet address 00:00:00:6c:fb:f2
Tue Jan 13 17:10:44 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): enabling...
Tue Jan 13 17:10:44 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): failed to open PCI device.
Tue Jan 13 17:10:44 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): setMode (true, false)
Tue Jan 13 17:10:44 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): setting multicast list with 0 items
Tue Jan 13 17:10:44 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): setMode (false, false)
Tue Jan 13 17:10:49 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): setMode (true, false)
Tue Jan 13 17:10:49 jays-mac-pro kernel[0] <Debug>: nForceLAN(en1): setting multicast list with 1 items
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): enabling...
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): setBufSize/Apple wants 1500 bytes
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): setBufSize/We can give them 1500 bytes
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): setBufSize/Setting with regards to mtu(1500) -- 1582 bytes
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): starting transmit/receive engines
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): Network link down.
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): setMode (true, false)
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): setting multicast list with 0 items
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): setMode (false, false)
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): IRQ event: 00000010
Tue Jan 13 17:11:12 jays-mac-pro kernel[0] <Debug>: nForceLAN(en5): Done with packet with flags 2000015a

 

looking at ifconfig, my second port is now en1 and the first is en5.

 

Yes eno, that was the question.

@Xander: tienes que eliminar el kext de forcedeth y despues instalar el nforcelan y deberia andar bien. Avisa como te ha salido.

 

@eno: The last (.10) version solved my slowdown problem, thanks a lot!!!

 

Thanks for the help. Glad to hear the latest version is working better for you.

Link to comment
Share on other sites
clonek
clonek
Posted
Posted

I have a working connection now (I hope). Here's everything I did.

 

Moved old kext to desktop

Deleted /Library/Preferences/SystemConfiguration/com.apple.network.identification.plist

Installed new kext with kext helper

Deleted kext cache

Shutdown and unplugged for 30 sec.

On boot went to network prefs, one interface appeared and received a dhcp address.

Disabled Wireless interface

Gave wired interface a static IP. Internet worked

Shutdown and unplugged for 30 seconds again.

Booted up and the interface said cable unplugged (No network connection)

Rebooted

Disabled 2nd interface in BIOS

Booted OSX, new interface appeared in network prefs, got DHCP, set to static, confirmed connection to the internet.

Shutdown and unplugged for 30 seconds

Booted up and network was still working.

 

I disabled the 2nd interface because I saw the duplicate mac address problem again. So it seems that was my problem. Hopefully things stay working. I don't use the 2nd interface for anything so it's no big deal for me to have it disabled.

 

Thanks for the help!

Link to comment
Share on other sites
eno
eno
Posted
  • Author
Posted

Glad to hear that worked for you.

 

I guess you have one of those motherboards with a bad MAC. Do you get a different MAC address in windows? If so it might be interesting to dump all of the NICs registers and see if the manufacturer set the MAC in the wrong register.

 

I have a working connection now (I hope). Here's everything I did.

 

Moved old kext to desktop

Deleted /Library/Preferences/SystemConfiguration/com.apple.network.identification.plist

Installed new kext with kext helper

Deleted kext cache

Shutdown and unplugged for 30 sec.

On boot went to network prefs, one interface appeared and received a dhcp address.

Disabled Wireless interface

Gave wired interface a static IP. Internet worked

Shutdown and unplugged for 30 seconds again.

Booted up and the interface said cable unplugged (No network connection)

Rebooted

Disabled 2nd interface in BIOS

Booted OSX, new interface appeared in network prefs, got DHCP, set to static, confirmed connection to the internet.

Shutdown and unplugged for 30 seconds

Booted up and network was still working.

 

I disabled the 2nd interface because I saw the duplicate mac address problem again. So it seems that was my problem. Hopefully things stay working. I don't use the 2nd interface for anything so it's no big deal for me to have it disabled.

 

Thanks for the help!

Link to comment
Share on other sites
eno
eno
Posted
  • Author
Posted

I just posted 0.62.11 which adds multiple IRQ support for optimization mode 0. In theory multiple IRQs should allow the driver to maximize throughput. I have been able to get up to 984 Mbits/sec with netcat using this version.

Link to comment
Share on other sites
Maciek Leja
Maciek Leja
Posted
Posted

Hey Eno,

 

I had that issue with after a while losing connectivity and my switch would give out.

 

I've been playing with Win7 for a few weeks so I gave up temporarily but I saw you came out with a new version.

 

I'm using it right now - it's been like an hour so far (so good) - but suddenly I have an extra ethernet adapter in my preferences tab even though I only have 2 integrated (MCP55). Any ideas how I can check wtf this is?

 

Also, I'm awaitng reply from a guy helping me and explaining the process to move to 10.5.6 from 10.5.5 so hopefully if this kext is working nothing will change with the update.

 

Any ideas?

 

Okay... so I'm 2 hours in using the kextlan.

 

Suddenly I lost connectivity to everything - got a 169 address and my brother who is connected to my swtich also lost connectivity (Windows box). BUT this time instead of restating my PC i just unplugged and plugged the switch back in an got connectivity back.

 

Any ideas wtf this could be? It's a regular linksys 8port switch - is it possible traffic tagged from the Mac makes it shutdown?

Link to comment
Share on other sites
eno
eno
Posted
  • Author
Posted

It sounds like the problem might have something to do with an incompatibility with your switch? Can you tell me the model number? Is the firmware of the switch up to date?

 

Also, do both your ethernet devices have unique MACs that start with 00:?

 

Hey Eno,

 

I had that issue with after a while losing connectivity and my switch would give out.

 

I've been playing with Win7 for a few weeks so I gave up temporarily but I saw you came out with a new version.

 

I'm using it right now - it's been like an hour so far (so good) - but suddenly I have an extra ethernet adapter in my preferences tab even though I only have 2 integrated (MCP55). Any ideas how I can check wtf this is?

 

Also, I'm awaitng reply from a guy helping me and explaining the process to move to 10.5.6 from 10.5.5 so hopefully if this kext is working nothing will change with the update.

 

Any ideas?

 

Okay... so I'm 2 hours in using the kextlan.

 

Suddenly I lost connectivity to everything - got a 169 address and my brother who is connected to my swtich also lost connectivity (Windows box). BUT this time instead of restating my PC i just unplugged and plugged the switch back in an got connectivity back.

 

Any ideas wtf this could be? It's a regular linksys 8port switch - is it possible traffic tagged from the Mac makes it shutdown?

Link to comment
Share on other sites
Maciek Leja
Maciek Leja
Posted
Posted

en0 = 04:4b:80:80:80:04

en1 = 04:4b:80:80:80:03

en2 = has that whole "Ethernet" portion missing in system profiler...

 

After I reset the switch (quick 1 second unplug and plug in) I've been online since then (35 minutes) - almost done with a 2gb download - been going around 700 kB/s (I'm on Comcast so that's pretty good for me lol)

Model: Linksys ezxs8ww - doubt it's the latest firmwire

 

I also have the Linksys wireless router downstairs model: WRT54G2 but that isn't effected when I lose any connectivity.

 

just checked linksys site - there are no firmwire upgrades to this switch. It's 1.0 since the beginning.

 

btw it just crapped out again - unplugged it and plugged it back in and I'm back online right away

Link to comment
Share on other sites
eno
eno
Posted
  • Author
Posted
en0 = 04:4b:80:80:80:04

en1 = 04:4b:80:80:80:03

en2 = has that whole "Ethernet" portion missing in system profiler...

 

After I reset the switch (quick 1 second unplug and plug in) I've been online since then (35 minutes) - almost done with a 2gb download - been going around 700 kB/s (I'm on Comcast so that's pretty good for me lol)

Model: Linksys ezxs8ww - doubt it's the latest firmwire

 

I also have the Linksys wireless router downstairs model: WRT54G2 but that isn't effected when I lose any connectivity.

 

just checked linksys site - there are no firmwire upgrades to this switch. It's 1.0 since the beginning.

 

btw it just crapped out again - unplugged it and plugged it back in and I'm back online right away

 

Huh, you also have an invalid MAC. Can you try turning one of the adapters off in the BIOS? It also might help if you set your device to have a real MAC using ifconfig eth0 hwaddr

 

In the next version (which should be out soon) I will try to detect these bad MACs and create a random MAC.

Link to comment
Share on other sites
Maciek Leja
Maciek Leja
Posted
Posted

Okay - so I just had my first ever kernel panic.

 

I'm still very new to osX - anyway to find out wtf caused it?

I was running itunes/ adium/ photshop cs4 installation at the time...

 

Also, I'll do that right now.

 

I saw something about HPET in this forum. Is there any specific setting for that in my bios I'm supposed to have it on?

Link to comment
Share on other sites
eno
eno
Posted
  • Author
Posted
Okay - so I just had my first ever kernel panic.

 

I'm still very new to osX - anyway to find out wtf caused it?

I was running itunes/ adium/ photshop cs4 installation at the time...

 

Also, I'll do that right now.

 

I saw something about HPET in this forum. Is there any specific setting for that in my bios I'm supposed to have it on?

 

The only way to tell what caused a kernel panic is the kernel backtrace (the crash reporter should provide this to you on the next boot).

Link to comment
Share on other sites
Maciek Leja
Maciek Leja
Posted
Posted

Okay definitely no crash reporter popping up.

 

I restarted my PC - turned off the second port.

 

Boot into my windows installation to see the Mac Address there (turns out it's the same one I told you 04:4B:80:80:80:03)

 

Now when I look in system profiler I still have all 3 ethernet ports but only one has a mac address the other two don't have almost any information about 'em. So en0 and en2 are not supposed to be there.... en1 currently has an ip.

 

Wow, that kext worked to make up a random Mac.

 

en0 - 00:00:80:6c:b3:26

 

The other two ports are still there.... not sure wtf they are but I'll try to download something right now and see how long I can go on this without my switch crapping out.

 

Thanks.

Link to comment
Share on other sites
eno
eno
Posted
  • Author
Posted
hi, eno, I got kernel panic when using your Lan driver 0.62.11n. My Device ID is 0x07dc10de, from a 630i/MCP73 MOBO

 

Do you have a snapshot or the text of the panic? Is forcedeth.kext installed? What distro/kernel are you using?

Link to comment
Share on other sites
eno
eno
Posted
  • Author
Posted
I am not using forcedeth. my system is 10.5.5 ideneb using 9.4 XNU kernel. the screen shot is in attachment. what's wrong?

 

Can you try optimization mode 1? If that doesn't work try setting DisableMSI. Both options are in the Info.plist

 

Try setting the optimization mode first and if any of those options help please send me a dump of only your MMAC device. You can get the dump by running ioreg -w 0 -l -p IODeviceTree -n MMAC

Link to comment
Share on other sites
xander29
xander29
Posted
Posted

Yes eno, that was the question.

@Xander: tienes que eliminar el kext de forcedeth y despues instalar el nforcelan y deberia andar bien. Avisa como te ha salido.

 

@eno: The last (.10) version solved my slowdown problem, thanks a lot!!!

 

 

 

GRACIAS AMIGO ME HE CONSEGUIDO ACA MISMO ESE KEXT LO INSTALE CON EL OSX86 Tools y adivina me reconocio de una la red, ahora mismo tengo internet full, y este post es lo primero q escribo por safari desde mi hackintosh subo el kext para el que lo necesite q lo utilice y tenga su red, a por cierto cuando estaba instalando el leopard, en personalizar no escogi nada para red, despues de tenerlo instalado fue que lo instale con el programa.

Link to comment
Share on other sites
eno
eno
Posted
  • Author
Posted
Hey folks, I was just wondering if anybody had an idea about the upload problem? I tried sending a file through Adium and it produced the same effect.

 

Uploading a random amount (usually a very small amount) causes the driver to go kaput. It doesn't mess up the state of the NIC as I can reload the driver and be back on, but uploading definitely causes problems. (which on a side thought might be related to the torrent issue as well)

 

The cause of this problem is the NIC stops sending IRQs and I think I have solved it. The fix will be in the next revision (0.62.12) which I expect to release tomorrow at the latest (once I finish testing).

Link to comment
Share on other sites
UTK
UTK
Posted
Posted

I've installed the 0.62.11n driver with OSX68Tools, and the PC freezes when i click the 'restart' button on the OSX86Tools. And then if i manualy reset the PC, i get a panic.

So, i restarted in safe mode, removed the driver, and restarts ok.

 

My Mobo is an Gigabyte GA-73vm-s2 (Chipset: NVIDIA® GeForce 7050/nForce 610i - Lan: RTL 8201N)

 

Someone can help me, plz? :)

 

(sorry about the bad english)

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...