Raspberry Pi 4 - kernel 5.15.x available for testing on Slackware ARM
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
And when you do, make sure you let us know how long it all took, I'm curious.
Kernel took 1 hr to build. Modules I'm not completely sure. I started at 10pm and went to bed. When I woke up and checked at 6am it was completed. I used -j10 for compiling. I haven't testing it out yet to see if everything works. Need to make a backup just in case something goes wrong.
Last edited by kermitdafrog8; 11-19-2021 at 06:44 AM.
root@slackware:~# git clone --depth=1 --branch rpi-5.15.y git://github.com/raspberrypi/linux
root@slackware:~# cd linux
At that point there should be config for the source just cloned? If needing to change something before continuing?
The kernel source which is downloaded from kernel.org or Raspberry Pi GitHub repository is in a raw state. It has not been configured in any way and no .config file exists for that reason. Until 'make menuconfig' (etc.) is run and a kernel .config file is created the source is not prepared to build or compile anything. In this case running 'make bcm2709_defconfig' would create a .config file which will compile a kernel for the Raspberry Pi 2/3 ARM device architecture. Source that has already been compiled (for example, with the sarpi*-kernel-source packages) then a kernel .config file is included as it's generally accepted and good practice that it should be. Any changes that need to be carried out can then be made in the .config file before it is used to compile the kernel source.
Another way that changes might be implemented is by applying patches or including drivers (modules) to the kernel source, where certain hardware is not already supported.
Kernel took 1 hr to build. Modules I'm not completely sure. I started at 10pm and went to bed. When I woke up and checked at 6am it was completed. I used -j10 for compiling. I haven't testing it out yet to see if everything works. Need to make a backup just in case something goes wrong.
WOW! Using -j10 multijobs is way more than I have ever specified. It's a general rule of thumb that number of CPUs ,$(nproc) + half that amount, combined is acceptable. So, say if you have a 4 core CPU then -j6 would be fine. I always use -j4 because I don't care at all about speed, and it's a constant that I use to test and compare over devices and build jobs. i would assert that if you used -j4 or -j6 you might find that compiling the kernel and modules runs and completes a little quicker on the Raspberry Pi 3. The size of the /swap partition is also a factor. I usually have a 2G or 4G /swap for build systems using a microSD card for storage. On my Raspberry Pi 4 [4GB] R&D test machine the /swap partition is 8G because it's running with a 500GB SSD through a sata-usb3 adapter.
You will see from the Slackware ARM website's Beehive glimpse (build server farm) that Stuart is running (and building) kernel 5.15.4 on Slackware ARM and AArch64. So, the SARPi Project, which closely follows in the footsteps of his work, has updated its installers and system packages to kernel 5.15.x accordingly. The 'test' installers and packages running kernel 5.15.1, that where previously available in a seperate directory on the Slackware.UK repository, are no longer required and have been removed.
Incidentally, if you aren't aware of this inspired Beehive glimpse presentation which Stuart has created then I strongly advise you to bookmark the page and watch it like it's your favourite TV station.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.