This became a problem for me on one system (of three) I upgraded to
Hardy. The 'options forcedeth msi=0 msix=0' fix seems to be working on
Hardy. Never had an issue that I am aware of on Gutsy involving
forcedeth.
I seem to be able to reproduce a loss of network (using synaptic, for
example) without the fix in place. Is there some debugger I can run on
this, or is this bug adequately documented already?
Here's lspci -v
00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2)
Subsystem: ASUSTeK Computer Inc. Unknown device 8239
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 10
Memory at fe02a000 (32-bit, non-prefetchable) [size=4K]
I/O ports at b000 [size=8]
Memory at fe029000 (32-bit, non-prefetchable) [size=256]
Memory at fe028000 (32-bit, non-prefetchable) [size=16]
Capabilities: [44] Power Management version 2
Capabilities: [70] MSI-X: Enable- Mask- TabSize=8
Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/3
Enable-
Capabilities: [6c] HyperTransport: MSI Mapping
On an Asus M2N SLi mobo
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/136836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
