AArch64 kernel and modules to install Slackware ARM current on the RPi3
Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
Thanks for this. I actually found it earlier via fatdog and have been running it for a few days without incident, except for one thing. I have a nodejs app which uses the node-rpio library which itself uses a bcm2835 library to access the GPIO. It depends on /dev/gpiomem for that access but it doesn't exist in the aarch64 system (whereas it does exist in the plain 32bit system). Checking in /proc/config.gz of the aarch64 system, I see that:
Code:
# Character devices
#
# CONFIG_BRCM_CHAR_DRIVERS is not set
# CONFIG_BCM2835_DEVGPIOMEM is not set
# CONFIG_BCM2835_SMI_DEV is not set
whereas the plain 32bit system (which works correctly) has:
So, they're both in that FatDog gang, eh?
Adding value to Rpis...
The only value you should place on Slackware ARM, SARPi or FatDog, or the Raspberry Pi, is what it's worth to you personally. I don't comprehend how any individual being part or party to anything adds significance or value, especially where the Raspberry Pi is concerned.
When the Raspberry Pi was first announced I saw a massive gaping hole of interest and support, where Slackware ARM was concerned, on the device. I fully intended to fill that void with the SARPi Project. Who is/was involved, who did what and when, is not important. The end result is all that matters and that it's done in a right, befitting, and appropriate way.
The only reason I put time and effort into the SARPi Project is because the Raspberry Pi is a massively popular ARM device. It might as well be a Banana Pi, Orange Pi, Beagleboard, or Odroid. The device has no meaning or value without the software to support it. Slackware ARM holds great value for me personally.
The only value you should place on Slackware ARM, SARPi or FatDog, or the Raspberry Pi, is what it's worth to you personally. I don't comprehend how any individual being part or party to anything adds significance or value, especially where the Raspberry Pi is concerned.
When the Raspberry Pi was first announced I saw a massive gaping hole of interest and support, where Slackware ARM was concerned, on the device. I fully intended to fill that void with the SARPi Project. Who is/was involved, who did what and when, is not important. The end result is all that matters and that it's done in a right, befitting, and appropriate way.
The only reason I put time and effort into the SARPi Project is because the Raspberry Pi is a massively popular ARM device. It might as well be a Banana Pi, Orange Pi, Beagleboard, or Odroid. The device has no meaning or value without the software to support it. Slackware ARM holds great value for me personally.
I'm known to quite often wrongly express my self
Yet those silly overpriced (or are they?) SBCs would be worth a dogs dinner if there weren't a Slackware for them.
I just wanted to point out that it's FatDog gang that adds the value that matters to the RPi-s.(At least to us, the Slackers )
So, is there even a remote chance we enjoy an mainline kernel for the RPi, any time soon?
By mainline i understand an kernel every one of us could build and deploy?
I just wanted to point out that it's FatDog gang that adds the value that matters to the RPi-s.(At least to us, the Slackers )
So, is there even a remote chance we enjoy an mainline kernel for the RPi, any time soon?
By mainline i understand an kernel every one of us could build and deploy?
The SARPi Project makes it easier for RPi users to install, configure, and run Slackware ARM. They do this by supplying installer images, packages and a comprehensive step by step "How To" tutorial, which is great for n00bz like me. If they hadn't already done it, someone else would surely have.
The remote chance to download and build/compile your own kernel has always existed. I've done it more times than I can count or remember.
I haven't heard/seen/read much feedback from the last release (running kernel 4.9.3) so I'm looking forward to all your unrestrained comments this time around.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
