# 8" Touch Screen maps every input to lower right corner

**URL:** <https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254>\
**Category:** Troubleshooting\
**Created:** [1 June 2026 19:35 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254 "2026-06-01T19:35:38Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Motte](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@Motte](https://dietpi.com/forum/u/Motte)\
**Post date:** [1 June 2026 19:35 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/1 "2026-06-01T19:35:38Z")

</div>

### Creating a bug report/issue

I have searched the existing open and closed issues

#### Required Information

- DietPi version | `10.4`
- Distro version | `trixie`
- Kernel version | 6.18.29-current-sunxi64
- Architecture | arm64
- SBC model | PINE A64 (aarch64)
- Power supply used | RPi 5V 1A
- SD card used | Samsung Evo

#### Additional Information (if applicable)

- Software: Kiauh, Klipperscreen, HelixScreen, xcalibrate, xinput-calibrator (fresh installs)
- Hardware: Elecrow 8" HDMI-Touchscreen **[DIS85801D](https://www.elecrow.com/8-inch-touchscreen-ips-display-1280x800-small-portable-monitor.html)**

#### Steps to reproduce

1. Connect touchscreen with hdmi and usb.
2. Install KIAUH via git clone
3. Install either Klipperscreen or Helixscreen via KIAUH
4. reboot

#### Expected behaviour

- Klipperscreen or Helixscreen should respond to touch inputs .

#### Actual behaviour

- No apparent reaction from any GUI element to touch input regardless where I touch the screen.

#### Extra details

- The issue started after I updated to dietpi 10.4.
- I found that I can wake up the screen by touch. I connected it to my windows machine and it worked fine using the same cables I used for my SBC.
- I tried recalibration using xinput-calibrator and xcalibrate. Both showed that every touch is mapped to the right lower corner. But no matter what, both tools weren’t able to change this behaviour.
- I also tried Elecrow’s guide. But I can’t find config.txt. It’s not in /boot and I don’t have /boot/firmware.

I’m at the brink of pulling my hair. Help would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\
**Post date:** [2 June 2026 15:36 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/2 "2026-06-02T15:36:06Z")

</div>

`config.txt` only exists on raspberry pi.  
Can you share the guide you are talking about?

---

<div class="post-metadata">

**Author:** ![Motte](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@Motte](https://dietpi.com/forum/u/Motte)\
**Post date:** [2 June 2026 19:13 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/3 "2026-06-02T19:13:09Z")

</div>

Oh that’s why I can’t find `config.txt`. I was starting to question my installation…

You can find that guide here: [8 inch Touchscreen IPS Display 1280x800 Small Portable Monitor Compatible with Raspberry Pi 540043 Win 111087 Jetson Nano - Elecrow Wiki](https://www.elecrow.com/pub/wiki/8_inch_Touchscreen_IPS_Display_1280x800.html)  
(just after the pictures showing how to mount a Rpi to the back of the screen).

I also read a thread on the arch forums ( [[SOLVED] Touchscreen not working / Newbie Corner / Arch Linux Forums](https://bbs.archlinux.org/viewtopic.php?id=153446) ) and verified that the touch screen is correctly recognized (and not as a generic device or a graphic tablet).

---

<div class="post-metadata">

**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\
**Post date:** [2 June 2026 23:30 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/4 "2026-06-02T23:30:05Z")

</div>

Can you share

```auto
xinput list

```

---

<div class="post-metadata">

**Author:** ![Motte](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@Motte](https://dietpi.com/forum/u/Motte)\
**Post date:** [4 June 2026 07:47 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/5 "2026-06-04T07:47:43Z")

</div>

Sure:

`dietpi@OctoPine:~$ DISPLAY=:0 xinput list`  
`⎡ Virtual core pointer id=2 [master pointer (3)]`  
`⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]`  
`⎜ ↳ dw_hdmi id=7 [slave pointer (2)]`  
`⎜ ↳ QDtech MPI1001 Touchscreen id=6 [slave pointer (2)]`  
`⎣ Virtual core keyboard id=3 [master keyboard (2)]`  
`↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]`  
`↳ axp20x-pek id=8 [slave keyboard (3)]`  
`↳ dw_hdmi id=9 [slave keyboard (3)]`

---

<div class="post-metadata">

**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\
**Post date:** [5 June 2026 16:14 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/6 "2026-06-05T16:14:38Z")

</div>

Okay can you also check

```auto
DISPLAY=:0 xinput list-props 6

```

And then test the screen, execute

```auto
DISPLAY=:0 xinput test 6

```

and touch it in different places. You should see different values. If you always see the same, then it’s probably a kernel/driver issue

---

<div class="post-metadata">

**Author:** ![Motte](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@Motte](https://dietpi.com/forum/u/Motte)\
**Post date:** [8 June 2026 20:36 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/7 "2026-06-08T20:36:57Z")

</div>

Here are the touch screen’s props:

```bash
DISPLAY=:0 xinput list-props 6
Device ‘dw_hdmi’:
Device Enabled (129): 1
Coordinate Transformation Matrix (130): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Natural Scrolling Enabled (251): 0
libinput Natural Scrolling Enabled Default (252): 0
libinput Scroll Methods Available (253): 0, 0, 1
libinput Scroll Method Enabled (254): 0, 0, 1
libinput Scroll Method Enabled Default (255): 0, 0, 1
libinput Button Scrolling Button (256): 0
libinput Button Scrolling Button Default (257): 0
libinput Button Scrolling Button Lock Enabled (258): 0
libinput Button Scrolling Button Lock Enabled Default (259): 0
libinput Accel Speed (260): 0.000000
libinput Accel Speed Default (261): 0.000000
libinput Accel Profiles Available (262): 1, 1, 1
libinput Accel Profile Enabled (263): 1, 0, 0
libinput Accel Profile Enabled Default (264): 1, 0, 0
libinput Accel Custom Fallback Points (265):    
libinput Accel Custom Fallback Step (266): 0.000000
libinput Accel Custom Motion Points (267):      
libinput Accel Custom Motion Step (268): 0.000000
libinput Accel Custom Scroll Points (269):      
libinput Accel Custom Scroll Step (270): 0.000000
libinput Left Handed Enabled (271): 0
libinput Left Handed Enabled Default (272): 0
libinput Send Events Modes Available (273): 1, 0
libinput Send Events Mode Enabled (274): 0, 0
libinput Send Events Mode Enabled Default (275): 0, 0
Device Node (276): “/dev/input/event1”
Device Product ID (277): 0, 0
libinput Drag Lock Buttons (278):       
libinput Horizontal Scroll Enabled (279): 1
libinput Scrolling Pixel Distance (280): 15
libinput Scrolling Pixel Distance Default (281): 15
libinput High Resolution Wheel Scroll Enabled (282): 1

```

I couldn’t find any info on what the props for my device should be. I wonder why natural scrolling is disabled, but everything else seems in order. Did I overlook something?

I did

```bash
DISPLAY=:0 xinput test 6

```

and I can see that some process started, but there is no verbose feedback in my SSH console.

Verbose output of xinput-calibrator:

```bash
dietpi@OctoPine:~$ DISPLAY=:0 xinput_calibrator -v
DEBUG: XInputExtension version is 2.4
DEBUG: Skipping virtual master devices and devices without axis valuators.
DEBUG: Skipping device 'Virtual core XTEST pointer' id=4, does not report Absolute events.
DEBUG: Skipping device 'dw_hdmi' id=7, does not report Absolute events.
DEBUG: Selected device: QDtech MPI1001 Touchscreen
DEBUG: Not usbtouchscreen calibrator: Not a usbtouchscreen device
DEBUG: Not evdev calibrator: Evdev: invalid "Evdev Axis Calibration" property format
Calibrating standard Xorg driver "QDtech MPI1001 Touchscreen"
        current calibration values: min_x=0, max_x=65535 and min_y=0, max_y=65535
        If these values are estimated wrong, either supply it manually with the --precalib option, or run the 'get_precalib.sh' script to automatically get it (through HAL).
DEBUG: Found that 'QDtech MPI1001 Touchscreen' is a sysfs name.
INFO: width=1280, height=800
DEBUG: Adding click 0 (X=1278, Y=798)
DEBUG: Not adding click 1 (X=1278, Y=798): within 7 pixels of previous click
DEBUG: Not adding click 1 (X=1278, Y=798): within 7 pixels of previous click
DEBUG: Not adding click 1 (X=1278, Y=798): within 7 pixels of previous click
DEBUG: Not adding click 1 (X=1278, Y=798): within 7 pixels of previous click
DEBUG: Not adding click 1 (X=1278, Y=798): within 7 pixels of previous click
DEBUG: Not adding click 1 (X=1278, Y=798): within 7 pixels of previous click
DEBUG: Not adding click 1 (X=1278, Y=798): within 7 pixels of previous click
DEBUG: Not adding click 1 (X=1278, Y=798): within 7 pixels of previous click
DEBUG: Not adding click 1 (X=1278, Y=798): within 7 pixels of previous click

```

I made `click 0` on the first cross shown in the upper left part of the screen, and the next cross is shown in the upper right part. Every click is registered in the same spot.

---

<div class="post-metadata">

**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\
**Post date:** [9 June 2026 12:11 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/8 "2026-06-09T12:11:52Z")

</div>

Alright, the calibration is correct, it shows meaningful min and max values, but it always registers just one coordinate, no matter where you touch.

Can you make one last test, with `evtest` (You probably need to install it first: `apt install evtest`)🙂  
run `sudo evtest` and chose the correct device from the list, then just touch the dispaly as you did before. It will show us the raw kernel events. If the coordinates stay the same again then we know that it is a kernel/driver problem.

> [@Motte](#):
>
> `Device Product ID (277): 0, 0`

This is odd, it does not recogn

---

<div class="post-metadata">

**Author:** ![Motte](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@Motte](https://dietpi.com/forum/u/Motte)\
**Post date:** [10 June 2026 22:11 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/9 "2026-06-10T22:11:22Z")

</div>

> [@Jappe](#):
>
> > [@Motte](#):
> >
> > `Device Product ID (277): 0, 0`
> 
> This is odd, it does not recogn

Oh wow i totally missed that. On the arch forums someone talked about how his touchscreen’s IDs weren’t listed in the kernel: [[SOLVED] Touchscreen not working / Newbie Corner / Arch Linux Forums](https://bbs.archlinux.org/viewtopic.php?id=153446)

Here is the output of evtest, I did four touches, each near a different corner.

```bash
dietpi@OctoPine:~$ sudo DISPLAY=:0 evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: axp20x-pek
/dev/input/event1: dw_hdmi
/dev/input/event2: QDtech MPI1001 Touchscreen
Select the device event number [0-2]: 2
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x484 product 0x5750 version 0x101
Input device name: "QDtech MPI1001 Touchscreen"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value 1280
      Min 0
      Max 1280
    Event code 1 (ABS_Y)
      Value 800
      Min 0
      Max 800
    Event code 40 (ABS_MISC)
      Value 0
      Min 0
      Max 1
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1781128886.698273, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1781128886.698273, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1781128886.698273, type 3 (EV_ABS), code 0 (ABS_X), value 183
Event: time 1781128886.698273, type 3 (EV_ABS), code 1 (ABS_Y), value 146
Event: time 1781128886.698273, type 3 (EV_ABS), code 0 (ABS_X), value 1280
Event: time 1781128886.698273, type 3 (EV_ABS), code 1 (ABS_Y), value 800
Event: time 1781128886.698273, -------------- SYN_REPORT ------------
Event: time 1781128886.812222, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1781128886.812222, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1781128886.812222, -------------- SYN_REPORT ------------
Event: time 1781128887.455267, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1781128887.455267, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1781128887.455267, type 3 (EV_ABS), code 0 (ABS_X), value 1124
Event: time 1781128887.455267, type 3 (EV_ABS), code 1 (ABS_Y), value 156
Event: time 1781128887.455267, type 3 (EV_ABS), code 0 (ABS_X), value 1280
Event: time 1781128887.455267, type 3 (EV_ABS), code 1 (ABS_Y), value 800
Event: time 1781128887.455267, -------------- SYN_REPORT ------------
Event: time 1781128887.589223, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1781128887.589223, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1781128887.589223, -------------- SYN_REPORT ------------
Event: time 1781128888.274271, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1781128888.274271, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1781128888.274271, type 3 (EV_ABS), code 0 (ABS_X), value 234
Event: time 1781128888.274271, type 3 (EV_ABS), code 1 (ABS_Y), value 596
Event: time 1781128888.274271, type 3 (EV_ABS), code 0 (ABS_X), value 1280
Event: time 1781128888.274271, type 3 (EV_ABS), code 1 (ABS_Y), value 800
Event: time 1781128888.274271, -------------- SYN_REPORT ------------
Event: time 1781128888.418223, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1781128888.418223, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1781128888.418223, -------------- SYN_REPORT ------------
Event: time 1781128889.082272, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1781128889.082272, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1781128889.082272, type 3 (EV_ABS), code 0 (ABS_X), value 1064
Event: time 1781128889.082272, type 3 (EV_ABS), code 1 (ABS_Y), value 516

```

---

<div class="post-metadata">

**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\
**Post date:** [11 June 2026 11:17 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/10 "2026-06-11T11:17:50Z")

</div>

> [@Motte](#):
>
> Oh wow i totally missed that. On the arch forums someone talked about how his touchscreen’s IDs weren’t listed in the kernel: [[SOLVED] Touchscreen not working / Newbie Corner / Arch Linux Forums](https://bbs.archlinux.org/viewtopic.php?id=153446)

Ok good to know, at least this does not indicate any problem.

> [@Motte](#):
>
> ```auto
> Event: time 1781128887.455267, type 3 (EV_ABS), code 0 (ABS_X), value 1124
> Event: time 1781128887.455267, type 3 (EV_ABS), code 1 (ABS_Y), value 156
> Event: time 1781128887.455267, type 3 (EV_ABS), code 0 (ABS_X), value 1280
> Event: time 1781128887.455267, type 3 (EV_ABS), code 1 (ABS_Y), value 800
> 
> ```

So the system gets the right coordinates, but then also gets the coordiantes for the bottom right corner, like you described. ~~This is likely a scaling/calibration issue.~~  
With the update to dietpi 10.4 you also udpated your kernel to mitigate the “Copy Fail” and “Dirty Frag” bugs?  
And the display also runs in it’s native resolution?

Klipper does also provice some troubleshooting steps for a behaviour like you are experiencing:  
[https://klipperscreen.readthedocs.io/en/latest/Troubleshooting/Touch\_issues/#touch-rotation-and-matrix](https://klipperscreen.readthedocs.io/en/latest/Troubleshooting/Touch_issues/#touch-rotation-and-matrix)

---

<div class="post-metadata">

**Author:** ![Motte](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@Motte](https://dietpi.com/forum/u/Motte)\
**Post date:** [11 June 2026 19:11 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/11 "2026-06-11T19:11:20Z")

</div>

> [@Jappe](#):
>
> Ok good to know, at least this does not indicate any problem.

If I read the posts at Arch Forums correctly, this might lead to wrong drivers being loaded:

> 1. the touchscreen manufacturer id (0x1ddb) and product id (0x1) are currently not into the usb vendors database (even after update-usbids)
> 2. as such, the kernel (through udev) tried to discover the nature of it blind folded (i’d be interested to know on what basis), and ends up thinking that’s a tablet device (and not a touchscreen)

(From the last post in that thread.)

> [@Jappe](#):
>
> With the update to dietpi 10.4 you also udpated your kernel to mitigate the “Copy Fail” and “Dirty Frag” bugs?

No I’v never explicitly updated the kernel. I only used apt upgrade or apt full-upgrade so far. How can do that?

> [@Jappe](#):
>
> And the display also runs in it’s native resolution?

Yes.

---

<div class="post-metadata">

**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\
**Post date:** [12 June 2026 21:04 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/12 "2026-06-12T21:04:17Z")

</div>

> [@Motte](#):
>
> If I read the posts at Arch Forums correctly, this might lead to wrong drivers being loaded:

But in your case the kernel detects a touch device also with the correct resolution (see the evtest output)

> [@Motte](#):
>
> No I’v never explicitly updated the kernel. I only used apt upgrade or apt full-upgrade so far. How can do that?

When you did full-upgrade you installed the newest kernel (which is recommended to mitigate the CVEs).  
You could try to downgrade the kernel for testing and see if it’s working again, but then you have a vulnerable system.  
@MichaIng what do you think is the best to do here?

---

<div class="post-metadata">

**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\
**Post date:** [15 June 2026 22:54 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/13 "2026-06-15T22:54:41Z")

</div>

The guide you mentioned is explicitly for RPi, and cannot work anywhere else. The `config.txt` changes are only to enforce the correct (display) resolution, mode, and disable HDMI audio, along with some legacy options that are noops since a longer time, nothing which would affect touch input coordinates or so. There is a weird “driver” download listed, which however is no driver, but RPi-only `config.txt` files and scripts, basically this repo: [GitHub - goodtft/LCD-show: 2.4" 2.8"3.2" 3.5" 5.0" 7.0" TFT LCD driver for the Raspberry PI 3B+/A/A+/B/B+/PI2/ PI3/ZERO/ZERO W · GitHub](https://github.com/goodtft/LCD-show)  
Moreover, this is almost only for (smaller) DSI displays, some with I2C-attached touch. None of this is relevant for a HDMI display + USB touch. =\> That guide is crap, forget about it 😄.

The Arch Linux thread is 14 years old, before the SBC era even started, and maybe a decade before your touchscreen was released. =\> Irrelevant 😉.

The DietPi ~~v10.4~~ v10.3 update implied the kernel upgrade from Linux 6.12 to 6.18, hence generally possible that this included some breaking change. But HDMI displays + USB touch inputs should not require any special drivers, but work mostly OOTB, after calibration.

`xinput_calibrator` should create a config below `/etc/X11/`. Check the configs there, `/etc/X11/xorg.conf` and everything below `/etc/X11/xorg.conf.d` in particular. Maybe there are some contradicting/conflicting ones. Maybe easiest to remove all of them (back them up somewhere). Then check again coordinates via `evtest` and/or touch input. If still wrong, run `xinput_calibrator` once. Check `/etc/X11/` about which config file it generated, so we know the pattern. … IIRC it is `/etc/X11/xorg.conf.d/99-calibration.conf`.

If nothing helps, you can try to downgrade the kernel. But before you do, run these commands to protect your system against the Copy Fail, Dirty Frag, and Fragnesia vulnerabilities:

```sh
printf 'install algif_aead /bin/false\nblacklist algif_aead\n' | sudo tee /etc/modprobe.d/copyfail.conf
printf 'install esp4 /bin/false\ninstall esp6 /bin/false\ninstall rxrpc /bin/false\n' | sudo tee /etc/modprobe.d/dirtyfrag.conf
printf 'blacklist esp4\nblacklist esp6\nblacklist rxrpc\n' | sudo tee -a /etc/modprobe.d/dirtyfrag.conf
sudo modprobe -r algif_aead esp4 esp6 rxrpc
echo 3 | sudo tee /proc/sys/vm/drop_caches

```

Then:

```sh
apt install linux-{image,dtb}-current-sunxi64=26.02.0-trunk-dietpi8

```

This is the latest Linux 6.12, from March. We pushed the first Linux 6.18 kernel in early April, so DietPi v10.3 included it already. Did you upgrade to v10.4 from an earlier version than that? Else, it is unlikely that a Linux 6.18 patch release caused the issue 🤔.

---

<div class="post-metadata">

**Author:** ![Motte](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@Motte](https://dietpi.com/forum/u/Motte)\
**Post date:** [22 June 2026 20:19 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/14 "2026-06-22T20:19:16Z")

</div>

Thanks for the detailed walkthrough!

I can’t find any configs in `/etc/X11`:

```auto
dietpi@OctoPine:/etc/X11$ ls
app-defaults fonts rgb.txt xinit Xreset Xresources Xsession.d Xwrapper.config
default-display-manager ratpoison xcalibrate xkb Xreset.d Xsession Xsession.options

```

But it seem they are stored in `/usr/share/X11`:

```auto
dietpi@OctoPine:/usr/share/X11$ ls
locale rgb.txt XErrorDB xkb xorg.conf.d

```

```auto
dietpi@OctoPine:/usr/share/X11/xorg.conf.d$ ls
10-amdgpu.conf 10-quirks.conf 10-radeon.conf 40-libinput.conf

```

I can’t use xinput\_calbrator, because it won’t accept any of my input after the first touch, as they’re too close to each other. Strange enough, I can’t deactivate the threshold (–misclick 0).

```auto
dietpi@OctoPine:/usr/share/X11/xorg.conf.d$ DISPLAY=:0 xinput_calibrator -v
DEBUG: XInputExtension version is 2.4
DEBUG: Skipping virtual master devices and devices without axis valuators.
DEBUG: Skipping device 'Virtual core XTEST pointer' id=4, does not report Absolute events.
DEBUG: Skipping device 'dw_hdmi' id=7, does not report Absolute events.
DEBUG: Selected device: QDtech MPI1001 Touchscreen
DEBUG: Not usbtouchscreen calibrator: Not a usbtouchscreen device
DEBUG: Not evdev calibrator: Evdev: invalid "Evdev Axis Calibration" property format
Calibrating standard Xorg driver "QDtech MPI1001 Touchscreen"
        current calibration values: min_x=0, max_x=65535 and min_y=0, max_y=65535
        If these values are estimated wrong, either supply it manually with the --precalib option, or run the 'get_precalib.sh' script to automatically get it (through HAL).
DEBUG: Found that 'QDtech MPI1001 Touchscreen' is a sysfs name.
INFO: width=1280, height=800
DEBUG: Adding click 0 (X=640, Y=400)
DEBUG: Not adding click 1 (X=640, Y=400): within 7 pixels of previous click
DEBUG: Not adding click 1 (X=640, Y=400): within 7 pixels of previous click
DEBUG: Not adding click 1 (X=640, Y=400): within 7 pixels of previous click
DEBUG: Not adding click 1 (X=640, Y=400): within 7 pixels of previous click

```

(I did the test _after_ I used xcalibrate, which generated a matrix that maps all input to the middle of the screen)

I do wonder about that line:

```auto
DEBUG: Not usbtouchscreen calibrator: Not a usbtouchscreen device

```

Does that indicate something?

I used xcalibrate ([GitHub - reinderien/xcalibrate: X.org touchscreen calibrator · GitHub](https://github.com/reinderien/xcalibrate)) instead:

```auto
dietpi@OctoPine:~/xcalibrate$ DISPLAY=:0 ./xcalibrate
Pointer devices:
ID Name
   4 Virtual core XTEST pointer
   6 QDtech MPI1001 Touchscreen
   7 dw_hdmi

Device to calibrate [6]:

Old calibration (Coordinate Transformation Matrix):
[[1. 0. 0.]
 [0. 1. 0.]
 [0. 0. 1.]]

Calibrate? [y]:
Point count (min 3) [4]:
Disable rotation and skew? [y]:

Warning: deficient transformation of rank 1. Please try calibrating again.
/home/dietpi/xcalibrate/./xcalibrate:258: RuntimeWarning: Mean of empty slice.
  quality = -np.log10(residuals.mean())
/usr/lib/python3/dist-packages/numpy/_core/_methods.py:145: RuntimeWarning: invalid value encountered in scalar divide
  ret = ret.dtype.type(ret / rcount)
Warning: deficient transformation of rank 1. Please try calibrating again.
New calibration:
[[0.24999969 0. 0.25039093]
 [0. 0.24999922 0.25062578]
 [0. 0. 1.]]
Quality (should be at least 3): nan

Test? [y]: y
Point count (min 3) [4]:
Use calibration? [y]: y
The new calibration has been activated.
Write example xorg conf for persistence? [y]: y
To persist this calibration,
sudo mv 99-libinput-ts-calib.conf /usr/share/X11/xorg.conf.d/
dietpi@OctoPine:~/xcalibrate$ ls
99-libinput-ts-calib.conf funding.md license readme.md requirements.txt xcalibrate

```

Contents of `99-libinput-ts-calib.conf`:

```auto
# Generated by xcalibrate on 22/06/26 21:52:28

# https://www.x.org/releases/current/doc/man/man5/xorg.conf.5.xhtml#heading9
Section "InputClass"
    Identifier "QDtech MPI1001 Touchscreen touchscreen calibration"

    # For xinput device 6
    MatchDevicePath "/dev/input/event1"
    MatchProduct "QDtech MPI1001 Touchscreen"

    # For xinput property "Coordinate Transformation Matrix"
    Option "TransformationMatrix" "0.249999694347009 0 0.250390930175408 0 0.249999216794434 0.250625781247553 0 0 1"
EndSection

```

When testing with `xcalibrate` and the new matrix it seems like all touches are now mapped to the screen’s middle.

Then tested it with `evtest`:

```auto
dietpi@OctoPine:~/xcalibrate$ sudo DISPLAY=:0 evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: axp20x-pek
/dev/input/event1: QDtech MPI1001 Touchscreen
/dev/input/event2: dw_hdmi
Select the device event number [0-2]: 1
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x484 product 0x5750 version 0x101
Input device name: "QDtech MPI1001 Touchscreen"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value 1280
      Min 0
      Max 1280
    Event code 1 (ABS_Y)
      Value 800
      Min 0
      Max 800
    Event code 40 (ABS_MISC)
      Value 0
      Min 0
      Max 1
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1782158778.789760, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1782158778.789760, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1782158778.789760, type 3 (EV_ABS), code 0 (ABS_X), value 115
Event: time 1782158778.789760, type 3 (EV_ABS), code 1 (ABS_Y), value 110
Event: time 1782158778.789760, type 3 (EV_ABS), code 0 (ABS_X), value 1280
Event: time 1782158778.789760, type 3 (EV_ABS), code 1 (ABS_Y), value 800
Event: time 1782158778.789760, -------------- SYN_REPORT ------------
Event: time 1782158778.934706, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1782158778.934706, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1782158778.934706, -------------- SYN_REPORT ------------
Event: time 1782158779.189757, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1782158779.189757, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1782158779.189757, type 3 (EV_ABS), code 0 (ABS_X), value 604
Event: time 1782158779.189757, type 3 (EV_ABS), code 1 (ABS_Y), value 126
Event: time 1782158779.189757, type 3 (EV_ABS), code 0 (ABS_X), value 1280
Event: time 1782158779.189757, type 3 (EV_ABS), code 1 (ABS_Y), value 800
Event: time 1782158779.189757, -------------- SYN_REPORT ------------
Event: time 1782158779.324706, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1782158779.324706, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1782158779.324706, -------------- SYN_REPORT ------------
Event: time 1782158780.298760, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1782158780.298760, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1782158780.298760, type 3 (EV_ABS), code 0 (ABS_X), value 1048
Event: time 1782158780.298760, type 3 (EV_ABS), code 1 (ABS_Y), value 360
Event: time 1782158780.298760, type 3 (EV_ABS), code 0 (ABS_X), value 1280
Event: time 1782158780.298760, type 3 (EV_ABS), code 1 (ABS_Y), value 800
Event: time 1782158780.298760, -------------- SYN_REPORT ------------
Event: time 1782158780.463705, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1782158780.463705, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1782158780.463705, -------------- SYN_REPORT ------------
Event: time 1782158780.636756, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1782158780.636756, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1782158780.636756, type 3 (EV_ABS), code 0 (ABS_X), value 943
Event: time 1782158780.636756, type 3 (EV_ABS), code 1 (ABS_Y), value 146
Event: time 1782158780.636756, type 3 (EV_ABS), code 0 (ABS_X), value 1280
Event: time 1782158780.636756, type 3 (EV_ABS), code 1 (ABS_Y), value 800
Event: time 1782158780.636756, -------------- SYN_REPORT ------------
Event: time 1782158780.761705, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1782158780.761705, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1782158780.761705, -------------- SYN_REPORT ------------

```

Btw: How can I change my code to be highlighted like your’s? Sometimes it’s done automatically, sometimes not…  
Also: Sorry for those long lines of code. Is there a way to collapse that so my post isn’t so bloated?

---

<div class="post-metadata">

**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\
**Post date:** [23 June 2026 12:36 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/15 "2026-06-23T12:36:25Z")

</div>

> [@Motte](#):
>
> Btw: How can I change my code to be highlighted like your’s?

You.can define a language for each codeblock and based on this it will highlight automatically. See

> **[Selecting the programming language used in code blocks](https://meta.discourse.org/t/selecting-the-programming-language-used-in-code-blocks/19247)**
>
> 🔖 This guide explains how to select the programming language used in code blocks within Discourse posts, along with how to suppress syntax highlighting. 🙋 Required user level: All users When you enclose code using triple backticks in your...

---

<div class="post-metadata">

**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\
**Post date:** [23 June 2026 22:29 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/16 "2026-06-23T22:29:35Z")

</div>

> [@Motte](#):
>
> ```auto
> To persist this calibration,
> sudo mv 99-libinput-ts-calib.conf /usr/share/X11/xorg.conf.d/
> 
> ```

Uhh, how come it makes such a false advice … `/usr/share` is for packages, not for custom admin or generated files. Those should go to `/etc/X11/xorg.conf.d`.

Maybe `xinput_calibrator` as well generates the file in the current dir, so you need to move it to `/etc/X11/xorg.conf.d` manually?

About the `TransformationMatrix`: [xorg.conf(5) — xserver-xorg-core — Debian trixie — Debian Manpages](https://manpages.debian.org/trixie/xserver-xorg-core/xorg.conf.5.en.html#Option~33)  
I know the `"Calibration"` option, which has 4 values only: min X, max X, min Y, max Y (while values can be swapped in case of axis swaps). But interestingly, I do not see this option in the manpage 🤔.

Btw, did you

```sh
apt install xserver-xorg-input-evdev

```

And there is another touchscreen calibrator to test:

```sh
apt install x11-touchscreen-calibrator

```

---

<div class="post-metadata">

**Author:** ![Motte](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@Motte](https://dietpi.com/forum/u/Motte)\
**Post date:** [31 August 2026 21:21 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/17 "2026-08-31T21:21:07Z")

</div>

Sorry for getting back to you so late. Life had some different plans so I hadn’t any time for my printer server ☹

> [@MichaIng](#):
>
> Uhh, how come it makes such a false advice … `/usr/share` is for packages, not for custom admin or generated files. Those should go to `/etc/X11/xorg.conf.d`.

Seems like both locations for that config do work.

> [@MichaIng](#):
>
> Maybe `xinput_calibrator` as well generates the file in the current dir, so you need to move it to `/etc/X11/xorg.conf.d` manually?

Can’t test that because all clicks register at the same coordinate so `xinput_calibrator` won’t advance after the first click.

> [@MichaIng](#):
>
> Btw, did you
> 
> ```auto
> apt install xserver-xorg-input-evdev
> 
> ```

Yes I did that but it didn’t change anything.

> [@MichaIng](#):
>
> And there is another touchscreen calibrator to test:
> 
> ```auto
> apt install x11-touchscreen-calibrator
> 
> ```

Tried that and on github it says this one automatically adapts the Coordinate Transformation Matrix on resolution change, so I did

```auto
sudo DISPLAY=:0 xrandr -q

```

which oddly enough showed my display was in 1024x768 resolution:

```auto
dietpi@OctoPine:~$ sudo DISPLAY=:0 xrandr -q
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
HDMI-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 1280mm x 800mm
   1280x800 63.59 +
   1920x1080 60.00
  1024x768 (0x43) 65.000MHz -HSync -VSync
        h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.36KHz
        v: height 768 start 771 end 777 total 806 clock 60.00Hz

```

I than did

```auto
sudo DISPLAY=:0 xrandr --output HDMI-1 --mode 1280x800

```

and

```auto
sudo DISPLAY=:0 xrandr --output HDMI-1 --mode 1920x1080

```

which both successfully changed the resolution (which btw I can’t using dietpi-config). The GUI then takes only a part of the screen but I still can’t calibrate the touch matrix to correctly register input. Also, I can’t change the resolution back to 1024x768.

I wonder if having an active `99-libinput-ts-calib.conf` and may cause `x11-touchscreen-calibrator` to be unable to do the automatic configuration?. I will have a look at that tomorrow. It’s time for bed now 😴

---

<div class="post-metadata">

**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\
**Post date:** [31 August 2026 22:27 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/18 "2026-08-31T22:27:38Z")

</div>

In any case, when testing different calibrators and re-calibration, remove any previously generated config file. Else they will most likely conflict. They configure things with different directives in different classes, IIRC.

> [@Motte](#):
>
> > [@MichaIng](#):
> >
> > Uhh, how come it makes such a false advice … `/usr/share` is for packages, not for custom admin or generated files. Those should go to `/etc/X11/xorg.conf.d`.
> 
> Seems like both locations for that config do work.

Sure both works, else either package configs or admin config changes wouldn’t be effective. This is about FHS and Linux distro conventions, and how package managers deal with it: `/usr` is static `dpkg` territory, where packages add/remove/replace files without asking. `/etc` is admin territory, where packages place files as formal `conffiles`, which are never replaced, removed, or re-added, without interactive admin confirmation, if they were ever edited or manually removed. And `/etc` takes priority over `/usr` for files with the same name. This way you can override package configs, or mask them by placing a symlink to `/dev/null` with the same name into the respective `/etc` dir.

---

<div class="post-metadata">

**Author:** ![Motte](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@Motte](https://dietpi.com/forum/u/Motte)\
**Post date:** [20 November 2026 14:47 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/19 "2026-11-20T14:47:13Z")

</div>

Sorry for coming back so late again. Life keeps getting in the way of my 3d printing hobby.

I made sure to delete the configs of one calilbrator before using the other - still no success.

I remember I tried an alternative to Klipperscreen called Helixscreen. I _thought_ it didn’t respond to touch input, but maybe it was just the same symptoms I have now? I fully deleted Helixscreen and tried looking for any leftovers - couldn’t find anything. I’ll ask the dev if he has any insights, but - by any chance - do you have an idea where to look for changed input configuration?

I also found this calibrator: [GitHub - ivan-matveev/xorg\_calibrator: Touch screen calibration utility for X.Org X Window System · GitHub](https://github.com/ivan-matveev/xorg_calibrator#acknowledgments) but it seems to be made for x64 architecture only.

Also Klipperscreen allows to use Wayland instead of Xserver. I tried Wayland with Cage as compositor, but the screen stayed black. Is Wayland a path to pursue or is that a dead end on DietPi?

---

<div class="post-metadata">

**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\
**Post date:** [20 November 2026 17:58 UTC](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254/20 "2026-11-20T17:58:33Z")

</div>

> [@Motte](#):
>
> do you have an idea where to look for changed input configuration?

See the [man page](https://manpages.debian.org/xorg.conf) about which files and directories X11 parses. For drop-in configs, `/usr/share/X11/xorg.conf.d` and `/etc/X11/xorg.conf.d`. Only the latter should contain custom configs, but as of all false guides and readmes, makes sense to check `/usr/share/X11/xorg.conf.d` too. If unsure whether a config is from a package or not, check with

```sh
dpkg -S <file path>

```

This will list any package which provides that path.

> [@Motte](#):
>
> I also found this calibrator: [GitHub - ivan-matveev/xorg\_calibrator: Touch screen calibration utility for X.Org X Window System · GitHub](https://github.com/ivan-matveev/xorg_calibrator#acknowledgments) but it seems to be made for x64 architecture only.

And a single pre-release shortly after the initial upload 3 years ago only. Doesn’t look trustworthy and has been abandoned. I wouldn’t use it.

> [@Motte](#):
>
> Is Wayland a path to pursue or is that a dead end on DietPi?

Not yet supported by `dietpi-software`. You can use it, but deskop environments and other GUI applications installed with `dietpi-software` ship with X11 setup only. There should be however guides around how to setup a particular desktop environment with Wayland, that work on any Debian/Ubuntu-like distro. Both windowing systems can work side by side, so if properly configured, you can start a desktop/application with either of them.

[Next page](https://dietpi.com/forum/t/8-touch-screen-maps-every-input-to-lower-right-corner/25254.md?page=2)
