Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

X fails to load FSC Buttons

Help
Tuvik
2010-12-21
2013-05-08
  • Tuvik
    Tuvik
    2010-12-21

    I've got a problem starting fscd. I read previous threads related to that, and tried everything suggested there, but to no avail.

    Everything used to work perfectly with old versions of X and  fjbtndrv, but at a certain point rotation stopped working. I still have a functioning stylus, eraser, etc., but I'm limited to landscape orientation.

    I'm running gentoo on T5010, with Xorg version 1.7.7, and fjbtndrv version 2.2.1 compiled from sources.
    Here's the output of fscd (debug enabled):

    $ fscd
    Found XInputExtension 2.2 extension (140, 0, 0)
    Found XTEST 2.2 extension (141, 0, 0)
    Found RANDR 2.2 extension (148, 0, 0)
    Found DPMS 2.2 extension (131, 0, 0)
    searching tablet buttons device …
    … device Virtual core pointer
    … device Virtual core keyboard
    … device Virtual core XTEST pointer
    … device Virtual core XTEST keyboard
    … device Synaptics Mouse
    … device Keyboard0
    … device USB Mouse
    … device stylus
    … device eraser
    … device cursor
    … device pad
    xinput device not found
    x11 initalisation failed

    In my Xorg.conf I have

    InputDevice     "FSC Tablet Buttons"

    in the ServerLayout section, and then

    Section "InputDevice"
            Identifier      "FSC Tablet Buttons"
            Driver          "evdev"
            Option          "Phys" "fsc/input0"
            Option          "SendCoreEvents" "true"
    EndSection

    I also have

    Option "AutoAddDevices" "false"

    in the ServerFlags section. Without it things seem to not work well.
    And here is some relevant output from Xorg.0.log:


    (**) Option "Device" "/dev/ttyS0"
    (**) Option "SendCoreEvents"
    (**) eraser: always reports core events
    (II) XINPUT: Adding extended input device "eraser" (type: ERASER)
    (-) eraser: top X=0 top Y=0 bottom X=28808 bottom Y=18080 resol X=2540 resol Y=
    2540
    (**) Option "Device" "/dev/ttyS0"
    (**) Option "SendCoreEvents"
    (**) cursor: always reports core events
    (II) XINPUT: Adding extended input device "cursor" (type: CURSOR)
    (-) cursor: top X=0 top Y=0 bottom X=28808 bottom Y=18080 resol X=2540 resol Y=2540
    (**) Option "Device" "/dev/ttyS0"
    (**) pad: always reports core events
    (II) XINPUT: Adding extended input device "pad" (type: PAD)
    (-) pad: top X=0 top Y=0 bottom X=28808 bottom Y=18080 resol X=2540 resol Y=2540
    (**) Option "SendCoreEvents" "true"
    (**) FSC Tablet Buttons: always reports core events
    (EE) FSC Tablet Buttons: No device specified.
    (II) UnloadModule: "evdev"
    (EE) PreInit returned NULL for "FSC Tablet Buttons"
    (II) config/hal: Adding input device fsc tablet switch
    (II) AutoAddDevices is off - not adding device.
    (EE) config/hal: NewInputDeviceRequest failed (8)
    (II) config/hal: Adding input device PnP Device (FUJ02e5)
    (II) AutoAddDevices is off - not adding device.
    (EE) config/hal: NewInputDeviceRequest failed (8)
    (II) config/hal: Adding input device SynPS/2 Synaptics TouchPad
    (II) AutoAddDevices is off - not adding device.
    (EE) config/hal: NewInputDeviceRequest failed (8)

    EVDEV is enabled in the kernel and the Xorg evdev driver loads correctly.

    Any idea what might be wrong, or at least what I should try next?

    Thanks in advance,
    Tuvik

     
  • Tuvik
    Tuvik
    2010-12-21

    I forgot to mention that the fsc_btns kernel modules loads correctly. All of the above refers to a state when the modules is loaded:

    $ lsmod
    Module                  Size  Used by
    bnep                    5932  2
    rfcomm                 25479  4
    fsc_btns                3264  0
    iwlagn                171320  0
    fujitsu_laptop         10646  0
    xfs                   555614  0
    exportfs                2458  1 xfs
    jfs                   154855  0
    raid456                42928  0
    async_raid6_recov        785  1 raid456
    async_memcpy             546  1 raid456
    async_pq                1436  1 raid456
    raid6_pq               77224  2 async_raid6_recov,async_pq
    async_xor                877  2 raid456,async_pq
    xor                    12933  1 async_xor
    async_tx                1141  5 raid456,async_raid6_recov,async_memcpy,async_pq,async_xor
    raid1                  16801  0
    raid0                   6859  0
    scsi_wait_scan           439  0
    sbp2                   15169  0

     
  • Robert Gerlach
    Robert Gerlach
    2010-12-21

    Hi,

    I think the problem is

    (EE) FSC Tablet Buttons: No device specified.
    

    Please try to specify the device directly. Is Phys still supported? It seems to be undocumented.

     
  • Indeed, that was the direct cause, but explicitly spacifying the device in xorg.conf had the strange effect of setting the buttons as a keyboard…

    xorg.conf section:

    Section "InputDevice"
            Identifier      "FSC Tablet Buttons"
            Driver          "evdev"
            #Option         "Phys" "fsc/input0"
            Option          "Device" "/dev/input/event12"
            Option          "SendCoreEvents" "true"
    EndSection

    Xorg.0.log:

    (**) FSC Tablet Buttons: always reports core events
    (**) FSC Tablet Buttons: Device: "/dev/input/event12"
    (II) FSC Tablet Buttons: Found keys
    (II) FSC Tablet Buttons: Configuring as keyboard
    (II) XINPUT: Adding extended input device "FSC Tablet Buttons" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us"

    Trying to start fscd still fails, claiming not to find the input device, though it is listed:

    Found XInputExtension 2.2 extension (140, 0, 0)
    Found XTEST 2.2 extension (141, 0, 0)
    Found RANDR 2.2 extension (148, 0, 0)
    Found DPMS 2.2 extension (131, 0, 0)
    searching tablet buttons device …
    … device Virtual core pointer
    … device Virtual core keyboard
    … device Virtual core XTEST pointer
    … device Virtual core XTEST keyboard
    … device Keyboard0
    … device Synaptics Mouse
    … device USB Mouse
    … device stylus
    … device eraser
    … device cursor
    … device pad
    … device FSC Tablet Buttons
    xinput device not found
    x11 initalisation failed

    As a side effect, my numeric keypad (including PgUp, PgDn and Del) no longer responds. Needless to say, the buttons don't operate as expected, but rather map to certain keyboard keys.

     
  • Robert Gerlach
    Robert Gerlach
    2010-12-21

    Please set Identifier to "fsc tablet buttons" and retry.

     
  • OK, there's progress!

    $ fscd
    Found XInputExtension 2.2 extension (140, 0, 0)
    Found XTEST 2.2 extension (141, 0, 0)
    Found RANDR 2.2 extension (148, 0, 0)
    Found DPMS 2.2 extension (131, 0, 0)
    searching tablet buttons device …
    … device Virtual core pointer
    … device Virtual core keyboard
    … device Virtual core XTEST pointer
    … device Virtual core XTEST keyboard
    … device Keyboard0
    … device Synaptics Mouse
    … device USB Mouse
    … device stylus
    … device eraser
    … device cursor
    … device pad
    … device fsc tablet buttons
    BadAccess (attempt to access private resource denied)
    BadAccess (attempt to access private resource denied)
    grab key XF86RotateWindows
    grab key SunVideoLowerBrightness
    BadAccess (attempt to access private resource denied)
    grab key SunVideoRaiseBrightness
    BadAccess (attempt to access private resource denied)
    BadName (named color or font does not exist)
    brightness: output=1 offset=0 max=7

    *** Please report bugs to http://fjbtndrv.sourceforge.net ***

    mapping keycode 186 to symbol XF86ScrollDown (0x1008ff79)
    mapping keycode 185 to symbol XF86ScrollUp (0x1008ff78)
    keycode 161 is ok.
    keycode 232 is ok.
    keycode 233 is ok.
    mapping keycode 186 to symbol Next (0x0000ff56)
    mapping keycode 185 to symbol Prior (0x0000ff55)

    The rotate button now actually rotates both the screen and the stylus, but two things are still not working as they should:
    1. My keyboard. The keypad is still lost, and now after playing with the rotate button and co. it seems to get stuck in Ctrl mode (playing with the buttons again freed it - I haven't tested to see which button it was exactly that caused this).
    2. When the screen rotates, the resolution isn't properly handled. It looks like I'm getting the same (landscape resolution) so part of the desktop is outside the screen, while the bottom of the screen is black.

    The Xork log still looks the same (except for the case of the buttons identifier), so I don't reattach it.