Skip to content
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

[issue]: Arch Linux 2024.05.01 Won't boot #2825

Closed
1 task done
knoppmyth opened this issue May 3, 2024 · 13 comments
Closed
1 task done

[issue]: Arch Linux 2024.05.01 Won't boot #2825

knoppmyth opened this issue May 3, 2024 · 13 comments
Labels
Fixed This issue has been fixed

Comments

@knoppmyth
Copy link

Official FAQ

  • I have checked the official FAQ.

Ventoy Version

1.0.97

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

Legacy BIOS Mode

Partition Style

MBR

Disk Capacity

16GB

Disk Manufacturer

MicroCenter

Image file checksum (if applicable)

No.

Image file download link (if applicable)

https://mirror.arizona.edu/archlinux/iso/2024.05.01/

What happened?

Arch Linux 2024.05.01 won't boot with Ventoy. Errors with /ventoy/busybox/sh: can't access tty; job control turned off. See included screenshot. To create:
Install Ventoy on thumb drive.
Copy the Arch Linux 2024.05.01 to the Ventoy partition.
Boot off the USB.
Select the ISO.
Select normal mode.
Note the failure to boot.

I had no issue booting the ISO with QEMU or Virtualbox.

Screenshot_20240502_224659

@Ithde
Copy link

Ithde commented May 3, 2024

I also encountered the same problem,Then I tried using Rufus.
When using Rufus, I was prompted:

“This mirror uses Syslinux 6.04/pre2-11-gbf6db5b4, and this program only contains the installation files for Syslinux 6.04/pre1. 
Since the new version of Syslinux is not compatible with other versions, and Rufus can't possibly include all of them, you need to download two additional files (ldlinux.sys and ldlinux.bss) from the Internet. The two extra files (ldlinux.sys and ldlinux.bss) need to be downloaded from the Internet.”

Then I can boot archiso normally.
Of course I'm not sure if that's the reason, Since I've always used ventoy, I ran into this problem this time, so I tried other tools.

@steve6375
Copy link

Select grub2 mode

@slyfox1186
Copy link

slyfox1186 commented May 3, 2024

I just wanted to chime in and say that this is also a problem for me!

Screenshot

@Ithde You mentioned that there were two files you needed to source on the internet. If you know where they are found would you share that with the group? Also, if you know where the files should be placed so ventoy can use them successfully please share that too. Thanks for the great information!

@ptr1337
Copy link

ptr1337 commented May 3, 2024

Hi,

Some Info from my debugging in CachyOS:

as written also in this bugreport #2824 , this issue comes from the microcode hook introduced by mkinitcpio. Somehow Ventoy does not handle the microcode handling correctly.
Removing the microcode hook at an archiso build fixes the issue.

Actually the only way, is to use grub2 mode right now, which is a bit sluggish

@Ithde
Copy link

Ithde commented May 5, 2024

@slyfox1186 I'm sorry, I don't know how to download it either, I just switched to Rufus and reinstalled ventoy after installing Arch again.

@slyfox1186
Copy link

@slyfox1186 I'm sorry, I don't know how to download it either, I just switched to Rufus and reinstalled ventoy after installing Arch again.

If you want to use Ventoy then when the main menu loads with all of your iso files listed, press control+r to enable grub 2. This allowed me to use the latest arch iso with no issues.

@duffydack
Copy link

duffydack commented May 5, 2024

I've checked the docs, is there any way to have specific ISO's use grub2 mode? I already a ventoy.json to auto select an iso and disable secondary, be nice if there was another variable to tell it to use grub2 before booting.
(Just 'r' works also btw)

@steve6375
Copy link

Yes, you can add a suffix to the filenames. Read the documents pages.

ventoy added a commit that referenced this issue May 12, 2024
@ventoy
Copy link
Owner

ventoy commented May 12, 2024

@ventoy ventoy added the Fixed This issue has been fixed label May 12, 2024
@knoppmyth
Copy link
Author

Functionality verified. Thanks for the quick response.

@HanabishiRecca
Copy link

I want to point out that despite the original issue is fixed, the normal mode is still kinda broken.
Microcode is not being loaded in the normal mode. Which could lead to problems on certain CPUs.

@street-grease-coder
Copy link

If you boot system rescue something is an issue already. It's pretty bad that normal mode fails in that moment with default options. It made me just not want to use ventoy in the first place

@youk
Copy link

youk commented Dec 1, 2024

If you boot system rescue something is an issue already

Not necessarily. With SystemRescue one can have multiple configuration profiles and switch them over easily. What other live Linux disto provides a convenience like this?

Besides that, SystemRescue is just a nice selection of disk management utilities. Repairing something is not their only purpose.

It made me just not want to use ventoy in the first place

This is free software and free world. Don't use it then. Complaints like this don't help in any way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed This issue has been fixed
Projects
None yet
Development

No branches or pull requests

10 participants