[issue]: Scrambled screen with new linux releases

[mrx23dot]

Official FAQ

• [X] I have checked the official FAQ.

Ventoy Version

1.0.61

What about latest release

Yes. I have tried the latest release, but the bug still exist.

BIOS Mode

Legacy BIOS Mode

Partition Style

MBR

Disk Capacity

32GB

Disk Manufacturer

Sandisk

Image file checksum (if applicable)

No response

Image file download link (if applicable)

No response

What happened?

I get this scrambled line image after trying out latest images of Kali, Clonezilla. Ventoy works perfectly with other images. There is a some incompatibility I guess.

Images: https://osdn.net/projects/clonezilla/downloads/76271/clonezilla-live-2.8.0-25-i686.iso https://cdimage.kali.org/kali-2021.3/kali-linux-2021.3a-live-amd64.iso

I made a video https://youtu.be/Bmg2M0JXvRM

Is it only for me?

[ventoy]

Please refer: https://www.ventoy.net/en/doc_fuzzy_screen.html (although it is more common when booting Windows/WinPE)

[mrx23dot]

Ah, I missed that, will try.

Could we put a big checkbox onto the installer app saying "compatibility text mode" with some hint? Looks like it's needed for HW older than 5years (my was thinkpad).

The goal is to make it trouble free as possible for new users/non experts.

[casiosmu]

I can confirm this bug. up to Ventoy 1.0.79

For me it occurs sometimes (not always!) for the following setups:

• industrial PC's, current hardware, different BIOSes: AMI (2019, 2022), Nuvo-6000
• via USB 2 and 3
• in UEFI mode Edit: with Paragon15 also in non-uefi mode
• different USB sticks (2.0 and 3.0, one being a mSata2USB bridge)
• also linux iso's: Clonezilla (alt.stable amd64 yakkety & hirsute), Paragon (12, 15)

First I thought it has sth. to do with USB3 support of the BIOSes, because sometimes it helped to put an usb 2.0 cable inbetween. But later it also occured with 2.0.

If it occures next I will test the mentioned "Text mode" and give an update here. Edit: switching to test mode helps with the above mentioned Paragon 15 image (others not tested so far)

If I can help you debugging this in any way, please tell me.