F5F Stay Refreshed Hardware Desktop Encounter problems with Secureboot on the ASRock X399 Phantom Gaming 6.

Encounter problems with Secureboot on the ASRock X399 Phantom Gaming 6.

Encounter problems with Secureboot on the ASRock X399 Phantom Gaming 6.

S
Shadowsuns
Member
228
04-08-2018, 01:51 PM
#1
Hello everyone, I’m trying to figure out the best way to organize this post. I’ll go through it in a timeline-like fashion. The setup involves an ASRock X399 Phantom Gaming 6 running BIOS version 1.31, paired with an AMD Threadripper 2920X EVGA GTX 1080. I mostly stick to Linux and have kept TPM and Secureboot disabled. Despite following the usual advice not to alter a running system, I chose to turn them on in case I ever need to install something. Instead of using the default Microsoft keys, I created my own Secureboot credentials. After rebooting, I noticed the PC didn’t display a POST or GRUB screen. Instead, it beeped five times during boot, indicating an issue with GPU detection. OBS also reported NVENC errors. When I tried to enter BIOS, the screen stayed black. Based on these symptoms, I suspect the 1080’s OpROM is signed by Microsoft, and my custom Secureboot keys aren’t loading the GPU firmware correctly. This blocks the POST and GRUB from appearing.

I tried a few fixes: first, I reset the CMOS by unplugging the PC, removing the battery, and holding the CMOS clear switch for a short while. After about half an hour, I restarted with Secureboot enabled and it worked—my Linux clock adjusted properly. The second option was to turn off Secureboot, but I couldn’t see my UEFI setup and found it hard to navigate. Disabling Secureboot from within Linux seemed possible, but I’m not sure how.

The third idea was to manually reflash the BIOS using a programmer, though I have no experience with that. The fourth option was to buy a new motherboard, which feels a bit unnecessary right now.

I’m in a bit of a tough spot and would appreciate any advice or resources you can share. If you need more details, feel free to ask. Thanks!
S
Shadowsuns
04-08-2018, 01:51 PM #1

Hello everyone, I’m trying to figure out the best way to organize this post. I’ll go through it in a timeline-like fashion. The setup involves an ASRock X399 Phantom Gaming 6 running BIOS version 1.31, paired with an AMD Threadripper 2920X EVGA GTX 1080. I mostly stick to Linux and have kept TPM and Secureboot disabled. Despite following the usual advice not to alter a running system, I chose to turn them on in case I ever need to install something. Instead of using the default Microsoft keys, I created my own Secureboot credentials. After rebooting, I noticed the PC didn’t display a POST or GRUB screen. Instead, it beeped five times during boot, indicating an issue with GPU detection. OBS also reported NVENC errors. When I tried to enter BIOS, the screen stayed black. Based on these symptoms, I suspect the 1080’s OpROM is signed by Microsoft, and my custom Secureboot keys aren’t loading the GPU firmware correctly. This blocks the POST and GRUB from appearing.

I tried a few fixes: first, I reset the CMOS by unplugging the PC, removing the battery, and holding the CMOS clear switch for a short while. After about half an hour, I restarted with Secureboot enabled and it worked—my Linux clock adjusted properly. The second option was to turn off Secureboot, but I couldn’t see my UEFI setup and found it hard to navigate. Disabling Secureboot from within Linux seemed possible, but I’m not sure how.

The third idea was to manually reflash the BIOS using a programmer, though I have no experience with that. The fourth option was to buy a new motherboard, which feels a bit unnecessary right now.

I’m in a bit of a tough spot and would appreciate any advice or resources you can share. If you need more details, feel free to ask. Thanks!

F
FidoFlapGames_
Junior Member
3
04-27-2018, 10:37 PM
#2
Take this advice seriously at all times. The most effective solution is to adjust the settings and reinstall the operating system immediately. There might be alternative methods, but they didn’t work for me. Good luck!
F
FidoFlapGames_
04-27-2018, 10:37 PM #2

Take this advice seriously at all times. The most effective solution is to adjust the settings and reinstall the operating system immediately. There might be alternative methods, but they didn’t work for me. Good luck!

M
matand_317
Member
168
05-05-2018, 09:56 AM
#3
I successfully repaired my mainboard. I reprogrammed the BIOS chip with a CH341A programmer and flashrom. I obtained BIOS 1.30 from ASRock and, after several attempts to properly align the clamp, managed to securely back up, erase, and write the chip.
M
matand_317
05-05-2018, 09:56 AM #3

I successfully repaired my mainboard. I reprogrammed the BIOS chip with a CH341A programmer and flashrom. I obtained BIOS 1.30 from ASRock and, after several attempts to properly align the clamp, managed to securely back up, erase, and write the chip.