I'm sorry, I re-read this morning what I wrote yesterday and realized it
doesn't make any sense for anyone that is not used to CLFS. Here are the
./configure options again, in a clearer way:
For the 32-bit:
CC="gcc -m32" CXX="g++ -m32"
PKG_CONFIG_PATH="/usr/lib/pkgconfig:/opt/firefox-2.0.0.4/lib/pkgconfig"
USE_ARCH=32 ./configure --prefix=/usr --x-libraries=/usr/lib
--build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --disable-xserver64
--enable-dlloader --with-arch=32 --with-xlib=/usr/lib --enable-wacom
For the 64-bit:
CC="gcc -m64" CXX="g++ -m64"
PKG_CONFIG_PATH="/usr/lib64/pkgconfig:/opt/firefox-2.0.0.4/lib64/pkgconfig"
USE_ARCH=64 ./configure --prefix=/usr --libdir=/usr/lib64
--x-libraries=/usr/lib64 --enable-xserver64 --enable-dlloader
--with-arch=64 --with-xlib=/usr/lib64 --enable-wacom
I am not sure if the --enable-dlloader option is used correctly, but I
assumed that, since it creates a .so module, and all my modules from Xorg
are ending in .so, it is the right option.
For the record, I use linuxwacom-7.8, Xorg 7.2, kernel 2.6.21.5, my 32-bit
libraries for X (and all other programs) are in /usr/lib and the 64-bit
libraries in /usr/lib64. I have TK and TCL installed.
The compilation went fine but I did not replace the kernel module with the
new version found in src/2.6.19, since I wanted to test it that way (I
figured from one of your posts that the only thing missing from my kernel
would be the Bamboo support). Doing modprobe wacom gives these lines in
the /var/log/messages, which I understand, reading from the documentation,
means the input system is controlling the tablet, rather then the wacom
module?
usbcore: registered new interface driver wacom
drivers/usb/input/wacom_sys.c: v1.46:USB Wacom Graphire and Wacom Intuos
tablet driver
I did try to pay more attention to the documentation, but I found no
suggestions for what to do when the input system controls the tablet.
Rebuilding HID-core and the rest using the old code found in
linuxwacom-7.8 did not sound safe to me, so I wanted your advice on this
before.
When I start Xorg, it loads the module, but the tablet is not detecting
the values for the tablet's surface:
(II) LoadModule: "wacom"
(II) Loading /usr/lib64/xorg/modules/input//wacom_drv.so
(II) Module wacom: vendor="X.Org Foundation"
compiled for 4.3.99.902, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.7
(II) Wacom driver level: 47-0.7.8 $
...
(**) stylus device is /dev/input/wacom
(**) stylus is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) stylus: reading USB link
(**) Option "BaudRate" "9600"
(**) Option "SendCoreEvents"
(**) eraser: always reports core events
(**) eraser device is /dev/input/wacom
(**) eraser is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) eraser: reading USB link
(**) Option "BaudRate" "9600"
(**) Option "SendCoreEvents"
(**) cursor: always reports core events
(**) cursor device is /dev/input/wacom
(**) cursor is in relative mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) cursor: reading USB link
(**) Option "BaudRate" "9600"
(**) pad device is /dev/input/wacom
(**) pad is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) pad: reading USB link
(**) Option "BaudRate" "9600"
(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(**) Option "Device" "/dev/input/wacom"
stylus Wacom X driver grabbed event device
WACOM: unable to ioctl max values.
(**) Option "Device" "/dev/input/wacom"
eraser Wacom X driver grabbed event device
WACOM: unable to ioctl max values.
(**) Option "Device" "/dev/input/wacom"
cursor Wacom X driver grabbed event device
WACOM: unable to ioctl max values.
(**) Option "Device" "/dev/input/wacom"
pad Wacom X driver grabbed event device
WACOM: unable to ioctl max values.
WACOM: unable to ioctl max values.
(**) Option "Device" "/dev/input/wacom"
pad Wacom X driver grabbed event device
WACOM: unable to ioctl max values.
If I run wacdmp /dev/input/wacom, everything seems to work fine, pressure,
distance, tilt are detected, so are the changes of stylus/eraser/cursor,
but the tablet's mouse is not moving the mouse cursor on the screen - the
buttons work OK though.
If I unplug the tablet and restart Xorg, the tablet gets its right values
and the whole screen is mapped to the whole tablet surface - but xidump -u
raw stylus does not do anything (no output when hovering/touching the
stylus on the tablet). All the tablet's devices (stylus, eraser, cursor)
basically act as a mouse - except stylus and eraser are in absolute mode.
(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(**) Option "Device" "/dev/input/wacom"
stylus Wacom X driver grabbed event device
(==) Wacom using pressure threshold of 61 for button 1
(==) Wacom USB Intuos3 tablet speed=9600 maxX=60960 maxY=45720 maxZ=1023
resX=50
80 resY=5080 tilt=enabled
(==) Wacom device "stylus" top X=0 top Y=0 bottom X=60960 bottom Y=45720
(==) Wacom device "eraser" top X=0 top Y=0 bottom X=60960 bottom Y=45720
(==) Wacom device "cursor" top X=0 top Y=0 bottom X=60960 bottom Y=45720
(==) Wacom device "pad" top X=0 top Y=0 bottom X=60960 bottom Y=45720
In the documentation on your website, it says that if I am using kernel
2.6.18 or newer, the build of HID-core and other modules are not
necessary. In my kernel, they are built static, not as modules.
If you need more information and by chance have the time, I am often in
the IRC server chat.freenode.net, channel #cross-lfs, between 6 PM and 11
PM EST.
> Hello Ping,
>
> Thank you for your reply. I had read the page you mentioned, but I think
I
> was trying to tackle the "Linux problem" the wrong way. With a simple
32-bit system, things are less complicated.
>
> I went back to my CLFS instructions and looked through other
instructions
> I had and came up with this line. I assume it did what I hoped it would
do, since everything worked fine.
>
> For the 32-bit:
>
> CC="gcc ${BUILD32}" CXX="g++ ${BUILD32}"
> PKG_CONFIG_PATH="${PKG_CONFIG_PATH32}" USE_ARCH=32 ./configure
> --prefix=/usr --x-libraries=/usr/lib --build=i686-pc-linux-gnu
> --host=i686-pc-linux-gnu --disable-xserver64 --enable-dlloader
> --with-arch=32 --with-xlib=/usr/lib --enable-wacom
>
> For the 64-bit:
>
> CC="gcc ${BUILD64}" CXX="g++ ${BUILD64}"
> PKG_CONFIG_PATH="${PKG_CONFIG_PATH64}" USE_ARCH=64 ./configure
> --prefix=/usr --libdir=/usr/lib64 --x-libraries=/usr/lib64
> --enable-xserver64 --enable-dlloader --with-arch=64
--with-xlib=/usr/lib64
> --enable-wacom
>
> The only problem seems to be the kernel module did not get installed. I
see it build in the src/2.6.19 directory.I suppose this is because the
wacom kernel driver was not built as a module (or, in fact, at all)?
>
> I went back and configured it as a module in the kernel and just copied
the src/2.6.19/wacom.ko in the modules' directory, manually. Should I have
> rebuilt it?
>
>> Page http://linuxwacom.sourceforge.net/index.php/howto/config
>> describes the options used to configure the package, for both 32-bit
and
> 64-bit. By default, configure script will make a best guess for each
option unless you explicitly define it. If you only need to build for
your own system, a ./configure is good enough in most cases.
>> If you want to build across 32 and 64 systems, you definitely need
>> the --enable-xserver64=yes|no option. Another option you may need is
> --enable-dlloader=yes|no.
>> Anyway, please read the page again and let me know if there is
>> anything that is not clear to you.
>> Ping
>> On 6/21/07, Punkie <[EMAIL PROTECTED]> wrote:
>>> Hi everyone,
>>> Since my "distribution" is not a standard one (I'm using CLFS -
> http://cross-lfs.org/ - which means I have to build every package I want
>>> on my computer), I need to build the kernel and Xorg modules from
scratch.
>>> I am also running on a AMD 64 cpu, and try to provide both 32-bit and
> 64-bit libraries to programs which I cannot build using the 64-bit
architecture.
>>> The HOWTO document available on the website and inside the package is
not
>>> very clear on how to achieve these two tasks. There is also no
information
>>> on what packages are _required_ to build the software and which are
> optional.
>>> Have I missed any documentation that explains this task in simple
terms
> (easy for someone with good follow-instructions skills but not so good
development skills to follow)?
>>> For the information, I'm running Xorg 7.2 and kernel 2.6.21.5.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
