Slackware - ARM This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
|
05-26-2018, 02:20 PM
|
#16
|
Senior Member
Registered: Dec 2002
Distribution: slackware!
Posts: 1,398
Original Poster
|
Since I've been using rpi-update per sarpi and not doing kernels slackware way,
when ChangeLog.txt says something like
a/kernel-firmware-20180518_2a9b2cf-noarch-1.txz: Upgraded.
a/kernel-modules-armv7-4.16.11_armv7-arm-1.txz: Upgraded.
a/kernel_armv7-4.16.11-arm-1.txz: Upgraded.
does slackpkg do the copying over the new firmware, overlays, dtbs, kernel, etc?
I've looked, maybe not hard enough, for how slackwarearm kernel update gets installed.
Thanks
|
|
|
05-26-2018, 02:51 PM
|
#17
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,708
|
Quote:
Originally Posted by glorsplitz
Since I've been using rpi-update per sarpi and not doing kernels slackware way,
when ChangeLog.txt says something like
a/kernel-firmware-20180518_2a9b2cf-noarch-1.txz: Upgraded.
a/kernel-modules-armv7-4.16.11_armv7-arm-1.txz: Upgraded.
a/kernel_armv7-4.16.11-arm-1.txz: Upgraded.
does slackpkg do the copying over the new firmware, overlays, dtbs, kernel, etc?
I've looked, maybe not hard enough, for how slackwarearm kernel update gets installed.
Thanks
|
Slackware ARM does not support the RPis, and those kernels have no support for them (so you don't need to use those packages).
You need to follow the instructions for what ever separate project you followed.
|
|
2 members found this post helpful.
|
05-26-2018, 03:08 PM
|
#18
|
Member
Registered: Dec 2008
Location: Middlesbrough, UK
Distribution: Slackware
Posts: 264
Rep:
|
i've a had beers
Quote:
Originally Posted by drmozes
Slackware ARM does not support the RPis,
|
... and Raspberry Pi (Trading) Ltd does not seem to support, or acknowledge Slackware ARM; because they like pointy-n-clicky things for NOOBS.
Quote:
Originally Posted by drmozes
and those kernels have no support for them (so you don't need to use those packages).
|
I'll buILD ONE!
Quote:
Originally Posted by drmozes
You need to follow the instructions for what ever separate project you followed.
|
Good advice! 
|
|
1 members found this post helpful.
|
05-26-2018, 04:14 PM
|
#19
|
Senior Member
Registered: Dec 2002
Distribution: slackware!
Posts: 1,398
Original Poster
|
Let me rephrase, if using Slackware ARM on a Slackware ARM supported device
when ChangeLog.txt says something like
a/kernel-firmware-20180518_2a9b2cf-noarch-1.txz: Upgraded.
a/kernel-modules-armv7-4.16.11_armv7-arm-1.txz: Upgraded.
a/kernel_armv7-4.16.11-arm-1.txz: Upgraded.
does slackpkg do the copying over the new firmware, overlays, dtbs, kernel, etc?
I'm not interested in doing this with my rpi3.
Last edited by glorsplitz; 05-26-2018 at 08:25 PM.
Reason: clarification
|
|
|
05-27-2018, 02:24 AM
|
#20
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,708
|
Quote:
Originally Posted by glorsplitz
Let me rephrase, if using Slackware ARM on a Slackware ARM supported device
when ChangeLog.txt says something like
a/kernel-firmware-20180518_2a9b2cf-noarch-1.txz: Upgraded.
a/kernel-modules-armv7-4.16.11_armv7-arm-1.txz: Upgraded.
a/kernel_armv7-4.16.11-arm-1.txz: Upgraded.
does slackpkg do the copying over the new firmware, overlays, dtbs, kernel, etc?
|
To upgrade these packages, you run upgradepkg and it's all taken care of -- but _only_ on supported devices where /boot is on a Linux file system (NOT 'FAT' or some variant of), and where you followed the installation instructions (which means that the u-boot configuration has hard coded DTB, initrd and kernel image file names, and the above packages are able to make symlinks (hence why no FAT) to point those static file names to the versioned files).
slackpkg runs upgradepkg, so it's all taken care of (unless you black listed kernel packages, which I don't suggest doing if you're using a supported device).
"Overlays" is solely a RPi concept.
|
|
1 members found this post helpful.
|
05-27-2018, 10:27 AM
|
#21
|
Senior Member
Registered: Dec 2002
Distribution: slackware!
Posts: 1,398
Original Poster
|
That's great Stuart, exactly what I wanted to know, thank you.
|
|
|
05-28-2018, 01:09 PM
|
#22
|
Senior Member
Registered: Dec 2002
Distribution: slackware!
Posts: 1,398
Original Poster
|
latest SARPi installer image for Slackware ARM -current on a Raspberry Pi 3 uses kernel 4.14.43 and was built on Sun, 27 May 2018
Current (pre-release) ChangeLog for ARM Thu May 24 08:08:08 UTC 2018 says
a/kernel_armv7-4.16.11-arm-1.txz: Upgraded.
The difference in kernel versions means there might be some mileage variance when rebuilding whatever? Like something SBo might work for slackwarearm-current but not SARPi?
I stopped fussing with kernels a while back and may build something SBo so I'm not up on kernel stuffs.
Thanks
Last edited by glorsplitz; 05-28-2018 at 01:11 PM.
|
|
|
05-29-2018, 04:00 PM
|
#23
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,708
|
Quote:
Originally Posted by glorsplitz
The difference in kernel versions means there might be some mileage variance when rebuilding whatever? Like something SBo might work for slackwarearm-current but not SARPi?
|
As far as I know, as long as the kernel-headers are the same as the running Kernel, it's fine.
|
|
1 members found this post helpful.
|
05-30-2018, 01:29 AM
|
#24
|
Member
Registered: Dec 2008
Location: Middlesbrough, UK
Distribution: Slackware
Posts: 264
Rep:
|
Quote:
Originally Posted by glorsplitz
latest SARPi installer image for Slackware ARM -current on a Raspberry Pi 3 uses kernel 4.14.43 and was built on Sun, 27 May 2018
Current (pre-release) ChangeLog for ARM Thu May 24 08:08:08 UTC 2018 says
a/kernel_armv7-4.16.11-arm-1.txz: Upgraded.
The difference in kernel versions means there might be some mileage variance when rebuilding whatever? Like something SBo might work for slackwarearm-current but not SARPi?
|
The reason why SARPi uses the 4.14.x kernel is mainly because of this reason: https://www.raspberrypi.org/forums/v...06400#p1279141
|
|
1 members found this post helpful.
|
05-30-2018, 04:29 PM
|
#25
|
Senior Member
Registered: Dec 2002
Distribution: slackware!
Posts: 1,398
Original Poster
|
drmozes, Penthux, thank you both!
|
|
|
All times are GMT -5. The time now is 04:19 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|