Jump to content

nForce LAN driver


eno
 Share

740 posts in this topic

Recommended Posts

After a while, USB gone, and I could see the following messages in Console (so exactly the same like with the nForceATA kext I've had before):

nForceLAN: NIC ring full, stalling.

disk1s4 data underrun (My comment: maybe it's the Data partition, where torrent was running.)

(My comment: yes, an empty line, then it is repeated...)

-- The last message repeated 1 time --

(If they are not exactly correct, I was just unable to remember the messages perfectly. :) )

 

It looks like your NIC stops producing interrupts. Are you still using the version I emailed to you? If so can you change UseTimerIRQ to true and let me know if that works any better?

 

I am still confused why turning off the HPET has any effect on your machine when it isn't even coming up in the device tree. Perhaps that is part of the problem??

Link to comment
Share on other sites

Thanks for the input. It appears that matching against any network or bus pci device using the plist (for some reason my ethernet comes up as a bus device) causes problems on some machines. In the next update I will just add every pci id to the Info.plist. To verify this can you try 0.62.8n again but change the IOPCIPrimaryMatch in the Info.plist to match your NIC (remove the 0x000010de&0x0000ffff match).

 

 

 

Cool. Let me know if it fixes your problem.

 

BTW, added a donation link to the first post B) . I always appreciate help.

 

Hi eno,

 

I too am currently testing my modified version of your last beta / pre-Release nForceLAN.kext onboard LAN driver (0.62.7n beta_osx) for nForce MOBOs, which now explicitly includes the nVidia MCP55 Ethernet/Marvell 88E1116 LAN chipset Vendor:Device ID of 10de:0373 in Info.plist (since as you say 0x037210de&0xfffeffff apparently matches both 0x037210de and 0x037310de but the masked IDs don't always match) on my 10.5.6 test system......so far so good with HPET enabled in BIOS......... :D

Link to comment
Share on other sites

I've been working with iPC 10.5.6 distro on an Asus M2N-SLI (nForce 4 MCP) lately and several other in the past. One very vexing issue is getting the on-board ethernet working. So far, nForceLAN_0.62.7.kext seems to actually work ... reliably, even. :)

 

But before trying nForceLAN_0.62.7.kext, I naturally tried the latest, and obstensibly greatest, nForceLAN_0.62.8.kext. According the log data, it seemed to work and was configurable in System Preferences..., just like it should be. But it wouldn't transfer data. Nada.

 

It seems like something was "broken" in the update. ???

Link to comment
Share on other sites

Thanks for the input. It appears that matching against any network or bus pci device using the plist (for some reason my ethernet comes up as a bus device) causes problems on some machines. In the next update I will just add every pci id to the Info.plist. To verify this can you try 0.62.8n again but change the IOPCIPrimaryMatch in the Info.plist to match your NIC (remove the 0x000010de&0x0000ffff match).

 

eno, I took the content of IOPCIPrimaryMatch from 0.62.7n and pasted into 0.62.8n but I have the same result when I load it, and again, no kp/crash report/log of any kind, so I don't know what else to tell you.

Any idea?

Link to comment
Share on other sites

I have been having a lot of trouble with file vault corrupting files when my computer kernel panics (happens a lot when I am working on the driver). From what I can tell sync does not force file vault writes to disk. This problem lost me most of the 0.62.4 source a while ago which is why 0.62.7 is largely based off of 0.61 (the last version I had a clean snapshot of. Why is this important? Well, I reimplemented most of the bug fixes from 0.61 to 0.62.6 but missed a few important ones. I think these bugs are the cause of the network connectivity loss and probably the cpu usage. That said, I expect the next release will fix many of the problems people have been having.

 

I will post 0.62.9 later tonight.

Link to comment
Share on other sites

My Lan working good on Leo4all AMD)) and voodoo kernel install too))) Thanks eno

 

Glad to hear it is working for you now. Not sure why 10.5.5 was crashing though :-/

 

Anyway, I posted 0.62.9n for testing. There may be a few bugs still but I want to see if the latest round of bug fixes helps with any of the connections issues.

Link to comment
Share on other sites

I have been having a lot of trouble with file vault corrupting files when my computer kernel panics (happens a lot when I am working on the driver). From what I can tell sync does not force file vault writes to disk. This problem lost me most of the 0.62.4 source a while ago which is why 0.62.7 is largely based off of 0.61 (the last version I had a clean snapshot of. Why is this important? Well, I reimplemented most of the bug fixes from 0.61 to 0.62.6 but missed a few important ones. I think these bugs are the cause of the network connectivity loss and probably the cpu usage. That said, I expect the next release will fix many of the problems people have been having.

 

I will post 0.62.9 later tonight.

 

I had some kind of timelags after upgrading to 10.5.6. , not so with this new release. Hope its not just a lucky evening, am gonna check during the next days, but actually after one movie wihout hiccups while downloading simultaneously everything at its best! Thanks eno!

Link to comment
Share on other sites

Howdy,

 

first off great work, eno :P unfortunately my card doesn't seem to want to work. it finds the card, and looks like its enabling it but then gives me a self-assigned IP address. the output i get is:

 

nForceLAN: found nVidia MCP77 Ethernet Controller device 10de:0760 with flags 0x001af55b

nForceLAN: Version 0.62.8 starting

nForceLAN: found nForce LAN with MAC: 00:01:2E:25:8B:DD

nForceLAN: Link speed now 10Mbps(duplex = Half, flow control = No), code 0x103e8

nForceLAN: Ethernet address 00:01:2e:25:8b:dd

nForceLAN(en0): Link speed now 100Mbps(duplex = Full, flow control = Yes), code 0x10064.

 

i grabbed the source from the first post and built it myself because the latest prebuilt caused a kernel panic on my machine (im using VoodooXNU 9.5.0 if that means anything)

 

oh, and i tried doing a manual configuration instead of a DHCP connection and it still didn't work.

 

im so close to internet, its just not giving me an ip address!

Link to comment
Share on other sites

Howdy,

 

first off great work, eno :) unfortunately my card doesn't seem to want to work. it finds the card, and looks like its enabling it but then gives me a self-assigned IP address. the output i get is:

 

nForceLAN: found nVidia MCP77 Ethernet Controller device 10de:0760 with flags 0x001af55b

nForceLAN: Version 0.62.8 starting

nForceLAN: found nForce LAN with MAC: 00:01:2E:25:8B:DD

nForceLAN: Link speed now 10Mbps(duplex = Half, flow control = No), code 0x103e8

nForceLAN: Ethernet address 00:01:2e:25:8b:dd

nForceLAN(en0): Link speed now 100Mbps(duplex = Full, flow control = Yes), code 0x10064.

 

i grabbed the source from the first post and built it myself because the latest prebuilt caused a kernel panic on my machine (im using VoodooXNU 9.5.0 if that means anything)

 

oh, and i tried doing a manual configuration instead of a DHCP connection and it still didn't work.

 

im so close to internet, its just not giving me an ip address!

 

Can you send me the kernel panic you got with 0.62.9?

 

Also, can you turn up the log level to 3 with 0.62.8 and send me the output of the driver again?

Link to comment
Share on other sites

Can you send me the kernel panic you got with 0.62.9?

 

Also, can you turn up the log level to 3 with 0.62.8 and send me the output of the driver again?

 

nm about sending me the kernel panic. I found the cause.

 

Try 0.62.10.

Link to comment
Share on other sites

Howdy,

 

first off great work, eno :) unfortunately my card doesn't seem to want to work. it finds the card, and looks like its enabling it but then gives me a self-assigned IP address. the output i get is:

 

nForceLAN: found nVidia MCP77 Ethernet Controller device 10de:0760 with flags 0x001af55b

nForceLAN: Version 0.62.8 starting

nForceLAN: found nForce LAN with MAC: 00:01:2E:25:8B:DD

nForceLAN: Link speed now 10Mbps(duplex = Half, flow control = No), code 0x103e8

nForceLAN: Ethernet address 00:01:2e:25:8b:dd

nForceLAN(en0): Link speed now 100Mbps(duplex = Full, flow control = Yes), code 0x10064.

 

i grabbed the source from the first post and built it myself because the latest prebuilt caused a kernel panic on my machine (im using VoodooXNU 9.5.0 if that means anything)

 

oh, and i tried doing a manual configuration instead of a DHCP connection and it still didn't work.

 

im so close to internet, its just not giving me an ip address!

 

Sounds like you got 0.62.8, grab 0.62.10 instead and try that out.

Link to comment
Share on other sites

0.62.10 claims my wire is unplugged. i tried turning off the computer for 30 seconds and all that jazz, but nothing\

 

 

Also, turning logging to 3 didn't produce anything extra

 

Hmm, now you are not even seeing a link with 0.62.10 but the kernel panic is gone?

 

Resetting the NIC on a laptop may be a little trickier than turning it off for 30 seconds. You might have to remove the battery and potentially the backup battery to get the NIC reset.

 

How did you set the log level? Did you change the value under LogLevel to 3? If you did you should see quite a bit more output in /var/log/system.log

Link to comment
Share on other sites

I having some trouble getting this kext to work properly. I had an older version of it working once upon a time, I think with 10.5.4 or 10.5.2 so I know it's possible. I've tried every version listed on the first page with no success. I'd like to get it working because VirtualBox has networking issues with wireless cards (I'm using wireless at the moment in OSX).

 

In System Prefs, I see my two nics, but both say "Cable Unplugged" and it seems that every time I boot, I have a new interface pops up there as well. I've tried every kext i can find as well as unplugging my PC for 15 seconds and booting up after.

 

My hardware is:

AMD X2 5000+

ASUS M2N32-SLI Deluxe Wireless Edition (I believe the network controller is a Marvel 88E1116. The chipset is nForce 590)

NVIDIA 8800GT 512

etc.

 

I currently have iPC 10.5.6 installed and I'm my built-in Realtek wireless for network access. I had no luck using iAtkos v4a 10.5.4 upgraded to 10.5.5 either.

Link to comment
Share on other sites

I having some trouble getting this kext to work properly. I had an older version of it working once upon a time, I think with 10.5.4 or 10.5.2 so I know it's possible. I've tried every version listed on the first page with no success. I'd like to get it working because VirtualBox has networking issues with wireless cards (I'm using wireless at the moment in OSX).

 

In System Prefs, I see my two nics, but both say "Cable Unplugged" and it seems that every time I boot, I have a new interface pops up there as well. I've tried every kext i can find as well as unplugging my PC for 15 seconds and booting up after.

 

My hardware is:

AMD X2 5000+

ASUS M2N32-SLI Deluxe Wireless Edition (I believe the network controller is a Marvel 88E1116. The chipset is nForce 590)

NVIDIA 8800GT 512

etc.

 

I currently have iPC 10.5.6 installed and I'm my built-in Realtek wireless for network access. I had no luck using iAtkos v4a 10.5.4 upgraded to 10.5.5 either.

 

Your board has the exact same chipset as my GA-M59SLI-S5 (nForce 590SLI MCP55) so it should work. Can you turn up the LogLevel to 2 or 3 and send me the output of the driver (any line starting with nForceLAN: in /var/log/system.log).

Link to comment
Share on other sites

Hello again,

 

Here's the latest output:

 

nForceLAN: setting log verbosity to 3
nForceLAN: enabling Message Signaled Interrupts (MSI)
nForceLAN: setting optimization mode: cpu
nForceLAN: probing...
nForceLAN: found nVidia MCP77 Ethernet Controller device 10de:0760 with flags 0x001af55b
nForceLAN: Version 0.62.10 starting
nForceLAN: found power management capability at 68
nForceLAN: PCI system 0x10DE:0x0760, subsystem 0x19DA:0x0AD4 revision 0xA2 opened.
nForceLAN: mapped from 0xFE02B000 of length 4096.
nForceLAN: found nForce LAN with MAC: 00:01:2E:25:8B:DD.
nForceLAN: taking PHY and NIC out of low power mode
nForceLAN: Link speed now 10Mbps(duplex = Half, flow control = No), code 0x103e8.
nForceLAN: fFound PHY 0x0000:0x0020 at address 1.
nForceLAN: supported media: 10BaseT(half) 10BaseT(full) 100BaseTX(full) 100BaseTX(half)
nForceLAN: reporting max packet size as: 1500
nForceLAN: reporting min packet size as: 1500
nForceLAN: registerWithPolicyMaker: entering ...
nForceLAN(en0): setPowerState: old state: 1, new state: 1
nForceLAN: Ethernet address 00:01:2e:25:8b:dd
nForceLAN(en0): enabling...
nForceLAN(en0): setBufSize/Apple wants 1500 bytes
nForceLAN(en0): setBufSize/We can give them 1500 bytes
nForceLAN(en0): setBufSize/Setting with regards to mtu(1500) -- 1564 bytes
nForceLAN(en0): starting transmit/receive engines
nForceLAN(en0): Network link down.
nForceLAN(en0): setMode (true, false)
nForceLAN(en0): setting multicast list with 0 items
nForceLAN(en0): setMode (false, false)

Link to comment
Share on other sites

Hello again,

 

Here's the latest output:

 

nForceLAN: setting log verbosity to 3
nForceLAN: enabling Message Signaled Interrupts (MSI)
nForceLAN: setting optimization mode: cpu
nForceLAN: probing...
nForceLAN: found nVidia MCP77 Ethernet Controller device 10de:0760 with flags 0x001af55b
nForceLAN: Version 0.62.10 starting
nForceLAN: found power management capability at 68
nForceLAN: PCI system 0x10DE:0x0760, subsystem 0x19DA:0x0AD4 revision 0xA2 opened.
nForceLAN: mapped from 0xFE02B000 of length 4096.
nForceLAN: found nForce LAN with MAC: 00:01:2E:25:8B:DD.
nForceLAN: taking PHY and NIC out of low power mode
nForceLAN: Link speed now 10Mbps(duplex = Half, flow control = No), code 0x103e8.
nForceLAN: fFound PHY 0x0000:0x0020 at address 1.
nForceLAN: supported media: 10BaseT(half) 10BaseT(full) 100BaseTX(full) 100BaseTX(half)
nForceLAN: reporting max packet size as: 1500
nForceLAN: reporting min packet size as: 1500
nForceLAN: registerWithPolicyMaker: entering ...
nForceLAN(en0): setPowerState: old state: 1, new state: 1
nForceLAN: Ethernet address 00:01:2e:25:8b:dd
nForceLAN(en0): enabling...
nForceLAN(en0): setBufSize/Apple wants 1500 bytes
nForceLAN(en0): setBufSize/We can give them 1500 bytes
nForceLAN(en0): setBufSize/Setting with regards to mtu(1500) -- 1564 bytes
nForceLAN(en0): starting transmit/receive engines
nForceLAN(en0): Network link down.
nForceLAN(en0): setMode (true, false)
nForceLAN(en0): setting multicast list with 0 items
nForceLAN(en0): setMode (false, false)

 

nForceLAN finds a 10/100 Realtek PHY and gets a valid MAC address yet it doesn't look like you are getting any interrupts. Try turning off MSI by setting the DisableMSI option in the Info.plist to true. That will force nForceLAN to use legacy interrupts instead. Also, can you post a dump of the MMAC device from your IO registry? You can get the dump by running ioreg -w 0 -l -p IODeviceTree . Just post the MMAC device.

Link to comment
Share on other sites

Your board has the exact same chipset as my GA-M59SLI-S5 (nForce 590SLI MCP55) so it should work. Can you turn up the LogLevel to 2 or 3 and send me the output of the driver (any line starting with nForceLAN: in /var/log/system.log).

 

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.

Link to comment
Share on other sites

Disabling MSI did the trick! :)

 

Also, here's the output you requested:

 

	| +-o MMAC@A  <class IOPCIDevice, registered, matched, active, busy 0, retain 9>
| |   {
| |	 "IOPCIResourced" = Yes
| |	 "IOInterruptControllers" = ("io-apic-0","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController","IOPCIMessagedInterruptController")
| |	 "IOName" = "ethernet"
| |	 "subsystem-id" = <d40a0000>
| |	 "IODeviceMemory" = (({"address"=18446744073676173312,"length"=4096}),{"parent"=({"address"=0,"length"=65536}),"offset"=55296,"length"=8},({"address"=18446744073676169216,"length"=256}),({"address"=18446744073676165120,"length"=16}))
| |	 "class-code" = <00000200>
| |	 "IOPowerManagement" = {"ChildrenPowerState"=2,"CurrentPowerState"=2}
| |	 "revision-id" = <a2000000>
| |	 "IOInterruptSpecifiers" = (<1700000007000000>,<2000000000000100>,<2100000000000100>,<2200000000000100>,<2300000000000100>,<2400000000000100>,<2500000000000100>,<2600000000000100>,<2700000000000100>,<2800000000000100>,<2900000000000100>,<2a00000000000100>,<2b00000000000100>,<2c00000000000100>,<2d00000000000100>,<2e00000000000100>,<2f00000000000100>)
| |	 "assigned-addresses" = <105000820000000000b002fe0000000000100000145000810000000000d80000000000000800
000185000820000000000a002fe00000000000100001c50008200000000009002fe0000000010000
00>
| |	 "built-in" = <00>
| |	 "acpi-device" = "IOACPIPlatformDevice is not serializable"
| |	 "device-id" = <60070000>
| |	 "vendor-id" = <de100000>
| |	 "acpi-path" = "IOACPIPlane:/_SB/PCI0@0/MMAC@a0000"
| |	 "subsystem-vendor-id" = <da190000>
| |	 "name" = "ethernet"
| |	 "reg" = <0050000000000000000000000000000000000000105000020000000000000000000000000010
00014500001000000000000000000000000080000001850000200000000000000000000000000010
001c50000200000000000000000000000010000000>
| |	 "compatible" = <"pci19da,ad4","pci10de,760","pciclass,020000">
| |   }

Link to comment
Share on other sites

Hey, I just ran into a peculiar problem with the driver. After uploading (using ssh, although I haven't tried anything else) a certain amount, which is random each time, the driver seems to just stop working and I have to reload it to regain network access. It happens every time I try, and each time I need to reload the driver to get it back. dmesg doesn't seem to have any unusual output from the driver than what it normally does.

Link to comment
Share on other sites

Hola gracias a todos por sus aportes, quisiera aportarles mi duda me he bajado la version 10.5.5 Ideneb y la instalacion es perfecta me reconoce video,sonido , de hecho todo menos la red, alguien me podria decir que kext debo usar para q me reconozca la red probre con forcedeath y no me ha funcionado.

 

Asus M2N-Sli Deluxe

ATHLON X2 4000+

3 GB DDR2 800mhz

HITACHI 300 GB DD IDE

NVIDIA GeForce 8600 GT (256 MB)

ASUS DRW-1814 BLT SATA

Samnsung SyncMaster 932b Plus

Link to comment
Share on other sites

Hola gracias a todos por sus aportes, quisiera aportarles mi duda me he bajado la version 10.5.5 Ideneb y la instalacion es perfecta me reconoce video,sonido , de hecho todo menos la red, alguien me podria decir que kext debo usar para q me reconozca la red probre con forcedeath y no me ha funcionado.

 

Asus M2N-Sli Deluxe

ATHLON X2 4000+

3 GB DDR2 800mhz

HITACHI 300 GB DD IDE

NVIDIA GeForce 8600 GT (256 MB)

ASUS DRW-1814 BLT SATA

Samnsung SyncMaster 932b Plus

 

Sorry, I can't speak any spanish.

 

From what I can tell (via google translate) you are asking which kext to use with your hardware? The old forcedeth kext will not work with your hardware so remove it from your system and use the nForceLAN kext from this thread.

 

If that was not your question can you write it in english or find someone to translate it to english for you?

Link to comment
Share on other sites

 Share

×
×
  • Create New...