Since after each Brams post I tend to be left with more questions than answers, I wanted to look more at StartFive2's software stack. There are now some RISC-V boards but honestly none look "ready-to-use". For each board somehow own image is offered which actually confuses more than helps. But as I said: at the moment StarFive2 is the most common board. The last images are from end of February. Then we look under the hood
I have downloaded "starfive-jh7110-VF2-SD-wayland.img.bzip2" from 202303.
Unpacked and extracted Linux partition
$ bunzip2 starfive-jh7110-VF2-SD-wayland.img.bz2
$ sfdisk -l -uS starfive-jh7110-VF2-SD-wayland.img
Disk starfive-jh7110-VF2-SD-wayland.img: 2,65 GiB, 2831155200 bytes, 5529600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 5BDD0F8F-36BE-4C36-B1D9-1A904F6B5393
Device Start End Sectors Size Type
starfive-jh7110-VF2-SD-wayland.img1 4096 8191 4096 2M HiFive Unleashe
starfive-jh7110-VF2-SD-wayland.img2 8192 16383 8192 4M HiFive Unleashe
starfive-jh7110-VF2-SD-wayland.img3 16384 221183 204800 100M EFI System
starfive-jh7110-VF2-SD-wayland.img4 221184 5527518 5306335 2,5G Linux filesyst5T084846Z unstable main
$ dd if=starfive-jh7110-VF2-SD-wayland.img of=risc5 skip=221184
$ sudo mount -o loop risc5 /mnt/
$ sudo mkdir /opt/bookworm-riscv64
$ sudo rsync -av /mnt/ /opt/bookworm-riscv64/
$ sudo umount /mnt
$ sudo chroot /opt/bookworm-riscv64/
Then I look at the repositories that are included
deb https://snapshot.debian.org/archive/debian-ports/20221225T084846Z unstable main
WTF? This is based on a snapshot of Debian Unofficial Port
Funny. New bugs may be prevented, but the old ones are not fixed. Really clever!
Then I try with apt to get the list of packages and it's failed
The following signatures were invalid: EXPKEYSIG B523E5F3FC4E5F2C Debian Ports Archive Automatic Signing Key (2023) <ftpmaster@ports-master.debian.org> The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8D69674688B6CB36
Reading package lists... Done
W: GPG error: http://ftp.ports.debian.org/debian-ports unstable InRelease: The following signatures were invalid: EXPKEYSIG B523E5F3FC4E5F2C Debian Ports Archive Automatic Signing Key (2023) <ftpmaster@ports-master.debian.org> The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8D69674688B6CB36
E: The repository 'http://ftp.ports.debian.org/debian-ports unstable InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Ooops... How did they do that? Never mind. I import the GPG keys from Debian
wget http://ftp.de.debian.org/debian/pool/main/d/debian-ports-archive-keyring/debian-ports-archive-keyring_2023.02.01_all.deb
dpkg -i debian-ports-archive-keyring_2023.02.01_all.deb
And change the list of repos. /etc/apt/sources.list looks like this
#deb https://snapshot.debian.org/archive/debian-ports/20221225T084846Z unstable main
deb http://ftp.ports.debian.org/debian-ports/ unstable main contrib non-free non-free-firmware
After that I can upgrade
$ apt update && apt upgrade
Get:1 http://ftp.ports.debian.org/debian-ports unstable InRelease [107 kB]
Get:2 http://ftp.ports.debian.org/debian-ports unstable/main riscv64 Packages [24.1 MB]
Get:3 http://ftp.ports.debian.org/debian-ports unstable/contrib riscv64 Packages [60.5 kB]
Get:4 http://ftp.ports.debian.org/debian-ports unstable/non-free riscv64 Packages [91.6 kB]
Get:5 http://ftp.ports.debian.org/debian-ports unstable/non-free-firmware riscv64 Packages [27.1 kB]
Fetched 24.3 MB in 23s (1040 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
605 packages can be upgraded. Run 'apt list --upgradable' to see them.
....
Now I take big cup of coffee...it takes time
Stay tuned