MIME-Version: 1.0
From: Jerome Marc <marcjero@yahoo.com>
Date: Tue, 31 May 2022 13:09:47 +0200
Message-ID: <CAD1Ag0yOBKKY56idfTUnbofGKiHm2NU=H8Tf0ERBGH4MSxkk=A@mail.gmail.com>
Subject: sys mode setup for RPI
To: ~alpine/users@lists.alpinelinux.org
Content-Type: multipart/alternative; boundary="0000000000002c563b05e04cd097"
References: <CAD1Ag0yOBKKY56idfTUnbofGKiHm2NU=H8Tf0ERBGH4MSxkk=A.ref@mail.gmail.com>

--0000000000002c563b05e04cd097
Content-Type: text/plain; charset="UTF-8"

Hi,

I followed the instructions here :
https://wiki.alpinelinux.org/wiki/Classic_install_or_sys_mode_on_Raspberry_Pi

I ran setup-disk this way :

alpine:~# export FORCE_BOOTFS=1
alpine:~# setup-disk -m sys /mnt
ext4 is not supported. Only supported are: vfat
Continuing at your own risk.
Installing system on /dev/mmcblk0p2:
/sbin/setup-disk: line 469: can't create /mnt/boot/config.txt: nonexistent
directory
/sbin/setup-disk: line 470: can't create /mnt/boot/cmdline.txt: nonexistent
directory
100%
/boot/initramfs-rpi
You might need fix the MBR to be able to boot

I'm confused now about the /mnt/boot directory structure. Because /mnt/boot
contains kernel stuff but also the firmware files.
If I move /mnt/boot/* to /media/mmcblk0p1/boot/ firmware files and overlays
will be copied as well
This means that these files will be available twice in the boot partition
(in /media/mmcblk0p1 and /media/mmcblk0p1/boot/)

The good thing is that firmware and kernel will be managed from apk.
However if apk upgrades the firmware files they won't be used by the system
because they are located in the /media/mmcblk0p1/boot/ subdirectory/.
Or do I have to change something in config.txt to force the use of the
firmware and overlays files stored in /media/mmcblk0p1/boot/ ?

Thanks !

--0000000000002c563b05e04cd097
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I followed the instructions here :=
=C2=A0<a href=3D"https://wiki.alpinelinux.org/wiki/Classic_install_or_sys_m=
ode_on_Raspberry_Pi">https://wiki.alpinelinux.org/wiki/Classic_install_or_s=
ys_mode_on_Raspberry_Pi</a></div><div><br></div><div>I ran setup-disk this =
way :</div><div><br></div><div>alpine:~# export FORCE_BOOTFS=3D1<br>alpine:=
~# setup-disk -m sys /mnt<br>ext4 is not supported. Only supported are: vfa=
t<br>Continuing at your own risk.<br>Installing system on /dev/mmcblk0p2:<b=
r>/sbin/setup-disk: line 469: can&#39;t create /mnt/boot/config.txt: nonexi=
stent directory<br>/sbin/setup-disk: line 470: can&#39;t create /mnt/boot/c=
mdline.txt: nonexistent directory<br>100%</div><div>/boot/initramfs-rpi<br>=
You might need fix the MBR to be able to boot<br></div><div><br></div><div>=
I&#39;m confused now about the /mnt/boot directory structure. Because /mnt/=
boot contains kernel stuff but also the firmware files.</div><div>If I move=
 /mnt/boot/* to=C2=A0/media/mmcblk0p1/boot/ firmware files and overlays wil=
l be copied as well</div><div>This means that these files will be available=
 twice in the boot partition (in /media/mmcblk0p1 and /media/mmcblk0p1/boot=
/)</div><div><br></div><div>The good thing is that firmware and kernel will=
 be managed from apk.</div><div>However if apk upgrades the firmware files =
they won&#39;t be used by the system because they are located in the /media=
/mmcblk0p1/boot/=C2=A0subdirectory/.</div><div>Or do I have to change somet=
hing in config.txt to force the use of the firmware and overlays files stor=
ed in /media/mmcblk0p1/boot/ ?</div><div><br></div><div>Thanks !</div><div>=
<br></div><div><br></div><div><br></div><div><br></div><div><br></div></div=
>

--0000000000002c563b05e04cd097--