[SOLVED] Raspberry Pi 4 bcm2711 (aarch64)

sndwvs · 05-18-2020, 02:59 AM

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.

Dunc. · 05-18-2020, 07:01 AM

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.img
arm_64bit=1

When you reboot you will find that all did not install properly. Simply re-install again. I know it is a bit of a kludge to install twice but I wanted to see if it worked ok rather than develop a slick installer.

The 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.

sndwvs · 05-18-2020, 07:07 AM

Thanks Dunc,

I want to add a build of a clean aarch64 system, and then a simple installation on sdcard or hdd.

mralk3 · 05-18-2020, 12:10 PM

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?

mralk3 · 05-18-2020, 12:18 PM

Forgive me for the noise. I just found http://dl.fail.pp.ua/slackware/packages/aarch64/mate/

sndwvs · 05-18-2020, 12:28 PM

Quote:

Originally Posted by mralk3

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?

I have been using this system every day (on all my armv8 devices) for more than a year as a desktop on rockpro64+ssd. I had no problems with compilation. And yes, I find it stable. the package base is the same as in the original Slackware64 with some exceptions. To build slarm64 i use lxc on rock pi 4

sndwvs · 05-19-2020, 02:27 PM

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

sndwvs · 05-21-2020, 12:34 AM

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

sndwvs · 05-21-2020, 03:20 PM

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

wowbaggerHU · 05-22-2020, 07:08 AM

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.

sndwvs · 05-22-2020, 07:20 AM

Fixed boot using u-boot, thanks to testing János

slarm64-current-aarch64-base-rootfs-20200520-5.6.14-raspberry_pi_4-build-20200522.img.xz
slarm64-current-aarch64-base-rootfs-20200520-5.6.14-raspberry_pi_4-build-20200522.img.xz.md5

sndwvs · 05-24-2020, 09:46 PM

slarm64-current-aarch64-xfce-rootfs-20200520-5.6.14-raspberry_pi_4-build-20200524.img.xz
slarm64-current-aarch64-xfce-rootfs-20200520-5.6.14-raspberry_pi_4-build-20200524.img.xz.md5

sndwvs · 05-25-2020, 02:48 PM

kernel-bcm2711-4.19.122-aarch64-1mara.txz
kernel-firmware-bcm2711-4.19.122-aarch64-1mara.txz
kernel-headers-bcm2711-4.19.122-aarch64-1mara.txz
kernel-modules-bcm2711-4.19.122-aarch64-1mara.txz
kernel-source-bcm2711-4.19.122-noarch-1mara.txz

sndwvs · 06-19-2020, 03:02 PM

added firmware packages and utilities
rpi-eeprom-r198.2a8c2e7-aarch64-1mara.txz
rpi-userland-r799.f97b1af-aarch64-1mara.txz

sndwvs · 06-27-2020, 12:40 AM

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.txt
echo -e "[all]\ndtparam=i2c_arm=on\ndtparam=spi=on\ndtparam=audio=on\n" >> /boor/config.txt

slarm64-current-aarch64-base-rootfs-20200528-5.7.6-raspberry_pi_4-build-20200627.img.xz
slarm64-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={
   ssid="access point"
   scan_ssid=1
   key_mgmt=WPA-PSK
   psk="password"
}

and
/etc/rc.d/rc.inet1.conf

Code:

IFNAME[4]="wlan0"
IPADDR[4]=""
NETMASK[4]=""
USE_DHCP[4]="yes"
#DHCP_HOSTNAME[4]="icculus-wireless"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
#WLAN_ESSID[4]=DARKSTAR
#WLAN_MODE[4]=Managed
#WLAN_RATE[4]="54M auto"
#WLAN_CHANNEL[4]="auto"
#WLAN_KEY[4]="D5A31F54ACF0487C2D0B1C10D2"
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
WLAN_WPA[4]="wpa_supplicant"