<div class="gmail_quote">On Mon, Nov 10, 2008 at 8:06 PM, A.J. <a href="mailto:Werkman@digifarma.nl">Werkman@digifarma.nl</a> <<a href="mailto:AJ.Werkman@digifarma.nl">AJ.Werkman@digifarma.nl</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On both the Asus M2A-VM and M2N-VM DVI motherboard I noticed the following. I have configured the system to dual boot between windows and fedora. When I switch from windows to fedora, fedora can not get control over the build in NIC anymore. So DHCP can not configure the NIC. A software reboot and a hardware reboot don't solve the problem. The only remedy is to fysically disconnect the power cord wait a few seconds and power up directly into fedora again. As soon as windows boots the problem reoccurs. </blockquote><div> What does "Fedora can not get control over the biuld in NIC anymore" ? What is the dmesg saying? The logs? lspci -vvv? </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I saw this too on some other motherboards I don't recall the name of. I tested three M2A-VM boards and found this problem on all three of them. This is 100% reproducible. It looks like Windows leaves the NIC in a state that fedora can't handle. Anyone seen this? Anyone who has a solution to this? Koos. -- fedora-test-list mailing list <a href="mailto:fedora-test-list@redhat.com">fedora-test-list@redhat.com</a> To unsubscribe: <a href="https://www.redhat.com/mailman/listinfo/fedora-test-list" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-test-list</a> </blockquote></div> -- Aioanei Rares <a href="mailto:schaiba@fedoraproject.org">schaiba@fedoraproject.org</a> "China is a big country, inhabited by many Chinese." --Charles de Gaulle