github physicsdolphin/nv-uefi-unlocker v2.1.12-rc6
v2.1.12-rc6(pre-release)——死槽复活全家桶:PORT-DIAG 端口诊断、SLOT-REVIVE 复活阶梯、FORCE-SBR、纪律窗口 GPU-SBR、GetBarAttributes 簿记恢复、FWSEC-FALLBACK

pre-releaseone hour ago

v2.1.12-rc6(pre-release)——死槽复活全家桶:PORT-DIAG 端口诊断、SLOT-REVIVE 复活阶梯、FORCE-SBR、纪律窗口 GPU-SBR、GetBarAttributes 簿记恢复、FWSEC-FALLBACK

这是 pre-release;Latest 仍为 v2.1.11。 资产:BOOTX64.EFI.2.1.12-rc6(TX 构建事务版)、BOOTX64.EFI.readonly.2.1.12-rc6(只读负控版)、nv-uefi-unlocker-v2.1.12-rc6.zip(不含 ssdiag——杀软误报隔离政策,ssdiag 一律单独下载)、ssdiag-x86_64-windows-0.8.5.exe(独立资产,与 rc5 相同未变)、falcgen-x86_64-windows-0.1.0.exe + falcgen-x86_64-linux-0.1.0(本版新增,见下方 falcgen 节)。校验和以 SHA256SUMS.2.1.12-rc6 为准。rc5 的全部行为(交接盲区三件套、tx-no-flr、stop-on-failure 等)全部继承,不带新 marker 的 rc6 与 rc5 行为一致(除 ENUMERATE 段新增的只读 PORT-DIAG 行——见下)。

新增能力一览(对应 issue)

能力 marker 内容
PORT-DIAG 端口诊断 无(无条件) 枚举时每个 PCI-PCI 桥/根口一行:PMCSR / LnkCap / LnkCtl / LnkSta / Bridge Control + 当前 secondary/subordinate 总线号;死功能行(vendor 0xffff)无条件记录(不受 ultrafast 门控)。判别「链路真关闭 vs 固件总线重编号」两家族
SLOT-REVIVE 复活阶梯 \tx-revive-dead-slot.txt 对枚举读 0xffff 的死槽:ROM 身份门(固件缓存影子的 PCIR 结构读 vendor/device——只对 N 卡执行,顺带打出死槽 device ID)、杠杆阶梯 PMCSR→D0 / 清 Link Disable / Secondary Bus Reset(每级读回验证,复活只认 vendor 读回);SBR 前自动断开属于死槽的 console GOP(GOP 绑定态 SBR = 黑屏卡死,台架实证);复活后从固件簿记(GetBarAttributes)恢复 BAR,成功则保留候选表、同 boot 交易
FORCE-SBR 强推档 \tx-revive-force-sbr.txt 对「悖论端口」(端口全绿但子端 0xffff)绕过保守 decline 强制 SBR。台架三连阴性:软死桥扛过 SBR(链路重训、config 仍死)——SBR 不是万能复活,软死在链路层之上需真实断电
GPU-SBR 纪律窗口实验 \tx-sbr-gpu.txt 事务内(detach+claim 之后、FWSEC 之前——驱动已断/console 已静默/零解锁状态)对目标卡父口强制 SBR,claim-baseline 全量 config 恢复 + MMIO 芯片身份实证后事务继续。首版在事务前执行(GOP 绑定态)已实证黑屏卡死,该位置已删除——GPU 的 SBR 必须在 GOP 断联后进行,本版为结构性保证(窗口位置 + 运行时 GOP 归属校验双保险)
FWSEC-FALLBACK 无(自动) FWSEC 点火死于 FBIF→sysmem 孔径签名(WPR2-never + 空窗残影 + EXCI 低 16 位 0x3ff,#89/#275 双机)时,免 marker 单次 FLR + VRAM staging 重点火;重试再死走原失败路径

台架验证(Z170 + TU106,九 boot 弧线)

  • DLLLA = LnkSta bit14(0x4000):首版误用 bit13(带宽管理状态位,易变),台架铁证纠错并钉值回归;
  • 04:00.0(ASMedia ASM1080,PCIe→PCI 桥——板载 legacy 供桥;当前 Windows 亦未枚举该设备)间歇 0xffff:悖论形态(父口 DLLLA=1 链路训练着、子端 config master-abort)——FORCE-SBR 三连阴性 = 软死在链路层之上,SBR 无法踢活(给死槽复活划界);
  • GPU-SBR 纪律窗口版全绿:SBR → vendor 翻回 → claim-baseline 六 dword 恢复零 MISMATCH → MMIO 芯片身份实证 → 事务端到端绿 → 系统内成功;
  • GetBarAttributes 簿记交叉验证 4/4 MATCH(base + granularity + 逻辑索引三项全对齐):固件簿记作为 0xffff 死槽的唯一 BAR 来源真硅验证可信;
  • 事务前位置的软锁事故(第 6 boot)已在归档记录,本版不再包含该路径。

已知边界

  • assets-x86_64-linux 未随 rc6 重编(Windows 主机无 linux 工具链):源码自 rc5 零变更,仅内嵌版本号仍为 rc5;Windows 侧 assets-x86_64-windows.exe 为 rc6 全新构建。
  • banner 内的构建时间戳跨增量编译可能不刷新(build.rs 缓存)——对版以 SHA256SUMS 为准。
  • SLOT-REVIVE/GPU-SBR 的 SBR 在 console 属于目标卡时会使屏幕熄灭直至 Windows 接管(结构性保证:GOP 先断联;loader.log 为唯一读回)。

附带工具:falcgen(第一性原理 V67 payload 生成器,独立版本 0.1.0)

本版起随 release 分发:falcgen-x86_64-windows-0.1.0.exe(Windows)与 falcgen-x86_64-linux-0.1.0(Linux ELF,musl 静态链接,rust-lld 构建)。它做的事情:读取钉定 SHA 的 NVIDIA GSP 固件 blob → 位置无关 fuc5(Falcon-5)指令解码器 + 窄解释器定位签名载荷区内的可劫持指令序列 → gadget 扫描器 + 帧文法合成器生成四写解锁链。三家钉值(TU102/GA102/AD102)逐字节复现,TU116 为首个完全第一性原理推导的 die;--gate ss / --gate bar1 输出选择器与 64-bit BAR1 门控预设,带逐 die 机械帧预算校验与钉 SHA 金标自测。操作手册 docs/falcgen-manual.md,横向扩展总账 docs/gate-inventory.md。宪法边界:工具产物只到 payload 文件为止,实机点火仍走里程碑门控。


English summary

v2.1.12-rc6 (pre-release) — the dead-slot revival kit: PORT-DIAG port diagnostics, SLOT-REVIVE revival ladder, FORCE-SBR, in-transaction GPU-SBR, GetBarAttributes bookkeeping restore, FWSEC-FALLBACK.

Pre-release; Latest remains v2.1.11. Assets: BOOTX64.EFI.2.1.12-rc6 (TX transaction build), BOOTX64.EFI.readonly.2.1.12-rc6 (read-only control build), nv-uefi-unlocker-v2.1.12-rc6.zip (no ssdiag by antivirus-isolation policy — download it separately), ssdiag-x86_64-windows-0.8.5.exe (standalone, unchanged from rc5), falcgen-x86_64-windows-0.1.0.exe + falcgen-x86_64-linux-0.1.0 (new in this release — see the falcgen section above). Verify against SHA256SUMS.2.1.12-rc6. All rc5 behavior is inherited; without the new markers, rc6 behaves exactly like rc5 except for the new read-only PORT-DIAG lines at enumeration.

New capabilities (issues)

capability marker what it does
PORT-DIAG port diagnostics none (unconditional) one line per PCI-to-PCI bridge/root port at enumeration: PMCSR, LnkCap/LnkCtl/LnkSta, Bridge Control + the current secondary/subordinate bus numbers; dead functions (vendor 0xffff) logged unconditionally (not gated by ultrafast). Discriminates the two families: link genuinely down vs firmware bus renumbering
SLOT-REVIVE revival ladder \tx-revive-dead-slot.txt for slots reading 0xffff at enumeration: an identity gate on the firmware-cached option ROM (PCIR parse — the shadow is host-side POST state and survives the config space dying; NVIDIA-identified slots only, and it prints the dead slot's device ID), then the lever ladder PMCSR→D0 / clear Link Disable / Secondary Bus Reset (each level readback-verified; revival is believed only on a clean vendor readback). The dead slot's own console GOP is disconnected before any reset (bench-proven: SBR with a bound GOP soft-locks the machine). After revival, BARs are restored from the firmware's own bookkeeping (GetBarAttributes) and a revived slot stays in the candidate list — the transaction runs same-boot
FORCE-SBR override \tx-revive-force-sbr.txt forces the SBR lever on "paradoxical ports" (port reads healthy, child reads 0xffff), overriding the conservative decline. Bench verdict after three rounds: a soft-dead bridge survives SBR (link retrains, config still dead) — SBR is not a universal revive; soft death above the link layer needs real power removal
GPU-SBR disciplined-window experiment \tx-sbr-gpu.txt forced Secondary Bus Reset on the target card's parent port inside the transaction (after detach+claim: drivers detached, console muted, nothing unlocked), claim-baseline full config restore + MMIO chip-identity proof before the chain continues. The earlier pre-transaction placement (GOP still bound) was bench-falsified with a hard soft-lock and is removed — a GPU SBR only runs after the GOP is disconnected; rc6 enforces this structurally (window placement + runtime GOP-ownership checks)
FWSEC-FALLBACK none (automatic) when FWSEC ignition dies on the FBIF→sysmem aperture signature (WPR2-never + empty-window residue + EXCI low-16 0x3ff, #89/#275, two machines): one marker-free FLR + BME re-arm + VRAM-staged re-ignition; a failed retry takes the canonical path

Bench validation (Z170 + TU106, nine-boot arc)

  • DLLLA = LnkSta bit 14 (0x4000): the first draft read bit 13 (the volatile Link Bandwidth Management Status bit); field-caught on the bench and pinned as regression tests.
  • 04:00.0 (ASMedia ASM1080, a PCIe→PCI bridge hosting an onboard legacy path; Windows does not enumerate it at the moment either) intermittent 0xffff: the paradoxical shape (parent DLLLA=1 with the link trained, child config master-aborting) — FORCE-SBR three consecutive negatives = soft death above the link layer; SBR cannot fix it (bounds the revival promise).
  • GPU-SBR disciplined-window round fully green: SBR → vendor reads back 0x10de → claim-baseline six-dword restore with zero mismatches → MMIO chip-identity proof → transaction green end-to-end → in-OS verified.
  • GetBarAttributes cross-check 4/4 MATCH (base + granularity + logical indexing all aligned): the firmware bookkeeping is field-validated as the BAR source for slots whose config cannot be read.
  • The soft-lock incident of the pre-transaction placement (round 6) is archived; rc6 contains none of that path.

Known boundaries

  • assets-x86_64-linux was not rebuilt for rc6 (no linux toolchain on the Windows host): sources unchanged since rc5, only the embedded version string is still rc5; the Windows-side assets-x86_64-windows.exe is a fresh rc6 build.
  • Banner build timestamps can lag across incremental builds (build.rs caching) — trust SHA256SUMS for versioning.
  • The SLOT-REVIVE/GPU-SBR SBR turns the screen off until Windows takes over when the target card owns the console (structural guarantee: the GOP is disconnected first; loader.log is the only readback from that point).

falcgen — what it is

falcgen (standalone crate, v0.1.0) is the first-principles V67 payload generator: a position-independent fuc5 (Falcon-5) instruction decoder + narrow interpreter locate the hijackable instruction sequences inside the signed payload region of a pinned NVIDIA GSP firmware blob; the gadget scanner + frame-grammar synthesizer then emit the four-write unlock chains. All three pinned die references (TU102/GA102/AD102) are reproduced byte-identically, and TU116 was the first die derived fully from first principles. --gate ss / --gate bar1 emit the selector and 64-bit-BAR1 gate-smash presets with per-die mechanical frame-budget checks and pinned-SHA gold-standard self-tests. Manual: docs/falcgen-manual.md; the horizontal-expansion ledger: docs/gate-inventory.md. Constitutional boundary: tool output stops at payload files — real-silicon ignition still goes through the milestone gates.

Don't miss a new nv-uefi-unlocker release

NewReleases is sending notifications on new releases.