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/

Comments

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...

Qubes OS: First Impressions

A few days ago, while browsing security topics online, Qubes OS surfaced—whether via YouTube recommendations or search results, I can't recall precisely. Intrigued by its unique approach to security through compartmentalization, I delved into the documentation and watched some demos. My interest was piqued enough that I felt compelled to install it and give it a try firsthand. My overall first impression of Qubes OS is highly positive. Had I discovered it earlier, I might have reconsidered starting my hardware password manager project. Conceptually, Qubes OS is not much different from running a bunch of virtual machines simultaneously. However, its brilliance lies in the seamless desktop integration and the well-designed template system, making it far more user-friendly than a manual VM setup. I was particularly impressed by the concept of disposable VMs for temporary tasks and the clear separation of critical functions like networking (sys-net) and USB handling (sys-usb) into the...

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...