Another question.
Every time I boot into it, I'm flung back in time to 01-01-1970, because it's got no hardware clock. I run ntpdate clock.akamai.com, as suggested in the installation instructions to correct it.
Would putting that in /etc/rc.d/rc.local be OK?
EDIT:
No, it didn't work. So how can I fix this?

on my rpi4, rc.local

1 members found this post helpful.

Or maybe a "sleep 10" or 15, or whatever works before the ntpdate command in rc.local. Works for me on an Rpi4 and 5.

1 members found this post helpful.

Thanks, both of you.
I've decided running ntpdate uk.pool.ntp.org after every boot isn't too much trouble.

1 members found this post helpful.

Slacker...

True. At one time I had in my signature here: "A slacker by nature, a Slacker by choice."

Do kde and xfce work for you? Mine works fine as a command-line system, but I cannot get either kde or xfce to work properly. My Pi400 shares a 4K monitor with my desktop machine, so I have to use scaling in both kde and xfce to make things readable (I also need to use the big font on the terminal too, as recommended!). However, as soon as I change anything - be it scaling, wallpaper, anything at all, it all becomes very unstable. Kde crashes as soon as you try to open anything - even System Settings - and on xfce all the panels vanish. I think the panels are still there, they are just underneath the background, where you can't see them!

I can't even get the Pi-fork kernel (which fixed these issues until the 6.6 version came along) to boot at all.

What are your experiences with kde and xfce? Is your monitor 1920x1080? I'm wondering if its something to do with the monitor size. Its certainly related to the graphics environment, as both kde and xfce work fine when I use the SARPI kernel.

Cheers,

--
Pete

Yes. I started with KDE, but it's a bit too "heavy" for the Pi, so I run XFCE now. As I mentioned before, I'm using a 10.1" monitor with the Pi, and only had size problems during installation. Once installed, everything was OK. The resolution of this little monitor is 1024x600.

The "official" RPi OS depends on fake-hwclock for time-keeping.
Seems to depend on s*****d?!

I need someone who knows more than me (everybody? ) to look at what's in that fake-hwclock package (mostly shell scripts & s*****d unit files) and tell me if anything can be used or adapted to be used on Slackware ARM.

Not sure why you are having trouble with the clock setting. All I've ever done is add a server into /etc/ntp.conf and its picked it up pretty quickly. In days of yore, I used to add a sequence of lines like so:But the advice these days is to use this instead:If you are using NetworkManager and WiFi for network connections instead of ethernet, make sure to check the box making the wifi connection accessible by all users (has the effect of storing the network password un-encrypted, which is why some people don't like doing this). However, if you don't make it accessible to all, root can't access it during boot and set the clock!

Once you've done this, the clock should set fine on each reboot without need for invoking any "home-made" scripts.

Regarding KDE and XFCE, I've never found any issues running KDE on the Pi400, until we moved to the 6.6 kernels. Admittedly they were a bit clunky unless you used the Pi-fork kernel, but using that (or SARPI) had it running quite nicely. But it all went screwy with 6.6! Its not 6.6 per se, as the SARPI 6.6 kernels work just fine.

I'll have to try mine on a lower-res monitor and see what happens. It will be a bit of a pain, as its on a sliding tray under my workstation desk, and I'll have to move it to another room to try a 1920x1080 monitor. The wiring under (and behind!) my desk is a right rat's nest...!

--
Pete

You might want to know NTP no longer requires you to set the time before starting the daemon. It offers a startup option -g which is the "allow the first adjustment to be big" option. The option lets ntpd know not to panic at startup when the time is way off. This option was added as part of the move to retire ntpdate. For more information, see https://support.ntp.org/Dev/DeprecatingNtpdate.

NTP 4.2.8p17 is listed as part of the slackwareaarch64-current distribution, so that distribution has -g support. But I did not see the file /etc/rc.d/rc.ntpd. So I suppose you had to roll your own boot script for it. In Slackware64 15.0, rc.ntpd does not bother with ntpdate. It just does:

/usr/sbin/ntpd -g -u ntp:ntp

Also, ntpdate is useful as an attempt to get the clock roughly updated before starting service that are time-sensitive. But now there is an NTP command ntp-wait that you can optionally run before starting a time-sensitive process. It delays the boot sequence until ntpd reports the clock has been set.

I've done all that was suggested, but I'm still back in 1970.

Do you have console output -- what is ntpd saying during multiuser startup?

I've shutdown the RPi 400 for the night, now I'm ARMless and on my x86_64.