Boot Chain State Machine & Telemetry
State: Framebuffer PanicBoot Probability
18%
SimpleDRM Clash
Active (Pink)
MOK Signature
Unsigned
PCIe Power Reset
Hang Risk
Interactive EFI → KMS Driver Pipeline (6 Stages)
Hover or click node for stage triage
Live Kernel Triage & dmesg Buffer
Active Diagnosis: SimpleDRM / EFI GOP buffer conflict with nvidia-drm modeset causes magenta/pink panic on Rocket Lake hybrid graphics.
Hardware & Kernel Mitigation Controls
Add to
/etc/default/grub under GRUB_CMDLINE_LINUX_DEFAULT:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Execute without disabling UEFI Secure Boot:
# 1. Generate local Machine Owner Key
openssl req -new -x509 -newkey rsa:2048 -keyout /root/MOK.priv -outform DER -out /root/MOK.der -nodes -days 36500 -subj "/CN=HP TE01 Custom Driver Key/"
# 2. Sign NVIDIA kernel module
sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 /root/MOK.priv /root/MOK.der $(modinfo -n nvidia)
# 3. Import key to Shim
sudo mokutil --import /root/MOK.der
# 4. Reboot tower & enter one-time password in HP MOK Management blue screen
Lite Hash Rate (LHR) Clarification: NVIDIA's LHR limiter does NOT cause the Linux kernel panic or black screen. LHR only throttles DaggerHashimoto memory throughput in userspace CUDA buffers. The real crash is SimpleDRM framebuffer collision during kernel modesetting.
HP InsydeH2O BIOS: HP locks down the "Advanced" BIOS menu on TE01-2000i OEM motherboards, preventing OS users from switching Primary Display from Auto/IGPU to PEG or adjusting PCIe ASPM power states. All mitigations must be passed at the kernel command-line layer.
Authoritative Post Fixture Check:
HP TE01-2000i (1K4E9AV)
Tested across: Fedora 41 WS, Linux Mint 22, Bazzite, Zorin OS 17 with Linux 6.8+ / 7.x series kernels.