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

No configuration of Inspiroy 2M possible in GNOME 47 #775

Closed
1 task done
Int-Circuit opened this issue Oct 7, 2024 · 7 comments
Closed
1 task done

No configuration of Inspiroy 2M possible in GNOME 47 #775

Int-Circuit opened this issue Oct 7, 2024 · 7 comments

Comments

@Int-Circuit
Copy link

Int-Circuit commented Oct 7, 2024

  • Device name:

  • Device model identifier:

  • libwacom version: 2.13

  • I understand that libwacom does affect whether the device works (see Troubleshooting)

Bug description

After upgrading to fedora 41 Beta and libwacom 2.13 (which partly fixed #772, the tablet is now detected) , the GNOME 47 control center reports the tablet and the stylus as a generic one, with no option to configure the buttons and sensibility of it.

image

image

image

image

This is a major deal breaker as the tablet picks up the stylus position from around two centimetres from the tablet's surface.

@Int-Circuit Int-Circuit changed the title No configuration of the tablet possible in GNOME 47 No configuration of Inspiroy 2M possible in GNOME 47 Oct 7, 2024
@whot
Copy link
Member

whot commented Oct 7, 2024

the GNOME 47 control center reports the tablet and the stylus as a generic one, with no option to configure the buttons and sensibility of it.

That's a misunderstanding. The tablet is an external one, not a generic one, so it should allow for button mappings. And the sensibility and stylus button mappings are configurable right there, isn't it?

What's missing are the external pad buttons but they don't show up in the list-local-devices output either so right now my guess is that the Pad device doesn't have ID_INPUT_TABLET_PAD assigned to it.

Using libinput record can you see the Pad device and if so what is its output? attach the output here please, don't copy it.

This is a major deal breaker as the tablet picks up the stylus position from around two centimetres from the tablet's surface.

Proximity? That is expected, yes. What exactly is the wrong behaviour here, can you expand please?

@Int-Circuit
Copy link
Author

Int-Circuit commented Oct 8, 2024

the GNOME 47 control center reports the tablet and the stylus as a generic one, with no option to configure the buttons and sensibility of it.

That's a misunderstanding. The tablet is an external one, not a generic one, so it should allow for button mappings. And the sensibility and stylus button mappings are configurable right there, isn't it?

Yes I can configure the stylus buttons and pressure. Sadly, as you can see in the 1st picture, I've got no option to configure the buttons of the tablet. A reboot didn't do anything.

What's missing are the external pad buttons but they don't show up in the list-local-devices output either so right now my guess is that the Pad device doesn't have ID_INPUT_TABLET_PAD assigned to it.

Using libinput record can you see the Pad device and if so what is its output? attach the output here please, don't copy it.

It seems that libinput sees the tablet as a mouse and keyboard
image
Pad_Output_Keyboard.txt
Pad_Output_Mouse.txt
Pad_Output_Pen.txt

This is a major deal breaker as the tablet picks up the stylus position from around two centimetres from the tablet's surface.

Proximity? That is expected, yes. What exactly is the wrong behaviour here, can you expand please?

EDIT: I talked with a friend that draws semi-pro, it's normal, I'm sorry if I confused you.

@whot
Copy link
Member

whot commented Oct 18, 2024

right, so this tablet needs a kernel driver or, better, a BPF to make it work properly. This is the M version of my S I think, so you should be able to use the existing one from udev-hid-bpf.

By changing this line to add your device. Basically it should look like this:

#define PID_INSPIROY_2_S 0x0066
#define PID_INSPIROY_2_M 0x0067

HID_BPF_CONFIG(
	HID_DEVICE(BUS_USB, HID_GROUP_GENERIC, VID_HUION, PID_INSPIROY_2_S),
	HID_DEVICE(BUS_USB, HID_GROUP_GENERIC, VID_HUION, PID_INSPIROY_2_M),
);

Then you should be able to install it, replug the device and hooray. There's a tutorial and other docs to explain what happens.

This may not give you all buttons, and you will also need huion-switcher to switch to raw mode but the pieces should all be there. See #718 for an outline though.

@Int-Circuit
Copy link
Author

Int-Circuit commented Oct 18, 2024 via email

@Int-Circuit
Copy link
Author

Quick question do you know which package in fedora installs libudev? I just can't seem to find it on the repos and need it for the compilation of the .bpf.c files.
Thanks in advance

@whot
Copy link
Member

whot commented Oct 21, 2024

Did it make some progress

not yet, huion-switcher is still required, there's no BPF hook to do what it does just yet. ETIME and tbh I'm kinda punting this to @bentiss anyway ;)

Quick question do you know which package in fedora installs libudev?

Best approach: sudo dnf "pkgconfig(libudev)" - that way dnf looks up what package provides libudev.pc so you don't have to care. Works with pretty much any meson error about a missing package.

@whot
Copy link
Member

whot commented Oct 21, 2024

closing this, we need the device to be supported by the kernel (via BPF), nothing libwacom can do here

/close

@whot whot closed this as completed Oct 21, 2024
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