Manjaro arm on Amlogic Tv box?

[dante6913]

Using kodi-wayland-19.0-6-aarch64.pkg.tar.zst from archlinuxdroid repo it seems that hardware acceleration video decoding works, (using 20% of system) and playing is fluid, but its strange because it says it is software acceleration. (Using linux-vim 5.11.2-1 and manjaro with gnome)

[JFL]

@spikerguy

This kernel panic is something different and not the one from previous bootloader issue, I have seen some kernel panic on AMlogic S905X3 as well. Still did not get time to see what is causing it as I am not getting any logs posted on uart.

Thanks for the info. I understand this kernel panic I am experiencing with linux-vim 5.11.2-1 seems different from previously. Previous kernel panic I can repeatedly induce it.

[spinax]

Hi @TheMojoMan, thank you for your reply
Yes I did follow those instructions using KDE edition, but I’m considering using XFCE because KDE isn’t fluid on my X96Max+. Does KDE edition works smoothly on your device ?
I wanted to know, when using linux-vim, do you choose the vim version of your .dtb files ?

[spinax]

Hi @spikerguy thank you
I am using an X96Max+ 4Gb/64Gb but I don’t know if this is the information you’re asking about. Chipset is AmLogic S905X3.

[spinax]

@TheMojoMan I once managed to extract the .dtb file from the android system installed on the X96M+ and convert it back to .dts. But I don’t have any knowledge in this language and It didn’t work when I tried to boot Mjro with it. I can share it if you’re interested by analyzing it

[rna]

@JFL

As long as you are using the “boot-vim3-2020.10-1” with GT King Pro it will work well with Manjaro-Arm and it works with linux or linux-vim kernel.

OK noted.

@spikerguy

we have a new thread where we add support to different boards ?

That would be great if we have a new thread for X96 Max+, I think everything is almost perfect, except for Blutooth and Audio Jack.

For H96 Max RK3399 I have made the thread, but still merged with Rockchip Topic. Everything is running perfectly, except bluetooth. I am waiting a cavalry to help to fix this.

Manjaro ARM for Rockchip TV Boxes

Finally I can boot to Manjaro using Vim3 image and “u-boo t-rk3399-nanopc-t4” via dd in terminal. So at first, I tried to install Manjaro on a new virtual machine and compile the image from Arm Installer for nanopc-t4 as per @spikerguy advice. But I still unable to boot on my box. Then I tried many attempt to understand Balbes150’s uboot topic on LibreElec. After many many hours of trial, finally I understood and actually it’s quite easy to do: Download Arm vim3 image from Manjaro official d…

Maybe it can help someone with H96 Max RK3399, please refer to the link above.

@spinax

I once managed to extract the .dtb file from the android system installed on the X96M+ and convert it back to .

As far as I know, android dtb is not working with mainline kernel. Unless there’s somebody that is skillfull to upgrade the code from kernel 4.9x to the mainline kernel. Therefore please stick with the @TheMojoMan dtb for X96 Max+.

In case you had a problem with booting after upgrade from linux-vim 20.12 to the latest stable release, I have backup of my boot partition and I can confirm that it works flawlessly without the problem that I mentioned above in discussion number 767. Here it is:

@rna

I updated the box now I got this error while booting:

** No partition table - mmc 1 **
MMC Device 2 not found
no mmc device at slot 2
ethernet@ff3f000 Waiting for PHY auto negotiation to complete… TIMEOUT !
Could not initialize PHY ethernet@ff3f000
missing environment variable: pxeuuid

Now my box failed to Boot

Based on my experience, sometimes an upgrade cause the box failed to boot. Therefore I would advise to make backup of the boot partition. In my case I make backup of the working unstable image. Therefore when it comes to the problem from stable release, I just need to restore my backup boot partition. Copy all files, except for “image” and “image.gz” use from your current update that failed to boot. With this workaround you will be able to boot to your box. I used @TheMojoMan method and his latest dtb for mainline but by box still cannot boot, until I came up with this workaround and the problem is solved event by using the old dtb. Just to let you know that I did this backup workaround on Armbian as well and my box never failed to boot.

This X96 Max+ box comes with three variants:

• 2gb / 16gb
• 4gb / 32gb
• 4gb / 64gb

The device tree for 2gb/16gb and 4gb/64gb is different, I don’t know about the 4gb/32gb because mine is the 4gb/64gb.

[TheMojoMan]

@spinax

Does KDE edition works smoothly on your device ?

I am sorry, since I do not use KDE I cannot answer this question. Tried it some time ago (last years November I think) and it was not very smooth as you have mentioned.

@spinax

I wanted to know, when using linux-vim, do you choose the vim version of your .dtb files ?

Sure. The vim version for the vim kernel and the other version for the mainline kernel if you want to go experimental. Hopefully, some day the fixes of the vim kernel will be integrated into the mainline kernel and then there should be no need for different .dtb files.

@spinax

I can share it if you’re interested by analyzing it

Thanks for the offer but I already extracted the .dtb from Android myself.

@spinax

… and convert it back to .dts.

That is a dead end as you have experienced. It is like taking the square root of x squared

[JFL]

Found out how to rectify Chromium visual glitch when displaying certain webpage.Chromium “GPU rasterization” when Enabled might cause the certain webpage with foreing text (eg. chinese characters) to have visual screen artifacts.

Disable “GPU rasterization” and the webpage will be displayed with no visual artifacts.

@spikerguy, Just upgraded to linux-vim 5.11.4-1 from linux-vim 5.11.2-1. All key functions working.

[spinax]

I am sorry, since I do not use KDE I cannot answer this question. Tried it some time ago (last years November I think) and it was not very smooth as you have mentioned.

Which version are you using ? I tried Manjaro-ARM-xfce-vim3-20.12.img.xz but it shows a turquoise screen when I boot the device. Did you experience this bug ?

[TheMojoMan]

@spinax

I tried Manjaro-ARM-xfce-vim3-20.12.img.xz but it shows a turquoise screen when I boot the device. Did you experience this bug ?

Interesting! I do not experience this bug on my X96Max+ (which I have successively updated over the past weeks) but have the same problem with my X96Mini which I have updated yesterday.
This is a well known bug of Amlogic devices that is related to the boot loader and was fixed (a long time ago) by adding the correct u-boot.ext file to the boot partition.
Since I do not have access to my boxes right now I cannot test it myself but you can try to rename the file u-boot-s905x2??? to u-boot.ext that is located at the boot partition of your sd card and have a look if this changes something.

[spinax]

In fact I went through and when I installed linux-vim (+updated the system) the screen went back to black. I noticed that the strcture of BOOT partition changed and extlinux folder was added (like in KDE edition).
Now sound is working, bluetooth seems to be recognized (but I haven’t tested yet) but Wifi doesn’t work.
Would the installation of linux-vim-headers add or change anything ?
I also noticed the display is flickering
I am now trying to test the bluetooth

UPDATE : in fact bluetooth doesn’t work either. Here’s the output of rfkill and blueman-adapters

xmaxx@x96 ~]$ rfkill & blueman-adapters
[1] 1019
ID TYPE DEVICE SOFT HARD
0 bluetooth hci0 débloqué débloqué
blueman-adapters version 2.1.4 starting
blueman-adapters 19.46.04 ERROR Adapter:53 init : No adapter(s) found
[1]+ Fini rfkill

[TheMojoMan]

@spinax

but Wifi doesn’t work.

For wifi to work you have to install rtl8822cs-dkms (don’t know exactly the name of the package right now). Maybe also bc, linux-vim-headers and make. I remember that some dependency was missing that was not installed automatically.

Edit: See post 702 or 703 → you have to install bc for rtl8822cs to compile correctly.

[JFL]

@SickOS

I have installed a generic 5.11.3 Ubuntu kernel from kernel.ubuntu.com on a Ubuntu ports distro, and I have sound. This is a not vim kernel but works.

Hi @SickOS Does wifi also work with Ubuntu kernel 5.11.3? How do you go about install it? Thanks.

[SickOS]

Hi JFL

Wifi driver stopped working because of 5.11 kernel, but installing the new updated driver solved the problem.

[JFL]

Hi @spikerguy
I have two Manjaro-Arm-XFCE image one using linux-vim 5.11.4-1 and another linux 5.11.4. The linux-vim default to cpupower governor “Performance” and linux kernel to “schedutil” and force to “Performance”.

FYI, I noticed with linux-vim kernel off and on there is a bit of hesitancy but not with linux kernel. No sure is specific to my situation.

[JFL]

spikerguy

Posts: 29

Joined: Thu Apr 30, 2020 12:35 am

languages_spoken: english

ODROIDs: HC4

Has thanked: 8 times

Been thanked: 15 times

Contact:

Contact spikerguy

Re: [OS] Manjaro ARM for HC4

Post by spikerguy » Tue Mar 16, 2021 5:05 am

Added Odroid OLED PKG in repo
Now Odroid HC4 have full support, Only thing left is VPU encoding which I have been trying using Chewitts ffmpeg source but no luck yet.

If anyone else have interest then we all can work on it together and try to get it to work.

These users thanked the author spikerguy for the post:

jgmdev (Tue Mar 16, 2021 9:53 am)

Manjaro ARM Team

Top
@spikerguy, Looking forward to have hardware video acceleration on Manjaro Amlogic Devices using ffmpeg

[rna]

@TheMojoMan I just found out the way to fix the Bluetooth issue on my H96 Max - RK3399 by converting the dtb to dts, then editing the bluetooth parameter in dts file info the correct driver name. I am pretty sure that this method can be transferred to fix the Bluetooth of X96 Max+.
Have a look here: Manjaro ARM for Rockchip TV Boxes - #55 by rna

However the only thing that I don’t know is the driver name of the wifi. Do you have any idea what is the correct driver name?

In that post I changed the parameter from:

		bluetooth {
			compatible = "brcm,bcm43438-bt";

Into this:

		bluetooth {
			compatible = "qcom,qca9377-bt";

and it fixes my bluetooth

I need those two driver name after compatible = …

As you said in the previous post, the bluetooth driver is already in the firmware. The only thing that is needed is fixing the dtb to use that correct driver. And it has to be those two name drivers. I have tried changing the last one, but it works partially. Once you have those two name, I am pretty sure that this might solve the bluetooth issue.

[spikerguy]

I’ve tried it few times still no success. Need to find what is missing.

[TheMojoMan]

@rna

However the only thing that I don’t know is the driver name of the wifi.

I did already include the correct name a while ago in my latest .dtb that you can download but unfortunately it does not fix the problem. It seems the bluetooth adapter is not active and I do not know how to wake it up, yet. Always shows error -110. With kernel 5.10 even the firmware was loaded once in a while but bluetooth adapter was still not present.

For X96Max+ it must be:

compatible = “realtek,rtl8822cs-bt”.

See Linux v5.12-rc3 - Documentation/devicetree/bindings/net/realtek-bluetooth.yaml

SPDX-License-Identifier: GPL-2.0

%YAML 1.2

$id: http://devicetree.org/schemas/net/realtek-bluetooth.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: RTL8723BS/RTL8723CS/RTL8822CS Bluetooth Device Tree Bindings

maintainers:

• Vasily Khoruzhick anarsoul@gmail.com
• Alistair Francis alistair@alistair23.me

description:
RTL8723CS/RTL8723CS/RTL8822CS is WiFi + BT chip. WiFi part is connected over
SDIO, while BT is connected over serial. It speaks H5 protocol with few
extra commands to upload firmware and change module speed.

properties:
compatible:
oneOf:
- const: “realtek,rtl8723bs-bt”
- const: “realtek,rtl8723cs-bt”
- const: “realtek,rtl8822cs-bt”

device-wake-gpios:
maxItems: 1
description: GPIO specifier, used to wakeup the BT module

enable-gpios:
maxItems: 1
description: GPIO specifier, used to enable the BT module

host-wake-gpios:
maxItems: 1
description: GPIO specifier, used to wakeup the host processor

required:

• compatible

additionalProperties: false

examples:

• |
  #include <dt-bindings/gpio/gpio.h>

  uart1 {
  pinctrl-names = “default”;
  pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>;
  uart-has-rtscts;

  bluetooth {
      compatible = "realtek,rtl8723bs-bt";
      device-wake-gpios = <&r_pio 0 5 GPIO_ACTIVE_HIGH>; /* PL5 */
      host-wake-gpios = <&r_pio 0 6 GPIO_ACTIVE_HIGH>; /* PL6 */
  };
  

  };

[rna]

@TheMojoMan

I did already include the correct name a while ago in my latest .dtb

Glad to hear that

@TheMojoMan

• const: “realtek,rtl8723bs-bt”
• const: “realtek,rtl8723cs-bt”
• const: “realtek,rtl8822cs-bt”

I know this might be a silly question, but Have you tried all of this three combination? Or the other name for the first line? Because in my H96 Max - RK3399 case, the Wifi is QCA9377, but my wifi driver is taken from Ath10k (Atheros) from the firmware. Instead of using “atheros”, the bluetooth use “qcom”. Which is a Qualcomm, I was surprised myself.

EDIT:
I Just Found Out that Atheros is the product of Qualcomm. That makes sense.