On Fri, Dec 22, 2017 at 12:37 PM, Jan Pazdziora <jpazdziora(a)redhat.com> wrote:
Hello,
I've got Banana Pi M64 on which I am able to run
2017-08-14-ubuntu-16.04-mate-desktop-beta-aarch64-bpi-m64-sd-emmc.img
from
http://www.banana-pi.org/m64-download.html reasonably well,
except for failing WiFi connections to hidden SSID networks and
for kodi being unbearably slow, even the UI and mouse movements.
So seeing Ubuntu MATE not failing completely, I thought I'd give
Well I suspect the Ubuntu images uses a vendor kernel and proprietary
display drivers, neither of which we will support in Fedora for
obvious reasons.
Fedora a try. I've used
Fedora-Minimal-27-1.6.aarch64.raw.xz
Upon boot I see U-Boot (?) output and EFI lines and then row of Tuxes
and initial boot messages but then my TV goes blank. At no point during
the boot (like grub interface) do I have USB (mouse, keyboard) working.
There is no display support [1] for the A64 SoC as yet, you'll need to
use a serial console.
There might be simple FB support landing in the 4.16 kernel so if that
support does land there will be basic text output support in Fedora
28.
[1]
https://nullr0ute.com/2017/11/overview-of-aarch64-sbc-support-in-fedora-27/
When I add the dtb symlink to workaround
https://bugzilla.redhat.com/show_bug.cgi?id=1528575
I see wired networking and DHCP working. Upgrading kernel seems to break
the wired networking
https://bugzilla.redhat.com/show_bug.cgi?id=1528593
You should add the ARMTracker tracking bug so we'e aware of ARM
related kernel bugs.
I'm aware of the breakage but I took some PTO and given the NIC
drivers for the 64 bit AllWinner stuff was pulled back I've not had
time to fix it. I'm sorry (I'm really not) but you can either stick on
the 4.13 kernels until I get time to fix it or go to the 4.15rc6
kernel [2] which is known to work.
[2]
https://koji.fedoraproject.org/koji/buildinfo?buildID=1012407
but with all the other packages from updates upgraded, the board
still
works including wired networking and DHCP.
The initial-setup.service seems to be looping during the boot and it
seems to also affect dnf operations so I've disabled it.
If it's run properly from the serial console on the first boot it will
disable itself.
Is there any opinion about how well can Banana Pi M64 be supported
by Fedora at this point, given that the board seems fine under Ubuntu
MATE but that might include some non-OSS bits that we might not want
in Fedora.
As I explain in the blog post referenced above there is no display
support for any of the AllWinner 64 bit devices.... and even when that
lands it'll be average support because it's a MALI chipset and won't
be accelerated. This is the case on all Allwinner devices
Specifically missing at this point seems to be USB support, console
after boot, and WiFi networking. Is there anything which might be useful
Have you looked at the upstream mailing lists to see if there's kernel
patches? As far as I can see, at least on linus's master, usb should
work (it definitely does on the various Pine64 variants) and wifi
might work if you have the appropriate brcm*.txt text file in
/lib/firmware/brcm/ (like what's needed on the RPi3). A grep through
dmesg for brcm should show more details there. I've not checked
anything older than linus's current head WRT to either of those.