After testing FreeBSD in a VM, I decided I wanted to install it onto my base system, so I burned my 64-bit 10.0RC4 ISO and ran the installer off of it. The installation went smoothly until I got to network configuration. I have an onboard Realtek RTL8111/8168D NIC detected as re0, but the status remained as "no carrier" no matter how many times I unplugged/replugged the cable. I doubt the issue is with this cable, because I've been using it for years and it's never failed me. That said, though, the switch didn't see the device on the other end of the cable, either.
I tried booting into Windows 7, and to my surprise, it doesn't see the cable as plugged in any more, either. What? Did FreeBSD's driver mess up my NIC? I reinstalled the device in Windows, but it still doesn't see the cable as plugged in. I would try testing it on Linux but I wiped the drive I had Linux on to put FreeBSD there.
To summarize:
Also, I tried reinstalling FreeBSD, and if I pressed Ctrl+Shift+F4 and typed
EDIT: I swapped Cat 5 cables with another system, and the cable I was using on my system is working in the second system, while the cable I was using on the second system isn't detected by my system. So it's not the cable, it seems like it's the NIC, which is a drag big time.
I tried booting into Windows 7, and to my surprise, it doesn't see the cable as plugged in any more, either. What? Did FreeBSD's driver mess up my NIC? I reinstalled the device in Windows, but it still doesn't see the cable as plugged in. I would try testing it on Linux but I wiped the drive I had Linux on to put FreeBSD there.
To summarize:
- The NIC was working perfectly.
- I tried to install FreeBSD.
- I couldn't connect using the NIC in FreeBSD (it said no carrier).
- Now Windows and the switch I am running through don't think the cable is connected, either.
Also, I tried reinstalling FreeBSD, and if I pressed Ctrl+Shift+F4 and typed
ifconfig
before going through the installer, the NIC (re0)'s status was active. I'm just confused.EDIT: I swapped Cat 5 cables with another system, and the cable I was using on my system is working in the second system, while the cable I was using on the second system isn't detected by my system. So it's not the cable, it seems like it's the NIC, which is a drag big time.