LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
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 08-10-2020, 02:11 PM   #16
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, RPi OS, Mint & Android
Posts: 12,855

Rep: Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677Reputation: 1677

Must be the same one I saw. The driver covered Every Ralink device in 2012.

Nothing wrong with the driver. The includes would need repointing a bit, because the headers moved; that's doable. It's inspiring to know that driver still sings.
 
Old 08-13-2020, 01:13 PM   #17
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Original Poster
Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
kernel 5.4.58 available to download

It has been a while since the last kernel 5.4.50 update from SARPi but hopefully it's been worth the wait.

Linux kernel 5.4.58 for Slackware ARM -current on the Raspberry Pi 2/3/4 is now available to download:

https://sarpi.fatdog.nl/index.php?p=downloads

Enjoy!
 
1 members found this post helpful.
Old 08-13-2020, 01:42 PM   #18
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Original Poster
Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Originally Posted by Exaga View Post
Linux kernel 5.4.58 for Slackware ARM -current on the Raspberry Pi 2/3/4 is now available to download:

https://sarpi.fatdog.nl/index.php?p=downloads
Obviously the kernel modules and boot-firmware have also been updated.
 
1 members found this post helpful.
Old 08-14-2020, 08:27 AM   #19
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Original Poster
Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Slackware ARM -current packages nginx 1.19.2 and JDK 8u261 updated.

Download them from: https://sarpi.fatdog.nl/index.php?p=...ads#currentpkg
 
1 members found this post helpful.
Old 09-06-2020, 05:14 AM   #20
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Original Poster
Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
SARPi updates & changes

Linux kernel 5.4.61 packages and installer for Slackware ARM -current on the Raspberry Pi 2/3/4 is now available to download:

https://sarpi.fatdog.nl/index.php?p=downloads

The kernel version-suffix on SARPi builds has been "-arm" pretty much since the get-go. From this day forward it has changed to "-sarpiX" - where "X" is the number of the Raspberry Pi version it's intended for. NOTE: with exception to the Raspberry Pi (1) where there is no "X" number and it's simply "-sarpi". Any future SARPi kernels that we build will carry this suffix. It makes sense to make the kernel instantly identifiable and recognisable in this way. For example, Slackware ARM -current on the Raspberry Pi 3 looks like this:

Code:
fatdog@dork:~$ uname -a
Linux dork.fatdog.eu 5.4.61-v7-sarpi3 #11 SMP Thu Sep 3 21:21:48 CEST 2020 armv7l BCM2835 GNU/Linux
Slackware ARM -current on the Raspberry Pi 4 looks like this:

Code:
root@torq:~# uname -a
Linux torq 5.4.61-v7l-sarpi4 #8 SMP Wed Sep 2 13:24:30 BST 2020 armv7l BCM2711 GNU/Linux
There have been multiple other changes but not that one would notice as they're related to the build process and such. Over the past week or so we've been working on "project engine v5.x" which is the 5th iteration of this build process which included a mammoth re-write and huge restructuring, with more Jaffa cakes involved than I will care to admit! That means be on the lookout for the usual steenking glitches or typos etc. but I've done my best to ensure there aren't any.

Last edited by Exaga; 09-06-2020 at 05:18 AM. Reason: meh
 
3 members found this post helpful.
Old 09-09-2020, 07:18 PM   #21
glorsplitz
Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 905

Rep: Reputation: 214Reputation: 214Reputation: 214
done

Quote:
Linux 5.4.61-v7-sarpi3 #27 SMP Sun Sep 6 06:33:57 BST 2020 armv7l unknown BCM2835 GNU/Linux
as far as any "usual steenking glitches or typos etc", you have a free pass, we'll let you know, please carry on and Thank you!
 
2 members found this post helpful.
Old 09-11-2020, 09:39 AM   #22
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Original Poster
Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Originally Posted by glorsplitz View Post
as far as any "usual steenking glitches or typos etc", you have a free pass, we'll let you know, please carry on and Thank you!
Thanks glorsplitz. It's going extremely well and we've added full logging capabilities and as a result it's not uncommon to have a build-log file size of +35MB

Build software is now in beta phase, but still undergoing testing. Shouldn't be too long before all the wrinkles are ironed out and any bugs dealt with. It's just finding them!
 
3 members found this post helpful.
Old 09-11-2020, 09:48 AM   #23
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Original Poster
Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Changes to /boot/config.txt [sarpi-boot-firmware*.txz]

Now when you install Slackware ARM on a Raspberry Pi using the SARPi installer you will find that the /boot/config.txt file is entirely #commented out. This means it's up to you (i.e. the admin) to decide which settings are required for your test-case. If you don't (for example) specify a value for 'gpu_ram' then default allocations will be set by the boot-firmware at boot time. It is good policy to keep an eye on the settings in this file in case they become supplanted by updates, etc.

The sarpi-boot-firmware*.txz package will never overwrite an existing /boot/config.txt file. Instead a /boot/config.txt.new file will be created so that the admin can decide what to do with it.

This is only something you should be concerned with for new Slackware ARM installations on a Raspberry Pi using the SARPi installer, or with sarpi-boot-firmware*.txz pkg updates/upgrades.
 
4 members found this post helpful.
Old 09-11-2020, 10:23 PM   #24
TheTKS
Member
 
Registered: Sep 2017
Location: The deep south... of Canada
Distribution: Slackware, Xubuntu, OpenBSD, elementary, Raspberry Pi OS, Puppy, TinyCore
Posts: 251

Rep: Reputation: 152Reputation: 152
Quote:
Originally Posted by Exaga View Post
Now when you install Slackware ARM on a Raspberry Pi using the SARPi installer you will find that the /boot/config.txt file is entirely #commented out. This means it's up to you (i.e. the admin) to decide which settings are required for your test-case....

The sarpi-boot-firmware*.txz package will never overwrite an existing /boot/config.txt file. Instead a /boot/config.txt.new file will be created so that the admin can decide what to do with it.

This is only something you should be concerned with for new Slackware ARM installations on a Raspberry Pi using the SARPi installer, or with sarpi-boot-firmware*.txz pkg updates/upgrades.
Thanks for the notification. Important for me to know since I did make modifications.

TKS
 
1 members found this post helpful.
Old 09-12-2020, 03:52 AM   #25
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Original Poster
Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Originally Posted by TheTKS View Post
Thanks for the notification. Important for me to know since I did make modifications.
Hi TKS, overwriting the /boot/config.txt shouldn't ever be a problem as far as the sarpi-boot-firmware*.txz pkg goes. For instance, on this system - I've been using a lot for testing recently - the /boot/config.txt is dated 2020-08-14 and the /boot/config.txt.new is dated 2020-09-12, and I have updated it with *sarpi*.txz pkgs many times over the past month. The sarpi-boot-firmware*.txz pkg is designed to overwrite the /boot/config.txt.new on installation if a /boot/config.txt is found - which it should always be. So, you shouldn't worry, I think. It's been many years since I updated using rpi-update but if it works the same as it used to do then config.txt might be overwritten or replaced via that method.

Users should decide their own settings in the /boot/config.txt file, as they need them. No default config.txt settings are required for the RPi to boot. So, in order to keep things simple and introduce conformity across the board, I'm happy to remove the conundrum of, "Which are the best ad-hoc config.txt settings?" from the equation as far as SARPi is concerned. Because the 'keep it simple' answer is, "No settings at all".

Last edited by Exaga; 09-12-2020 at 04:02 AM. Reason: hmm Saturday
 
2 members found this post helpful.
Old 09-19-2020, 07:44 PM   #26
jozwiak
LQ Newbie
 
Registered: Aug 2020
Posts: 9

Rep: Reputation: Disabled
I haven't noticed anyone commenting on the new allowed frequencies on the sarpi4 kernel. Previously, the Pi went up 25% when it needed more than 0.6G, up 33% when it needed more than .75G, and up 50% when it needed more than 1G. Now it just moves through all 10 frequencies, and that slows down the scaling governors, creating micro-hesitations.

Here is my solution:

#!/bin/sh

Code:
echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 98 > /sys/devices/system/cpu/cpufreq/conservative/up_threshold
echo 64 > /sys/devices/system/cpu/cpufreq/conservative/down_threshold 
echo 36 > /sys/devices/system/cpu/cpufreq/conservative/freq_step
 
Old 09-20-2020, 03:07 AM   #27
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Original Poster
Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Originally Posted by jozwiak View Post
I haven't noticed anyone commenting on the new allowed frequencies on the sarpi4 kernel. Previously, the Pi went up 25% when it needed more than 0.6G, up 33% when it needed more than .75G, and up 50% when it needed more than 1G. Now it just moves through all 10 frequencies, and that slows down the scaling governors, creating micro-hesitations.

Here is my solution:

#!/bin/sh

Code:
echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 98 > /sys/devices/system/cpu/cpufreq/conservative/up_threshold
echo 64 > /sys/devices/system/cpu/cpufreq/conservative/down_threshold 
echo 36 > /sys/devices/system/cpu/cpufreq/conservative/freq_step
Really not sure what this post is intended to achieve. Are you making a complaint that nobody has commented on this? Or are you highlighting a problem and/or offering a solution? Or are you just sharing information on CPU-scaling? Please clarify in full. Thanks.
 
Old 09-20-2020, 01:18 PM   #28
jozwiak
LQ Newbie
 
Registered: Aug 2020
Posts: 9

Rep: Reputation: Disabled
Quote:
Originally Posted by Exaga View Post
Really not sure what this post is intended to achieve. Are you making a complaint that nobody has commented on this? Or are you highlighting a problem and/or offering a solution? Or are you just sharing information on CPU-scaling? Please clarify in full. Thanks.
I am highlighting a problem and/or offering a solution.

To clarify in full, I also looked at the Raspberry Pi foundation and found no mention of the change, which I would assume is part of the proprietary blobs. They still insist the Pi has .6, .75, 1, 1.5 in their documentation.

Thanks,

Jim Jozwiak
 
Old 09-22-2020, 08:08 AM   #29
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Original Poster
Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Originally Posted by Desiderius View Post
Thanks for your answer @Exaga !

In the mean time, I have succedded to buy the ChronoDot !

SO I will follow the instructions of your tutorial
The Slackware ARM on a Raspberry Pi "RTC guide" has been revised and updated! It now reflects a more modern device-tree standard, amongst other new things - but some of the old guide has been left in, as a "Legacy Guide" for anyone who might still be running non-dt, and for posterity.

View the RTC guide here: https://sarpi.fatdog.eu/index.php?p=chronodot-rtc
 
1 members found this post helpful.
Old 09-30-2020, 06:15 AM   #30
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Original Poster
Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
SARPi kernel 5.4.68 updates

SARPi installer and packages have been updated using kernel 5.4.68 - which includes the Raspberry Pi (1).

Available here: https://sarpi.fatdog.eu/index.php?p=downloads

Enjoy!
 
2 members found this post helpful.
  


Reply

Tags
docker, nginx, raspberry pi, slackware arm


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
[SOLVED] Sarpi / Raspberry (RPi 3) - sound issue under 5.4.18-v7-arm eduardr Slackware - ARM 11 02-28-2020 04:12 AM
SARPi - Slackware ARM 14.2 installer images and packages updated to kernel 5.4.x. Exaga Slackware - ARM 2 01-26-2020 12:44 PM
SARPi - Slackware ARM -current installer images & packages updated to kernel 5.4.x Exaga Slackware - ARM 5 01-22-2020 04:35 PM
SARPi website new URL - sarpi.co.uk Exaga Slackware - ARM 4 01-28-2018 06:36 PM

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

All times are GMT -5. The time now is 06: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
Open Source Consulting | Domain Registration