this post was submitted on 15 Sep 2026
7 points (100.0% liked)

postmarketOS (moved to lemmy.world/c/nura ๐Ÿšš๐Ÿšš๐Ÿšš)

345 readers
1 users here now

Moved to: !nura@lemmy.world

founded 1 year ago
MODERATORS
JustSoup321@lemmy.world
ollieparanoid@lemmy.world
achill@lemmy.world
PureTryOut@lemmy.world
7
Moto G7 (Codename river), touchscreen not working (lemmy.blahaj.zone)
submitted 4 weeks ago* (last edited 4 weeks ago) by protogen420@lemmy.blahaj.zone to c/postmarketos@lemmy.world
3 comments fedilink hide all child comments
 

I have managed to get PMOS booting and even displaying the lockscreen and responding to power and volomue buttons and usb networking with ssh over it but the touch screen simply does not work, the wiki page on the device says that the touchscreen works

I have built an image with Phosh and systemd for it and flashed it, Phosh's lock screen loads, reacts to power button (turning on and off he display and holding for the power menu), reacts to volume down and up buttons (audio slider indicator appears), screen display auto dimms when inactive and eventually turns off, the only thing unexpected is the touchscreen not working at all

if there is any extra info needed feel free to ask

how do I trouble shoot this issue?

top 3 comments
sorted by: hot top controversial new old
[โ€“] INeedMana@piefed.zip 2 points 4 weeks ago (1 children)

I guess, same as on desktop. Do you have a device for it in xev/wev/xinput/swaymsg -t get_inputs/lsusb(?)/lspci/... is the device being set up sometime in journalctl -b0 (I guess you have systemd, right?) ?

When going deeper there probably are some other steps but initially think of it as if you booted a Linux on a laptop and its touchscreen didn't work. It might be the kernel in the end, but first go from the top down. Right now your WM does not get touchscreen events. So does your X/Wayland get the device? If not, get deeper. Yes, look around if it sends any events

[โ€“] protogen420@lemmy.blahaj.zone 0 points 3 weeks ago (1 children)

my system doesnt has xev/wev/xinput, I tried finding the packages for those but I couldn't, journalctl -b0 gave some interesting things

here are some snips of it that i think are relevant

[...]

Jun 21 13:36:16 fluffy kernel: /soc@0/clock-controller@1800000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/phy@1a94400
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/display-controller@1a01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/display-controller@1a01000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/phy@1a94400: Fixed dependency cycle(s) with /soc@0/clock-controller@1800000
Jun 21 13:36:16 fluffy kernel: /soc@0/camss@1b00020: Fixed dependency cycle(s) with /soc@0/cci@1b0c000/i2c-bus@0/s5k4h7yx@10
Jun 21 13:36:16 fluffy kernel: /soc@0/camss@1b00020: Fixed dependency cycle(s) with /soc@0/cci@1b0c000/i2c-bus@1/s5k5e9@2d
Jun 21 13:36:16 fluffy kernel: /soc@0/cci@1b0c000/i2c-bus@0/s5k4h7yx@10: Fixed dependency cycle(s) with /soc@0/camss@1b00020
Jun 21 13:36:16 fluffy kernel: /soc@0/cci@1b0c000/i2c-bus@1/s5k5e9@2d: Fixed dependency cycle(s) with /soc@0/camss@1b00020
Jun 21 13:36:16 fluffy kernel: /soc@0/spmi@200f000/pmic@2/typec@1500/connector: Fixed dependency cycle(s) with /soc@0/usb@7000000
Jun 21 13:36:16 fluffy kernel: /soc@0/usb@7000000: Fixed dependency cycle(s) with /soc@0/spmi@200f000/pmic@2/typec@1500/connector
Jun 21 13:36:16 fluffy kernel: /soc@0/clock-controller@b011050: Fixed dependency cycle(s) with /soc@0/clock-controller@b011050
Jun 21 13:36:16 fluffy kernel: /soc@0/clock-controller@1800000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/phy@1a94400
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000: Fixed dependency cycle(s) with /soc@0/interconnect@500000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000: Fixed dependency cycle(s) with /soc@0/clock-controller@1800000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/display-controller@1a01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/display-controller@1a01000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/phy@1a94400: Fixed dependency cycle(s) with /soc@0/clock-controller@1800000
Jun 21 13:36:16 fluffy kernel: /soc@0/camss@1b00020: Fixed dependency cycle(s) with /soc@0/cci@1b0c000/i2c-bus@0/s5k4h7yx@10
Jun 21 13:36:16 fluffy kernel: /soc@0/camss@1b00020: Fixed dependency cycle(s) with /soc@0/cci@1b0c000/i2c-bus@1/s5k5e9@2d
Jun 21 13:36:16 fluffy kernel: /soc@0/cci@1b0c000/i2c-bus@0/s5k4h7yx@10: Fixed dependency cycle(s) with /soc@0/camss@1b00020
Jun 21 13:36:16 fluffy kernel: /soc@0/cci@1b0c000/i2c-bus@1/s5k5e9@2d: Fixed dependency cycle(s) with /soc@0/camss@1b00020
Jun 21 13:36:16 fluffy kernel: /soc@0/spmi@200f000/pmic@2/typec@1500/connector: Fixed dependency cycle(s) with /soc@0/usb@7000000
Jun 21 13:36:16 fluffy kernel: /soc@0/spmi@200f000/pmic@2/typec@1500/connector: Fixed dependency cycle(s) with /soc@0/usb@7000000
Jun 21 13:36:16 fluffy kernel: /soc@0/usb@7000000: Fixed dependency cycle(s) with /soc@0/spmi@200f000/pmic@2/typec@1500/connector
Jun 21 13:36:16 fluffy kernel: /soc@0/clock-controller@b011050: Fixed dependency cycle(s) with /soc@0/clock-controller@b011050

[...]

Jun 21 13:36:16 fluffy :   โฌโฌ PMOS STAGE 1 โญโญ
Jun 21 13:36:16 fluffy : initramfs version: 3.11.0-r1
Jun 21 13:36:16 fluffy :   โฌโฌ PMOS STAGE 2 โญโญ
Jun 21 13:36:16 fluffy kernel: mmc1: new HS400 MMC card at address 0001
Jun 21 13:36:16 fluffy kernel: mmcblk1: mmc1:0001 S0J9N8 58.2 GiB
Jun 21 13:36:16 fluffy kernel:  mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 p29 p30 p31 p32 p33 p34 p35 p36 p37 p38 p39 p40 p41 p42 p43 p44 p45 p46 p47 p48 p49 p50 p51 p52 p53 p54 p55 p56 p57 p58 p59 p60 p61 p62 p63 p64
Jun 21 13:36:16 fluffy kernel: mmcblk1boot0: mmc1:0001 S0J9N8 4.00 MiB
Jun 21 13:36:16 fluffy kernel: mmcblk1boot1: mmc1:0001 S0J9N8 4.00 MiB
Jun 21 13:36:16 fluffy kernel: mmcblk1rpmb: mmc1:0001 S0J9N8 16.0 MiB, chardev (244:0)
Jun 21 13:36:16 fluffy kernel: platform 1a01000.display-controller: Adding to iommu group 4
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/display-controller@1a01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/display-controller@1a01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/display-controller@1a01000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: panel-boe-624-v0 1a94000.dsi.0: supply vsn not found, using dummy regulator
Jun 21 13:36:16 fluffy kernel: panel-boe-624-v0 1a94000.dsi.0: supply vsp not found, using dummy regulator
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: bound 1a94000.dsi (ops dsi_ops [msm])
Jun 21 13:36:16 fluffy kernel: adreno 1c00000.gpu: supply vdd not found, using dummy regulator
Jun 21 13:36:16 fluffy kernel: adreno 1c00000.gpu: supply vddcx not found, using dummy regulator
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: bound 1c00000.gpu (ops a3xx_ops [msm])
Jun 21 13:36:16 fluffy kernel: [drm:dpu_kms_hw_init:1173] dpu hardware revision:0x10100000
Jun 21 13:36:16 fluffy kernel: [drm] Initialized msm 1.13.0 for 1a01000.display-controller on minor 0
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: Direct firmware load for qcom/a530_pm4.fw failed with error -2
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: [drm:adreno_request_fw [msm]] *ERROR* failed to load a530_pm4.fw
Jun 21 13:36:16 fluffy kernel: Console: switching to colour frame buffer device 135x141
Jun 21 13:36:16 fluffy kernel: fb0: sys_imageblit: framebuffer is not in virtual address space.
Jun 21 13:36:16 fluffy kernel: fb0: sys_fillrect: framebuffer is not in virtual address space.
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: [drm] fb0: msmdrmfb frame buffer device
Jun 21 13:36:16 fluffy kernel: rmi4_i2c 3-0020: rmi_set_page: set page failed: -6.
Jun 21 13:36:16 fluffy kernel: rmi4_i2c 3-0020: Failed to set page select to 0
Jun 21 13:36:16 fluffy :   Setting up USB gadget through configfs
Jun 21 13:36:16 fluffy kernel: configfs-gadget.g1 gadget.0: HOST MAC 12:90:53:60:2f:9f
Jun 21 13:36:16 fluffy kernel: configfs-gadget.g1 gadget.0: MAC e6:d2:7e:64:fc:7e
Jun 21 13:36:16 fluffy : Trying to start server with parameters: Server IP addr: 172.16.42.1:67, client IP addr: 172.16.42.2, interface: usb0
Jun 21 13:36:16 fluffy : Setting framebuffer mode to: U:1080x2270p-0
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: Direct firmware load for qcom/a530_pm4.fw failed with error -2
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: [drm:adreno_request_fw [msm]] *ERROR* failed to load a530_pm4.fw
Jun 21 13:36:16 fluffy : Trying to mount subpartitions for 10 seconds...
[โ€“] INeedMana@piefed.zip 1 points 3 weeks ago

I'm not sure there's something about input in here

I know that those are different devices but take a look what was being used for debugging those issues
https://gitlab.postmarketos.org/postmarketOS/pmaports/-/work_items/352
https://gitlab.postmarketos.org/postmarketOS/pmaports/-/work_items/337

Can you run libinput debug-events and touch the screen a bit?

https://wiki.postmarketos.org/wiki/Input_devices