For Testing: Slackware ARM installation media for ARM and Aarch64
I'd like to share some of my own scripts for Aarch64 now that there is a release candidate for 15.0.
There aren't any distribution files for Aarch64 but here is an sd image that boots the Raspberry Pi 4: http://slackware.uk/slackwarearm/peo...64-rpi/images/ It should boot into the installer and is strictly for testing on the Raspberry Pi 4 model(s). Any and all suggestions welcome! Thanks. NOTE: I failed to mention that to boot you need to run a few commands in U-boot to start it up: Code:
setenv devtype "mmc" |
Quote:
|
The image i posted already has a 5.14.7 kernel, built from the sources published by Stuart. I can take a look at yours. Maybe I can glean something about the Pi 3s that will help, and mark those off the list.
|
Quote:
Code:
No mmc device at slot 1 1 It's been many years since I did anything with u-boot (2014-2015) and, most poignantly, I consider myself to be somewhat of a u-boot noob. So bear that in mind. A step-by-step, end-to-end, set of instructions would certainly be welcomed by me in order to facilitate success. I do remember there was a uEnv.txt file that was used in order to preset environment variables/values before running 'bootcmd' which eliminated the need to enter manual commands beforehand. Is that still an option? If so, it might be prudent to implement such a feature IMHO. Please advise and thanks for your time in advance. :cool: |
There is a new image up with a 5.14.9 kernel and the most recent Slackware arm installer baked in (from Stuart). Ignore the rk3399 image / uboot for now, they are not current. The latest image should just be a symlink to the actual image:
rpi_arm64-sdimg_5.14.9_1.img.xz Keep in mind, this is just the installer. I have only tested it with aarch64. You can find out what your sdcard is recognized as with: Code:
mmc list Code:
ls mmc 0:2 You should only have to point "distro_bootpart" to the second partition like so, and run bootcmd var. Code:
setenv distro_bootpart 2 Let me know how it goes! Everything is kind of hacked together and needs testing. Your input is very welcome. :) |
1 Attachment(s)
Quote:
So, using the commands above as instructed, when booting the 'rpi_arm64-sdimg_5.14.9_1.img' disk image it loads the kernel, finds the initrd OK, then gets so far into the boot process before it hangs indefinitely with a constantly flashing green LED on the RPi4 [4GB]. Although, there doesn't seem to be any errors flagging up and certainly no kernel panic. Screenshot... |
Are you plugged into HDMI and Serial? The Slackware arm installer assumes you are running it over serial. The reason your HDMI attached screen stops output is because it's being sent to the serial console.
Try (with serial cable attached): Code:
screen /dev/ttyUSB0 115200 Code:
dmesg | grep tty An alternative to the serial adapter is to connect by SSH, like a head less install. |
Here is the Rpi GPIO pinout: https://pinout.xyz/
You want to attach the Ground to the black pin, it doesn't matter which one. The TX line on the adaptor to the UART RX and the same goes with the RX line -> UART TX Gpio pin. |
Quote:
|
Quote:
This is incorrect. Rewrite your SD image, edit the config.txt, boot it up on HDMI, then hold CTRL + ALT + F2 and you will get a shell after hitting enter in tty2. No serial connecting is necessary, BUT it is the default/preferred method of installation. The config.txt should look like so: Code:
enable_uart=1 Quote:
|
Quote:
Your disk images weres not working for me, but I cannot say if anything was broken. I reported it when I made you aware of my issue(s) here on LQ and asked for your advice. I've informed you that I was somewhat of a u-boot noob and that was my attempt at letting you know that I do not have the knowledge or experience to offer any kind of solution(s). Subsequently, you told me on IRC that a UART serial cable was needed for the Slackware installer to load successfully because that's how Stuart was doing it. This revelation was not documented or discussed at any point before then. My only whinge is not to have been made aware of this initially, as it may have saved me some considerable time on Google while scratching my head. Quote:
|
New image up. It is just the installer. It should not need anything in u-boot to be edited or have any commands to run.
https://slackware.uk/slackwarearm/pe...64-rpi/images/ Test the following: If on HDMI, use the tty2 console (CTRL + ALT + F2) after boot to partition and launch the installer. The second partition has been marked active, so the default u-boot will boot it first when searching for partitions in scripts. This should not be an issue for rk3399 stuff, for those who are testing on rockpro64 or pinebook pros. It should load extlinux.conf and then the kernel bits on partition 2 once u-boot is finished with its thing. |
Quote:
After fulfilling the keyboard map requirement I found myself at the command prompt. So, as a proof of concept test, this installer disk image works on the Raspberry Pi 4 up to that point. |
All times are GMT -5. The time now is 10:13 AM. |