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.
Once you get your sustem running again, copy over the latest u-boot from ayufan ( i think that is the spelling). Put it on the SPI flash mtd0, I think. It is basically the same thing as erasing the flash, except you are flashing it instead with a new image. From what you posted it looks like Right now your sd card has u-boot on it and that is why the sbc still boots. Just be careful not to put the wrong image, file or /dev/random onto SPI flash. You will have to jump the SPI flash again and erase it, rinse, repeat the SPI flash write.
I flashed the SPI following this guide https://github.com/ayufan-rock64/lin...s/flash-spi.md
And booted again. It seems to have worked, but the guide says that during the flashin process the white light should blick at a rate of one per second. I did not see any blinking. I works now, I just hope I'll be able to transfer the system to the eMMC module once it arrives...
it is not necessary to have a bootloader in SPI (since there may be nuances with loading a more recent kernel). transferring slarm64 is just enough to perform transfer-to-disk
I am not sure if anyone here is interested in this, but I uploaded my slightly old Rock64 base image, with a 5.6.19 kernel. I am pretty sure this one boots without needing the eMMC attached, and is one of the most stable images I ever produced for the Rock64 board. The kernel is a bit outdated, but otherwise it might be worth playing around with if you are still having trouble booting the other images:
I started with having to erase the SPI, then I tried slarm64-current-aarch64-base-rock64-5.11.11-build-20210402.img.zst This would not start up reliably. Maybe once in 3 tries. Then I switched to slarm64-current-aarch64-base-rock64-5.10.10-build-20210126.img.zst. That was much better, but still not reliable. And I noticed quite a few flaws. For instance iptables wouldn not install corretcly, with some libraries with md5 errors. Also bind would not work.
Now I am trying slarm64-current-aarch64-base-rock64-4.4.254-build-20210130.img.zst. So far it looks promising...I'll see.
Hello, I want to use it in my raspberry pi 4B. I downloaded “slarm64-current-aarch64-server-raspberry_pi_4-5.13.9-build-20210816.img.zst”. It is recorded on the SD card. However, when it is half started, it will display a black screen, and there will be no response。 The same is true when I replace it with another two img。
Record “slarm64-current-aarch64-enlightenment-raspberry_pi_4-5.10.9-build-20210124.img.zst”, the raspberry pie cannot be recognized. I switched back to the latest image,
I deleted "dtoverlay = vc4-fkms-v3d" in config.txt and started normally。
I don't know much English. I use translation tools to translate, which may be different from the original meaning
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.