Page 29 of 88 FirstFirst ... 1927282930313979 ... LastLast
Results 281 to 290 of 874

Thread: New Wacom Bamboo not working

  1. #281
    Join Date
    Apr 2007
    Location
    Mount Horeb, WI
    Beans
    4,312
    Distro
    Kubuntu Development Release

    Re: New Wacom Bamboo not working

    Quote Originally Posted by johnny2k View Post
    I had to reinstall the driver that was patched with that because I was using your new patch and I attached it so it wouldn't take up so much space.
    I think that you might have used the wcm_patch instead of the wcm2_patch. The information in this patch was using the old code so it reported your information as a mouse movement.

    If we are able to get a good reading with the wcm2_patch, I will remove the original wcm_patch because it might have run its life. Sorry for the confusion.

  2. #282
    Join Date
    Oct 2009
    Location
    Quebec city, Quebec
    Beans
    75
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: New Wacom Bamboo not working

    Quote Originally Posted by Ayuthia View Post
    I am glad that the patch is starting to work!

    Has xxd always worked with wacom /dev/input/eventX entries? I know that mine is usually blocked off from reading.

    Once again, I have updated the wcm2_patch in hopes to get all of the data that is coming in. I found that the way that I was finding the length of the data was incorrect. I am trying to use a different version that one of the other functions is using so hopefully it will work. If it doesn't, there is a possibility that the driver will crash. This patch is also trying out a version value that is based on ehfortin's suggestion.

    So basically, this patch is mainly for trying to find out the touch and button codes. If you want to try out the more stable changes, you can now use the wcm_working_patch.tar.bz2 file instead. The location for the patches are located here.
    Hi Ayuthia,

    I've implemented the latest code (not the working bundle). I'm including the log below. However, I would say I'm still not seeing any log from the touch part of this tablet. Let me know if you see something from the logs.

    If you look at this extract from the log, you will see that there is two ID/addresses/devices that respond each time I'm connecting the tablet (or that the boot process would recognize if already connected). I'm always under the impression that we only see one of the two.

    Code:
    Oct 22 20:49:52 efortin-laptop kernel: [  480.290710] input: Wacom Bamboo P&T 6x8 as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.0/input/input15
    Oct 22 20:49:52 efortin-laptop kernel: [  480.309412] input: Wacom Bamboo P&T 6x8 as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.1/input/input16
    For these current input15 and input16, the xinput --list is giving me 3 different id (2,8 and 9). I'm not sure why (it's the first time I'm noticing this). I would think the id=2 is coming from xorg.conf that is recognized when X start. The other id are what I'm used to see.

    Code:
    "Wacom Bamboo P&T 6x8"    id=2    [XExtensionKeyboard]
        Type is Wacom Stylus
        Num_keys is 248
        Min_keycode is 8
        Max_keycode is 255
        Num_buttons is 5
        Num_axes is 6
        Mode is Absolute
        Motion_buffer is 256
        Axis 0 :
            Min_value is 0
            Max_value is 21648
            Resolution is 2540
        Axis 1 :
            Min_value is 0
            Max_value is 13530
            Resolution is 2540
        Axis 2 :
            Min_value is 0
            Max_value is 1023
            Resolution is 1
        Axis 3 :
            Min_value is -64
            Max_value is 63
            Resolution is 1
        Axis 4 :
            Min_value is -64
            Max_value is 63
            Resolution is 1
        Axis 5 :
            Min_value is 0
            Max_value is 1023
            Resolution is 1
    "Wacom Bamboo P&T 6x8"    id=8    [XExtensionKeyboard]
        Type is Wacom Stylus
        Num_keys is 248
        Min_keycode is 8
        Max_keycode is 255
        Num_buttons is 5
        Num_axes is 6
        Mode is Absolute
        Motion_buffer is 256
        Axis 0 :
            Min_value is 0
            Max_value is 21648
            Resolution is 2540
        Axis 1 :
            Min_value is 0
            Max_value is 13530
            Resolution is 2540
        Axis 2 :
            Min_value is 0
            Max_value is 1023
            Resolution is 1
        Axis 3 :
            Min_value is -64
            Max_value is 63
            Resolution is 1
        Axis 4 :
            Min_value is -64
            Max_value is 63
            Resolution is 1
        Axis 5 :
            Min_value is 0
            Max_value is 1023
            Resolution is 1
    "Wacom Bamboo P&T 6x8"    id=9    [XExtensionKeyboard]
        Type is Wacom Stylus
        Num_keys is 248
        Min_keycode is 8
        Max_keycode is 255
        Num_buttons is 5
        Num_axes is 6
        Mode is Absolute
        Motion_buffer is 256
        Axis 0 :
            Min_value is 0
            Max_value is 21648
            Resolution is 2540
        Axis 1 :
            Min_value is 0
            Max_value is 13530
            Resolution is 2540
        Axis 2 :
            Min_value is 0
            Max_value is 1023
            Resolution is 1
        Axis 3 :
            Min_value is -64
            Max_value is 63
            Resolution is 1
        Axis 4 :
            Min_value is -64
            Max_value is 63
            Resolution is 1
        Axis 5 :
            Min_value is 0
            Max_value is 1023
            Resolution is 1
    How can I make sure that both "devices" that are recognized are returning some data? I know the tablet work as Windows recognized both area so it is only a matter of figuring why it seems that only one of the multiple personality this tablet has is generating logs. Any idea?

    Thanks

    ehfortin

    PS:
    As per this output (more /proc/bus/input/devices), we see that the stylus is using event7/mouse2 while the touch section is using event9/mouse3. I'm however unable to do xxd on the touch (or I should say it is not returning anything).

    Code:
    N: Name="Wacom Bamboo P&T 6x8"
    P: Phys=
    S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.0/input/input15
    U: Uniq=
    H: Handlers=mouse2 event7 
    B: EV=1f
    B: KEY=1c63 0 70033 0 0 0 0 0 0 0 0
    B: REL=100
    B: ABS=100 3000103
    B: MSC=1
    
    I: Bus=0003 Vendor=056a Product=00d3 Version=0106
    N: Name="Wacom Bamboo P&T 6x8"
    P: Phys=
    S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.1/input/input16
    U: Uniq=
    H: Handlers=mouse3 event9 
    B: EV=1f
    B: KEY=1c63 0 70033 0 0 0 0 0 0 0 0
    B: REL=100
    B: ABS=100 3000103
    B: MSC=1
    Attached Files Attached Files
    Last edited by ehfortin; October 23rd, 2009 at 02:16 AM. Reason: added information

  3. #283
    Join Date
    Apr 2007
    Location
    Mount Horeb, WI
    Beans
    4,312
    Distro
    Kubuntu Development Release

    Re: New Wacom Bamboo not working

    Quote Originally Posted by ehfortin View Post
    How can I make sure that both "devices" that are recognized are returning some data? I know the tablet work as Windows recognized both area so it is only a matter of figuring why it seems that only one of the multiple personality this tablet has is generating logs. Any idea?
    It might be just as simple as adding the touch as another input device in the .fdi or xorg.conf file and setting the device to point to that other event. If you are not for sure about what I am saying, you can attach your current configuration file and we can help create the touch device.

  4. #284
    Join Date
    Oct 2009
    Location
    Quebec city, Quebec
    Beans
    75
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: New Wacom Bamboo not working

    Quote Originally Posted by Ayuthia View Post
    It might be just as simple as adding the touch as another input device in the .fdi or xorg.conf file and setting the device to point to that other event. If you are not for sure about what I am saying, you can attach your current configuration file and we can help create the touch device.
    I just tried this with xorg.conf (as was not figuring how to do it in .fdi as I'm not sure how the file is evaluated). I've added the following:

    Code:
    Section "InputDevice"
        Identifier    "Wacom Touch"
        Driver        "wacom"
        Option        "Device" "/dev/input/wacom-touch"
        Option        "Type"    "touch"
        Option        "DebugLevel"    "12"
        Option        "commonDBG"    "3"
        Option        "USB"    "on"
    EndSection
    
    and added     InputDevice    "Wacom Touch" "SendCoreEvents" in the ServerLayout area.
    And this is the related part in Xorg.0.log:

    Code:
    (**) Option "SendCoreEvents"
    (**) Wacom Touch: always reports core events
    (**) Wacom Touch device is /dev/input/wacom-touch
    (**) Option "DebugLevel" "12"
    (**) WACOM: Wacom Touch debug level set to 12
    (**) Option "CommonDBG" "3"
    (**) WACOM: Wacom Touch tablet common debug level set to 3
    (**) Wacom Touch is in absolute mode
    (**) WACOM: suppress value is 2
    (**) Option "USB" "on"
    (**) Wacom Touch: reading USB link
    (**) Option "BaudRate" "9600"
    (II) XINPUT: Adding extended input device "Wacom Touch" (type: Wacom Touch)
    BEGIN xf86WcmProc dev=0xb3e50e0 priv=0xb3d9860 type=eraser(Wacom Touch) flags=16
    642 fd=-1 what=INIT
    xf86WcmDevOpen
    opening /dev/input/wacom-touch
    (**) Option "Device" "/dev/input/wacom-touch"
    usbDetect
    Wacom Touch Wacom X driver grabbed event device
    initializing USB tablet
    WACOM: touch max value(s) was wrong MaxTouchY = 0 MaxTouchY = 0.
    Failed to open device (fd=-1)
    xf86WcmProc INIT FAILED
    (EE) Couldn't init device "Wacom Touch"
    xf86WcmUninit
    (II) UnloadModule: "wacom"
    I'm not sure my modif in xorg.conf is fine but... it seems to load something which generate an error because of incorrect MaxTouchY. BTW, I have no idea where the "eraser" type is coming from. Is the touch area considered like a "eraser"?

    Let me know if I did something wrong with the xorg.conf.

    ehfortin

  5. #285
    Join Date
    Feb 2006
    Beans
    16

    Re: New Wacom Bamboo not working

    Ayuthia

    Doh.. that was an old log./ Sorry. I got the one you want right here.
    Attached Files Attached Files

  6. #286
    Join Date
    Apr 2007
    Location
    Mount Horeb, WI
    Beans
    4,312
    Distro
    Kubuntu Development Release

    Re: New Wacom Bamboo not working

    Quote Originally Posted by ehfortin View Post
    I just tried this with xorg.conf (as was not figuring how to do it in .fdi as I'm not sure how the file is evaluated). I've added the following:

    Code:
    Section "InputDevice"
        Identifier    "Wacom Touch"
        Driver        "wacom"
        Option        "Device" "/dev/input/wacom-touch"
        Option        "Type"    "touch"
        Option        "DebugLevel"    "12"
        Option        "commonDBG"    "3"
        Option        "USB"    "on"
    EndSection
    
    and added     InputDevice    "Wacom Touch" "SendCoreEvents" in the ServerLayout area.
    And this is the related part in Xorg.0.log:

    Code:
    (**) Option "SendCoreEvents"
    (**) Wacom Touch: always reports core events
    (**) Wacom Touch device is /dev/input/wacom-touch
    (**) Option "DebugLevel" "12"
    (**) WACOM: Wacom Touch debug level set to 12
    (**) Option "CommonDBG" "3"
    (**) WACOM: Wacom Touch tablet common debug level set to 3
    (**) Wacom Touch is in absolute mode
    (**) WACOM: suppress value is 2
    (**) Option "USB" "on"
    (**) Wacom Touch: reading USB link
    (**) Option "BaudRate" "9600"
    (II) XINPUT: Adding extended input device "Wacom Touch" (type: Wacom Touch)
    BEGIN xf86WcmProc dev=0xb3e50e0 priv=0xb3d9860 type=eraser(Wacom Touch) flags=16
    642 fd=-1 what=INIT
    xf86WcmDevOpen
    opening /dev/input/wacom-touch
    (**) Option "Device" "/dev/input/wacom-touch"
    usbDetect
    Wacom Touch Wacom X driver grabbed event device
    initializing USB tablet
    WACOM: touch max value(s) was wrong MaxTouchY = 0 MaxTouchY = 0.
    Failed to open device (fd=-1)
    xf86WcmProc INIT FAILED
    (EE) Couldn't init device "Wacom Touch"
    xf86WcmUninit
    (II) UnloadModule: "wacom"
    I'm not sure my modif in xorg.conf is fine but... it seems to load something which generate an error because of incorrect MaxTouchY. BTW, I have no idea where the "eraser" type is coming from. Is the touch area considered like a "eraser"?

    Let me know if I did something wrong with the xorg.conf.

    ehfortin
    This looks correct. Have you checked to see if you are getting any data from wacom-touch? If so, can you post it? Also check and see if the touch works along with the pen with it. If it does, you can try to point the stylus to the wacom-touch and have the touch also point to the wacom-touch.

    My N-Trig device had two events at one point, but one of them did not produce any data. The other thing that we found is that we received that same error message if we tried to assign the touch without the stylus.

  7. #287
    Join Date
    Oct 2009
    Location
    Quebec city, Quebec
    Beans
    75
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: New Wacom Bamboo not working

    Quote Originally Posted by Ayuthia View Post
    This looks correct. Have you checked to see if you are getting any data from wacom-touch? If so, can you post it? Also check and see if the touch works along with the pen with it. If it does, you can try to point the stylus to the wacom-touch and have the touch also point to the wacom-touch.

    My N-Trig device had two events at one point, but one of them did not produce any data. The other thing that we found is that we received that same error message if we tried to assign the touch without the stylus.
    I'm not sure I'm following you. As the log is saying the module was unloaded, there is no additional log that is showing from the touch mode. My stylus is still working fine (it is also defined in the xorg.conf in the same way but with a stylus type and another device name).

    I can try to load the stylus type on the touch device to see if it change something. I doubt that's what you are talking about however.

    ehfortin

  8. #288
    Join Date
    Apr 2007
    Location
    Mount Horeb, WI
    Beans
    4,312
    Distro
    Kubuntu Development Release

    Re: New Wacom Bamboo not working

    Quote Originally Posted by ehfortin View Post
    I'm not sure I'm following you. As the log is saying the module was unloaded, there is no additional log that is showing from the touch mode. My stylus is still working fine (it is also defined in the xorg.conf in the same way but with a stylus type and another device name).

    I can try to load the stylus type on the touch device to see if it change something. I doubt that's what you are talking about however.

    ehfortin
    What I was thinking is that event7 exists currently but for some reason the wacom xorg module cannot use it. I was wondering if you are still able to receive any data from /dev/input/event7:
    Code:
    sudo hexdump /dev/input/event7
    If so, does it work with the pen and the finger?

    If it does work for either one, you might try to set up the stylus on event7 and see what happens. So, yes, it is sorta what I am looking for.

  9. #289
    Join Date
    Apr 2007
    Location
    Mount Horeb, WI
    Beans
    4,312
    Distro
    Kubuntu Development Release

    Re: New Wacom Bamboo not working

    Post 144 has now been updated again. wcm_patch.tar.bz2 has been removed because we have a working patch so wcm_working_patch.tar.bz2 replaces it.

    wcm2_patch might fix the scrolling issue. I am thinking that there was an entry in the pad section that was calling the mouse wheel accidentally so I have removed it. The patch also makes its own function for the input_dev section in wacom_sys.c so now there are two additional patches in wcm2_patch so make sure that you use all the patches in the folder. The purpose for the new function is to try and see if we can get some other buttons recognized. I am not for sure if it is needed or not yet though.

  10. #290
    Join Date
    Jan 2008
    Location
    Romania, Eastern Europe
    Beans
    74
    Distro
    Kubuntu 10.04 Lucid Lynx

    Re: New Wacom Bamboo not working

    Could you make the post containing the driver patch and the 10-linuxwacom.fdi/xorg.conf files sticky? Or rather ask a forum admin to do so?

    I've been away for a few days and I've lost track of the discussion.
    UPDATE: I didn't see the latest post from Ayuthia:
    Post 144 has now been updated again
    Now I'm reading "How to get help on Linux forums". Please join me.

Page 29 of 88 FirstFirst ... 1927282930313979 ... LastLast

Tags for this Thread

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
  •