Re: Intl I350 Network Card Not Found

2020-09-25 Thread Brandon Woodford
On Thu, Sep 17, 2020, at 1:39 PM, Brandon Woodford 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.

Update: I was able to solve this issue. I was using a PCIe 2 card in a PCIe 3 
slot. My motherboard had an option to correct the slot to a previous generation 
of PCIe (for w/e reason it was called Gen1 in the BIOS). I had seen this option 
previously but kept it on auto. All link lights were working for the card 
during this time so I figured it was an OS issue. Turns out I was dead wrong... 
Changing the setting has fixed all the issues, so now the em firmware is loaded 
during boot.


Re: Intl I350 Network Card Not Found

2020-09-18 Thread Brandon Woodford
>> And what was the result?  What's the current output of fw_update -i?
> 
> Installed: intel-firmware-20200508v0 inteldrm-firmware-20181218 
> vmm-firmware-1.11.0p2
> 
>> In the long run I probably can't help you, but if others are to help you you 
>> should include a full dmesg.
> 
> No worries. I've attached my dmesg output to the email.
> 
> Brandon


On Thu, Sep 17, 2020, at 8:59 PM, Greg Thomas wrote:
> On Thu, Sep 17, 2020 at 11:43 AM Brandon Woodford  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.
> 
> And what was the result?  What's the current output of fw_update -i?
>  
>> 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.
> 
> I'm running a different Intel em card but here's what your dmesg would like 
> if it was initialized:
> 
> em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address 
> f0:de:f1:d9:fa:03
> 
> In the long run I probably can't help you, but if others are to help you you 
> should include a full dmesg.
> 
> Greg
>  
OpenBSD 6.7 (GENERIC.MP) #6: Thu Sep  3 14:08:18 MDT 2020

r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16837939200 (16057MB)
avail mem = 16315002880 (15559MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xee840 (26 entries)
bios0: vendor American Megatrends Inc. version "P2.10" date 07/19/2013
bios0: ASRock Z77 Extreme6/TB4
acpi0 at bios0: ACPI 5.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT MCFG AAFT HPET SSDT SSDT SSDT BGRT
acpi0: wakeup devices UAR1(S4) P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) 
USB5(S3) USB6(S3) USB7(S3) RP01(S4) RP02(S4) RP03(S4) RP04(S4) RP05(S4) 
RP06(S4) RP07(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3500.48 MHz, 06-3a-09
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 100MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3500.04 MHz, 06-3a-09
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3500.03 MHz, 06-3a-09
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3500.04 MHz, 06-3a-09
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu3: 256KB 64b/line 8

Re: Intl I350 Network Card Not Found

2020-09-17 Thread Brandon Woodford
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  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.


Intl I350 Network Card Not Found

2020-09-17 Thread Brandon Woodford
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.