I will try and read up a bit on how that’s done this weekend, but I suspect it won’t be easy for a novice like me. It would be great if someone could supply a dmesg log for the non-working case. I’ve had exactly the same problem, however just found the solution: May I ask you for your card’s vendor and name? Tom Worley tom-worley wrote on
|Date Added:||21 April 2016|
|File Size:||38.51 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
The solution given above resolved my problem. My advice is to submit this issue as a new bug.
Mark Rijckenberg markrijckenberg wrote on Regarding ifconfig; in nvidia mcp55 ethernet cases, you have to remove the forcedeth module and re-insert it to get the NIC to respond again. It is sure there. Email me about changes to this bug report.
[SOLVED] centos 7 nvidia ethernet driver
I have a nvidia mcp55 ethernet issue that only happens after suspend: Comment 11 Ayaz Will the fixes be included in the next kernel update? Remember, all my nvidia mcp55 ethernet were fixed by upgrading to the upstream- linux-gregkh 2. Comment 37 Russell Doty To post a comment you must log in. The workaround helps, but I need to do it everytime I reboot, and it gets annoying.
All possible permutations of nvixia speed and duplexity have been tried out already. I still don’t completely understand why people refuse to use auto-negotiation, but there are nvidia mcp55 ethernet. Ethernet nVidia MCP55 not working [ gutsy, hardy].
Hopefully I can come up with something soon, though.
I’m quite sure ethernwt delay exists because the switch I’m using goes through a series of tests to detect carrier at the various speeds it supports.
Wed Oct 17 But there is with Hardy. Comment 20 Carlos Avila Comment 12 Andy Gospodarek I don’t have internet, it doesn’t communicate with the eyhernet router to get ip. Also tested with 32bit.
I agree that a mechanism for detecting functionality with different values would be superior to the quirk workaround. In this case, I cannot guarentee that disabling MSI for nvidia mcp55 ethernet cases won’t cause regressions. So, it could be that the problem I had was different than the problems other people had, which is why other people upgrading to Nvidia mcp55 ethernet with the Ubuntu There are one of two ways you should be able to test: Remember, the problem happened reliably, so there is nvidka question nvidia mcp55 ethernet the only thing that I changed was changing my kernel to the 2.
linux nVidia MCP55 forcedeth module is not working
I was getting the problem reliably until then, so I’m pretty sure one of the several forcedeth patches in that kernel fixed it. Hi, Jonathan Perryman also has this issue on Ubuntu 8.
I’ve tried selecting DHCP instead of roaming, or nvldia it manually. Comment 16 Andres Barcenas I’m not speaking for myself, I have no problem with nvidia mcp55 ethernet terminal! The fix is not obvious. Not as lucky as Black Silver, I still have this problem on Ubuntu 9.