robertoj

Your gpios lines are declaring reset="i6" and dc="h4"... is that correct? At this point, we can see that all pins are correctly defined and connected. Maybe wire length issue? Bad terminal connection? My wires are 15cm long... directly connected with dupont connectors.

Boot while looking at the serial output, what do you see?

Self compiled Armbian Bookworm + XFCE with Linux Edge 6.15.x Then follow all the instructions in https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/#findComment-176981 Then add extraargs=cma=256M to armbianEnv.txt

If it doesn't work, compile your own Armbian with EDGE linux (what worked for me). Stay away from Trixie at this time (its mpv doesn't work as well as Bookworm's)

THANK YOU

I get this warning because I removed lightdm-gtk-greeter.desktop... what should I do to not expect the file? roberto@orangepizero3:~$ update-alternatives --display lightdm-greeter update-alternatives: warning: alternative /usr/share/xgreeters/lightdm-gtk-greeter.desktop (part of link group lightdm-greeter) doesn't exist; removing from list of alternatives lightdm-greeter - auto mode link best version is /usr/local/share/xgreeters/pi-greeter.desktop link currently points to /usr/local/share/xgreeters/pi-greeter.desktop link lightdm-greeter is /usr/share/xgreeters/lightdm-greeter.desktop /usr/local/share/xgreeters/pi-greeter.desktop - priority 70 After some research of greeters, I see that the default greeter is compatible with wayland https://github.com/Xubuntu/lightdm-gtk-greeter I have been working as if lightdm requires X11 (which I need to avoid), and so I wanted to used pi-greeter Does anybody have lightdm+gtkgreeter in a pure wayland setup? No X11

What is the difference between --hwdec=v4l2request and --hwdec=drm ? And drmprime, drmprime_overlay, and auto? Is the v4l2request absent from Trixie's mpv, due to a pre-compile configuration, or was it removed from the mpv source code?

Are you using the same GPIO wiring as I am? Previously, I was using different GPIO for the chip select, and touch wasn't working... now with my current GPIO in my DTS, it works perfectly.

Hello, I am trying to have a graphical login screen for my orange pi zero 3 with ili9488 LCD screen. A problem I have is that X11 can't start with the LCD driver... so I need to stay 100% wayland. I was able to compile and run labwc with these instructions: https://forum.armbian.com/topic/53797-labwc-wayland-crashes-on-exit/#findComment-223267 Labwc runs well on a HDMI screen and in the small ili9488 screen Next, I found this graphical login, which is made to install on top of lightdm: https://github.com/raspberrypi-ui/pi-greeter/tree/master Compilation rerequisites: sudo apt install gobject-introspection libgtk-3-dev liblightdm-gobject-dev libgtk-layer-shell-dev Lightdm requirement: sudo apt install accountsservice Compile it: $ autogen.sh $ ./configure $ make $ sudo make install There are some hints to post-install in the debian package postint: $ update-alternatives --install /usr/share/xgreeters/lightdm-greeter.desktop lightdm-greeter /usr/share/xgreeters/pi-greeter.desktop 70 In lightdm.conf: greeter-session=pi-greeter I check the lightdm configuration: $ update-alternatives --display lightdm-greeter lightdm-greeter - auto mode link best version is /usr/local/share/xgreeters/pi-greeter.desktop link currently points to /usr/local/share/xgreeters/pi-greeter.desktop link lightdm-greeter is /usr/share/xgreeters/lightdm-greeter.desktop /usr/local/share/xgreeters/pi-greeter.desktop - priority 70 /usr/share/xgreeters/lightdm-gtk-greeter.desktop - priority 60 Then I erase the link to lightdm-gtk: sudo rm /usr/share/xgreeters/lightdm-gtk-greeter.desktop When I try to start lightdm with sudo systemctl start lightdm, fails with: Job for lightdm.service failed because the control process exited with error code. In journalctl logs, $ journalctl -xeu lightdm.service I see Aug 09 09:18:19 orangepizero3 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ An ExecStart= process belonging to unit lightdm.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Aug 09 09:18:19 orangepizero3 systemd[1]: lightdm.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit lightdm.service has entered the 'failed' state with result 'exit-code'. Aug 09 09:18:19 orangepizero3 systemd[1]: Failed to start lightdm.service - Light Display Manager. ░░ Subject: A start job for unit lightdm.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit lightdm.service has finished with a failure. ░░ ░░ The job identifier is 6519 and the job result is failed. Does anybody have experience in installing pi-greet, or another greeter that would work in wayland? I need it to be efficient THANK YOU!

Share your DTS, maybe you missed something Run: dmesg | grep -E 'spi|panel' and post the result I already saw the online store... it is the same LCD that I use (I have both 3.5" and 4.0" and they work with the same DTS and bin file)

Make sure to power the VCC and LED with 3.3v, not 5v

Hmmm ok Now I am out of ideas. Are you using a downloaded armbian image? I have been using only self-compiled armbian images... (I need features of the latest linux-edge) It also prevents some problems if you uninstall or disable plymouth (interferes with loading the firmware file).

Uninstall the debian v4l2loopback package Did you add the build parameter to build for your specific kernel version? Did you do the final "make install" step? https://github.com/v4l2loopback/v4l2loopback?tab=readme-ov-file#build-for-a-different-kernel Search in the raspberry pi forum also

The online store link doesnt work Did you try lowering the SPI frequency? Are you using the panel-mipi-dbi-spi driver? I have no idea about the timing parameters in the firmware bin file. Are you familiar with notro's python script that turns a txt into a firmware bin file? There's a chance that your LCD is bad. Try buying an extra LCD. Future note for when you succeed with the driver: X11 will not work. There's a driver issue. If you can compile MESA3D you might get the needed updated driver. I have been using wayland+labwc... and I am currently in the effort to add a wayland greeter for the display manager (lightdm or greetd). (search my threads)

post the link of the online store where you bought your LCD. Why do you describe your problem as "offset", if your problem is a big rectangle that covers 25% of your screen?

Try a lower SPI frequency and use direct wires from the orange pi zero 2w to the LCD There might be something in the panel-mipi-dbi-spi.bin firmware to improve the display of the received bytes, but first do these two improvements (first try the direct wires) Opiz2w cases: https://forum.armbian.com/topic/52880-orangepi-zero-2w-wrong-color-display-on-mpi3501/ https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/page/2/ https://forum.armbian.com/topic/46824-orange-pi-zero-3-ili9486-tft-lcd/

Does this package exist? (sorry I am away from my armbian device) https://packages.debian.org/bookworm/v4l2loopback-dkms

My DTS is for the Orange Pi Zero 3. There's another thread that shows the correct GPIO wiring and DTS GPIO definitions for Orange Pi Zero 2w.

It probably means that you are close to having it work. 75% of the effort (or good luck) results in the LCD displaying noise or bad image. What model LCD? Photos? Confirm the wiring matches the default SPI terminals and the custom GPIO I included in the DTS. Are you connecting the touch chip terminals? LInux and armbian version? Downloaded or self compiled? Run the tests I have shown in several of my LCD threads: ili9341, ili9488.

Thank you... I will try with trixie again some time

Thank you but my use case is orange pi zero 3 and orange pi zero 2w… they are 64 bit H618

I got hardware acceleration working in wayland+labwc, in Bookworm, Linux 6.15.4, self built armbian With a self-compiled labwc (instructions: https://forum.armbian.com/topic/53797-labwc-wayland-crashes-on-exit/#findComment-223267 ) And the ffmpeg instructions in the original post were used with no changes... plus the extraargs=cma=256M in armbianEnv.txt Side question: can anybody make hardware acceleration work in Trixie?

Yes. Correct. Start with an armbian minimal or xcfe image that you build, with linux edge. Then install all the compilation dependencies mentioned in https://github.com/labwc/labwc/wiki and https://github.com/swaywm/sway/wiki/Debian-10-(Buster)-Installation#install-wlroots Some are mentioned as indicated for raspberry, but I installed them as well Do not install the debian bookworm libwlroots10 !! (this old wlroots interferes with the wlroots that will be installed now) Do not install libelogind-dev (it tried to modify my initramfs, it messed up the boot process, I didnt actually need it) You need a meson compiler more recent than bookworm provides. Install the backports repo: https://backports.debian.org/Instructions/ $ sudo apt install meson/bookworm-backports $ meson -v 1.7.0 Getting the labwc source code, and building: $ sudo apt install foot seatd (a minimal xterm for wayland, and a "seat manager" (may not be needed)) $ git clone https://github.com/labwc/labwc $ cd labwc $ meson setup build <-check that you have at least the GLES2 or EGL renderer If not, check that you have these dependencies: libegl-dev, libegl1-mesa-dev, libgles2-mesa-dev, libgles-dev If xwayland is desired, install xwayland from the bookworm repo After installing extra dependencies, run reconfiguration: $ meson setup --reconfigure build You will notice that the labwc build process auto-downloads and compiles a recent wlroots Finally compile (it took less than 5 minutes in my orange pi zero 3) $ meson compile -C build If it finishes compiling, check that the produced labwc works with: $ ./build/labwc -s foot If there's an error about memory allocation, add to armbianEnv.txt "extraargs=cma=256M", then reboot To install globally: $ sudo meson install -C build Test by exiting the labwc folder: cd ~ $ labwc -s foot Tomorrow, I will continue installing a display manager and greeter that works with wayland... since I am trying to avoid X11, due to my SPI LCD driver But all of you who try getting labwc in bookworm, hopefully the meson install command does something that lets lightdm see it is available as an option (I started with a minimal image)

I didn't try to replicate the problem in x86... but I compiled the latest labwc 0.9.0, in Orange Pi Zero 3 with Bookworm, and this problem does not show up

Thank you for the information I have completed the build dependencies step, for mesa 25.2, in Debian Trixie. However, when I build it, my orange pi zero 3 with 1 GB or RAM, it runs out of memory... even when I make a swap file of 2GB. I keep rebooting the opiz3, and continue the compilation job. Is this normal? In the raspberry forum, they told me that my LCD driver panel-mipi-dbi.ko doesn't work with X11... so I give up on this, and continue my development with labwc/wayland (easily installed in Trixie)