Hi Brandon, The key point here for the answer provided to iyou was "Firmware" not "driver"
Two different things. Driver for Linux for example is use to allow the network stack of Linux to use the card based on what the actual card support. Firmware is what actually run on the flash of the card to initialize the card itself an, etc. That's what OpenBSD install when you do a fresh install, but that can't be distributed because of license issue and that you download at install time, not part of the OS. Think about it as a BLOB, not driver. Hope this clarify the answer you got more. Daniel On 9/17/20 6:55 PM, Brandon Woodford wrote: > Should this really be necessary though? The card is listed under the > supported em(4) devices. > > I've found the drivers on Intel's website but only for Linux specific > systems. Not really sure where to go from here... > > On Thu, Sep 17, 2020, at 2:07 PM, Tom Smyth wrote: >> Try >> Getting the intel firmware from the intel download site or >> From your pci card manufacturer... >> >> >> >> >> >> >> >> >> >> On Thursday, 17 September 2020, Brandon Woodford <ive...@norto.dev> wrote: >>> Hello, >>> >>> I've been trying to fix an issue with my Intel I350-T4 PCI Network card >>> not being reported to the OpenBSD 6.7 system during boot. Looking through >>> dmesg, I was not able to find any reference to the card or the em interface >>> name that it should have. I've also tried updating all firmware with >>> fw_update. After that I tried creating a /etc/hostname.em1 file that just >>> has dhcp included in it and ran sh /etc/netstart. Unfortunately, no luck as >>> of yet. I was able to find the boot_config(8) man page that describes a >>> similar issue with the ne(4) driver. I went into the boot configuration and >>> ran: find em and received a response of: em* at pci* dev -1 function -1 >>> flags 0x0. Not sure if that means anything. >>> >>> Quick note: the card does work on a separate system that is not OpenBSD but >>> FreeBSD. >>> >>> Any help in the right direction is appreciated! >>> >>> Thanks. >> >> >> -- >> Kindest regards, >> Tom Smyth.
