|
Posting this on behalf of a friend, as I've been trying to help him sort it out to little avail. Problem description: About a week ago, the motherboard's on-board NIC stopped working, always saying the cable was unplugged when it was firmly in place (and tested with different cables). Attempted fixes: A reinstall of the drivers and using the Windows troubleshooter didn't help any, so he picked up a PCI NIC (TP-Link). This also didn't work, but for a different reason. Windows kept spitting out Could not start, Code 10 . I had him boot to a Linux live USB, where the TP-Link NIC kept flicking between trying to get an IP and not connected (other devices are getting DHCP just fine) and didn't see the onboard one. A replacement NIC exhibited the same results. Different cables and ports didn't help. Recent changes: Only the stuff above. -- Operating system: Windows 7 Home Premium 64-bit System specs: GA-970A-UD3 AMD Phenom II X4 945 Radeon HD 5700 12GB RAM, DDR3 Onboard NIC: Realtek PCIe GBE Family Controller PCI NICs: TP-LINK TG-3269 10/100/1000 I have Googled and read the FAQ: Yes
|
#
?
Aug 25, 2015 08:25
|
|
|
|
| # ? Apr 25, 2024 02:10 |
|
|
You can't use PCI Ethernet cards with modern motherboards, they're exclusively meant for old boards without PCI-E slots. Remove the PCI cards, shut the system down, remove the power cord from the back, and press the power button to drain the capacitors. Let it sit for an hour or so, then plug it back in and power it up. This will reset the onboard Ethernet controller that normally remains turned on when the system is powered off or briefly unplugged. If it still doesn't work with the latest drivers from the Realtek website, try with a PCI-E NIC.
|
|
#
?
Aug 25, 2015 17:45
|
|
