|
Raspberry Pi 4 bcm2711 (aarch64)
I don’t know whether many people want or not, but I was contacted about installing slarm64 on this device.
After reading the data on the operation of this device, I realized that this device can be added to the image assembly (images_build_kit) system for devices. While this is not in the main branch, I would like to test for transfer to the general branch, but I do not have this device. so please test the system boot. I decided to use u-boot as a kernel loading layer, let's see what happens. compiled the kernel 5.6.10 slarm64-current-aarch64-base-rootfs-20200513-5.6.10-raspberry_pi_4-build-20200517.img.xz slarm64-current-aarch64-base-rootfs-20200513-5.6.10-raspberry_pi_4-build-20200517.img.xz.md5 if the download fails, try changing the kernel=u-boot.bin parameter to kernel=Image in /boot/config.txt I also want to mention akschu which already described the assembly process. |
I have installed slarm64 on my pi4. It works really well. I used the 32 bit installer to put the software on it. You have to edit your config.txt.
Code:
kernel=kernel8.imgThe gcc compiler does not build a bootable kernel. Building the arm version of gcc (version 9.2.1) and replacing the slarm64 version now works. I have no other issues (yet). Kind regards, Dunc. |
Thanks Dunc,
I want to add a build of a clean aarch64 system, and then a simple installation on sdcard or hdd. |
My biggest concern about switching to slarm64 on my pi 4 is the lack of arm64 software, along with the headaches of compiling stuff that I already know works on Slackware ARM.
I use mate (msb) on my laptop. I did my daily git pull of all the repos I follow and found: https://github.com/mateslackbuilds/m...04b20b0b573804 Is this still in the very early testing phase? Or do you have a working mate environment in slarm64? |
Forgive me for the noise. I just found http://dl.fail.pp.ua/slackware/packages/aarch64/mate/
|
Quote:
|
Thanks to János testing, the system boots normally without using u-boot.
Of course I would like to use u-boot, but again there is no way to test. please check the work: slarm64-current-aarch64-base-rootfs-20200513-5.6.10-raspberry_pi_4-build-20200519.img.xz slarm64-current-aarch64-base-rootfs-20200513-5.6.10-raspberry_pi_4-build-20200519.img.xz.md5 |
if it does not load, try to remove everything from the **config.txt** leave only
enable_uart=1 kernel=u-boot.bin or change only kernel=u-boot.bin to kernel=Image kernel 5.6.14 slarm64-current-aarch64-base-rootfs-20200520-5.6.14-raspberry_pi_4-build-20200521.img.xz slarm64-current-aarch64-base-rootfs-20200520-5.6.14-raspberry_pi_4-build-20200521.img.xz.md5 |
patches were applied for u-boot if it will not boot try changing the kernel=u-boot.bin parameter to kernel=Image in /boot/config.txt
slarm64-current-aarch64-base-rootfs-20200520-5.6.14-raspberry_pi_4-build-20200521.img.xz slarm64-current-aarch64-base-rootfs-20200520-5.6.14-raspberry_pi_4-build-20200521.img.xz.md5 |
Thanks to sndwvs, support for Raspberry 3 and 4 will me merged to images_build_kit soon, so anyone can build a Slarm64 installer for themselves, and can install a completely 64-bit ARM-based Slackware derivative on their 64-bit capable Raspberry Pis.
|
|
|
|
added firmware packages and utilities
rpi-eeprom-r198.2a8c2e7-aarch64-1mara.txz rpi-userland-r799.f97b1af-aarch64-1mara.txz |
1 Attachment(s)
update kernel 5.7.6
enable audio: Code:
echo "extraargs=coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1" >> /boot/uEnv.txtslarm64-current-aarch64-base-rootfs-20200528-5.7.6-raspberry_pi_4-build-20200627.img.xz.md5 slarm64-current-aarch64-xfce-rootfs-20200528-5.7.6-raspberry_pi_4-build-20200627.img.xz slarm64-current-aarch64-xfce-rootfs-20200528-5.7.6-raspberry_pi_4-build-20200627.img.xz.md5 WIFI through NetworkManager is not connected. use /etc/wpa_supplicant.conf Code:
network={/etc/rc.d/rc.inet1.conf Code:
IFNAME[4]="wlan0" |
| All times are GMT -5. The time now is 05:28 PM. |