04-12-2020, 10:37 AM
I recently had to run through this entire process again from scratch after installing a new eMMC module in my Pinebook (now at 128GB, yay!). I ran into a few gotchas that I thought were worth sharing here.
1) For some reason, ca-certificates does not get installed correctly into the rootfs, even if it is the latest version. Reinstalling it re-runs the install scripts and fixes whatever is broken about ca-certificates after first boot. Before this, you cannot connect to https:// sites. So, one of the first steps after updating the package list would be to:
I am not sure what else from the rootfs is broken like this, so I just re-install everything before installing any new packages. This is easiest done in the base image, because there is less to reinstall. Anything that got installed in the chroot environment of the base rootfs would not have this problem. The only package I have noticed a problem with is ca-certificates, but there may be others, but they would be restricted to what comes with the base rootfs image.
If you have anything you know was installed on top of the base rootfs (you can usually tell by the timestamps), that would not need to be reinstalled.
This is just some quirk about how the base image is built. I will let the author of the build script know about it, he may already in fact.
2) The LCD brightness script needs a group to be set for it to work. The details are at the URL listed in the comments:
https://github.com/pfeerick/pine64-scrip...ess-script
Note that the command in Slackware is not addgroup, but groupadd:
The rest of the instructions at that link work as written. And the rest of my instructions above also work as written if you apply these two extra steps.
1) For some reason, ca-certificates does not get installed correctly into the rootfs, even if it is the latest version. Reinstalling it re-runs the install scripts and fixes whatever is broken about ca-certificates after first boot. Before this, you cannot connect to https:// sites. So, one of the first steps after updating the package list would be to:
Code:
slackpkg reinstall ca-certificates
I am not sure what else from the rootfs is broken like this, so I just re-install everything before installing any new packages. This is easiest done in the base image, because there is less to reinstall. Anything that got installed in the chroot environment of the base rootfs would not have this problem. The only package I have noticed a problem with is ca-certificates, but there may be others, but they would be restricted to what comes with the base rootfs image.
Code:
slackpkg reinstall slarm64
If you have anything you know was installed on top of the base rootfs (you can usually tell by the timestamps), that would not need to be reinstalled.
Code:
ls -lt /var/log/packages/
This is just some quirk about how the base image is built. I will let the author of the build script know about it, he may already in fact.
2) The LCD brightness script needs a group to be set for it to work. The details are at the URL listed in the comments:
https://github.com/pfeerick/pine64-scrip...ess-script
Note that the command in Slackware is not addgroup, but groupadd:
Code:
groupadd gpio
The rest of the instructions at that link work as written. And the rest of my instructions above also work as written if you apply these two extra steps.