[SOLVED] NICs werden nicht erkannt, Intel 82599 nicht auf HCL

[BEHIND-IT]

Hallo Leute,

wir benutzen OPNsense schon seit einiger Zeit - es funktioniert super, danke für die großartige Software, die Dokumentation, die Hilfe in den Foren, die Anleitungen und den Arbeitsaufwand, der damit verbunden ist!

Gestern haben wir einen neuen Stapel von Firewall-Hardware bekommen, 2 x DELL R620 und diese mit OPNsense 20.1, installiert - soweit so gut.

Versions aus dem Dashboard
OPNsense 20.1-amd64
FreeBSD 11.2-RELEASE-p16-HBSD
OpenSSL 1.1.1d 10 Sep 2019

Leider werden unsere 10 GBit/s Netzwerkkarten nicht erkannt:

• Supermicro AOC-STGN-i2S 10Gigabit SFP+ Dual Port basieren auf
• Intel® 82599 10 Gigabit Ethernet Controller

Habe möglichst viel der gefunden Artikel gelesen und probiert, aber leider kam ich hier nicht weiter.
Aus meiner Sicht scheint es so das die Karten, schlichtweg nicht gefunden werden können.

Sie stehen leider auch nicht auf der HCL https://www.freebsd.org/releases/11.2R/hardware.html#ethernet.

dmesg Output

Code: [Select]

root@OPNsense:~ # dmesg
Copyright (c) 2013-2018 The HardenedBSD Project.
Copyright (c) 1992-2018 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.2-RELEASE-p16-HBSD  fc65add89c3(stable/20.1) amd64
FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
VT(vga): resolution 640x480
HardenedBSD: initialize and check features (__HardenedBSD_version 1100056 __FreeBSD_version 1102000).
CPU: Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz (2000.04-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206d7  Family=0x6  Model=0x2d  Stepping=7
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x1fbee3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x1<LAHF>
  Structured Extended Features3=0x9c000400<IBPB,STIBP,SSBD>
  XSAVE Features=0x1<XSAVEOPT>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 34359738368 (32768 MB)
avail memory = 33260380160 (31719 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <DELL   PE_SC3  >
FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs
FreeBSD/SMP: 1 package(s) x 8 core(s) x 2 hardware threads
ioapic1: Changing APIC ID to 1
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 32-55 on motherboard
SMP: AP CPU #1 Launched!
SMP: AP CPU #6 Launched!
SMP: AP CPU #11 Launched!
SMP: AP CPU #5 Launched!
SMP: AP CPU #10 Launched!
SMP: AP CPU #9 Launched!
SMP: AP CPU #8 Launched!
SMP: AP CPU #7 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #4 Launched!
SMP: AP CPU #12 Launched!
SMP: AP CPU #13 Launched!
SMP: AP CPU #15 Launched!
SMP: AP CPU #14 Launched!
SMP: AP CPU #2 Launched!
Timecounter "TSC" frequency 2000041700 Hz quality 1000
wlan: mac acl policy registered
random: entropy device external interface
000.000016 [4213] netmap_init               netmap: loaded module
module_register_init: MOD_LOAD (vesa, 0xffffffff8114aef0, 0) error 19
kbd1 at kbdmux0
nexus0
vtvga0: <VT VGA driver> on motherboard
cryptosoft0: <software crypto> on motherboard
acpi0: <DELL PE_SC3> on motherboard
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
cpu4: <ACPI CPU> on acpi0
cpu5: <ACPI CPU> on acpi0
cpu6: <ACPI CPU> on acpi0
cpu7: <ACPI CPU> on acpi0
cpu8: <ACPI CPU> on acpi0
cpu9: <ACPI CPU> on acpi0
cpu10: <ACPI CPU> on acpi0
cpu11: <ACPI CPU> on acpi0
cpu12: <ACPI CPU> on acpi0
cpu13: <ACPI CPU> on acpi0
cpu14: <ACPI CPU> on acpi0
cpu15: <ACPI CPU> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x7f irq 8 on acpi0
atrtc0: registered as a time-of-day clock, resolution 1.000000s
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x5f irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 350
Event timer "HPET1" frequency 14318180 Hz quality 340
Event timer "HPET2" frequency 14318180 Hz quality 340
Event timer "HPET3" frequency 14318180 Hz quality 340
Event timer "HPET4" frequency 14318180 Hz quality 340
Event timer "HPET5" frequency 14318180 Hz quality 340
Event timer "HPET6" frequency 14318180 Hz quality 340
Event timer "HPET7" frequency 14318180 Hz quality 340
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff numa-domain 0 on acpi0
pci0: <ACPI PCI bus> numa-domain 0 on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 53 at device 1.0 numa-domain 0 on pci0
pci1: <ACPI PCI bus> numa-domain 0 on pcib1
bge0: <Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000> mem 0xd90a0000-0xd90affff,0xd90b0000-0xd90bffff,0xd90c0000-0xd90cffff irq 34 at device 0.0 numa-domain 0 on pci1
bge0: APE FW version: NCSI v1.5.12.0
bge0: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus0: <MII bus> numa-domain 0 on bge0
brgphy0: <BCM5720C 1000BASE-T media interface> PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge0: Using defaults for TSO: 65518/35/2048
bge0: Ethernet address: 90:b1:1c:51:85:32
bge1: <Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000> mem 0xd90d0000-0xd90dffff,0xd90e0000-0xd90effff,0xd90f0000-0xd90fffff irq 36 at device 0.1 numa-domain 0 on pci1
bge1: APE FW version: NCSI v1.5.12.0
bge1: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus1: <MII bus> numa-domain 0 on bge1
brgphy1: <BCM5720C 1000BASE-T media interface> PHY 2 on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge1: Using defaults for TSO: 65518/35/2048
bge1: Ethernet address: 90:b1:1c:51:85:33
pcib2: <ACPI PCI-PCI bridge> irq 53 at device 1.1 numa-domain 0 on pci0
pci2: <ACPI PCI bus> numa-domain 0 on pcib2
bge2: <Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000> mem 0xd91a0000-0xd91affff,0xd91b0000-0xd91bffff,0xd91c0000-0xd91cffff irq 35 at device 0.0 numa-domain 0 on pci2
bge2: APE FW version: NCSI v1.5.12.0
bge2: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus2: <MII bus> numa-domain 0 on bge2
brgphy2: <BCM5720C 1000BASE-T media interface> PHY 1 on miibus2
brgphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge2: Using defaults for TSO: 65518/35/2048
bge2: Ethernet address: 90:b1:1c:51:85:30
bge3: <Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000> mem 0xd91d0000-0xd91dffff,0xd91e0000-0xd91effff,0xd91f0000-0xd91fffff irq 38 at device 0.1 numa-domain 0 on pci2
bge3: APE FW version: NCSI v1.5.12.0
bge3: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus3: <MII bus> numa-domain 0 on bge3
brgphy3: <BCM5720C 1000BASE-T media interface> PHY 2 on miibus3
brgphy3:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge3: Using defaults for TSO: 65518/35/2048
bge3: Ethernet address: 90:b1:1c:51:85:31
pcib3: <ACPI PCI-PCI bridge> irq 53 at device 2.0 numa-domain 0 on pci0
pci3: <ACPI PCI bus> numa-domain 0 on pcib3
pcib4: <ACPI PCI-PCI bridge> irq 53 at device 2.2 numa-domain 0 on pci0
pci4: <ACPI PCI bus> numa-domain 0 on pcib4
mfi0: <Drake Skinny> port 0xfc00-0xfcff mem 0xddffc000-0xddffffff,0xddf80000-0xddfbffff irq 42 at device 0.0 numa-domain 0 on pci4
mfi0: Using MSI
mfi0: Megaraid SAS driver Ver 4.23
mfi0: 364578 (637954864s/0x0020/info) - Shutdown command received from host
mfi0: 364579 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0073/1000/1f51/1028)
mfi0: 364580 (boot + 3s/0x0020/info) - Firmware version 2.121.14-6325
mfi0: 364581 (boot + 5s/0x0020/info) - Package version 20.13.3-0001
mfi0: 364582 (boot + 5s/0x0020/info) - Board Revision A01
mfi0: 364583 (boot + 30s/0x0002/info) - Unexpected sense: Encl PD 20 Path 5a0b10c00059db00, CDB: 1c 01 00 00 20 00, Sense: 6/29/00
mfi0: 364584 (boot + 32s/0x0004/info) - Enclosure PD 20(c None/p1) communication restored
mfi0: 364585 (boot + 32s/0x0002/info) - Inserted: Encl PD 20
mfi0: 364586 (boot + 32s/0x0002/info) - Inserted: PD 20(c None/p1) Info: enclPd=20, scsiType=d, portMap=00, sasAddr=5a0b10c00059db00pcib5: ,0000000000000000
mfi0: 364587 (boot + 32s/0x0002/info) - Inserted: PD 00(e0x20/s0)
<ACPI PCI-PCI bridge> irq mfi0: 53364588 (boot + 32s/0x0002/info) - Inserted: PD 00(e0x20/s0) Info: enclPd=20, scsiType=0, portMap=00, sasAddr=5000c5008948b055,0000000000000000
mfi0: 364589 (boot + 32s/0x0002/info) - Inserted: PD 01(e0x20/s1)
 at device 3.0 numa-domain 0 on pci0
mfi0: 364590 (boot + 32s/0x0002/info) - Inserted: PD 01(e0x20/s1) Info: enclPd=20, scsiType=0, portMap=01, sasAddr=5000c5008961bb0d,pci5: 0000000000000000
mfi0: 364591 (boot + 48s/0x0001/info) - Background Initialization started on VD 00/0
mfi0: 364592 (637954977s/0x0020/info) - Time established as 03/19/20 17:42:57; (48 seconds since power on)
mfi0: 364593 (637955198s/0x0020/info) - Host driver is loaded and operational
<ACPI PCI bus> numa-domain 0 on pcib5
pcib6: <PCI-PCI bridge> irq 16 at device 17.0 numa-domain 0 on pci0
pci6: <PCI bus> numa-domain 0 on pcib6
pci0: <simple comms> at device 22.0 (no driver attached)
pci0: <simple comms> at device 22.1 (no driver attached)
ehci0: <Intel Patsburg USB 2.0 controller> mem 0xdf8fd000-0xdf8fd3ff irq 23 at device 26.0 numa-domain 0 on pci0
usbus0: EHCI version 1.0
usbus0 numa-domain 0 on ehci0
usbus0: 480Mbps High Speed USB v2.0
pcib7: <ACPI PCI-PCI bridge> at device 28.0 numa-domain 0 on pci0
pci7: <ACPI PCI bus> numa-domain 0 on pcib7
pcib8: <ACPI PCI-PCI bridge> irq 19 at device 28.7 numa-domain 0 on pci0
pci8: <ACPI PCI bus> numa-domain 0 on pcib8
pcib9: <PCI-PCI bridge> at device 0.0 numa-domain 0 on pci8
pci9: <PCI bus> numa-domain 0 on pcib9
pcib10: <PCI-PCI bridge> at device 0.0 numa-domain 0 on pci9
pci10: <PCI bus> numa-domain 0 on pcib10
pcib11: <PCI-PCI bridge> at device 0.0 numa-domain 0 on pci10
pci11: <PCI bus> numa-domain 0 on pcib11
vgapci0: <VGA-compatible display> mem 0xd8000000-0xd8ffffff,0xdeffc000-0xdeffffff,0xde000000-0xde7fffff irq 19 at device 0.0 numa-domain 0 on pci11
vgapci0: Boot video device
pcib12: <PCI-PCI bridge> at device 1.0 numa-domain 0 on pci9
pci12: <PCI bus> numa-domain 0 on pcib12
ehci1: <Intel Patsburg USB 2.0 controller> mem 0xdf8fe000-0xdf8fe3ff irq 22 at device 29.0 numa-domain 0 on pci0
usbus1: EHCI version 1.0
usbus1 numa-domain 0 on ehci1
usbus1: 480Mbps High Speed USB v2.0
pcib13: <PCI-PCI bridge> at device 30.0 numa-domain 0 on pci0
pci13: <PCI bus> numa-domain 0 on pcib13
isab0: <PCI-ISA bridge> at device 31.0 numa-domain 0 on pci0
isa0: <ISA bus> numa-domain 0 on isab0
ahci0: <Intel Patsburg AHCI SATA controller> port 0xece8-0xecef,0xecf8-0xecfb,0xecf0-0xecf7,0xecfc-0xecff,0xecc0-0xecdf mem 0xdf8ff000-0xdf8ff7ff irq 20 at device 31.2 numa-domain 0 on pci0
ahci0: AHCI v1.30 with 6 3Gbps ports, Port Multiplier not supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0
ahcich4: <AHCI channel> at channel 4 on ahci0
ahcich5: <AHCI channel> at channel 5 on ahci0
ahciem0: <AHCI enclosure management bridge> on ahci0
pcib14: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
pci14: <ACPI PCI bus> numa-domain 0 on pcib14
pci14: <dasp, performance counters> at device 14.1 (no driver attached)
pci14: <dasp, performance counters> at device 19.1 (no driver attached)
pci14: <dasp, performance counters> at device 19.4 (no driver attached)
pci14: <dasp, performance counters> at device 19.5 (no driver attached)
pcib15: <ACPI Host-PCI bridge> on acpi0
pci15: <ACPI PCI bus> on pcib15
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xec000-0xeffff on isa0
ppc0: cannot reserve I/O port range
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est0 attach returned 6
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est1 attach returned 6
est2: <Enhanced SpeedStep Frequency Control> on cpu2
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est2 attach returned 6
est3: <Enhanced SpeedStep Frequency Control> on cpu3
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est3 attach returned 6
est4: <Enhanced SpeedStep Frequency Control> on cpu4
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est4 attach returned 6
est5: <Enhanced SpeedStep Frequency Control> on cpu5
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est5 attach returned 6
est6: <Enhanced SpeedStep Frequency Control> on cpu6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est6 attach returned 6
est7: <Enhanced SpeedStep Frequency Control> on cpu7
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est7 attach returned 6
est8: <Enhanced SpeedStep Frequency Control> on cpu8
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est8 attach returned 6
est9: <Enhanced SpeedStep Frequency Control> on cpu9
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est9 attach returned 6
est10: <Enhanced SpeedStep Frequency Control> on cpu10
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est10 attach returned 6
est11: <Enhanced SpeedStep Frequency Control> on cpu11
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est11 attach returned 6
est12: <Enhanced SpeedStep Frequency Control> on cpu12
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est12 attach returned 6
est13: <Enhanced SpeedStep Frequency Control> on cpu13
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est13 attach returned 6
est14: <Enhanced SpeedStep Frequency Control> on cpu14
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est14 attach returned 6
est15: <Enhanced SpeedStep Frequency Control> on cpu15
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001800
device_attach: est15 attach returned 6
Timecounters tick every 1.000 msec
mfid0 numa-domain 0 on mfi0
mfid0: 571776MB (1170997248 sectors) RAID volume 'H310RAID1' is optimal
ugen1.1: <Intel EHCI root HUB> at usbus1
ugen0.1: <Intel EHCI root HUB> at usbus0
uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
ses0 at ahciem0 bus 0 scbus6 target 0 lun 0
cd0 at ahcich4 bus 0 scbus4 target 0 lun 0
ses0: <AHCI SGPIO Enclosure 1.00 0001> SEMB S-E-S 2.00 device
ses0: SEMB SES Device
cd0: <TSSTcorp DVD+-RW TS-U633J D150> Removable CD-ROM SCSI device
cd0: Serial Number R8FM6GUC6001KT
cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes)
cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed
random: unblocking device.
Trying to mount root from ufs:/dev/gpt/rootfs [rw]...
uhub1: 2 ports with 2 removable, self powered
uhub0: 2 ports with 2 removable, self powered
ugen1.2: <vendor 0x8087 product 0x0024> at usbus1
uhub2 numa-domain 0 on uhub0
uhub2: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus1
ugen0.2: <vendor 0x8087 product 0x0024> at usbus0
uhub3 numa-domain 0 on uhub1
uhub3: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus0
uhub3: 6 ports with 6 removable, self powered
uhub2: 8 ports with 8 removable, self powered
ugen0.3: <USB USB Keyboard> at usbus0
ukbd0 numa-domain 0 on uhub3
ukbd0: <USB USB Keyboard, class 0/0, rev 1.10/1.10, addr 3> on usbus0
kbd2 at ukbd0
ugen0.4: <no manufacturer Gadget USB HUB> at usbus0
uhub4 numa-domain 0 on uhub3
uhub4: <no manufacturer Gadget USB HUB, class 9/0, rev 2.00/0.00, addr 4> on usbus0
uhub4: 6 ports with 6 removable, self powered
ugen0.5: <Avocent KeyboardMouse Function> at usbus0
ukbd1 numa-domain 0 on uhub4
ukbd1: <Keyboard> on usbus0
kbd3 at ukbd1
ums0 numa-domain 0 on uhub3
ums0: <USB USB Keyboard, class 0/0, rev 1.10/1.10, addr 3> on usbus0
ums0: 3 buttons and [XYZ] coordinates ID=3
ums1 numa-domain 0 on uhub4
ums1: <Mouse> on usbus0
ums1: 3 buttons and [Z] coordinates ID=0
ums2 numa-domain 0 on uhub4
ums2: <Mouse REL> on usbus0
ums2: 3 buttons and [XYZ] coordinates ID=0
bge0: link state changed to DOWN
bge1: link state changed to DOWN
bge2: link state changed to DOWN
bge3: link state changed to DOWN
bge2: link state changed to UP
aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
bge2: link state changed to DOWN
bge2: link state changed to UP
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
ugen0.3: <USB USB Keyboard> at usbus0 (disconnected)
ukbd0: at uhub3, port 4, addr 3 (disconnected)
ukbd0: detached
ums0: at uhub3, port 4, addr 3 (disconnected)
ums0: detached
ugen0.3: <USB USB Keyboard> at usbus0
ukbd0 numa-domain 0 on uhub3
ukbd0: <USB USB Keyboard, class 0/0, rev 1.10/1.10, addr 3> on usbus0
kbd2 at ukbd0
ums0 numa-domain 0 on uhub3
ums0: <USB USB Keyboard, class 0/0, rev 1.10/1.10, addr 3> on usbus0
ums0: 3 buttons and [XYZ] coordinates ID=3
bge1: link state changed to UP
mfi0: 364790 (637967789s/0x0001/info) - Background Initialization completed on VD 00/0
Hat hier jemand eine Idee, kann man diese zum Laufen bringen? Oder sollte ich lieber andere besorgen?
Meine Favoriten wären Chelsio 110-1120-40 PCIexpress 8x Dual port 10Gbps T420-CR Network Card.

Wenn nicht, hat jemand einen Tipp für bezahlbare unterstützte Dual 10 Gbit/s Karten (Marke, Modell) aus der Bucht o.ä.?


Vielen lieben Dank & bleibt gesund

Oliver

[hbc]

Meine Favoriten wären Chelsio 110-1120-40 PCIexpress 8x Dual port 10Gbps T420-CR Network Card.

Und was spricht gegen die T420-CR? Wir haben zwar nur T540 Quad-Ports im Einsatz, aber mit entsprechenden Einträgen in der /boot/loader.conf.local läuft das ohne Probleme:

Code: [Select]

# load Chelsio NIC driver
t5fw_cfg_load="YES"
if_cxgbe_load="YES"

Für die T4XX wäre es dann analog:

Code: [Select]

# load Chelsio NIC driver
t4fw_cfg_load="YES"
if_cxgbe_load="YES"


[BEHIND-IT]

Hi hbc,

danke das du dir die Zeit genommen hast.

Es spricht nur dagegen das wir diese erst kaufen müssen , aber da wir nun wissen das diese dann einwandfrei funktionieren ist das kein allzu großes Hindernis.

Mir ging es auch darum zu zeigen, das wir uns selbst gekümmert haben und nicht einfach blind nach Hilfe rufen.

Vielen lieben Dank & bleib gesund

Oliver

[BEHIND-IT]

Hi hbc,

ich noch mal, hab es nach deinem Tip versucht:

Für die T4XX wäre es dann analog:

Code: [Select]

# load Chelsio NIC driver
t4fw_cfg_load="YES"
if_cxgbe_load="YES"


Hab die Karten T420-CR (110-1120-40 E0 steht auf den Karten) besorgt und folgendes angelegt:

Code: [Select]

root@OPNsense:~ # ls -ahl /boot/loader.conf.local
-rw-r--r--  1 root  wheel    83B Mar 26 17:39 /boot/loader.conf.local

root@OPNsense:~ # cat /boot/loader.conf.local
# 26.03.2020 - OK: load Chelsio NIC driver
t4fw_cfg_load="YES"
if_cxgbe_load="YES"
Leider tauchen auch nach Reboot, einem Kernel Update auf die letzte 20.1.3 und einem Live Boot von USB jeweils keine weiteren Interfaces auf. Hast du noch eine Idee?

Im BIOS sind die 3 PCIe Ports alle aktiviert.

Vielen lieben Dank & bleib gesund

Oliver

[hbc]

Is there any dmesg output, if you load drivers manually on cli:

Code: [Select]

kldload /boot/kernel/t4fw_cfg.ko
If you need TOE then you need to load t4_tom.ko, too.

[BEHIND-IT]

Das hat mir letzendlich geholfen, habe beide Module geladen. / This helped me out finally, i've loaded both modules.

Code: [Select]

kldload /boot/kernel/t4fw_cfg.ko --> Nichts / nothing
kldload /boot/kernel/if_cxgbe.ko --> dmesg Party 8), auf die ich gewartet habe / i've been waiting for this

Jetzt habe ich das noch dauerhaft gemacht mit / now i've fixed it permanently by adding the boot/loader.conf.local with

Code: [Select]

t4fw_cfg_load="YES"
if_cxgbe_load="YES"
t4_tom_load="YES"
Besten Dank / many thanks
Oliver

[franco]

Hallo zusammen,

Kann man übrigens auch unter System: Settings: Tunables hinterlegen.


Grüsse
Franco

[BEHIND-IT]

Moin Franco,

danke dir - eine kurze Rückfrage hätte ich dazu:

Kann man übrigens auch unter System: Settings: Tunables hinterlegen.

Habe mir nach Doku mit sysctl -a eine Liste der möglichen Werte ausgegeben, und danach gesucht, aber ich bin mir nicht sicher ob untenstehendes richtig ist?

Wie ist der Aufbau der Syntax der Tunables?

Code: [Select]

t4fw_cfg_load="YES" --> hw.t4fw.cfg 1
if_cxgbe_load="YES" --> hw.if.cxgbe 1
t4_tom_load="YES" --> hw.t4.tom 1
Für einen weiteren Hinweis wäre ich dir dankbar!

Beste Grüße und eine gesunde Zeit
Oliver

[franco]

Hi Oliver,

Tunables kann beides: sysctl (-a) Werte und Kernel Bootloader Werte. Manches überschneidet sich, aber nicht alles.

"_load" sind z.B. reine Bootloader Werte die das Modul "MODULE_load" laden... Prinzipiell gilt NAME="WERT" also

t4fw_cfg_load -> YES

Die Werte hier haben nichts miteinander zu tun:

t4fw_cfg_load="YES" --> hw.t4fw.cfg 1
etc.


Grüsse
Franco

[franco]

PS: Warum kann Tunables beides? Weil man die Sysctl-Werte schon vor dem Laden des Kernels aktivieren kann. Manche benötigen dies sogar da diese zur Laufzeit nicht mehr gesetzt werden können.