![]() | |||||||||||||
Messages in this thread |
foner+x-forcedeth@media.mit.edu wrote:
>So do you (or anyone) have any suggestions for what to do? This is a
>reasonably new motherboard (I don't think it has any new firmware
>versions out yet) and this leaves me dead in the water---all I can do
>at this point is to just try the nVidia drivers and hope they work
>better than forcedeth.
>
I would propose that as the first step: If this fails, then you can try
to get support from NVidia.
From you description it doesn't look like a bug directly in the
forcedeth driver: Perhaps a problem with a shared interrupt, or the vesa
bios uses an area for I/O and the ethernet registers are remapped on top
of the vesa registers.
Could you post lspci -vxx from both before and after loading forcedeth.
Or try bios settings that sound like Plug-N-Play aware OS. Or try ACPI
instead of APM (I've seen a boot log that contains both acpi and apm -
which one do you use? Try to boot with "acpi=off", "pci=noacpi", etc.)
--
Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
| ||||||||||||
| Last update: 2005-03-22 13:03 [from the cache] ©2003-2008 | |||||||||||||