Problem with starting fscd

Help
2008-12-17
2013-05-08
  • Hi there,

    I'm trying to get my Fujitsu Siemens T4010 Buttons to work.
    I downloaded fjbtndrv, compiled and installed, without errors.

    But when trying to start fscd via Console an Error occurs:

    $sudo fscd
    x11 initalisation failed

    I'm sorry, but am new to Ubuntu an Linux in general, every help is welcome =)

    Thx

    Marius

     
    • Robert Gerlach
      Robert Gerlach
      2008-12-19

      > I downloaded fjbtndrv, compiled and installed, without errors.

      What version, 1.4 or 2?

      > $sudo fscd
      > x11 initalisation failed

      Try to start fscd without sudo.

        Robert

       
    • Version 2.0

       
    • Hello,

      i have the same problem with fjbtndrv-2.0-rc1. I'm in the group of users and i tested the split option in the fsc_btns.
      I have ubuntu 8.10 64bit.

       
      • Robert Gerlach
        Robert Gerlach
        2009-01-26

        Please rebuild with --enable-debug, start fscd and fscrotd from a xterm and send me the output. Thanks.

        robert

         
        • I'm having the same problem with fjbtndrv-2.0 on my T4010D. 

          I enabled debug and the output is as such:

          Found XInputExtension 2.2 extension (147, 0, 0)
          Found XTEST 2.2 extension (148, 0, 0)
          Found RANDR 2.2 extension (156, 0, 0)
          Found DPMS 2.2 extension (141, 0, 0)
          searching fsc_btns device ...
          ... device eraser
          ... device stylus
          ... device Keyboard0
          ... device Mouse0
          xinput device not found
          x11 initalisation failed

          I have loaded the fsc_btns module:
          # lsmod | grep fsc
          fsc_btns               10848  0

          However, if I make and instlal fscd-1,41, the fscd from that loads up fine (however, a lot of the keys don't work - the debug info reports for the brightness keys as an example:

          INPUT: key 224 pressed
          INPUT: unknown key, skipping
          LOOPY: time = 688092854, timeout = 1400
          LOOPY: time = 688092854, timeout = 1400
          INPUT: key 224 released
          INPUT: unknown key, skipping
          LOOPY: time = 688093004, timeout = 1400
          LOOPY: time = 688093004, timeout = 1400
          INPUT: key 225 pressed
          INPUT: unknown key, skipping
          LOOPY: time = 688093200, timeout = 1400
          LOOPY: time = 688093200, timeout = 1400
          INPUT: key 225 released
          INPUT: unknown key, skipping

          I would ideally like to get fjbtndrv working, but I seem to have an issue with fscd as well, when I am able to get it to run.  Any thoughts are appreciated! 

           
          • The main difference between Fscd 1.x and 2.0 is how they access the input device. Fscd 1.x used direct access to the input device while Fscd 2.0 used XInput. So you need to configure X to access the input device, if it not using hal. So please modify your X configuration by adding the following section...

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

            ... and add the following line in the ServerLayout section.

              InputDevice "FSC Tablet Buttons"

            Does it helps?

              Robert

             
            • Ah thanks, seems to work now.  Screen rotation is working, but I'm having some difficulty with the brightness changing.  When I try to use the brightness keys, I get a floating point exception:

              This is the debug output:

              backlight value: 0
              backlight value: 0
              Floating point exception

              Any thoughts?  Thanks again for your help

               
              • Oops, spoke too soon.  I was using an older kernel version than I had originally wanted to.  When I try fscd on a 2.6.28 kernel, it hangs up on this line in fscd.c (in int main, in the main while loop):

                select(xfh+1, &in, NULL, NULL, &tv);

                I'm not too sure what differences in my kernel configurations might have caused this if anything.  When I looked, I didn't see anything that was obviously wrong.  Any thoughts? 

                 
                • Robert Gerlach
                  Robert Gerlach
                  2009-04-19

                  How do you start fscd? And what version of Xorg are you using?
                  Please make sure the X connection works correctly (DISPLAY, xauth etc).
                  And don't use sudo.

                    Robert

                   
    • Cefn Hoile
      Cefn Hoile
      2009-02-07

      I had trouble following the full instructions since they are a bit implicit, at...
      http://fjbtndrv.wiki.sourceforge.net/install

      I was running into the initIalisation error which reported (sic)...
      x11 initalisation failed
      ...which with the debug option compiled in, showed...

      cefn@cefn-linux-tablet:~/Desktop/fsc_btns-1.41$ fscd
      X11: Found XInputExtension 2.2 extension (146, 0, 0)
      X11: Found XTEST 2.2 extension (147, 0, 0)
      X11: Found RANDR 2.2 extension (153, 0, 0)
      X11: Found DPMS 2.2 extension (137, 0, 0)
      xinput: searching fsc_btns device ...
      xinput:  ... device Virtual core keyboard
      xinput:  ... device Virtual core pointer
      xinput:  ... device Macintosh mouse button emulation
      xinput:  ... device DualPoint Stick
      xinput:  ... device AlpsPS/2 ALPS DualPoint TouchPad
      xinput:  ... device AT Translated Set 2 keyboard
      xinput:  ... device Fujitsu FUJ02B1
      xinput:  ... device Video Bus
      xinput:  ... device Fujitsu FUJ02E3
      X11: xinput device not found
      x11 initalisation failed

      Which just meant that the fsc_btns module wasn't loaded.

      I didn't download the version of fjbtndrv from...
      http://jan.rychter.com/software/fjbtndrv/fjbtndrv.ucw
      ...since it seemed to be an older version than the maintained one.

      Instead I did the following on Xubuntu intrepid.

      Downloaded fsc_btns-1.41 extracted it, loaded up a terminal window and navigated until I was in the fsc_btns-1.41 directory.

      Ran...

      make
      sudo make install  
      sudo /sbin/depmod -ae
      modprobe fsc_btns

      ...which then successfully loaded the button kernel module (the key step is to run depmod.

      If you want this module to load again after a reboot, then you should edit /etc/modules and add a line...
      fsc_btns

      Once the kernel module is loaded, fscd seems to run fine. To build fscd for my Fujitsu P1610 I downloaded fjbtndrv 2.00-rc1 and from a terminal console in the extracted directory I ran...
      ./configure
      make WACOM=n OSD=n
      sudo make install
      ...but to do ./configure successfully you may be required to install some extra dev packages (I had to install libhal-dev and libxtst-dev), which you can install like this...
      sudo apt-get install libhal-dev libxtst-dev

      You can trace the correct dev package for a dependency which ./configure complains about by searching the repositories, e.g.
      apt-cache search hal | grep dev
      ...shows you some packages containing hal and dev, then...
      sudo apt-get install libhal-dev
      ...will actually install the missing package.

      After successfully loading the module and building the fscd binary, everything worked fine for me.

       
      • Robert Gerlach
        Robert Gerlach
        2009-02-10

        Sorry for the confusion, I'll revise the wiki.

        The kernel module is part of the fscd and fjbtndrv package (see src/linux) and should be installed into the extra folder of your kernel modules tree. Please check the output of modinfo fsc_btns.
        The fsc_btns package is a slightly modified version of the kernel module and for people only who don't like daemons like fscd... so it's best just ignore it.

        > If you want this module to load again after a reboot, then you should edit /etc/modules and add a line...
        > fsc_btns

        It's not needed. The module should be loaded for the ACPI IDs FUJ02BD and FUJ02BF automatically. If not, you can try to run `depmod -a' manually and report it as a bug please.

        > make WACOM=n OSD=n

        Better to use `configure --disable-wacom --disable-xosd'.

        > but to do ./configure successfully you may be required to install some extra dev packages

        Yes, this are the build dependencies from my ubuntu package:
        libhal-dev, libx11-dev, libxi-dev, libxext-dev, libxtst-dev, libxrandr-dev, libxosd-dev, wacom-tools

        But note, debian/ubuntu still have no dev package of wacom-tools. So you need to install linuxwacom manually or download the source and point configure to it (--with-linuxwacom).

        Thanks for the report,
          Robert

         
    • Cefn Hoile
      Cefn Hoile
      2009-02-07

      Out of interest if I try to compile it without explicitly disabling xosd, it throws this error when I try to run it...

      cefn@cefn-linux-tablet:~/Desktop/fjbtndrv-2.00-rc1$ fscd
      BadName (named color or font does not exist)

      ...so I'm running make with the OSD=n option to avoid this.

       
      • Robert Gerlach
        Robert Gerlach
        2009-02-11

        I can reproduce this on OpenSUSE 11.1. But it's only a info, fscd works here (with another font for OSD messages of course). Anyway, you can try to replace the used font in src/gui-xosd.c line 54. For example change helvetica to verdana (try xlsfont or xfontsel).

        Hope it helps,
          Robert

         
  • Hello,

    first I'd like to thank you for your work, I've been using it for quite a while now and its quite useful.

    I recently upgraded my t4010d to linux mint. After an install and configuration, I fail to run fscd with the following debug message:

    Found XInputExtension 2.2 extension (140, 0, 0)
    Found XTEST 2.2 extension (141, 0, 0)
    Found RANDR 2.2 extension (149, 0, 0)
    Found DPMS 2.2 extension (131, 0, 0)
    searching tablet buttons device …
    … device Virtual core pointer
    … device Virtual core keyboard
    … device cursor
    … device stylus
    … device eraser
    … device AT Translated Set 2 keyboard
    … device Power Button
    … device Fujitsu FUJ02B1
    … device Video Bus
    … device Power Button
    … device Macintosh mouse button emulation
    … device AlpsPS/2 ALPS GlidePoint
    … device PS/2 Mouse
    xinput device not found
    x11 initalisation failed

    Can you advice me on what I did wrong ?

    Have a nice day !

     
  • With the additional informations regarding my Xorg:

    X.Org X Server 1.6.4
    Release Date: 2009-9-27
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.24-23-server i686 Ubuntu
    Current Operating System: Linux wintermute 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686
    Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=83abcbd9-7691-44df-93f0-4473f0022d2e ro quiet splash
    Build Date: 26 October 2009  05:15:02PM
    xorg-server 2:1.6.4-2ubuntu4 (buildd@)
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.

    I tried to run fscd both as root or normal user with the same output

     
  • Problem solved :

    I installed fscd using the ubuntu .deb from your ppa, it works flawlessly.

    Thank you very much for this wonderful software ^^

     
  • The fsc_btns device isn't listed. Please check the kernel module (maybe load it manually before starting X).

     
  • i have the same issue, the problem is that there is a kernel module that needs to be loaded so that ithe software finds the tablet buttons. I know that the command is something like 'modprobe fsc_btns' but i can't seem to get it to work properly (I think fsc_btns is not the right thing to load).

    It's a recurring problem, everytime Xorg is updated on Fedora, this kernel driver needs to be reloaded, and it's not.

    The maintainer of the code should push the kernel module upstream so that it's supported and maintained by the linux kernel dev team.

     
  • Robert Gerlach
    Robert Gerlach
    2010-03-24

    You are right and I've already tired, but I have no time for this now. Maybe I'll retry in a half year.