Passing USB serial through to jail

VeeDubb65

Cadet
Joined
Oct 25, 2020
Messages
4
I'm struggling to figure out if this is a hardware issue, FreeNAS issue, or HomeAssistant issue.

Last week my motherboard died, so I ended up moving my drives to a second-hand chasis. No software changes. Just plunked the drives in the new case and hooked them up to the new board.

I'm running FreeNAS-11.3-U3.2.
The new motherboard is a GIGABYTE ultra-tough socket 1150 micro ATX. The model is not printed on the board as far as I can see, and this was a freebie.
CPU is an i5
RAM is 32GB DDR3 1600 ECC from my old system
8 drives in two arrays, but honestly, it's not a storage problem.

I'm running homeassistant in an iocage jail. Before the motherboard/chasis swap, I had a USB Zigbee dongle that was connected to the host, and the jail was allowed the necessary permissions to mount devfs. Specifically:

- allow_mount
- allow_mount_devfs
- enforce_statfs - set to 0 or 1 (used to be one. I've switched it to 0 while troublehsooting with no effect)
- mount_devfs

The results of dmesg are as follows:

Code:
root@CompanionCube:~ # dmesg
Copyright (c) 1992-2019 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.3-RELEASE-p9 #0 r325575+588899735f7(HEAD): Mon Jun  1 15:04:31 EDT 2020
    root@mp20.tn.ixsystems.com:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64
FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on LLVM 8.0.0)
VT(vga): text 80x25
CPU: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz (3292.45-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x306c3  Family=0x6  Model=0x3c  Stepping=3
  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=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x21<LAHF,ABM>
  Structured Extended Features=0x2fbb<FSGSBASE,TSCADJ,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,NFPUSG>
  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 = 33181011968 (31643 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <ALASKA A M I>
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
ioapic0 <Version 2.0> irqs 0-23 on motherboard
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #3 Launched!
Timecounter "TSC-low" frequency 1646224866 Hz quality 1000
random: entropy device external interface
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
kbd1 at kbdmux0
mlx5en: Mellanox Ethernet driver 3.5.1 (April 2019)
nexus0
vtvga0: <VT VGA driver> on motherboard
cryptosoft0: <software crypto> on motherboard
aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
padlock0: No ACE support.
acpi0: <ALASKA A M I> 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
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 550
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
Event timer "HPET3" frequency 14318180 Hz quality 440
Event timer "HPET4" frequency 14318180 Hz quality 440
atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
atrtc0: Warning: Couldn't map I/O.
atrtc0: registered as a time-of-day clock, resolution 1.000000s
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pcib0: _OSC returned error 0x10
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
mps0: <Avago Technologies (LSI) SAS2008> port 0xe000-0xe0ff mem 0xf7dc0000-0xf7dc3fff,0xf7d80000-0xf7dbffff irq 16 at device 0.0 on pci1
mps0: Firmware: 20.00.07.00, Driver: 21.02.00.00-fbsd
mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
vgapci0: <VGA-compatible display> port 0xf000-0xf03f mem 0xf7800000-0xf7bfffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
vgapci0: Boot video device
pci0: <multimedia, HDA> at device 3.0 (no driver attached)
xhci0: <Intel Lynx Point USB 3.0 controller> mem 0xf7e00000-0xf7e0ffff irq 16 at device 20.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
xhci0: Port routing mask set to 0xffffffff
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
pci0: <simple comms> at device 22.0 (no driver attached)
uart2: <Intel Lynx Point KT Controller> port 0xf0c0-0xf0c7 mem 0xf7e1d000-0xf7e1dfff irq 19 at device 22.3 on pci0
ehci0: <Intel Lynx Point USB 2.0 controller USB-B> mem 0xf7e1c000-0xf7e1c3ff irq 16 at device 26.0 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci0
usbus1: 480Mbps High Speed USB v2.0
pci0: <multimedia, HDA> at device 27.0 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> irq 18 at device 28.2 on pci0
pci3: <ACPI PCI bus> on pcib3
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xd000-0xd0ff mem 0xf7c00000-0xf7c00fff,0xf0000000-0xf0003fff irq 18 at device 0.0 on pci3
re0: Using 1 MSI-X message
re0: Chip rev. 0x2c800000
re0: MAC rev. 0x00100000
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
re0: Using defaults for TSO: 65518/35/2048
re0: Ethernet address: fc:aa:14:7f:21:05
pcib4: <ACPI PCI-PCI bridge> irq 19 at device 28.3 on pci0
pci4: <ACPI PCI bus> on pcib4
ehci1: <Intel Lynx Point USB 2.0 controller USB-A> mem 0xf7e1b000-0xf7e1b3ff irq 23 at device 29.0 on pci0
usbus2: EHCI version 1.0
usbus2 on ehci1
usbus2: 480Mbps High Speed USB v2.0
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
ahci0: <Intel Lynx Point AHCI SATA controller> port 0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem 0xf7e1a000-0xf7e1a7ff irq 19 at device 31.2 on pci0
ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahciem0: <AHCI enclosure management bridge> on ahci0
acpi_button0: <Power Button> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_tz1: <Thermal Zone> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
ichwd0: <Intel Lynx Point watchdog timer> on isa0
ichwd0: ICH WDT present but disabled in BIOS or hardware
device_attach: ichwd0 attach returned 6
ichwd0: <Intel Lynx Point watchdog timer> at port 0x1830-0x1837,0x1860-0x187f on isa0
ichwd0: ICH WDT present but disabled in BIOS or hardware
device_attach: ichwd0 attach returned 6
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
est2: <Enhanced SpeedStep Frequency Control> on cpu2
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
est3: <Enhanced SpeedStep Frequency Control> on cpu3
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 1.000 msec
freenas_sysctl: adding account.
freenas_sysctl: adding directoryservice.
freenas_sysctl: adding middlewared.
freenas_sysctl: adding network.
freenas_sysctl: adding services.
ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
ugen1.1: <Intel EHCI root HUB> at usbus1
ugen2.1: <Intel EHCI root HUB> at usbus2
ugen0.1: <0x8086 XHCI root HUB> at usbus0
uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
uhub1: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
uhub2: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
mps0: SAS Address for SATA device = 3c3b592f8b855143
mps0: SAS Address for SATA device = 403b592f83924a4a
mps0: SAS Address for SATA device = 7b856c1499c6ca92
mps0: SAS Address for SATA device = db86631499c7caa5
mps0: SAS Address for SATA device = db89842490b8dc94
mps0: SAS Address for SATA device = 75727d2490b8dbb5
mps0: SAS Address for SATA device = 727c7d2690b8dbaa
mps0: SAS Address for SATA device = 61835b2690b8dbaa
mps0: SAS Address from SATA device = 3c3b592f8b855143
mps0: SAS Address from SATA device = 403b592f83924a4a
mps0: SAS Address from SATA device = 7b856c1499c6ca92
mps0: SAS Address from SATA device = db86631499c7caa5
mps0: SAS Address from SATA device = db89842490b8dc94
mps0: SAS Address from SATA device = 75727d2490b8dbb5
mps0: SAS Address from SATA device = 727c7d2690b8dbaa
mps0: SAS Address from SATA device = 61835b2690b8dbaa
uhub2: 2 ports with 2 removable, self powered
uhub0: 2 ports with 2 removable, self powered
uhub1: 21 ports with 21 removable, self powered
ugen0.2: <American Power Conversion Back-UPS XS 1500G FW866.L8 .D USB FWL8> at usbus0
ugen1.2: <vendor 0x8087 product 0x8008> at usbus1
uhub3 on uhub0
uhub3: <vendor 0x8087 product 0x8008, class 9/0, rev 2.00/0.05, addr 2> on usbus1
ugen2.2: <vendor 0x8087 product 0x8000> at usbus2
uhub4 on uhub2
uhub4: <vendor 0x8087 product 0x8000, class 9/0, rev 2.00/0.05, addr 2> on usbus2
uhub4: 6 ports with 6 removable, self powered
uhub3: 6 ports with 6 removable, self powered
ses0 at ahciem0 bus 0 scbus2 target 0 lun 0
ses0: <AHCI SGPIO Enclosure 2.00 0001> SEMB S-E-S 2.00 device
ses0: SEMB SES Device
ada0 at ahcich0 bus 0 scbus1 target 0 lun 0
ada0: <ADATA SP600 2.9> ACS-2 ATA SATA 3.x device
ada0: Serial Number 2E4420004780
ada0: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 30533MB (62533296 512 byte sectors)
ses0: ada0 in 'Slot 00', SATA Slot: scbus1 target 0
da2 at mps0 bus 0 scbus0 target 21 lun 0
da2: <ATA Hitachi HUA72302 A840> Fixed Direct Access SPC-4 SCSI device
da2: Serial Number YFH8PUAA           
da2: 600.000MB/s transfers
da2: Command Queueing enabled
da2: 1907729MB (3907029168 512 byte sectors)
da3 at mps0 bus 0 scbus0 target 22 lun 0
da3: <ATA Hitachi HUA72302 A840> Fixed Direct Access SPC-4 SCSI device
da3: Serial Number YGHK0V8A           
da3: 600.000MB/s transfers
da3: Command Queueing enabled
da3: 1907729MB (3907029168 512 byte sectors)
da4 at mps0 bus 0 scbus0 target 23 lun 0
da4: <ATA Hitachi HUS72403 A5F0> Fixed Direct Access SPC-4 SCSI device
da4: Serial Number P8H60XYP           
da4: 600.000MB/s transfers
da4: Command Queueing enabled
da4: 2861588MB (5860533168 512 byte sectors)
da7 at mps0 bus 0 scbus0 target 26 lun 0
da7: <ATA Hitachi HUS72403 A5F0> Fixed Direct Access SPC-4 SCSI device
da7: Serial Number P8GL6R0R           
da7: 600.000MB/s transfers
da7: Command Queueing enabled
da7: 2861588MB (5860533168 512 byte sectors)
da5 at mps0 bus 0 scbus0 target 24 lun 0
da5: <ATA Hitachi HUS72403 A5F0> Fixed Direct Access SPC-4 SCSI device
da5: Serial Number P8GWJARP           
da5: 600.000MB/s transfers
da5: Command Queueing enabled
da5: 2861588MB (5860533168 512 byte sectors)
da6 at mps0 bus 0 scbus0 target 25 lun 0
da6: <ATA Hitachi HUS72403 A5F0> Fixed Direct Access SPC-4 SCSI device
da6: Serial Number P8GLGKRR           
da6: 600.000MB/s transfers
da6: Command Queueing enabled
da6: 2861588MB (5860533168 512 byte sectors)
random: unblocking device.
Trying to mount root from zfs:freenas-boot/ROOT/11.3-U3.2 []...
da1 at mps0 bus 0 scbus0 target 20 lun 0
da1: <ATA ST3000DM001-9YN1 CC9E> Fixed Direct Access SPC-4 SCSI device
da1: Serial Number W1F0JWEL
da1: 600.000MB/s transfers
da1: Command Queueing enabled
da1: 2861588MB (5860533168 512 byte sectors)
da1: quirks=0x8<4K>
da0 at mps0 bus 0 scbus0 target 19 lun 0
da0: <ATA ST3000DM001-9YN1 CC9F> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number S1F0RJLE
da0: 600.000MB/s transfers
da0: Command Queueing enabled
da0: 2861588MB (5860533168 512 byte sectors)
da0: quirks=0x8<4K>
lo0: link state changed to UP
re0: link state changed to UP
hwpmc: SOFT/16/64/0x67<INT,USR,SYS,REA,WRI> TSC/1/64/0x20<REA> IAP/8/48/0x3ff<INT,USR,SYS,EDG,THR,REA,WRI,INV,QUA,PRC> IAF/3/48/0x67<INT,USR,SYS,REA,WRI> UCP/8/48/0x3f8<EDG,THR,REA,WRI,INV,QUA,PRC> UCF/1/48/0x60<REA,WRI>
GEOM_MIRROR: Device mirror/swap0 launched (2/2).
GEOM_MIRROR: Device mirror/swap1 launched (2/2).
GEOM_MIRROR: Device mirror/swap2 launched (2/2).
GEOM_MIRROR: Device mirror/swap3 launched (2/2).
GEOM_ELI: Device mirror/swap0.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:     Crypto: hardware
GEOM_ELI: Device mirror/swap1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:     Crypto: hardware
GEOM_ELI: Device mirror/swap2.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:     Crypto: hardware
GEOM_ELI: Device mirror/swap3.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:     Crypto: hardware
re0: link state changed to DOWN
CPU: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz (3292.45-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x306c3  Family=0x6  Model=0x3c  Stepping=3
  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=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x21<LAHF,ABM>
  Structured Extended Features=0x27ab<FSGSBASE,TSCADJ,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,NFPUSG>
  Structured Extended Features3=0x9c000400<MD_CLEAR,IBPB,STIBP,L1DFL,SSBD>
  XSAVE Features=0x1<XSAVEOPT>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
nfsd: can't register svc name
re0: link state changed to UP
tap0: Ethernet address: 00:bd:56:fe:f7:00
bridge0: Ethernet address: 02:67:05:b3:fa:00
tap0: promiscuous mode enabled
bridge0: link state changed to DOWN
re0: promiscuous mode enabled
re0: link state changed to DOWN
tap0: link state changed to UP
bridge0: link state changed to UP
epair0a: Ethernet address: 02:3d:d0:00:05:0a
epair0b: Ethernet address: 02:c2:75:00:06:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: changing name to 'vnet0.1'
re0: link state changed to UP
vnet0.1: promiscuous mode enabled
lo0: link state changed to UP
epair1a: Ethernet address: 02:3d:d0:00:06:0a
epair1b: Ethernet address: 02:c2:75:00:07:0b
epair1a: link state changed to UP
epair1b: link state changed to UP
epair1a: changing name to 'vnet0.2'
epair1b: changing name to 'epair0b'
vnet0.2: promiscuous mode enabled
lo0: link state changed to UP
epair2a: Ethernet address: 02:3d:d0:00:07:0a
epair2b: Ethernet address: 02:c2:75:00:08:0b
epair2a: link state changed to UP
epair2b: link state changed to UP
epair2a: changing name to 'vnet0.3'
epair2b: changing name to 'epair0b'
vnet0.3: promiscuous mode enabled
lo0: link state changed to UP
epair3a: Ethernet address: 02:3d:d0:00:08:0a
epair3b: Ethernet address: 02:c2:75:00:09:0b
epair3a: link state changed to UP
epair3b: link state changed to UP
epair3a: changing name to 'vnet0.4'
epair3b: changing name to 'epair0b'
vnet0.4: promiscuous mode enabled
lo0: link state changed to UP
tun0: link state changed to UP
tun0: link state changed to DOWN
tun0: link state changed to UP
ugen0.3: <dresden elektronik ingenieurtechnik GmbH ConBee II> at usbus0
umodem0 on uhub1
umodem0: <dresden elektronik ingenieurtechnik GmbH ConBee II, class 2/0, rev 2.01/1.00, addr 2> on usbus0
umodem0: data interface 1, has CM over data, has no break
ugen0.3: <dresden elektronik ingenieurtechnik GmbH ConBee II> at usbus0 (disconnected)
umodem0: at uhub1, port 6, addr 2 (disconnected)
umodem0: detached
ugen0.3: <dresden elektronik ingenieurtechnik GmbH ConBee II> at usbus0
umodem0 on uhub1
umodem0: <dresden elektronik ingenieurtechnik GmbH ConBee II, class 2/0, rev 2.01/1.00, addr 3> on usbus0
umodem0: data interface 1, has CM over data, has no break
tun0: link state changed to DOWN
tun0: link state changed to UP
tun0: link state changed to DOWN
tun0: link state changed to UP
tun0: link state changed to DOWN
tun0: link state changed to UP
tun0: link state changed to DOWN
tun0: link state changed to UP
tun0: link state changed to DOWN
tun0: link state changed to UP
tun0: link state changed to DOWN
tun0: link state changed to UP


You can pretty safely ignore tun0 flapping. I know what that's about, and haven't dealt with that jail yet.

The USB device I'm dealing with is "dresden elektronik ingenieurtechnik GmbH ConBee II"

I'm confused because the device is really /dev/cuaU0 but I don't see that here at all. Instead I see ugen0.3 and umodem0. With that device plugged in, I see the following related devices in /dev/

root@CompanionCube:~ # ls /dev/cu*
/dev/cuaU0 /dev/cuaU0.lock /dev/cuau2.init
/dev/cuaU0.init /dev/cuau2 /dev/cuau2.lock

/dec/cuau2 is there where this dongle is connected or not. No idea what it is.

From the terminal, I can see both of those devices in /dev/, so they're passing through. However, the device appears to be non-functional in the jail, and I'm honestly not sure where to go.

Somewhere along the line I got it to work briefly (so I know the hardware works, but I had made numerous manual changes to config files on the host, and apparently not taken good notes.

If anybody has any thoughts, I'm all ears.
 

VeeDubb65

Cadet
Joined
Oct 25, 2020
Messages
4
I've narrowed this down further, and I think it's a FreeNAS issue.

The .init and .lock files for /dev/cuaU0 are there, even before the jail starts up, so something on the system is creating those files and locking the device.

Anybody know how to determine what is locking the device?
 

VeeDubb65

Cadet
Joined
Oct 25, 2020
Messages
4
Moving it to a USB 3.0 port (even though it's a 2.0 device) appears to have at least worked around the problem, if not completely fixed it.
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,776
Nobody is locking the device. The .init and .lock devices are part of the regular FreeBSD terminal/modem interface. A process can use the .init device to set particular stty() parameters that are inherited when another process uses open() on the regular device, The .lock device can be used to lock those parameters, so the subsequent process cannot change them.

It's an API to hardwire a certain configuration to a serial port. The mere presence of .lock does not imply that anything is locked.
 

VeeDubb65

Cadet
Joined
Oct 25, 2020
Messages
4
Nobody is locking the device. The .init and .lock devices are part of the regular FreeBSD terminal/modem interface. A process can use the .init device to set particular stty() parameters that are inherited when another process uses open() on the regular device, The .lock device can be used to lock those parameters, so the subsequent process cannot change them.

It's an API to hardwire a certain configuration to a serial port. The mere presence of .lock does not imply that anything is locked.

I appreciate the info. In most of the systems I've worked on more extensively, lock files only show up when some process has exclusive control over whatever the lock file points to. But I work with BSD a lot less than Linux or Windows, and I almost never mess with serial anymore, so I had wrongly assumed this was the same for serial devices in BSD.

I do find it both interesting and confusing the combination of symptoms I'm seeing. The dongle works perfectly in the front panel USB 3.0 ports on the case, but not on any of the rear panel ports, and not using a 9-pin header to USB A internal adapter. I went so far as to get an internal adapter that would plug into the 20-pin USB 3 header, unplugged the front panel connector, and plugged the dongle into the same slot. It's as if the dongle (despite looking very normal) is EXTREMELY picky about what physical USB ports it will work in, which isn't something I've really ever run into before.
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,776
lock files only show up when some process has exclusive control over whatever the lock file points to
Of course. Same in FreeBSD. But those go into /var/spool/uucp, IIRC, /var/something for sure. You cannot create regular files in /dev. Look closely at your .lock and .init entries. These are device nodes.
 
Last edited:
Top