Re: [Linuxwacom-discuss] Getting started

[Chris P. <chr...@ma...>]

Hi John,

I am sorry you are having so many problems.  I get lost every time I try 
to build from the wacom sources myself, there are so many steps and 
optional parts of the howto.  And I consider myself quite familiar with 
building and installing software the Unix way.

Your best bet is to play around with the configure options.  Type 
./configure --help to see them, and then page up to see the ones 
specific to linuxwacom.  As far as I know, you don't need to build your 
own usbhid.ko.  IIRC, it's not even possible under Debian using an 
unpatched linuxwacom since the kernel sources and build dirs are 
separate, and the linuxwacom configure doesn't expect that.

Also make sure to read the warning messages output by configure.

# ./configure --enable-wacom --disable-modver --enable-tabletdev

is the command I have in my bash history, and I get:

----------------------------------------
   BUILD ENVIRONMENT:
        architecture - i686
        linux kernel - yes 2.6.11
   module versioning - no
       kernel source - yes /lib/modules/2.6.12-1-686/build
            Xorg SDK - no /root/linuxwacom-0.7.2
           XSERVER64 - no
            dlloader - yes
                XLib - yes /usr/X11R6/lib
                 TCL - yes /usr/include/tcl8.4/
                  TK - yes /usr/include/tcl8.4/
             ncurses - yes

   BUILD OPTIONS:
             wacom.o - yes
             wacdump - yes
              xidump - yes
         libwacomcfg - yes
          libwacomxi - yes
           xsetwacom - yes
               hid.o - no
          usbmouse.o - no
             evdev.o - no
          mousedev.o - no
             input.o - no
         tabletdev.o - yes
        wacom_drv.so - no
         wacom_drv.o - no


That is for a Debian 2.6.12 kernel.  I don't know if the 
--enable-tabletdev is necessary.  I also had to copy over the wacom_drv 
to the Xorg dir, change my xorg.conf, and I usually have to do the 
rmmod/modprobe usbhid/wacom dance even once I'm into X in order for the 
tablet to work.  System logs and event reporters are your friends:

# less /proc/bus/usb/devices
# wacdump /dev/input/wacom
# less /var/log/messages
# grep -i wacom /var/log/messages
# dmesg
# dmesg | grep -i wacom
# less /var/log/Xorg.0.log
# grep -i wacom /var/log/Xorg.0.log

If you can document a step-by-step process of what you do (put it in a 
text file), and then attach the whole thing to the list or put it on a 
website, somebody is going to be able to help you.  But without 
extremely verbose and tedious descriptions of what you are doing, it's 
difficult to see where the problem is.

Cheers,
Chris

John ff wrote:
> I am fairly sure that I copied wacom_drv.o from the linuxwacom-0.7.2/prebuilt
> directory to /usr/X11R6/lib/modules/input/ but cannot prove that now as I am
> part way to restoration.
> 
> My plan today is to try to install on this machine (Pentium Centrino laptop)
> from scratch again.
> So more later today.
> 
> Currently stuck on
> 
>   Building modules, stage 2.
>   MODPOST
> *** Warning: "hid_find_field_by_usage"
> [/home/jpff/System/linuxwacom-0.7.2/src/2.6.11/usbhid.ko] undefined!
> 
> Indeed it is used but not defined in src/2.6.11/pid.c, although it is
> defined in 2.6.13 and 14 in hid-core.c
> 
> ==John ff
> --
> View this message in context: http://www.nabble.com/Getting-started-t1174681.html#a3259015
> Sent from the linuxwacom-discuss forum at Nabble.com.
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Linuxwacom-discuss mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>