I buy Banana Pi M2 Zero, and try to use latest Fedora 28 on it, but the
device don't start with it. When I try tu use original Arbian, than
device works as expected, so device is OK.
Will be there support for this device in Fedora?
I know that this is a cheap board and probably no one want to waste
time with this "low quality" stuff.
However Fedora boot without any issue.
My question is: what about on board wifi? Is it better to go for an
USB wifi adapter?
I would like to ask representatives of Fedora Working Groups and Spins
and Labs SIGs to work with the Fedora Marketing team and solicit
bullet points for the F28 Final release announcement.
Thanks and Regards,
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
F27 will not boot on the new Model 3+. Green LED blinks 4 times
(medium), then 4 times (fast), then repeats. The colored splash screen
Might this be just a device tree problem? Raspbian journal contains a line:
raspberrypi kernel: OF: fdt:Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
Do we just need a bcm2710-rpi-3-b-plus.dtb file in Fedora's /boot
filesystem? Has anyone succeeded to boot Fedora on the 3+ Pi?
I used F28 latest image ( Fedora-Server-armhfp-28-20180412.n.0-sda.raw.xz) on my RPi3+. It was able to boot, but I stucked quite early - on dnf command, which does not work on my device currently. I did and obtained folowing:
[root@localhost ~]# dnf clean metadata
Cache was expired
45 files removed
[root@localhost ~]# dnf updateinfo
Fedora Modular 28 - armhfp 2.6 MB/s | 159 kB 00:00
Fedora Modular 28 - armhfp - Updates 3.2 kB/s | 257 B 00:00
Fedora Modular 28 - armhfp - Test Updates 2.5 MB/s | 345 kB 00:00
Fedora 28 - armhfp - Test Updates 4.8 MB/s | 14 MB 00:02
Fedora 28 - armhfp - Updates 5.2 kB/s | 257 B 00:00
Fedora 28 - armhfp 4.9 MB/s | 54 MB 00:11
Last metadata expiration check: 0:00:00 ago on Fri 13 Apr 2018 03:29:10 AM EDT.
Traceback (most recent call last):
File "/usr/bin/dnf", line 58, in <module>
File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 179, in user_main
errcode = main(args)
File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 64, in main
return _main(base, args, cli_class, option_parser_class)
File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 99, in _main
return cli_run(cli, base)
File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 115, in cli_run
File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 1015, in run
File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 768, in _process_demands
File "/usr/lib/python3.6/site-packages/dnf/base.py", line 454, in fill_sack
File "/usr/lib/python3.6/site-packages/dnf/base.py", line 217, in _setup_modules
module_metadata = ModuleMetadataLoader(repo).load()
File "/usr/lib/python3.6/site-packages/dnf/module/metadata_loader.py", line 53, in load
File "/usr/lib/python3.6/site-packages/modulemd/__init__.py", line 99, in loads_all
File "/usr/lib/python3.6/site-packages/modulemd/__init__.py", line 229, in loadd
raise ValueError("The supplied metadata version isn't supported")
ValueError: The supplied metadata version isn't supported
I was able to find the same problem in some discussion threads in the past, now the problem appeared again.
with actual kernel-4.16.0-300.fc28.armv7hl from Fedora 28 Beta no Xorg
is working on my Odroid XU4 and the system load is constant at 4 .
with kernel-core-4.16.0-0.rc6.git2.1.fc29.armv7hl everything is working
fine. I can work on Xorg with mate (slow, but it works) an system load
is nearly 0.
QA is trying to consolidate target sizes for all images built by Fedora into a single document that we can easily check, in a response to one of blocking images being oversize again . The document of choice is this wiki page . In a newly added column, the target size of each release-blocking image will be documented. (It can also contain target sizes of non-blocking images, but our major focus is on the blocking ones, of course). The target size will be a blocker for Fedora Final releases.
These ARM images are currently considered blocking :
We're not aware of any size limits on those images at the moment. We'd like you to think over whether this is correct, decide on new numbers if needed, and then write it down into the document . (If you decide to change it in the future, notifying us at the same time is very appreciated.)
We'd like to avoid the situation when the image goes oversize and the target size is simply bumped, because it adds delays to the release process. So please think ahead and choose a size that you really want to keep and block on it (You can of course also choose to have no=unlimited target size).
Peter sorry for the confusion and thank you for the prompt reply
in your reply to Fri, Mar 23, 2018 at 11:28 AM, Tomáš Frolík
"Once it's running if you update the kernel to rc6 you should be
running just fine. One other thing to note is there's some different
bits needed for the wifi. I'm going to put all of those, inc the one
needed for the original Pi3, into an rpm but I've not had a chance to
do that as yet. Give me a day or so and I'll likely get that done."
This is what I was enquiring about. I have fedora 28 beta running in a
3B+ all good but no wifi.
Regards Chris Hall