Bug #4742
closednfe0 NIC shows no carrier after interface configuration
0%
Description
I am able to use the 2.2.2 memstick image to boot up an asrock ion330 based computer. I am able to install pfsense and perform the first reboot. When the system boots the NIC shows a link light but as soon as interface configuration is complete (even if only assigning the nic to WAN and continuing) nfe0 drops the physical media and ifconfig shows status of (no carrier).
On subsequent reboots the NIC drops it's link to the switch at the "configuring WAN interface" step of the startup process.
Updated by Adrien Carlyle almost 9 years ago
I was able to get the device working properly by manually restoring my alix config.xml to the device. On bootup I was able to get to the web UI but during configuration of the interfaces the NIC exhibits the same behavior.
Updated by Chris Buechler almost 9 years ago
- Category set to Operating System
- Status changed from New to Needs Patch
looks to be a driver issue of some sort that needs to be replicated on stock FreeBSD and reported upstream.
Updated by Adrien Carlyle almost 9 years ago
Is there a way to tell what is being done to the interface when it is being configured? I can install and replicate on stock freebsd.
Updated by Kill Bill almost 9 years ago
There are multiple Ion 330 BIOS updates mentioning "improve LAN compatibility" on the ASUS website. Perhaps start there. (Certainly not a generic issue with all nfe NICs, have a couple of boards with no such issue.)