LinuxQuestions.org - [SOLVED] slarm64 (aarch64 unofficial slackware)

- Slackware - ARM (https://www.linuxquestions.org/questions/slackware-arm-108/)

- - slarm64 (aarch64 unofficial slackware) (https://www.linuxquestions.org/questions/slackware-arm-108/slarm64-aarch64-unofficial-slackware-4175613287/)

added clause to README.TXT rock64, rockpro64 loading on broken SPI and then cleaning.

Quote:

Originally Posted by mralk3 (Post 6239302)

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...

Thank you for your help!

Karl

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

Quote:

Originally Posted by shelldweller (Post 6239373)

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:

slarm64-current-aarch64-base-rootfs-20201023-5.6.19-rock64-build-20201031.img.zst
slarm64-current-aarch64-base-rootfs-20201023-5.6.19-rock64-build-20201031.img.zst.sha256

Hi, It could be my hardware, but my experience with slackware on my rock64 has been rocky during the last few days. I tried your image, too, with no success. https://nextcloud.krasso.com/index.p...5TkjnxHFWcdfCo

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.

One noob question, I would like to test that version on a RPi3, what's the default passwd to log in?

Quote:

Originally Posted by nobodino (Post 6240105)

One noob question, I would like to test that version on a RPi3, what's the default passwd to log in?

README.TXT

Quote:

Default Login
------------------
login: root
password: password

Quote:

Originally Posted by KarlF (Post 6240078)

Oh, right, if I recall correctly that image assumes you are using eMMC only. If you are using SD card, try changing two files:

1) edit /boot/uEnv.txt and add the following line:

Code:

rootdev=/dev/mmcblk0p1

or, if you see

Code:

rootdev=/dev/mmcblk1p1

change that line to the line above.

2) edit /etc/fstab, and change the line that starts with

Code:

/dev/mmcblk1p1 / ext4 ......

so that it starts like

Code:

/dev/mmcblk0p1 / ext4 ......

and then that image should boot from the SD card.

Sorry, I forgot about that bit.

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。

how did you record the image?
zstdcat slarm64-current-*-server-*-build-*.img.zst > /dev/mmcblk0
the previous image doesn't work either?
slarm64-current-aarch64-enlightenment-raspberry_pi_4-5.10.9-build-20210124.img.zst

you can try to change

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