Dawid Zamirski schreef:
On Mon, 2008-11-10 at 19:06 +0100, A.J. Werkman@xxxxxxxxxxxx wrote: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.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@xxxxxxxxxxTo unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-listI suppose that your NIC chipset is r8169, if so try:
Yes
su - rmmod r8196 modprobe r8196
This works for me. Thanks.
It should get IP from DHCP after this. I've had exactly the same problem with my friend's PC who has Gigabyte GA-MA790X-DS4 motherboard and after booting into Windows and then back to Fedora 9, his NIC would not get IP from DCHP. I have added rmmod r8196 and modprobe r8696 to /etc/rc.local as workaround until this issue gets fixed in the kernel. See: https://bugzilla.redhat.com/show_bug.cgi?id=438046 https://bugzilla.redhat.com/show_bug.cgi?id=460747 (F10 Blocker)
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
