F38 on RPi4-8G
by Randy DuCharme
Am I the only one having difficulties with this? It's worse than half
as fast as f37 was, NTP/Chrony refuses to work..... I could go on.
Afraid I'm going to have to ditch this. Kernel's been building for 7
hours now. Clocking, over-clocking, governors, schedulers make no
difference. Btrace, strace points to nothing. CPU load through the roof
though yet I don't see anything especially noteworthy.
Thoughts?
--
Randall DuCharme (Radio AD5GB)
Powered entirely by Open Source software.
1 month
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, 4 weeks
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
2 months