[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
slackwarearm:cstmz_kernel_rpi [2023/06/08 16:33 (UTC)] – mozesslackwarearm:cstmz_kernel_rpi [2023/07/13 15:01 (UTC)] (current) – mozes
Line 6: Line 6:
 | Version | 1.00, June 2023 | | Version | 1.00, June 2023 |
 | Author | Stuart Winter <mozes@slackware> | | Author | Stuart Winter <mozes@slackware> |
-| See also | * [[slackwarearm:cstmz_kernel|Slackware AArch64 Kernel customisation and self-build options]] * [[slackwarearm:cstmz_kernel_rpi_selfbuild|Self-build Raspberry Pi Slackware Kernel packages]] |+| See also | <WRAP> 
 +  * [[slackwarearm:cstmz_kernel|Slackware AArch64 Kernel customisation and self-build options]] 
 +  * [[slackwarearm:cstmz_kernel_rpi_selfbuild|Self-build Raspberry Pi Slackware Kernel packages]] 
 +</WRAP> |
  
  
Line 16: Line 19:
  
 Raspberry Pi's are **only** intended to run the vendor's own Linux distribution, or to run as an 'Appliance' using the Raspberry Pi Linux Kernel fork. Raspberry Pi's are **only** intended to run the vendor's own Linux distribution, or to run as an 'Appliance' using the Raspberry Pi Linux Kernel fork.
- +Consequently, the upstream mainline Linux Kernel in which support for the Raspberry Pi is fragile, prone to breaking without warning and has a feature disparity (most noticeably for hardware support).  Slackware uses official upstream repositories/releases and has a no-patch policy.  As such, the recommendation of using the vendor's own Kernel fork is far outside the scope of Slackware.
-As a consequence, the upstream mainline Linux Kernel in which support for the Raspberry Pi is fragile, prone to breaking without warning and has a feature disparity (most noticeably for hardware support).  Slackware uses official upstream repositories/releases and has a no-patch policy.  As such, the recommendation of using the vendor's own Kernel fork is far outside the scope of Slackware.+
  
 If you are considering purchasing a Raspberry Pi and have not yet done so, take heed of this caution and you may wish to consider purchasing one of the other Hardware Models.  Over time the support for the Raspberry Pi will continue to appear in the main stream Kernel. If you are considering purchasing a Raspberry Pi and have not yet done so, take heed of this caution and you may wish to consider purchasing one of the other Hardware Models.  Over time the support for the Raspberry Pi will continue to appear in the main stream Kernel.
Line 23: Line 25:
 ==== The workaround ==== ==== The workaround ====
  
-Install using the official Slackware Linux installer and official Kernel packages, then migrate to the RPi Kernel fork packages from within the Operating System proper (e.g. when the OS has been installed and booted) using the instructions within this document.+  * Install using the [[slackwarearm:inst|official Slackware Linux installer]] 
 +  * Migrate to the RPi Kernel fork packages from within the Operating System proper (i.e. when the OS has been installed and booted) using the instructions within this document.
  
  
Line 142: Line 145:
 == Verify the packages == == Verify the packages ==
  
-<code>$ gpg --verify-files *.asc</code>+<code>$ gpg --verify-files rpi-kernel-fork/*.asc</code> 
 + 
 +<note tip>If you see validation errors such as ''gpg: key 1623FC33 was created 1402910394 seconds in the future (time warp or clock problem)'' your machine's clock is wrong.</note>
  
 === Transition to the new Kernel packages === === Transition to the new Kernel packages ===
Line 166: Line 171:
 === Warnings during upgrade === === Warnings during upgrade ===
  
-The packages of the Raspberry Pi Kernel fork are configured using the default Kernel configuration for that Hardware Model, rather than the generic configuration for Slackware.  As a consequence, there is a feature disparity between the two Kernels which presents itself during the transition in the following ways.+As a consequence of the Kernel configuration disparity, this warning message presents itself during the transition in the following ways:
  
 //These warnings are harmless and should be ignored.// //These warnings are harmless and should be ignored.//
Line 211: Line 216:
 These are harmless and should be ignored. These are harmless and should be ignored.
  
-{{:slackwarearm:slackarm-rpi-kernel-fork-missing-mods.png?400|}}+{{:slackwarearm:slackarm-rpi-kernel-fork-missing-mods.png?600|}}
  
 === Warnings once the OS has booted === === Warnings once the OS has booted ===
 +
 +This message will appear on the Virtual Console every few minutes, and is due to the serial console configuration within the Kernel.
  
 <code>init: Id "s0" respawning too fast: disabled for 5 minutes</code> <code>init: Id "s0" respawning too fast: disabled for 5 minutes</code>
  
-This is due to the serial console configuration and will be outputted to the Virtual Console. 
-It's harmless and can be ignored or disabled. 
  
 +It's harmless and can be ignored or disabled:
  
 <code>root@rpi:~# nano /etc/inittab</code> <code>root@rpi:~# nano /etc/inittab</code>
Line 273: Line 279:
 == Upgrade to the official Slackware Kernel packages == == Upgrade to the official Slackware Kernel packages ==
  
-{{:slackwarearm:slackarm-switchbackofficialkernel.png?200|}}+<code> 
 +root@rpi:~# slackpkg update 
 +root@rpi:~# slackpkg upgrade-all 
 +</code> 
 + 
 +{{:slackwarearm:slackarm-switchbackofficialkernel.png?600|}} 
 + 
 + 
 +You will see the same errors emitted as during the initial transition.  These are harmless and can be ignored. 
 + 
 +<code> 
 +WARNING: /boot/dtb-6.1.32/overlays/wm8960-soundcard.dtbo changed after package installation. 
 +  --> Deleting /boot/dtb-6.1.32/overlays/wm8960-soundcard.dtbo 
 +  --> Deleting empty directory /boot/dtb-6.1.32/overlays/ 
 +Verifying package kernel_armv8-6.1.32-aarch64-1.txz. 
 +Installing package kernel_armv8-6.1.32-aarch64-1.txz: 
 +PACKAGE DESCRIPTION: 
 +# Linux kernel for the 64-bit AArch64/ARM64 platform. 
 +# 
 +# This is a generic Linux kernel for systems that are powered by an 
 +# ARM CPU that supports the ARMv8 or higher chip set. 
 +#  
 +# 
 +#  
 +# 
 +# Other drivers (such as additional file system support) may be 
 +# loaded as modules.  See /etc/rc.d/rc.modules for examples. 
 +Executing install script for kernel_armv8-6.1.32-aarch64-1.txz. 
 +modinfo: ERROR: Module algif_hash not found. 
 +modinfo: ERROR: Module algif_skcipher not found. 
 +modinfo: ERROR: Module bcm2835_codec not found. 
 +modinfo: ERROR: Module bcm2835_isp not found. 
 +modinfo: ERROR: Module rpivid_hevc not found. 
 +modinfo: ERROR: Module vc_sm_cma not found. 
 +modinfo: ERROR: Module uio_pdrv_genirq not found. 
 +modinfo: ERROR: Module uio not found. 
 +modinfo: ERROR: Module nvmem_rmem not found. 
 +Package kernel_armv8-6.1.32-aarch64-1.txz installed. 
 +Package kernel_armv8-6.1.32-aarch64-1_rpi upgraded with new package ./kernel_armv8-6.1.32-aarch64-1.txz. 
 +Searching for NEW configuration files... 
 +                No .new files found. 
 +</code> 
 + 
 +Finally, reboot.

Trace:

slackwarearm:cstmz_kernel_rpi ()