LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 05-26-2018, 02:20 PM   #16
glorsplitz
Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 598

Original Poster
Rep: Reputation: 118Reputation: 118

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
 
Old 05-26-2018, 02:51 PM   #17
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 678

Rep: Reputation: 520Reputation: 520Reputation: 520Reputation: 520Reputation: 520Reputation: 520
Quote:
Originally Posted by glorsplitz View Post
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.
Old 05-26-2018, 03:08 PM   #18
Penthux
Member
 
Registered: Dec 2008
Location: Middlesbrough, UK
Distribution: Slackware
Posts: 228

Rep: Reputation: 67
i've a had beers

Quote:
Originally Posted by drmozes View Post
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 View Post
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 View Post
You need to follow the instructions for what ever separate project you followed.
Good advice!
 
1 members found this post helpful.
Old 05-26-2018, 04:14 PM   #19
glorsplitz
Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 598

Original Poster
Rep: Reputation: 118Reputation: 118
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
 
Old 05-27-2018, 02:24 AM   #20
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 678

Rep: Reputation: 520Reputation: 520Reputation: 520Reputation: 520Reputation: 520Reputation: 520
Quote:
Originally Posted by glorsplitz View Post
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.
Old 05-27-2018, 10:27 AM   #21
glorsplitz
Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 598

Original Poster
Rep: Reputation: 118Reputation: 118
That's great Stuart, exactly what I wanted to know, thank you.
 
Old 05-28-2018, 01:09 PM   #22
glorsplitz
Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 598

Original Poster
Rep: Reputation: 118Reputation: 118
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.
 
Old 05-29-2018, 04:00 PM   #23
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 678

Rep: Reputation: 520Reputation: 520Reputation: 520Reputation: 520Reputation: 520Reputation: 520
Quote:
Originally Posted by glorsplitz View Post
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.
Old 05-30-2018, 01:29 AM   #24
Penthux
Member
 
Registered: Dec 2008
Location: Middlesbrough, UK
Distribution: Slackware
Posts: 228

Rep: Reputation: 67
Quote:
Originally Posted by glorsplitz View Post
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.
Old 05-30-2018, 04:29 PM   #25
glorsplitz
Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 598

Original Poster
Rep: Reputation: 118Reputation: 118
drmozes, Penthux, thank you both!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: FSF dragging its feet on secure boot LXer Syndicated Linux News 0 01-02-2013 01:03 AM
Microsoft dragging its feet on Linux Secure Boot fix etech3 General 10 12-01-2012 07:32 AM
LXer: Microsoft dragging its feet on Linux Secure Boot fix LXer Syndicated Linux News 16 11-26-2012 10:15 AM
LXer: Howto: build Linux kernel module against installed kernel w/o full kernel source tree LXer Syndicated Linux News 0 09-03-2006 08:21 PM
Howto install Woody with latest kernel? hellwoofer Debian 3 08-13-2003 12:15 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 08:38 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration