aarch64 testing enabled in openQA production
by Adam Williamson
Hi folks!
A few of you have seen this already, but just wanted to send out a
wider announcement: having been deservedly shamed by pbrobinson, I
spent most of this week working on aarch64 testing in openQA, and am
happy to announce that:
* Quite a few existing issues in tests have been fixed
* Testing coverage has been enhanced a lot to cover the Minimal, Server
and Workstation disk images, with the full set of Base tests run on
each
* aarch64 testing is now enabled on the production openQA instance!
We've had testing running on the lab (formerly known as staging)
instance for a long time now, and I've been meaning to also enable it
on production for over a year, but it kept getting delayed by this and
that (most recently, the infra move). But now it's done.
The consequences of this - beyond, of course, that you can now see
aarch64 tests in the production openQA web UI - should be that the
aarch64 results show up in the "compose check report" emails, and will
also show up in the validation wiki pages, just like x86_64 results.
openQA should fill in quite a lot of boxes in the Installation, Base
and Cloud pages for future validation events, taking some of the test
load off of manual testers. Next week I intend to enable most of the
Desktop tests on the Workstation disk image too.
I have not enabled updates testing yet, because we just don't have the
capacity, unfortunately. If we can get more testing capacity we could
do this.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
2 years, 10 months
Status of armhfp grubs2-efi on top of Uboot
by Mark Verlinde
Hi,
A while ago (around the freeze of FC29) grub2-efi on top of Uboot was proposed as the (potentially) default setup for armhfp too. Unfortunately (IMHO) it did not materialize and I'm searching for the game-breaker.
On buggzilla found a few hints, " we have at least a grub2 <-> kernel bug" (1) among them, they did not make the holdup clear to me.
My investigation so-far:
* It works pretty good with a close to upstream build grub, not with the default gub2 packages. Which makes me believe loading an arm32 kernel as an Portable Executable instead of grub's LoadImage() and StartImage() services may be a game-stopper. NOTE : I understand this is necessary for chain loading efi stubs for secure-boot. IMO this is not the pursued goal here.
* Since kernel patch "efi: libstub/arm: account for firmware reserved memory at the base of RAM" (2) it works on RPI's too (given a "custom" build grub2)
All feedback is appreciated,
grtz Mark
1) https://bugzilla.redhat.com/show_bug.cgi?id=1602948
2) https://patchwork.kernel.org/patch/11189097/
2 years, 10 months
Fedora 32 on Pinebook Pro
by Andreas Reschke
Hi there,
I've a well good working Fedora 32 installation an my Pinebook Pro. I
want to replace the custom kernel with official fedora one. But it's not
working.
Failure: Bad Linux ARM64 Image magic!
How to resolv this ?
Thanks
Andreas
Boot message:
Card did not respond to voltage select!
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3c0000: USB EHCI 1.00
Bus dwc3: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus dwc3: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 3 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Device 0: unknown device
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
868 bytes read in 19 ms (43.9 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command: autoboot
Ignoring malformed menu command: hidden
Ignoring unknown command: totaltimeout
Ignoring unknown command: default=Fedora
1: Fedora (5.8.10-200.fc32.aarch64)
Retrieving file: /initramfs-5.8.10-200.fc32.aarch64.img
23434154 bytes read in 1030 ms (21.7 MiB/s)
Retrieving file: /vmlinuz-5.8.10-200.fc32.aarch64
12317358 bytes read in 556 ms (21.1 MiB/s)
append: ro root=UUID=cb3d578a-5e54-46bd-9de8-020f78bb6267 console=tty1
console=ttyS2,1500000 root=LABEL=ROOT_FEDORA rw rootwait
video=eDP-1:1920x1080@60 video=HDMI-A-1:1920x1080@60
Retrieving file:
/dtb-5.8.10-200.fc32.aarch64/rockchip/rk3399-pinebook-pro.dtb
59659 bytes read in 34 ms (1.7 MiB/s)
Bad Linux ARM64 Image magic!
SCRIPT FAILED: continuing...
60731 bytes read in 27 ms (2.1 MiB/s)
No ethernet found.
/boot/extlinux/extlinux.conf
#Org
#LABEL Fedora ARM
#KERNEL /Image
#FDT /dtb/rockchip/rk3399-pinebook-pro.dtb
#APPEND initrd=/initramfs-linux.img console=tty1 console=ttyS2,1500000
root=LABEL=ROOT_FEDORA rw rootwait video=eDP-1:1920x1080@60
video=HDMI-A-1:1920x1080@60
#Org
ui menu.c32
menu autoboot Welcome to Fedora-Server-armhfp-31-1.9. Automatic boot in
# second{,s}. Press a key for options.
menu title Fedora-Server-armhfp-31-1.9 Boot Options.
menu hidden
timeout 20
totaltimeout 600
default=Fedora (5.8.10-200.fc32.aarch64)
label Fedora (5.8.10-200.fc32.aarch64)
kernel /vmlinuz-5.8.10-200.fc32.aarch64
append ro root=UUID=cb3d578a-5e54-46bd-9de8-020f78bb6267
console=tty1 console=ttyS2,1500000 root=LABEL=ROOT_FEDORA rw rootwait
video=eDP-1:1920x1080@60 video=HDMI-A-1:1920x1080@60
fdtdir /dtb-5.8.10-200.fc32.aarch64/
initrd /initramfs-5.8.10-200.fc32.aarch64.img
[root@pinebook-pro ~]#
2 years, 11 months
Ethernet not working on pine64-pro Fedora 32 aarch64
by Karl Li
Hello all!
I noticed that on a pine64-pro board running aarch64 Fedora 32, ethernet is broken with the latest set of patches installed through dfn update. To reproduce:
1. Download the latest Fedora-Minimal-32-1.6.aarch64.raw.xz image from the Fedora alternate architectures page
2. Flash the image to an SD card using 'arm-image-installer --image=Fedora-Minimal-32-1.6.aarch64.raw.xz --media=[sd card here] --target=pine64_plus'
3. Boot the pine64-pro board from the SD card like usual, set up new account, etc.
4. At this point, ethernet should work. Run 'dnf update', install latest patches, reboot
5. Upon reboot, ethernet no longer works
Has anyone else run into this or have some possible hints?
Thanks!
-Karl
2 years, 11 months
Expanding Root
by brm
System is Pine64+ with Allwinner A64 SoC.
kernel 5.7.15-sunxi64
Fedora 32 is booting and running on this sdcard based system. However it is using a very small part of the 64GB sd card. I am looking for suggestions on how to utilize the non-partitioned space. Manjaro seems to have a script to resize the root partition and incorporate unused space into the system. Alternatively I could create a new partition and file system. This would be handy for the home directory. How do we turn my existing home directory into a new one with its own partition?
2 years, 11 months
New Fedora raw images on the Pine64
by brm
Has anyone booted a newer Fedora raw image on the Pine64 Allwinner V8? I cannot get anything working here. I have tried many Fedora aarch64 releases - Fedora 32 Fedora beta 33 etc.
2 years, 11 months
