Page 11 of 107 FirstFirst ... 9101112132161 ... LastLast
Results 101 to 110 of 1069

Thread: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

  1. #101
    Join Date
    Nov 2007
    Location
    Portugal
    Beans
    1,155

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    forget this post, New driver now supports input profiles!
    Last edited by falkTX; July 27th, 2009 at 09:00 AM.

  2. #102
    Join Date
    Mar 2009
    Beans
    17

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    Quote Originally Posted by falkTX View Post
    QUESTION:
    Should the init script (the one that allows connect sixaxis from boot) use:
    1. Support for input profiles but no accelerometers
    2. No support for input profiles but accelerometers do work


    (maybe an option to configure it inside QtSixA?)
    I suspect most people will be using it for vintage emulation, and I think support for non-console accelerometer applications is still very limited. I would vote for profiles (1). Of course, an option would be the best.

  3. #103
    Join Date
    Nov 2007
    Location
    Portugal
    Beans
    1,155

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    Update: (copied from changelog)
    * New upstream release:
    - New SixA driver is now compatible with input profiles!
    - Fixed input profiles "none" keys (may had cause X crashes)
    - "New" button on input profile tab is available again
    [You're now able to choose the filename/path to save to]
    - 'List of Sixaxis' now also displays controller's name (at right of address)
    - "QtSixA Modules" now has option to start the new driver
    - Removed the experimental driver tab
    - Added a "Game Profiles" tab ('Neverball' and 'ePSXe' profiles are available now)
    - Added a simple label text that informs if QtSixA modules are running or not
    - In the about dialog, 'devs' has changed to 'thanks to'
    - Support for new hardware:
    + PS3 remote appears in 'list of Sixaxis' when connected through USB (bluetooth not yet)
    + PS3 remote support using the new driver (NOT TESTED!, and will not appear on 'list of Sixaxis' or setup)
    + Keypad support using the new driver (only mouse "works" yet [NOT TESTED!])
    - New 'List of Features' menu action in "Help"
    - Allow the 'non-use' of LED in QtSixA modules (new driver only, all LEDs will be off)
    - Auto-start new driver when starting QtSixA
    - Added a splash screen [can someone do a better one, please?]
    - 'List of Sixaxis' is now 'list of devices', since QtSixA supports more than just Sixaxis
    - QtSixA Daemon removed (QtSixA auto-loads modules now; still available in applications)
    - Other small fixes

  4. #104
    Join Date
    Nov 2007
    Location
    Portugal
    Beans
    1,155

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    There's a lot of new things...
    The most notable one (besides the splash screen), is that QtSixA modules now automatically loads when starting the app.

    The next thing I'll focus on is the keypad, but I need help to get it working. If you have one and you're not a linux newbie, please reply

  5. #105
    Join Date
    Nov 2007
    Location
    Portugal
    Beans
    1,155

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    Donations are now accepted:
    http://falktx.blogspot.com/

    The first thing I'll get is a Keypad, then a DS3. Maybe, if enough money, a PS3 remote as well

  6. #106
    Join Date
    Jul 2009
    Beans
    9
    Distro
    Xubuntu 9.04 Jaunty Jackalope

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    I got a new harddisk for my ps3 so I reinstalled xubuntu from scratch. Had to start over with all the things

    When I installed sixa (added the repository and then did apt-get install sixa) I got this error:
    Code:
    Setting up sixa-extra-modules (0.2a-falktx8) ...
    -m64 build flag was set
    sixad-bin: no process killed
    gcc -m64 -Wall -O2 -D_GNU_SOURCE    -c -o uinputdev.o uinputdev.c
    gcc -m64 -Wall -O2 -D_GNU_SOURCE    -c -o sixsrv.o sixsrv.c
    gcc uinputdev.o sixsrv.o -m64 -Wall -O2 -D_GNU_SOURCE  -o sixad-bin  -lbluetooth
    /usr/bin/ld: skipping incompatible /usr/lib/gcc/powerpc-linux-gnu/4.3.3/../../../libbluetooth.so when searching for -lbluetooth
    /usr/bin/ld: skipping incompatible /usr/lib/libbluetooth.so when searching for -lbluetooth
    /usr/bin/ld: cannot find -lbluetooth
    collect2: ld returned 1 exit status
    make: *** [sixad-bin] Error 1
    cp: cannot stat `/tmp/sixa_extra/sixad-bin': No such file or directory
    rm -f uinputdev.o sixsrv.o sixad-bin

    but .. good news! I got my keypad to work

    Quote Originally Posted by falkTX View Post
    This should be fixed with a simple text file in the right location.

    Please try downloading the attached file, unzip it, and copy it to:
    /usr/share/hal/fdi/policy/20thirdparty

    Then check if anything changed when connecting the pad again
    This was your fdi file:
    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <deviceinfo version="0.2">
      <device>
          <!-- Experimental Keypad driver for Sixaxis -->      
          <match key="input.product" string_outof="Sony Computer Entertainment Wireless Keypad">
            <merge key="input.x11_driver" type="string">joystick</merge>
    	<merge key="input.x11_driver" type="string">keyboard</merge>
          </match>
      </device>
    </deviceinfo>
    I moved the file to /etc/hal/fdi/policy (where you put one of your fdi's as well?)
    and changed the file to:
    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <deviceinfo version="0.2">
      <device>
          <!-- Experimental Keypad driver for Sixaxis -->
          <match key="input.product" string_outof="Sony Computer Entertainment Wireless Keypad">
            <merge key="input.x11_driver" type="string">synaptic</merge>
            <merge key="input.x11_driver" type="string">evdev</merge>
          </match>
      </device>
    </deviceinfo>
    And then it worked

    happily mousing and typing away on my ps3 via the keypad.

    Just one question .. not sure if it's possible. this keypad isn't a true keyboard, misses some buttons like .. ctrl, alt, all the f keys.
    It does have 2 buttons that is just for the ps3, a link to the message menu in the XMB and the friendlist. Would it maybe be possible somehow to bind these 2 keys to make them work as ctrl and alt?

  7. #107
    Join Date
    Jul 2009
    Beans
    9
    Distro
    Xubuntu 9.04 Jaunty Jackalope

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    hmmm

    that's weird .. I just saw I made a typing error in "synaptic" .. it should be "synaptics"

    It still works though

    with only evdev I get this in the log:
    Code:
    (II) config/hal: Adding input device Sony Computer Entertainment Wireless Keypad
    (**) Sony Computer Entertainment Wireless Keypad: always reports core events
    (**) Sony Computer Entertainment Wireless Keypad: Device: "/dev/input/event2"
    (II) Sony Computer Entertainment Wireless Keypad: Found 2 mouse buttons
    (II) Sony Computer Entertainment Wireless Keypad: Found x and y relative axes
    (II) Sony Computer Entertainment Wireless Keypad: Found keys
    (II) Sony Computer Entertainment Wireless Keypad: Configuring as mouse
    (II) Sony Computer Entertainment Wireless Keypad: Configuring as keyboard
    (**) Sony Computer Entertainment Wireless Keypad: YAxisMapping: buttons 4 and 5
    (**) Sony Computer Entertainment Wireless Keypad: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Sony Computer Entertainment Wireless Keypad" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Sony Computer Entertainment Wireless Keypad: xkb_rules: "evdev"
    (**) Option "xkb_model" "pc105"
    (**) Sony Computer Entertainment Wireless Keypad: xkb_model: "pc105"
    (**) Option "xkb_layout" "us"
    (**) Sony Computer Entertainment Wireless Keypad: xkb_layout: "us"
    (**) Sony Computer Entertainment Wireless Keypad: (accel) keeping acceleration scheme 1
    (**) Sony Computer Entertainment Wireless Keypad: (accel) filter chain progression: 2.00
    (**) Sony Computer Entertainment Wireless Keypad: (accel) filter stage 0: 20.00 ms
    (**) Sony Computer Entertainment Wireless Keypad: (accel) set acceleration profile 0
    guess I don't have to define it as a touchpad .. evdev does that itself or so?

  8. #108
    Join Date
    Apr 2009
    Location
    Missouri, USA
    Beans
    12
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    Quote Originally Posted by falkTX View Post
    Update: (copied from changelog)
    * New upstream release:
    - New SixA driver is now compatible with input profiles!
    - Fixed input profiles "none" keys (may had cause X crashes)
    - "New" button on input profile tab is available again
    [You're now able to choose the filename/path to save to]
    - 'List of Sixaxis' now also displays controller's name (at right of address)
    I am unable to open the available keys file to make a new profile.

  9. #109
    Join Date
    Nov 2007
    Location
    Portugal
    Beans
    1,155

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    Quote Originally Posted by Polk1986 View Post
    I am unable to open the available keys file to make a new profile.
    just do in a terminal:
    Code:
    xmodmap -pke
    I'll fix that soon (it was supposed to open your default text editor; I guess you don't have one set..?)

  10. #110
    Join Date
    Nov 2007
    Location
    Portugal
    Beans
    1,155

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    Quote Originally Posted by stingerid4 View Post
    I got a new harddisk for my ps3 so I reinstalled xubuntu from scratch. Had to start over with all the things

    When I installed sixa (added the repository and then did apt-get install sixa) I got this error:
    Code:
    Setting up sixa-extra-modules (0.2a-falktx8) ...
    -m64 build flag was set
    sixad-bin: no process killed
    gcc -m64 -Wall -O2 -D_GNU_SOURCE    -c -o uinputdev.o uinputdev.c
    gcc -m64 -Wall -O2 -D_GNU_SOURCE    -c -o sixsrv.o sixsrv.c
    gcc uinputdev.o sixsrv.o -m64 -Wall -O2 -D_GNU_SOURCE  -o sixad-bin  -lbluetooth
    /usr/bin/ld: skipping incompatible /usr/lib/gcc/powerpc-linux-gnu/4.3.3/../../../libbluetooth.so when searching for -lbluetooth
    /usr/bin/ld: skipping incompatible /usr/lib/libbluetooth.so when searching for -lbluetooth
    /usr/bin/ld: cannot find -lbluetooth
    collect2: ld returned 1 exit status
    make: *** [sixad-bin] Error 1
    cp: cannot stat `/tmp/sixa_extra/sixad-bin': No such file or directory
    rm -f uinputdev.o sixsrv.o sixad-bin
    This should be fixed now

Page 11 of 107 FirstFirst ... 9101112132161 ... 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
  •