почему wayland?
с ним нормально работает графика, и плюс он лучше поддерживается в основном ядре
Playing around a little more. I noticed that the monitor refresh rate only had one option, 30mhz and I was unable to connect to to either the Kodi or Libreelec repositories to install addons. I just get a timeout error.
Here are screenshots showing that the network turnips are working on the supported models (the installation is going well) and the frequency is available at 60 Hz.
My motherboard won't boot with this image.
It's not sending a signal to the monitor. Is there a graphics issue?
What does Wayland mean?
I managed to get connection to the repositories. During the initial set-uo, only my local network was auto configured for ethernet.
I had to add the default gateway manually, which opened up access to the internet.
I still can't get past the 30mhz refresh rate but the Orange Pi 5 is not officially supported, so it is entirely reasonable that some functionality might not be there.
The vertical USB 2.0 port is not supported but then it is also problematic on most Linux distros.
Likewise, the USB-C data port is not detected, which is also the case with one or two other distros and full mainline support is, as I believe things, still to come.
Having some fun testing it though and it is worth other Orange Pi 5 users trying it.
Use the LibreELEC-ARMv8.aarch64-13.0-devel-20250607193042-e5590fa-rk3588-roc-pc.img image and change the config file to reflect use of the correct DTB image.
balbes150 is building the image with the Wayland windowing environment, and this restricts you to a single refresh rate because Wayland does not support dynamic refresh rate changes. This is why LE does not use Wayland in official images (only GBM, and Xorg for nVidia). The LE build system supports Wayland because it's used with the Lakka retrogaming fork.
balbes150 is building the image with the Wayland windowing environment, and this restricts you to a single refresh rate because Wayland does not support dynamic refresh rate changes. This is why LE does not use Wayland in official images (only GBM, and Xorg for nVidia). The LE build system supports Wayland because it's used with the Lakka retrogaming fork.
That does explain what is happening then.
Researching this more seems to suggest that right now, manual adjustments using tools such as wlr-randr, which I am not familiar with can sometimes be required.
I dare say that as Wayland development matures, solutions will be created.
I dare say that as Wayland development matures, solutions will be created.
The issue is known about in the Wayland ecosystem for many years already so I woulnd't hold breath or hope of a solution. NB: It's generally not an issue as Kodi GBM works well, although on new hardware where the DRM layer is still maturing there might be some glitches to resolve.
The issue is known about in the Wayland ecosystem for many years already so I woulnd't hold breath or hope of a solution. NB: It's generally not an issue as Kodi GBM works well, although on new hardware where the DRM layer is still maturing there might be some glitches to resolve.
Yes, further research does indeed stop me from holding my breath.
I did manage to get Kodi GBM working on one or two Linux distros a few months back and for the most part, Kodi could run rather well overall.
Steps forward in one way or another I guess.
My motherboard won't boot with this image.
It's not sending a signal to the monitor. Is there a graphics issue?What does Wayland mean?
is building the image with the Wayland windowing environment, and this restricts you to a single refresh rate because Wayland does not support dynamic refresh rate changes. This is why LE does not use Wayland in official images (only GBM, and Xorg for nVidia). The LE build system supports Wayland because it's used with the Lakka retrogaming fork.
If wyland hadn't been able to do this, no one would have started translating all modern distributions to wyland with gnome and kde. I admit that there are no such tools in LE yet (perhaps they just weren't needed yet).
I launched armbian with a 6.15 core on Rock 5b with gnome and wyland - in the settings I can change the screen frequency (60 59.5 50 etc) and any resolution formats. And this is taking into account that there is not all support for 3588 yet.
Alpha version 20250610-wayland . This is a universal version for all supported devices RK3399 RK356X RK3588 RK3576. SW decoding works on all devices by default. To enable HW decoding (including on 3588), need to enable drm_prem_hw in the settings (see the screenshots for details on how to do this). But on 3588, when HW decoding is turned on, there is a bug - on 4K video it does not work and the video freezes, all videos =< 1920 x 1080 work with HW decoding without any problems.
My motherboard
Did you not specify the exact model of the equipment, did not provide logs, and do you want someone to respond to you? There are no psychics here to guess what's not working for you.
Did you not specify the exact model of the equipment, did not provide logs, and do you want someone to respond to you? There are no psychics here to guess what's not working for you.
Sorry, but I don't speak English and I have to use a translator.
I also don't know anything about viewing logs because the topic is beyond me. I'll just post the exact model of my computer with all its components and pictures where you can see them.
I finally managed to get it to boot with this new version, Wayland, using the DTB from the second version, although mine is from the first.
With this version, hardware acceleration DOES work and it runs much better. What still doesn't work is Wi-Fi, Ethernet, and Bluetooth.
How can I see the log where the errors are specified, what command should I use?
