-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UEFI64 1.20 img doesn't boot #403
Comments
I just found this by chance: https://github.com/Drive-Trust-Alliance/sedutil/wiki/How-To-Fix-Black-Screen-(no-PBA)-on-XPS-Precision-Laptops
What is missing? |
@iramello Hello, did you solve the problem? |
Hello @neo125874, unfortunately I couldn' t solve it yet. |
@iramello I tried Chubby's version & set secure boot, and it's working with lock/unlock, starting OS. |
@iramello, @neo125874: This sounds like another duplicate of #375 and #404. |
No I had this as well. The last thing I saw was the "ok" of the loading of the kernel, then after few seconds the system hangs, with the keyboard that isn't working anymore. I had to shut down the system using the power button. |
sedutil UEFI64 PBA boot images with updated bzImage kernels that solve boot issues can be found here: |
Hello,
I've followed exact instructions on https://github.com/Drive-Trust-Alliance/sedutil/wiki/Encrypting-your-drive, however, when machine boots, I'm presented with the message:
It sounds the image being written on the command
sedutil-cli --loadpbaimage debug /usr/sedutil/UEFI64-1.20.img /dev/nvme0
is not working.I have a NVME Samsung 970 Pro, UEFI without Secure Boot enabled.
Any help / direction is appreciated.
Thanks.
The text was updated successfully, but these errors were encountered: