Slackware ARM aarch64 (arm64)

The SARPi project forum. For anything and everything relating to Slackware ARM on a Raspberry Pi 1, 2, and 3. This forum is NOT a replacement or substitute for the Slackware (ARM) forums on Linux Questions website! Please try to seek help there first about any issues you may be experiencing, or question you might have, before posting on here.
User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 195
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Slackware ARM aarch64 (arm64)

Postby Exaga » Sat Dec 24 2016 - 01:48:13

http://test.fatdog.eu/dev/alchemy/sarpi ... ds/4.8.15/

SARPi AArch64 Project (experimental) :cool:
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
chris.willing
Registered user
Registered user
Posts: 4
Joined: Thu Jan 12 2017 - 07:06:33

Re: Slackware ARM aarch64 (arm64)

Postby chris.willing » Sat Jan 14 2017 - 07:51:07

I tried experimenting with the AArch64 stuff. Running the installer all seemed to work as for normal systems. On reboot, I see only 1 raspberry displayed (the installer showed 4) and at the login prompt there is no response to the keyboard, therefore can't log in. After the first failure, I went through the whole process again - twice actually - with identical result.

Mounting the SD on another machine and examining the system's syslog shows that the firmware hasn't been registered correctly. Since the syslog file is pretty small, I've added it below (I hope that's OK - I don't know how to add it as an attachment).

The same hardware runs a normal sarpi system just fine.

Any insights would be appreciated.

chris

/var/log/syslog:

Code: Select all

 Jan  1 10:00:09 arm64test kernel: [    0.000000] /cpus/cpu@1: missing enable-method property
Jan  1 10:00:09 arm64test kernel: [    0.000000] /cpus/cpu@2: missing enable-method property
Jan  1 10:00:09 arm64test kernel: [    0.000000] /cpus/cpu@3: missing enable-method property
Jan  1 10:00:09 arm64test kernel: [    0.000000]     modules : 0xffffff8000000000 - 0xffffff8008000000   (   128 MB)
Jan  1 10:00:09 arm64test kernel: [    0.000000]     vmalloc : 0xffffff8008000000 - 0xffffffbebfff0000   (   250 GB)
Jan  1 10:00:09 arm64test kernel: [    0.000000]       .text : 0xffffff8008080000 - 0xffffff8008680000   (  6144 KB)
Jan  1 10:00:09 arm64test kernel: [    0.000000]     .rodata : 0xffffff8008680000 - 0xffffff8008810000   (  1600 KB)
Jan  1 10:00:09 arm64test kernel: [    0.000000]       .init : 0xffffff8008810000 - 0xffffff80088e0000   (   832 KB)
Jan  1 10:00:09 arm64test kernel: [    0.000000]       .data : 0xffffff80088e0000 - 0xffffff8008995800   (   726 KB)
Jan  1 10:00:09 arm64test kernel: [    0.000000]        .bss : 0xffffff8008995800 - 0xffffff8008a5648c   (   772 KB)
Jan  1 10:00:09 arm64test kernel: [    0.000000]     fixed   : 0xffffffbefe7fd000 - 0xffffffbefec00000   (  4108 KB)
Jan  1 10:00:09 arm64test kernel: [    0.000000]     PCI I/O : 0xffffffbefee00000 - 0xffffffbeffe00000   (    16 MB)
Jan  1 10:00:09 arm64test kernel: [    0.000000]     vmemmap : 0xffffffbf00000000 - 0xffffffc000000000   (     4 GB maximum)
Jan  1 10:00:09 arm64test kernel: [    0.000000]               0xffffffbf00000000 - 0xffffffbf00ec0000   (    14 MB actual)
Jan  1 10:00:09 arm64test kernel: [    0.000000]     memory  : 0xffffffc000000000 - 0xffffffc03b000000   (   944 MB)
Jan  1 10:00:09 arm64test kernel: [    0.000000] arm_arch_timer: WARNING: Invalid trigger for IRQ1, assuming level low
Jan  1 10:00:09 arm64test kernel: [    0.000000] arm_arch_timer: WARNING: Please fix your firmware
Jan  1 10:00:09 arm64test kernel: [    0.000000] arm_arch_timer: WARNING: Invalid trigger for IRQ2, assuming level low
Jan  1 10:00:09 arm64test kernel: [    0.000000] arm_arch_timer: WARNING: Please fix your firmware
Jan  1 10:00:09 arm64test kernel: [    0.090079] dmi: Firmware registration failed.
Jan  1 10:00:09 arm64test kernel: [    1.141492] Unable to detect cache hierarchy from DT for CPU 0
Jan  1 10:00:09 arm64test kernel: [    1.291785] mmc0: host does not support reading read-only switch, assuming write-enable
Jan  1 10:00:09 arm64test kernel: [    1.334557] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Jan  1 10:00:09 arm64test kernel: [    1.340642] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Jan  1 10:00:09 arm64test kernel: [    1.346969] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Jan  1 10:00:09 arm64test kernel: [    1.354667] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Jan  1 10:00:09 arm64test kernel: [    3.840455] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: May 27 2016 00:13:38 version 7.45.41.26 (r640327) FWID 01-df77e4a7
Jan  1 10:00:09 arm64test kernel: [    3.872359] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)
Jan  1 10:00:09 arm64test kernel: [    4.427871] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)
Jan  1 10:00:23 arm64test rpc.statd[624]: Failed to read /var/lib/nfs/state: Success
Jan  1 10:00:33 arm64test ntpd[653]: restrict: 'monitor' cannot be disabled while 'limited' is enabled
Jan  1 10:00:30 arm64test kernel: [    0.000000] /cpus/cpu@1: missing enable-method property
Jan  1 10:00:30 arm64test kernel: [    0.000000] /cpus/cpu@2: missing enable-method property
Jan  1 10:00:30 arm64test kernel: [    0.000000] /cpus/cpu@3: missing enable-method property
Jan  1 10:00:30 arm64test kernel: [    0.000000]     modules : 0xffffff8000000000 - 0xffffff8008000000   (   128 MB)
Jan  1 10:00:30 arm64test kernel: [    0.000000]     vmalloc : 0xffffff8008000000 - 0xffffffbebfff0000   (   250 GB)
Jan  1 10:00:30 arm64test kernel: [    0.000000]       .text : 0xffffff8008080000 - 0xffffff8008680000   (  6144 KB)
Jan  1 10:00:30 arm64test kernel: [    0.000000]     .rodata : 0xffffff8008680000 - 0xffffff8008810000   (  1600 KB)
Jan  1 10:00:30 arm64test kernel: [    0.000000]       .init : 0xffffff8008810000 - 0xffffff80088e0000   (   832 KB)
Jan  1 10:00:30 arm64test kernel: [    0.000000]       .data : 0xffffff80088e0000 - 0xffffff8008995800   (   726 KB)
Jan  1 10:00:30 arm64test kernel: [    0.000000]        .bss : 0xffffff8008995800 - 0xffffff8008a5648c   (   772 KB)
Jan  1 10:00:30 arm64test kernel: [    0.000000]     fixed   : 0xffffffbefe7fd000 - 0xffffffbefec00000   (  4108 KB)
Jan  1 10:00:30 arm64test kernel: [    0.000000]     PCI I/O : 0xffffffbefee00000 - 0xffffffbeffe00000   (    16 MB)
Jan  1 10:00:30 arm64test kernel: [    0.000000]     vmemmap : 0xffffffbf00000000 - 0xffffffc000000000   (     4 GB maximum)
Jan  1 10:00:30 arm64test kernel: [    0.000000]               0xffffffbf00000000 - 0xffffffbf00ec0000   (    14 MB actual)
Jan  1 10:00:30 arm64test kernel: [    0.000000]     memory  : 0xffffffc000000000 - 0xffffffc03b000000   (   944 MB)
Jan  1 10:00:30 arm64test kernel: [    0.000000] arm_arch_timer: WARNING: Invalid trigger for IRQ1, assuming level low
Jan  1 10:00:30 arm64test kernel: [    0.000000] arm_arch_timer: WARNING: Please fix your firmware
Jan  1 10:00:30 arm64test kernel: [    0.000000] arm_arch_timer: WARNING: Invalid trigger for IRQ2, assuming level low
Jan  1 10:00:30 arm64test kernel: [    0.000000] arm_arch_timer: WARNING: Please fix your firmware
Jan  1 10:00:30 arm64test kernel: [    0.090117] dmi: Firmware registration failed.
Jan  1 10:00:30 arm64test kernel: [    1.140840] Unable to detect cache hierarchy from DT for CPU 0
Jan  1 10:00:30 arm64test kernel: [    1.291779] mmc0: host does not support reading read-only switch, assuming write-enable
Jan  1 10:00:30 arm64test kernel: [    1.334176] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Jan  1 10:00:30 arm64test kernel: [    1.349241] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Jan  1 10:00:30 arm64test kernel: [    1.355337] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Jan  1 10:00:30 arm64test kernel: [    1.362612] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Jan  1 10:00:30 arm64test kernel: [   25.321680] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: May 27 2016 00:13:38 version 7.45.41.26 (r640327) FWID 01-df77e4a7
Jan  1 10:00:30 arm64test kernel: [   25.353214] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)
Jan  1 10:00:30 arm64test kernel: [   25.664637] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)
Jan  1 10:00:30 arm64test kernel: [   29.673809] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jan  1 10:00:45 arm64test ntpd[602]: restrict: 'monitor' cannot be disabled while 'limited' is enabled

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 195
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Slackware ARM aarch64 (arm64)

Postby Exaga » Sat Jan 14 2017 - 16:51:14

chris.willing wrote:I tried experimenting with the AArch64 stuff. Running the installer all seemed to work as for normal systems. On reboot, I see only 1 raspberry displayed (the installer showed 4) and at the login prompt there is no response to the keyboard, therefore can't log in. After the first failure, I went through the whole process again - twice actually - with identical result.

Mounting the SD on another machine and examining the system's syslog shows that the firmware hasn't been registered correctly. Since the syslog file is pretty small, I've added it below (I hope that's OK - I don't know how to add it as an attachment).

The same hardware runs a normal sarpi system just fine.

Any insights would be appreciated.

chris


Hi Chris,

Firstly, welcome to the FatDog forum. It's always good to see new people joining in. Especially seeing as you have an interest in AArch64 architecture. :good:

This little side-project was done with some haste, and I'd very much assert that there are more issues than I was initially aware of. The idea of the Slackware ARM aarch64 kernel was to gain interest from other users in an attempt to maybe combine efforts and further a project towards a full arm64/aarch64 port of the OS. In retrospect it seems to have gathered little interest with less support than a snowball in Hell.

However, you're not the first user to point out that there is no keyboard detected. Although on my RPi3, there are 4 cores active and the keyboard/mouse works as expected.

I will try to find the time to rebuild the images and packages, with a little more care and attention to help iron out whatever niggles exist. Hopefully.

I shall keep you posted. ;)
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
chris.willing
Registered user
Registered user
Posts: 4
Joined: Thu Jan 12 2017 - 07:06:33

Re: Slackware ARM aarch64 (arm64)

Postby chris.willing » Mon Jan 16 2017 - 02:05:17

I did some more experimenting - used the instructions at bottom of http://raspberrypi.stackexchange.com/qu ... -and-armv8 to build a kernel. At boot, the firmware now loads and the keyboard works so I can log in, set up wired network, run ntpdate etc. Running uname tells me aarch64 - so far so good.

My problem now is to set up the wifi. While investigating that, I found that no modules at all were loaded and any attempt to load a module using modprobe e.g. 'modprobe rfkill' results in:

Code: Select all

modprobe: ERROR: could not insert 'rfkill': Exec format error
yet running 'file' on rfkill.ko says its an ELF 64-bit LSB relocatable, ARM aarch64, version 1 (SYSV), BuildID[sha1]=70724........... i.e. seems to be the right format. I'm presuming that some devices won't be available unless the respective module is loaded and that's where I'm stuck at the moment.

Any ideas?

chris

User avatar
linicks
Registered user
Registered user
Posts: 125
Joined: Mon Oct 27 2014 - 20:26:01
Location: Pompey, England

Re: Slackware ARM aarch64 (arm64)

Postby linicks » Mon Jan 16 2017 - 21:40:53

Exaga wrote:In retrospect it seems to have gathered little interest with less support than a snowball in Hell.


:-@ Sorry, I haven't a 64 bit yet...

Nick ;)
https://linicks.net/

Q. What is the difference between a duck and an elephant?
A. You can't get down off an elephant.

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 195
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Slackware ARM aarch64 (arm64)

Postby Exaga » Mon Jan 16 2017 - 21:59:56

chris.willing wrote:My problem now is to set up the wifi. While investigating that, I found that no modules at all were loaded and any attempt to load a module using modprobe e.g. 'modprobe rfkill' results in:

Code: Select all

modprobe: ERROR: could not insert 'rfkill': Exec format error
yet running 'file' on rfkill.ko says its an ELF 64-bit LSB relocatable, ARM aarch64, version 1 (SYSV), BuildID[sha1]=70724........... i.e. seems to be the right format. I'm presuming that some devices won't be available unless the respective module is loaded and that's where I'm stuck at the moment.

Any ideas?

chris


I have lots of ideas, Chris. Most of them are outlandish and/or unorthodox. :lol:

First of all, I've compiled a new Slackware ARM current installer and packages running a 4.9.3 kernel built for aarch64 architecture. These are available from:

http://test.fatdog.eu/dev/alchemy/sarpi-aarch64/builds/4.9.3/

Let me know if you have any issues with the installer or packages because I spent some time making sure every thing works as intended, and apart from the expected timing errors when booting it's seems to work very well. There are still no WNIC drivers included though. I may look at that sometime in the future.

For the WNIC you could borrow the drivers from a Raspbian image. This post should help you in that respect. Then you could install the ftp://slackware.uk/slackwarearm/slackwarearm-current/extra/wicd/wicd-1.7.4-arm-1.txz package and get your wireless network up and running that way. Getting the WNIC up and running before installing Slackware ARM isn't something I've attempted. Although it might be fun to do so, just to see how easy it is or what problems I might encounter. In my experience the RPi3 onboard WNIC is somewhat unreliable and suffers from the 'cheap and nasty' syndrome. I find than many other very cheap USB wireless adapters (such as the Ralink RT5370) perform much better and are inherently more stable. The RPi3 WNIC tends to drop connection quite often for no reason at all, even when the signal strength is at maximum and the RPi3 is less than a metre from my router.

Yesterday evening, I was given the opportunity to install the aarch64 kernel 4.8.15 and modules on Aal's RPi3 and after rebooting everything seemed to run fine. So, perhaps instead of trying to install Slackware ARM current with the provided installer running the aarch64 kernel, simply upgrading the kernel and modules from a Slackware ARM current 32-bit system might prove more successful. You could then upgrade your RPi3 firmware using the 'rpi-update' command with the following options:

Code: Select all

root@myrpi3box:# BRANCH=next SKIP_KERNEL=1 rpi-update


Re: Building your own aarch64 kernel. If you're wanting to build an aarch64 cross-compiler for the Raspberry Pi 3 then take a look at this Slack Docs page:

http://docs.slackware.com/howtos:hardware:arm:gcc_aarch64_cross-compiler

Hope some of this helps you in your quest. :cool:
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
chris.willing
Registered user
Registered user
Posts: 4
Joined: Thu Jan 12 2017 - 07:06:33

Re: Slackware ARM aarch64 (arm64)

Postby chris.willing » Tue Jan 17 2017 - 09:33:17

The new 64bit installer with 4.9.3 kernel works perfectly. Everything just worked - including wifi (without any borrowing from elsewhere required). Thanks to all concerned for making it available.

chris

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 195
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Slackware ARM aarch64 (arm64)

Postby Exaga » Tue Jan 17 2017 - 11:49:15

chris.willing wrote:The new 64bit installer with 4.9.3 kernel works perfectly. Everything just worked - including wifi (without any borrowing from elsewhere required). Thanks to all concerned for making it available.

chris


Excellent. It works as planned then.

Happy days once again. :D
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
glorsplitz
Registered user
Registered user
Posts: 35
Joined: Sun Aug 07 2016 - 22:54:24

Re: Slackware ARM aarch64 (arm64)

Postby glorsplitz » Thu Jan 19 2017 - 02:58:38

/etc/slackpkg/mirrors didn't install with any ARM mirrors? I followed the README.txt, rebooted, got wireless going, system seems fine.

In slackware/ap/slackpkg-2.82.1-noarch-2.txz I found /usr/doc/slackpkg-2.82.1/mirrors-arm.sample pasted that into /etc/slackpkg/mirrors and now its running successfully.

Did I miss something? THANKS

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 195
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Slackware ARM aarch64 (arm64)

Postby Exaga » Thu Jan 19 2017 - 08:59:20

glorsplitz wrote:Did I miss something? THANKS


I'm not sure what you're missing, or what you think you've missed.
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
glorsplitz
Registered user
Registered user
Posts: 35
Joined: Sun Aug 07 2016 - 22:54:24

Re: Slackware ARM aarch64 (arm64)

Postby glorsplitz » Fri Jan 20 2017 - 02:44:10

The installed slackpkg mirrors didn't contain any ARM mirrors. I had to add them.

That didn't happen when I installed the hard/soft float slackware arm versions, there were ARM mirrors.

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 195
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Slackware ARM aarch64 (arm64)

Postby Exaga » Fri Jan 20 2017 - 09:18:09

glorsplitz wrote:The installed slackpkg mirrors didn't contain any ARM mirrors. I had to add them.

That didn't happen when I installed the hard/soft float slackware arm versions, there were ARM mirrors.


I'll look into that. Thanks. :)
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
glorsplitz
Registered user
Registered user
Posts: 35
Joined: Sun Aug 07 2016 - 22:54:24

Re: Slackware ARM aarch64 (arm64)

Postby glorsplitz » Sat Jan 21 2017 - 06:34:11

Yes I know this is experimental, if I'm need to RTFM something please point me where and I will follow up, I am trying to google things.

BRANCH=next rpi-update
Is that just the first time rpi-update is run after Slackware ARM aarch64 (arm64) is installed or every time?

After doing everything like Slackware ARM aarch64 (arm64) README.txt says to and 'BRANCH=next rpi-update'

Code: Select all

ls -la /lib/modules/
total 28
drwxr-xr-x 5 root root  4096 Jan 20 23:35 ./
drwxr-xr-x 8 root root 12288 Jan 18 09:27 ../
drwxr-xr-x 3 root root  4096 Jan 21  2017 4.9.3-v8-arm64/
drwxr-xr-x 3 root root  4096 Jan 20 23:35 4.9.4+/
drwxr-xr-x 3 root root  4096 Jan 20 23:35 4.9.4-v7+/

Code: Select all

aplay -l
aplay: device_list:268: no soundcards found...

I found somebody said to

Code: Select all

modprobe snd-bcm2835

Code: Select all

slocate snd-bcm2835
/lib/modules/4.9.4+/kernel/sound/arm/snd-bcm2835.ko
/lib/modules/4.9.4-v7+/kernel/sound/arm/snd-bcm2835.ko

Code: Select all

modprobe snd-bcm2835
modprobe: FATAL: Module snd-bcm2835 not found in directory /lib/modules/4.9.3-v8-arm64

lsusb comes up empty, I have usb keyboard and mouse connected.

Code: Select all

Linux sarpi64 4.9.3-v8-arm64 #1 SMP PREEMPT Mon Jan 16 01:24:18 GMT 2017 aarch64 GNU/Linux

Reinstall and not run rpi-update to get /lib/modules right?
THANKS!

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 195
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Slackware ARM aarch64 (arm64)

Postby Exaga » Sat Jan 21 2017 - 11:19:10

glorsplitz wrote:Yes I know this is experimental, if I'm need to RTFM something please point me where and I will follow up, I am trying to google things.

BRANCH=next rpi-update
Is that just the first time rpi-update is run after Slackware ARM aarch64 (arm64) is installed or every time?


You need to use the 'BRANCH=next rpi-update' command option each time you upgrade _IF_ you're running a 4.9.x kernel. Otherwise you will be downgrading to a 4.4.x kernel. The 4.4.x kernel is what the RPi Foundation are still distributing by default. This will change when the RPi Foundation move to the 4.9.x kernel. RTFM is always a prerequisite and not an option!

glorsplitz wrote:After doing everything like Slackware ARM aarch64 (arm64) README.txt says to and 'BRANCH=next rpi-update'

Code: Select all

ls -la /lib/modules/
total 28
drwxr-xr-x 5 root root  4096 Jan 20 23:35 ./
drwxr-xr-x 8 root root 12288 Jan 18 09:27 ../
drwxr-xr-x 3 root root  4096 Jan 21  2017 4.9.3-v8-arm64/
drwxr-xr-x 3 root root  4096 Jan 20 23:35 4.9.4+/
drwxr-xr-x 3 root root  4096 Jan 20 23:35 4.9.4-v7+/

Code: Select all

aplay -l
aplay: device_list:268: no soundcards found...

I found somebody said to

Code: Select all

modprobe snd-bcm2835

Code: Select all

slocate snd-bcm2835
/lib/modules/4.9.4+/kernel/sound/arm/snd-bcm2835.ko
/lib/modules/4.9.4-v7+/kernel/sound/arm/snd-bcm2835.ko

Code: Select all

modprobe snd-bcm2835
modprobe: FATAL: Module snd-bcm2835 not found in directory /lib/modules/4.9.3-v8-arm64

lsusb comes up empty, I have usb keyboard and mouse connected.

Code: Select all

Linux sarpi64 4.9.3-v8-arm64 #1 SMP PREEMPT Mon Jan 16 01:24:18 GMT 2017 aarch64 GNU/Linux

Reinstall and not run rpi-update to get /lib/modules right?
THANKS!


Which README.txt tells you to use 'rpi-update' to upgrade? http://test.fatdog.eu/dev/alchemy/sarpi ... README.txt (the latest README) makes no mention of it. If you are referring to http://sarpi.fatdog.eu/index.php?p=rpiupdate then that is for 32-bit ARM architecture and has NOTHING to do with the aarch64 kernel and modules!

Code: Select all

The SARPi AArch64 Project installer and packages are seperate from the main
SARPi Project website on http://sarpi.fatdog.eu and are not connected or
related in any way.


If you know the kernel/modules and firmware you're running are experimental AND you've also upgraded them using 'rpi-update' then it should be clear to you that some things simply will not work. The RPi Foundation aren't even building, distributing, or documenting, an aarch64 port. So, support for an aarch64 system via 'rpi-update' is simply out of the question at the moment. I don't know what 'rpi-update' is installing on your system, or what changes to configuration settings it makes. I don't even know if audio hardware is supported in the device tree blobs at this time. Software that's available from the RPi Foundation GitHub repository is not something that the SARPi Project supports, or maintains, or contributes towards, or is responsible for. You'd have to ask the maintainers of that software in order to get answers to your sound issues.

The whole point of this SARPi AArch64 Project is to get people interested in Slackware ARM64 and hopefully generate enough support to start working towards a full port. Solving problems created by users upgrading with 'rpi-update' is not within the scope of this project.
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
glorsplitz
Registered user
Registered user
Posts: 35
Joined: Sun Aug 07 2016 - 22:54:24

Re: Slackware ARM aarch64 (arm64)

Postby glorsplitz » Sat Jan 21 2017 - 16:32:12

Ok got it, thanks for following up.

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 195
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: Slackware ARM aarch64 (arm64)

Postby Exaga » Sun Feb 05 2017 - 18:34:57

Aarch64 kernel 4.9.8, kernel modules, firmware packages and Slackware ARM -current installer image for the Raspberry Pi 3

http://test.fatdog.eu/dev/alchemy/sarpi ... lds/4.9.8/

Let me know if you find any bugs or errors. :good:
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

Return to “SARPi Project - Slackware ARM on a Raspberry Pi”

Who is online

Users browsing this forum: CommonCrawl [Bot] and 0 guests