Skip to content

Touchscreen not working in latest Bookworm image #43

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
lurch opened this issue Oct 10, 2023 · 44 comments
Closed

Touchscreen not working in latest Bookworm image #43

lurch opened this issue Oct 10, 2023 · 44 comments
Milestone
First patch release

Comments

@lurch
Copy link
Collaborator

lurch commented Oct 10, 2023

There's a kernel change needed ( raspberrypi/linux#5622 ) in order to get the touchscreen-part of the Raspberry Pi Touch Display working, which isn't yet in the APT-packaged kernel. The display-part of the Raspberry Pi Touch Display still works fine.

As a temporary workaround, until the stable APT-packaged kernel gets updated, you can run rpi-update to get the latest bleeding-edge kernel.
@lurch lurch added this to the First patch release milestone Oct 10, 2023
@steveiliop56
Copy link

It works now. I tested it.

@XECDesign
Copy link

We haven't done anything on our end to fix it, so I don't think it would've magically started working.

@willyvaessen
Copy link

I performed an rpi-update and indeed, the screen now responds to a touch. However, the touch functionality seems to be inverted after the first reboot following the update.
I had to set the orientation back to "normal" and then inverted it again to get it to perform as desired.

@lurch
Copy link
Collaborator Author

lurch commented Oct 12, 2023

On a Raspberry Pi 4, I've just tested all combinations of 32-bit / 64-bit Bookworm and DSI-only / DSI & HDMI, and in no situations was the "touch" of the touchscreen working.

@lurch lurch reopened this Oct 12, 2023
@pelwell
Copy link

pelwell commented Oct 12, 2023

Did you rpi-update? We know that the fix isn't in the current images.

@steveiliop56
Copy link

Umm I have a dfrobot 7 inch dsi display and it works just fine...

@lurch
Copy link
Collaborator Author

lurch commented Oct 12, 2023

Please re-read the initial comment... "Raspberry Pi Touch Display" i.e. https://www.raspberrypi.com/products/raspberry-pi-touch-display/

@steveiliop56
Copy link

Yeah I am just saying that something is wrong in the gpio communication part of the official screen I guess because in the screen I have that's only with a dsi cable it works...

@SerdarAbali
Copy link

Official 7" display, the touch function does not work. I am here to acknowledge and confirm the problem.

@6by9
Copy link

6by9 commented Oct 13, 2023

@SerdarAbali

Official 7" display, the touch function does not work. I am here to acknowledge and confirm the problem.

and as per #43 (comment)

Did you rpi-update? We know that the fix isn't in the current images.

@SerdarAbali
Copy link

@6by9 my bad, thank you. rpi-update fixes it for good.
fresh bookworm 64-bit
Pi 4

@homebrewzero
Copy link

I performed an rpi-update and indeed, the screen now responds to a touch. However, the touch functionality seems to be inverted after the first reboot following the update. I had to set the orientation back to "normal" and then inverted it again to get it to perform as desired.

I have done this several times, and the touch functionality is inverted still.

@jvoss11
Copy link

jvoss11 commented Oct 21, 2023 •
edited
Loading

very new to raspberry pi. just moved from bullseye to a fresh bookwarm install.
i have only done ssh, and rpi-update as stated above to the fresh OS.
However i noticed that the mouse pointer is not showing when dragging or when selecting any item. it will return if i use a connected usb mouse. not sure if this has been addressed.

guess this is a goodby to bookworm. to may thing not working back to bulleye or buster. can we say microsoft. i try bookworm next year..

@willyvaessen
Copy link

I performed an rpi-update and indeed, the screen now responds to a touch. However, the touch functionality seems to be inverted after the first reboot following the update. I had to set the orientation back to "normal" and then inverted it again to get it to perform as desired.

I have done this several times, and the touch functionality is inverted still.

Sorry to hear that. I performed the update that was suggested and the steps I described. Nothing more.

@raccoon-mh
Copy link

https://www.okdo.com/getting-started/get-started-with-7-touchscreen-for-raspberry-pi/

I wired on the above site.

And on debian bookworm Release 2023-10-10(bake with pi imager v1.7.5),

it worked after sudo rpi-update

I'm not sure if that wiring actually works.

@GeekNJ
Copy link

GeekNJ commented Oct 28, 2023

Thanks - the rpi-update worked for me after reflashing a SD card with the latest 32-bit image that Pi Imager offered.

@6by9
Copy link

6by9 commented Oct 28, 2023

@raccoon-pi

https://www.okdo.com/getting-started/get-started-with-7-touchscreen-for-raspberry-pi/

I wired on the above site.

That wiring is wrong. You only need two wires for power - please see the Raspberry Pi documentation for the display at https://www.raspberrypi.com/documentation/accessories/display.html#powering-the-touch-display

The extra two wires are covered in https://www.raspberrypi.com/documentation/accessories/display.html#legacy-support and are only needed for the very original Pi1 Model A and Model B.

@tigernero79
Copy link

double tapping doesn't work in Debian 12. this doesn't allow you to open folders or launch apps that are on the desktop

@ysiegel29
Copy link

Hello, does anyone know if this screen will work with OS Lite Bookworm and Pygame? The above discussion relates to the desktop version but does it matter?
I have a hdmi 7" display and can't get touchscreen to work... Thank you!

@pelicanmedia
Copy link

double tapping doesn't work in Debian 12. this doesn't allow you to open folders or launch apps that are on the desktop

Same here. After a rpi-update. Changing orientation and rebooting, twice. Single touch works, but double tap does not.

@MartinNK
Copy link

MartinNK commented Nov 6, 2023

I installed bookworm 64bit on a fresh microSD with image on a Pi 3b ... now having some problems. My original 7" touch display is used 180 degrees rotated because of the frame I used.

Out of the box 2 problems ... display is now upside down, but I want to see console mode (at boot with logo and gui - wayland insteed of X - rotated right ... touch does not work (seen above solution ... rpi-update) ...

problem with vnc ... heard about realvnc server not compatible with wayland at the moment :-(

Some data I put on install with newest rpi-imager (v1.7.1 I think) is not copied right ...

@tigernero79
Copy link

Rip imager online version 1.8.1

@MartinNK
Copy link

MartinNK commented Nov 7, 2023 via email

@DNSGeek
Copy link

DNSGeek commented Dec 16, 2023

It's still not working for me on an RPi 3B running bookworm-64 bit. Yes, I've run rpi-update.

@aneitzel
Copy link

same problem here, i also applied latest rpi-updates + reboot

BUT ORIGINAL 7" SCREEN TOUCH NOT WORKING :-(

alpha@pi2:~ $ cat /proc/version
Linux version 6.1.68-v8+ (dom@buildbot) (aarch64-linux-gnu-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1708 SMP PREEMPT Thu Dec 14 16:09:41 GMT 2023

alpha@pi2:~ $ sudo rpi-update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** Performing self-update
*** Relaunching after update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** We're running for the first time
*** Backing up files (this will take a few minutes)
*** Backing up firmware
*** Backing up modules 6.1.21-v8+
#############################################################
WARNING: This update bumps to rpi-6.1.y linux tree
See: https://forums.raspberrypi.com/viewtopic.php?t=344246

'rpi-update' should only be used if there is a specific
reason to do so - for example, a request by a Raspberry Pi
engineer or if you want to help the testing effort
and are comfortable with restoring if there are regressions.

DO NOT use 'rpi-update' as part of a regular update process.
##############################################################
Would you like to proceed? (y/N)

*** Downloading specific firmware revision (this will take a few minutes)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 144M 100 144M 0 0 189k 0 0:13:03 0:13:03 --:--:-- 177k
*** Updating firmware
*** Updating kernel modules
*** depmod 6.1.68-v7+
*** depmod 6.1.68-v7l+
*** depmod 6.1.68-v8+
*** depmod 6.1.68+
*** depmod 6.1.68-v8-16k+
*** Updating VideoCore libraries
*** Using SoftFP libraries
*** Updating SDK
*** Running ldconfig
*** Storing current firmware revision
*** Deleting downloaded files
*** Syncing changes to disk
*** If no errors appeared, your firmware was successfully updated to ceecdc222d448aa708b1de59f7053aa55c43b283
*** A reboot is needed to activate the new firmware

@tigernero79
Copy link

the only way to have touch working is:

to type:

sudo nano /boot/config.txt

put a # inside
(comment out) then disable the entry:

comment on the entry like this:

dtoverlay=vc4-kms-v3d

like this:

#dtoverlay=vc4-kms-v3d

Then

enable xorg mode from "sudo raspi-config ---> advance options ---> Wayland ---> select --- > W1 X11

reboot and the touch will work

if you have to reverse it, remember to put the directive in confix.txt:

sudo nano /boot/config.txt

insert

lcd_rotate=2

@steveiliop56
Copy link

steveiliop56 commented Dec 16, 2023 •
edited
Loading

No why? The whole point is to work on wayland. Not switch back to x11.

@tigernero79
Copy link

No why? The whole point is to work on wailand. Not switch back to x11.

the touch with wayland works for me, I'm talking on an official pi5 4gb ram and 7" touch, the touch problem happens when I rotate the screen, it doesn't rotate the touch so clicking on the left results in a touch on the right but above all in wayland the double touch doesn't work Going back to 100% certified with their official display.

@steveiliop56
Copy link

steveiliop56 commented Dec 16, 2023 •
edited
Loading

Maybe try to disable the full kms driver?

@tigernero79
Copy link

Unfortunately it doesn't solve the problem, the double touch would actually work but according to the Raspberry technicians the finger doesn't put pressure on the same point as the touch and therefore it doesn't perform. with x11 instead the system senses a nearby area and performs a double tap. it is used to open folders and run a program. going back to x11 is currently the ideal solution for those who want to use official displays with bookworm

@steveiliop56
Copy link

Yeah indeed it's unstable for now. It was even hard to set up a keyboard until recently. It's a big change but needs a lot of work to be stable.

@lurch
Copy link
Collaborator Author

lurch commented Dec 17, 2023

There seems to be a couple of different issues being discussed here:

  1. Double-touch not working: known problem, see Double-click doesn't work with the Touch Display #15
  2. Display / touchscreen rotation: see the documentation at https://www.raspberrypi.com/documentation/accessories/display.html#changing-the-screen-orientation

@DNSGeek
Copy link

DNSGeek commented Dec 17, 2023

There seems to be a couple of different issues being discussed here:

  1. Double-touch not working: known problem, see Double-click doesn't work with the Touch Display #15
  2. Display / touchscreen rotation: see the documentation at https://www.raspberrypi.com/documentation/accessories/display.html#changing-the-screen-orientation

No, we're also talking about the complete lack of touch functionality at all on an RPi 3B running bookworm. 64.

@lurch
Copy link
Collaborator Author

lurch commented Dec 17, 2023

@DNSGeek Sure, I was going to check that when I'm in the office tomorrow, and update this issue as appropriate 🙂

@lurch
Copy link
Collaborator Author

lurch commented Dec 18, 2023

The original problem reported in this issue (where an rpi-update was needed in order to get the touch functionality of the Raspberry Pi Touch Display working) has now been incorporated into the December 5th 2023 release of Raspberry Pi OS, so closing this issue.

@DNSGeek I've been doing extensive testing today, and I've not found any situations where the touch functionality isn't working. Note that if you have both an HDMI and DSI screen attached, you need to use the Screen Configuration program to assign the touch-inputs to the DSI screen, as described in https://www.raspberrypi.com/documentation/accessories/display.html#changing-the-screen-orientation
(If you're still having problems, please open a separate issue)

I did find a separate problem with the 3B+ though (see raspberrypi/linux#5801 ), but that also affects the display-output of the screen, not just the touch-input.

@lurch lurch closed this as completed Dec 18, 2023
@tigernero79
Copy link

tigernero79 commented Dec 19, 2023 •
edited
Loading

With wayland after reading the link above:

https://www.raspberrypi.com/documentation/accessories/display.html#changing-the-screen-orientation

placing the directive in boot/confix.txt

dtoverlay=vc4-kms-dsi-7inch,invx,invy

and disabling the entry:

display_auto_detect=1

putting the hash sign # at the beginning

#display_auto_detect=1

the touch works with the rotation done via "GUI"

but the double touch still doesn't work

I hope they will resolve it soon

for the moment I return to x11 with the config.txt configuration I reported above

@colejohnson66
Copy link

Experiencing this issue on an image created yesterday (with official imaging tool). We have a CM4 with the official 7-inch display on DSI0. We ran rpi-update and apt update+upgrade, but the touchscreen still does not work.

@6by9
Copy link

6by9 commented Jan 18, 2024

Experiencing this issue on an image created yesterday (with official imaging tool). We have a CM4 with the official 7-inch display on DSI0. We ran rpi-update and apt update+upgrade, but the touchscreen still does not work.

DSI0 is known to have issues on CM4 though - raspberrypi/linux#4946.

The dsi0 override to vc4-kms-dsi-7inch is currently intended for Pi5 only.
And neither display_auto_detect nor camera_auto_detect are intended to work on CMs as there are too many wiring permutations to make it worth trying to handle.

@colejohnson66
Copy link

We don't have any issues with the display part of the module - only the touchscreen. And this was working fine when we were running Buster.

@6by9
Copy link

6by9 commented Jan 18, 2024 •
edited
Loading

We don't have any issues with the display part of the module - only the touchscreen. And this was working fine when we were running Buster.

In which case you're using the touch screen with the legacy display stack, and not vc4-kms-v3d as is the default with Bookworm.
If you've changed that, then there is no saying what else you've changed. At that point it's hardly the fault of the Bookworm image.

If you wish to open a thread on the forums, then we can try to work out why it doesn't work, but it's not this issue.

@DNSGeek
Copy link

DNSGeek commented Jan 18, 2024 via email

@6by9
Copy link

6by9 commented Jan 19, 2024

I’ve changed nothing, and the touchscreen which worked fine in buster does not work in bookworm. The display works fantastic. I can’t touch a damn thing. I’ve made no changes to bookworm other than doing updates.

I was responding directly to colejohnson66 as he's using a CM4 and on DSI0.
The CM4 has no autodetection for the display, or configuration in the legacy stack, and DSI0 has other issues.

In #43 (comment) lurch said

(If you're still having problems, please open a separate issue)

Did you do that?

@JojoEffect JojoEffect mentioned this issue Oct 6, 2024
Open
@mangelozzi
Copy link

I’ve changed nothing, and the touchscreen which worked fine in buster does not work in bookworm. The display works fantastic. I can’t touch a damn thing. I’ve made no changes to bookworm other than doing updates.

I was responding directly to colejohnson66 as he's using a CM4 and on DSI0. The CM4 has no autodetection for the display, or configuration in the legacy stack, and DSI0 has other issues.

In #43 (comment) lurch said

(If you're still having problems, please open a separate issue)

Did you do that?

So what is the fix? "DSI0 has other issues", how do we fix these "other issue" ? I am also using a CM4.

@6by9
Copy link

6by9 commented Jan 3, 2025

So what is the fix? "DSI0 has other issues", how do we fix these "other issue" ? I am also using a CM4.

DSI0 issues were resolved back in April 2024, and isn't the subject of this issue.
Use a kernel from after that date and it should al be working.

If you have a specific problem, then open a new issue.
Commenting on closed issues which are only tangentially related won't help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
First patch release
Development

No branches or pull requests