Parabola systemd CLI image freezes when booting into the USB
I've made the bootable USB via dd with Arch, and Rufus via my girlfriend's Windows 10 laptop, and tried 3 different USB drives. My Arch ISO USB works fine.
Is the installer corrupted? Has it been checked lately? The only message I get before it freezes is that KVM is disabled by the BIOS, but it says the same for my Arch USB before it works fine.
you can use the provided checksum in the SHA512SUMS file to
verify that the download was not corrupted
the systemd and openrc ISOs behave differently on some computers
- there are a few things you could try
- press the TAB key at the GRUB menu, and add nomodeset to the boot command
- set your computer to beet in "legacy BIOS" mode
- try the TalkingParabola ISO
- try one of the openrc ISOs
after reading your other post, i am confused now, why you want to boot a CLI ISO
in that thread, you mentinoed that you only had trouble booting the systemd/CLI ISO; but you were able to boot the systemd/LXDE ISO and run the installer - if you can boot any parabola LiveISO, then you do not need to try any other
from the downlaods page
Which one should I choose?
All Parabola LiveISOs are capable of installing any variant of Parabola system to the target disk, regardless of the init-system or graphical environment. For example, any of the SystemD LiveISOs can be used to install an OpenRC system and vice-versa. Likewise, any of the LiveISOs (either CLI or graphical) can be used to install any WM/DE, such as Gnome, KDE, and many others, or none at all.
I think I could have worded things better on my end.
When I say "didn't boot" I'm referring to the USB drive itself. The CLI one couldn't even get to the installer. The LXDE ISO runs fine on a USB but fails the install (the error says it is unable to install the bootloader).
if any of the parabola LivISOs boot on your computer, then
do not worry about the ones that you can not boot - just use
the one that works - all parabola LivISOs are adequate to
install any variety of parabola system - the main reason why
there are both systemd and openrc ISOs available, is because
certain computers can boot the openrc ISOs but not the systemd
ISOs, and certain other computers can boot the systemd ISOs but
not the openrc ISOs
for the sake of completeness, there are multple open bug reports
about the problem - the reason why some computers have trouble
booting some ISOs, is not related to the initsystem - it is
because they have different EFI images - i beleive that it has
been determined, that those problematic computers can boot all
parabola LiveISOs in "legacy BIOS" mode - for those reasons, it
is a relatively low-priority problem - we are not aware of any
x86 computers, which parabola can not be installed onto somehow