I agree that a mechanism for detecting functionality with different
values would be superior to the quirk workaround. I added that on the
assumption that this was a one-time problem which was caused by a BIOS
bug on the Asus P5N32-SLI Premium. Since different potentially related
occurrences have su
After looking into the problem, I'm convinced that my problem (with the
P5N32-SLI Premium mobo), is caused by a buggy BIOS. I also have the same
PCI bridge and NIC on another Asus motherboard, where it works
flawlessly (for small and large data transfers). I have submitted a
kernel patch where msi
Thanks for the feedback. I'm primarily trying to find out if this is
P5N32-SLI-specific, so a clarification of the above question is: Are
there anybody (in addition to me) who still experiences the network
problems after upgrading to 2.6.27+ and has other motherboards than the
Asus P5N32-SLI Premiu
I got no suggestions/feedback when posting this question on the netdev-
list, but I have done some experimenting with msi disabling for affected
devices in order to produce a (preliminary) patch. What I would like to
know is if there are other motherboards than the Asus P5N32-SLI Premium
which are
I've tested the current development kernel (2.6.28-rc3) on my computer
(Asus P5N32-SLI Premium motherboard), and the problem is still present.
I can take this to the mailing lists to try to find a reasonable
solution.
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.n
