Kernel 4.10 doesn't detect digitizer in evtest

[ElectricPrism]

I just switched back to Kernel 4.9 LTS on Arch Linux and the Digitizer came back on device 15, on Kernel 4.10 it is missing. I wonder why.

$ sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	Power Button
/dev/input/event1:	Power Button
/dev/input/event2:	Logitech USB Receiver
/dev/input/event3:	Logitech USB Receiver
/dev/input/event4:	HDA Digital PCBeep
/dev/input/event5:	BTC USB Multimedia Keyboard
/dev/input/event6:	BTC USB Multimedia Keyboard
/dev/input/event7:	PC Speaker
/dev/input/event8:	HDA Intel PCH Rear Mic
/dev/input/event9:	HDA Intel PCH Front Mic
/dev/input/event10:	HDA Intel PCH Line Out
/dev/input/event11:	HDA Intel PCH Front Headphone
/dev/input/event12:	HDA NVidia HDMI/DP,pcm=3
/dev/input/event13:	HDA NVidia HDMI/DP,pcm=7
/dev/input/event14:	HDA NVidia HDMI/DP,pcm=8
/dev/input/event15:	Monoprice 22

[stacksmith]

This project is (or should I say, I am) lacking a rigorous understanding of kernel drivers and there was a lot of guesswork involved. If you go back to 4.10, you could try to see if lsusb sees it and follow up the chain? I am not currently using the Mono, so I cannot immediately check things...

[odysseywestra]

@stacksmith I'm up for figuring this out and testing if you wish to tackle this. I can say that this problem is persistent in Kernel 4.12 as well.

[stacksmith]

@odysseywestra I haven't had much of a chance to mess with this - I currently don't even have a mono set up (to top it off I dropped it yesterday - it turns on but I haven't had a chance to test the digitizer).. You are welcome to do anything you wish - pull request, or take over the repo altogether - it sounds like you are more in position to do something useful.

[odysseywestra]

@ElectricPrism the digitizer works on kernel 4.12. I was able to compile and install the module without any problems. The only reason I was having trouble installing the module was because I was missing the linux headers files which have to be installed. If you can confirm, I think we can close this issue.

[odysseywestra]

@stacksmith If you want me to take over the repo for you, I'll be willing to do it. Since this is going to be my main monitor for the next couple of years, I want to get the most I can out of it.

[stacksmith]

That's fine. A quick history: I started with aidyw's bosto driver, could not figure out what the heck, read a bunch of things and looked at the driver it was originally based on, realised that whoever wrote it didn't know what they were doing (they were keeping a lot of unnecessary state and copying stuff around pointlessly). So I stripped down everything I could - and it just worked. So apparently newer kernels made it not work.

In the process I inhereted the GPL licenses.

So, feel free to fork it and I will make a notation that you are developing. I haven't had much traffic - probably about 10 people used it.

[ElectricPrism]

@stacksmith Thank you. For me personally I noticed that after the next minor kernel version on Archlinux it returned to working again so I waited to see if it was a fluke.

It seems to be doing okay on 4.14.13-1-ARCH, we still use the device regularly, for the cost in many ways it is just as good or superior to our Wacom 21ux, so I hope to see new iterations of the device as with this driver Linux graphics development has been much more of a breeze, especially since people like everyone in this thread work together to resolve issues with the code available.

I have since purchased a Wacom Mobilestudio Pro 16 and I honestly love the Monoprice for Desktop Usage because it just works better with AMD MESA drivers and the input system doesn't require me running around hacking in evdev overrides for libinput to get the small finite motions to input and render correctly on high resolution documents.