Jump to content

nForce LAN driver


  • Please log in to reply
731 replies to this topic

#101
eno

eno

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 188 posts

Does that mean that we will be able to use vanilla kernel on nvidia with kernel from new MBP nvidia-based?


If you have a MCP79 motherboard there is a possibility you will be able to use a vanilla 10.5.6 kernel.

#102
Volcacius

Volcacius

    InsanelyMac Sage

  • Donators
  • 461 posts
  • Gender:Male
  • Location:BG, Italy
I've an MCP55 motherboard, but i think that if it works on MCP79, it will work also on MPC55 (i mean, vanilla kernel works on any kind of intel chipset like P35, P45, X38, X48 etc)

#103
The Sauce

The Sauce

    InsanelyMac Protégé

  • Members
  • PipPip
  • 67 posts
  • Gender:Male
  • Location:New Britain, CT but NY'er 4Life!
I'm getting an issue that so far, has happened 3 times. I install the nforcelan kext v4 and my internet works beautifully except for the fact that I guess with all the device ID's it seems to assign the first one to make a connection, not the right one. For example, my ehternet is RLT8211BL and the first driver that works is for a 8029 as per Parallels Desktop, I can't upload or sent attachments thru email due to this, and so, I deleted all the device ID's except for the one that belongs to my hardware, and everything was working fine. I logged into myspace, and my connection dropped in mid click, I went to check, everything appeared fine, couldn't connect after a few attempts, so I used my back up air port connection.

I went back to system prefs and now my ethernet says "NOT CONNECTED" which is not true since I haven't changed anything since switching from Ehter to Air, so I restart, still "not connected" I open OSX86tools and reinstall the original nforcelan kext with all the device ID's and still nothing. Any ideas??? I don't want to go do a fresh install because that's just annoying, and I don't want to just go on Air Port because the connection is constantly dropping and I hate running system diags just because I wanna browse.

Please help.

#104
brennenmark

brennenmark

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 2 posts
I am having the same problem as weekender.

My motherboard is also an eVGA nForce 680i SLI and I am having the same problem. All USB devices freeze at random times but always within 5 minutes of boot-up. The device id is 0x037310de.

If i use cpus=1, everything works perfectly. But if i run all 4 cores, it freezes every time.

#105
Snerler

Snerler

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 272 posts
  • Gender:Male
brennenmark, try using the new Voodoo_beta2 kernel.

#106
icedtrip

icedtrip

    InsanelyMac Protégé

  • Members
  • PipPip
  • 67 posts

brennenmark, try using the new Voodoo_beta2 kernel.


As for the Voodoo_beta2 kernel. I played around with it the other night, and although I haven't spent time looking deep into it, the voodoo 9.5.0 kernel wasn't playing nice with the nforcelan connection. I was constantly losing either my network connection or simply network traffic. I'll see if I can play more with it over the next couple days.

#107
scififan68

scififan68

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 151 posts
  • Gender:Male
I'm not sure if this is related or not, but for some reason iTunes crashes when my internet is using my nforce lan(RTL8201N) but it launches if I plug in my usb ethernet. Crash log is attached.

Attached Files



#108
brennenmark

brennenmark

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 2 posts
Snerler, thank you! That worked for me so far.

I had to delete extensions.mkext and boot with -f the first time i booted with voodoo_beta2. Now OS X is running with all 4 cores and onboard LAN is working fine.

Much appreciated!

#109
kozlowski

kozlowski

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 213 posts
  • Gender:Female
  • Location:Greece

I'm not sure if this is related or not, but for some reason iTunes crashes when my internet is using my nforce lan(RTL8201N) but it launches if I plug in my usb ethernet. Crash log is attached.


I have the same LAN, but in your signature you mention that you're using Voodoo 9.5.0 BETA 2.
I think that's the reason.

#110
Hugo Guerreiro

Hugo Guerreiro

    OSX86 Dumb Tester...

  • Members
  • PipPipPip
  • 114 posts
  • Gender:Male
  • Location:Portugal
This thread should get sticky!!!! Now!!!

(What are you waiting for moderator?)

I said NOW!!!!! :(

#111
The Sauce

The Sauce

    InsanelyMac Protégé

  • Members
  • PipPip
  • 67 posts
  • Gender:Male
  • Location:New Britain, CT but NY'er 4Life!
Any ideas on my previous post??

#112
eno

eno

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 188 posts

Any ideas on my previous post??


Are you still having the issue with 0.61.5? Can you send me a copy (via PM) of each line in your /var/log/system.log that begins with nForceLAN:

Also, have you tried other kernels (such as the Voodoo XNU beta 2c)? The latest Voodoo kernel made my system a lot more stable.

#113
phake

phake

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 1 posts
Lan working perfectly on my rig :D
asus m2n-sli deluxe (nforce 570)

just wanna say cheers for the great work

#114
eno

eno

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 188 posts
I strongly recommend the Voodoo XNU Beta 2c kernel for use with nVidia chipsets. My osx86 box now appears to work flawlessly (GA-M59SLI-S5).

Also, check out the new version of nForceLAN (0.62.0n). I added true sleep mode (D3) and added some 88E1011 code from the nVidia 0.62 linux driver. Let me know if there are any problems. One thing to look for is that the MAC address isn't reversed after waking from sleep.

#115
icedtrip

icedtrip

    InsanelyMac Protégé

  • Members
  • PipPip
  • 67 posts

I strongly recommend the Voodoo XNU Beta 2c kernel for use with nVidia chipsets. My osx86 box now appears to work flawlessly (GA-M59SLI-S5).

Also, check out the new version of nForceLAN (0.62.0n). I added true sleep mode (D3) and added some 88E1011 code from the nVidia 0.62 linux driver. Let me know if there are any problems. One thing to look for is that the MAC address isn't reversed after waking from sleep.


Does the 0.62.0n version have multicast issues again like 0.61.4?

My machines are not properly seeing each other again for purposes of screen sharing, bonjour, etc (or if they do, it is brief and trying to connect that way isn't possible).

Also, network seems to drop completely from my Hackintosh when I try copying files from it and my Mac Mini. I still have an IP address, but I can no longer access my internal network nor the internet. A reboot seems to fix things. I have not seen this network drop with simple web/email style activity.

BTW, I am using the Voodoo Beta 2 9.5.0 kernel

#116
eno

eno

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 188 posts

Does the 0.62.0n version have multicast issues again like 0.61.4?

My machines are not properly seeing each other again for purposes of screen sharing, bonjour, etc (or if they do, it is brief and trying to connect that way isn't possible).

Also, network seems to drop completely from my Hackintosh when I try copying files from it and my Mac Mini. I still have an IP address, but I can no longer access my internal network nor the internet. A reboot seems to fix things. I have not seen this network drop with simple web/email style activity.

BTW, I am using the Voodoo Beta 2 9.5.0 kernel


There shouldn't be a multicast issue but there is always a possibility I messed something up since I implemented a new solution to the multicast problem that works with my MCP55.

I will take a look and see what might be going on.

#117
dustobub

dustobub

    InsanelyMac Protégé

  • Members
  • Pip
  • 13 posts
I'm having mixed results with the newest driver 62.0n on my gigabyte ga-73pvm-s2h (Realtek 8211B) using Jas 10.5.4 Client Server, at first when I installed it all was great, my connection at 1000mbit was stable. Then after several hours of usage it would drop, and say that it was connected via DHCP but had a self assigned IP. Apparently this is a somewhat common thing on nforce boards I've read. I reinstalled your kext, and it got it working again after a reboot. This has happened several times and now I can no longer get it working. Any ideas? I have tried the previous driver, but not any others. Would logs help? Thanks.

Dustin

#118
eno

eno

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 188 posts
Good news everybody!

The nvenet.kext that comes with the new Macbook Pro works with the MCP55. It gets the mac address backward but that isn't much of an issue. I only had to add my device id to the plist and remove the PCIClass match. I will see what I can do to post the driver for others to try.

I'm having mixed results with the newest driver 62.0n on my gigabyte ga-73pvm-s2h (Realtek 8211B) using Jas 10.5.4 Client Server, at first when I installed it all was great, my connection at 1000mbit was stable. Then after several hours of usage it would drop, and say that it was connected via DHCP but had a self assigned IP. Apparently this is a somewhat common thing on nforce boards I've read. I reinstalled your kext, and it got it working again after a reboot. This has happened several times and now I can no longer get it working. Any ideas? I have tried the previous driver, but not any others. Would logs help? Thanks.

Dustin


If there are any interesting messages being printed to /var/log/system.log please send them to me.

Which kernel are you using? I find that nForce boards work best with the Voodoo XNU kernel.

#119
thefoul

thefoul

    InsanelyMac Protégé

  • Members
  • PipPip
  • 83 posts
  • Gender:Male
  • Location:Rome, Italy
Hi eno! Thank you for the effort in making your driver available.

My config:
iDeneb 10.5.5
Asus P5N32-E SLI Plus
Intel Q6600 + 4GB Ram
2SATA TSST Corp DVD burners
1SATA HD 500 GB

Following your instructions, I've substituted the forcedeth.kext with your nForceLan.Kext (version 0.62.0n alpha_osx) and...the vendor + device ids immediately popped-up in both Network Utility and Network Preferences!

My issue: as soon as I started using the internet connection the system got frozen (USB peripherals like keyboard and mouse stopped working, etc...)...hence I've disabled the Nvidia Lan from BIOS.

We got so close with it that I don't wanna stop trying right now...
Any idea? Anything I can try with?

#120
weekender

weekender

    InsanelyMac Protégé

  • Members
  • Pip
  • 49 posts

Hi eno! Thank you for the effort in making your driver available.

My config:
iDeneb 10.5.5
Asus P5N32-E SLI Plus
Intel Q6600 + 4GB Ram
2SATA TSST Corp DVD burners
1SATA HD 500 GB

Following your instructions, I've substituted the forcedeth.kext with your nForceLan.Kext (version 0.62.0n alpha_osx) and...the vendor + device ids immediately popped-up in both Network Utility and Network Preferences!

My issue: as soon as I started using the internet connection the system got frozen (USB peripherals like keyboard and mouse stopped working, etc...)...hence I've disabled the Nvidia Lan from BIOS.

We got so close with it that I don't wanna stop trying right now...
Any idea? Anything I can try with?


What kernel are you using? Try the Voodoo kernel (link in my sig) as Eno suggests. It might solve your problem. It didn't solve it for me though but it did for some people so just try it.
I'm just waiting for that new driver that is delivered with the new macbooks.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy