Ventoy
Ventoy copied to clipboard
[issue]: Ventoy SecureBoot feature causes blank interactive output
Official FAQ
- [X] I have checked the official FAQ.
Ventoy Version
1.0.78
What about latest release
Yes. I have tried the latest release, but the bug still exist.
BIOS Mode
UEFI Mode
Partition Style
GPT
Disk Capacity
500GiB
Disk Manufacturer
Seagate
Image file checksum (if applicable)
No response
Image file download link (if applicable)
No response
What happened?
Problem - Blank display output when enabling Ventoy SecureBoot feature
When using the default SecureBoot feature with Ventoy (regardless of firmware SecureBoot enable / disabled):
- Ventoy would boot to a blank display.
- Ventoy remained interactive with keyboard, I could still navigate and launch an ISO, just no display output.
Originally I thought the bug was related to https://github.com/ventoy/Ventoy/issues/1707
Cause - gfxmode 1920x1080
{
"theme": {
"gfxmode": "1920x1080",
In ventoy.json
setting theme.gfxmode
to the supported output 1920x1080
causes the blank display.
Workaround fixes:
- Changing
ventoy.json
to use a lower resolution or removing this line. - When the Ventoy SecureBoot feature is disabled (via Windows Ventoy GUI), the problem does not occur.
Additional Info
I saw this older issue and followed the advice to press c
and go to grub shell and get output of videoinfo
:
List of supported video modes:
Legend mask/position=red/green/blue/reserved
Adapter 'Bochs PCI Video Driver':
No info available
Adapter 'Cirrus CLGD 5446 PCI Video Driver':
No info available
Adapter 'EFI GOP driver':
0x000 1920 x 1080 x 32 (7680) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x001 640 x 480 x 32 (2560) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x002 800 x 600 x 32 (3200) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x003 1024 x 768 x 32 (4096) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x004 1280 x 1024 x 32 (5120) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
It appears that 1920x1080
would be supported? It works fine with 1280x1024
or lower.
This doesn't bother me as I can use one of the workaround fixes. I am reporting the bug to benefit others. I do not know why it only occurs when enable Ventoy SecureBoot feature (default).