Rock64 RK3328 (aarch64)
previous discussion Rock64
|
Thanks! Should I comment out the mirror in /etc/slackpkg/mirrors and update? Is that safe to do?
|
Quote:
|
update kernel 5.16.9
Installation README.TXT slarm64-current-aarch64-server-rock64-5.16.9-build-20220214.img.zst slarm64-current-aarch64-server-rock64-5.16.9-build-20220214.img.zst.sha256 slarm64-current-aarch64-xfce-rock64-5.16.9-build-20220214.img.zst slarm64-current-aarch64-xfce-rock64-5.16.9-build-20220214.img.zst.sha256 |
Just a quick FYI/bug report. I'm writing up some nice instructions for getting Octoprint up on the Rock64. In doing that, I'm trying to do everything "right". If you do the recommended slackpkg commands, it will brick it. Well, just not boot to that SD again, until you reimage or fix it.
Code:
slackpkg update The image I'm installing with is: slarm64-current-aarch64-xfce-rock64-5.16.9-build-20220214.img I was doing it on Mar-10-2022 and Mar-11-2022. It did it using both slarm64-15.0 and slarm64-current from Code:
http://dl.slarm64.org/slarm64/slarm64-15.0/ Code:
ffmpeg-rockchip-4.4.1-aarch64-2 Also, there's something wrong with the osdn.net mirrors. Some files on some mirrors are showing 404, and slackpkg is saving a 0 byte file for each. That upsets it when it's trying to install them. It was also throwing md5sum and gpg errors, but I think they were all caused by the 404 thing. Switching to dl.slarm64.org links fixed that. Sorry for sucking up your bandwidth. Code:
https://osdn.net/projects/slarm64/storage/slarm64-15.0/ |
Quote:
Some packages are also removed that are not included in the slarm64 distribution (which repeats the slackware64 package base). Quote:
|
Quote:
I have updated my instructions to warn about this. Just to not do clean-system, not update the blacklist. |
Quote:
osdn.net loading fixed. |
Quote:
BTW, did you notice that wget doesn't work on https://dl.slarm64.org? It's something with the ZeroSSL CA. I guess it isn't in our cert bundle. My site (also tested below) was failing with the ca-certificates included on the installation image, but it was fixed after updating ca-certificates to current. That was because of a recent problem with Let's Encrypt, which was fixed recently. I checked it with wget on the Rock64, and on my Slackware64 14.2 server. Those are both broken It also fails under the Kali WSL on Windows, with the "certificate ... doesn't have a known issuer". I also updated the ca-certificates on the Rock64 with the mainstream Slackware-current package (20220309), and it still fails. It does work fine with current Chrome on Win11. I know the Chrome folks are more attentive to keeping all the certs updated. It doesn't matter to me, and just using the http:// link works perfectly, but some people may not know or bother to look. I will try building my own updated ca-certificates package with the Slackware-current build scripts, and see if it fixes anything, but that looks like it last gathered the cert data 3 days ago. So it's a problem with ZeroSSL's trust, not slarm64, other than making life difficult for people. Code:
root@rock64:~# slackpkg search ca-certificates |
Quote:
Code:
update-ca-certificates |
Quote:
|
On a slightly different note, I am running into an issue with u-boot when trying to build a post-"dirty pipe" image for this board. (bold emphasis added)
Code:
UPD include/generated/timestamp_autogenerated.h Code:
root@quartz:/hdd/slarm64/images_build_kit# ls /hdd/slarm64/images_build_kit/build/source/rkbin/bin/rk33/ I recall that the last time this happened I worked around it with a symlink. I just wanted to bring it up here in case you wanted to add a more elegant solution. Thank you, as always. |
This is due to the fact that at some time the rkbin repository was not available at https://github.com/rockchip-linux/rkbin and I switched to https://github.com/caesar-github/rkbin.git
Let us turn on https://github.com/caesar-github/rkbin.git |
Quote:
Code:
MKIMAGE tpl/u-boot-tpl-rockchip.bin I have tried switching between the two sources for rkbin as well as u-boot-tools in config/sources/rockchip.inc, but nothing lets me get past the u-boot compilation stage above. FWIW, I am getting something similar when I try to build images for Quartz64 also. So, maybe something is going on with the rockchip boot sources and I just need to be more patient. Just for your info, nothing critical. Thanks much. |
All times are GMT -5. The time now is 10:02 PM. |