Season 2, Ep. 19. Slackathon - Raspberry Pi4 & Pinebook Pro.
Summary: Quote:
|
Season 2, Episode 20 - Slackathon - Raspberry Pi 4.
We're finalising the RaspberryPi4 support in Slackware. |
Quote:
What struck me was the amount of work involved in setting up the system to run the Slackware AArch64 installer. Although u-boot seems overly complicated you had it all worked out before you rebooted and loaded it, which was kind of impressive - but rather you than me, as I prefer the easy life. lol :D Can't say I've had any problems with the Kingston SDCG3 "Canvas Go!" range of SD cards I currently use. I run Slackware ARM and build all the installers and pkgs on them repeatedly. Cheaper and lower quality SD cards do tend to fail more frequently, in my experience. I'll assume it'll be a similar affair with Slackware AArch64 but time will surely tell. It's all looking really great Stu. Can't wait until you release it into the wild and I can put the fruits of your labour to very good use. :cool: |
Quote:
That's all you do. The Micro SD card is transformed into the Slackware OS /boot partition automatically. You didn't see dding the installer in the video because I already had it on another SD card, so I just booted it. Quote:
What's more, the U-Boot config for the RockPro64/Pinebook Pro will boot the RPi without modification (assuming the same block device is used for the root fs). You're going to love it! |
Hi Stuart, in your last video i saw at the end that the default's target block device is set to /dev/mmcblk1... Why not conserving the standard /dev/mmcblk0.. as in SARPi's installer? ;)
|
Quote:
Quote:
Quote:
Maybe the way in which people expect the SARPi installer to work is about to change. First we'll wait until Stuart releases Slackware AArch64. Then take it from there. Slackware leads and SARPi follows. That is the order of things. ;) |
Quote:
|
Quote:
Code:
[ Build host: Linux mojo.arm.slackware.com 5.15.10-armv7 #1 SMP Fri Dec 17 10:40:25 GMT 2021 armv7l Allwinner sun8i Family GNU/Linux ] |
Quote:
Re the numbering of mmcblk --I did explain in the video about that. U-Boot has detected the single Micro SD card as number 1, as has Linux. However it also occasionally appears as 0. I don't know why at the moment and it's low importance. However, one benefit of it is that it highlighted a bug in /sbin/probe in the installer, which I fixed and is merged back into Slackware upstream. |
Quote:
|
Quote:
The other is having a consistent approach across all Hardware Models that can be managed by the OS toolset without an array of exceptions. That's my approach for Slackware anyway! |
I've been playing around with the RPi boot loader and it'll be very easy to support using it instead of U-Boot with seamless Kernel upgrades; as I can add a hook into the Kernel package's post installation script to call another within /boot/local which updates the Kernel, OS InitRD and DTBs on the RPI BL's FAT partition.
I won't do that now but it's a 30 minute job and straight forward to implement and document. |
Quote:
Quote:
I fully understand why you've chosen u-boot and it makes perfect sense from an official Slackware perspective. All that closed-course RPi shizzle is undesirable when there are open-source alternatives available. I'm very happy that you're doing it the way you are and more than interested to see how you've put it all together. Also very glad you've decided to support the RPi devices, after constantly bugging you for years to do it. It makes perfect sense to include the most popular ARM device on the planet in your Slackware portfolio. With that, and the release of Slackware AArch64, these are very exciting times indeed. :thumbsup: |
Quote:
It won't be supported in the Installer but one can switch to it post installation. |
Quote:
|
All times are GMT -5. The time now is 03:49 AM. |