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 year
Fedora on Odroid M1
by Andreas Reschke
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
1 year, 5 months
Include arm SBCs in the renewed Fedora docs homepage and make it more visible?
by Peter Boy
On behalf of the docs team:
We are in the process to renew the content of the Fedora docs homepage at https://docs.fedoraproject.org. For details see https://communityblog.fedoraproject.org/fedora-docs-is-about-to-change-si...
My questions is wouldn't it be beneficial to include all your work on Fedora support of SBC boards, i.e. Raspberry Pi & Co., in the new homepage.
Content-wise, this could be a page with a brief overview of SBC support with a link to the SIG Wiki page, plus installation instructions and an overview of supported supports. The latter two would then replace the existing wiki pages and will become the authoritative reference. Of course, more is also possible.
Writing the docs pages would not be the problem. But the SIG would have to do a final review of the pages and do the update in the future. Docs team would be able to support that. There are also simple tools to do the updates, easier to use than the wiki pages.
In the positive case, we would introduce a new „box“, probably next to Quick Docs, on the planned page (see https://pboy.fedorapeople.org/fedora/fedora-docs-2.html), e.g. "Fedora on Single Board Computers: RasPi & Co" (or hopefully a better and catchier wording).
It would be really nice to get a dedicated decision and not just a rejection by ignorance.
1 year, 7 months
System no longer bootable after latest update.
by Peter Boy
Yesterday I (re-)installed my Rock Pi4 with F36 and then did an update.
During the update there showed up various messages listed below. Afterwards the system didn’t boot anymore.
Last messages on screen:
Started Plymouth-start.ser?e - Show Plymouth Boot Screen
Started systems-ask-passw*uests to Plymouth Directory Watch.
Reached target paths.target - Path Units.
Reached target basic.target - Basic System.
Then nothing happened anymore.
One question is, how to fix it.
The other question is how can such a disaster happen? With an item that is offered for download on the Fedora Server page, something like this should not happen.
Update messages
Updating: selinux-policy-36.14-1.fc36.noarch 240/670
Scriptlet: selinux-policy-36.14-1.fc36.noarch 240/670
Updating: selinux-policy-targeted-36.14-1.fc36.noarch 241/670
Scriptlet: selinux-policy-targeted-36.14-1.fc36.noarch 241/670
uavc: op=load_policy lsm=selinux seqno=2 res=1Regex version mismatch, expected: 10.39 2021-10-29 actual: 10.40 2022-04-14
Regex version mismatch, expected: 10.39 2021-10-29 actual: 10.40 2022-04-14
Scriptlet: container-selinux-2:2.188.0-1.fc36.noarch 242/670
Updating: container-selinux-2:2.188.0-1.fc36.noarch 242/670
Scriptlet: container-selinux-2:2.188.0-1.fc36.noarch 242/670
uavc: op=load_policy lsm=selinux seqno=3 res=1Regex version mismatch, expected: 10.39 2021-10-29 actual: 10.40 2022-04-14
Regex version mismatch, expected: 10.39 2021-10-29 actual: 10.40 2022-04-14
Updating: containers-common-4:1-59.fc36.noarch 243/670
Scriptlet: freeipa-selinux-4.9.10-4.fc36.noarch 244/670
Updating: freeipa-selinux-4.9.10-4.fc36.noarch 244/670
Ausgeführtes Scriptlet: freeipa-selinux-4.9.10-4.fc36.noarch 244/670
uavc: op=load_policy lsm=selinux seqno=4 res=1Regex version mismatch, expected: 10.39 2021-10-29 actual: 10.40 2022-04-14
Regex version mismatch, expected: 10.39 2021-10-29 actual: 10.40 2022-04-14
Updating: freeipa-common-4.9.10-4.fc36.noarch 246/670
Scriptlet: smartmontools-selinux-1:7.3-2.fc36.noarch 246/670
uavc: op=load_policy lsm=selinux seqno=5 res=1Regex version mismatch, expected: 10.39 2021-10-29 actual: 10.40 2022-04-14
Regex version mismatch, expected: 10.39 2021-10-29 actual: 10.40 2022-04-14
Updating: krb5-pkinit-1.19.2-11.fc36.aarch64 247/670
Updating: krb5-workstation-1.19.2-11.fc36.aarch64 248/670
...
Updating: cockpit-ws-275-1.fc36.aarch64 251/670
Scriptlet: cockpit-ws-275-1.fc36.aarch64 251/670
uavc: op=load_policy lsm=selinux seqno=6 res=1Regex version mismatch, expected: 10.39 2021-10-29 actual: 10.40 2022-04-14
Regex version mismatch, expected: 10.39 2021-10-29 actual: 10.40 2022-04-14
…
Updating: nss-3.81.0-1.fc36.aarch64 253/670
Scriptlet: nss-3.81.0-1.fc36.aarch64 253/670
Updating: certmonger-0.79.15-3.fc36.aarch64 254/670
Scriptlet: certmonger-0.79.15-3.fc36.aarch64 254/670
No CA with name "certmaster" found.
Updating: libblockdev-crypto-2.27-1.fc36.aarch64 255/670
...
Scriptlet: certmonger-0.79.15-2.fc36.aarch64 351/670
Scriptlet: nfs-utils-1:2.6.1-0.rc3.fc36.aarch64 352/670
Clean up : nfs-utils-1:2.6.1-0.rc3.fc36.aarch64 352/670
Scriptlet: nfs-utils-1:2.6.1-0.rc3.fc36.aarch64 352/670
Not supported unit type
Clean Up : sssd-tools-2.7.0-1.fc36.aarch64 353/670
Scriptlet: sssd-kcm-2.7.0-1.fc36.aarch64 354/670
Updating: nss-3.81.0-1.fc36.aarch64 253/670
Scriptlet: nss-3.81.0-1.fc36.aarch64 253/670
Updating: certmonger-0.79.15-3.fc36.aarch64 254/670
Scriptlet: certmonger-0.79.15-3.fc36.aarch64 254/670
No CA with name "certmaster" found.
1 year, 7 months
Test of Fedora-Server-37-20220831.n.0.aarch64 image
by Peter Boy
I just tested the image on my rock pi 4a and it failed to boot. The last messages on screen are
| [OK] Found device dev-mapper-fe_ice - /dev/mapper/fedora-root.
| [OK] Reached target ignited-root_e.target - Initrd Root Device
And then nothing happened any more.
It’s booting from the NMVe device. F36 works fine.
My old raspi3 dir does boot, but showed
| Booting ‚Fedora Linux (5.19.3-300.fc37.aarch64) …
| [ 11.976909] dracut-pre-udev[394]: sh: line 1:/sbin/sysctl: No such file or directory
But continues to boot without problems.
1 year, 7 months
