[DragonFlyBSD - Bug #3038] (Resolved) Intel Ethernet Could not Connect to Network

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Wed May 24 07:12:32 PDT 2017

Issue #3038 has been updated by newnix.

Status changed from New to Resolved

Sorry I didn't get back to you sooner, just rebuilt with the patch, no longer need to set ifconfig_em0="DHCP polling" in /etc/rc.conf, the patch appears to have solved the problem entirely.

Bug #3038: Intel Ethernet Could not Connect to Network

* Author: newnix
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: Latest stable
Upon trying to install DragonFly BSD 4.8 on a new Dell Optiplex 7040, I found that em0 would not receive any DHCPOFFER packets when trying to connect via DHCP and tcpdump found no traffic either after ensuring that the interface was up and active.
While in the IRC chat, it was suggested to run `ifconfig em0 polling` which resolved the issue, it's believed that the problem was with the interrupt not being mapped correctly for the hardware. As suggested, I've attached my verbose dmesg logs as well as the output from pciconf to help in fixing this problem. In the meantime, I've found that adding ifconfig_em0="DHCP npolling" to my /etc/rc.conf has taken care of this problem, allowing me to use my system as normal.

dmesg_verbose.txt - booting with verbose logging enabled, no special settings in /etc/rc.conf regarding em0
dmesg_verbose_dhcp.txt - booting with verbose logging, this time with ifconfig_em0="DHCP" set in /etc/rc.conf

dmesg_verbose.txt (58.3 KB)
dmesg_verbose_dhcp.txt (121 KB)
pciconf.txt (8.83 KB)

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

More information about the Bugs mailing list