On Mon, Nov 10, 2008 at 8:06 PM, A.J. Werkman@xxxxxxxxxxxx <AJ.Werkman@xxxxxxxxxxxx> wrote:
What does "Fedora can not get control over the biuld in NIC anymore" ? What is the dmesg saying? The logs? lspci -vvv?
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.
What does "Fedora can not get control over the biuld in NIC anymore" ? What is the dmesg saying? The logs? lspci -vvv?
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
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
--
Aioanei Rares
schaiba@xxxxxxxxxxxxxxxxx
"China is a big country, inhabited by many Chinese." --Charles de Gaulle
-- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
