Here are some of the Screenshots.
BananaPi - M64 - Manjaro Linux - KDE - Neofetch
BananaPi - M64 - Manjaro Linux - KDE - GLXGears
Here are some of the Screenshots.
BananaPi - M64 - Manjaro Linux - KDE - Neofetch
BananaPi - M64 - Manjaro Linux - KDE - GLXGears
GL_VENDOR: VMware , and with High CPU usage. That means it is not using lima. Check with them if you should have to re-build Mesa. There are some users in this forum running lima, maybe they can help.
Yes Will look into the Lima thing.
your dtb doesnt boot. It fails with the following error:
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
963 bytes read in 3 ms (313.5 KiB/s)
## Executing script at 4fc00000
** fs_devread read error - block
invalid extent block
** Can't read partition table on 0:0 **
** Invalid partition 1 **
** Can't read partition table on 0:0 **
** Invalid partition 1 **
Bad Linux ARM64 Image magic!
SCRIPT FAILED: continuing...
** Can't read partition table on 0:0 **
** Invalid partition 1 **
** Can't read partition table on 0:0 **
** Invalid partition 1 **
** Can't read partition table on 0:0 **
** Invalid partition 1 **
** Can't read partition table on 0:0 **
** Invalid partition 1 **
** Can't read partition table on 0:0 **
** Invalid partition 1 **
** Can't read partition table on 0:0 **
** Invalid partition 1 **
** Can't read partition table on 0:0 **
** Invalid partition 1 **
Device 0: device type unknown
... is now current device
ethernet@1c30000 Waiting for PHY auto negotiation to complete........ done
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
Update: Usb hub works give in my image. Anarsoul adviced to use mesa-git version to get lima to work. So will try that tomorrow.
Found the way to make lima work but the device stopped working before i could test it.
Lima will only work with mesa 19.3 which is available in our repo as mesa-git. Tried it on other device but it seem have lima only for gpu and without the vdec support. So gui on modesetting works without fbturbo.
Hi Thank you for this. I’m interested on the server version.
Yes there is a server image too.
HI: Good job, i like it.
@BPI_Justin Hi. It would be helpful if you can help me with this. As I am not able to do any development.
The modules on the v1.1 are as follows:
Currently downloading the LXQT version. While I probably will use it without screen it is often nice to have some lightwight GUI for maintenance usage.
PS: The file ending “.xz” is a bit unknown to me, which kind of compression is this, or is this only to let Yandex not confuse it with an image?
This is our standard compression at Manjaro. And I think arch uses the same. It is highly compresses. Just put it in etcher and it will decompress and flash it to the sd card. Thanks for giving it a try.
Hi @avaf I tested my dead m64 after Sinovoip asked me to use 12v but that didn’t help so i tried 5v again and it worked.
As I have the device working. I will start porting the uboot to manjaro package and maybe use right kernel for it.
Can you advice if m64 have good mainline uboot support? If so then I can build one without any patch.
Thanks.
I think u-boot-2020.04 works without any patch, at least for v1.1.
Build it tonight
Will reuse our pine64 uboot pkg for m64
Thanks for the quick reply. I am just going through your m64-kodi git repo and I see that you used mali blob’s instead of lima
I will and see if I can make use of lima with waylan on kde, if that works then it will have a smooth UI and then we can get kodi to work with gles
Thanks.
Build a latest image for M64 with Kernel 5.6.0-1 with lima and it boots to the OEM Setup but I cannot test it as my usb ports stopped working
Also My board still stucks down when powered with 5V2A DC Barrel jack. while it works fine with Micro-USB 5V2A connector. I tried all my old images and it works without USB connection I don’t think I can make use of GPIO connection of USB. I can only try to give power to the keyboard from gpio and see if it works.
@sinovoip I think the device have power ic issue since the beginning. Is there a possibility to replace it ?
Let me know thanks.
Finally got Lima to work on M64 so full HW acc for the UI.
If anyone is interested in use Manjaro ARM on M64 then do let me know I will prepare a latest image only on request and share it here as I cannot test the UI cause of my USB chip not working on the board. So without keyboard mouse I cannot test ui I can only test from UART login.
inxi -Fxzi
System:
Host: Manjaro-M64 Kernel: 5.6.0-1-MANJARO-ARM aarch64 bits: 64
compiler: gcc v: 9.1.0 Console: tty 0 Distro: Manjaro ARM
Machine:
Type: ARM Device System: BananaPi-M64 details: N/A serial: <filter>
Battery:
ID-1: axp20x-battery charge: 100% condition: N/A model: N/A
status: Charging
CPU:
Topology: Quad Core model: N/A variant: cortex-a53 bits: 64 type: MCP
arch: ARMv8 rev: 4
features: Use -f option to see features bogomips: 0
Speed: 648 MHz min/max: 648/1152 MHz Core speeds (MHz): 1: 648 2: 648
3: 648 4: 648
Graphics:
Device-1: sun50i-a64-mali driver: N/A bus ID: N/A
Device-2: sun50i-a64-dw-hdmi driver: sun8i_dw_hdmi v: N/A bus ID: N/A
Device-3: sun50i-a64-display-engine driver: sun4i_drm v: N/A bus ID: N/A
Display: server: X.org 1.20.5 driver: modesetting tty: 80x24
Message: Advanced graphics data unavailable in console. Try -G --display
Audio:
Device-1: sun50i-a64-dw-hdmi driver: sun8i_dw_hdmi bus ID: N/A
Device-2: simple-audio-card driver: N/A bus ID: N/A
Device-3: simple-audio-card driver: N/A bus ID: N/A
Sound Server: ALSA v: k5.6.0-1-MANJARO-ARM
Network:
Device-1: sun50i-a64-emac driver: dwmac_sun8i v: N/A port: N/A bus ID: N/A
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
IP v6: <filter> type: noprefixroute scope: link
Device-2: mmc-pwrseq-simple driver: pwrseq_simple v: N/A port: N/A
bus ID: N/A
WAN IP: <filter>
Drives:
Local Storage: total: 22.12 GiB used: 3.98 GiB (18.0%)
ID-1: /dev/mmcblk0 model: SS16G size: 14.84 GiB
ID-2: /dev/mmcblk2 model: 8GTF4R size: 7.28 GiB
Partition:
ID-1: / size: 14.40 GiB used: 3.98 GiB (27.6%) fs: ext4
dev: /dev/mmcblk0p2
Sensors:
Message: No sensors data was found. Is sensors configured?
Info:
Processes: 121 Uptime: 4m Memory: 1.89 GiB used: 180.2 MiB (9.3%)
Init: systemd Compilers: gcc: N/A Shell: bash v: 5.0.11 inxi: 3.0.36
Also I have build a package on chromium to make Netflix, Amazon to work smoothly on Manjaro Arm. Users can install that package themselve.
Cheers
FYI. Lima drivers came to Armbian about 16 months ago. The other day I was running Gnome3 on top of Orangepi Prime, which is similar to this. On the acceptable level. You don’t need to do anything … it just works.
Can you explain what you did?
Yes I am aware of this dear. I respect Armbian and their team alot cause that’s the source of linux kernel for most of the sbc. I tested this now as this board was dead since long time but now its working without a functional usb chip. I tried the lima config in xorg and it worked and as you know manjaro is rolling release we always have latest mesa package from git for testing. The docker image was worked by someone else for pinebookpro and manjaro and we optimized it with updated widevine, and chromium to use gpu hw acc. So its not just my achievements its team work
I had vim1 aml s905x mali-450 which gives me glmark2 1920x1080 score of 58 which is quite ok for mali-450. Assuming a64 have better support in display controller i expect it to give better gpu performance
Alot of workarounds. As you know we only maintain aarch64 and there is no widevine for it we had to use chromium armv7 with chromeos widevine as everyone else does like kodi, le and ce. This can be done in docker or nspawn, I have used docker for now but plan to use nspawn in future to reduce overhead of dockers libs.
Does armbian use armv7 or both depending on the board arch? Afaik armbian image maintained by oleg is aarch64 so you will need chromium armv7 with gpu hw acc. Here is a screenshot of Netflix on vim1 with lima.
Quite watchable.
@igorpec Thanks for all your work with armbian and always replying in the forums.
Highly appreciated.
Cheers.
It is still unclear what you did if anything? What you are showing me is no video hw acceleration involved … Lima only drives things like this https://webglsamples.org/ If you have a strong machine like VIM, video is watchable …
I don’t know what extra is needed for Netflix. If you were doing workaround - can we see what? Perhaps community can improve it?
Mesa drivers are good enough also on Ubuntu since 19.10. They are too old on Bionic, but works on Focal user land OOB … or on Debian unstable / sid
… where packages are build from the trunk.
IDK if you’re aware of Widevine on a Browser is always Software accelerated. So the video playback will always be using CPU. This is what I have understood by watching Netflix on my X64 laptop and also on aarch64 boards.
DM
Got it write.
What do you mean ? You mean built from git repo ? Then yes