I've attached an ebuild for the kernel module of nvidia's nforce onboard NIC. The NIC is on almost every nForce chipset on the market right now, and while the forcedeth module works, I (and others) find the proprietary driver to be more stable and faster (it will run at 1000baseT, forcedeth is stuck at 100). Not sure where it should be filed. net-misc/nvnet perhaps?
Created attachment 65476 [details] Ebuild for nvnet kernel module.
Comment on attachment 65476 [details] Ebuild for nvnet kernel module. I've only tested this on an amd64 system, but it should work on x86 too. if someone can confirm that it'd be swell.
Since this module was removed from portage in the past, and nvidia are actively contributing to forcedeth at the same time as developing nvnet, I'd prefer that this didn't get added right now. (1000base is supported, but you might have to be running a recent kernel) Still, I'll leave this open for now, assuming it is if some benefit to users :)
*** Bug 102109 has been marked as a duplicate of this bug. ***
but _right_now_ forcedeth on some machine isn't working _at_all_ maybe nvnet removed from portage too fast?
I searched, but I'm unable to find the bug report which you filed about this problem with forcedeth. Can you point me in the right direction? :)
i'm sorry ;( after deep digging, found that this is damn asus acpi problems ;(
WONTFIX. If you really want this, grab it from ViewCVS: http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-misc/nforce-net/?hideattic=0