Skip to content
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.

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

Getac UX10 tablet not recognized #197

Closed
TidelyPom opened this issue Feb 2, 2022 · 3 comments
Closed

Getac UX10 tablet not recognized #197

TidelyPom opened this issue Feb 2, 2022 · 3 comments

Comments

@TidelyPom
Copy link

Hi

I have a Getac UX10 tablet that isn't recognised by Ubuntu 20.04, I have run the sysnsinfo.sh script and I am sending you the tarball as recommended .
sysinfo.s4LlfzTr3g.tar.gz

@jigpu
Copy link
Member

jigpu commented Feb 2, 2022

It looks like this device is using a touchscreen digitizer from eGalax / EETI, which our sysinfo script largely ignored. I've updated it to no longer skip over devices from EETI. Can you please run the updated sysinfo.sh script and attach its results?

Does your UX10 use the "digitizer pen" (https://www.getac.com/us/accessories/digitizer-pen-gmpdx6/) or the "capacitive pen" (https://www.getac.com/us/accessories/capacitive-hard-tip-stylus-tether-gmpsxl/)?

@TidelyPom
Copy link
Author

Thank you. The pen is the capacitive pen. Here is the new tarball.

sysinfo.KtRbPRYHog.tar.gz

jigpu added a commit that referenced this issue Feb 9, 2022
@jigpu
Copy link
Member

jigpu commented Feb 9, 2022

Thanks! The update seems to have done the trick and dumped data for the eGalax / EETI sensor correctly. It looks like this particular model only uses a plain touchscreen sensor without any special digitizer handling. Because of this, it doesn't need an tablet definition file in libwacom -- there are no digitizer properties to be configured. I've added the sysinfo to the database for future reference, however, since it seems there is a sibling model which may have special digitizer handling...

The device shows up in the output of xinput list which indicates that it "should" be working. If it doesn't, you may need to contact the libinput developers (https://gitlab.freedesktop.org/libinput/libinput/) to diagnose why not. You can include a link to this issue since they would find the sysinfo output handy.

@jigpu jigpu closed this as completed Feb 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants