Slackware ARM on a Raspberry Pi - kernel 4.9
 

### IMPORTANT ANNOUNCEMENT! ###

These last few days have been HELL, after the stockpile of Jaffa cakes at the SARPi Citadel were depleted! Alas, with no viable opportunity to replenish the coffers, I was forced to go 'cold-turkey' for several days this week. However, yesterday a very lucrative offer at a local store was located and copious amounts of Jaffa cakes were procured. I'm very pleased to announce the state of emergency has now ended.

### End of important announcement. ###

Other news:
The SARPi Project has moved to the 4.9 kernel on the Raspberry Pi 1/2/3. I've finally found the time to finish what was started before Christmas 2016. All of you who've asked, "Why isn't SARPi using the 4.8/4.9 kernel?" have now been answered.

As always, SARPi images and packages can be downloaded from:

http://sarpi.fatdog.eu/index.php?p=downloads

NB: If you're using rpi-update to upgrade your kernel, kernel modules, and/or firmware, then please take time to read this page:

http://sarpi.fatdog.eu/index.php?p=rpiupdate

It explains a few things about upgrading 4.4.x/4.9.x kernels, as well as the firmware, on your Slackware ARM system on a Raspberry Pi device using rpi-update. Incidentally, you don't *have* to run the 4.9.x kernel, the RPi Foundation are still using the 4.4.x kernel as standard, for now. An announcement has been made that they will be moving to the 4.9 kernel, "soon".

ALL feedback is very welcome, especially negative feedback! :cool:

Exaga --

I am glad to hear about your score ( Jaffa Cakes ) :)

And I am even more gladder to hear about the 4.9.x Kernel :) :)

Heads up though. The two SARPi links are mangeled.

Thanks !

-- kjh

Thanks, kjhambrick. Fixed the links. :o

I installed the 4.9.5 kernel:
1. Downloaded the *.txz
2. mounted the /boot/ partition holding the kernel (had 4.4.21 there)
3. installed modules and kernel, firmware seemed to be up to date?
4. rebooted and
hang there every since
last line says something like vc-smi-init and hangs there?

works ! :)

The culprit was twofold:
1. me assuming the firmware is up to date (wasn't)
2. The package not being named so one could discern adjacent versions from it?

so my case is [SOLVED] (works now)
Kudos to the good sarpi maintainers, for their effort and dedication.
:hattip:

If anyone does not want to upgrade quite yet to the bleeding edge kernel rpi-update does offer the option to install the latest stable kernel the foundation offers with a simple: You'll be on the latest 4.4.x offerings right now at least, until 4.9.x is deemed stable. Not sure why you wouldn't mention on SARPi or here even, the semi-correct Slackware way to keep a stable kernel running but this is the most Slackware out of using the included packages which I myself am unsure if they run or not on a pi.

There are a few reasons why it's not mentioned on SARPi project website. First and foremost, if you want to know how to use rpi-update with all the prefixes, suffixes, and options; go and have a good read of the rpi-update website. The rpi-update tool is not in-line with the Slackware way and I would certainly argue that your "semi-correct" terminology is in fact in-correct (sic).

I would wholeheartedly recommend that users ignore rpi-update and upgrade their systems with the Slackware ARM packages provided from SARPi website. Or better still, build your own. Slackware for me is all about learning and experiencing Linux. I don't learn anything by typing 'rpi-update' and letting the tool do its thing. Neither will you.

SARPi website is just an initial guide. It's meant as a means to get you started with Slackware ARM on a Raspberry Pi. It doesn't cover everything and only scratches the surface of all things Slackware.