# Touchscreen Issue Resolved
**URL:** https://gpdsupport.com/t/touchscreen-issue-resolved/132
**Category:** Outstanding Issue
**Tags:** software, fault, linux, p2max
**Created:** [August 27, 2019, 11:00pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132 "2019-08-27T23:00:07Z")
**Posts on this page:** 20
**Page:** 3
### Author:  [@petem](https://gpdsupport.com/u/petem)
#### Post date: [September 14, 2019, 7:40pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/45 "2019-09-14T19:40:18Z")
Wish I could help @naquad - But I gave up after hours of messing with grub.d and trying to load the acpi override. I agree’d with Josh’s summation grub ~~sucks~~ or in my words is shit and it was simply not loading or not loading first. I believe arch and bios 0.23 works on systemd. I think this is what
@joshwiththegoodhair is using?
---
### Author:  [@wondow](https://gpdsupport.com/u/wondow)
#### Post date: [September 14, 2019, 8:23pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/46 "2019-09-14T20:23:44Z")
Could touchscreen work if we replace grub with systemd on debian/ubuntu derivatives?
---
### Author:  [@petem](https://gpdsupport.com/u/petem)
#### Post date: [September 14, 2019, 8:46pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/47 "2019-09-14T20:46:49Z")
It’s entirely possible, but I’m not that good with Linux to know exactly how to do so.
I use Ubuntu MATE / Xubuntu primarily for emacs / org-mode and LaTeX / Biblatex & TexLive stuff and even that its a steep learning curve and I’m fairly new at it sorry.
---
### Author:  [@naquad](https://gpdsupport.com/u/naquad)
#### Post date: [September 14, 2019, 9:05pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/48 "2019-09-14T21:05:48Z")
For the sake of testing I’ve moved from GRUB to systemd-boot with acpi\_override for BIOS 0.23, now I have those magic lines:
```
[0.017282] ACPI: DSDT ACPI table found in initrd [kernel/firmware/acpi/dsdt.aml][0x28dc3]
[0.017343] ACPI: Table Upgrade: override [DSDT-ALASKA- A M I]
```
But there’s no Goodix Touchscreen device at all and system boots only 1 time of 5, it stalls after “SHA256 validated” message ☹
After booting Windows and then booting to Linux it boots 100%. But kworker/0:2-kacpi\_notify process does 100% load on 1 core and still no touchscreen. Hence I suspect that version for BIOS 0.23 is not actually working.
In any case this is a huge red flag for me as touchscreen is essential for a device like P2 Max as touchpad here is very small and inconvenient.
I’m thinking we should officially request GPD company to fix this problem for us as they’ve also stated support for Linux ([GPD P2 Max: The world's smallest Ultrabook | Indiegogo](https://www.indiegogo.com/projects/gpd-p2-max-the-world-s-smallest-ultrabook/x/19199182#/updates/all) update at Jul 31, 2019 • 10:31AM) so its time to provide some 🙂 Also it’ll be interesting how will they fix it in Ubuntu MATE that’s announced for October.
P. S. There should be absolutely no custom kernels as solution to this problem. Those dark times passed years ago and I don’t want to manually update kernels.
---
### Author:  [@joshwiththegoodhair](https://gpdsupport.com/u/joshwiththegoodhair)
#### Post date: [September 15, 2019, 12:14pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/49 "2019-09-15T12:14:52Z")
Sorry guys for my delay. It’s been a bit busy with work lately.
@naquad - Are you using Xorg or Wayland?
I’ll have some time later today, and I’ll work on installing Mate on USB stick so that I can help get this override loading.
---
### Author:  [@naquad](https://gpdsupport.com/u/naquad)
#### Post date: [September 15, 2019, 12:28pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/50 "2019-09-15T12:28:42Z")
Xorg. And MATE will get updates from GPD somewhere in October according to their update at Indiegogo.
I’ve started looking into kernel patch by @PeterCxy and thinking to make it a standalone custom driver: [https://www.reddit.com/r/GPDPocket/comments/cuqb6x/on\_the\_issues\_of\_the\_touch\_screen\_of\_gpd\_p2\_max/f0c3iea/?context=3](https://www.reddit.com/r/GPDPocket/comments/cuqb6x/on_the_issues_of_the_touch_screen_of_gpd_p2_max/f0c3iea/?context=3) This way no kernel patching needs to be done.
Considering how much issues with BIOS GPD is having I really doubt we’ll have some BIOS level fix in the nearest future.
---
### Author:  [@joshwiththegoodhair](https://gpdsupport.com/u/joshwiththegoodhair)
#### Post date: [September 15, 2019, 1:01pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/51 "2019-09-15T13:01:30Z")
Honestly, the easiest way is to just preload the proper CPIO image - this prevents the need for any kernel or driver package changes that need to be maintained. The only time that CPIO image would need to be updated is if the BIOS changes.
I’m unsure of what the issue is in Ubuntu, but I’m installing it now to work through it. The end result should be a few lines of grub updating that should persist through kernel updates and whatnot. No custom kernel. No custom drivers.
---
### Author:  [@joshwiththegoodhair](https://gpdsupport.com/u/joshwiththegoodhair)
#### Post date: [September 15, 2019, 1:51pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/52 "2019-09-15T13:51:24Z")
Installed standard 64 bit Ubuntu Mate on a USB stick. This should work through any standard Ubuntu kernel updates or package updates. The _only_ time this would stop working is if another version of the GPD BIOS is used (either a version older than v0.23 or newer version). And if a newer version comes out, I will create a new CPIO image for that BIOS version.
This should also work on any Ubuntu variant and the generalized instructions should work for any distribution that uses grub. (Not sure if all distros use grub-mkconfig and `/etc/grub.d`, but the instructions should be similar.)
1. Download [acpi\_override\_23](http://josh.sh/acpi_override_23)
2. (As root/sudo), placed `acpi_override_23` in /boot
3. Edited `/etc/grub.d/10_linux` - changed line :225 from `initrd ${rel_dirname}/${initrd}` to `initrd /boot/acpi_override_23 ${rel_dirname}/${initrd}`
4. `sudo grub-mkconfig -o /boot/grub/grub.cfg`
5. Rebooted to a working touchscreen
[Video of this working in Ubuntu Mate](http://josh.sh/20190915-working-touchscreen-ubuntu-mate.mov)
---
### Author:  [@naquad](https://gpdsupport.com/u/naquad)
#### Post date: [September 15, 2019, 2:12pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/53 "2019-09-15T14:12:38Z")
1. I’m trying to do that in Arch Linux.
2. Exactly that solution resulting “initrd /boot/acpi\_override\_23 /boot/initramfs-linux.img” grub config line doesn’t boot at all. It is hanging after the line “Booting Arch Linux…” and nothing is happening.
I suspect this is related to kernel version or GRUB version. GRUB version is 2.04 and kernel is 5.2.11. What are the version in Ubuntu MATE?
---
### Author:  [@joshwiththegoodhair](https://gpdsupport.com/u/joshwiththegoodhair)
#### Post date: [September 15, 2019, 2:15pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/54 "2019-09-15T14:15:54Z")
Depending on how Arch was installed, you probably don’t need to preface the files with `/boot`. I use systemd-boot with Arch and EFI at `/boot`, and I never reference `/boot` in the loader entry.
---
### Author:  [@naquad](https://gpdsupport.com/u/naquad)
#### Post date: [September 15, 2019, 2:19pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/55 "2019-09-15T14:19:11Z")
I’ve put acpi\_override in the same folder where initramfs-linux.img and kernel reside. The path is correct. With systemd-boot there are boot & acpi issues + touchscreen is not visible in the system at all but this patch is definitely applied.
---
### Author:  [@naquad](https://gpdsupport.com/u/naquad)
#### Post date: [September 15, 2019, 2:22pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/56 "2019-09-15T14:22:00Z")
To be precise that’s the whole grub.cfg: [https://gist.github.com/27011f909d341a663113e2a7abbc5553](https://gist.github.com/27011f909d341a663113e2a7abbc5553) - see line #108 for override. This way system does not boot at all.
---
### Author:  [@joshwiththegoodhair](https://gpdsupport.com/u/joshwiththegoodhair)
#### Post date: [September 15, 2019, 2:27pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/57 "2019-09-15T14:27:50Z")
I’m unsure of what’s going on. If you’re not moving forward outside of grub, the issue is related to path or inability to determine the rootfs.
---
### Author:  [@naquad](https://gpdsupport.com/u/naquad)
#### Post date: [September 15, 2019, 2:33pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/58 "2019-09-15T14:33:24Z")
If I don’t mind originally you’ve been using Arch Linux to test the fix. Could you please share your mkinitcpio.conf? I suspect this is somehow related to GRUB unable to parse acpi\_override as initramfs-linux.img is gzip compressed and acpi\_override is not.
UPDATE: scratch that. I’ve tried to gzip acpi\_override, but no luck. No override has happened.
UPDATE 2: It looks like GRUB actually applies the override with both acpi and initrd ways, but kernel simply doesn’t boot when they’re applied. It is not clear why is that so and looks to be an issue of my particular setup ☹
---
### Author:  [@joshwiththegoodhair](https://gpdsupport.com/u/joshwiththegoodhair)
#### Post date: [September 15, 2019, 2:50pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/59 "2019-09-15T14:50:56Z")
@naquad - I would honestly try systemd-boot over grub. It’s easy to install in Arch and it’s a lot more direct with less config bullshit than grub.
1. `bootctl-install`
2. Create an entry in `/boot/loader/entries/arch.conf` with:
> title arch
> linux /vmlinuz-linux
> initrd /acpi\_override\_23
> initrd /initramfs-linux.img
> options rw
1. Edit `/boot/loader/loader.conf` and make sure `default` is set to `arch`
2. Reboot and make sure the EFI entry “Linux Boot Manager” is loaded
---
### Author:  [@naquad](https://gpdsupport.com/u/naquad)
#### Post date: [September 15, 2019, 2:52pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/60 "2019-09-15T14:52:06Z")
I already did so and the effect was 100% load of single core by kworker/0:2-kacpi\_notify and no touchscreen in the system at all. But the override was applied successfully, yes.
P. S. Details in the comment above: [Touchscreen Issue Resolved](https://gpdsupport.com/t/touchscreen-issue-resolved/132/48)
---
### Author:  [@joshwiththegoodhair](https://gpdsupport.com/u/joshwiththegoodhair)
#### Post date: [September 15, 2019, 2:55pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/61 "2019-09-15T14:55:25Z")
Are you sure you used my `acpi_override_23` instead of the one in PeterCxy’s Github releases page? When using his older `acpi_override` file on my machine with the v0.23 BIOS, I ran into power issues that sound similar to what you were experiencing.
---
### Author:  [@naquad](https://gpdsupport.com/u/naquad)
#### Post date: [September 15, 2019, 2:58pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/62 "2019-09-15T14:58:17Z")
```
naquad-gpd# ls -l
total 45576
-rw-r--r-- 1 root root 168448 сен 15 17:39 acpi_override
-rwxr-xr-x 1 root root 168448 сен 14 23:37 acpi_override.cpio
drwxr-xr-x 5 root root 4096 сен 15 17:41 grub
-rw-r--r-- 1 root root 30986814 сен 12 18:15 initramfs-linux-fallback.img
-rw-r--r-- 1 root root 9122565 сен 12 18:15 initramfs-linux.img
-rw-r--r-- 1 root root 6203776 сен 10 21:10 vmlinuz-linux
naquad-gpd# wget -q http://josh.sh/acpi_override_23
naquad-gpd# cmp acpi_override_23 acpi_override; echo $?
0
```
Absolutely sure.
---
### Author:  [@naquad](https://gpdsupport.com/u/naquad)
#### Post date: [September 15, 2019, 3:01pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/63 "2019-09-15T15:01:30Z")
@joshwiththegoodhair I think there could be another issue: when I’ve been updating BIOS firmwares I’ve skipped a single version: I’ve updated with 0.22 and then 0.23, 0.21 was never applied. Could that be a reason?
UPD: @joshwiththegoodhair is that what you’re seein
 g in your BIOS?
UPD 2: I can’t write more replies as a new user ☹ @joshwiththegoodhair thank you for your help. It looks like this is something related to my system, no idea what it is or what to do about it. I’ll wait for another BIOS update and see what happens. Thank you for your help.
---
### Author:  [@joshwiththegoodhair](https://gpdsupport.com/u/joshwiththegoodhair)
#### Post date: [September 15, 2019, 3:07pm UTC](https://gpdsupport.com/t/touchscreen-issue-resolved/132/64 "2019-09-15T15:07:21Z")
I don’t think that would be an issue. The BIOS flasher completely erases the previous BIOS before flashing the new version.
I’m honestly unsure of what’s going on. I would like to see others try to apply this CPIO image in Ubuntu+grub (now that there’s instructions on how to do so) to see if they have issues with the touchscreen working.
[Previous page](https://gpdsupport.com/t/touchscreen-issue-resolved/132.md?page=2)
[Next page](https://gpdsupport.com/t/touchscreen-issue-resolved/132.md?page=4)