Failed to install Arch Linux 64bit onto Raspberry Pi 4.

Raspberry Pi
Reading Time: 3 minutes



I have 2 Raspberry Pi 4 in my home as below.

1. Nextcloud server
2. WordPress server, samba server, virus scan server



This time I decided to install Arch Linux onto them.
– I like Arch Linux OS.
– My laptop is installed Endeavour OS which is one of Arch Linux flavor.

I tried to install Arch Linux 64bit but failed because kernel doesn’t start up.
I took note here to memorize for future chance.

05/10/2023
The reason is I ran this "sed -i ..." command.

> You need to do this command when 64bit as described on this page.



This is another article which I succeeded to install Arch Linux 64bit onto Raspberry Pi 4.

What I did

I installed Arch Linux 64bit onto Raspberry Pi 4 following this page.

Raspberry Pi 4 | Arch Linux ARM



You will be able to install by following this section.



You need to do this command when 64bit as described on this page.

05/10/2023
As mentioned earlier, this "sed -i ..." doesn't need to be done on my environment.
If you face similar problem, it may be valuable to skip this command.



I connected microSD to Raspberry Pi and turned on.
But,



There are so many error message like this.
I guess this is due to microSD related error.

error -5 whlist initialising SD card



I searched on Google and found similar situation.

Arch Linux ARM • View topic - "error -5 whilst initializing SD card"@20220315 aarch64 img



This Youtuber mentions the same topic.



On comment there is hint which recommends to apply rpi-update.
– You know rpi-update is for updaring firmware of Raspberry Pi.

the arch kernel doesn't use the same one as rpi. plug the sdcard into another os, sudo mount /dev/sdbX root && sudo mount /dev/sdbX boot. then git clone rpi-update from hexxeh and run that on your mounted directories. the command will look like sudo ROOT_PATH=$HOME/root BOOT_PATH=$HOME/boot ./rpi-update. 

that's it, enjoy!

ps. if you want 3d GPU acceleration too you'll need to flash grayskys kernel. goodluck :))



This is my result which looks good.

$ git clone https://github.com/Hexxeh/rpi-update
$ cd rpi-update
$ sudo BOOT_PATH=$HOME/boot ROOT_PATH=$HOME/root ./rpi-update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** Performing self-update
 *** Relaunching after update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
FW_REV:ecb31dc9a698ff9d17d9a5a24550ea5b9aaea7eb
 *** We're running for the first time
 *** Backing up files (this will take a few minutes)
 *** Remove old firmware backup
 *** Backing up firmware
 *** Backing up modules 6.1.21-v8+
WANT_32BIT:0 WANT_64BIT:1 WANT_PI4:1
#############################################################
WARNING: This update bumps to rpi-6.1.y linux tree
See: https://forums.raspberrypi.com/viewtopic.php?t=344246

'rpi-update' should only be used if there is a specific
reason to do so - for example, a request by a Raspberry Pi
engineer or if you want to help the testing effort
and are comfortable with restoring if there are regressions.

DO NOT use 'rpi-update' as part of a regular update process.
##############################################################
Would you like to proceed? (y/N)
 *** Downloading specific firmware revision (this will take a few minutes)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  116M    0  116M    0     0   9.9M      0 --:--:--  0:00:11 --:--:-- 10.9M
 *** Updating firmware
 *** Updating kernel modules
 *** depmod 6.1.25-v8+
 *** Updating VideoCore libraries
 *** Using SoftFP libraries
 *** Updating SDK
 *** Running ldconfig
 *** Storing current firmware revision
 *** Deleting downloaded files
 *** Syncing changes to disk
 *** If no errors appeared, your firmware was successfully updated to ecb31dc9a698ff9d17d9a5a24550ea5b9aaea7eb



If I tried with /boot 200MB then below warning occurred so I would recommend to expand /boot as 256MB or larger.

Partition size 200M may not be sufficient for new Pi4 files
This could result in a system that will not boot.
256M FAT partition is recommended. Ensure you have a backup if continuing.
Would you like to proceed? (y/N)



I am advancing but still some errors.



And somehow microSD is mounted Read-Only.

Conclusion

How wat it?

I still continue to solve this problem!

Comments

タイトルとURLをコピーしました