On Mon, Jan 08, 2018 at 08:17:17AM +0000, Peter Robinson wrote: > On Fri, Dec 22, 2017 at 12:37 PM, Jan Pazdziora <jpazdziora@xxxxxxxxxx> 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. Do you think that https://github.com/yuq/linux-lima might be something to watch? Or https://free-electrons.com/blog/mali-opengl-support-on-allwinner-platforms-with-mainline-linux/ ? > > 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. OK. Out of curiosity, the boot messages that I can see at the early boot stage of Fedora 27 get output via what mechanism? > > 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. WILCO (will try to not forget ;-) next time. > 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. I'll try it when I get some cycles to focus on it again, thanks for the hint. > > 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. Does it make sense to track the fact that on console-less machine, we might want it to fail more gracefully? > > 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. I'll put this to the list of things to check. Thank you for you replies! -- Jan Pazdziora Senior Principal Software Engineer, OpenShift Security Team, Red Hat _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
