
Edit: there was a commit regarding N2 several hours ago.
I believe yes (as complete as what is in the git repo is
I searched the manjaro's forum, and stumbled on this topic: https://forum.manjaro.org/t/manjaro-arm ... 114406/120, in which Strit stated that they don't have mali blobs. So, I believe there is only the panfrost driver which doesn't support yet the G52 chipset (bifrost).mxmilkb wrote: ↑Tue Dec 31, 2019 9:16 pmI believe yes (as complete as what is in the git repo is. The PKGBUILD that creates the mesa-git package is here. There is some related talk on the Manjaro forum here. I can test and report something if anyone would like.
Re kodi; it was kodi-git-gbm that I compiled. I ran it from a pty but it was much slower than CoreELECs. There's also kodi-wayland-devel and kodi-git-wayland to try later.
(A small note for anyone who is coming to Arch/Manjaro - part of the magic of Arch is there are the official repos then there is the unofficially supported AUR (Arch User Repo) which doesn't contain package files but contains PKGBUILD scripts (potentially from any Arch user) which are used to create packages. This, combined with no "dependency hell" because everything is latest release (or latest/pinned commit for *-git packages), means that there is a vast number of applications available (covering the "long tail") that you don't have available in other distributions (I saw a statistic a few years ago that said it was x5 at that point). One big thing to note for searching for software in the AUR is that the version number listed is from the time the PKGBUILD maintainer last build the software before pushing the PKGBUILD to the AUR. If one were to build using the PKGBUILD locally, the pkgver() function in the PKGBUILD will update its pkgver= variable.)
I downloaded it and flashed on sd card with balenaetcher as usual, but it doesn't start. I get solid blue and red leds, no hdmi output, nor ethernet.mxmilkb wrote: ↑Tue Dec 31, 2019 10:16 amHere is the Firefox Send link for the minimal install - https://send.firefox.com/download/7e25d ... t_fqkIxKZg - good for 7 days or 100 downloads.
The user/password/root password/hostname is "on2".
I'm going to try enlightenment-git after kodi finally finishes compiling..
Doh.. As I said, was my first attempt ever. Taking me out of the equation would help, and it would be worth much more to others if manjaro-arm-installer could output an image file, so I've made a request to Strit.
Have I to add the tobetter's boot.ini before booting the image created with the manjaro utility?odroidn2user wrote: ↑Fri Jan 03, 2020 7:37 pmYou can build an image with the manjaro-arm-tools:
https://forum.manjaro.org/t/wiki-contri ... -arm/91053
Like:
$ sudo buildarmoem -d on2 -e kde-plasma -v myfirstbuild -n
Builds an OEM image to distribute, so without username and with configure (username, timezone, etc) script on first boot.
It is a fully automated script, which fully automatically creates/adds a boot.ini.
They use llvmpipe / fbdev / fbturbo for the user space driver and keep hardware acceleration off by default.
Thanks for the info, I am working on Qt5 with Bifrost-Wayland driver and having some progress but KDE has no luck with me yet. Still, I am testing more features of Qt5 since some examples give an error. I am looking forward to seeing KDE eye candies on ODROID-N2.odroidn2user wrote: ↑Mon Jan 13, 2020 7:51 pmThey use llvmpipe / fbdev / fbturbo for the user space driver and keep hardware acceleration off by default.
Even on devices like the rockpro64, the panfrost userspace driver isn't enabled by default.
You can enable hardware acceleration, but they have an howto for that, and that's not for bifrost devices.
https://forum.manjaro.org/t/how-to-enab ... ces/114885
They were considering making hardware acceleration the default, but up until recently (when last I checked a couple of weeks ago) they opted to go for stability over hardware acceleration.
https://forum.manjaro.org/t/status-of-o ... ima/113591
And with regards to KDE plasma being laggy, they have QT packages compiled specifically for opengl es 2, so I wouldn't expect that to be slower.
But then you have software that requires full OpenGL 2, 3 of up, and that's an extra challenge. Never even mind vulkan.
It seems to be quite a challenge to create a fully accelerated desktop stack on Linux, from kernel drivers, to userspaces drivers, to toolkits, to window managers, to end user apps, to video players actually using the VPU, etc, etc.
To be honest, I am amazed it works somewhere, with all the different standards, components, packages, libraries, etc. Let alone on devices like these!
Awesome, looking forward to the eye candies indeed!tobetter wrote: ↑Mon Jan 13, 2020 8:08 pmThanks for the info, I am working on Qt5 with Bifrost-Wayland driver and having some progress but KDE has no luck with me yet. Still, I am testing more features of Qt5 since some examples give an error. I am looking forward to seeing KDE eye candies on ODROID-N2.![]()
tobetter wrote:Thanks for the info, I am working on Qt5 with Bifrost-Wayland driver and having some progress but KDE has no luck with me yet. Still, I am testing more features of Qt5 since some examples give an error. I am looking forward to seeing KDE eye candies on ODROID-N2.odroidn2user wrote: ↑Mon Jan 13, 2020 7:51 pmThey use llvmpipe / fbdev / fbturbo for the user space driver and keep hardware acceleration off by default.
Even on devices like the rockpro64, the panfrost userspace driver isn't enabled by default.
You can enable hardware acceleration, but they have an howto for that, and that's not for bifrost devices.
https://forum.manjaro.org/t/how-to-enab ... ces/114885
They were considering making hardware acceleration the default, but up until recently (when last I checked a couple of weeks ago) they opted to go for stability over hardware acceleration.
https://forum.manjaro.org/t/status-of-o ... ima/113591
And with regards to KDE plasma being laggy, they have QT packages compiled specifically for opengl es 2, so I wouldn't expect that to be slower.
But then you have software that requires full OpenGL 2, 3 of up, and that's an extra challenge. Never even mind vulkan.
It seems to be quite a challenge to create a fully accelerated desktop stack on Linux, from kernel drivers, to userspaces drivers, to toolkits, to window managers, to end user apps, to video players actually using the VPU, etc, etc.
To be honest, I am amazed it works somewhere, with all the different standards, components, packages, libraries, etc. Let alone on devices like these!
Not a whole lot of people are anxiously awaiting an LXQT or Enlightenment distro/image/desktop, I imagine.Sav wrote: ↑Mon Jan 13, 2020 9:44 pmI think lxqt could be a better solution, but I don't know if there is a Wayland support.
Right now the lightest desktop with Wayland could be enlightenment, but I'm unable to built it from the git repository.
As for Manjaro, it would be interesting to have aur repository for Wayland support with Mali blobs.
Not sure if LXQT doesn't use KWin though... If kwin wayland doesn't work on KDE, then probably doesn't go with LXQT.
Put it this way; I've run Plasma on a RPi3b and my older laptop (that was 75% the speed of the slightly less older laptop I'm now using), and the framerate with those was too low for it to be comfortable. On the N2, even with CPU, I can click-drag windows around quickly and works well enough that I don't get frustrated by it (not that I've yet pushed it with browser, office, drawing and media open at the same time)
Haha, thanks, I'm mildly dyslexic, not sure what I was thinking about when I swapped mmc for mcc typing that post!Also, is the block device node name is mccblk*, not mmcblk*?
Sav wrote: ↑Mon Jan 13, 2020 9:44 pmtobetter wrote:Thanks for the info, I am working on Qt5 with Bifrost-Wayland driver and having some progress but KDE has no luck with me yet. Still, I am testing more features of Qt5 since some examples give an error. I am looking forward to seeing KDE eye candies on ODROID-N2.odroidn2user wrote: ↑Mon Jan 13, 2020 7:51 pmThey use llvmpipe / fbdev / fbturbo for the user space driver and keep hardware acceleration off by default.
Even on devices like the rockpro64, the panfrost userspace driver isn't enabled by default.
You can enable hardware acceleration, but they have an howto for that, and that's not for bifrost devices.
https://forum.manjaro.org/t/how-to-enab ... ces/114885
They were considering making hardware acceleration the default, but up until recently (when last I checked a couple of weeks ago) they opted to go for stability over hardware acceleration.
https://forum.manjaro.org/t/status-of-o ... ima/113591
And with regards to KDE plasma being laggy, they have QT packages compiled specifically for opengl es 2, so I wouldn't expect that to be slower.
But then you have software that requires full OpenGL 2, 3 of up, and that's an extra challenge. Never even mind vulkan.
It seems to be quite a challenge to create a fully accelerated desktop stack on Linux, from kernel drivers, to userspaces drivers, to toolkits, to window managers, to end user apps, to video players actually using the VPU, etc, etc.
To be honest, I am amazed it works somewhere, with all the different standards, components, packages, libraries, etc. Let alone on devices like these!
I think lxqt could be a better solution, but I don't know if there is a Wayland support.
Right now the lightest desktop with Wayland could be enlightenment, but I'm unable to built it from the git repository.
As for Manjaro, it would be interesting to have aur repository for Wayland support with Mali blobs.
Inviato dal mio iPad utilizzando Tapatalk
Well, most likely because Panfrost doesn't support the G52 GPU used on the Odroid N2 yet.m8kbv wrote: ↑Tue Jan 14, 2020 7:11 pmHi. I have Monjaro 19.08 XFCE.
I used the instructions:
https://forum.manjaro.org/t/how-to-enab ... ces/114885. After doing the following: sudo pacman -S mesa-git qt5-es2-base qt5-es2-declarative qt5-es2-multimedia is ok. After removing the FB Turbo driver by the command: sudo pacman -R xf86-video-fbturbo-git, when I reboot - the system displays a black background, only reset via ctrl + alt + del. The system does not start. Why? Without removing FB turbo driver the system starts up correctly.
I will test today.tobetter wrote: ↑Tue Jan 14, 2020 8:35 pmThis is not about Manjaro, but I would like to share what I've made to run GNOME Desktop with Mali Bifrost Wayland driver as well as Qt5/Wayland and written it up.
https://medium.com/@tobetter/running-gn ... a187dff055
What version of Mali is that? Is it related to the binary blob from ARM? I'd like to use it in Manjaro
The blob from Amlogic licensed by ARM and it is already uploaded to Github.
No, it just replaces the libraries installed by *mesa* packages like this.
Code: Select all
lrwxrwxrwx 1 root root 10 Jan 13 2020 /usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0 -> libmali.so
lrwxrwxrwx 1 root root 10 Jan 13 2020 /usr/lib/aarch64-linux-gnu/libGLESv1_CM.so.1 -> libmali.so
lrwxrwxrwx 1 root root 10 Jan 13 2020 /usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0 -> libmali.so
-rw-r--r-- 1 root root 18357592 Jan 13 2020 /usr/lib/aarch64-linux-gnu/libmali.so
lrwxrwxrwx 1 root root 23 Nov 8 20:10 /usr/lib/aarch64-linux-gnu/libmali.so.0 -> libwayland-egl.so.1.0.0
lrwxrwxrwx 1 root root 10 Jan 13 2020 /usr/lib/aarch64-linux-gnu/libwayland-egl.so.1.0.0 -> libmali.so
I have zero understanding of the ARCH package but have small about Debian. For the conflicting package due to libraries, what I use is Provides and Replaces such that keep the original package as installed but replace some file in the package with mine without conflict. This way made me build the package mali-bifrost-wayland-driver a bunch of times whenever conflict happens with other packages but reduce the number of packages that I have to build. I already more than 20 projects to build and package in order to put into Netboot Installer and GNOME desktop.mxmilkb wrote: ↑Wed Jan 15, 2020 4:10 amTrying to figure this out to make a binary package for the AUR
On Arch/Manjaro:
/usr/lib/libEGL_mesa.so is owned by mesa-git 20.0.0_devel.118876.645b1953-1
/usr/lib/libwayland-egl.so is owned by wayland 1.17.0-1
So I guess I need to make two packages, mesa-git-mali and wayland-mali
Code: Select all
root@disco:~# kwin_wayland --xwayland --socket nested
kwin_wayland: relocation error: /lib/aarch64-linux-gnu/libQt5Quick.so.5: symbol _ZN20QOpenGLFunctions_1_014versionProfileEv version Qt_5 not defined in file libQt5Gui.so.5 with link time reference
I think I found the reason why the missing symbol problem happens and I have to rebuild Qt5 again and play with it for sure. The problem is also can be solved by building QtQuick library with my current Qt5 but I'd like to avoid this since it causes one build job I have to manage. Let me do build Qt5 in this weekend.tobetter wrote: ↑Wed Jan 15, 2020 4:24 ammxmilkb wrote: ↑Wed Jan 15, 2020 4:10 amTrying to figure this out to make a binary package for the AUR
On Arch/Manjaro:
/usr/lib/libEGL_mesa.so is owned by mesa-git 20.0.0_devel.118876.645b1953-1
/usr/lib/libwayland-egl.so is owned by wayland 1.17.0-1
So I guess I need to make two packages, mesa-git-mali and wayland-maliCode: Select all
root@disco:~# kwin_wayland --xwayland --socket nested kwin_wayland: relocation error: /lib/aarch64-linux-gnu/libQt5Quick.so.5: symbol _ZN20QOpenGLFunctions_1_014versionProfileEv version Qt_5 not defined in file libQt5Gui.so.5 with link time reference
OK, how do you guys get this to work?tobetter wrote: ↑Wed Jan 15, 2020 10:12 pmI think I found the reason why the missing symbol problem happens and I have to rebuild Qt5 again and play with it for sure. The problem is also can be solved by building QtQuick library with my current Qt5 but I'd like to avoid this since it causes one build job I have to manage. Let me do build Qt5 in this weekend.
By the way, I've seen the face of KDE today with local build QtQuick but it does not look pretty for now and login is not allowed. I suspect that current KDE in Dicso only works on X11, not native Wayland...![]()
Are you going to kill Manjaro installled on eMMC?odroidn2user wrote: ↑Wed Jan 15, 2020 10:27 pmOK, how do you guys get this to work?tobetter wrote: ↑Wed Jan 15, 2020 10:12 pmI think I found the reason why the missing symbol problem happens and I have to rebuild Qt5 again and play with it for sure. The problem is also can be solved by building QtQuick library with my current Qt5 but I'd like to avoid this since it causes one build job I have to manage. Let me do build Qt5 in this weekend.
By the way, I've seen the face of KDE today with local build QtQuick but it does not look pretty for now and login is not allowed. I suspect that current KDE in Dicso only works on X11, not native Wayland...![]()
I have an installation of MAnjaro 19.08 on the EMMC and flashed the N2 disco installer from:
http://ppa.linuxfactory.or.kr/installer/ODROID-N2/
to a micro SD card known to work.
I used dd to 'burn' the image. Then checked the image and see the preseed.ini with its contents and everything.
So, it looks ok.
I put then the micro SD card into the sd slot of the Odroid N2 and boot up.
Nothing, it just boots Manjaro. I've set the spi-switch to MMC.
Now, petitboot doesn't work with any of my hardware, so that's a no go for me.
I've tried the buster net installer from the above url, using another SD card, and there the screen just stays black.
The blue blinking light goes off though, so I imagine behind the scenes it is booting MAnjaro 19.08 as well.
I've removed the eMMC and checked the SD. It then actually loads the SD with the netinst.
Haha.
OK, so the installation completed, had to remove the SD in a timely fashion to prevent installing it for a third time
That's interesting...why LGTV does not work? You mean after Petitboot.odroidn2user wrote: ↑Thu Jan 16, 2020 1:14 amOK, so the installation completed, had to remove the SD in a timely fashion to prevent installing it for a third time
But then, it doesn't boot. The blue light never comes on, it only shows the red led.
I suspect it needs petitboot to boot?
Well, petitboot loads and shows an image on the emmc (NOLABEL) to boot.
I select it, but then, nothing seems to happen, screen stays black.
And we're probably back to petitboot not actually working.
update: OK, interesting results.
The installed system requires Petitboot. It can't boot unless it is booted by Petitboot.
Petitboot doesn't work with my LG FullHD 23" TV Monitor, so after selecting the image to boot, it loads the OS, but just only ever shows a black screen.
That's interesting. If my understanding is correct 1400x1050 is supported with Ubuntu Disco installed today which has v5.4 kernel not v4.9.However, now my Samsung 20" 1400x1050 monitor *is* supported!
On Hardkernels kernel 4.9 and according to the official Odroid wiki, it shouldn't be supported, but now it actually works.
Interesting plot twists.
Yeah, 4.9 on 1400x1050 is a no go. But with 5.4 it actually works perfectly fine. Petitboot is squished to fit, but the normal desktop is 1400x1050 looking good.
Well, Petitboot itself works (a november dev version).tobetter wrote: ↑Thu Jan 16, 2020 1:57 amThat's interesting...why LGTV does not work? You mean after Petitboot.
Then you may need to install U-boot manually, download the U-boot tarball and use the scrip in it. sd_fusing.sh /dev/mmcblk0 from ODROID-N2 or sd_fusing.sh /dev/block/<your/usb/card/reader> from PC will install U-boot to your eMMC.
https://github.com/hardkernel/u-boot/re ... droidn2-64
My understanding was (and I could well be wrong) that the most important component to support Wayland was the compositor / window manager.
but the wiki article says "It is supported on some desktop environments like GNOME and KDE." with further KDE mentions later in the page.
Wow! Good work mxmilkb!mxmilkb wrote: ↑Thu Jan 16, 2020 9:00 pmboom - https://osdn.net/projects/manjaro-arm/s ... imal/20.01 - I'm still downloading.
<dodgejcr[m]> only made a minimal but there is a chance the ON2 will see more images soon. I did test that image flashed using etcher on an eMMC. Worked like a charm
Yeah, youtube video's seems to suggest it both exists and works, though there are open issues remaining. So even if KDE does Wayland, would you want to use it?
Users browsing this forum: No registered users and 2 guests