arm October 2022

arm@lists.fedoraproject.org

7 participants
15 discussions

BeagleBone Black cannot boot with Fedora 34/35
by Zamir SUN 04 Apr '23

04 Apr '23

Hi, Recently I reflashed my BeagleBone Black. However, I find it simply cannot go beyond uboot with Fedora 34 or Fedora 35. Images I tried: Fedora-Minimal-35-20211020.n.0.armhfp.raw.xz Fedora-Minimal-34-1.2.armhfp.raw.xz If I press the button when plug the power cable, it will loop forever like the following U-Boot SPL 2021.10 (Oct 14 2021 - 00:00:00 +0000) Trying to boot from MMC1 U-Boot SPL 2021.10 (Oct 14 2021 - 00:00:00 +0000) Trying to boot from MMC1 U-Boot SPL 2021.10 (Oct 14 2021 - 00:00:00 +0000) Trying to boot from MMC1 CCCCCCCC U-Boot SPL 2021.10 (Oct 14 2021 - 00:00:00 +0000) Trying to boot from MMC1 If I don't press the button it will boot directly to the system in emmc. I've tried different tf cards and concluded it's not the card issue. The latest image that works for me on BBB is Fedora-Minimal-armhfp-33-1.2-sda.raw.xz It's interesting that the image has a different name schema that F34/F35 ones(the sda in filename). I roughly remember I also tried F33 without 'sda' - Fedora-Minimal-33-1.3.armhfp.raw.xz and IIRC this also cannot boot. So is there any different for images with or without -sda ? Can anyone offer some suggestions how I can test or boot F35 on BBB? Thanks in advance! -- Zamir SUN GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E Want to know more about Fedora? Visit https://fedoraproject.org/wiki/ Ready to contribute? See https://whatcanidoforfedora.org/ 想了解更多中文资讯，访问 https://zh.fedoracommunity.org/

2 3

Thinkpad X13s, a wikipage about support development
by Germano Massullo 29 Nov '22

29 Nov '22

More and more Fedora people are buying the Thinkpad X13s and willing to participate in the testing and development for the Linux support. Some Fedora developers have already managed to successfully boot Fedora. I would like to ask if we can create a Fedora wiki page with all instructions to build a live USB with all needed tweaks and other infos. By doing this, it will be easier for the testers to quickly get to a point where they can provide useful data. Moreover this Fedora wiki page could be also used to keep track of the developments. Cheers

3 5

Fedora on Odroid M1
by Andreas Reschke 19 Nov '22

19 Nov '22

Hello, I would like to buy a Odroid M1 (CPU RK3568B2, petitboot as bootloader). Is there any change to install Fedora on it? Even a headless installation would be nice. Greetings Andreas

2 5

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠fedoraproject.org 30 Oct '22

30 Oct '22

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2022-11-01 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.libera.chat The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/9910/

1 0

2022-10-31 @ 16:00 UTC - Fedora 37 Blocker Review Meeting
by Adam Williamson 28 Oct '22

28 Oct '22

# F36 Blocker Review meeting # Date: 2022-10-31 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 1 proposed Final freeze exception to review, but also we can probably kick around the plans for the release process over the next couple of weeks (hence the wide distribution on this mail - come along if you want to talk about that!), so let's have a review meeting. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F36 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Info on RC 1.4 incoming
by Adam Williamson 24 Oct '22

24 Oct '22

Hey folks! Just wanted to give a heads-up that there's an RC 1.4 incoming. There was an oversight in the RC 1.3 compose that meant it got an older version than intended of uboot-tools, which is critical for boot on ARM platforms. The difference between the version included in RC 1.3 and the one that was meant to be there is big enough that it seemed a good idea to respin; usually I'd have asked for Peter Robinson's input on this, but he's on PTO, so this seemed the safer course. Including the correct uboot-tools version will be the only difference between RC 1.3 and RC 1.4. That means many RC 1.3 test results will be valid for 1.4 and can be transferred if necessary. We should definitely re-do all the key ARM tests, and we should also redo the 'smoke tests' for x86_64 - the "default boot and install" tests, tests where we make sure the images actually write to a USB stick and boot and install properly, just in case something weird goes wrong in the compose process. But for tests like the desktop and server application functionality, we don't necessarily need to repeat any of those that have already been done for 1.3. So, when 1.4 lands, please focus on the 'smoke tests', ARM testing, and any tests that were not run for 1.3. Thanks folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠fedoraproject.org 23 Oct '22

23 Oct '22

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2022-10-25 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.libera.chat The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/9910/

1 0

NanoPC-t4 does not boot with branch 20221008
by Peter Boy 19 Oct '22

19 Oct '22

Last week I got my hands on a FriendlyElec NanoPC-t4 I tried to boot branch 20221008, but the boot process stopped at: [OK] Reached target basic.target - Basic System [14.886445] dracut-initqueue[696]: WARNING: File locking is disabled. Starting dbs-broker.serv…ice - D-Bus System Message Bus … [OK] Found device dev-mapper-fe…ice - /dev/mapper/fedora-root. [OK] Reached target initrd-root...e.target – Initrd Root Device. [OK] Started dbus-broker.service – D-Bus System Message Bus. The same is true with Beta 1.5 and with Fedora 36. It looks similar to an error I had with my Radxa Rock Pi 4a which was resolved (the Rock Pi boots that branch without any problems, even from NVMe disk using Armbian SPI Flash, by the way). Some branches earlier the process stopped at the same line, but after about 15 mins continued repeatedly showing the same error message again and again, and finally an emergency mode shell prompt. Unfortunately I didn’t noted any details because I run out of time. So I retried today with the current branch. It it helps I can try to find the branch with the latter behaviour.

2 9

Fwd: [Test-Announce] Fedora 37 Candidate RC-1.2 Available Now!
by Adam Williamson 18 Oct '22

18 Oct '22

Hi folks, just a heads-up that the second RC for 37 Final is out now and we need to get through the testing by Thursday. There are a few potential blockers to work through, but so far I kinda suspect we may decide to reject or waive the ones that have arisen, so I still want to treat this as a 'viable' candidate for now and get all the tests run on it. This particularly includes the Active Directory tests (pinging sgallagh, thanks as always...) and testing Cloud on real clouds. The forwarded email has links to the results pages, which have links to the images (including AMIs on the Cloud results page). You can edit results into the wiki pages directly or use `relval report-results` (after `dnf -y install relval`) which is a CLI that edits the pages for you and makes the process slightly less annoying. :D Thanks a lot folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠fedoraproject.org 16 Oct '22

16 Oct '22

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2022-10-18 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.libera.chat The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/9910/

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm October 2022