And it sort of boots up when I put it to a USB-stick, but after I choose Install Rocky Linux 10.1 from boot menu, it loads some time and crashes and BIOS-boot cycles.
Apparently it doesn’t work, but is this supposed to work or there is some kind of glitch somewhere? Whole device is quite rare so I would not be surprised that nobody else has tried this.
R10 and R9 won’t boot with installer, R8 does but this thing has PATA (parallel ATA) disk that has been removed from Enterprise releases.
This thing has an old Fedora, lsmod shows that it had pata_acpi, pata_via modules loaded. Now trying Fedora Server, it failed too to find disk to install.
I think the most likely choice to succeed would be R8 + driverdisk with PATA-drivers. Apparently those are not even on RPM-packages so I’d have to compile those myself, mayble in KVM-instance.
See this list here: Index of /linux/dud/el8/x86_64 you can see a dd-pata_via. This is a driver update disk iso which you should be able to use to get Rocky installed.
Well that was a huge help and it worked. Looks like the “minimal” is not so minimal after all, it needs 20GB which that PATA is not. Only way to try that is kickstart file.
Another thing is an old VT6122 ethernet, velocity driver that is not in the elrepo package names. Need to dig deeper that too.
That PATA is 4GB and yes, me too do a minimal also. Not sure, but it appears that there is also @^minimal-environment dnf group, is that the same as Anaconda selection “Minimal system” whatever, I don’t know.
My first attempt with kickstart failed, will try again later.
Is the padlock driver visible? (Former Centaurian who helped with the design/support of this CPU)
# dmesg | grep padlock
padlock_aes: Using VIA PadLock ACE for AES algorithm.
padlock_sha: Using VIA PadLock ACE for SHA1/SHA256 algorithms.
# openvpn --show-engines
OpenSSL Crypto Engines
Dynamic engine loading support [dynamic]
VIA PadLock (no-RNG, ACE) [padlock]