diff --git a/blog/posts/0144-archarm-uefi-mcbin-install.cfg b/blog/posts/0144-archarm-uefi-mcbin-install.cfg index 0ddebfc..0932d07 100644 --- a/blog/posts/0144-archarm-uefi-mcbin-install.cfg +++ b/blog/posts/0144-archarm-uefi-mcbin-install.cfg @@ -2,4 +2,4 @@ filename = 2021-08-31-installing-archarm-with-uefi-on-the-mcbin.html title = Installing ArchLinuxARM with UEFI on the MACCHIATObin description = A guide to installing ArchLinuxARM with UEFI boot on a MACCHIATObin. created = 2021-08-31 -updated = 2021-09-06 +updated = 2021-11-16 diff --git a/blog/posts/0144-archarm-uefi-mcbin-install.html b/blog/posts/0144-archarm-uefi-mcbin-install.html index 4bfb862..a591348 100644 --- a/blog/posts/0144-archarm-uefi-mcbin-install.html +++ b/blog/posts/0144-archarm-uefi-mcbin-install.html @@ -115,12 +115,12 @@ instructions for installing an image to the SPI Flash via U-Boot found in the documentation,[5] modifying, of course, for the filename:

- +
+usb start
+load usb 0:1 $kernel_addr_r uefi-mcbin-spi.bin
+sf probe
+sf write $kernel_addr_r 0 0x$filesize
+

To test to see if this has worked, turn off the MACCHIATObin, switch the jumpers to boot from SPI, and check to see if you get a UEFI prompt. This should @@ -181,10 +181,10 @@ solved by just making a simple symbolic link to the kernel file with a filename that is recognized. In my case, I simply created a link named vmlinuz-linux as appears on my x86_64 machine:

- +
+cd /boot
+ln -s Image vmlinuz-linux
+

Reboot

At this point, the OS should be properly installed, and you should be able to