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.
I just received my rockpro64 this week (my first arm board), and I'm trying out your slarm64 images on a micro sd to try to get slackware up and running on it. It seems that only the images with kernel 4.4.230 (2020-07-11) will run. I've tried the newer 4.4.249 and 5.9.16 images and they both hang at "Booting using the fdt blob at 0x1f00000". I'll link a picture of the boot screen at the end of this post, if it helps.
I'm new to running anything on an arm board so I'm not sure the cause but it seems to be a problem with uboot, and working with that is completely new to me. Perhaps you have an idea on what can be done to get a newer image to boot?
For now I can run with the 4.4.230 images. Both base and xfce work fine, I just need to figure out what I want to use.
I got your latest "slarm64-current-aarch64-base-rockpro64-5.10.11-build-20210128.img.zst" image downloaded and copied to my sd card and it booted up properly. My usb keyboard plugged into the rockpro64 is working fine too. I was wondering how that would go since those bug reports were talking about breaking usb keyboard support.
to download and then erase the SPI use the method: Disable SPI (while booting)
Quote:
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it. Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.
After erasing SPI Flash, "env default -a ; reset", and finally booting the SD Card with slarm64, I was able to get Linux booted again. Thanks for the information. It's surprisingly difficult to glean any information about u-boot. There are so many versions and platforms that have different u-boot commands. A lot of the information I found was old, incorrect, or missing commands.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
