On Wed, Jan 20, 2010 at 10:38 PM, Denis Heidtmann <denis.heidtm...@gmail.com> wrote: > > I had previously posted this: > 00:0a.0 Ethernet controller: nVidia Corporation MCP78S [GeForce 8200] > Ethernet (rev a2) > Subsystem: ASUSTeK Computer Inc. Device 82f2 > Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 2300 > Memory at fcf7c000 (32-bit, non-prefetchable) [size=4K] > I/O ports at c880 [size=8] > Memory at fcf7f400 (32-bit, non-prefetchable) [size=256] > Memory at fcf7f000 (32-bit, non-prefetchable) [size=16] > Capabilities: [44] Power Management version 2 > Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ > Queue=0/4 Enable+ > Capabilities: [6c] HyperTransport: MSI Mapping Enable+ Fixed+ > Kernel driver in use: forcedeth > Kernel modules: forcedeth > > This tells me the driver name. It is not clear to me what to do with > this information.
It sounds like you may have a flaky kernel module for that ethernet chip. The command "modinfo forcedeth" will show you the module version. You can check if the motherboard or chipset manufacture has a more recent module available. You will probably need to install the kernel source code and software build tools to compile the new module. I had a similar problem with the Intel e1000 driver for a couple years. The kernel module wouldn't work on my motherboard for some reason. I had a 3com PCI ethernet card in that chassis until Intel provided some better code. Steve D... -- "Every perception is a gamble" Robert Anton Wilson _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
