FatDog SARPi - one site to rule them all
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! :cool: |
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) |
Quote:
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 Code:
vermagic: 4.4.30-v7-arm SMP mod_unload modversions ARMv7 Code:
vermagic: 4.4.30-v7-arm+ SMP mod_unload modversions ARMv7 The kernel refuses to load the module with Code:
insmod: ERROR: could not insert module sevseg.ko: Invalid module format |
Quote:
Code:
cat /usr/doc/kernel_sarpi3-4.4.30_arm/config Code:
explodepkg kernel_sarpi3-4.4.30-armv7-1_slackcurrent_fd0.txz Quote:
|
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 |
Quote:
Code:
PRUNE_MODULES=1 rpi-update <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 |
Quote:
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 Code:
make config LOCALVERSION="-MY_SUFFIX" Code:
# append a plus sign if the repository is not in a clean |
All times are GMT -5. The time now is 04:03 PM. |