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/
5 months, 3 weeks
Fedora on Pinebook Pro
by Andreas Reschke
Hi there,
I've updated my Pinebook Pro today. With actual kernel NVME Discs are
working.
root@pinebook-pro ~]# uname -a
Linux pinebook-pro.reschke.lan 5.13.13-200.fc34.aarch64 #1 SMP Thu Aug
26 16:51:14 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
[root@pinebook-pro ~]# nvme list
Node SN Model Namespace
Usage Format FW Rev
---------------- --------------------
---------------------------------------- ---------
-------------------------- ---------------- --------
/dev/nvme0n1 2018FV440610 WDC
WDS250G2B0C-00PXH0 1 250,06 GB / 250,06
GB 512 B + 0 B 211070WD
[root@pinebook-pro ~]# df -h
Dateisystem Größe Benutzt Verf. Verw%
Eingehängt auf
devtmpfs 1,9G 0 1,9G 0% /dev
tmpfs 1,9G 1,2M 1,9G 1% /dev/shm
tmpfs 767M 1,8M 766M 1% /run
/dev/mapper/fedora_pinebook--pro-root 56G 6,1G 47G 12% /
tmpfs 1,9G 3,1M 1,9G 1% /tmp
/dev/mapper/fedora_pinebook--pro-homelv 216G 8,8G 196G 5% /home
/dev/mmcblk2p2 976M 197M 713M 22% /boot
/dev/mmcblk2p1 599M 5,9M 593M 1% /boot/efi
tmpfs 384M 68K 384M 1%
/run/user/1000
[root@pinebook-pro ~]#
The last thing what I want to have is external Monitor over USB-C.
Thanks to all who managed these.
Andreas
1 year, 11 months
Fedora 35 status and testing needed
by Adam Williamson
Hi folks! Just wanted to give an update on Fedora 35 status and beg for
testing :D
We are now down to either one or two blocker bugs. They are in quite
specific areas so the fixes will not be hugely impactful to anything
else. I'm hoping to be able to run an RC compose later today (Tuesday).
However, we're also only 2 days from go/no-go.
Given this, it'd be super helpful if people could help get the
validation tests run on the current nominated nightly compose. We don't
need to wait for an RC to run most tests; for the more complicated or
trickier tests, we can run them now against a nightly and the results
can be counted so long as nothing relevant changes in the RC.
I've just manually nominated the most recent compose (20211018.n.0) for
testing; it won't have the fixes currently in updates-testing (mainly
for plasma-discover), so take that into account. You can see the
summary page (which shows results from all individual pages) here:
https://fedoraproject.org/wiki/Test_Results:Current_Summary
you can enter results by editing individual sections from that page
(the wiki will automagically edit the correct individual page), or by
using the relval tool - just 'dnf install relval' then 'relval report-
results'.
You can look for tests that really need to be run here:
https://openqa.fedoraproject.org/testcase_stats/35/
each of the pages there shows a sort of 'over time view' of the test
cases of that type, showing when it was most recently run and a little
chart view that illustrates which composes the test has been run on and
what the results were (green for pass, orange for warn, red for
failed). Look out for tests that have release level 'Basic', 'Beta' or
'Final' and which have not been run recently or at all; these are the
ones to focus on. For instance, at
https://openqa.fedoraproject.org/testcase_stats/35/Desktop.html we can
see that several of the desktop tests have not yet been run on aarch64;
it'd be great if anyone with an aarch64 system capable of running
Workstation could run those tests and add the results.
Thanks everyone!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 year, 11 months
Fedora ARM and AArch64 Status Meeting Minutes 2021-10-19
by Paul Whalen
========================================================
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
========================================================
Meeting started by pwhalen at 15:00:41 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-2/2021-10-19/fedora_ar...
.
Meeting summary
---------------
* roll call (pwhalen, 15:00:41)
* LINK:
https://fedoraproject.org/wiki/Test_Results:Fedora_35_Branched_20211018.n...
(pwhalen, 15:03:48)
* 1) ==== Userspace Status ==== (pwhalen, 15:04:56)
* No new issues. (pwhalen, 15:05:54)
* 2) ==== Kernel Status ==== (pwhalen, 15:06:01)
* kernel-5.15.0-0.rc6.47.fc36 (pwhalen, 15:06:11)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1846599
(pwhalen, 15:06:11)
* kernel-5.14.13-300.fc35 (pwhalen, 15:11:00)
* LINK:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1846290sa
(pwhalen, 15:11:00)
* Please test and report any issues to the list or #fedora-arm.
(pwhalen, 15:17:18)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2014462
(pbrobinson, 15:18:44)
* https://bugzilla.redhat.com/show_bug.cgi?id=2014462 Kernel panic in
tpm_tis_spi driver on reboot (device release) (pbrobinson,
15:19:08)
* 3) ==== Bootloader Status ==== (pwhalen, 15:20:39)
* uboot-tools-2021.10-2.fc35 (pwhalen, 15:20:50)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1846324
(pwhalen, 15:20:50)
* 4) ==== Fedora 35 ==== (pwhalen, 15:26:56)
* Latest Fedora 35 Nominated Nightly (pwhalen, 15:27:05)
* LINK:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
(pwhalen, 15:27:05)
* Blockers (pwhalen, 15:27:44)
* LINK:
https://qa.fedoraproject.org/blockerbugs/milestone/35/final/buglist
(pwhalen, 15:27:45)
* It is possible to go through the initial setup without creating a
root and without adding a user to the wheel group (pwhalen,
15:28:07)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2015490
(pwhalen, 15:28:07)
* LINK: https://pagure.io/fedora-qa/blocker-review/issue/555
(pwhalen, 15:30:14)
* Fedora 35 aarch64 cloud image based openstack VM hangs (pwhalen,
15:31:51)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2011928
(pwhalen, 15:31:51)
* 5) == Open Floor == (pwhalen, 15:39:47)
Meeting ended at 15:42:48 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* pwhalen (56)
* pbrobinson (16)
* zodbot (6)
* jlinton (6)
* coremodule (2)
Generated by `MeetBot`_ 0.3
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 11 months