Some of the talks from ORCONF 2016 which I’ve enjoyed recently.
lowRISC project update:
I’m happy to announce that we have done that. Almost.
There are two mandatory packages that we’re not building, dracut and plymouth. Luckily neither are relevant to RISC-V at the moment since we’re not using an initramfs and there is no graphical boot device.
Another milestone is we have built more than 5,000 Fedora packages. Fedora has about 18,400 packages in total, so that’s a respectable chunk.
Here is what Fedora/RISC-V looks like when it is booting in QEMU:
Props to Stefan O’Rear, David Abdurachmanov for doing most of the real work.
Amazon, so convenient, yet so annoying when things go wrong. This useless seller looks like a new type of scam to me. It seems to go like this:
Bootstrapping Fedora on the new RISC-V architecture continues apace.
I have now written a small autobuilder which picks up new builds from the Fedora Koji build system and attempts to build them in the clean “stage4” environment.
Getting latest packages from Koji ... Running: 0 (max: 16) Waiting to start: 7 uboot-tools-2016.09.01-1.fc25.src.rpm | 11 MB 00:10 uboot-tools-2016.09.01-1.fc25 build starting tuned-2.7.1-2.fc25.src.rpm | 136 kB 00:00 tuned-2.7.1-2.fc25 build starting rubygem-jgrep-1.4.1-1.fc25.src.rpm | 24 kB 00:00 rubygem-jgrep-1.4.1-1.fc25 build starting qpid-dispatch-0.6.1-3.fc25.src.rpm | 1.3 MB 00:01 qpid-dispatch-0.6.1-3.fc25 build starting python-qpid-1.35.0-1.fc25.src.rpm | 235 kB 00:01 python-qpid-1.35.0-1.fc25 build starting java-1.8.0-openjdk-aarch32-220.127.116.11-4.160812.fc25.src.rpm | 53 MB 00:54 java-1.8.0-openjdk-aarch32-18.104.22.168-4.160812.fc25 build starting NetworkManager-strongswan-1.4.0-1.fc25.src.rpm | 290 kB 00:00 NetworkManager-strongswan-1.4.0-1.fc25 build starting MISSING DEPS: NetworkManager-strongswan-1.4.0-1.fc25 (see logs/NetworkManager-strongswan/1.4.0-1.fc25/root.log) ... etc ...
Given that we don’t have GCC in the stage4 environment yet, almost all of them currently fail due to missing dependencies, but we’re hoping to correct that soon. In the mean time a few packages that have no C dependencies can actually compile. This way we’ll gradually build up the number of packages for Fedora/RISC-V, and that process will accelerate rapidly once we’ve got GCC.
You can browse the built packages and build logs here: https://fedorapeople.org/groups/risc-v/
I’ve uploaded our latest stage4 to http://oirase.annexia.org/riscv/.
util-linux is still missing, so there’s no mount command and the filesystem comes up read-only.
RPM has been added, but there’s some sort of bug or configuration problem in libdb which means that RPM cannot read its own database (although the RPM database that has been written seems fine and can be read quite happily from an x86_64 machine). Still under investigation …
I’m happy to announce that Fedora/RISC-V, the project to bootstrap Fedora on the new RISC-V architecture, has reached a key milestone: We are now releasing clean “stage4” disk images which are built entirely from RPMs (ie. every file except two are managed by RPM).
You can get the latest image from http://oirase.annexia.org/riscv/
To use it, you must enable my RISC-V tools copr:
# dnf copr enable rjones/riscv # dnf install riscv-qemu riscv-pk
and you can then boot the stage4 directly using this qemu command:
$ qemu-system-riscv -m 4G -kernel /usr/bin/bbl \ -append vmlinux \ -drive file=stage4-disk.img,format=raw -nographic
This is an early release and there are a few problems. The main one is that we lack a util-linux package, and thus there is no mount command so the disk image stays read-only after boot. You’ll see lots of errors like this at boot:
/init: line 16: mount: command not found /init: line 19: mount: command not found /init: line 20: mount: command not found
I hope to get that fixed soon.
There’s also no actual
rpm command in the stage4, again because of a required dependency, and again that’s something that will be fixed real soon.
Many thanks go to David Abdurachmanov and Stefan O’Rear for their huge efforts building packages.
 Because there is no systemd package yet, currently two extra files are added to the disk image which are not under the control of RPM:
 For real hardware, read this page