Skip to main content

Linux 下绘图板配置

作为一个绘画爱好者，绘图板是必不可少的。 怎奈Linux下面绘图板时认时不认，压感也时支持时不支持。 今天终于下决心弄好它。

我的板子是Tooya Pro，USB版。 Linux下认成WALTOP International Corp. Slim Tablet
系统是Ubuntu 8.04

首先是要定位设备名，一种方法是找到绘图板是哪一个/dev/input/event*，这又有多种方法，一种是看dmesg，记住pci地址，然后去/dev/input/by-path找到对应的，再看其是哪个/dev/input/event*的symlink；另一种方法是用wacdump挨个测试/dev/input/event*。当然也可以二者结合使用。在我机器上绘图板是/dev/input/event2

由于我对/dev/input/event*命名不是很了解，所以担心改了配置后这个数值会变，于是再一个网页上学到了修改udev rules的方法，让它自动建立symlink。后来发现wacom就是这样做的。
具体方法是首先用lsusb等工具找到设备的idProduct和idVendor。 我的绘图板在lsusb下看是172f:0031
然后建立文件/etc/udev/rules.d/65-tablet.rules:
KERNEL=="event*", SYSFS{idProduct}=="0031", SYSFS{idVendor}=="172f", SYMLINK+="input/tablet"
这样以后会自动建立/dev/input/tablet到对应/dev/input/event*的symlink，很是方便。

下一步是需要确定板子的坐标范围（或许这步可以省略），主要是用wacdump看看板子左上角和右下角的坐标。后来我有参考了以下板子的说明书，得到坐标(0,0)-(10000,6250)

接着当然是修改xorg.conf （听说最新的Xorg对即插即用支持得很好，真希望不用老改这玩意儿了）
ServerLayout Section中加一句
InputDevice "stylus" "SendCoreEvents"
然后加一个InputDevice Section
Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/tablet"
Option "Mode" "Absolute"
Option "Type" "stylus"
Option "USB" "on"
Option "TopX" "0"
Option "TopY" "0"
Option "BottomX" "10000"
Option "BottomY" "6250"
Option "MaxX" "10000"
Option "MaxY" "6250"
EndSection

注意我只添加了一个stylus设备，eraser, pad之类的都不需要

最后，软件也得配置一下，比如Gimp。

按理说重启X就应该行了，可是我这里一定要重启系统，要不压感说什么都不认。

另外有个Gnome Graphics Tablet Apps，也有些帮助。

这样就完美了。


参考链接：
http://linuxwacom.sourceforge.net/index.php/howto/x11
http://littlethorpe.net/tptrn/article/72/aldis-low-cost-digitiser-tablet-in-linux
https://help.ubuntu.com/community/Wacom#fnref-ec6781974bf16fcc57d0d15e8186755fb5d1784c
https://help.ubuntu.com/community/WacomTroubleshooting
http://www.alexmac.cc/tablet-apps/
Labels:

Comments

Post a Comment

Popular posts from this blog

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...
3 comments
Read More »

Chasing an IO Phantom

My home server has been weird since months ago, it just becomes unresponsive occassionally. It is annoying but it happens only rarely, so normally I'd just wait or reboot it. But weeks ago I decided to get to the bottom of it. What's Wrong My system set up is: Root: SSD, LUKS + LVM + Ext4 Data: HDD, LUKS + ZFS 16GB RAM + 1GB swap Rootless dockerd The system may become unresponsive, when the IO on HDD  is persistantly high for a while. Also: Often kswapd0 has high CPU High IO on root fs (SSD) From dockerd and some containers RAM usage is high, swap usage is low It is very strange that IO on HDD can affect SSD. Note that when this happens, even stopping the IO on HDD does not always help. Usually restarting dockerd does not help, but rebooting helps. Investigation: Swap An obvious potential root cause is the swap. High CPU on kswapd0 usually means the free memory is low and the kernel is busy exchanging data between disk and swap. However, I tried the following steps, none of the...
Post a Comment
Read More »

Fix Google Security Code

Google Security Code (http://g.co/sc) is one type of 2-step verification. This is particularly useful when security keys and passkeys are not available. I have been using it in my LXC containers, until today I found out that it stopped working. It just kept saying "The code is invalid". It is easy to rule out some factors: The code works on other browsers on my laptop. The code works on other devices that are directly connected to the router. So it appears that Google also checks IP addresses besides the security code. Recently I have IPv6 enabled, so most devices that are directly connected to the router have both IPv4 and IPv6 addresses. But  I only enabled IPv4 for my LXC containers. So I guess when a code is generated by device A and used by device B, Google should be able to check that device A and device B are closely located. But in my case, IPv6 address appears on device A but not on device B, which may look suspicious. To fix the problem, I just needed to disable IPv...
Post a Comment
Read More »