# ASUS NUC BIOS Thunderbolt options and the iSetupCfg CLI > What is and is not known about the firmware and BIOS of an ASUS NUC 15 Pro for Thunderbolt eGPU use on Linux — the options that could govern the tunnel and the evidence for each, the undocumented-opti Parent: [Thunderbolt eGPU on Linux for local LLM inference](https://llms-explorer.com/tree/thunderbolt-egpu-linux/) · 11 facets · 72 facts · page: https://llms-explorer.com/tree/asus-nuc-bios-isetupcfg/ ## ASUS NUC BIOS Thunderbolt options and the iSetupCfg CLI - What is and is not known about the firmware and BIOS of an ASUS NUC 15 Pro for Thunderbolt eGPU use on Linux - the options that could govern the tunnel and the evidence for each, the undocumented-options route through the iSetupCfg setup CLI, the NPSS suite, BIOS updates and recovery risk, and a read-before-write change procedure. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#asus-nuc-bios-thunderbolt-options-and-the-isetupcfg-cli) - --- name: asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux title: ASUS NUC 15 Pro (NUC15CRK, Arrow Lake) firmware/BIOS for a Thunderbolt eGPU on Linux description: >- TRIGGER: choosing, reading or changing BIOS/firmware options on an ASUS NUC 15 Pro (NUC15CRK*, Core Ultra 5 225H) that affect Thunderbolt PCIe tunnelling for an eGPU on Linux; using iSetupCfg / NUC Firmware Integrator Tool, NPSS, BIOS updates, recovery, fwupd coverage. SKIP: kernel-side tunnel/bolt/IOMMU, BAR allocation, PCIe PM, fallen-off-bus (see sibling hub references); NVIDIA driver tuning; non-ASUS hosts. Verified as of 2026-09-25. --- — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#asus-nuc-bios-thunderbolt-options-and-the-isetupcfg-cli) ## ASUS NUC 15 Pro firmware for a Thunderbolt eGPU on Linux - Verified-as-of 2026-09-25. Tags: [SOURCED url] published source, [INFERRED] reasoning from sources, [BOX] measured on the reference machine ("the box" below), [UNVERIFIED] could not be confirmed. A BOX tag that names a vendor document (for example "BOX from ASUS TPS") is a document claim, not a measurement. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#asus-nuc-15-pro-firmware-for-a-thunderbolt-egpu-on-linux) - Bottom line: the ASUS pages this research reached document almost nothing about Thunderbolt/eGPU in BIOS for this family. The working setup is kernel-command-line driven [BOX]. BIOS options that could matter exist only as generic Thunderbolt and AMI-firmware (AptioV) concepts; treat every menu name below as [UNVERIFIED] on NUC15CRK until you read it from the machine's own setup dump. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#asus-nuc-15-pro-firmware-for-a-thunderbolt-egpu-on-linux) ## Core Concepts - Firmware connection manager decides tunnel policy. On Intel Thunderbolt (TB)/USB4 hosts the BIOS/firmware sets the security level; Linux only authorises within it. Levels: none, user, secure, dponly, usbonly, nopcie; read at /sys/bus/thunderbolt/devices/domainX/security. If the level is user/secure, PCIe tunnels are created only after the device is authorised. [SOURCED https://www.kernel.org/doc/html/latest/admin-guide/thunderbolt.html] — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#core-concepts) - Security level changed tunnel behaviour on an older Intel NUC; it is not shown on the NUC 15. A Linux kernel bug report on an older Intel NUC (Thunderbolt 3 host) states BIOS level "Unique ID" triggered tunnel attempts while "No Security" prevented any attempt; that host's PCIe tunnel then failed with a firmware error. It is a different platform, so it shows the lever, not the NUC15 behaviour. [SOURCED https://ratatoskr.run/linux-usb/2026/08/17378667/t] — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#core-concepts) - Kernel DMA protection is checked from Linux, not only BIOS. /sys/bus/thunderbolt/devices/domainX/iommu_dma_protection reads 1 when enabled; the kernel doc ties it to native IOMMU on 2018+ systems. That VT-d must also be on in BIOS is this file's inference, not the doc's statement [INFERRED]. [SOURCED kernel doc above] — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#core-concepts) - Secondhand OEM statement: ASUS firmware owns the eGPU-relevant BIOS behaviour. An Intel Community reply on a NUC15CRK eGPU thread (ASMedia ASM2464PDX bridge, RTX 5060 Ti) said Above-4G Decoding, Resizable BAR (ReBAR), security level and cold-boot/sleep/hot-plug behaviour are determined by ASUS firmware and that Intel does not validate them on OEM systems. The page returned HTTP 403 to the research fetch; the content came via a search-result summary, so treat it as secondhand. [SOURCED https://community.intel.com/t5/Mobile-and-Desktop-Processors/NUC15CRK-eGPU-via-TB4-PCIe-tunneling-ASM2464PDX-RTX-5060-Ti/m-p/1756462] — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#core-concepts) - Bandwidth ceiling. The ASUS technical product specification (TPS) lists PCIe tunnelling at 32 Gbps (PCIe 3.0 x4 class) [BOX from ASUS TPS; not re-fetched]. No BIOS option is known to raise this (inferred, untested) [INFERRED]. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#core-concepts) - The box's BIOS. Product NUC15CRKU5, BIOS CRARL579.0032.2026.0704.0118, rev 5.32, embedded controller (EC) 2.12; fwupd shows only the Internal SPI Controller, no Thunderbolt controller-firmware (NVM) entry [BOX]. ASUS lists BIOS 0032 dated 2026/07/28 on its support page while the box's build string carries 0704 (read here as 4 July; field order assumed [INFERRED]); do not equate the two dates [SOURCED https://www.asus.com/us/supportonly/nuc15crku5/helpdesk_bios/]. This file flags the gap without resolving it: whether the box runs the exact image ASUS lists as 0032 is [UNVERIFIED]. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#core-concepts) ## Options That May Govern the Tunnel - Only items named in the ASUS manuals are confirmed to exist: fan mode, after-power-failure, modern standby, ErP Ready (enter setup with F2 or Del) [BOX from ASUS manuals]. Everything else is a candidate class, not a verified menu. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#options-that-may-govern-the-tunnel) ## Undocumented Options and the Setup CLI - /o reads or exports and /i writes; a wrong write can leave the machine hard to boot or configure [INFERRED]. Read the Safe-change procedure and Anti-patterns before any write. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#undocumented-options-and-the-setup-cli) - Tool. The NUC Firmware Integrator Tool (downloaded from the ASUS support site) ships AptioV Integrator Tools: iFlashV, iDMIEdit, iCHLogo and iSetupCfg. iSetupCfg is a command-line tool to update NVRAM variables from EFI, Linux or Windows. ASUS warns the tools work only on AptioV-based products and may not suit every model in a series. [SOURCED https://www.asus.com/us/support/faq/1052633/] [SOURCED https://www.asus.com/support/faq/1052866/] Only iSetupCfg is covered here; this file gives no procedure for iFlashV (by name a flasher [INFERRED]), iDMIEdit or iCHLogo. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#undocumented-options-and-the-setup-cli) - Export. ASUS documents iSetupCfgWin64.exe /o /s for "NUC Gen 8 and later". [SOURCED https://www.asus.com/us/support/faq/1052729/] Whether NUC15CRK (Arrow Lake) is on the supported list was not confirmed [UNVERIFIED] (ASUS also warns the tools may not suit every model in a series); check the tool's own product list first, and do not write if the tool rejects this model or the export fails or is empty. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#undocumented-options-and-the-setup-cli) - Syntax from a practitioner write-up (Windows build). Export all: /o /s: /b; non-default only: /ndef /q; read one value by map string: /o /ms:; writes, which change firmware settings: /i /ms: /qv: /cpwd:; apply a file (every setting in it is applied): /i /s: /cpwd:. Map strings are identifiers found in your own export (the example given there is for USB boot); values are per-setting hex like 00/01. Never copy a map string from another model or BIOS. [SOURCED https://www.systanddeploy.com/2025/03/managing-bios-settings-on-asus-nuc.html] The ASUS FAQ above writes the switch as /s and this write-up as /s:; which form the NUC15 Linux build accepts is [UNVERIFIED], so check the tool's help before any write. /cpwd also leaves the password in shell history and process listings; avoid shared shells and clear the history afterwards [INFERRED]. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#undocumented-options-and-the-setup-cli) - Password behaviour. Per the write-up, writes need the supervisor password via /cpwd, and setting an "iSetupCfg Password Check" option to Bypass makes /cpwd:admin acceptable. That option's menu location on NUC15 is [UNVERIFIED], as is whether a machine with no supervisor password needs /cpwd at all. Bypass turns a password check off, so treat it as its own single-setting change and record its original value so you can set it back [INFERRED]. Do not set a supervisor password casually: it probably also gates setup entry, and recovery from a lost one probably needs a physical or board-level step [INFERRED]; the jumper route is under CMOS/recovery. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#undocumented-options-and-the-setup-cli) - Linux variant. ASUS says the tools run in EFI, Linux or Windows [SOURCED FAQ 1052633]; exact Linux binary name/arguments not verified [UNVERIFIED]. The EFI-shell variant should avoid OS-side driver loading and is probably the lower-risk path if the Linux binary misbehaves [INFERRED]. Either variant may be blocked by Secure Boot; whether it must be turned off is [UNVERIFIED], and turning it off is its own single-setting change. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#undocumented-options-and-the-setup-cli) - What this research could not find documented: a NUC15CRK map-string list, a Thunderbolt/ReBAR/Above-4G map string, or the setup-page hierarchy. The only route found is to export from the machine and diff [INFERRED]. Whether an export contains the Thunderbolt or Above-4G settings at all is [UNVERIFIED]. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#undocumented-options-and-the-setup-cli) ## NPSS on Linux - NUC Pro Software Suite (NPSS) is an application watchdog/failover suite for unattended and signage systems, plus a Configuration Tool; supports Windows 10/11 and Ubuntu 20.04 LTS per ASUS. It talks to WMI interfaces exposed by NUC ACPI BIOS for diagnostics; nothing indicates it edits BIOS settings or Thunderbolt policy. ASUS states NPSS is deprecated and replaced by ASUS Edge Suite in 2026. [SOURCED https://www.asus.com/us/support/faq/1052851/] — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#npss-on-linux) - The Linux download on the NUC15CRH page (not the box's NUC15CRKU5) is NPSS v4.0.6 (2026/04/10, 47.69 MB); that it also applies to NUC15CRKU5 is [UNVERIFIED]. [SOURCED https://www.asus.com/us/supportonly/nuc15crh/helpdesk_download/] — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#npss-on-linux) - Working verdict: NPSS is very likely irrelevant to eGPU tunnelling; nothing found says it edits BIOS or Thunderbolt policy [INFERRED]. The missing Qt libraries on the box [BOX] are not worth fixing for this purpose [INFERRED]. Its Ubuntu 20.04 target probably explains the library gaps on a newer release [INFERRED]. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#npss-on-linux) ## BIOS Updates and Recovery - Delivery. ASUS support-site download per model: Windows express installer, F7 flash from USB during POST, power-button-menu update, UEFI shell. Recovery: power-button-menu recovery and a security jumper (steps in that FAQ). Warnings: do not power down during the update (up to about 3 minutes), use stable power/UPS, note custom settings first, format USB as FAT32, downgrading is discouraged. [SOURCED https://www.asus.com/support/faq/1052506/] — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) - Release notes for NUC15CRKU5. Versions 0021 through 0032 (2025/03 to 2026/07/28) list only "Security patches", "BIOS flash robustness improvement" and "Platform issue fix"; none mentions Thunderbolt or PCIe. [SOURCED https://www.asus.com/us/supportonly/nuc15crku5/helpdesk_bios/] So there is no release-note evidence that any BIOS version changed eGPU behaviour; "Platform issue fix" is opaque [INFERRED]. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) - Thunderbolt firmware. ASUS has a FAQ titled "Firmware Updates Available for Thunderbolt on NUC products" (fetch blocked, 403; content unread) [SOURCED title only https://zentalk.asus.com/t5/faq/nuc-firmware-updates-available-for-thunderbolt-on-nuc-products/ta-p/409754]. The box shows no TB controller NVM in fwupd [BOX]; the NUC15CRH download page listing (not the box's NUC15CRKU5 page) showed no TB firmware entry for the NUC 15 Pro [SOURCED download page above, extraction partial]. Read the Thunderbolt FAQ above (this research could not) before any Thunderbolt firmware flash; this file gives no procedure for it, and the sibling firmware-hygiene reference warns that a bad update can be hard or impossible to undo. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) - fwupd/LVFS. ASUS has published some board firmware on LVFS, but this research found no confirmation of NUC BIOS on LVFS; the Internal SPI Controller listing is device enumeration, not proof of updates being offered. [SOURCED https://www.phoronix.com/news/ASUS-LVFS-First-Motherboard] Treat NUC updates as ASUS-site-only until fwupdmgr get-updates says otherwise [INFERRED]. A listed update is not a reason to apply it: run the pre-flash checklist below first. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) - "BIOS flashback": no ASUS NUC 15 Pro documentation found for a flashback button; the documented mechanisms are F7, power-button menu and the recovery jumper [UNVERIFIED for flashback]. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) - Risk model and pre-flash checklist [INFERRED unless noted]. Do these in order; stop at the first step you cannot complete. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) - Use only the NUC15CRKU5 image, downloaded from the ASUS support page; another model's image is not interchangeable. Compare size or checksum if ASUS publishes one [INFERRED]. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) - Note every custom setting and save the iSetupCfg export, because updates may reset custom settings [SOURCED FAQ 1052506 "document custom settings"]. Confirm the export file is not empty. Whether an export covers every setting you changed is [UNVERIFIED], so also write down or photograph the setup screens. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) - Keep the last-known-good BIOS file. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) - Flash on stable AC power (a UPS if you have one), with no eGPU or docks attached, from a clean boot. Never flash over an unstable remote session or from a Thunderbolt-attached disk, and do not interrupt the update (ASUS: up to about 3 minutes). — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) - Downgrade only if the vendor page says the older image supports the CPU. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) - Afterwards, re-export and diff against the pre-update export. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) - If the machine will not boot, stop and use the recovery route below. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) - CMOS/recovery. Use the ASUS-documented jumper/power-button recovery (FAQ 1052506), not improvised board shorting; exact jumper position for NUC15CRK not verified [UNVERIFIED]. The ASUS TPS also documents a BIOS Security Jumper whose configuration mode can clear the BIOS user and supervisor passwords (pick only that option: its Clear TPM option makes TPM-encrypted data unreadable), and an MEBX reset header that resets CMOS values, for example after a failed BIOS update; move a jumper only with power off and the cord unplugged [BOX from ASUS TPS 3.1.12 and 3.1.13, read from the box's local copy]. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#bios-updates-and-recovery) ## Safe-change procedure - Record baseline: dmidecode BIOS version/date, kernel cmdline, TB security and iommu_dma_protection, and a full iSetupCfg export (read-only) saved off-box. Confirm the export exists and is not empty; if it failed, stop, since step 4's diff needs a baseline. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#safe-change-procedure) - Read before write: find the target setting and its map string in your own export; read its value with /o /ms:. Note it as the revert value. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#safe-change-procedure) - Change exactly one setting per boot. Keep the eGPU attached only if that is the test; this is for setting changes, never for a flash. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#safe-change-procedure) - Reboot, re-export, diff; confirm only the intended line changed. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#safe-change-procedure) - Test the symptom with the same repro; log the result and revert to the step-2 value if not clearly better. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#safe-change-procedure) - Keep working kernel-cmdline setup unchanged while testing BIOS changes so effects are separable. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#safe-change-procedure) - Do not set or change a supervisor password as part of this. iSetupCfg writes need a supervisor password or Bypass (see Password behaviour); with neither, change the one setting by hand in setup (F2 or Del), noting its current value from the screen first [INFERRED]. Enabling Bypass counts as its own single-setting change. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#safe-change-procedure) - If the machine will not boot after any change, stop. For a bad setting, the power button menu's F5 "Restore BIOS Settings" returns setup to build-time defaults (not your earlier values; the step-1 export records those) [BOX from ASUS TPS 4.3.2, read from the box's local copy]. For a failed flash, use the recovery route under BIOS Updates and Recovery. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#safe-change-procedure) ## Anti-patterns - Copying map strings or settings files from another NUC model/BIOS revision. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#anti-patterns) - Applying a whole exported file (/i /s:) when one setting was meant to change. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#anti-patterns) - Flashing BIOS with an eGPU or dock attached, on unstable mains power with no UPS, or over an unstable remote session. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#anti-patterns) - Assuming a newer BIOS fixes eGPU issues; the NUC15CRKU5 release notes for 0021 through 0032 do not say so. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#anti-patterns) - Chasing NPSS for tunnelling control, or ASUS Edge Suite (not reviewed here). — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#anti-patterns) - Enabling Bypass with no written revert plan. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#anti-patterns) - Trusting secondhand menu names (including those in this file) as present on your firmware. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#anti-patterns) - Treating fwupd's SPI controller entry as an update channel. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#anti-patterns) - Downgrading for a hoped-for fix without vendor confirmation of CPU support. — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#anti-patterns) ## Cross-references - Sibling hub references (not duplicated here), all under references/: — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#cross-references) - Tunnel, bolt, IOMMU: thunderbolt-usb4-pcie-tunnel-bolt-iommu-linux.md — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#cross-references) - BAR allocation: linux-pcie-hotplug-bar-allocation.md — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#cross-references) - PCIe power management: pcie-power-management-aer-dpc-egpu-linux.md — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#cross-references) - Fallen off the bus: linux-nvidia-egpu-fallen-off-bus-diagnosis.md — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#cross-references) - Thunderbolt firmware updates and kernel-regression triage: thunderbolt-firmware-and-kernel-regression-hygiene-linux.md — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#cross-references) - Related references added later: egpu-unattended-remote-recovery-and-out-of-band-linux.md (host-first escalation ladder, remote power control and out-of-band access); egpu-reproducible-bringup-and-drift-detection-linux.md (capturing this wiring as a restorable manifest, drift verifier and restore order). — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#cross-references) ## Sources - ASUS, NUC15CRKU5 BIOS support page: https://www.asus.com/us/supportonly/nuc15crku5/helpdesk_bios/ — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#sources) - ASUS, BIOS Update and Recovery Instructions for NUC: https://www.asus.com/support/faq/1052506/ — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#sources) - ASUS, AptioV Integrator Tools for NUC: https://www.asus.com/us/support/faq/1052633/ — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#sources) - ASUS, How to download the NUC Firmware Integrator Tool: https://www.asus.com/support/faq/1052866/ — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#sources) - ASUS, Exporting NUC BIOS settings in Windows: https://www.asus.com/us/support/faq/1052729/ — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#sources) - ASUS, What is NUC Pro Software Suite: https://www.asus.com/us/support/faq/1052851/ — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#sources) - ASUS, NUC15CRH downloads page (not the box's NUC15CRKU5): https://www.asus.com/us/supportonly/nuc15crh/helpdesk_download/ — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#sources) - Linux kernel, USB4 and Thunderbolt admin guide: https://www.kernel.org/doc/html/latest/admin-guide/thunderbolt.html — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#sources) - iSetupCfg PowerShell write-up (practitioner): https://www.systanddeploy.com/2025/03/managing-bios-settings-on-asus-nuc.html — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#sources) - Linux USB list, PCIe tunnel creation failure report: https://ratatoskr.run/linux-usb/2026/08/17378667/t — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#sources) - Intel Community, NUC15CRK eGPU thread (secondhand, 403 on fetch): https://community.intel.com/t5/Mobile-and-Desktop-Processors/NUC15CRK-eGPU-via-TB4-PCIe-tunneling-ASM2464PDX-RTX-5060-Ti/m-p/1756462 — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#sources) - ASUS ZenTalk, Thunderbolt firmware FAQ (title only, 403): https://zentalk.asus.com/t5/faq/nuc-firmware-updates-available-for-thunderbolt-on-nuc-products/ta-p/409754 — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#sources) - Phoronix, ASUS LVFS first motherboard: https://www.phoronix.com/news/ASUS-LVFS-First-Motherboard — [source](https://llms-explorer.com/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux/#sources) ## Context files - [ASUS NUC BIOS Thunderbolt options and the iSetupCfg CLI](https://llms-explorer.com/downloads/sources/global-ai-hub/asus-nuc15-pro-firmware-for-thunderbolt-egpu-linux.md)