Hi! While theoretically should be possible, i would like to hear some
confirmation that f33 can work on odroid N2 ...
Moreover, if it can work, all i have to do is to write the image on
eMMC, isn't it?
Disclaimer: it's my first time playing in arm world, so many things are
strange to me..
Thanks a lot!!
I’m still doing various test for my Fedora Server documentation about usage of SBC  and a scheduled Fedora Magazine article about Fedora Server and Arm SBC.
After some difficulties regarding Odroid and Banana Pi I now got hold of an Radxa Rock Pi 4 to explore and test an alternative hardware to Raspberry Pi 4
During first start, after the grub menu was displayed the monitor lost connection and showed nothing. But the device bootet correctly and I had access over network. After an update the monitor worked correctly anything else I tried was fine.
When I connected a NVMe SSD it didn’t boot anymore. I had to re-flash the SD card and start over. It worked than but didn’t show the NVMe.
When I tried an Ubuntu image as delivered by Radxa the NMMe worked fine (with the Radxa provided uboot). So the hardware setup is OK. I tried Armbian (using mainline uboot as it states) and it worked fine with NVMe.
Is there a way to access NVMe in Fedora?
And if it is, is there a way to flash the SPI with fedora so I can boot from NVMe? There seems to be some provision for this, but I can't figure out the details.
 In case anyone is curious:
I want to do a fresh installation and encrypt the installation. So I
boot the Pinebook Pro with Fedora-Everything-netinst-aarch64-34-1.2.iso.
The boot process runs fine but stopped with
Starting installer, one moment...
anaconda 34.24.9-1.fc34 for Fedora 34 started.
* installation log files are stored in /tmp during the installation
* shell is available on TTY2
* when reporting a bug add logs from /tmp as separate text/plain
[anaconda]1:main* 2:shell 3:log 4:storage-log >Switch tab: Alt+Tab |
I've waiting for more than a half our but nothing was shown on the display.
How do proceed ?
Hello, devel and arm lists!
We recently ran into a testsuite failure when building glibc for
Rawhide on armv7hl:
The test program experienced a hang after a thread was cancelled.
So far, it appears that either annobin generated notes or the way in
which the static linker interprets them lead to incorrect unwind
information in 32 bit Arm binaries.
While in this case only a glibc testsuite failure was caught, there is
a chance that building with annobin can lead to incorrect unwind
information and associated problems for any armv7hl Rawhide package
built this way.
With this in mind, I would like to know how the Fedora-Arm developer
community feels about disabling annobin when building RPMs only on
armv7hl until this issue is investigated and the root cause fixed.
This should be possible with a change to the redhat-rpm-config.