I built a new installer with the latest edition of images_build_kit, and I did not encounter the crash after 10 minutes.
I have to add though I was using the base image (not the xfce one).

Follow up:

Still crashes with init 3. Actually locked up solid while doing a 'slackpkg upgrade-all'. Heartbeat led stopped, screen went blank...no IP activity.

Probably a kernel issue. logs aren't much help, dmesg shows lots of errors for bluetooth.

I'll check out the new build this week.

Hi,

I built an image for RPi3 for you. You can download it from here. Also tested it on my own Pi3, and it has been running for 40 minutes with X and XFCE running.

The 5.9.2 build is working MUCH better! No crashes so far, using the XFCE build. This makes me happy.

Issues:

I want the 'heartbeat' gone. The stated method in an earlier reply didn't work. I was hoping to use a config.txt line to change it. The sarpi install leaves the LED's alone.

WHY is the ethernet MAC address randomized? I create dhcp reservations for all of my 'known' devices.

The ntp.conf file has servers already setup. Don't do that. It's not the Slackware way.

No support for RTC's. I have a DS3231 RTC that works fine with sarpi. I just include these lines in config.txt.
Doesn't work in slarm64

Naive question: How can I complete a FULL install of more packages since it's running? I've tried slackpkg install-new; slackpkg upgrade-all. Not catching everything. Is there an equivalent to the original 'setup' that goes through all the different sections (a, ap, d. e, f, etc.)??

this is the default kernel configuration behavior.
let's check: disabled:
also the default kernel setting
Add the following line if it does not already exist:
fixed

this is not a default installation, but a minimal setting of the finished system.

no way to check. watch dmesg.

you can install everything in the series for example:

1 members found this post helpful.

Sorry, but is it a good idea to hard-code the MAC address for all installations on all the RPi3 boards?

Hi Mara,

Could you also please add the kernel config to the kernel (at least as a module)?
I would also kindly ask you to add support for the Dallas/Maxim DS1307 RTC to the kernel config.

I also have a separate question. Obviously kernel images for the different devices are not part of the Slarm64 package repository. Then what is the recommended way of keeping up to date with new kernel versions? Am I supposed to build it myself? (I personally have no problems with that.) If yes, then what is the recommended way to do it? (I'm avare of the general process on x86 and x86_64, but AFAIK there are some extra steps that one needs to do when compiling a kernel for ARM or ARM64, like generating the device tree files (dtbs). That's why I'm asking.)

for network access it makes sense, and it can always be easily configured by removing this setting uEnv.txt

the module is present in the kernel to install a separate kernel, everything is the same installpkg, having downloaded a separate kernel for a specific board.

The kernel packages are not part of the slarm64 package repository. At least I could not find them at http://mirrors.slackware.bg/slarm64/slarm64-current/
Where do you upload/share them?

Of course I know I could build a new kernel with images-build-kit as well, and then use the kernel packages generated as an upgrade source.

In /boot/config.txt just remove the line

in slarm64, the kernel is not modified for general use (you can also try to use it), kernel packages are located according to the board http://dl.fail.pp.ua/slackware/packages/aarch64/k/

1 members found this post helpful.

Yes, I can confirm it. RTC support works.
Could you still add the configuration at least as a loadable module, please?

Thank you Mara!

automatically load the module:

added the ability to disable the NTP server settings at the stage of building the image