What most of you will know, and recognise, as the SARPi project websites have now gone. Vanished. Deleted. They went face to face with ´rm -rf´, and ´rm -rf´ won (with root priviledges).

Instead of three seperate websites supporting Slackware ARM on the Raspberry Pi 1, 2, & 3, respectively... there is now a brand new, pantheonic, SARPi website in their place.

New SARPi project URL: http://sarpi.fatdog.eu

This new SARPi website supplants the original sites and combines them all into one. If/when users try to access http://rpi.fatdog.eu, http://rpi2.fatdog.eu, and http://rpi3.fatdog.eu, they will be taken to the new SARPi website. The content of the original three sites has been incorporated and merged into this new website. So, Raspberry Pi users, whichever model they have, are still supported. All, except for the steenking RPi Zero.

Please let me know your thoughts and opinions on the new SARPi website. We´re always looking to improve and your feedback is very welcome.

Cheers!

The hyperlink for the -current version of kernel_rpi3-4.4.19-armv7-1_05Sep16_fd.txz is listed as "kernel_rpi3-4.4.19-armv7-1_Monday 5th September 2016_fd.txz" and throws a 404 error if you blindly copy the link like I just did :-)
(The correctly-named file is there, just the hyperlink is incorrect)

Oh dear. Sorry for the schoolboy error. This is me getting confused over ´release date´ and ´build date´ %TAGS%. Although, in this case they are the same date, the output is in a different format for each of these %TAGS%.

Thank you for this, CODOR. Good feedback. The link is fixed now.

I am looking for the .config file used to compile the current SARPI kernel (kernel_sarpi3-4.4.30-armv7-1_slackcurrent_fd0.txz). I need it to build my kernel modules.

I cloned the source from the git repository, checkout the used commit (from /boot/version-kernel_sarpi3.txt), make bcm2709_defconfig, modified CONFIG_LOCALVERSION="-v7-arm".

modinfo of the stock modules returns
modinfo of my module returns
Where does the additional + come from?

The kernel refuses to load the module with

If you have installed Slackware ARM using the 4.4.30 SARPi installer...

Or if not ...

The "-arm" suffix is put there to tell the difference between SARPi kernels and kernels which have been installed from the RPi repository (using rpi-update, for example). Kernels which have been installed using rpi-update always carry the "+" suffix (e.g. 4.4.30-v7+). I'm not sure why you have the additional "+" but my advice would be not to set a LOCALVERSION and test build without it. Also, 'uname -r' should tell you which kernel and modules you currently have installed and if that's telling you "4.4.30-v7+" then perhaps you have already updated using rpi-update and are trying to use modules for a kernel you had installed (4.4.30-v7-arm) rather than the one you have installed (4.4.30-v7+), but that's just a guess. "Invalid module format" usually means the modules were built for a previous kernel version. You need to check that your installed kernel version and the kernel-headers are the same. Then you can (re)compile your modules for the current kernel.

1 members found this post helpful.

Speaking of kernels, I notice
drwxr-xr-x 3 root root 4096 Oct 6 08:13 /lib/modules/4.4.21-v7-arm/
thru
drwxr-xr-x 3 root root 4096 Nov 26 18:20 /lib/modules/4.4.35-v7+/
17 folders about 855M.

Been using rpi-update, I've no experience with, is there something rpi-update switch, parameter to remove anything not current kernel, or is this a manual delete or just leave them alone?

Thanks

Just bear in mind that rpi-update is an 'apt-get -y install' type tool that may be convenient but it can seriously break things from time to time, depending on how it's used, and is not totally in-line with the Slackware way of maintaining/updating your system. There are various command-line options but to understand and learn how to use them you need to do some RTFM. The following command-option might be what you're looking for?

See https://github.com/Hexxeh/rpi-update for more information.

<edit> use WITH caution!

That's great Penthux, thanks, I will RTFM.

Success I have installed the fatdog kernel so I found 'config' in /usr/doc. Thanks Penthux.

The key was to build the kernel (no need to install/run it) so Module.symvers to be created. After that I built and loaded my module with no issues. Even though the kernel version strings differ:
uname -r: 4.4.30-v7-arm
modinfo: vermagic: 4.4.30-v7+ SMP mod_unload modversions ARMv7

Not related to my issue but a bit of information about the extra +:
Kernel local version

Good to hear. Well done.

The kernel version is 4.4.30 and anything after the "-" is the version suffix specified by CONFIG_LOCALVERSION= within the kernel .config file or by building with The suffix is set by the /usr/src/linux/scripts/setlocalversion script in your Linux kernel source directory and is well worth a read.