I bought this refurbed HP with the intention of wiping Win10 and replacing it with Rocky Linux. It will boot windows. But, when I change to boot drive to cd/dvd drive and insert a Rocky Linux 9.2 install CD, it gives an error message. I have used the linux boot cds to install Rocky Linux on a Toshiba laptop.
Any idea what is causing the problem? The cd/dvd drive recognizes and runs a Win10 repair cd. But not either of my Rocky Linux cds. There’s no option for chosing a USB stick.
Your processor is likely too old to be supported by Rocky Linux 9. You can verify this by running a Rocky Linux 8 installer. If it comes up, attempt to go to a terminal (e.g. ctrl+alt+f1) and run: /lib64/ld-linux-x86-64.so.2 --help
Subdirectories of glibc-hwcaps directories, in priority order:
x86-64-v2 (supported, searched)
You will need at least x86-64-v2 for Rocky Linux 9 to run.
Intel has released 13 generations of “i5” CPUs, first around 2009.
First Intel CPU’s to support x86-64-v2 were also about 2009, but that does not mean that all do.
HP site says about “600 G1”: 4th gen CPU. Likely to support, but better to verify.
Error message: Invalid disk image. This was from trying to boot from either ‘boot’ iso or from ‘minimal’ iso.
There was no option in the boot devices for booting from USB memory stick. Yes, for USB hard drive (that didn’t work for a memory stick), and for ATAPI and USB cd/dvd druves. Those didn’t work either. None of the option in the boot lust would allow booting from a memory stick.
The ATAPI cd attempted to boot from the two iso dvds but failed with the error message above.
The Secure Boot is a feature in UEFI mode boot. The firmware, UEFI (aka BIOS), has some certificates stored on the motherboard. The Secure Boot checks bootloader, kernel, and kernel modules that they are all signed by some of the certificate chains that the UEFI has. If signatures are not valid, then invalid components are not loaded.
Therefore, Secure Boot does not prevent “other” OS, just unknown OS, and Rocky ought to be known.
Then again, an ancient machine might not have valid certificates for any current OS.
It is possible to load certificates to the UEFI (with mokutil).