Posts by thes3pt3mb3r

thes3pt3mb3r · Desktop and Multimedia

Sorry,It was my mistake becouse I have always used seatd like that and did not check 'dwl' by itself.

thes3pt3mb3r · Desktop and Multimedia

Yes,I know this much but the problem is that this message shows and compositor does not start.

thes3pt3mb3r · Desktop and Multimedia

Command 'ls -l' on /etc/seatd* showed that /run/seatd.sock is owned by root and video group. User is in video group,yet I still get 'Socket file found at socket path /run/seatd.sock, refusing to start' after running 'seatd-launch dwl'. That message is not really telling me much.

thes3pt3mb3r · Hardware & System Configuration

Comparison of part of dmesg of plugging Waveshare 7inch LCD HDMI (C) and MSI MAG 276CXF to the same device,ARM64 board.
https://privatebin.net/?6ea54c60a34f818 … STdn3hw1XN

EDIT:
I will find different screen

thes3pt3mb3r · Hardware & System Configuration

Could you please say who that may or where to go?

Well regardless EDID itself is fine,and size is the same from both devices('wc -c' outputs 128). I checked it from device that screen did work with, to make sure(some newer Dell laptop with Windows11).

EDIT:
Corrected EDID that was pasted incorrectly in one of my comments above
Results of "for d in /sys/class/drm/*; do echo "== $(basename $d)"; cat $d/status 2>/dev/null; cat $d/modes 2>/dev/null; done"
for Waveshare screen;
"== card0
== card0-HDMI-A-1
connected
== card1
== renderD128
== version"

For MSI(comparison);
"== card0
== card0-HDMI-A-1
connected
1920x1080
1920x1080
1920x1080
1680x1050
1280x1024
1280x1024
1280x720
1280x720
1024x768
== card1
== renderD128
== version"

thes3pt3mb3r · Hardware & System Configuration

Dmesg log of plugging HDMI(for displaying) and USB(for power),waiting just enough and plugging them out, this was produced with with me also adding 'drm.debug=0xe' to kernel commandline.
[ 770.782136] rockchip-drm display-subsystem: [drm:vop2_plane_atomic_update [rockchipdrm]] vp0 update Smart0-win0[1920x1080->1920x1080@0x0] fmt[XR24 little-endian (0x34325258)_] addr[0x0000000000000000] <--- This line in original log repeats many many many times and it makes log hard to read.

[ 981.428739] rockchip-drm display-subsystem: [drm:check_connector_changed] [CONNECTOR:53:HDMI-A-1] status updated from connected to disconnected
[ 981.428825] rockchip-drm display-subsystem: [drm:check_connector_changed] [CONNECTOR:53:HDMI-A-1] Changed epoch counter 4 => 5
[ 981.428886] rockchip-drm display-subsystem: [drm:drm_sysfs_connector_hotplug_event] [CONNECTOR:53:HDMI-A-1] generating connector hotplug event
[ 981.429073] rockchip-drm display-subsystem: [drm:drm_fb_helper_hotplug_event]
[ 981.429122] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe]
[ 981.429173] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:53:HDMI-A-1]
[ 981.429240] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:53:HDMI-A-1] disconnected
[ 981.429301] rockchip-drm display-subsystem: [drm:drm_edid_connector_update] [CONNECTOR:53:HDMI-A-1] EDID changed, epoch counter 6
[ 981.429373] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] No connectors reported connected with modes
[ 981.429416] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [CONNECTOR:53:HDMI-A-1] enabled? no
[ 981.429473] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] Not using firmware configuration
[ 981.429520] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] picking CRTCs for 1920x1080 config
[ 981.429706] rockchip-drm display-subsystem: [drm:vop2_plane_atomic_disable [rockchipdrm]] Smart0-win0 disable
[ 981.435763] rockchip-drm display-subsystem: [drm:drm_client_dev_hotplug] fbdev: ret=0
[ 988.267440] usb 6-1: new full-speed USB device number 2 using ohci-platform
[ 988.488629] usb 6-1: New USB device found, idVendor=0eef, idProduct=0005, bcdDevice= 1.11
[ 988.488671] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 988.488694] usb 6-1: Product: WS170120
[ 988.488710] usb 6-1: Manufacturer: WaveShare
[ 988.488728] usb 6-1: SerialNumber: 220211
[ 988.503856] input: WaveShare WS170120 Touchscreen as /devices/platform/fd840000.usb/usb6/6-1/6-1:1.0/0003:0EEF:0005.0003/input/input7
[ 988.504947] hid-generic 0003:0EEF:0005.0003: input,hiddev97,hidraw2: USB HID v1.11 Device [WaveShare WS170120] on usb-fd840000.usb-1/input0
[ 988.567520] input: WaveShare WS170120 as /devices/platform/fd840000.usb/usb6/6-1/6-1:1.0/0003:0EEF:0005.0003/input/input9
[ 988.568685] hid-multitouch 0003:0EEF:0005.0003: input,hiddev97,hidraw2: USB HID v1.11 Device [WaveShare WS170120] on usb-fd840000.usb-1/input0
[ 991.634368] rockchip-drm display-subsystem: [drm:check_connector_changed] [CONNECTOR:53:HDMI-A-1] status updated from disconnected to connected
[ 991.634468] rockchip-drm display-subsystem: [drm:check_connector_changed] [CONNECTOR:53:HDMI-A-1] Changed epoch counter 6 => 7
[ 991.634530] rockchip-drm display-subsystem: [drm:drm_sysfs_connector_hotplug_event] [CONNECTOR:53:HDMI-A-1] generating connector hotplug event
[ 991.634714] rockchip-drm display-subsystem: [drm:drm_fb_helper_hotplug_event]
[ 991.634765] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe]
[ 991.634820] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:53:HDMI-A-1]
[ 991.636333] rockchip-drm display-subsystem: [drm:drm_mode_prune_invalid] Rejected mode: "640x480": 60 25175 640 656 752 800 480 490 492 525 0x40 0xa (NOCLOCK)
[ 991.636429] rockchip-drm display-subsystem: [drm:drm_mode_prune_invalid] Rejected mode: "800x600": 56 36000 800 824 896 1024 600 601 603 625 0x40 0x5 (NOCLOCK)
[ 991.636490] rockchip-drm display-subsystem: [drm:drm_mode_prune_invalid] Rejected mode: "800x600": 60 40000 800 840 968 1056 600 601 605 628 0x40 0x5 (NOCLOCK)
[ 991.636549] rockchip-drm display-subsystem: [drm:drm_mode_prune_invalid] Rejected mode: "848x480": 60 33750 848 864 976 1088 480 486 494 517 0x40 0x5 (NOCLOCK)
[ 991.636606] rockchip-drm display-subsystem: [drm:drm_mode_prune_invalid] Rejected mode: "1024x768": 60 65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa (NOCLOCK)
[ 991.636664] rockchip-drm display-subsystem: [drm] User-defined mode not supported: "1024x600": 60 48924 1024 1064 1168 1312 600 601 604 622 0x20 0x6
[ 991.636707] rockchip-drm display-subsystem: [drm:drm_mode_prune_invalid] Rejected mode: "1024x600": 60 48924 1024 1064 1168 1312 600 601 604 622 0x20 0x6 (NOCLOCK)
[ 991.636767] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] No connectors reported connected with modes
[ 991.636812] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [CONNECTOR:53:HDMI-A-1] enabled? yes
[ 991.636873] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] Not using firmware configuration
[ 991.636921] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [CONNECTOR:53:HDMI-A-1] no mode found
[ 991.636966] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] picking CRTCs for 1920x1080 config
[ 991.637160] rockchip-drm display-subsystem: [drm:drm_client_dev_hotplug] fbdev: ret=0
[ 991.814004] rockchip-drm display-subsystem: [drm:check_connector_changed] [CONNECTOR:53:HDMI-A-1] Same epoch counter 7
[ 1023.840233] usb 6-1: USB disconnect, device number 2
[ 1031.163549] rockchip-drm display-subsystem: [drm:check_connector_changed] [CONNECTOR:53:HDMI-A-1] Same epoch counter 7

thes3pt3mb3r · Hardware & System Configuration

This is part of dmesg log when I connnected it,waited, then I disconnected it.
[ 121.206366] rockchip-drm display-subsystem: [drm] User-defined mode not supported: "1024x600": 60 48924 1024 1064 1168 1312 600 601 604 622 0x20 0x6
[ 131.023945] usb 3-1: new full-speed USB device number 3 using ohci-platform
[ 131.245001] usb 3-1: New USB device found, idVendor=0eef, idProduct=0005, bcdDevice= 1.11
[ 131.245036] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 131.245057] usb 3-1: Product: WS170120
[ 131.245074] usb 3-1: Manufacturer: WaveShare
[ 131.245091] usb 3-1: SerialNumber: 220211
[ 131.263396] input: WaveShare WS170120 as /devices/platform/fd840000.usb/usb3/3-1/3-1:1.0/0003:0EEF:0005.0004/input/input9
[ 131.264563] hid-multitouch 0003:0EEF:0005.0004: input,hiddev97,hidraw2: USB HID v1.11 Device [WaveShare WS170120] on usb-fd840000.usb-1/input0
[ 141.814785] usb 3-1: USB disconnect, device number 3
[ 149.842736] rockchip-drm display-subsystem: [drm] User-defined mode not supported: "1024x600": 60 48924 1024 1064 1168 1312 600 601 604 622 0x20 0x6

I also have result of "cat /sys/class/drm/card0-HDMI-A-1/edid > /root/edid.txt" which is:
ےےےےےےپ€
Eہ$ AX 0`:ڑV‡
I do not really see it fully since font that I use doesn't support these signs.

'hexdump -C edid.txt' is:
00000000 00 ff ff ff ff ff ff 00 04 81 04 00 01 00 00 00 |................|
00000010 01 11 01 03 80 0f 09 00 0a 00 00 00 00 00 00 00 |................|
00000020 00 00 00 00 00 00 45 c0 01 01 01 01 01 01 01 01 |......E.........|
00000030 01 01 01 01 01 01 24 13 00 20 41 58 18 20 30 60 |......$.. AX. 0`|
00000040 3a 00 9a 56 00 00 00 18 00 00 00 10 00 00 00 00 |:..V............|
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 10 00 00 |................|
00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10 |................|
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 87 |................|
00000080
Apparently it's corrupted here but I do not think that it is inherently corrupted since It worked with Laptop that had windows11.
I also have dmesg log that was captured when I added 'drm.debug=0xe.

thes3pt3mb3r · Hardware & System Configuration

No, what you wrote doesn't really do anything.

I had screen plugged before turning it on, but I do not see what the issue is?

if my more 'PC' monitor didn't pose any issues like that,they both used standard HDMI interface for displaying although waveshare device additionally uses usb for touch.

Also I feel that it is important to mention that OS I use is basically DietPi's Debian converted to Devuan so, there is no config.txt in /boot dir.

thes3pt3mb3r · Hardware & System Configuration

I have https://www.waveshare.com/wiki/7inch\_HDMI\_LCD_(C), version Rev4.1. When I connect it to my ARM board, nothing shows up (the screen only lights up slightly) even though the LED dot is blinking, indicating that Devuan is starting/running.

I possess an MSI monitor that also uses HDMI for display and it works, so I don’t understand what’s wrong with the former device.

One more thing mentioned in the instructions is setting the right resolution by pasting:
'hdmi_group=2
hdmi_mode=87
hdmi_cvt 1024 600 60 6 0 0 0
hdmi_drive=1' at the end of the config.txt file that is found on the TF card after flashing the Raspberry Pi image, but I do not know how to do this on Devuan because these instructions are only focused on Raspberry Pi OS.

I asked Waveshare about this and they said that the Linux kernel itself should support it. They did not help me much.

I do not know if there is any problem with the touch part of this device yet.

thes3pt3mb3r · Installation

I think the problem could be the .config file that the bootloader was compiled with,options that are required for luks support could be unchecked. I will mark this as solved if I compile,flash bootloader and it boots.

EDIT: failure;

I compiled TF-A from https://github.com/TrustedFirmware-A/trusted-firmware-a for BL31 and got ROCKCHIP_TPL from https://github.com/rockchip-linux/rkbin.

I compiled them and got a sort of warning-alike that OP-TEE is missing but I am not sure how to deal with it.

I have tried to compile it (I am not cross-compiling here) but I got error that I do not have GCC ARMHF compiler.

Nevertheless, the message after compilation that I wrote about sentence ago did also say that basic functionality still is there so I assumed it will boot at least something.

DietPi images have tools have option to flash boot loader to SPI, It uses files from https://dietpi.com/apt/dists/all/orange … ietpi1.deb for that operation.

I moved those files from their original place somewhere else and copied ones I compiled with same name in their place.

I tried to flash it with that tool(not its fault since flashes from (*deb file mentioned above) files from have never failed), result is corrupted boot loader. Although this is not my first time.

So what I with to ask now as it is related to this process, how to update U-Boot boot loader correctly, preferably with 'dd'? This topic confuses me, I am not very well-versed in it.

thes3pt3mb3r · Installation

One of the packages that I meant is https://dietpi.com/apt/dists/all/orange … ietpi1.deb (more *.deb files with similar names at the bottom of https://dietpi.com/apt/dists/all/orange … ary-arm64/ ).

I have changed the boot partition's filesystem to ext4 (I am not sure how clear I am coming across, but just to be sure: [MMC] mmcblk0 --> mmcblk0p1 (ext4), mmcblk0p2 (LUKS) with f2fs type underneath).

I do not possess a serial cable at the moment, but I also own an SD card on which I have flashed and succeeded with https://dietpi.com/downloads/images/Die … xie.img.xz and https://github.com/manjaro-arm/opi-3b-images/releases .

Both make the system ext4-based, and it always makes them 'vanilla' without any things like ZFS, LUKS, etc. (that means that there is only one partition that is both boot and root, marked as bootable).

The Manjaro image had only extlinux.conf as its boot option, and the DietPi image had only boot.scr as its boot method. I prefer extlinux; it seems simpler.

Is there anything else I could do?
EDIT:I also see option of doing U-Boot over UEFI...It would make things easier probably(?)

It would be helpfull to get recipe for https://dietpi.com/apt/dists/all/orange … ietpi1.deb , there is also Armbian mirror with this mirror.sjtu.edu.cn/armbian/pool/main/l/linux-u-boot-orangepi3b-edge/

thes3pt3mb3r · Installation

I wanted Devuan to run on an SBC (I have an ARM64 SBC with an RK3566 RockChip SoC) which uses the U-Boot bootloader to boot with LUKS. There are two partitions: boot (ext3) marked as bootable, and cryptroot (LUKSv2).

What I did:

I used file from linux-u-boot-orangepi3b to update bootloader,factory one is from 2017.

I made a Devuan system with the help of debootstrap using the default variant, version ceres, and I added DietPi mirrors (because they have a kernel that fits my board). I installed cryptsetup, the kernel, Wi‑Fi-related packages, added firmware blobs to /lib/firmware, and compiled booster for the initramfs tool.

I wrote boot.cmd and compiled it to boot.scr, and also wrote extlinux.conf (because I had seen one of the Manjaro ARM images boot on my board; it didn't have the syslinux package but also no boot.scr).

The bootloader still doesn't recognize the partition; there was no blinking LED. Debian system from DietPi has no problem booting, I wish DietPi images had a LUKS option.

I also tried converting the fully LUKSv2 partition to LUKSv1 to see if this was a problem, since the first article I saw was https://u-boot.org/blog/unlocking-disks … rint=print ; but I later found https://u-boot.org/blog/unlocking-moder … 2-support/ when digging through their blog, so this was not a problem by itself.

The officially official Devuan Forum!

#1 Re: Desktop and Multimedia » [SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start » 2026-05-20 14:30:59

#2 Re: Desktop and Multimedia » [SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start » 2026-05-20 07:06:24

#3 Desktop and Multimedia » [SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start » 2026-05-19 20:21:14

#4 Re: Hardware & System Configuration » [SOLVED] HDMI touchscreen display doesn't really display » 2026-05-10 11:01:11

#5 Re: Hardware & System Configuration » [SOLVED] HDMI touchscreen display doesn't really display » 2026-05-10 09:13:28

#6 Re: Hardware & System Configuration » [SOLVED] HDMI touchscreen display doesn't really display » 2026-05-09 20:10:02

#7 Re: Hardware & System Configuration » [SOLVED] HDMI touchscreen display doesn't really display » 2026-05-09 13:30:36

#8 Re: Hardware & System Configuration » [SOLVED] HDMI touchscreen display doesn't really display » 2026-05-08 20:32:39

#9 Hardware & System Configuration » [SOLVED] HDMI touchscreen display doesn't really display » 2026-05-08 13:00:21

#10 Re: Installation » [SOLVED] Struggle with making Devuan + LUKS setup boot on Orange Pi 3B v1.1 » 2026-04-16 08:53:03

#11 Re: Installation » [SOLVED] Struggle with making Devuan + LUKS setup boot on Orange Pi 3B v1.1 » 2026-04-13 19:17:27

#12 Installation » [SOLVED] Struggle with making Devuan + LUKS setup boot on Orange Pi 3B v1.1 » 2026-04-11 11:59:55

Board footer