Any plan for basic mainline linux support?

[istanbulls]

Thank you for what you said.
I have a child's curiosity in me that never grows. I ask a lot of questions about everything.
Yeah, you're right, in my experience.
But my biggest handicap is that I don't speak any English and I'm not very talented to learn a language: D
I can sew all kinds of clothes (I have exported clothes to the whole world for many years), I can make all kinds of home furniture, I can make all kinds of delicious food, I can create very creative clothes, furniture, chandeliers, meals (yes they say I am creative), electrical, electronic repair everything. and mostly fix it. But I can't learn a new language

I appreciate you and thank you for everything.

[brad]

@chewitt is the man! a great project manager who is very proficient in organising technical resources and collaborating with the community for the greater good.

Buy that man a beer

[crashoverride]

One of the issues with Amlogic 4.9 DRM driver is that it has no cursor (secondary) plane support. This results in Wayland/Weston being unusable for desktop (no mouse cursor).

I keep checking mainline at each release and it appears the situation has not changed:
https://github.com/torvalds/linux/blob/ ... #L307-L313

Code: Select all

	ret = meson_plane_create(priv);
	if (ret)
		goto free_drm;


	ret = meson_overlay_create(priv);
	if (ret)
		goto free_drm;

There is a single framebuffer and a single video plane (hardware supports at least two of each). The video plane only accepts YUV derived color formats (non-RGB). While this does not affect Android or *ELEC, its been an issue for desktop support.

[istanbulls]

@chewitt is the man! a great project manager who is very proficient in organising technical resources and collaborating with the community for the greater good.

Buy that man a beer

yes i should do that, and we should how can we get him beer. I'm making very nice Lager beers but it doesn't make much sense to send him from Istanbul
Anyway, I'd love to get him a beer!

[chewitt]

For someone who speaks no English we understand you very well (Google translate does a good job sometimes). For the beer donation, the thought is appreciated but I never accept personal donations. I earn enough in my day-job to fund my vacations and Porsche habit and I'm sure there is a good cause somewhere that deserves your $$ more than me. Maybe next time I'm in Instanbul for business we can meet for a coffee .. I am there every 2-3 months for work

[istanbulls]

@chewitt

This is great news, I would be honored to welcome you, I would be very pleased.

[ajcard]

Sounds like the ram is working. So, you haven't tested ethernet yet?

it works. had some probs with the surf stick, solved. alsa is not working yet, but I have no
experience with it. I've used oss all the time

[chewitt]

thanks for the updates. means that by 5.9 (which i think will be long LTS till 2025) most stuff will be working, but may need out-of-tree patches for HDR and H265

I think everything will be upstream long before then as there are commercially funded "Android on mainline" projects with milestones and timescales. HEVC was already working on GX before the compliance changes broke it, and the issue with G12 is in firmware not codec. HDR is already sort-of working on Allwinner and Rockchip which have near-identical versions of DesignWare IP and Kodi/ffmpeg has bare-bones HDR support in the GBM/VAAPI code path after Intel adopted Kodi as their userspace app for getting the initial HDR changes merged in 5.3 (after getting nowhere with Weston). All the ingredients are kind of available and it's mostly a developer "cat herding" exercise to get everyone in the same room and focused on the same objectives at the same time problem to bake the code. Since the summer months there's been too many people busy in their real-world jobs or off-sick or on-vacation to make progress so my fingers are crossed for a cold/windy/rainy winter season to keep people indoors with their keyboards

[ajcard]

bad news:
can't get alsa to work. syslog reports:
fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
and some others, but I think this is the main cause and a driver problem.
Does anybody now something about this?

good news:
the unreleased pre 5.5 kernel compiles and runs.

bad news:
cant get alsa to work. syslog ....
<break>

[elatllat]

5.4.1 (lkml)
builds (and script).

[elatllat]

5.4.2 (lkml)
builds (and script).

[maier-johno]

Hello elatllat, I just wanted to say thank you for all your efforts! For all the compilied kernel-images and for the great script!

[elatllat]

5.5.0-rc1 (lkml)
builds (and script).

[ResdexR6]

Hi,
So far I did not test your Kernel, but I will check it, when I get my second N2 in a few weeks.
Did anybody try to run UFW init with 5.* Kernel?
With the Hardkernel 4.9 I got ip6tables Errors. I could not get UFW to work with 4.9

[rooted]

Hi,
So far I did not test your Kernel, but I will check it, when I get my second N2 in a few weeks.
Did anybody try to run UFW init with 5.* Kernel?
With the Hardkernel 4.9 I got ip6tables Errors. I could not get UFW to work with 4.9

I imagine it was simply a kernel configuration issue, some necessary module likely wasn't enabled or loaded.

[elatllat]

UFW has no chains so is like coding without functions; horrific.

Anyway according to https://wiki.gentoo.org/wiki/Ufw

Code: Select all

zgrep -E "CONFIG_(NF_CONNTRACK_NETBIOS_NS|IP6_NF_MATCH_HL|IP6_NF_MATCH_RT)[= ]" /proc/config.gz

would tell you if UFW is compatible with a kernel. (Maybe I'll add those configs to my next build)

select IPTables support check;

Code: Select all

zgrep -E "CONFIG_(IPV6|NF_CONNTRACK|NETFILTER_NETLINK_LOG|NETFILTER_XTABLES|NETFILTER_XT_MATCH_CONNTRACK|CONFIG_IP_NF_IPTABLES|IP6_NF_IPTABLES)[= ]" /proc/config.gz

[elatllat]

5.4.3 (lkml)
builds (and script).

[ResdexR6]

UFW has no chains so is like coding without functions; horrific.

Anyway according to https://wiki.gentoo.org/wiki/Ufw

Code: Select all

zgrep -E "CONFIG_(NF_CONNTRACK_NETBIOS_NS|IP6_NF_MATCH_HL|IP6_NF_MATCH_RT)[= ]" /proc/config.gz

would tell you if UFW is compatible with a kernel. (Maybe I'll add those configs to my next build)

select IPTables support check;

Code: Select all

zgrep -E "CONFIG_(IPV6|NF_CONNTRACK|NETFILTER_NETLINK_LOG|NETFILTER_XTABLES|NETFILTER_XT_MATCH_CONNTRACK|CONFIG_IP_NF_IPTABLES|IP6_NF_IPTABLES)[= ]" /proc/config.gz

I tried

Code: Select all

 zgrep -E "CONFIG_(NF_CONNTRACK_NETBIOS_NS|IP6_NF_MATCH_HL|IP6_NF_MATCH_RT)[= ]" /proc/config.gz
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_RT=m

and:

Code: Select all

zgrep -E "CONFIG_(IPV6|NF_CONNTRACK|NETFILTER_NETLINK_LOG|NETFILTER_XTABLES|NETFILTER_XT_MATCH_CONNTRACK|CONFIG_IP_NF_IPTABLES|IP6_NF_IPTABLES)[= ]" /proc/config.gz 
CONFIG_IPV6=y
CONFIG_NETFILTER_NETLINK_LOG=y
CONFIG_NF_CONNTRACK=m
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_IP6_NF_IPTABLES=m

I opened the gentoo wiki link but I have no clue what these messages mean.
Note this is not any of your images, but maybe you can tell me what is the problem.

[rooted]

Looks like you have what you need and you just have to load the modules.

[elatllat]

5.4.4 (lkml)
builds (and script).

[elatllat]

5.4.5 (lkml)
builds (and script).

[erm67]

@elatllat I was comparing the boot.ini created by your script with that shipped by hardkernel and I noticed a difference, maybe it is not really important but after loading the dtb in memory they use the command fdt addr to inform uboot about the location of the dtb: https://www.denx.de/wiki/view/DULG/UBootCmdFDT

Code: Select all

# Load kernel, dtb and initrd
fatload mmc ${devno}:1 ${k_addr} Image.gz
fatload mmc ${devno}:1 ${dtb_loadaddr} meson64_odroidn2.dtb
fatload mmc ${devno}:1 ${initrd_loadaddr} uInitrd
fdt addr ${dtb_loadaddr}
# unzip the kernel
unzip ${k_addr} ${loadaddr}

# boot
booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}

Maybe it is not important but I added the fdt addr command to my boot.ini as well like this:

Code: Select all

fatload mmc ${devno}:1 ${dtb_loadaddr} meson-g12b-odroid-n2.dtb
fatload mmc ${devno}:1 0x01080000 uImage
fdt addr ${dtb_loadaddr}
bootm 0x1080000 - ${dtb_loadaddr

[brad]

Maybe it is not important but I added the fdt addr command to my boot.ini as well like this:

I don't believe the vendor uboot can correctly understand the format of mainline dtb so it is unable to read or modify the image even if it knows the memory location.

[erm67]

good point, I will try a couple of fdt commands the next time I connect the serial. The vendor dtb can be decoded correctly by the dtc compiler, so the format is standard ... maybe you mean that the names of the nodes (symbols) defined inside are different from what the proprietary uboot expects ... but I don't think uboot reinitializes the hw after the command.
It looks like the n2 uses the ancient and heavily modified uboot from amlogic:
https://wiki.odroid.com/odroid-n2/softw ... ing_u-boot
It would be interesting however since I use it as a server and don't need hdmi cec and stuff like that, there was very useful boot.ini for the odroid c2 that used fdt rm commands to remove the nodes of the graphic devices and boot the C2 headless, it was able to free several hundreds of MB of RAM, I remember. There was also an howto that explained how free the ram used by unwanted devices. Something like that would be useful for the N2 as well, even if it could probably free a 100MB

[evrflx]

I am really eager to get more free memory as well - using the odroid n2 as a mini-cluster node for kubernetes and don't need any GPU or graphics.

[elatllat]

5.4.6 (lkml)
builds (and script).

[tobetter]

I've uploaded the Ubuntu Bionic Minimal image that boots with Linux v5.4.6 kernel, download from link and its default account and password is odroid/odroid. In order to test Wayland with the Weston, you can follow up on the commands to install the necessary packages on the image.

Installing Mali userland driver as well as the kernel driver.

Code: Select all

$ sudo apt update
$ sudo apt install -y linux-headers-$(uname -r)
$ sudo apt install -y mali-bifrost-wayland-driver mali-bifrost-dkms
$ sudo reboot

Once reboot, install Weston and glmark2-es2-wayland.

Code: Select all

$ sudo -s
# apt install -y weston glmark2-es2-wayland
# mkdir -p /tmp/${UID}-runtime-dir
# export XDG_RUNTIME_DIR=/tmp/${UID}-runtime-dir
# weston --tty=1 &
# glmark2-es2-wayland

Please note that this is the first integration of the mainline kernel and Mali Wayland driver, many features would not function. I am also trying to boot GDM3 on this image, no luck to run mutter yet. Please advise me if you have any instructions to make it work.

[Sav]

I've uploaded the Ubuntu Bionic Minimal image that boots with Linux v5.4.6 kernel, download from link and its default account and password is odroid/odroid. In order to test Wayland with the Weston, you can follow up on the commands to install the necessary packages on the image.

Installing Mali userland driver as well as the kernel driver.

Code: Select all

$ sudo apt update
$ sudo apt install -y linux-headers-$(uname -r)
$ sudo apt install -y mali-bifrost-wayland-driver mali-bifrost-dkms
$ sudo reboot

Once reboot, install Weston and glmark2-es2-wayland.

Code: Select all

$ sudo -s
# apt install -y weston glmark2-es2-wayland
# mkdir -p /tmp/${UID}-runtime-dir
# export XDG_RUNTIME_DIR=/tmp/${UID}-runtime-dir
# weston --tty=1 &
# glmark2-es2-wayland

Please note that this is the first integration of the mainline kernel and Mali Wayland driver, many features would not function. I am also trying to boot GDM3 on this image, no luck to run mutter yet. Please advise me if you have any instructions to make it work.

Thanks a lot.
I just finshed to run the test:

Code: Select all

=======================================================
    glmark2 2014.03+git20150611.fa71af2d
=======================================================
    OpenGL Information
    GL_VENDOR:     ARM
    GL_RENDERER:   Mali-G52
    GL_VERSION:    OpenGL ES 3.2 v1.r16p0-01rel0.2943fc4ef9657d91ee32c9a58dec6cd2
=======================================================
[build] use-vbo=false: FPS: 852 FrameTime: 1.174 ms
[build] use-vbo=true: FPS: 1444 FrameTime: 0.693 ms
[texture] texture-filter=nearest: FPS: 1289 FrameTime: 0.776 ms
[texture] texture-filter=linear: FPS: 1439 FrameTime: 0.695 ms
[texture] texture-filter=mipmap: FPS: 1389 FrameTime: 0.720 ms
[shading] shading=gouraud: FPS: 1192 FrameTime: 0.839 ms
[shading] shading=blinn-phong-inf: FPS: 1170 FrameTime: 0.855 ms
[shading] shading=phong: FPS: 1113 FrameTime: 0.898 ms
[shading] shading=cel: FPS: 1185 FrameTime: 0.844 ms
[bump] bump-render=high-poly: FPS: 496 FrameTime: 2.016 ms
[bump] bump-render=normals: FPS: 1621 FrameTime: 0.617 ms
[bump] bump-render=height: FPS: 1659 FrameTime: 0.603 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 1026 FrameTime: 0.975 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 379 FrameTime: 2.639 ms
[pulsar] light=false:quads=5:texture=false: FPS: 1919 FrameTime: 0.521 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 358 FrameTime: 2.793 ms
[desktop] effect=shadow:windows=4: FPS: 742 FrameTime: 1.348 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 126 FrameTime: 7.937 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 124 FrameTime: 8.065 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 160 FrameTime: 6.250 ms
[ideas] speed=duration: FPS: 383 FrameTime: 2.611 ms
[jellyfish] <default>: FPS: 1149 FrameTime: 0.870 ms
[terrain] <default>: FPS: 59 FrameTime: 16.949 ms
[shadow] <default>: FPS: 530 FrameTime: 1.887 ms
[refract] <default>: FPS: 101 FrameTime: 9.901 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 2193 FrameTime: 0.456 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 2498 FrameTime: 0.400 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 2343 FrameTime: 0.427 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 2374 FrameTime: 0.421 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 2187 FrameTime: 0.457 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 2275 FrameTime: 0.440 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 2253 FrameTime: 0.444 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 2238 FrameTime: 0.447 ms
=======================================================
                                  glmark2 Score: 1220
=======================================================
Segmentation fault

It's normal the segmentation fault at the end?

[brad]

I've uploaded the Ubuntu Bionic Minimal image that boots with Linux v5.4.6 kernel, download from link and its default account and password is odroid/odroid. In order to test Wayland with the Weston, you can follow up on the commands to install the necessary packages on the image.

Thanks @tobetter I have it a shot and is working.

I'm trying to test gnome

1) Added odroid user to video group

Code: Select all

sudo usermod -aG video odroid

2) installed basic packages

Code: Select all

$ sudo apt-get install gdm3 wayland-protocols gnome-session-wayland

Gnome runs and gives me the icon to select Gnome or Gnome on X11 but im not getting mali accelleration via wayland. I think mutter or clutter rather might need a recompile to support egl.

[Sav]

I've uploaded the Ubuntu Bionic Minimal image that boots with Linux v5.4.6 kernel, download from link and its default account and password is odroid/odroid. In order to test Wayland with the Weston, you can follow up on the commands to install the necessary packages on the image.

Thanks @tobetter I have it a shot and is working.

I'm trying to test gnome

1) Added odroid user to video group

Code: Select all

sudo usermod -aG video odroid

2) installed basic packages

Code: Select all

$ sudo apt-get install gdm3 wayland-protocols gnome-session-wayland

Gnome runs and gives me the icon to select Gnome or Gnome on X11 but im not getting mali accelleration via wayland. I think mutter or clutter rather might need a recompile to support egl.

Some days ago Memeka told me that

MATE on mir on wayland is a prototype. I don't see any reason to have MATE running over GNOME - with XOrg MATE is faster, but this is not the case with Wayland, since GNOME is more stable than the proof of concept MATE atm.
Also you must remember, only GTK3 apps have support for Wayland, and last time I used MATE it still had GTK2 apps.
If you want to have a desktop-accelerated nice GUI and think GNOME is too slow or you don't like it, then I would recommend Enlightenment. It works very well on Wayland, and is very fast. It also looks good (see https://phab.enlightenment.org/file/dat ... eme_Sample).

[tobetter]

@Sav and @brad, I am not that expert to explain why GPU acceleration is not working as expected as of now, but learning what it should be. I will welcome your advice and suggestions. The image I've shared is built with the packages from my personal repository ppa.linuxfactory.or.kr that has many experimental packages, a version of any package starting with 5: comes from my repo and the rest are from Ubuntu repo.

[RussianNeuroMancer]

I think mutter or clutter rather might need a recompile to support egl.

With Panforst on NanoPC-T4 Gnome Shell Wayland worked for me without recompilation.

[brad]

With Panforst on NanoPC-T4 Gnome Shell Wayland worked for me without recompilation.

Yes Panfrost is only working for some arm midgard boards at the moment. bifrost (N2) is still in development. Method above is using arm / amlogic wayland drivers and libmali.

[RussianNeuroMancer]

Yes Panfrost is only working for some arm midgard boards at the moment. bifrost (N2) is still in development. Method above is using arm / amlogic wayland drivers and libmali.

I know, the point is - you don't need no recompile compositor to enable egl support, at least on Ubuntu 19.04/19.10.

[Sav]

Yes Panfrost is only working for some arm midgard boards at the moment. bifrost (N2) is still in development. Method above is using arm / amlogic wayland drivers and libmali.

I know, the point is - you don't need no recompile compositor to enable egl support, at least on Ubuntu 19.04/19.10.

Did you get an accelerated desktop with the latest Ubuntu?

Inviato dal mio GM1913 utilizzando Tapatalk

[brad]

know, the point is - you don't need no recompile compositor to enable egl support, at least on Ubuntu 19.04/19.10.

Oh sorry I see, the image is based on 18.04.3 LTS for the moment. Its mutter 3.28.1.

mutter fails with an error about no backend clutter drivers. it appears it trying to use GL rather than gles2

I pulled the source and tried compiling with defaults but it complains about missing GL libraries even though they appear to exist.

Its trying to use /usr/lib/aarch64-linux-gnu/libgl.so which is not linked to libmali.so

So maybe a compile with gl disabled might help, otherwise maybe I update to 19.10 as it using a later version of mutter

[brad]

Did you get an accelerated desktop with the latest Ubuntu?

Only for basic weston, have not been able to get gnome or kde plasma working with wayland as yet

[RussianNeuroMancer]

Did you get an accelerated desktop with the latest Ubuntu?

Unfortunately, I don't have N2 (yet) to help with finding out what exactly is broken regarding Gnome Shell Wayland session, I just point out that issue described in this message is most likely caused by mali driver itself or the way it was packaged.

[brad]

Did you get an accelerated desktop with the latest Ubuntu?

Unfortunately, I don't have N2 (yet) to help with finding out what exactly is broken regarding Gnome Shell Wayland session, I just point out that issue described in this message is most likely caused by mali driver itself or the way it was packaged.

Yes thanks, the libmali seems to be missing some extensions (gbm) that mutter requires, @memeka had some patches to work around on 3.32 here but pastbin has expired viewtopic.php?f=176&t=33993&start=50#p250371

I will try to use his compat libraries with 3.28.1 to see if it helps as for the moment I cant recompile standard ubuntu mutter due to missing GL library error. Other than this ill update the image to Ubuntu 19.10 to see if mutter will detect the libmali drivers.

[RussianNeuroMancer]

@memeka had some patches to work around on 3.32 here but pastbin has expired viewtopic.php?f=176&t=33993&start=50#p250371

There is link to deb repository in the same message, try that.

[tobetter]

Did you get an accelerated desktop with the latest Ubuntu?

Unfortunately, I don't have N2 (yet) to help with finding out what exactly is broken regarding Gnome Shell Wayland session, I just point out that issue described in this message is most likely caused by mali driver itself or the way it was packaged.

Yes thanks, the libmali seems to be missing some extensions (gbm) that mutter requires, @memeka had some patches to work around on 3.32 here but pastbin has expired viewtopic.php?f=176&t=33993&start=50#p250371

I will try to use his compat libraries with 3.28.1 to see if it helps as for the moment I cant recompile standard ubuntu mutter due to missing GL library error. Other than this ill update the image to Ubuntu 19.10 to see if mutter will detect the libmali drivers.

I have recompiled mutter v3.28 with the patch of @memeka in my repository but having an error this. Any suggestion to figure out this?

Code: Select all

# mutter --nested --wayland

(mutter:3544): mutter-WARNING **: 03:04:06.641: Failed to create backend: Unable to open display, DISPLAY not set

After installing mutter on my Ubuntu image, its version should be like this.

Code: Select all

dpkg -l | grep mutter
ii  libmutter-2-0:arm64                  5:3.28.1-1ubuntu1+201912260632~bionic arm64        window manager library from the Mutter window mana
ger
ii  mutter                               5:3.28.1-1ubuntu1+201912260632~bionic arm64        lightweight GTK+ window manager
ii  mutter-common                        5:3.28.1-1ubuntu1+201912260632~bionic all          shared files for the Mutter window manager

The mutter is linked with libGL, FYI.

Code: Select all

# ldd /usr/bin/mutter
        linux-vdso.so.1 (0x0000ffff9d9ca000)
        libmutter-2.so.0 => /usr/lib/aarch64-linux-gnu/libmutter-2.so.0 (0x0000ffff9d84b000)
        libglib-2.0.so.0 => /usr/lib/aarch64-linux-gnu/libglib-2.0.so.0 (0x0000ffff9d73d000)
        libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x0000ffff9d5e4000)
        /lib/ld-linux-aarch64.so.1 (0x0000ffff9d99f000)
        libGL.so.1 => /usr/lib/aarch64-linux-gnu/libGL.so.1 (0x0000ffff9d4e5000)
        libEGL.so.1 => /usr/lib/aarch64-linux-gnu/libEGL.so.1 (0x0000ffff9c330000)
        libupower-glib.so.3 => /usr/lib/aarch64-linux-gnu/libupower-glib.so.3 (0x0000ffff9c2ff000)
        libgnome-desktop-3.so.17 => /usr/lib/aarch64-linux-gnu/libgnome-desktop-3.so.17 (0x0000ffff9c2b9000)
        libXcomposite.so.1 => /usr/lib/aarch64-linux-gnu/libXcomposite.so.1 (0x0000ffff9c2a6000)
        libXcursor.so.1 => /usr/lib/aarch64-linux-gnu/libXcursor.so.1 (0x0000ffff9c28d000)
        libXdamage.so.1 => /usr/lib/aarch64-linux-gnu/libXdamage.so.1 (0x0000ffff9c27a000)
        libXfixes.so.3 => /usr/lib/aarch64-linux-gnu/libXfixes.so.3 (0x0000ffff9c264000)
        libXi.so.6 => /usr/lib/aarch64-linux-gnu/libXi.so.6 (0x0000ffff9c246000)
        libxkbfile.so.1 => /usr/lib/aarch64-linux-gnu/libxkbfile.so.1 (0x0000ffff9c212000)
        libxkbcommon-x11.so.0 => /usr/lib/aarch64-linux-gnu/libxkbcommon-x11.so.0 (0x0000ffff9c1fa000)
        libxkbcommon.so.0 => /usr/lib/aarch64-linux-gnu/libxkbcommon.so.0 (0x0000ffff9c1b0000)
        libXrender.so.1 => /usr/lib/aarch64-linux-gnu/libXrender.so.1 (0x0000ffff9c197000)
        libX11-xcb.so.1 => /usr/lib/aarch64-linux-gnu/libX11-xcb.so.1 (0x0000ffff9c185000)
        libxcb.so.1 => /usr/lib/aarch64-linux-gnu/libxcb.so.1 (0x0000ffff9c155000)
        libxcb-randr.so.0 => /usr/lib/aarch64-linux-gnu/libxcb-randr.so.0 (0x0000ffff9c136000)
        libxcb-res.so.0 => /usr/lib/aarch64-linux-gnu/libxcb-res.so.0 (0x0000ffff9c122000)
        libstartup-notification-1.so.0 => /usr/lib/aarch64-linux-gnu/libstartup-notification-1.so.0 (0x0000ffff9c10a000)
        libcanberra-gtk3.so.0 => /usr/lib/aarch64-linux-gnu/libcanberra-gtk3.so.0 (0x0000ffff9c0f5000)
        libcanberra.so.0 => /usr/lib/aarch64-linux-gnu/libcanberra.so.0 (0x0000ffff9c0d5000)
        libgtk-3.so.0 => /usr/lib/aarch64-linux-gnu/libgtk-3.so.0 (0x0000ffff9ba79000)
        libgdk-3.so.0 => /usr/lib/aarch64-linux-gnu/libgdk-3.so.0 (0x0000ffff9b98f000)
        libpango-1.0.so.0 => /usr/lib/aarch64-linux-gnu/libpango-1.0.so.0 (0x0000ffff9b938000)
        libcairo.so.2 => /usr/lib/aarch64-linux-gnu/libcairo.so.2 (0x0000ffff9b83e000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib/aarch64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x0000ffff9b80f000)
        libgio-2.0.so.0 => /usr/lib/aarch64-linux-gnu/libgio-2.0.so.0 (0x0000ffff9b693000)
        libwacom.so.2 => /usr/lib/aarch64-linux-gnu/libwacom.so.2 (0x0000ffff9b679000)
        libgirepository-1.0.so.1 => /usr/lib/aarch64-linux-gnu/libgirepository-1.0.so.1 (0x0000ffff9b639000)
        libXrandr.so.2 => /usr/lib/aarch64-linux-gnu/libXrandr.so.2 (0x0000ffff9b61f000)
        libSM.so.6 => /usr/lib/aarch64-linux-gnu/libSM.so.6 (0x0000ffff9b607000)
        libICE.so.6 => /usr/lib/aarch64-linux-gnu/libICE.so.6 (0x0000ffff9b5df000)
        libX11.so.6 => /usr/lib/aarch64-linux-gnu/libX11.so.6 (0x0000ffff9b4b6000)
        libXext.so.6 => /usr/lib/aarch64-linux-gnu/libXext.so.6 (0x0000ffff9b496000)
        libXinerama.so.1 => /usr/lib/aarch64-linux-gnu/libXinerama.so.1 (0x0000ffff9b481000)
        libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x0000ffff9b3c7000)
        libdrm.so.2 => /usr/lib/aarch64-linux-gnu/libdrm.so.2 (0x0000ffff9b3a8000)
        libsystemd.so.0 => /lib/aarch64-linux-gnu/libsystemd.so.0 (0x0000ffff9b324000)
        libinput.so.10 => /usr/lib/aarch64-linux-gnu/libinput.so.10 (0x0000ffff9b2e4000)
        libgudev-1.0.so.0 => /usr/lib/aarch64-linux-gnu/libgudev-1.0.so.0 (0x0000ffff9b2ca000)
        libgobject-2.0.so.0 => /usr/lib/aarch64-linux-gnu/libgobject-2.0.so.0 (0x0000ffff9b26a000)
        libmutter-clutter-2.so => /usr/lib/aarch64-linux-gnu/mutter/libmutter-clutter-2.so (0x0000ffff9b11e000)
        libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0 (0x0000ffff9b0f2000)
        libpcre.so.3 => /lib/aarch64-linux-gnu/libpcre.so.3 (0x0000ffff9b080000)
        libGLX.so.0 => /usr/lib/aarch64-linux-gnu/libGLX.so.0 (0x0000ffff9b040000)
        libGLdispatch.so.0 => /usr/lib/aarch64-linux-gnu/libGLdispatch.so.0 (0x0000ffff9af12000)
        libdl.so.2 => /lib/aarch64-linux-gnu/libdl.so.2 (0x0000ffff9aefd000)
        libstdc++.so.6 => /usr/lib/aarch64-linux-gnu/libstdc++.so.6 (0x0000ffff9ad6a000)
        libwayland-server.so.0 => /usr/lib/aarch64-linux-gnu/libwayland-server.so.0 (0x0000ffff9ad49000)
        libwayland-client.so.0 => /usr/lib/aarch64-linux-gnu/libwayland-client.so.0 (0x0000ffff9ad2c000)
        libgcc_s.so.1 => /lib/aarch64-linux-gnu/libgcc_s.so.1 (0x0000ffff9ad08000)
        libudev.so.1 => /lib/aarch64-linux-gnu/libudev.so.1 (0x0000ffff9acdc000)
        libseccomp.so.2 => /lib/aarch64-linux-gnu/libseccomp.so.2 (0x0000ffff9ac87000)
        libxcb-xkb.so.1 => /usr/lib/aarch64-linux-gnu/libxcb-xkb.so.1 (0x0000ffff9ac61000)
        libXau.so.6 => /usr/lib/aarch64-linux-gnu/libXau.so.6 (0x0000ffff9ac4e000)
        libXdmcp.so.6 => /usr/lib/aarch64-linux-gnu/libXdmcp.so.6 (0x0000ffff9ac39000)
        libxcb-util.so.1 => /usr/lib/aarch64-linux-gnu/libxcb-util.so.1 (0x0000ffff9ac21000)
        libvorbisfile.so.3 => /usr/lib/aarch64-linux-gnu/libvorbisfile.so.3 (0x0000ffff9ac09000)
        libtdb.so.1 => /usr/lib/aarch64-linux-gnu/libtdb.so.1 (0x0000ffff9abe5000)
        libltdl.so.7 => /usr/lib/aarch64-linux-gnu/libltdl.so.7 (0x0000ffff9abcc000)
        libgmodule-2.0.so.0 => /usr/lib/aarch64-linux-gnu/libgmodule-2.0.so.0 (0x0000ffff9abb8000)
        libpangocairo-1.0.so.0 => /usr/lib/aarch64-linux-gnu/libpangocairo-1.0.so.0 (0x0000ffff9ab9c000)
        libcairo-gobject.so.2 => /usr/lib/aarch64-linux-gnu/libcairo-gobject.so.2 (0x0000ffff9ab81000)
        libatk-1.0.so.0 => /usr/lib/aarch64-linux-gnu/libatk-1.0.so.0 (0x0000ffff9ab4d000)
        libatk-bridge-2.0.so.0 => /usr/lib/aarch64-linux-gnu/libatk-bridge-2.0.so.0 (0x0000ffff9ab0f000)
        libepoxy.so.0 => /usr/lib/aarch64-linux-gnu/libepoxy.so.0 (0x0000ffff9aa1b000)
        libpangoft2-1.0.so.0 => /usr/lib/aarch64-linux-gnu/libpangoft2-1.0.so.0 (0x0000ffff9a9f8000)
        libfontconfig.so.1 => /usr/lib/aarch64-linux-gnu/libfontconfig.so.1 (0x0000ffff9a9a8000)
        libwayland-cursor.so.0 => /usr/lib/aarch64-linux-gnu/libwayland-cursor.so.0 (0x0000ffff9a98e000)
        libwayland-egl.so.1 => /usr/lib/aarch64-linux-gnu/libwayland-egl.so.1 (0x0000ffff9a97c000)
        librt.so.1 => /lib/aarch64-linux-gnu/librt.so.1 (0x0000ffff9a965000)
        libthai.so.0 => /usr/lib/aarch64-linux-gnu/libthai.so.0 (0x0000ffff9a94d000)
        libpixman-1.so.0 => /usr/lib/aarch64-linux-gnu/libpixman-1.so.0 (0x0000ffff9a8e9000)
        libfreetype.so.6 => /usr/lib/aarch64-linux-gnu/libfreetype.so.6 (0x0000ffff9a83e000)
        libpng16.so.16 => /usr/lib/aarch64-linux-gnu/libpng16.so.16 (0x0000ffff9a803000)
        libxcb-shm.so.0 => /usr/lib/aarch64-linux-gnu/libxcb-shm.so.0 (0x0000ffff9a7f0000)
        libxcb-render.so.0 => /usr/lib/aarch64-linux-gnu/libxcb-render.so.0 (0x0000ffff9a7d5000)
        libz.so.1 => /lib/aarch64-linux-gnu/libz.so.1 (0x0000ffff9a7a8000)
        libselinux.so.1 => /lib/aarch64-linux-gnu/libselinux.so.1 (0x0000ffff9a775000)
        libresolv.so.2 => /lib/aarch64-linux-gnu/libresolv.so.2 (0x0000ffff9a74e000)
        libmount.so.1 => /lib/aarch64-linux-gnu/libmount.so.1 (0x0000ffff9a6f1000)
        libffi.so.6 => /usr/lib/aarch64-linux-gnu/libffi.so.6 (0x0000ffff9a6d9000)
        libuuid.so.1 => /lib/aarch64-linux-gnu/libuuid.so.1 (0x0000ffff9a6c2000)
        libbsd.so.0 => /lib/aarch64-linux-gnu/libbsd.so.0 (0x0000ffff9a6a0000)
        liblzma.so.5 => /lib/aarch64-linux-gnu/liblzma.so.5 (0x0000ffff9a66e000)
        liblz4.so.1 => /usr/lib/aarch64-linux-gnu/liblz4.so.1 (0x0000ffff9a642000)
        libgcrypt.so.20 => /lib/aarch64-linux-gnu/libgcrypt.so.20 (0x0000ffff9a587000)
        libmtdev.so.1 => /usr/lib/aarch64-linux-gnu/libmtdev.so.1 (0x0000ffff9a572000)
        libevdev.so.2 => /usr/lib/aarch64-linux-gnu/libevdev.so.2 (0x0000ffff9a549000)
        libjson-glib-1.0.so.0 => /usr/lib/aarch64-linux-gnu/libjson-glib-1.0.so.0 (0x0000ffff9a513000)
        libXtst.so.6 => /usr/lib/aarch64-linux-gnu/libXtst.so.6 (0x0000ffff9a4fd000)
        libmutter-cogl-2.so => /usr/lib/aarch64-linux-gnu/mutter/libmutter-cogl-2.so (0x0000ffff9a45c000)
        libmutter-cogl-pango-2.so => /usr/lib/aarch64-linux-gnu/mutter/libmutter-cogl-pango-2.so (0x0000ffff9a443000)
        libmutter-cogl-path-2.so => /usr/lib/aarch64-linux-gnu/mutter/libmutter-cogl-path-2.so (0x0000ffff9a425000)
        libvorbis.so.0 => /usr/lib/aarch64-linux-gnu/libvorbis.so.0 (0x0000ffff9a3ed000)
        libogg.so.0 => /usr/lib/aarch64-linux-gnu/libogg.so.0 (0x0000ffff9a3d6000)
        libdbus-1.so.3 => /lib/aarch64-linux-gnu/libdbus-1.so.3 (0x0000ffff9a384000)
        libatspi.so.0 => /usr/lib/aarch64-linux-gnu/libatspi.so.0 (0x0000ffff9a348000)
        libharfbuzz.so.0 => /usr/lib/aarch64-linux-gnu/libharfbuzz.so.0 (0x0000ffff9a2a8000)
        libexpat.so.1 => /lib/aarch64-linux-gnu/libexpat.so.1 (0x0000ffff9a267000)
        libdatrie.so.1 => /usr/lib/aarch64-linux-gnu/libdatrie.so.1 (0x0000ffff9a251000)
        libblkid.so.1 => /lib/aarch64-linux-gnu/libblkid.so.1 (0x0000ffff9a1fc000)
        libgpg-error.so.0 => /lib/aarch64-linux-gnu/libgpg-error.so.0 (0x0000ffff9a1da000)
        libgraphite2.so.3 => /usr/lib/aarch64-linux-gnu/libgraphite2.so.3 (0x0000ffff9a1a7000)

[brad]

I have recompiled mutter v3.28 with the patch of @memeka in my repository but having an error this. Any suggestion to figure out this?

Can you try to see the output...

Code: Select all

LD_DEBUG=libs MUTTER_VERBOSE=1 MUTTER_DEBUG=true mutter --nested --wayland

Also try a non root user as mutter may not like the root user, you will need to add to the user to group video or give /dev/dri/card0 world read/write access

I upgraded quickly to 19.04 and added back your repo but when I install mali-bifrost-wayland-driver it does not create all the symlinks in /usr/lib/aarch64-linux-gnu so I guess the package is not compatible with 19.04. 19.04 is using mutter 3.32

[tobetter]

I have recompiled mutter v3.28 with the patch of @memeka in my repository but having an error this. Any suggestion to figure out this?

Can you try to see the output...

Code: Select all

LD_DEBUG=libs MUTTER_VERBOSE=1 MUTTER_DEBUG=true mutter --nested --wayland

Also try a non root user as mutter may not like the root user, you will need to add to the user to group video or give /dev/dri/card0 world read/write access

I upgraded quickly to 19.04 and added back your repo but when I install mali-bifrost-wayland-driver it does not create all the symlinks in /usr/lib/aarch64-linux-gnu so I guess the package is not compatible with 19.04. 19.04 is using mutter 3.32

I'm fixing the packages and uploading for Disco as I did for Bionic, please let me update when I finish it.

[memeka]

I have my N2 at work so cannot test now in holiday.
I’ll see in January

[brad]

I'm fixing the packages and uploading for Disco as I did for Bionic, please let me update when I finish it.

Im running gnome-shell like follows and it is starting. (it fails without the --no-x11)

Code: Select all

~$ WAYLAND_DISPLAY=wayland-0 dbus-run-session gnome-shell --wayland --no-x11 --display-server > /home/odroid/gnome-shell.log 2>&1

Now if I start something in this mutter window from another, its crashing with a core dump. Strangely there is a funny X11 session also running on tty10 - just a flashing "_" at the top of the screen.

Code: Select all

WAYLAND_DISPLAY=wayland-0 gnome-terminal

Code: Select all

(gnome-shell:16062): mutter-WARNING **: 04:35:10.533: drmModeSetCursor2 failed with (No such device or address), drawing cursor with OpenGL from now on
Window manager warning: Failed to set environment variable WAYLAND_DISPLAY for gnome-session: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.SessionManager" does not exist

I cannot get any of the startup daemons to run (ie gdm3, sddm or lightdm) as they try to start in X11 mode and fail usually with a fault *using" gbm_surface_create_with_modifiers. I have memeka's gbm_compat library installed and LD_PRELOAD set to load it so not sure why it is failing there for X11 (an strace shows its preloading the library with gbm_surface_create_with_modifiers function). I had to remove lib-bifrost-wayland-drivers and install libgbm1-dev to be able to compile gbm_compat before I put back the mali drivers package

Similarly I can kde to show with but cannot get a window manager to start

Code: Select all

XDG_SESSION_TYPE=wayland dbus-run-session kwin_wayland

For the moment on 19.4 nothing X11 will run (it was running with no acceleration in 18.04) and weston no longer runs - I might get back to a clean install and try to get X11 running with no acceleration on 19.04 first.

[tobetter]

I've uploaded a Ubuntu Disco minimal image that boots with Linux kernel v5.4.6 kernel, download from link.
Unlike Ubuntu Bionic, the version of Weston on Ubuntu Disco is 5.0.0 and gives an error that the symbol gbm_bo_get_plane_count is missing.

Code: Select all

[06:01:46.179] Loading module '/usr/lib/aarch64-linux-gnu/libweston-5/drm-backend.
so'
[06:01:46.210] Failed to load module: /usr/lib/aarch64-linux-gnu/libweston-5/drm-b
ackend.so: undefined symbol: gbm_bo_get_plane_count
[06:01:46.210] fatal: failed to create compositor backend

@memeka had made a library gbm-compat.so earlier that contains missing symbols in Amlogic's GBM library and I packaged it as libgbm1-compat and let the library can be loaded.

Code: Select all

$ sudo apt install libgbm1-compat

So Weston can be started but the problem this image is that the screen does not come with the errors.

Code: Select all

[06:04:33.236] failed to create kms fb: Invalid argument
[06:04:33.236] failed to get drm_fb for bo

[brad]

I've uploaded a Ubuntu Disco minimal image that boots with Linux kernel v5.4.6 kernel, download from link.

I will try this out shortly, i'm playing with Ubuntu 20.04 testing release at the moment. It has some nice features coming including new kernel by default (5.5+ when released in April), updated gnome with performance improvements and ZFS install

I could not get weston running in 19.04 either. Maybe I can take a look at the function gbm_bo_get_plane_count and add a fix to memeka's gbm_compat library.

[tobetter]

I've uploaded a Ubuntu Disco minimal image that boots with Linux kernel v5.4.6 kernel, download from link.

I will try this out shortly, i'm playing with Ubuntu 20.04 testing release at the moment. It has some nice features coming including new kernel by default (5.5+ when released in April), updated gnome with performance improvements and ZFS install

I could not get weston running in 19.04 either. Maybe I can take a look at the function gbm_bo_get_plane_count and add a fix to memeka's gbm_compat library.

Please do refer the repo I've packaged of the code of @memeka.
https://github.com/tobetter/libgbm-compat
https://github.com/tobetter/libgbm-comp ... m-compat.c

[brad]

I've uploaded a Ubuntu Disco minimal image that boots with Linux kernel v5.4.6 kernel, download from link.

This one is missing mali-bifrost-dkms package to build the kernel module. Is it easy for you to add this in or I can compile the module manually?

[tobetter]

I've uploaded a Ubuntu Disco minimal image that boots with Linux kernel v5.4.6 kernel, download from link.

This one is missing mali-bifrost-dkms package to build the kernel module. Is it easy for you to add this in or I can compile the module manually?

Oh...can you see the file if my repository is added properly? If there no contrib, please add it and do run apt update. This will let you install mali-bifrost-dkms to build mali_kbase.ko.

Code: Select all

cat /etc/apt/sources.list.d/ppa-linuxfactory-or-kr.list 
deb http://ppa.linuxfactory.or.kr disco main non-free contrib
deb-src http://ppa.linuxfactory.or.kr disco main non-free contrib

Also make sure that you have installed header package with the command sudo apt install linux-headers-$(uname -r) before installing the driver package.