March 2023 - arm - Fedora Mailing-Lists

BeagleBone Black cannot boot with Fedora 34/35

by Zamir SUN

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/

1 month, 3 weeks

2
3
0 / 0

Pine64 RockPro doesn't boot with F38 Beta 1 nor branched 20230326 nightly composed

by Peter Boy

Fedora 37 aarch64 Server edition works just fine. With F38 beta 1 & branched 20230326 it starts: U-Boot 2023.04-rc2 (Feb 17 2023) SoC: Rockchip rk 3399 Reset cause: POR Model: Pine64 RockPro64 v2.1 ... Core: 394 devices, 33 uclasses, devicetree: separate MMC: mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0 Loading environment from SPIFlash... SF: Detected .... total 16 MiB *** Warning - bad CRC, using default evironment .... In: serial ... scanning usb for storage devices... 0 Storage Devices found Hit any key to stop autoboot: 0 ## Error: "distro_bootcmd" not definded => With F37 the first part is the same: but at the end scanning for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 2 - 1 - 0 switch to partitions #0, OK mmc1 us current device Scanning mmc 1:1 … … and continues to boot. Sorry to be so late with testing. Would be nice to get it work, nevertheless. -- Peter Boy https://fedoraproject.org/wiki/User:Pboy pboy(a)fedoraproject.org Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora docs team contributor Java developer and enthusiast

1 month, 3 weeks

6
26
0 / 0

Le Potato?

by Richard Shaw

Google has failed me. Can I run Fedora on a Le Potato? If so, what target do I use? Anything I need to do before writing the image? I plan to use eMMC if I can get it cheap enough due to the failure rate of SD cards. Thanks, Richard

1 month, 3 weeks

5
5
0 / 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

by coremodule＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2023-03-28 from 16:00:00 to 17: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.o... Source: https://calendar.fedoraproject.org//meeting/10455/

2 months

1
0
0 / 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

by coremodule＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2023-03-21 from 16:00:00 to 17: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.o... Source: https://calendar.fedoraproject.org//meeting/10455/

2 months, 1 week

1
0
0 / 0

2023-03-20 @ **16:00** UTC - Fedora 38 Blocker Review Meeting

by Adam Williamson

# F37 Blocker Review meeting # Date: 2023-03-20 # Time: **16:00** UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 5 proposed Final blockers to review, so let's have a review meeting. Remember that clocks went forward in North America last weekend, so the meeting time in UTC is an hour earlier than before. If you do not observe daylight savings time, or your clocks did not yet go forward, the meeting will be an hour earlier in your local time. Please double check! 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 F38 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 day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org https://www.happyassassin.net

2 months, 1 week

1
0
0 / 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

by coremodule＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2023-03-14 from 16:00:00 to 17: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.o... Source: https://calendar.fedoraproject.org//meeting/10455/

2 months, 2 weeks

1
0
0 / 0

2023-03-13 @ **16:00** UTC - Fedora 38 Blocker Review Meeting

by Adam Williamson

# F37 Blocker Review meeting # Date: 2023-03-13 # Time: **16:00** UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 11 proposed Final blockers to review, so let's have a review meeting. Note that clocks went forward in North America this weekend, so the meeting time in UTC is an hour earlier than before. If you do not observe daylight savings time, or your clocks did not yet go forward, the meeting will be an hour earlier in your local time. Please double check! 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 F38 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 day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org https://www.happyassassin.net

2 months, 2 weeks

1
0
0 / 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

by coremodule＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2023-03-07 from 16:00:00 to 17: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.o... Source: https://calendar.fedoraproject.org//meeting/10455/

2 months, 3 weeks

1
0
0 / 0

2023-03-06 @ 17:00 UTC - Fedora 38 Blocker Review Meeting

by Adam Williamson

# F37 Blocker Review meeting # Date: 2023-03-06 # Time: 17:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 4 proposed Beta blockers, 10 proposed Beta freeze exceptions and 7 proposed Final blockers to review, 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 F38 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 day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org https://www.happyassassin.net

2 months, 3 weeks

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm March 2023