Page 23 of 34 FirstFirst ... 13212223242533 ... LastLast
Results 221 to 230 of 340

Thread: Install Wizardpen driver for Iball tablet

  1. #221

    Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET

    Moved to T & T. Another Howto thread.
    Learning is not attained by chance, it must be sought for with ardor and attended to with diligence. Abigail Adams ( 1744 - 1818 ), 1780;

    My blog Poetry and More Free Ubuntu Magazine

  2. #222
    Join Date
    Apr 2011
    Beans
    1

    Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET

    hello, I'm new to ubuntu and i'm tryin to install my trust-5300 tablet. When i type the ./configure --with-xorg-module-dir=/usr/lib/xorg/modules
    make && sudo make install

    I get this..
    make all-recursive
    make[1]: Entering directory `/home/janani/Desktop/xorg-input-wizardpen-0.3.8.0'
    Making all in src
    make[2]: Entering directory `/home/janani/Desktop/xorg-input-wizardpen-0.3.8.0/src'
    /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 -I../src -MT wizardpen.lo -MD -MP -MF .deps/wizardpen.Tpo -c -o wizardpen.lo wizardpen.c
    libtool: Version mismatch error. This is libtool 2.2.6 Debian-2.2.6a-4, but the
    libtool: definition of this LT_INIT comes from libtool 2.2.6b.
    libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6 Debian-2.2.6a-4
    libtool: and run autoconf again.
    make[2]: *** [wizardpen.lo] Error 63
    make[2]: Leaving directory `/home/janani/Desktop/xorg-input-wizardpen-0.3.8.0/src'
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory `/home/janani/Desktop/xorg-input-wizardpen-0.3.8.0'
    make: *** [all] Error 2

    What am I doing wrong?

  3. #223
    Join Date
    Nov 2008
    Beans
    9,635
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET

    Hi Ethcelon,

    Welcome to Ubuntu forums!

    You don't mention what release of Ubuntu you are using. Is that because you're on a Debian release? I don't recognize that version of the WizardPen driver. Where did you get it from? You should be able to use DoctorMO's PPA: https://launchpad.net/~doctormo/+archive/xorg-wizardpen

    The error seems to be from a xorg-macros mismatch. For example the version is 1.5 in Lucid and some drivers now need version 1.8. In Ubuntu though the macros are in the xutils-dev package, so I'm not sure. You can get 1.8 directly from Xorg: http://xorg.freedesktop.org/releases...-1.8.0.tar.bz2 If you use the:
    Code:
    ./configure --prefix=/usr
    flag when you compile it will install the macros in the correct /usr/share/aclocal/xorg-macros.m4 directory.

    I suppose it could just be a libtool mismatch so maybe try this first:
    Code:
    sudo apt-get update
    
    sudo apt-get install libtool
    
    sudo apt-get upgrade

  4. #224
    Join Date
    Apr 2011
    Beans
    1

    Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET

    Hi Ethcelon

    I’m under Debian Testing and, since the kernel was updated, I had to rebuild that driver… And I just run into the same error !

    In fact, it seems the default configure script (built under ubuntu I guess) is not compatible with debian’s autotools version, so you just have to rebuild it by running
    Code:
    ./autogen.sh
    (and then the standard make && su make install…).

    However, I wonder why you stick to 0.3.8 ? I used 0.8.0 (trunk version), but you could at least use stable 0.7.4 !

  5. #225
    Join Date
    Apr 2008
    Beans
    1

    Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET

    Hi!

    I'm trying to make my Genius's EasyPen i405 work on my lucid 10.04 system. while trying:
    ./configure --with-xorg-module-dir=/usr/lib/xorg/modules make && sudo make install

    I get the following:

    ---configure: WARNING: you should use --build, --host, --target
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for a thread-safe mkdir -p... /bin/mkdir -p
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking whether to enable maintainer-specific portions of Makefiles... no
    checking build system type... Invalid configuration `make': machine `make' not recognized
    configure: error: /bin/bash ./config.sub make failed

    (o:
    I tried to reinstall the build-essential package but it didn't help.

    Any idea would be greatly appricieted..

  6. #226
    Join Date
    May 2011
    Beans
    2

    Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET

    anybody here running natty,having a tablet with bundled mouse that works as good as the stylus? if yes can you please post config files (xorg.conf.d and udev/rules.d)

  7. #227
    Join Date
    Oct 2007
    Location
    Todd Mission Texas
    Beans
    427
    Distro
    Ubuntu Gnome 14.04 Trusty Tahr

    Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET

    Message deleted because it became irrelevant. I found pre-compiled drivers. My Digipro WP8060 drawing tablet works.
    Last edited by Silvernail; July 19th, 2011 at 03:53 AM.
    "Let us run the risk of wearing out rather than rusting out." __Theodore Roosevelt

  8. #228
    Join Date
    Oct 2007
    Location
    Todd Mission Texas
    Beans
    427
    Distro
    Ubuntu Gnome 14.04 Trusty Tahr

    Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET

    Works out of the box with Gimp, Pencil, Open Office Drawing, Agave, Inkscape, Krita, and Ktoon. No go on Blender, Scribus, but that may be just a configuration problem.
    "Let us run the risk of wearing out rather than rusting out." __Theodore Roosevelt

  9. #229
    Join Date
    Aug 2011
    Beans
    23

    Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET

    Hi everybody,

    I am trying to install a Genius EasyPen i405x on Ubuntu 10.4. Control of the position of the cursor is working fine, but the action of pressing with the pen on the tablet does not do what I would like it to. For instance, I cannot draw with gimp, pressure does nothing at all. Yet, under certain circumstances pressure does have an effect. For instance, I can use pressure to open the "System" menu usually appearing on the top of Ubuntu desktop, I can open Gimp, click on "File > Open" using pressure. But then things stop to work, I cannot click OK (although pressure "highlights" the button I want to click on), and then nothing happens when I try to draw something.

    Under firefox, pressure has the effect of the "go back" button (while some button of the pen does the "go forward" button).

    So my problem is this: how can I have my computer understand what I mean when I press on the tablet with the pen ?

    I followed instructions from https://help.ubuntu.com/community/TabletSetupWizardpen, using "method 1" to install the driver. I think that driver installation went well, since
    Code:
    ls /usr/lib/xorg/modules/input/wizardpen_drv.*
    gives what it should.

    Then I messed up /usr/lib/X11/xorg.conf.d/70-wizardpen.conf, which at first looked like this :
    Code:
    Section "InputClass"
       Identifier "wizardpen"
       MatchIsTablet "on"
       MatchDevicePath "/dev/input/event*"
       MatchVendor "UC-LOGIC|KYE Systems|Ace Cad"
       Driver "wizardpen"
    EndSection
    Section "InputClass"
       Identifier "wizardpen ignore mouse dev"
       MatchIsTablet "on"
       MatchDevicePath "/dev/input/mouse*"
       MatchVendor "UC-LOGIC|KYE Systems|Ace Cad"
       Driver ""
    EndSection
    to which i tried to add various things, ending up with something like this
    Code:
    Section "InputClass"
       Identifier "wizardpen"
       MatchIsTablet "on"
       MatchDevicePath "/dev/input/by-id/usb-Genius_EasyPen_i405X-event-mouse"
       MatchVendor "UC-LOGIC|KYE Systems|Ace Cad"
       Driver "wizardpen"
       Option "SendCoreEvents" "true"
       Option "TopX" "2199"
       Option "TopY" "3598"
       Option "BottomX" "30325"
       Option "BottomY" "29278"
       Option "TopZ" "10"
       Option "BottomZ" "1023"
    EndSection
    Section "InputClass"
       Identifier "wizardpen ignore mouse dev"
       MatchIsTablet "on"
       MatchDevicePath "/dev/input/by-id/usb-Genius_EasyPen_i405X-mouse"
       MatchVendor "UC-LOGIC|KYE Systems|Ace Cad"
       Driver ""
    EndSection
    But it did not change anything. I also tried to create some .fdi file in /etc/hal/fdi/policy/, but if I understood correctly what people said here, I should not do this with my Ubuntu 10.4. In any case, it didn't work either.

    So I'm coming short of ideas to solve the problem... Any sugestions ?

    Maybe a look at the end of my /var/log/Xorg.0.log may help people :
    Code:
    (II) config/udev: Adding input device HDA Intel Headphone (/dev/input/event11)
    (II) No input driver/identifier specified (ignoring)
    (II) config/udev: Adding input device HDA Intel Mic (/dev/input/event12)
    (II) No input driver/identifier specified (ignoring)
    (II) config/udev: Adding input device HDA Intel Mic (/dev/input/event13)
    (II) No input driver/identifier specified (ignoring)
    (II) config/udev: Adding input device HDA Intel Headphone (/dev/input/event14)
    (II) No input driver/identifier specified (ignoring)
    (II) config/udev: Adding input device Genius EasyPen i405X (/dev/input/event6)
    (**) Genius EasyPen i405X: Applying InputClass "evdev pointer catchall"
    (**) Genius EasyPen i405X: Applying InputClass "evdev keyboard catchall"
    (**) Genius EasyPen i405X: Applying InputClass "evdev tablet catchall"
    (**) Genius EasyPen i405X: always reports core events
    (**) Genius EasyPen i405X: Device: "/dev/input/event6"
    (II) Genius EasyPen i405X: Found 10 mouse buttons
    (II) Genius EasyPen i405X: Found scroll wheel(s)
    (II) Genius EasyPen i405X: Found relative axes
    (II) Genius EasyPen i405X: Found x and y relative axes
    (II) Genius EasyPen i405X: Found absolute axes
    (II) Genius EasyPen i405X: Found x and y absolute axes
    (II) Genius EasyPen i405X: Found absolute tablet.
    (II) Genius EasyPen i405X: Found keys
    (II) Genius EasyPen i405X: Configuring as tablet
    (II) Genius EasyPen i405X: Configuring as keyboard
    (**) Genius EasyPen i405X: YAxisMapping: buttons 4 and 5
    (**) Genius EasyPen i405X: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Genius EasyPen i405X" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "pc105"
    (**) Option "xkb_layout" "ch"
    (**) Option "xkb_variant" "fr"
    (**) Option "xkb_options" "grp:alts_toggle"
    (WW) Genius EasyPen i405X: touchpads, tablets and touchscreens ignore relative axes.
    (II) Genius EasyPen i405X: initialized for absolute axes.
    (II) config/udev: Adding input device Genius EasyPen i405X (/dev/input/mouse1)
    (II) No input driver/identifier specified (ignoring)
    (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event4)
    (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    (**) AT Translated Set 2 keyboard: always reports core events
    (**) AT Translated Set 2 keyboard: Device: "/dev/input/event4"
    (II) AT Translated Set 2 keyboard: Found keys
    (II) AT Translated Set 2 keyboard: Configuring as keyboard
    (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "pc105"
    (**) Option "xkb_layout" "ch"
    (**) Option "xkb_variant" "fr"
    (**) Option "xkb_options" "grp:alts_toggle"
    (II) config/udev: Adding input device AlpsPS/2 ALPS DualPoint TouchPad (/dev/input/event10)
    (**) AlpsPS/2 ALPS DualPoint TouchPad: Applying InputClass "evdev pointer catchall"
    (**) AlpsPS/2 ALPS DualPoint TouchPad: Applying InputClass "evdev touchpad catchall"
    (**) AlpsPS/2 ALPS DualPoint TouchPad: Applying InputClass "touchpad catchall"
    (II) LoadModule: "synaptics"
    (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    (II) Module synaptics: vendor="X.Org Foundation"
        compiled for 1.7.6, module version = 1.2.2
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 7.0
    (II) Synaptics touchpad driver version 1.2.2
    (**) Option "Device" "/dev/input/event10"
    (II) AlpsPS/2 ALPS DualPoint TouchPad: x-axis range 0 - 1023
    (II) AlpsPS/2 ALPS DualPoint TouchPad: y-axis range 0 - 767
    (II) AlpsPS/2 ALPS DualPoint TouchPad: pressure range 0 - 127
    (II) AlpsPS/2 ALPS DualPoint TouchPad: finger width range 0 - 0
    (II) AlpsPS/2 ALPS DualPoint TouchPad: buttons: left right middle
    (--) AlpsPS/2 ALPS DualPoint TouchPad: touchpad found
    (**) AlpsPS/2 ALPS DualPoint TouchPad: always reports core events
    (II) XINPUT: Adding extended input device "AlpsPS/2 ALPS DualPoint TouchPad" (type: TOUCHPAD)
    (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) keeping acceleration scheme 1
    (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration profile 0
    (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration factor: 2.000
    (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration threshold: 4
    (--) AlpsPS/2 ALPS DualPoint TouchPad: touchpad found
    (II) config/udev: Adding input device AlpsPS/2 ALPS DualPoint TouchPad (/dev/input/mouse3)
    (II) No input driver/identifier specified (ignoring)
    (II) config/udev: Adding input device DualPoint Stick (/dev/input/event9)
    (**) DualPoint Stick: Applying InputClass "evdev pointer catchall"
    (**) DualPoint Stick: always reports core events
    (**) DualPoint Stick: Device: "/dev/input/event9"
    (II) DualPoint Stick: Found 3 mouse buttons
    (II) DualPoint Stick: Found relative axes
    (II) DualPoint Stick: Found x and y relative axes
    (II) DualPoint Stick: Configuring as mouse
    (**) DualPoint Stick: YAxisMapping: buttons 4 and 5
    (**) DualPoint Stick: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "DualPoint Stick" (type: MOUSE)
    (II) DualPoint Stick: initialized for relative axes.
    (II) config/udev: Adding input device DualPoint Stick (/dev/input/mouse2)
    (II) No input driver/identifier specified (ignoring)
    (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event7)
    (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
    (**) ThinkPad Extra Buttons: always reports core events
    (**) ThinkPad Extra Buttons: Device: "/dev/input/event7"
    (II) ThinkPad Extra Buttons: Found keys
    (II) ThinkPad Extra Buttons: Configuring as keyboard
    (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "pc105"
    (**) Option "xkb_layout" "ch"
    (**) Option "xkb_variant" "fr"
    (**) Option "xkb_options" "grp:alts_toggle"
    (II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/event3)
    (**) Macintosh mouse button emulation: Applying InputClass "evdev pointer catchall"
    (**) Macintosh mouse button emulation: always reports core events
    (**) Macintosh mouse button emulation: Device: "/dev/input/event3"
    (II) Macintosh mouse button emulation: Found 3 mouse buttons
    (II) Macintosh mouse button emulation: Found relative axes
    (II) Macintosh mouse button emulation: Found x and y relative axes
    (II) Macintosh mouse button emulation: Configuring as mouse
    (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
    (**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
    (II) Macintosh mouse button emulation: initialized for relative axes.
    (II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/mouse0)
    (II) No input driver/identifier specified (ignoring)
    (II) intel(0): EDID vendor "LEN", prod id 16500
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1440x900"x0.0  102.00  1440 1488 1520 1836  900 903 909 926 -hsync -vsync (55.6 kHz)
    (II) intel(0): Modeline "1440x900"x0.0   85.00  1440 1488 1520 1836  900 903 909 926 -hsync -vsync (46.3 kHz)
    (II) intel(0): EDID vendor "LEN", prod id 16500
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1440x900"x0.0  102.00  1440 1488 1520 1836  900 903 909 926 -hsync -vsync (55.6 kHz)
    (II) intel(0): Modeline "1440x900"x0.0   85.00  1440 1488 1520 1836  900 903 909 926 -hsync -vsync (46.3 kHz)
    (II) intel(0): EDID vendor "LEN", prod id 16500
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1440x900"x0.0  102.00  1440 1488 1520 1836  900 903 909 926 -hsync -vsync (55.6 kHz)
    (II) intel(0): Modeline "1440x900"x0.0   85.00  1440 1488 1520 1836  900 903 909 926 -hsync -vsync (46.3 kHz)
    (II) intel(0): EDID vendor "LEN", prod id 16500
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1440x900"x0.0  102.00  1440 1488 1520 1836  900 903 909 926 -hsync -vsync (55.6 kHz)
    (II) intel(0): Modeline "1440x900"x0.0   85.00  1440 1488 1520 1836  900 903 909 926 -hsync -vsync (46.3 kHz)
    In case it helps, my computer is a laptop with touchpad and trackpoint.

    Many thanks for your help !

  10. #230
    Join Date
    Nov 2008
    Beans
    9,635
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET

    Hi random_jc,

    Welcome to Ubuntu forums!

    According to your Xorg.0.log the tablet hasn't been matched to the WizardPen X driver:
    Code:
    (II) config/udev: Adding input device Genius EasyPen i405X (/dev/input/event6)
    (**) Genius EasyPen i405X: Applying InputClass "evdev pointer catchall"
    (**) Genius EasyPen i405X: Applying InputClass "evdev keyboard catchall"
    (**) Genius EasyPen i405X: Applying InputClass "evdev tablet catchall"
    (**) Genius EasyPen i405X: always reports core events
    (**) Genius EasyPen i405X: Device: "/dev/input/event6"
    Instead it has been picked up by the evdev X driver, specifically the "evdev tablet catchall" snippet.

    Let's check your tablets vendor and product ID with:
    Code:
    lsusb
    in a terminal. Post the output line with the tablet in it. Let's also see what keywords xinput is seeing and if they are the problem with the match. Run this command in a terminal.
    Code:
    xinput list
    And post the output.

Page 23 of 34 FirstFirst ... 13212223242533 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •