|
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" |
Quote:
I'm glad to see that you made it work so fast, and that Xfce is also working great! Does the firmware upgrade procedure for 'boot from USB' differ in any way in case Slarm64 when compared to Raspbian? Eariler I had problems with WiFi on my RPi 3 and 4s too. Back then the solution was to take extract the Broadcom WLAN NIC firmware from Raspbian and install it in /lib/firmware. I believe the topics can still be found on this forum. (But of course it is perfectly possible that you are dealing with a totally different WiFi problem.) |
Quote:
Code:
rpi-eeprom-updateCode:
rpi-eeprom-update -a
Firmware: BCM4345/6 wl0: Mar 1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4 new Firmware: BCM4345/6 wl0: Mar 2 2020 23:30:41 version 7.45.202 (r724630 CY) FWID 01-72f6ece2 |
update kernel 5.7.6 v2
slarm64-current-aarch64-base-rootfs-20200528-5.7.6-raspberry_pi_4-build-20200628.img.zst slarm64-current-aarch64-base-rootfs-20200528-5.7.6-raspberry_pi_4-build-20200628.img.zst.md5 slarm64-current-aarch64-xfce-rootfs-20200528-5.7.6-raspberry_pi_4-build-20200628.img.zst slarm64-current-aarch64-xfce-rootfs-20200528-5.7.6-raspberry_pi_4-build-20200628.img.zst.md5 to use network-manager-applet Code:
chmod +x /etc/rc.d/rc.networkmanager && reboot |
Added installation instructions for slarm64 on USB-SSD/HDD
Code:
installation on a USB-SSD/HDD |
update
slarm64-current-aarch64-base-rootfs-20200628-5.8.2-raspberry_pi_4-build-20200829.img.zst slarm64-current-aarch64-base-rootfs-20200628-5.8.2-raspberry_pi_4-build-20200829.img.zst.md5 slarm64-current-aarch64-xfce-rootfs-20200628-5.8.2-raspberry_pi_4-build-20200829.img.zst slarm64-current-aarch64-xfce-rootfs-20200628-5.8.2-raspberry_pi_4-build-20200829.img.zst.md5 |
update raspberry pi firmware:
rpi-eeprom-r249.1a099a5-aarch64-1mara.txz rpi-userland-r806.f73fca0-aarch64-1mara.txz |
update
slarm64-current-aarch64-base-rootfs-20200901-5.8.11-raspberry_pi_4-build-20200926.img.zst slarm64-current-aarch64-base-rootfs-20200901-5.8.11-raspberry_pi_4-build-20200926.img.zst.md5 slarm64-current-aarch64-xfce-rootfs-20200901-5.8.11-raspberry_pi_4-build-20200926.img.zst slarm64-current-aarch64-xfce-rootfs-20200901-5.8.11-raspberry_pi_4-build-20200926.img.zst.md5 |
added initialization of bluetooth at boot.
Code:
[ 5.755256] Bluetooth: Core ver 2.22 |
update
slarm64-current-aarch64-base-rootfs-20201115-5.9.12-raspberry_pi_4-build-20201206.img.zst slarm64-current-aarch64-base-rootfs-20201115-5.9.12-raspberry_pi_4-build-20201206.img.zst.sha256 slarm64-current-aarch64-xfce-rootfs-20201115-5.9.12-raspberry_pi_4-build-20201206.img.zst slarm64-current-aarch64-xfce-rootfs-20201115-5.9.12-raspberry_pi_4-build-20201206.img.zst.sha256 |
update
slarm64-current-aarch64-base-rootfs-20201218-5.10.2-raspberry_pi_4-build-20201222.img.zst slarm64-current-aarch64-base-rootfs-20201218-5.10.2-raspberry_pi_4-build-20201222.img.zst.sha256 slarm64-current-aarch64-xfce-rootfs-20201218-5.10.2-raspberry_pi_4-build-20201222.img.zst slarm64-current-aarch64-xfce-rootfs-20201218-5.10.2-raspberry_pi_4-build-20201222.img.zst.sha256 |
update
added boot model 400 and cm4 slarm64-current-aarch64-base-raspberry_pi_4-5.10.3-build-20201228.img.zst slarm64-current-aarch64-base-raspberry_pi_4-5.10.3-build-20201228.img.zst.sha256 slarm64-current-aarch64-xfce-raspberry_pi_4-5.10.3-build-20201228.img.zst slarm64-current-aarch64-xfce-raspberry_pi_4-5.10.3-build-20201228.img.zst.sha256 slarm64-current-aarch64-base-raspberry_pi_4-5.10.3-build-20201229.img.zst slarm64-current-aarch64-base-raspberry_pi_4-5.10.3-build-20201229.img.zst.sha256 slarm64-current-aarch64-xfce-raspberry_pi_4-5.10.3-build-20201229.img.zst slarm64-current-aarch64-xfce-raspberry_pi_4-5.10.3-build-20201229.img.zst.sha256 |
update kernel 5.10.6
|
1 Attachment(s)
update kernel 5.10.9
new drivers for wifi realtek were added to the kernel, the desktop was also replaced with enlightenment. slarm64-current-aarch64-base-raspberry_pi_4-5.10.9-build-20210124.img.zst slarm64-current-aarch64-base-raspberry_pi_4-5.10.9-build-20210124.img.zst.sha256 slarm64-current-aarch64-enlightenment-raspberry_pi_4-5.10.9-build-20210124.img.zst slarm64-current-aarch64-enlightenment-raspberry_pi_4-5.10.9-build-20210124.img.zst.sha256 |
shot-1970-01-01_00-39-59.jpg, you didn't run ntp?
is mpv part of base install? |
Quote:
yes, mpv is included in prebuilt builds. |
Quote:
|
Quote:
but globally you can build with both xfce and enlightenment, this is just the first build with enlightenment. |
Quote:
|
kernel 5.11.0
slarm64-current-aarch64-base-raspberry_pi_4-5.11.0-build-20210218.img.zst slarm64-current-aarch64-base-raspberry_pi_4-5.11.0-build-20210218.img.zst.sha256 slarm64-current-aarch64-xfce-raspberry_pi_4-5.11.0-build-20210218.img.zst slarm64-current-aarch64-xfce-raspberry_pi_4-5.11.0-build-20210218.img.zst.sha256 |
kernel 5.10.23
|
kernel 5.11.10
slarm64-current-aarch64-base-raspberry_pi_4-5.11.10-build-20210329.img.zst slarm64-current-aarch64-base-raspberry_pi_4-5.11.10-build-20210329.img.zst.sha256 slarm64-current-aarch64-xfce-raspberry_pi_4-5.11.10-build-20210329.img.zst slarm64-current-aarch64-xfce-raspberry_pi_4-5.11.10-build-20210329.img.zst.sha256 |
update kernel 5.12.0
|
kernel 5.12.4
slarm64-current-aarch64-server-raspberry_pi_4-5.12.4-build-20210517.img.zst slarm64-current-aarch64-server-raspberry_pi_4-5.12.4-build-20210517.img.zst.sha256 slarm64-current-aarch64-xfce-raspberry_pi_4-5.12.4-build-20210517.img.zst slarm64-current-aarch64-xfce-raspberry_pi_4-5.12.4-build-20210517.img.zst.sha256 |
Hi sndwvs,
I don't wish to sidetrack this thread, but I encountered a previously unknown problem (at least for me). I have a 4 GB raspberry pi 4, and I would like to use an RTC. I own a number of them, and they all are this model. Until now used them happily but I recently switched from a 2 GB to a 4 GB RPi4, and also upgraded to kernel 5.10.0. The problem is that: In /boot/config.txt, I have Code:
dtparam=i2c_arm=onCode:
root@raspberry-pi-4:~# i2cdetect -y 1However when I try to execute the usual commands to activate the RTC, Code:
lsmod | grep -q i2c-bcm2708 || modprobe i2c-bcm2708Code:
[ 11.711634] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes readyCode:
[ 88.940468] i2c /dev entries driverI already spent a few hours googling around, but wasn't able to fix the problem. |
|
Quote:
Although I have to point out that the address had to be (or was) corrected to 0x68. Either way, thank you for helping me out! |
update kernel 5.13.0
|
slarm64-current-aarch64-server-raspberry_pi_4-5.13.1-build-20210710.img.zst
slarm64-current-aarch64-server-raspberry_pi_4-5.13.1-build-20210710.img.zst.sha256 slarm64-current-aarch64-xfce-raspberry_pi_4-5.13.1-build-20210710.img.zst slarm64-current-aarch64-xfce-raspberry_pi_4-5.13.1-build-20210710.img.zst.sha25 |
On a similar theme, I've noticed a lot of new files going in to Slarm64 recently (I rsync a local NAS with Slackware.UK), but slackpkg isn't detecting them. It looks as if the changelog isn't getting updated, nor are the checksums, which are throwing up md5 errors.
Not criticising, as I know its a lot of work! Just flagging up in case you were unaware. Slackware64-curent from the same source is fine. -- Pete |
Slackware.UK is lagging behind in sync. i checked a couple of other mirrors they show the same number of updates as in dl.slarm64.org
|
Yes, very odd! The packages themselves seem to be pretty up-to-date, its just the support files required by slackpkg that aren't being picked up! I've let Darren know!
-- Pete |
Looks like its fixed! Everything now showing up-to-date at Slackware.uk.
Guess we'll find out for sure when the next updates land...! ;) -- Pete |
kernel 5.13.9
slarm64-current-aarch64-server-raspberry_pi_4-5.13.9-build-20210816.img.zst slarm64-current-aarch64-server-raspberry_pi_4-5.13.9-build-20210816.img.zst.sha256 slarm64-current-aarch64-xfce-raspberry_pi_4-5.13.9-build-20210816.img.zst slarm64-current-aarch64-xfce-raspberry_pi_4-5.13.9-build-20210816.img.zst.sha256 |
kernel 5.14.0
slarm64-current-aarch64-server-raspberry_pi_4-5.14.0-build-20210902.img.zst slarm64-current-aarch64-server-raspberry_pi_4-5.14.0-build-20210902.img.zst.sha256 slarm64-current-aarch64-xfce-raspberry_pi_4-5.14.0-build-20210902.img.zst slarm64-current-aarch64-xfce-raspberry_pi_4-5.14.0-build-20210902.img.zst.sha256 slarm64-current-aarch64-enlightenment-raspberry_pi_4-5.14.0-build-20210902.img.zst slarm64-current-aarch64-enlightenment-raspberry_pi_4-5.14.0-build-20210902.img.zst.sha256 |
| All times are GMT -5. The time now is 01:29 AM. |