http://test.fatdog.nl/dev/alchemy/sa...builds/4.8.15/ - AArch64 kernel and modules running with Slackware ARM current installer and packages for the Raspberry Pi 3.

First and foremost, merry Christmas to you all! May you all be blessed with good company, good wine, and good cheer, throughout this festive season.

Before you do download and install any of the AArch64 files, PLEASE take time to read the README.txt file first!

http://test.fatdog.nl/dev/alchemy/sa....15/README.txt


NB: This is an experimental development build from the "SARPi AArch64 Project" which has nothing at all to do with SARPi, per se. Some things still need work but the installer has been tested to a satisfactory level, considering this is an entirely experimental affair that's intended for the Raspberry Pi 3 ONLY! If you try to run it on a RPi1 or RPi2 it most likely won't even boot past the rainbow splash screen.

Try it, install it, play with it, (fix it?) or do what you can with it. All I ask is that you give me your opinion(s), thoughts, ideas, criticism(s), and any derision you feel is necessary/warranted.

MERRY CHRISTMAS! <3

<edit> in case any of you might be interested in cross compiling Slackware ARM binaries/packages/SlackBuilds (etc.) for aarch64 (arm64) architecture there's a pretty easy guide I wrote on SlackDocs for building and installing a GCC aarch64-linux cross-compiler on a Raspberry Pi - http://docs.slackware.com/howtos:har...cross-compiler

Well I gave it a whirl over Christmas in between replacing the hot water service, repairing the air conditioning and replacing the water pump on the ute. All at 36 degrees centigrade.


Boots to Login screen Ok but no mouse or keyboard found so can't check any logs etc, and no progress as a result

Also libtevent.so.0 and libtalloc.so.2 are missing so no samba.

No lan connection so no SSH.

An interesting exercise and a good effort on your part but back to Raspbian pro tem.


And only one processor showing in the raspberries

Happy New Year

Mike

THANK YOU! For the feedback, Mike.

It's strange that you had no keyboard/mouse/network. I was able to use this same installer image and packages to install and run Slackware ARM current on my RPi3, without any problems. It wouldn't have been made publicly available if it didn't work as a Slackware ARM installer.

Anybody else have the same or similar problems?

<edit> I installed Slackware ARM current using FTP server as source, and I installed remotely via SSH, using this image.

Hi Exaga.

Have tried re-downloading the installer and slackware current with same result. I don't suppose you fancy putting an image of your system up somewhere so that I can copy it and then compare with what I've got


Mike

upgraded my 4.4.37 to that kernel 4.8.15. Booted succesfully and I think all works good. Thanks!

Then I'm clueless as to why it's not working for you. Remember, this is just a test development release of an aarch64 kernel and modules so it's of no great significance or importance in the order of things. I know there's issues that need fixing and that's mainly due to RPi firmware and the fact that the installer is for 32-bit Slackware ARM current and not backed/supported by a 64-bit OS. So, with that in mind, I'm going to wait until there's further developments in those areas before putting any more serious time and effort into this project. I'm not planning to make any pre-built images available.

Good to know. Thanks for the feedback. As previously stated, there are known issues which exist. Just be mindful of this if/when you do encounter any problems.

I found the first big problem, some slackbuilds doesn't build

1 members found this post helpful.

Yes it's worth noting that Exaga has been sneaky here. This isn't an aarch64 build -- the above message means that there's no tool chain named that.

To make aarch64 a whole pile of work needs to be done to the source tree. Migrating to hard float was a short walk in the park compared to what's required for 64bit. I started modifying the source tree to accommodate aarch64, but it's not a case of compiling a few packages -- it's porting the entire OS.

Hmm, I think that I can't compile toolchain for my PI, anyone has it?

Looks like I've been rumbled. Oh well... "Guilty as charged, Your Honour!" [Does a runner...]

With a desire to drum up some enthusiasm in a Slackware aarch64/arm64 project from you wonderful Slackers I intentionally titled my opening post to that effect. Although, I thought I'd made it clear in the README file that what's available is an aarch64 kernel and modules running an installer for Slackware ARM current (which is the 32-bit hard float port), experience dictates that I should have appreciated that not everybody bothers to read the README file, or that not everybody is aware that there isn't a Slackware AArch64/ARM64 port available at this time. If you were expecting a full port of Slackware ARM running on 64-bit architecture then you only have me to blame for any consequential disappointment.

Yes, and there's a few more problems I could mention to add to that list.

New Slackware ARM current installer image and packages running an aarch64/arm64/armv8 kernel 4.9.3 are available for the RPi3.

Download them from here:

http://test.fatdog.eu/dev/alchemy/sa.../builds/4.9.3/

These have been tested and seem to be working as expected.

I know a few of you complained about having no keyboard or mouse when using the previous installer running an aarch64 kernel 4.8.15 but in both cases they have worked fine for me. I'll be especially interested to hear from users who are still experiencing issues of this nature.

PLEASE give me all your thoughts and any feedback; good, bad, or indifferent. It will be very much appreciated.

1 members found this post helpful.

So far so good. Both keyboaard and mouse are "alive". No chance to try anything else yet.
My last attempts with the first version of the installer must have failed due to a corrupt installer. Dd copied 2Gb ??????? From somewhere.

UTB

mike

I will try it, surely, although a tad further down the road. I'm busy with my Opi-PC and H3 ATM.

And i would appreciate video acceleration more than 64bit at the moment FWIW, but any advance is wholeheartedly welcome nonetheless.

There's been a firmware update, which seems to have fixed a few problems, since the installer and packages running an aarch64 kernel 4.8.15 was built.

That /dev/mmcblk0p3 partition was intended. dd didn't just write it from somewhere. The partition was present for a reason. Otherwise the initrd (i.e. Slackware ARM current installer) failed to load.