Table of Contents
BIOS Settings
A TetherBox records around the clock with no keyboard or monitor attached, often at a site far from the nearest engineer. A handful of BIOS settings decide whether it starts by itself after a power cut, boots straight from its own drive and resets itself if its software ever freezes. This page lists every setting to check when you build a TetherBox on your own hardware, prepare a customer unit or visit a unit on site.
These settings apply to Intel and AMD units, including the TetherBox Pico, TetherBox Giga, TetherBox Pro and x86 hardware you have built yourself. Raspberry Pi units and the entry-level TetherBox (2 and 5 channel) do not have a BIOS.
Settings at a Glance
| Setting | Set to | Purpose |
|---|---|---|
| Restore AC Power Loss | Power On | Starts the unit by itself when power returns |
| Halt On | No Errors | Stops a minor fault holding start-up at a keypress prompt |
| Boot priority | Internal drive first | Boots from the TetherBox drive, not from USB or the network |
| Boot Mode | UEFI | Matches how the TetherBox drive is installed |
| Secure Boot | Disabled (recommended) | Not required by TetherBox, and it blocks add-on drivers and firmware checks |
| SATA Mode | AHCI | The standard drive mode |
| Hardware watchdog | Enabled, on boards that need it | Resets the unit if its software or kernel freezes |
| Intel AES-NI | Enabled | Faster VPN and TLS encryption |
| Intel XD Bit (NX / DEP) | Enabled | Security hardening |
| EIST / Turbo | Either value | The operating system governs idle behaviour |
| TPM and BIOS Write Protect | Leave unchanged | No TetherBox requirement |
| Power-On by PCIe, LAN or wake | Either value | Makes no difference on an always-on unit |
To enter the BIOS, connect a display and USB keyboard, switch the unit on and press Del (or F2 on some models) until the BIOS screen appears. Enter the BIOS has the full steps with screenshots. Menu layouts vary between manufacturers, so if a setting is not on the tab named below, look for the same setting name on the other tabs.
Power-Up and Start-Up
Restore AC Power Loss: Power On. On AMI BIOS this is under the Chipset tab. With it set, the unit starts by itself as soon as power returns after a cut, without anyone pressing the power button. Configuring Automatic Power-Up walks through the change with screenshots and a test.
The TetherBox reads this setting each time it starts. If the unit will not switch itself back on after a power cut, the Health box on its overview shows a warning with a link to this page.
Halt On: No Errors. On AMI BIOS this is under the Boot tab; on Phoenix/Award BIOS it is under Main. A unit set to All Errors stops at the power-on self-test (POST) waiting for a keypress on any minor fault, for example a missing keyboard, and stays offline until someone visits the site.
Boot Order and Drive Settings
The TetherBox drive is a GPT disk that boots in UEFI mode. Check each of these:
- Boot priority: internal drive first. Set the TetherBox drive (Hard Disk) as Boot Option #1, with Removable Device and LAN below it or switched off. If Removable is first, the unit tries USB on every boot, which is slower and lets a stray USB stick or a network boot take over start-up. Reconfiguring the Boot Device shows how to change it.
- Boot Mode: UEFI. If the BIOS is set to Legacy only, switch it to UEFI, or UEFI with legacy fallback. The drive installs its bootloader to the standard removable EFI path, so it still boots under UEFI if the saved boot entry is lost.
- Secure Boot: Disabled. TetherBox does not require Secure Boot, and we recommend switching it off, as the note below explains.
- SATA Mode: AHCI. This is the standard mode. Only change it if TetherX has told you otherwise for a specific unit.
Note: A unit with Secure Boot enabled still starts and records normally. With it on, however, Linux refuses drivers built on the unit itself, such as those for an AI accelerator or a graphics card, and it blocks the low-level hardware access TetherBox uses to check firmware settings remotely. Switching it off avoids both.
Hardware Watchdog
The hardware watchdog is a timer built into the board itself. If the TetherBox software or the Linux kernel freezes, the board resets the unit instead of leaving it offline until someone visits the site.
The TetherBox software arms the watchdog automatically at every boot, with a 10-minute timeout, whenever the BIOS exposes it. There is nothing to configure in Linux. Whether the BIOS exposes the watchdog depends on the board.
Boards That Work Without a BIOS Change
On these boards the watchdog works with no BIOS change:
- Gigabyte BRIX J3455 and J4105 (TetherBox Pico).
- Intel NUC11 with an N4505, N5105 or N6005 processor.
- Older Intel J1900, J3160, N3050 and N2830 units.
- AMD Ryzen boards.
Intel N100, N150 and 9th-Generation or Newer Core Boards
On these boards the chipset watchdog only works if the BIOS enables it. To enable it on the Intel reference BIOS (AMI Aptio), follow these steps:
- Open the Chipset tab, then PCH-IO Configuration.
- Set Enable TCO Timer to Enabled.
- Save your changes and restart.
The option's own BIOS help text says that when it is disabled, it "stops TCO timer, and ACPI WDAT table will not be published". Some manufacturers name the same setting ACPI Watchdog or Watchdog Timer.
Warning: Some boards also offer a watchdog that the BIOS runs itself, with a fixed timeout and no hand-over to the operating system. Leave that one off: it restarts the unit every time its timeout runs out, as reported on Intel's community forum for an N150 board.
If you cannot tell which kind of watchdog an option is, leave it off and contact TetherX with the board model and a photo of the BIOS screen.
Shuttle DL30N
The Shuttle DL30N (Intel N100) has the Enable TCO Timer option in every BIOS release (1.03, 1.05, 1.07 and 1.09), but Shuttle hides it from the setup screen by suppressing the Chipset menu, and it defaults to Disabled. It cannot be set from the BIOS screen today.
Tip: No action is needed on a DL30N for now. TetherX is working on a procedure to enable the watchdog on these units.
Boards Whose BIOS Settings Linux Can Read
There is no BIOS option that hands its settings to the operating system. Whether the TetherBox software can read the chipset settings (including the watchdog switch) from Linux is decided by how the manufacturer built the BIOS. Where it can, TetherX can check a setting remotely; where it cannot, the setting can only be checked at the BIOS screen.
| Linux can read the chipset settings | Linux cannot read them |
|---|---|
| Intel NUC11 (N4505, N5105, N6005) | Shuttle DL30N |
| Gigabyte BRIX GB-BTIP-N150 | Gigabyte BRIX J1900, J3160, J3455 and J4105 |
| Gigabyte H610M S2H V3 | Lenovo ThinkCentre Tiny (6th and 7th generation) |
| Dell OptiPlex Tower 7020 | HP ProDesk 400 G5 Mini, ProDesk 600 G3 Mini, EliteDesk 800 G2 Mini |
| HP ProBook 450 G9 | LattePanda Sigma; Supermicro X12STH-F |
| AMD boards: ASUS PRIME A320M-K and B450M-A II, Gigabyte A520M K V2 and A620M H, ASRock A620AM Pro-A, MSI A520M-A PRO |
When choosing new hardware, a board from the left-hand column is easier to support remotely.
Checking the Watchdog
TetherX staff can see whether the watchdog is armed in the hardware details on the TetherBox page. To confirm a unit after changing the setting, contact TetherX support with its serial number.
Processor Settings
Both are under the Advanced tab:
- Intel AES-NI: Enabled. Encryption acceleration in the processor, which speeds up VPN and TLS connections with no downside.
- Intel XD Bit (NX / DEP): Enabled. Security hardening that some kernels expect.
EIST and Turbo can be left at either value. The operating system governs idle behaviour regardless.
Settings You Can Leave As They Are
- TPM and BIOS Write Protect: leave them as they are.
- Power-On by PCIe, LAN or wake: either value is harmless on a unit that is always on.
Save and Test
Save your changes with F4, or open Save & Exit and select Save Changes and Reset.
Then run the power-up test: unplug the power cable, wait 5 seconds and plug it back in. The unit should start by itself, without anyone pressing the power button.
If the settings are lost again after a later power cut, the CMOS battery probably needs replacing. See CMOS Battery Replacement.
Related Articles
- Power Recovery & Boot Errors - automatic power-up, boot errors and the CMOS battery
- Hardware Specifications - choose hardware for a TetherBox
- Build a TetherBox on Your Own Hardware - prepare your own x86 host
- Remote Power Management - smart plug power cycling when a site loses connectivity
- TetherBox Troubleshooting - diagnose hardware, storage and network faults
Referenced in: