Yes. I have tried the latest release, but the bug still exist.
Try alternative boot mode
Yes. I have tried them, but the bug still exist.
BIOS Mode
UEFI Mode
Partition Style
GPT
Disk Capacity
32
Disk Manufacturer
No response
Image file checksum (if applicable)
None
Image file download link (if applicable)
No response
What happened?
Sorry I'm new to Github so i post it here.
It took me 9 hours to figure this out:
the goal was to get rid of win10 on my daughters chiliGREEN Mobilitas c14b Notebook.
note: secure boot off, no way to boot in legacy mode with this strange bios
so i put the latest linux mint on a usb stick - and NO - other distros - NO
after a while - rufus - without persistence ! - only the .iso file - in the last step use DD MODE
install ok - reboot - nope stuck in efi shell
played around with efi shell grub shell even initramfs, tried everything, sometimes even get it booted to the installed system
with weired things (eg. in initramfs , showed mmcblk1p2 not found, cat /proc/partitions displays mmcblk0p2, so i changed it, next boot mmcblk0p2 not found, and so on)
tried to update grub - reboot - nope
a few hours later, having google search mask burned into my eyeballs
i found it
when dropped into grub commandline after install
THE SIMPLE solution was:
Use the live CD session to add bootia32-efi to the EFI boot partition, next to grub64. Bootia on Github.
Now booting without the live USB should bring a Grub2 shell, which allowed me to boot Mint reading this doc.
in the grub shell
ls to see the partitions.
ls (hd0,gpt2)/ in my example, to verify its the root partition
configfile (hd1,gpt2)/boot/grub/grub.cfg
boot
Then the screen fills up with weird characters, I recognised a menu and just hit enter for the first choice, system booted.
Booted correctly into a Mint session, update the Grub configuration from a terminal window, in my case :
apt update && apt install grub-efi-ia32-bin && sudo grub-install -v --target=i386-efi --efi-directory=/boot/efi /dev/mmcblk1
Official FAQ
Ventoy Version
not tried yet
What about latest release
Yes. I have tried the latest release, but the bug still exist.
Try alternative boot mode
Yes. I have tried them, but the bug still exist.
BIOS Mode
UEFI Mode
Partition Style
GPT
Disk Capacity
32
Disk Manufacturer
No response
Image file checksum (if applicable)
None
Image file download link (if applicable)
No response
What happened?
Sorry I'm new to Github so i post it here.
It took me 9 hours to figure this out:
the goal was to get rid of win10 on my daughters chiliGREEN Mobilitas c14b Notebook. note: secure boot off, no way to boot in legacy mode with this strange bios
so i put the latest linux mint on a usb stick - and NO - other distros - NO after a while - rufus - without persistence ! - only the .iso file - in the last step use DD MODE install ok - reboot - nope stuck in efi shell
played around with efi shell grub shell even initramfs, tried everything, sometimes even get it booted to the installed system with weired things (eg. in initramfs , showed mmcblk1p2 not found, cat /proc/partitions displays mmcblk0p2, so i changed it, next boot mmcblk0p2 not found, and so on) tried to update grub - reboot - nope
a few hours later, having google search mask burned into my eyeballs i found it
when dropped into grub commandline after install
THE SIMPLE solution was:
Use the live CD session to add bootia32-efi to the EFI boot partition, next to grub64. Bootia on Github. Now booting without the live USB should bring a Grub2 shell, which allowed me to boot Mint reading this doc.
in the grub shell
ls to see the partitions. ls (hd0,gpt2)/ in my example, to verify its the root partition
configfile (hd1,gpt2)/boot/grub/grub.cfg boot
Then the screen fills up with weird characters, I recognised a menu and just hit enter for the first choice, system booted. Booted correctly into a Mint session, update the Grub configuration from a terminal window, in my case : apt update && apt install grub-efi-ia32-bin && sudo grub-install -v --target=i386-efi --efi-directory=/boot/efi /dev/mmcblk1
Reboot and you're done. https://forums.linuxmint.com/viewtopic.php?p=2247107&sid=81ca1ad81deefd616df8c39fdd7267ae#p2247107
in the hope this will help anyone in a similar case (maybe someone can put this post in a better understanding way)
wop