Just wanted to introduce myself as I am interested in helping with the ARM effort. I currently have a [personal] Macbook Air M1 and will be issued a MBP M1 for work [in several weeks] as part of a pilot program. I believe I could use them to contribute to the Fedora ARM effort.
I have limited kernel experience, but have built the kernel, applied the Fedora config, installed a minimalist [hello world] module and my [Intel] hardware is still working :)
Early on in my career, I worked on telephony switching systems and IP telephony protocol stacks (mostly on Sun Sparc systems.) I love to code, pure and simple and that is where I am most inspired/productive. I have done C/C++, SmallTalk, Java, Scala, shell scripting, etc., and now pursuing Rust in my spare time.
Looking forward to helping...
PS: I should be on the ARM SIG meeting today.
Principal Software Engineer, Multi-Architecture
A group of computer science undergraduates and I are interested in
contributing to the usability of Fedora Linux on the Raspberry Pi 4.
I was a part of this group as an undergrad and we developed a compatibility
layer for translating RPi.GPIO syntax into calls to libgpiod. It is
currently available on PyPi and under review for inclusion in Fedora:
The maintainer of the (broken) RPi.GPIO fedora package agreed to obsolete
it in favor of our new package, which is a drop in replacement for RPi.GPIO
(hence the 2), however I have not heard from him since September.
Anyway, we are looking for a new project or area of Fedora on the Raspberry
Pi to improve over the upcoming semester. Does anyone have any suggestions?
Fedora 33 Workstation on the RPI4 with UEFI runs fine for me. However, I can't figure out how to get accelerated video working. Without UEFI, Fedora 33 with kernel 5.10.7 seems to enable accelerated video without any further configuration. There is a /boot/efi/config.txt in this case. It contains things like
Where would one put these setttings for UEFI boot?
Hey folks! Just a heads up that I merged a branch I've had lying around
for weeks that enables *some* of the openQA desktop tests on the
aarch64 Workstation image.
I left out some with known issues. desktop_notifications_postinstall
needs to boot to runlevel 3, which is actually a bit tricky because of
UEFI - we don't get the boot menu with a usable timeout and the trick
we use to work around that on x86_64 (where we run the tests on BIOS)
doesn't work on UEFI because the setting is in the UEFI vars which are
not part of the main disk image.
To fix this I think I need to have the 'image deploy' test upload its
UEFI vars disk image and have the desktop_notifications_postinstall
test attach that as well as the main disk image, but I need to look
into the ins and outs of that a bit and this is my last work day of the
year, so I'll do it next year.
The desktop_login test is generally fragile (things tending to get
stuck or time out), but if it gets that far, it *always* fails when it
tests locking the screen; on aarch64 this seems to cause the VM to
permanently stop updating the display, or something. Again I haven't
had time to look into this, and I want to enable the other tests
without waiting for it.
The desktop_browser test is also failing, but I left that in because
it's not a test bug, it's a distro bug. Firefox builds have just been
disabled on aarch64 since 2020-11-20, so current composes don't have
Firefox in them on aarch64 at all. There's a bug related to this:
which I just gave a bit of a bump, because it shouldn't really be
acceptable to just turn off our default browser's build on one of our
primary arches for weeks at a time :(
This also breaks several of the other tests which use Firefox, like the
Cockpit and FreeIPA browser tests.
The tests should run on openQA prod from the next compose. The branch
has been deployed on openQA lab (staging) for weeks (including the
broken tests), so you can see how it's been behaving there.
IRC: adamw | Twitter: adamw_ha
i want to try install 32 Bit software ( Moneyplex = Homebanking
software) on my Fedora aarch64 system. This didn't work.
[andreas@pinebook-pro moneyplex]$ ll
-rwxr--r--. 1 andreas andreas 7543589 Jan 21 2020 Handbuch.pdf
-rwxr-xr-x. 1 andreas andreas 12369492 Apr 29 2020 moneyplex
-rwxr-xr-x. 1 andreas andreas 3079188 Oct 4 2019 prestart
drwxr-xr-x. 2 andreas andreas 4096 Oct 4 2019 reports
drwxr-xr-x. 2 andreas andreas 4096 Feb 5 2020 scripts
drwxr-xr-x. 2 andreas andreas 4096 Apr 29 2020 system
[andreas@pinebook-pro moneyplex]$ ./prestart
bash: ./prestart: No such file or directory
[andreas@pinebook-pro moneyplex]$ file prestart
prestart: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV),
dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux
[andreas@pinebook-pro moneyplex]$ uname -a
Linux pinebook-pro.reschke.lan 5.10.5-1 #1 SMP Thu Jan 7 14:35:07 UTC
2021 aarch64 aarch64 aarch64 GNU/Linux
Is this supportet? If yes, how can I solve this?
I recently got Fedora 33 Server booting on my RPI 4 - 8G using the RPI4 UEFI firmware. The usb3 adapter I used worked fine with Raspbian, but with Fedora 33, there was an issue. I've worked around this issue and another involving F33 complaining about the lack of sd card. These are my brief notes, hopefully they help someone. If a longer write up or a bug report would be helpful, I'm happy to do so. Also looking for feedback if I could have done anything better/different.
RPI 4B - 8G model
128G "Inland" brand ssd - OEM Phison - Model 'SATA AAD'
Orico Brand SATA to USB3 external enclosure - model 'ORICO 2139U3'
- uses JMicron Technology Corp. JMS578 chip - Sata 6Gb/s
UEFI Firmware: https://github.com/pftf/RPi4/releases/tag/v1.21
After Fedora install;
- switched advanced settings in UEFI from 'ahci' to 'devicetree'
- removed 3G ram limit
1. Pi treats usb drive as uas device causing extremely slow read/write - ext4 fs would not mount rw
[ 1247.365069] usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 1247.387663] scsi host0: uas_eh_device_reset_handler success
[ 1279.648929] sd 0:0:0:0: [sda] tag#3 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD IN
[ 1279.648937] sd 0:0:0:0: [sda] tag#3 CDB: opcode=0x28 28 00 03 fa 64 50 00 01 00 00
[ 1279.649085] sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
[ 1279.649091] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 00 00 10 00 00 04 00 00
[ 1279.649553] sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[ 1279.649559] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 0c 00 00 04 00 00
[ 1286.049165] sd 0:0:0:0: tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD
[ 1286.049173] sd 0:0:0:0: tag#4 CDB: opcode=0x0 00 00 00 00 00 00
[ 1286.065838] scsi host0: uas_eh_device_reset_handler start
2. Pi is missing sdhc card ( mostly annoying, could've just turned off kernel message echo to console? )
mmc1: Timeout waiting for hardware cmd interrupt.
mmc1: sdhci: =========== SDHCI REGISTER DUMP ===========
mmc1: sdhci: blah
1. uas device
- add usb quirk to kernel args in /etc/default/grub
- add quirk to config.txt (is this necessary?)
- rebuild grub with grub2-mkconfig
- dracut -f (not sure if I needed to do this?)
2. sdhc card
- block(black)list sdhc drivers
install sdhci /bin/false
install sdhci_platform /bin/false
install sdhci_iproc /bin/false
- From [finishing steps for rhel 8](https://access.redhat.com/solutions/41278)
- added 'sdhci.blacklist=1 rd.driver.blacklist=sdhci' to the above GRUB_CMDLINE_LINUX
- rebuilt grub again
- (make a copy of and) rebuilt initramfs
'dracut --omit-drivers sdhci -f'
### Things I didn't do
1. fool around with kdump
2. Edit the installer kernel CMDLINE to blacklist the sdhci module and add the usb quirks
### Other Helpful notes
Article - https://fwmotion.com/blog/operating-systems/2020-09-04-installing-fedora-...