Hi, (Updated subject.) On 13.6.2025 14.22, John Paul Adrian Glaubitz wrote:
On Thu, 2025-06-12 at 17:54 +0300, Eero Tamminen wrote:(Full m68k Debian is too heavy to boot in reasonable time on machines that Hatari emulates, due to missing crypto acceleration, but IMHO also unnecessary for kernel ABI change discussions.)
Note that above is about Debian defaults. What one gets before being able to locate, disable and configure every option and service that makes things crawl (and build own kernel more optimal for that setup).
Last time I booted Debian/m68k on my Amiga 68060 it booted fine. It took a few minutes but that's not surprising given the machine has only 50 MHz.
It's few years since I tried it, but I was testing on (emulated) 030 @ 32Mhz [1] which is quite a bit slower than your setup, and I included logging into console to "booting Debian".
When Debian changed encryption default from MD5 to SHA512, login time exploded. If I don't completely misremember, it took something like 20 min. Switching PAM back to MD5 helped a lot with login.
Debian has switched to "yescrypt" since then, which I assume to be even slower default. :-)
=> It's hard for me to image somebody even trying to use something like KDE, Gnome or Libreoffice on m68k HW, even fast FPGA ones.
- Eero[1] Hatari can emulate up to 060 @ 32Mhz, but 060 emulation did not work with Linux when I did that testing. It does now, but unlike with 030, only if one disables d/i-cache emulation...
(My Google-Foo may be lacking, but at least I did not find any guide / wiki helping to optimize Debian for such slow setup, so I gave up, as I had other issues to investigate / solve.)