robertoj
-
Posts
524 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by robertoj
-
-
If you already checked "dmesg|grep panel-mipi" and "dmesg|grep spi", check this:
* share which LCD you are using. Half of those LCDs are waveshare clones, which need a different driver. My DTS works in the RED LCDs.
* Look at the uboot messages in the serial port output. Does it confirm it is finding your dtbo and using it?
* verify that panel-mipi-dbi.ko exists in the modules folder. I know it is not preselected by default within the linux configuration menu
* Search the word "pinctrl" in this thread https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/#comment-204741
To confirm that the kernel driver is using the gpio and spi pins
* send link of the rock3c DTS you are referencing, to see an example of how GPIOs are configured
* correct the gpio pin map you shared. Instead of tx/rx, use MOSI, MISO. Highlight and label clearly the CS0, CS1, RESET, DC, IRQ
* explain how those gpio numbers gpioX,XX transform into the DTS gpioX XX 1/0
If you at least get noise in the LCD, you are 50% done
(and maybe you will get lucky in the last 50%)
-
Can you copy those dtbo's to /boot/user-overlays (maybe they will need renaming)
Then activate them in armbianEnv.txt?
-
Oh I get it. Since you are using another distro with newer versions of everything, my effort to build ffmpeg and mpv in Debian Trixie LOOKS like a backport to you XD
upon reading your comment again, I understand the consequences of upgrading ffmpeg from source (Debian Trixie's ffmpeg is version 7.1.2)
According to: https://forums.linuxmint.com/viewtopic.php?t=457495, I would need to check with "apt-rdepends -r ffmpeg"
-
6 minutes ago, usual user said:
Just out of curiosity, why are you trying to backport the v4l2request support?
Why not build the pull request tree directly:I thought this was the best way: official latest mpv + pull request
i am not trying to backport it. I want to make it work in trixie.
-
The ffmpeg discussion posted a way to test the code (at the bottom of https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20847 )
*install all the ffmpeg dependencies, then:
$ git fetch -u https://code.ffmpeg.org/Kwiboo/FFmpeg v4l2request-v3:Kwiboo-v4l2request-v3 $ git switch Kwiboo-v4l2request-v3* compile and install
Then rebuild mpv+PR14690 (https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/page/5/#findComment-226567)
-
9 hours ago, JFL said:
You managed to build mpv with v4l2request for Debian Trixie that has vpu hardware acceleration? Care to share?
No. I haven't tried anything new. My previous attempts compiling mpv in Trixie were unsuccessful.
I want to try it again by compiling and installing this new ffmpeg+v4l2 first, then trying compiling mpv again.
You should try it too
-
Thank you for sharing it
Can you include these specifications, for quick reference for future readers?
Board, Debian version, Kernel, Graphics (console, X11, wayland)
-
There's a new version of the kwiboo ffmpeg+v4l2request function
https://code.ffmpeg.org/Kwiboo/FFmpeg/src/branch/v4l2request-v3
And it was shown as a work in progress in the ffmpeg community
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20847
Then, it was noticed in the mpv community
https://github.com/mpv-player/mpv/pull/14690#issuecomment-3500141427
They previously said that v4l2request first needs to be integrated in ffmpeg officially, then mpv would start working on v4l2request
This is needed, to have mpv+v4l2request compiling successfully and working under Debian Trixie (my experience)
-
In bookworm, trixie or noble?
-
Can someone confirm that xwayland is working in the other wayland desktops in armbian?
I can't make it work in labwc
-
20 hours ago, Sári Zoltán said:
Paste your custom overlay configuration for SPI, DC, and reset GPIOs
Share your DTS. It is the most challenging part of this. We can customize, based on SBC model.
-
Start with this DTS and change the GPIO for your OPIZ3
https://github.com/raspberrypi/linux/blob/rpi-6.12.y/arch/arm/boot/dts/overlays/piscreen-overlay.dts
Or start with your DTS and change the "compatible" line to "compatible=waveshare,rpi-lcd-35" and copy the other parameters of piscreen-overlay.dts if needed
Let us know if it works
-
Getting video acceleration is realtively easy in bookworm, but making it work in Trixie would be newsworthy
-
It all depends on the GUI apps you want to run.
Web browser: at least 4GB
Your own Python GUI app: 1GB
16GB storage is fine.
"A more advanced build framework" only refers to the laptop you use to compile your own Armbian OS... it doesn't refer to the SBC where you will run it.
-
Yes, CONFIG_TINYDRM_ILI9486 is the kernel module for that model of LCD with DRM. There's another thread explaining how to use it.
I think you can use udev rules to force SPI LCD as /dev/fb0 and HDMI as /dev/fb1 always.
-
I noticed this problem a long time ago, but now I feel it is important to fix it:
I get a
slim black bar on the left side, and a portion of the pixels on the right get "cropped" because they don't fit in the LCD display area?I get the left 2 pixels of the screen "cropped", so in console, the first left-side are always missing the left pixels.
Do you get the same in your LCD? Do you know a way to fix it? I am talking about this LCD: RED PCB LCD https://www.aliexpress.us/item/3256802847521952.html?
-
In that case, dont try my solution: it is for the red ili9341.
If you search ili9486 threads in this forum, that same blue LCD is ili9486... so you were wrong in calling it ili9341 in the first place
If you have time, find another solution to get you a DRM frambuffer (instead of a classic FB). Then you can enjoy smoother animations and video.
Regarding displaying boot messages to the LCD, instead of HDMI. I don't know, but it may be because your HDMI is /dev/fb0 and the LCD is /dev/fb1
Will you use X11?
-
Try this solution for the orange pi zero LTS, which is the same chip as the opiPC, but change the pin definitions to what you have.
Do you have a 480x320 ili9341? Which one is it?
-
If anyone in interested in a lightweight wayland desktop, inspired by openbox, you should try labwc.
In orange pi zero 3, we need to stay in bookworm to get video acceleration, so this guide helps build labwc in bookworm
As a greeter, I chose pi-greeter, because it is the lightest login manager I could setup, without any X11
https://github.com/robertojguerra/opiz3-labwc-setup
I am open to read any improvements, or show me how I could make deb packages.
In the near future, I will make a step-by-step video tutorial in Youtube.
-
For video acceleration, you need to stick with Bookworm.
-
Has anybody tried compiling mpv-0.35 + PR14690 within Trixie and ffmpeg 7.x.x?
If anyone is curious... mpv-0.37 fails in the compilation step in ad-spdif.c due to an incompatible pointer
But mpv-0.38 (without patches) compiles successfully
-
Dont write that "fbi works correctly", when it is not.
The display remains white, and the kernel doesn't show any errors.
* Re-check your wiring
* Disconnect the touch part of the LCD pins
* Try reversing the polarity:
dc-gpios = <&pio 2 6 1>; << change the 1 to 0
reset-gpios = <&pio 2 9 1>; << change the 1 to 0If the CPU is successful sending the reset signal, the data/command, the chip select and any bytes through SPI, at least the LCD should turn black.
-
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 filesDEBUG: 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 unsetThe 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/labwcrpi-greeter does not allow selection of other sessions: only labwc
-
Thank you. I meant to ask about that PR14690
I would rather stay with trixie and low fps, because it seems easier to solve my other problem: need 100% wayland and 0% X11 due to a LCD driver problem.

Repository for v4l2request hardware video decoding (rockchip, allwinner)
in Reviews, Tutorials, Hardware hacks
Posted · Edited by robertoj
The first post reads "your mileage may vary" and "the latest kernel will work best"
Start by recompiling armbian for your Rockchip SBC, with the edge kernel option, then follow the ffmpeg install instructions
If it doesn't work, try the older Ubuntu, and both Debian options