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.
Slackchat S02E23: We talk about the new root file system and swap labeling within the Slackware Installer on ARM, and the rationale behind it. We hack on the RTC detection code and discuss the integration for the Raspberry Pi 3 & 4.
Slackchat S02E23: We talk about the new root file system and swap labeling within the Slackware Installer on ARM, and the rationale behind it. We hack on the RTC detection code and discuss the integration for the Raspberry Pi 3 & 4.
Damned good episode.
So, allow me to add some clarity to the 3.3v vs 5v RTC conundrum. It's got nothing to do with the DS3231 RTC controller, as this operates on anything from 2.8-5.5v, but it has everything to do with the button battery. Some RTCs are designed to run from the 5v power but do not put any of it into the 3v button cell battery. Other RTCs that are designed to accommodate a rechargeable battery you will generally find that there is an in-line resistor on the 5v supply. This is because you need to supply more power to a rechargeable button cell than it outputs in order for it to 'trickle charge'. Putting 5v into a 3v lithium button battery is not recommended (it could ultimately be dangerous) whereas rechargeable button batteries are designed to handle it. Not all RTCs are designed to accommodate rechargeable button batteries. That's it, in a nutshell.
Specifying the split between system and GPU RAM on the Raspberry Pi devices is a config setting passed on to the boot loader (usually within the /boot/config.txt file) and I'm not sure if U-boot supports any of them. The dtoverlays can be called via commands and settings/parameters can be specified in the same way. U-boot doesn't handle (any?) dtoverlays so it might be tricky to invoke them without using the RPi bespoke boot-firmware. Other distros seem to have managed it by various means and methods in some degree.
Fun times! It's always a pleasure to record with Stuart.
Quote:
Specifying the split between system and GPU RAM on the Raspberry Pi devices is a config setting passed on to the boot loader (usually within the /boot/config.txt file) and I'm not sure if U-boot supports any of them. The dtoverlays can be called via commands and settings/parameters can be specified in the same way. U-boot doesn't handle (any?) dtoverlays so it might be tricky to invoke them without using the RPi bespoke boot-firmware. Other distros seem to have managed it by various means and methods in some degree.
The config variable that dictates how much memory to put where is gpu_mem=. I read that the rpi will pick the default memory allocation if nothing is in config.txt. The Raspberry Pi foundation ships a config.txt with gpu_mem=16 for the Pi 4. I will have to look that up how that works later on for the Pi 3. Anyway, one can only assume it will do the same with U-Boot because the boot rom reads all the files then hands off kernel / ramdisk / dtb loading to extlinux.
Fun times! It's always a pleasure to record with Stuart.
I'm sure it is. For me it was always about why we were doing the slack chat podcast rather than who I was doing it with. On that note, it might be prudent for you to rearrange your setup or consider using a different microphone. Stu comes through crystal clear but you are difficult to hear at the best of times. That's not your voice or accent, it's the quality that's the issue. Like you're using a built-in condenser mic on a laptop that makes you sound muffled with some small degree of background noise/interference.
Quote:
Originally Posted by mralk3
The config variable that dictates how much memory to put where is gpu_mem=. I read that the rpi will pick the default memory allocation if nothing is in config.txt. The Raspberry Pi foundation ships a config.txt with gpu_mem=16 for the Pi 4. I will have to look that up how that works later on for the Pi 3. Anyway, one can only assume it will do the same with U-Boot because the boot rom reads all the files then hands off kernel / ramdisk / dtb loading to extlinux.
I don't know how much of the RPi memory options is relevant (if at all) when using U-boot. The Raspberry Pi Documentation offers much information and guidance - although it's not always accurate or 100% reliable. Therefore testing, testing, and more testing, is always required. The available config.txt settings is a list longer than your arm and a veritable mindfield (sic) of information.
On that note, it might be prudent for you to rearrange your setup or consider using a different microphone. Stu comes through crystal clear but you are difficult to hear at the best of times. That's not your voice or accent, it's the quality that's the issue. Like you're using a built-in condenser mic on a laptop that makes you sound muffled with some small degree of background noise/interference.
I agree. I was using the Pinebook Pro built in microphone. I ordered a headset that should fix the muffling, background noise, and it will be here today.
almost watched it all now in three-four days, have a half episode left
The latest episode is a demonstration of what I do each day while testing any changes Stuart pushes out to me. Sometimes I have to improvise. I probably could have added some commentary or text to the video. It was recorded and edited on the RockPro64. Rendering the video took 2 hours. However, editing it took about 4 hours in Kdenlive.
The latest Slackware ARM podcast episode is a status update for Slackware AArch64.
In summary, it's almost baked and will be released to the supporters first as a 'thank you' for paying for the hardware.
As a follow up to the video regarding Raspberry Pi 3 support.. My raspberry pi 3 will start Xfce - both with and without the xorg.conf in /etc/X11. With compositing disabled, the removal of the xorg.conf, the video is more reliable and snappy. Xfce reports that VC4 V3D 2.1 driver is in use. Youtube loads in firefox and does not freeze like the Pi 4. I made no changes to config.txt in /boot.
Code:
test@rpithreeb:~$ w | head -n 1
10:37:08 up 21 min, 2 users, load average: 7.12, 4.35, 2.29
test@rpithreeb:~$ free -h
total used free shared buff/cache available
Mem: 907Mi 662Mi 37Mi 25Mi 207Mi 146Mi
Swap: 4.0Gi 432Mi 3.6Gi
KDE will not load in either run level 3 or 4 with the display manager (sddm).
The latest Slackware ARM podcast episode is a status update for Slackware AArch64.
In summary, it's almost baked and will be released to the supporters first as a 'thank you' for paying for the hardware.
One more follow up from one of the previous videos. Suspend to RAM (Sleep mode) will work in KDE, Xfce, and from a console. However, I'm not sure there is support for hibernation in U-boot or the ARM Trusted Firmware just yet.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
For me it was always about why we were doing the slack chat podcast rather than who I was doing it with. On that note, it might be prudent for you to rearrange your setup or consider using a different microphone. Stu comes through crystal clear but you are difficult to hear at the best of times. That's not your voice or accent, it's the quality that's the issue. Like you're using a built-in condenser mic on a laptop that makes you sound muffled with some small degree of background noise/interference. 
