Re: bootstra.tos broken on 68040/68060 real hardware
Miro Kropáček <[email protected]> Sun, 19 Jul 2026 10:08:43 +1000
| Newsgroups | gmane.linux.debian.ports.68k |
|---|---|
| Message-ID | <CAN5rfbSZ=cLuXo+ZZaG7u_ya82jMosZWwozgEspUaWtJho7M9g@mail.gmail.com> |
--0000000000006da9670656eb98ec Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable That's exactly why I'm posting these emails, I won't remember a thing in one weeks time. :-) However if you have a wiki which I can access and update, I can post my findings there, too. I remember seeing an aranym guide from ~2012. Surprisingly (to me), I had the netusbee (network) driver available all along, at least in the installed root. No need to use Geert's tree (but thanks to docker it is quite trivial to setup the whole cross compiler tool chain). The actual apt update (first I had to update the keyring as the one in Debian 12 iso is no longer valid) and install was another slow motion show. :-) But the good news is that NetUSBee's transfer rate is basically identical to what I'm seeing in FreeMiNT, about 300 KB/s. So even with all that modern baggage, the kernel itself can still run efficiently. Would be interesting to explore how many kernel options can be disabled to help out ancient hardware to boot/work faster. I'm sure that there is also a lot of user space stuff to skip/disable. http://mikro.atari.org On Sun, 19 July 2026, 4:12=E2=80=AFam Michael Schmitz, <[email protected]= m> wrote: > Miro, > > please compile some notes on what you had to add to the initrd, and what > changes were necessary after installation. Even if none of that ever make= s > it into the installer bugfixes, it would help anyone trying to install > Debian on the CT60. > > Last I heard of someone attempting to use systemd on the CT60, it was too > slow and continued to time out. That was 10 years or more ago, so some > issues appear to have been fixed in the meantime. > > You'll likely hit the same timeouts due to slow crypto code again when > using ssh - public key authentication (and the simplest crypto algorithms > supported) was the only way for me. There used to be 060 optimized crypto > libraries that could speed up logins a great deal, but AFAIR they used ha= nd > optimized assembly for crypto primitives. Not sure letting the compiler > optimize for 060 can achieve near as much speedup. > > The keymap issue is a long standing problem - that should be reported to > the installer team as a bugfix (same as the missing modules). > > Cheers, > > Michael > On 19/07/2026 12:27 AM, Miro Krop=C3=A1=C4=8Dek wrote: > > On Sat, 18 Jul 2026 at 00:39, Michael Schmitz <[email protected]> > wrote: > >> I'm sure that would be a lot easier (unless FreeMINT has introduced >> endianness issues). >> > It was. But of course I had to prepare another initrd because the default > one didn't contain ext4.ko and jbd2.ko. :) > > So, after that I was finally able to finish the installation but oh dear, > was it a long one. Against Debian 3.1, Debian 12's netinst.iso is twice a= s > big but the installation time was 30 minutes vs. ... I don't know, severa= l > hours (I let it run during the night). And that was with TT RAM enabled! > > Another hiccup was booting the installed system: since the default kernel > doesn't contain pata_falcon.ko, libata.ko, ext4.ko and jbd2.ko, I had to > boot into the installer again, take initrd.img from my installed partitio= n, > copy to FreeMiNT's ext2 partition, then copy it to TOS GEMDOS partition, > then add -r to bootargs (unlike 2.2.25) and after *that* I was able to > see the login prompt after a long series of debug messages. Funny to see > systemd on my Falcon. :) > > Could I log into the system after all? Of course not. :) This took anothe= r > couple of hours: by default, Debian 12 uses yescrypt for password hashes. > yescrypt is so heavy that even 60s is not enough for verifying my passwor= d > so after entering login+password I was welcomed with ... a restarted logi= n > prompt because the kernel killed the login process for taking 100% CPU ti= me > for one minute. :) > > So a happy end but oh dear, Debian 3.1 was a breeze in comparison to this= . > I have one last item on my TODO and that is trying a build from Geert's > branch so I can see my NetUSBee alive. > > P.S. I could also observe a few minor oddities like "shutdown" actually > not shutting down the CT60 or that after a while (that happened in both t= he > installer and the installed system), IKBD packets are interpreted > somewhat... weirdly. For instance UP arrow doesn't work anymore, I have t= o > use INSERT. shell history's UP arrow also doesn't work and if I use CTRL+= P, > I have to go RIGHT if I want to move the cursor LEFT. > > -- > http://mikro.atari.org > > --0000000000006da9670656eb98ec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div>That's exactly why I'm posting these emails,= I won't remember a thing in one weeks time. :-)</div><div dir=3D"auto"= ><br></div><div dir=3D"auto">However if you have a wiki which I can access = and update, I can post my findings there, too. I remember seeing an aranym = guide from ~2012.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Surpri= singly (to me), I had the netusbee (network) driver available all along, at= least in the installed root. No need to use Geert's tree (but thanks t= o docker it is quite trivial to setup the whole cross compiler tool chain).= </div><div dir=3D"auto"><br></div><div dir=3D"auto">The actual apt update (= first I had to update the keyring as the one in Debian 12 iso is no longer = valid) and install was another slow motion show. :-)</div><div dir=3D"auto"= ><br></div><div dir=3D"auto">But the good news is that NetUSBee's trans= fer rate is basically identical to what I'm seeing in FreeMiNT, about 3= 00 KB/s. So even with all that modern baggage, the kernel itself can still = run efficiently.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Would b= e interesting to explore how many kernel options can be disabled to help ou= t ancient hardware to boot/work faster. I'm sure that there is also a l= ot of user space stuff to skip/disable.</div><div><br></div><div data-smart= mail=3D"gmail_signature"><div dir=3D"ltr"><div><a href=3D"http://mikro.atar= i.org" target=3D"_blank">http://mikro.atari.org</a></div></div></div></div>= <br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class= =3D"gmail_attr">On Sun, 19 July 2026, 4:12=E2=80=AFam Michael Schmitz, <= <a href=3D"mailto:[email protected]">[email protected]</a>> wrote:= <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord= er-left:1px #ccc solid;padding-left:1ex"><u></u> =20 =20 =20 <div> <p>Miro,</p> <p>please compile some notes on what you had to add to the initrd, and what changes were necessary after installation. Even if none of that ever makes it into the installer bugfixes, it would help anyone trying to install Debian on the CT60.</p> <p>Last I heard of someone attempting to use systemd on the CT60, it was too slow and continued to time out. That was 10 years or more ago, so some issues appear to have been fixed in the meantime.</p> <p>You'll likely hit the same timeouts due to slow crypto code agai= n when using ssh - public key authentication (and the simplest crypto algorithms supported) was the only way for me. There used to be 060 optimized crypto libraries that could speed up logins a great deal, but AFAIR they used hand optimized assembly for crypto primitives. Not sure letting the compiler optimize for 060 can achieve near as much speedup.</p> <p>The keymap issue is a long standing problem - that should be reported to the installer team as a bugfix (same as the missing modules).=C2=A0</p> <p>Cheers,</p> <p>=C2=A0 =C2=A0 Michael=C2=A0=C2=A0</p> <div>On 19/07/2026 12:27 AM, Miro Krop=C3=A1=C4=8Dek wrote:<br> </div> <blockquote type=3D"cite"> =20 <div dir=3D"ltr"> <div dir=3D"ltr"><span style=3D"background-color:transparent">On Sat, 18 Jul 2026 at 00:39, Michael Schmitz <<a href=3D"mailt= o:[email protected]" target=3D"_blank" rel=3D"noreferrer">schmitzmic@gma= il.com</a>> wrote:</span></div> <div class=3D"gmail_quote"> <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8= ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div> <p><span style=3D"background-color:transparent">I'm sure that would be a lot easier (unless FreeMINT has introduced endianness issues).=C2=A0</span></p> </div> </blockquote> <div>It was. But of course I had to prepare another initrd because the default one didn't contain ext4.ko and=C2=A0jbd= 2.ko. :)</div> <div><br> </div> <div>So, after that=C2=A0I was finally able to finish the installation but oh dear, was it a long one. Against Debian 3.1, Debian 12's netinst.iso is twice as big but the installation time was 30 minutes=C2=A0vs. ... I don't know, several hours (I let it run during the night). And that was with TT RAM enabled!</div> <div><br> </div> <div>Another hiccup was booting the installed system: since the default kernel doesn't contain=C2=A0pata_falcon.ko, libata.ko, ext4.ko and=C2=A0<span style=3D"background-color:tra= nsparent">jbd2.ko, I had to boot into the installer again, take initrd.img from my installed partition, copy to FreeMiNT's ext2 partition, then copy it to TOS GEMDOS partition, then add -r to bootargs </span>(unlike 2.2.25)=C2=A0<span style=3D"backgroun= d-color:transparent">and after <i>that</i>=C2=A0I was able to see the login prompt after a long series of debug messages. Funny to see systemd on my Falcon. :)</span><= /div> <div><span style=3D"background-color:transparent"><br> </span></div> <div>Could I log into the system after all? Of course not. :) This took another couple of hours: by default, Debian 12 uses yescrypt for password hashes. yescrypt is so heavy that even 60s is not enough for verifying my password so after entering login+password I was welcomed with ... a restarted login prompt because the kernel killed the login process for taking 100% CPU time for one minute. :)</div> <div><br> </div> <div>So a happy end but oh dear, Debian 3.1 was a breeze in comparison to this. I have one last item on my TODO and that is trying a build from Geert's branch so I can see my NetUSBee alive.</div> <div><br> </div> <div>P.S. I could also observe a few minor oddities like "shutdown" actually not shutting down the CT60 or tha= t after a while (that happened in both the installer and the installed system), IKBD packets are interpreted somewhat... weirdly. For instance UP arrow doesn't work anymore, I have to use INSERT. shell history's UP arrow also doesn't wo= rk and if I use CTRL+P, I have to go RIGHT if I want to move the cursor LEFT.</div> </div> <div><br> </div> <span class=3D"gmail_signature_prefix">-- </span><br> <div dir=3D"ltr" class=3D"gmail_signature"> <div dir=3D"ltr"> <div><a href=3D"http://mikro.atari.org" target=3D"_blank" rel= =3D"noreferrer">http://mikro.atari.org</a></div> </div> </div> </div> </blockquote> </div> </blockquote></div> --0000000000006da9670656eb98ec--