Bug 333453 - Graphics Tablet MD 85925 not recognized.
Summary: Graphics Tablet MD 85925 not recognized.
Status: RESOLVED WORKSFORME
Alias: None
Product: wacomtablet
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Jörg Ehrichs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-04-15 10:09 UTC by Christian González
Modified: 2018-10-27 03:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
"lsusb -vv -s1:5" output (2.94 KB, text/plain)
2014-04-27 23:53 UTC, Christian González
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian González 2014-04-15 10:09:19 UTC
I have a Medion/Tevion MD 85925 graphics tablet, which works quite well with Kubuntu as input source under X, I even have a second monitor, and the tablet width is spread over both monitors perfectly. Clicking and drag/drop works too.
But under systemsettings/input/graphics tablets it is "not recognized".
It is also recognized as external disk and I can see/copy the files on it.
This is maybe just a feature request, but what can be done / how can I help to make this device recognized by KDE systemsettings?
It is recognized by the kernel as "idVendor=172f, idProduct=0027"

dmesg output after plugging in:
[35591.586948] usb 1-1.2: new full-speed USB device number 6 using ehci-pci
[35591.686515] usb 1-1.2: New USB device found, idVendor=172f, idProduct=0027
[35591.686527] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[35591.686533] usb 1-1.2: Product: Digital Ink Pad
[35591.686538] usb 1-1.2: Manufacturer:
[35591.686542] usb 1-1.2: SerialNumber: 01.00.00
[35591.687191] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[35591.687502] scsi8 : usb-storage 1-1.2:1.0
[35591.696918] input:                 Digital Ink Pad as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/input/input16
[35591.697521] hid-generic 0003:172F:0027.0008: input,hidraw3: USB HID v1.10 Mouse [                Digital Ink Pad] on usb-0000:00:1a.0-1.2/input1
[35592.690312] scsi 8:0:0:0: Direct-Access              Pen Pad storage  1.00 PQ: 0 ANSI: 0
[35592.693426] scsi 8:0:0:1: Direct-Access              Pen Pad storage  1.00 PQ: 0 ANSI: 0
[35592.694088] sd 8:0:0:0: Attached scsi generic sg2 type 0
[35592.694673] sd 8:0:0:1: Attached scsi generic sg3 type 0
[35592.702720] sd 8:0:0:0: [sdb] 60640 512-byte logical blocks: (31.0 MB/29.6 MiB)
[35592.709963] sd 8:0:0:0: [sdb] Write Protect is off
[35592.709977] sd 8:0:0:0: [sdb] Mode Sense: 20 00 00 00
[35592.720337] sd 8:0:0:0: [sdb] No Caching mode page found
[35592.720349] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[35592.749819] sd 8:0:0:1: [sdc] Attached SCSI removable disk
[35592.774533] sd 8:0:0:0: [sdb] No Caching mode page found
[35592.774543] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[35592.796744]  sdb: sdb1
[35592.848275] sd 8:0:0:0: [sdb] No Caching mode page found
[35592.848288] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[35592.848296] sd 8:0:0:0: [sdb] Attached SCSI removable disk
Comment 1 Jörg Ehrichs 2014-04-24 20:05:14 UTC
Can your tablet be changed via the wacom driver?
So does xsetwacom have any effect on your tablet?

I once tried to add support for othe rdevices, but never found any source on how to alter their settings.

Support for other devices would be great,
So if you could point me to any information how to change some settings for this devices. I 'll try to add it.

For the moment the system settings works only for tablets that are supported by the wacom kernel driver (and thus can be changed via xsetwacom calls)
Comment 2 Christian González 2014-04-27 23:36:07 UTC
No, sorry, "xsetwacom --list" does not generate any output. What else can I do?
Comment 3 Christian González 2014-04-27 23:52:21 UTC
According to lsusb, it identifies itself as usb stick (that's where the saved drawings live), and as "ID 172f:0027 Waltop International Corp."
I found in the source of xf86-input-wacom, in wcmUSN.c (http://sourceforge.net/p/linuxwacom/xf86-input-wacom/ci/39c4c7fca7db19ac550332fa53d0d4f58a26f67f/tree/src/wcmUSB.c) that ID, and it links to "IDs from Waltop's driver" at http://www.waltop.com.tw/download.asp?lv=0&id=2 - which unfortuneately is a 404 link. And at waltop.com I don't know which model to select...
Because mine is not really a Waltop, but a "Medion" (which mostly is a vendor that sells technical things from other vendors under it's own name). I'll at least add some "lsusb -vv info". as attachment
Comment 4 Christian González 2014-04-27 23:53:52 UTC
Created attachment 86306 [details]
"lsusb -vv -s1:5" output
Comment 5 Christian González 2014-04-27 23:59:00 UTC
(In reply to comment #2)
> No, sorry, "xsetwacom --list" does not generate any output. 
I meant "xsetwacom --list devices".
Comment 6 Christian González 2014-04-28 00:29:03 UTC
Oh. 'nother thing (sorry for my spam):
In /usr/share/X11/xorg.conf.d/50-wacom.conf is the following section:
  # Waltop tablets
  Section "InputClass"
          Identifier "Waltop class"
          MatchProduct "WALTOP"
          MatchIsTablet "on"
          MatchDevicePath "/dev/input/event*"
          Driver "wacom"
  EndSection
If I change 'MatchProduct "WALTOP"' to 'MatchProduct "WALTOP|Digital"', as recommended in e.g. http://ubuntuforums.org/archive/index.php/t-1639395.html, the tablet seems to be recognized by the wacom driver, and xsetwacom lists the device.

Tataaaaa, and the kde settings for graphics tablets show the tablet. Anyway, all the settings do not really match the functions the tablet has: I have no eraser button e.g.
The leftmost two buttons (a trash and a folder symbol) both seems to be assimilated to "button 2" - and I can change the click behaviour in the KDE settings dialog to match right mouse button. This works well.
Comment 7 Andrew Crouthamel 2018-09-25 03:42:25 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-10-27 03:35:31 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!