Re: [DIGImend-users] Huion H610 and Gimp: sometimes strange behaviour
Brought to you by:
spb_nick
From: Vince H. <Vi...@Pl...> - 2015-02-14 22:20:08
|
your modinfo version doesn't match mine. Missing version 5 [vince@desk2 kernelDrivers.pre-svn]$ tail hid-huion.c .report_fixup = huion_report_fixup, .raw_event = huion_raw_event, }; module_driver(huion_driver, hid_register_driver, hid_unregister_driver); MODULE_AUTHOR("Martin Rusko"); MODULE_AUTHOR("Nikolai Kondrashov"); MODULE_DESCRIPTION("Huion HID driver"); MODULE_LICENSE("GPL"); MODULE_VERSION("5"); [vince@desk2 kernelDrivers.pre-svn]$ I had the buttons working on F20. re update to f21, to use fedup, I had to delete all the nvidia propriatary drivers. fedup just loops otherwise. Nick says his latest should be in the 3.18 kernel. I didn't try huion with virgin kernel when I put in update Friday. On Sat, Feb 14, 2015 at 4:47 PM, Sergey 'Jin' Bostandzhyan <ji...@me...> wrote: > On Sat, Feb 14, 2015 at 04:27:06PM -0500, Vince Herried wrote: >> when it fails for me usually because X didn't restart. > > it was restarted and the "wacom" driver was loaded when attaching the > tablet, not the standard evdev driver, so that part worked as I > mentioned in my last mail. > >> first be sure the driver is installed >> >> [vince@desk2 ~]$ modinfo hid-huion >> filename: /lib/modules/3.18.6-200.fc21.i686+PAE/extra/hid-huion.ko >> version: 5 >> license: GPL >> description: Huion HID driver >> author: Nikolai Kondrashov >> author: Martin Rusko >> srcversion: 29344D5C58BC9ECAAA4F28A >> alias: hid:b0003g*v00005543p0000004D >> alias: hid:b0003g*v00005543p0000006E >> alias: hid:b0003g*v0000256Cp0000006E >> depends: >> vermagic: 3.18.6-200.fc21.i686+PAE SMP mod_unload 686 >> [vince@desk2 ~]$ > > modinfo hid-huion > filename: > /lib/modules/3.18.6-100.fc20.x86_64/kernel/drivers/hid/hid-huion.ko > license: GPL > description: Huion HID driver > author: Martin Rusko > alias: hid:b0003g*v00005543p0000006E > alias: hid:b0003g*v0000256Cp0000006E > depends: > intree: Y > vermagic: 3.18.6-100.fc20.x86_64 SMP mod_unload > > I should probably upgrade to fc21 and see what happens. > >> Then check >> >> /var/log/Xorg.0.log >> >> assuming X was restarted you should find something like: >> 249.920] (II) XINPUT: Adding extended input device "HUION PenTablet >> stylus" (type: STYLUS, i >> d 8) > > ...yes, I do have those messages. > >> >> [vince@desk2 ~]$ xsetwacom --list >> HUION PenTablet stylus id: 8 type: STYLUS >> HUION PenTablet pad id: 9 type: PAD > >> Your list makes me think the driver is not installed. a recent change >> from Nick consolidated the devices > > > With the evdev driver xsetwacom always returned an empty list, so now > the driver is clearly installed - I get a list of devices. > > Question is of course, if F21 has something more recent than F20, although > the kernel version seems to be the same... > >> >> >> and >> [vince@desk2 ~]$ xsetwacom -V >> 0.28.0 > > ...your xsetwacom versoin is newer, maybe that makes the difference. > >> I don't think the problem is with your version of xsetwacom. But that >> is a guess on my part. > > It seems that xsetwacom is the only thing that differs between your and > my installation, so I think it might make a difference... I will try to > upgrade. > >> Gimp gave me lots of issues. Some times I would >> $ rm .gimp-2.8/devicerc >> >> >> I noticed that some times the stylus would move the mouse pointer but >> that it could only select some things and not others. >> Say file but not the pencil icon in gimp. >> Then noticed that it had same issues outside of gimp. I got no idea >> what was going on. > > Interesting, hmm, I only noticed that I sometimes was not able to draw > on the canvas, just as I described in my first mail, but otherwise > everything seemed to work fine. It almost sounds that you ran into more > problems than I did, but then again, I do not use the tablet too much > outside of gimp, I tried it with blender (worked) and with synfig studio > (partly worked), also wanted to try krita but it crashes right away when > the tablet is plugged in. > >> btw I have to re-execute the huion.sh script every time the tablet >> gets plugged in. > > From what I understand those settings (also the ones that the windows > tool makes) are not permanent. It would be cool if we could pass those > options directly to the driver to make the settings "more" permanent. > Nick, do you think this would be possible? > >> Which is why I tried to get it to run of the udev script. >> The udev trigger works but to set the xsetwacom it has to have a X11 DISPLAY. >> The I tried various delays in the udev trigger to wait till X was up. >> Also put in the log statements to help me determine what it was runing >> vs when X started. > > Why don't you loop until (pseudo code) [ -n `pidof -s X` ] and try it > then after a short delay? You may also need to set xhost +localhost to > add yourself to the access list, but that's just a guess, I'll try it out, > provided that xsetwacom lets me map the buttons, I'll let you know how far I > get, but I'll update to Fedora 21 first. > > Thanks once more for the hints, scripts and configs! > > Kind regards, > Jin > > >> The udev is >> # to restart udev after changes issue >> # >> # udevadm control --reload >> # >> SUBSYSTEM=="usb", ATTRS{idVendor}=="256c", SYMLINK+="input/H610N", >> RUN+="/home/vince/bin/udevHuion" >> >> >> and >> [vince@desk2 ~]$ cat bin/udevHuion >> #!/bin/bash >> #Mon Jan 19 16:49:06 EST 2015 >> # called by udev rule >> #set -x >> WHO=vince >> WHAT="/home/vince/bin/huion.sh" >> >> Display=`who | grep -m1 ^$WHO.*\( | awk '{print $5}' | sed 's/[(|)]//g'` >> export DISPLAY="$Display" >> su vince -c "DISPLAY=$Display $WHAT udev"& >> >> [vince@desk2 ~]$ >> >> fails every time. >> >> ---------- >> good luck >> >> On Sat, Feb 14, 2015 at 5:12 AM, Sergey 'Jin' Bostandzhyan >> <ji...@me...> wrote: >> > Hi Vince, >> > >> > thanks for your reply. >> > >> > The xorg config worked, the Wacom driver is now loaded. >> > >> > xsetwacom --list devices does indeed list: >> > >> > HUION PenTablet stylus id: 15 type: STYLUS >> > HUION PenTablet stylus id: 17 type: STYLUS >> > HUION PenTablet eraser id: 18 type: ERASER >> > HUION PenTablet pad id: 19 type: PAD >> > >> > In gimp I also see those devices as well (although there I have only one >> > "stylus", the other one is just called "HUION PenTablet" >> > >> > The huion.sh script does not work however, it prints the following >> > message 7 times: >> > >> > Invalid offset into Wacom Button Actions property. >> > >> > I can confirm that the script is not faulty, i.e. it's trying to set things >> > like: >> > ++ xsetwacom set 19 button 11 key '[' >> > Invalid offset into Wacom Button Actions property. >> > >> > So it's some problem with the wacom driver or xsetwacom tool? >> > Setting the keys does not seem to work :( >> > >> > Also, in Gimp, I do not really know how to select the other devices (or if >> > it even makes sesnes to select other devices? It's always using the >> > "HUION PenTablet stylus". >> > >> > Question is... why does xsetwacom work for you? >> > >> > xsetwacom -V gives me: >> > 0.23.0 >> > >> > What version do you have? >> > >> > Kind regards, >> > Jin >> > >> > >> > On Fri, Feb 13, 2015 at 11:03:22PM -0500, Vince Herried wrote: >> >> to set up the buttons you need to do several things. >> >> first create this file.... >> >> [vince@desk2 ~]$ cat /etc/X11/xorg.conf.d/50-huion.conf >> >> Section "InputClass" >> >> Identifier "digimend2 version" >> >> MatchIsTablet "on" >> >> MatchDevicePath "/dev/input/event*" >> >> # use for wacom driver >> >> MatchProduct "PenTablet" >> >> Driver "wacom" >> >> Option "rotate" "half" >> >> #Option "Button1" "key +Control_L +z -z " # undo >> >> #Option "Button2" "key +Shift_L +e -e " # eraser >> >> #Option "Button3" "key +n -n " # pencil >> >> #Option "Button8" "key +Shift_L +equal -equal " # zoom in >> >> #Option "Button9" "key +minus -minus " # zoom out >> >> #Option "Button10" "key +bracketright -bracketright " >> >> # + pencil >> >> #Option "Button11" "key +bracketleft -bracketleft " >> >> # - pencil >> >> # Option "Button12" # hand >> >> # >> >> # end GIMP settings >> >> # >> >> >> >> # use for evdev >> >> # Driver "evdev" >> >> # Option "InvertX" "on" >> >> # Option "InvertY" "on" >> >> EndSection >> >> --------------------------------------------------------ends above >> >> this line-------------------------------------------------- >> >> note the commented out settings they don't work. >> >> I have the line >> >> Option "rotate" "half" >> >> because I'm left handed, if you are not left handed, leave that out. >> >> >> >> >> >> Then re-start X. There is a setting in the system settings that will >> >> enable the key combination of ctrl alt backspace to cause X to >> >> restart. >> >> I can't find the kde settings at moment where I enabled that key >> >> combination. There are several ways to re-start X, search google. >> >> >> >> Then copy the attached shell script some place and mark it executable...;. >> >> chmod u+x huion.sh >> >> >> >> the script is kind of messy, but it works to set up the buttons on my H610. >> >> >> >> good luck. >> >> ------------------ >> >> Vince >> >> >> >> On Fri, Feb 13, 2015 at 5:49 PM, Sergey 'Jin' Bostandzhyan >> >> <ji...@me...> wrote: >> >> > Hi, >> >> > >> >> > first of all: thanks a lot for the driver! I'm on Fedora 20 with >> >> > 3.18.5-101.fc20.x86_64 kernel, just plugged it in and it worked :) >> >> > >> >> > I do however experience some glitches now and then and I am not sure if its >> >> > a problem with the driver or with Gimp. >> >> > >> >> > Sometimes when I start Gimp I can not paint using the tablet, i.e. the input >> >> > devices does not switch to Huion when I'm trying to paint. I can still >> >> > navigate all menus and clicks on menus and toolboxes work, but painting on >> >> > the canvas is impossible. When this happens, painting with the mouse is also >> >> > impossible, while clicks on menus etc. work fine. >> >> > >> >> > When this happens I have to quite Gimp, disconnect and reconnect the tablet >> >> > and start Gimp again and chances are high that it will just start working >> >> > again. >> >> > >> >> > Any ideas how to debug this? >> >> > >> >> > Second thing that I noticed is that it's sometimes recognized differently >> >> > in Gimp. When selecting the tablet in the input devices dialog >> >> > I will see no keys at all, sometimes I will see >200 keys which is really >> >> > weird. >> >> > >> >> > And one last question: is there also a utility, similar to the one that is >> >> > supplied with the windows drivers, to tell the tablet to send other key >> >> > combos? In default mode it sends weird combinations with ctrl- and shift- >> >> > and I somehow failed to remap that. >> >> > >> >> > Kind regards, >> >> > Jin >> >> > >> >> > >> >> > ------------------------------------------------------------------------------ >> >> > Dive into the World of Parallel Programming. The Go Parallel Website, >> >> > sponsored by Intel and developed in partnership with Slashdot Media, is your >> >> > hub for all things parallel software development, from weekly thought >> >> > leadership blogs to news, videos, case studies, tutorials and more. Take a >> >> > look and join the conversation now. http://goparallel.sourceforge.net/ >> >> > _______________________________________________ >> >> > DIGImend-users mailing list >> >> > DIG...@li... >> >> > https://lists.sourceforge.net/lists/listinfo/digimend-users >> > >> > |