I picked up one of these little boxes on eBay for what I considered a reasonable gamble price; I had seen some for sale with OPNsense already installed, and so I figured I could figure out how to re-purpose an essentially e-waste item by installing it myself if I got my hands on one.
They've got great specs- 120GB NvME SSD, 16GB ECC RAM, Quad Core Intel Atom C3558 2.20 GHz CPU with AES-NI Crypto Capability, (6) 10/100/1000 Intel Gigabit Ethernet Ports, (2) USB ports, (1) Console port.
The good news is, I was able to install OPNsense to a spare NvME I had laying around which I swapped into the machine.
The bad news is, the unit reboots exactly every 10 minutes, which I presume to be some sort of manufacturer failsafe to prevent unauthorized or unlicensed use.
The serial console on the unit runs at 9600 baud with the default OS, and there is an option to enter the BIOS, but the BIOS is password protected. Digging around the internet yields no useful information for the password, and 'Silverpeak123' does not work (although the OS username and password is 'admin' and 'admin').
Does anyone have any experience with, or advice for re-purposing these boxes?
I have no useful info beside that I love that kind of stuff :) ... if the model of the motherboard is known, maybe it's possible to flash a vendor neutral BIOS ... if you got the time, nerves and chip reader/writer.
Is it a Lanner NCA-153 (https://www.lannerinc.com/products/telecom-datacenter-appliances/vcpe-ucpe-platforms/nca-1513) based device, with the console port left of the two USB ports (Silver Peak Hardware Reference (https://www.silver-peak.com/sites/default/files/userdocs/hardware_reference_guide_rev-j.pdf), EC-XS PN 200889)? Or the model with the console port above the two USB ports, same reference PDF, Silver Peak EX-CS PN 201571 (probably Lanner as well)?
And regarding the reboot, it's usually a watchdog and I assume it can be stopped, don't know yet how (regarding a different Silver Peak appliance and OpenWRT Silver Peak FW-7551A-SV1 (https://forum.openwrt.org/t/silver-peak-fw-7551a-sv1-almost/163479/18))
Quote from: patient0 on March 15, 2025, 08:29:49 AMI have no useful info beside that I love that kind of stuff :) ... if the model of the motherboard is known, maybe it's possible to flash a vendor neutral BIOS ...
Thank you so much for your response!
It seems to be based on Advantech hardware (FWA-ASP1012). The motherboard silkscreen says NAMB-SP1012MB Rev.A103-1
Quote..if you got the time, nerves and chip reader/writer.
I can make the time, I have the nerves...no chip reader at this time, but I could pick one up on a recommendation...but do I have the brains?? Doubtful.
QuoteIs it a Lanner NCA-153 (https://www.lannerinc.com/products/telecom-datacenter-appliances/vcpe-ucpe-platforms/nca-1513) based device, with the console port left of the two USB ports (Silver Peak Hardware Reference (https://www.silver-peak.com/sites/default/files/userdocs/hardware_reference_guide_rev-j.pdf), EC-XS PN 200889)? Or the model with the console port above the two USB ports, same reference PDF, Silver Peak EX-CS PN 201571 (probably Lanner as well)?
Here (https://www.ebay.com/itm/326442364404?mkcid=16&mkevt=1&mkrid=711-127632-2357-0&ssspo=zWSzTHz-RVO&sssrc=4429486&ssuid=eatLJHzWSTa&var=&widget_ver=artemis&media=COPY) is a link to an identical unit, with OPNsense installed that sold on eBay. (You need to scroll down to the bottom to see the listing). The Console is above the USB ports.
QuoteAnd regarding the reboot, it's usually a watchdog and I assume it can be stopped, don't know yet how (regarding a different Silver Peak appliance and OpenWRT Silver Peak FW-7551A-SV1 (https://forum.openwrt.org/t/silver-peak-fw-7551a-sv1-almost/163479/18))
I do recognize the console output as nearly identical, but the hardware part numbers do not seem to line up..mine is labeled as an Advantech motherboard, NAMB-SP1012MB..
QuoteI can make the time, I have the nerves...no chip reader at this time, but I could pick one up on a recommendation...but do I have the brains?? Doubtful.
It's been a few year for me, too. But you could try to read the BIOS into a file with flashrom -r <where to write the BIOS file to> for a start. Maybe a scan for strings of the BIOS shows some potential passwords. I have never decoded one, maybe someone else here did.
Btw, what password have you already tried? Like SilverPeak, Silverpeak, SilverPeak!, Silverpeak! ? In the other *sense forum there is a thread about WatchGuard and the BIOS password was their brand name + a '!'. You never know.
And have you tried removing the BIOS battery to see if the password gets reset/delete if you remove it for <insert some time frame>? It's probably backed into the BIOS and will survive the removal of the battery. But you never know
QuoteHere is a link to an identical unit, with OPNsense installed that sold on eBay. (You need to scroll down to the bottom to see the listing). The Console is above the USB ports.
Are the screenshots correct and you got ix port, that's the 10G intel driver.
Quote from: patient0 on March 15, 2025, 07:07:36 PM..what password have you already tried? Like SilverPeak, Silverpeak, SilverPeak!, Silverpeak! ? In the other *sense forum there is a thread about WatchGuard and the BIOS password was their brand name + a '!'. You never know.
And have you tried removing the BIOS battery to see if the password gets reset/delete if you remove it for <insert some time frame>? It's probably backed into the BIOS and will survive the removal of the battery. But you never know
I have tried Silverpeak123, which I found in a manual somewhere deep on the web. I will try some of the others you suggested.
I have removed the battery and cleared the CMOS via jumper many times, yes. By doing so, the unit went through a long power cycle and I was then able to boot to USB and install OPNsense to the spare SSD I installed.
QuoteAre the screenshots correct and you got ix port, that's the 10G intel driver.
Yeah, Intel ix on the LAN and WAN.
It just works.. 10 minutes at a time :P
Regarding the watchdog: Thread on the other *sense forum Silver Peak 7551a-sv1 - watchdog timer reset (https://forum.netgate.com/topic/185970/watchdog-timer-reset-problem). The board got a C2000 processor but the basic infos are still relevant. According to the thread there usually are two watchdogs, one in the chipset and one in the superio.
You would load the watchdog driver by adding it to the loader.conf.local (or do it manually, kldload wbwd.ko). Loading the module works on 25.1.
echo 'wbwd_load="YES"' >> /boot/loader.conf.local
After the reboot you should see something like the following (from the mentioned thread) in dmseg (I guess the lines would start with 'superio' and 'wbwd', after that maybe wildly different):
wbwd0: <Winbond 83627DHG-P (0xb0/0x73) Watchdog Timer> at WDT ldn 0x08 on superio0
wbwd0: Before watchdog attach: Watchdog enabled. Scaling by 60s, timer at 12 (<=720s left). CRF5 0x0a CRF7 0x00
For OT the loading of the wbwd.ko itself didn't solve it, only when unloading the driver did it stop resetting.
root@EventHorizon:~ # cat /boot/loader.conf.local
wbwd_load="YES"
And, after reboot:
root@EventHorizon:~ # kldstat | grep -i wbwd
7 1 0xffffffff82233000 4570 wbwd.ko
root@EventHorizon:~ # dmesg | grep -i watchdog
root@EventHorizon:~ # dmesg | grep -i wbwd
root@EventHorizon:~ # dmesg | grep -i superio
root@EventHorizon:~ #
After that, I did kldunload wbwd but it rebooted after 10 minutes again.
I also tried leaving wbwd.ko running...same result. :(
Man, I truly thank you for your digging this up..but, looks like this is not my day.
I see, nothing in dmesg, the watchdog chip is not known by FreeBSD 14.2 then.
I would boot into either a current Linux or FreeBSD 15-CURRENT to see if the watchdog is recognized. It's of course very unpractical to have to do that in 10min steps :/ but the options are limited at the moment.
And maybe a high-res photo of the motherboard so components to be identified, like the SuperIO.
I had a look Silver Peak 7551a-sv1 because there is driver download from Lanner for that series, the device itself is a Intel C2000 based device, I'm not sure yes what the similarities there are between C2000 and C3000.
The interesting part is that manufacturer do seem to make it complicated to handle the watchdog sometimes. In the case of the Silver Peak 7751 they released the source code for their kernel watchdog driver (for Linux and FreeBSD 8.0). Have not found anything similar for Advantech.
Can you maybe post a boot log, like from as early as possible? Is it an AMI BIOS they use on that thing?
I'm trying to upload a hi res image but having some difficulty..
Quote from: patient0 on March 16, 2025, 10:25:25 AMI see, nothing in dmesg, the watchdog chip is not known by FreeBSD 14.2 then.
I would boot into either a current Linux or FreeBSD 15-CURRENT to see if the watchdog is recognized. It's of course very unpractical to have to do that in 10min steps :/ but the options are limited at the moment.
I will try it and report back.
QuoteAnd maybe a high-res photo of the motherboard so components to be identified, like the SuperIO.
I had a look Silver Peak 7551a-sv1 because there is driver download from Lanner for that series, the device itself is a Intel C2000 based device, I'm not sure yes what the similarities there are between C2000 and C3000.
The interesting part is that manufacturer do seem to make it complicated to handle the watchdog sometimes. In the case of the Silver Peak 7751 they released the source code for their kernel watchdog driver (for Linux and FreeBSD 8.0). Have not found anything similar for Advantech.
Can you maybe post a boot log, like from as early as possible?
QuoteIs it an AMI BIOS they use on that thing?
Yeah, American Megatrends.
root@EventHorizon:~ # cat /var/run/dmesg.boot
---<<BOOT>>---
Copyright (c) 1992-2023 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 14.2-RELEASE-p2 stable/25.1-n269670-fd3d1a7d1e1 SMP amd64
FreeBSD clang version 18.1.6 (https://github.com/llvm/llvm-project.git llvmorg-18.1.6-0-g1118c2e05e67)
VT(vga): resolution 640x480
CPU: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz (2200.21-MHz K8-class CPU)
Origin="GenuineIntel" Id=0x506f1 Family=0x6 Model=0x5f Stepping=1
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=0x4ff8ebbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,RDRAND>
AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
AMD Features2=0x101<LAHF,Prefetch>
Structured Extended Features=0x2294e283<FSGSBASE,TSCADJ,SMEP,ERMS,NFPUSG,MPX,PQE,RDSEED,SMAP,CLFLUSHOPT,PROCTRACE,SHA>
Structured Extended Features3=0xac000400<MD_CLEAR,IBPB,STIBP,ARCH_CAP,SSBD>
XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
IA32_ARCH_CAPS=0x69<RDCL_NO,SKIP_L1DFL_VME,MDS_NO>
VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
TSC: P-state invariant, performance statistics
real memory = 17179869184 (16384 MB)
avail memory = 16559833088 (15792 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <INTEL TIANO >
WARNING: L1 data cache covers fewer APIC IDs than a core (0 < 1)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
random: unblocking device.
ioapic0 <Version 2.0> irqs 0-23
Launching APs: 1 3 2
random: entropy device external interface
wlan: mac acl policy registered
kbd1 at kbdmux0
WARNING: Device "spkr" is Giant locked and may be deleted before FreeBSD 15.0.
vtvga0: <VT VGA driver>
smbios0: <System Management BIOS> at iomem 0xf05e0-0xf05fe
smbios0: Version: 3.0, BCD Revision: 3.0
aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS,SHA1,SHA256>
acpi0: <ALASKA A M I >
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 24000000 Hz quality 950
Event timer "HPET" frequency 24000000 Hz quality 550
Event timer "HPET1" frequency 24000000 Hz quality 440
Event timer "HPET2" frequency 24000000 Hz quality 440
Event timer "HPET3" frequency 24000000 Hz quality 440
Event timer "HPET4" frequency 24000000 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
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 6.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <processor> at device 0.0 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> mem 0xdff60000-0xdff7ffff irq 19 at device 12.0 on pci0
pci2: <ACPI PCI bus> on pcib2
nvme0: <Generic NVMe Device> mem 0xdfd00000-0xdfd03fff irq 19 at device 0.0 on pci2
pcib3: <ACPI PCI-PCI bridge> mem 0xdff40000-0xdff5ffff irq 21 at device 15.0 on pci0
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> mem 0xdff20000-0xdff3ffff irq 22 at device 16.0 on pci0
pci4: <ACPI PCI bus> on pcib4
igb0: <Intel(R) I210 (Copper)> port 0xd000-0xd01f mem 0xdfc00000-0xdfc7ffff,0xdfc80000-0xdfc83fff irq 22 at device 0.0 on pci4
igb0: EEPROM V3.25-0 eTrack 0x800005d0
igb0: Using 1024 TX descriptors and 1024 RX descriptors
igb0: Using 4 RX queues 4 TX queues
igb0: Using MSI-X interrupts with 5 vectors
igb0: Ethernet address: 74:fe:48:6e:24:43
igb0: netmap queues/slots: TX 4/1024, RX 4/1024
pcib5: <ACPI PCI-PCI bridge> mem 0xdff00000-0xdff1ffff irq 23 at device 17.0 on pci0
pci5: <ACPI PCI bus> on pcib5
igb1: <Intel(R) I210 (Copper)> port 0xc000-0xc01f mem 0xdfb00000-0xdfb7ffff,0xdfb80000-0xdfb83fff irq 23 at device 0.0 on pci5
igb1: EEPROM V3.25-0 eTrack 0x800005d0
igb1: Using 1024 TX descriptors and 1024 RX descriptors
igb1: Using 4 RX queues 4 TX queues
igb1: Using MSI-X interrupts with 5 vectors
igb1: Ethernet address: 74:fe:48:6e:24:44
igb1: netmap queues/slots: TX 4/1024, RX 4/1024
ahci0: <Intel Denverton AHCI SATA controller> port 0xe050-0xe057,0xe040-0xe043,0xe020-0xe03f mem 0xdff94000-0xdff95fff,0xdff9b000-0xdff9b0ff,0xdff9a000-0xdff9a7ff irq 20 at device 19.0 on pci0
ahci0: AHCI v1.31 with 1 6Gbps ports, Port Multiplier supported
ahcich1: <AHCI channel> at channel 1 on ahci0
ahciem0: <AHCI enclosure management bridge> on ahci0
xhci0: <Intel Denverton USB 3.0 controller> mem 0xdff80000-0xdff8ffff irq 19 at device 21.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
pcib6: <ACPI PCI-PCI bridge> irq 16 at device 22.0 on pci0
pci6: <ACPI PCI bus> on pcib6
ix0: <Intel(R) X553 (1GbE)> mem 0xdf600000-0xdf7fffff,0xdf804000-0xdf807fff irq 16 at device 0.0 on pci6
ix0: Using 2048 TX descriptors and 2048 RX descriptors
ix0: Using 4 RX queues 4 TX queues
ix0: Using MSI-X interrupts with 5 vectors
ix0: allocated for 4 queues
ix0: allocated for 4 rx queues
ix0: Ethernet address: 74:fe:48:6e:24:45
ix0: nvm 0.58.0 eTrack 0x80000878
ix0: netmap queues/slots: TX 4/2048, RX 4/2048
ix1: <Intel(R) X553 (1GbE)> mem 0xdf400000-0xdf5fffff,0xdf800000-0xdf803fff irq 17 at device 0.1 on pci6
ix1: Using 2048 TX descriptors and 2048 RX descriptors
ix1: Using 4 RX queues 4 TX queues
ix1: Using MSI-X interrupts with 5 vectors
ix1: allocated for 4 queues
ix1: allocated for 4 rx queues
ix1: Ethernet address: 74:fe:48:6e:24:46
ix1: nvm 0.58.0 eTrack 0x80000878
ix1: netmap queues/slots: TX 4/2048, RX 4/2048
pcib7: <ACPI PCI-PCI bridge> irq 16 at device 23.0 on pci0
pci7: <ACPI PCI bus> on pcib7
ix2: <Intel(R) X553 L (1GbE)> mem 0xdf000000-0xdf1fffff,0xdf204000-0xdf207fff irq 16 at device 0.0 on pci7
ix2: Using 2048 TX descriptors and 2048 RX descriptors
ix2: Using 4 RX queues 4 TX queues
ix2: Using MSI-X interrupts with 5 vectors
ix2: allocated for 4 queues
ix2: allocated for 4 rx queues
ix2: Ethernet address: 74:fe:48:6e:24:47
ix2: nvm 0.58.0 eTrack 0x8000087c
ix2: netmap queues/slots: TX 4/2048, RX 4/2048
ix3: <Intel(R) X553 L (1GbE)> mem 0xdee00000-0xdeffffff,0xdf200000-0xdf203fff irq 17 at device 0.1 on pci7
ix3: Using 2048 TX descriptors and 2048 RX descriptors
ix3: Using 4 RX queues 4 TX queues
ix3: Using MSI-X interrupts with 5 vectors
ix3: allocated for 4 queues
ix3: allocated for 4 rx queues
ix3: Ethernet address: 74:fe:48:6e:24:48
ix3: nvm 0.58.0 eTrack 0x8000087c
ix3: netmap queues/slots: TX 4/2048, RX 4/2048
pci0: <simple comms> at device 24.0 (no driver attached)
sdhci_pci0: <Intel Denverton eMMC 5.0 Controller> mem 0xdff98000-0xdff98fff,0xdff97000-0xdff97fff irq 16 at device 28.0 on pci0
sdhci_pci0: 1 slot(s) allocated
mmc0: <MMC/SD bus> on sdhci_pci0
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
pci0: <memory> at device 31.2 (no driver attached)
pci0: <serial bus> at device 31.5 (no driver attached)
acpi_button0: <Sleep Button> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
uart0: <Non-standard ns8250 class UART with FIFOs> port 0x3f8-0x3ff irq 16 flags 0x10 on acpi0
ns8250: UART FCR is broken
uart0: console (115200,n,8,1)
ns8250: UART FCR is broken
uart1: <Non-standard ns8250 class UART with FIFOs> port 0x2f8-0x2ff irq 17 on acpi0
uart2: <Non-standard ns8250 class UART with FIFOs> port 0x3e8-0x3ef irq 18 on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 219900001600
device_attach: est0 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 219900001600
device_attach: est1 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 219900001600
device_attach: est2 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 219900001600
device_attach: est3 attach returned 6
Timecounter "TSC-low" frequency 1099999949 Hz quality 1000
Timecounters tick every 1.000 msec
ugen0.1: <Intel XHCI root HUB> at usbus0
uhub0 on usbus0
uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
mmcsd0: 8GB <MMCHC DG4008 0.1 SN CBA61821 MFG 10/2021 by 69 0x0000> at mmc0 200.0MHz/8bit/8192-block
mmcsd0boot0: 4MB partition 1 at mmcsd0
mmcsd0boot1: 4MB partition 2 at mmcsd0
mmcsd0rpmb: 4MB partition 3 at mmcsd0
nda0 at nvme0 bus 0 scbus2 target 0 lun 1
nda0: <SAMSUNG MZVLB256HAHQ-000L7 1L2QEXD7 S41GNF0K740623>
nda0: Serial Number S41GNF0K740623
nda0: nvme version 1.2
nda0: 244198MB (500118192 512 byte sectors)
ses0 at ahciem0 bus 0 scbus1 target 0 lun 0
ses0: <AHCI SGPIO Enclosure 2.00 0001> SEMB S-E-S 2.00 device
ses0: SEMB SES Device
Trying to mount root from zfs:zroot/ROOT/default []...
uhub0: 8 ports with 8 removable, self powered
pid 35 (zpool) is attempting to use unsafe AIO requests - not logging anymore
I did a bit more digging into the watchdog topic: there are multiple drivers for different watchdogs, wbwd being Winbond driver.
AMD SB600/SB7xx/SB8xx - amdsbwd
fintek - ftwd
intel - ichwd
ITE SuperIO - itwd
VIA VT8251 CX700 VX800 VX855VX900 - viawd
Winbond <long list of chips> - wbwd
WDA something or other - wdatwd
It would be worth a shot to try the Intel watchdog driver, 'kbdload ichwd' and see if something pops up in dmesg. If not then it would be necessary to check the source code to see why the C3000 is not supported. And what SuperIO is used on the board to see if support possible, maybe some did it already but it's not in FreeBSD yet.
Of course check with a Linux first, best chance that it's supported there.
Eureka!
echo 'ichwd_load="YES"' > /boot/loader.conf.localroot@EventHorizon:~ # cat /boot/loader.conf.local
ichwd_load="YES"
root@EventHorizon:~ # dmesg | grep -i watchdog
ichwd0: <Intel Atom C3000 watchdog timer> at port 0x400-0x41f iomem 0xfdc6000c-0xfdc6000f on isa0
ichwd0: <Intel Atom C3000 watchdog timer> at port 0x400-0x41f iomem 0xfdc6000c-0xfdc6000f on isa0
ichwd0: <Intel Atom C3000 watchdog timer> at port 0x400-0x41f iomem 0xfdc6000c-0xfdc6000f on isa0
root@EventHorizon:~ # dmesg | grep -i superio
root@EventHorizon:~ # kldunload ichwd
ichwd0: detached
root@EventHorizon:~ # date
Wed Jan 2 10:59:23 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:00:32 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:02:27 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:02:56 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:02:57 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:03:01 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:03:31 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:03:56 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:04:33 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:05:47 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:06:53 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:08:06 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:08:47 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:09:49 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:11:09 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:11:55 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:12:02 EST 2008
root@EventHorizon:~ # date
Wed Jan 2 11:13:30 EST 2008
root@EventHorizon:~ #
(I'll have to fix the date, but we're way beyond the 10 minute mark!!)
Wow....like magic.
2 things come to mind.
1.) I'm going to try and reboot and continue without unloading ichwd and see the results.
2.) If normal functionality is only able to be achieved by unloading it, is there a recommended rc.conf that is run at the end of the FreeBSD boot process where I can place kldunload ichwd in order to automate it?
So, to answer my own question, I believe that /etc/rc.local would have been the file to unload the module, after adding the execute bit to it.
However, the machine has been up for 16 minutes now without unloading it.. I will update.
Thank you for ostensibly solving this riddle, Patient_0!
If I can get this thing to stay up for 24 hours, I will post a simple tutorial in this subforum, unless you would like to do so.
These boxes have great specs and can be found for cheap, and getting this information into the hands of others would be great.
Quote from: Ground_0 on March 17, 2025, 02:45:51 PMEureka!
Quoteecho 'ichwd_load="YES"' > /boot/loader.conf.local
...
the machine has been up for 16 minutes now without unloading it.
That is excellent news, happy that it works without programming some watchdog driver. Leaves the BIOS password to find out.
QuoteIf I can get this thing to stay up for 24 hours, I will post a simple tutorial in this subforum, unless you would like to do so.
Good idea, and just you write the tutorial, you got the device.
root@EventHorizon:~ # uptime
9:53AM up 1 day, 1 min, 1 user, load averages: 0.35, 0.36, 0.31
Still chugging. [SOLVED]
Here is a link to the tutorial. (https://forum.opnsense.org/index.php?topic=46431.0)