robertoj

I got my issue resolved with labwc+greetd+nwg-hello
 
See this link https://github.com/nwg-piotr/nwg-hello/issues/43
 
Please check it and post any corrections if needed
 
Getting rpi-greeter (no python) and wf-panel-pi (combines panel and launcher in compact form) would be ideal, but not resolved yet.
 
If anyone is interested in getting rpi-greeter working, this is my partial progress, and I still cannot make it start under lightdm, without any X11:
 
sudo apt install lightdm accountsservice polkitd
sudo apt install libgtk-layer-shell-dev librsvg2-common
sudo apt install gnome-common gobject-introspection gir1.2-gtk-3.0
 
These might be needed. I installed them the day after I installed greetd and ngw-hello. Note: I am working from a minimal debian trixie image
appmenu-gtk-module-common libaccountsservice-dev gir1.2-accountsservice-1.0 liblightdm-gobject-dev liblightdm-gobject-1-0 libgtk-3-dev gnome-common nasm
 
~$ mkdir rpi-greeter ; cd rpi-greeter
wget https://github.com/raspberrypi-ui/pi-greeter/archive/refs/heads/master.zip
unzip master.zip ; cd rpi-greeter-master
autogen.sh
./configure
make
sudo make install
 
Change /etc/lightdm/lightdm.conf with:
greeter-session=pi-greeter-labwc
 
Test with:
$ sudo lightdm --test-mode --debug
or
$ sudo systemctl start lightdm
$ journalctl -b -u lightdm.service
The error is:
 
Oct 13 22:01:49 orangepizero3 lightdm[845]: Error updating user /org/freedesktop/Accounts/User1000: GDBus.Error:org.freedesktop.Accounts.Error.PermissionDenied: Not authorized: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PolicyKit1 was not provided by any .service files
 
DEBUG: Could not run plymouth --ping: Failed to execute child process ?plymouth? (No such file or directory)
 
I think I am very close to getting rpi-greeter working. What could be missing?
 
I see that in a raspberry pi, the folder /etc/xdg/labwc-greeter/ exists, with 3 files inside, but in armbian, it doesn't exist. Should it be created by sudo make install?
 
sudo nano /var/log/lightdm/lightdm.log:
Nothing weird. Only:
[+0.07s] DEBUG: Session pid=6392: Running command /usr/bin/labwc -C /etc/xdg/labwc-greeter/ (and this folder /etc/xdg/labwc-greeter/ does not exist)
In raspberry: /etc/xdg/labwc-greeter/ contains autostart, rc.xml and environment
 
sudo nano /var/log/lightdm/seat0-greeter.log:
** (process:6392): WARNING **: 00:23:07.745: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.E>
00:00:00.000 [ERROR] [../src/main.c:202] XDG_RUNTIME_DIR is unset
 
The etc/xdg/labwc-greeter/autostart, etc files come from a package named raspberrypi-ui-mods
(raspberry$ dpkg -S /etc/xdg/labwc-greeter/autostart)
What part of https://github.com/raspberrypi-ui/raspberrypi-ui-mods would get my lightdm+labwc+rpigreeter working?
 
Copying the /etc/xdg/labwc-greeter/ folder with the 3 files, with the same permissions, allow the pi-greeter to display (it is very plain), but after entering the password, the text mode display shows for 2 seconds, then the labwc black background and cursor shows for 1/4 second, then returns to the login screen.
 
Found this error in the log:
/etc/xdg/labwc-greeter//autostart: 2: /usr/bin/kanshi: not found
 
Final part of solution:
lightdm should contain:
user-session=LXDE-pi-labwc
 
Create file /usr/share/wayland-sessions/ LXDE-pi-labwc.desktop:
[Desktop Entry] Type=Application Name=Labwc Desktop on Wayland Exec=/usr/bin/labwc  
rpi-greeter does not allow selection of other sessions: only labwc

https://forum.armbian.com/topic/46824-orange-pi-zero-3-ili9486-tft-lcd/
user wdr_s had success with that same lcd. Try it with linux 6.1 (check the success case)
If you have a file named orangeEnv.txt... you arent using armbian yet!
 
Make sure to use armbian-add-overlay
 
In the ili9341 or ili9488 there's someone trying with orange pi zero 2w, which is very close to zero 3

THANKS TO USER KungFuPancake, who showed me his github repo, where he indicates to use the latest Armbian-edge, and provides the a command byte sequence for the ili9488
 
https://github.com/KungfuPancake/v0_ips_touch_display?tab=readme-ov-file
 
If you see inverted colors, edit the panel-mipi-dbi-spi.txt and comment the line #command 0x21 before using the mipi-dbi-cmd
 
If you have the cheap chinese clone LCD (see first post), use this DTS (change the gpio codes as needed):
 
 
 
 
 
 

It would be better if you make a copy of the dtbo from the original folder and name, to the overlays-user folder, then use the user_overlays parameter in armbianEnv.txt to add it.
 
In general, a DTBO copied from one SBC to another, will only work if the Radxa Zero 3W and the Radxa Zero 3 share the same:
* CPU chip
* chip pinout to the wireless chip
* wireless chip
* nothing else extra or missing interfering with the chip-wifi channel
 
It is always better to have the DTS (source code of DTBO), so you have full awareness of what it does, and compile with armbian-add-overlay
 
You can try it, then if you don't like the result, disable the dtbo with the user_overlays parameter.  ... and report whether it works or not.
 
When the kernel is upgraded, you may get a better support of the chip (if the Radxa or wifi software engineers have done something toward it)
 
 
When you upgrade kernel, the same DTBO can be used to patch the SBC DTB... unless there's a change in kernel module parameters (rare).
 

For anyone interested in connecting the ili9341 to an orange pi zero, and use the adafruit DRM driver: ili9341-spi1-drm.dts
 
 
I made these experiments, since the LCD is the only one chip in the SPI bus.
* disconnect the LCD's Chip Select -> LCD remains white
* connect the LCD's Chip Select to GND -> LCD displays the login line and linux crashes soon after <- it might be my orange pi zero, which needs a heatsink
 
Update: this thread also refers to orange pi zero 3... the solution (with touch function) is in this post:
https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/#findComment-204672
 

In armbianenv.txt, erase the overlay “tve” (abbreviation of tv signal encoder)
 
if you don’t use any analog outputs, can the pins be used as GPIO?