so i decided to start working my way through the code and found references to uinput in input/device.c
this gave me another keyword to use in google and lo and behold this popped up:
Fri Oct 17 2008 - Bastien Nocera <[email protected] <mailto:[email protected]>> - 4.14-2
- Add script to autoload uinput on startup, so the PS3 remote
works out-of-the-box
sure enough i did not have this module in my kernel.
just building now in hope that this might be the issue
not being a fedora user i never thought to look there to see if there was documentation ;-(
--
simon
Jelle de Jong wrote:
> There are a number of things not working yet. The connecting/pairing
> system should make the input device, at leased that is what I think. The
> X stuff is so that the input system can understand what it is saying,
> this is some sort of hid driver for the device. This is also not yet
> working. Then there is the thing that some of the developers like to
> merge everything in gui application so that is can only be setup with
> this gui or by manually creating dbus command and sending them ....
>
> I am also not a bluez developer and I tolled people I would like to
> understand how the heck somebody can implement proper support for these
> devices (I got a bag full of non working bluetooth devices), nobody seem
> to make the time to explain in detail how it works ... and how to get
> add code to get it working.
>
> So my strategy is just to wait until somebody cares to fix it... Not
> very fast or effective but nothing else I can do. I spent far to much
> time telling people it does not work.
>
then why does Bastien keep repeating that it is working?
has anybody else got it to work?
i'm not going to give up.
tomorrow i will put debug statements everywhere to see what is going on.
this has become a personnel challenge to get it working
--
simon
Simon Kenyon wrote:
> Jelle de Jong wrote:
>> I will wait until the next debian update of libx11 and hope an input
>> event will be created when connecting the device.
> why would X11 be involved in creating the event device?
> i might be using the remote without X
There are a number of things not working yet. The connecting/pairing
system should make the input device, at leased that is what I think. The
X stuff is so that the input system can understand what it is saying,
this is some sort of hid driver for the device. This is also not yet
working. Then there is the thing that some of the developers like to
merge everything in gui application so that is can only be setup with
this gui or by manually creating dbus command and sending them ....
I am also not a bluez developer and I tolled people I would like to
understand how the heck somebody can implement proper support for these
devices (I got a bag full of non working bluetooth devices), nobody seem
to make the time to explain in detail how it works ... and how to get
add code to get it working.
So my strategy is just to wait until somebody cares to fix it... Not
very fast or effective but nothing else I can do. I spent far to much
time telling people it does not work.
I am sorry for all the frustrations...
Best regards,
Jelle
Jelle de Jong wrote:
> I will wait until the next debian update of libx11 and hope an input
> event will be created when connecting the device.
why would X11 be involved in creating the event device?
i might be using the remote without X
--
simon
http://filebin.ca/xfgtug/bluez-gnome_1.9git_i386.deb
http://filebin.ca/mdxohj/bluez-utils_4.19git_i386.deb
------------------------------------------------------------------------
bluetoothd --nodaemon --debug
bluetoothd[3552]: Bluetooth daemon
bluetoothd[3552]: Enabling debug information
bluetoothd[3552]: parsing main.conf
bluetoothd[3552]: offmode=NoScan
bluetoothd[3552]: discovto=0
bluetoothd[3552]: pairto=0
bluetoothd[3552]: pageto=8192
bluetoothd[3552]: name=%h-%d
bluetoothd[3552]: class=0x000100
bluetoothd[3552]: inqmode=0
bluetoothd[3552]: Starting SDP server
bluetoothd[3552]: Loading plugins /usr/lib/bluetooth/plugins
bluetoothd[3552]: register_interface: path /org/bluez/3552/any
bluetoothd[3552]: Registered interface org.bluez.Service on path /org/bluez/3552/any
bluetoothd[3552]: Parsing /etc/bluetooth/network.conf failed: No such file or directory
bluetoothd[3552]: Config options: InterfacePrefix=bnep%d, PANU_Script=(null), GN_Script=(null), NAP_Script=(null), GN_Interface=pan0, NAP_Interface=pan1, Security=true
bluetoothd[3552]: Can't create GN bridge
bluetoothd[3552]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
bluetoothd[3552]: Unix socket created: 12
bluetoothd[3552]: audio.conf: Key file does not have key 'MaxConnected'
bluetoothd[3552]: Telephony plugin initialized
bluetoothd[3552]: HFP AG features: "Ability to reject a call" "Enhanced call status" "Extended Error Result Codes"
bluetoothd[3552]: HCI dev 0 registered
bluetoothd[3552]: child 3553 forked
bluetoothd[3552]: HCI dev 0 already up
bluetoothd[3552]: register_interface: path /org/bluez/3552/hci0
bluetoothd[3552]: Registered interface org.bluez.Service on path /org/bluez/3552/hci0
bluetoothd[3552]: network_server_probe: path /org/bluez/3552/hci0
bluetoothd[3552]: Adding record with handle 0x10000
bluetoothd[3552]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001115-0000-1000-8000-00805f9
bluetoothd[3552]: register_server_record: got record id 0x10000
bluetoothd[3552]: Registered interface org.bluez.NetworkPeer on path /org/bluez/3552/hci0
bluetoothd[3552]: network_server_probe: path /org/bluez/3552/hci0
bluetoothd[3552]: Adding record with handle 0x10001
bluetoothd[3552]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001117-0000-1000-8000-00805f9
bluetoothd[3552]: register_server_record: got record id 0x10001
bluetoothd[3552]: Registered interface org.bluez.NetworkHub on path /org/bluez/3552/hci0
bluetoothd[3552]: network_server_probe: path /org/bluez/3552/hci0
bluetoothd[3552]: Adding record with handle 0x10002
bluetoothd[3552]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001116-0000-1000-8000-00805f9
bluetoothd[3552]: register_server_record: got record id 0x10002
bluetoothd[3552]: Registered interface org.bluez.NetworkRouter on path /org/bluez/3552/hci0
bluetoothd[3552]: proxy_probe: path /org/bluez/3552/hci0
bluetoothd[3552]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/3552/hci0
bluetoothd[3552]: headset_server_probe: path /org/bluez/3552/hci0
bluetoothd[3552]: audio.conf: Key file does not have key 'Master'
bluetoothd[3552]: Adding record with handle 0x10003
bluetoothd[3552]: Record pattern UUID 00000003-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001108-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001112-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001203-0000-1000-8000-00805f9
bluetoothd[3552]: audio.conf: Key file does not have key 'SCORouting'
bluetoothd[3552]: a2dp_server_probe: path /org/bluez/3552/hci0
bluetoothd[3552]: audio.conf: Key file does not have key 'Disable'
bluetoothd[3552]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[3552]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[3552]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[3552]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[3552]: audio.conf: Key file does not have key 'Master'
bluetoothd[3552]: SEP 0xb93c7030 registered: type:0 codec:0 seid:1
bluetoothd[3552]: Adding record with handle 0x10004
bluetoothd[3552]: Record pattern UUID 00000019-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 0000110a-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 0000110d-0000-1000-8000-00805f9
bluetoothd[3552]: avrcp_server_probe: path /org/bluez/3552/hci0
bluetoothd[3552]: audio.conf: Key file does not have key 'Master'
bluetoothd[3552]: Adding record with handle 0x10005
bluetoothd[3552]: Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 0000110c-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[3552]: Adding record with handle 0x10006
bluetoothd[3552]: Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[3552]: Creating device /org/bluez/3552/hci0/dev_00_1A_80_AB_0A_B1
bluetoothd[3552]: Probe drivers for /org/bluez/3552/hci0/dev_00_1A_80_AB_0A_B1
bluetoothd[3552]: adapter_get_device(00:1A:80:AB:0A:B1)
bluetoothd[3552]: Found Audio Sink
bluetoothd[3552]: Registered interface org.bluez.AudioSink on path /org/bluez/3552/hci0/dev_00_1A_80_AB_0A_B1
bluetoothd[3552]: Found AV Target
bluetoothd[3552]: Registered interface org.bluez.Control on path /org/bluez/3552/hci0/dev_00_1A_80_AB_0A_B1
bluetoothd[3552]: Found AV Target
bluetoothd[3552]: Creating device /org/bluez/3552/hci0/dev_00_0C_55_D1_C9_78
bluetoothd[3552]: Probe drivers for /org/bluez/3552/hci0/dev_00_0C_55_D1_C9_78
bluetoothd[3552]: serial_probe: path /org/bluez/3552/hci0/dev_00_0C_55_D1_C9_78: 00001108-0000-1000-8000-00805f9b34fb
bluetoothd[3552]: Registered interface org.bluez.Serial on path /org/bluez/3552/hci0/dev_00_0C_55_D1_C9_78
bluetoothd[3552]: serial_probe: path /org/bluez/3552/hci0/dev_00_0C_55_D1_C9_78: 0000111e-0000-1000-8000-00805f9b34fb
bluetoothd[3552]: headset_probe: path /org/bluez/3552/hci0/dev_00_0C_55_D1_C9_78
bluetoothd[3552]: Registered interface org.bluez.Input on path /org/bluez/3552/hci0/dev_00_0C_55_D1_C9_78
bluetoothd[3552]: adapter_get_device(00:0C:55:D1:C9:78)
bluetoothd[3552]: Found Headset record
bluetoothd[3552]: Discovered Headset service on RFCOMM channel 2
bluetoothd[3552]: Registered interface org.bluez.Headset on path /org/bluez/3552/hci0/dev_00_0C_55_D1_C9_78
bluetoothd[3552]: audio handle_uuid: server not enabled for 0000111e-0000-1000-8000-00805f9b34fb (0x111e)
bluetoothd[3552]: Found Audio Sink
bluetoothd[3552]: Registered interface org.bluez.AudioSink on path /org/bluez/3552/hci0/dev_00_0C_55_D1_C9_78
bluetoothd[3552]: Found AV Remote
bluetoothd[3552]: Registered interface org.bluez.Control on path /org/bluez/3552/hci0/dev_00_0C_55_D1_C9_78
bluetoothd[3552]: Adapter /org/bluez/3552/hci0 has been enabled
bluetoothd[3552]: Starting security manager 0
bluetoothd[3552]: HCI dev 1 registered
bluetoothd[3552]: child 3554 forked
bluetoothd[3552]: HCI dev 1 already up
bluetoothd[3552]: register_interface: path /org/bluez/3552/hci1
bluetoothd[3552]: Registered interface org.bluez.Service on path /org/bluez/3552/hci1
bluetoothd[3552]: network_server_probe: path /org/bluez/3552/hci1
bluetoothd[3552]: Adding record with handle 0x10007
bluetoothd[3552]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001115-0000-1000-8000-00805f9
bluetoothd[3552]: register_server_record: got record id 0x10007
bluetoothd[3552]: Registered interface org.bluez.NetworkPeer on path /org/bluez/3552/hci1
bluetoothd[3552]: network_server_probe: path /org/bluez/3552/hci1
bluetoothd[3552]: Adding record with handle 0x10008
bluetoothd[3552]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001117-0000-1000-8000-00805f9
bluetoothd[3552]: register_server_record: got record id 0x10008
bluetoothd[3552]: Registered interface org.bluez.NetworkHub on path /org/bluez/3552/hci1
bluetoothd[3552]: network_server_probe: path /org/bluez/3552/hci1
bluetoothd[3552]: Adding record with handle 0x10009
bluetoothd[3552]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001116-0000-1000-8000-00805f9
bluetoothd[3552]: register_server_record: got record id 0x10009
bluetoothd[3552]: Registered interface org.bluez.NetworkRouter on path /org/bluez/3552/hci1
bluetoothd[3552]: proxy_probe: path /org/bluez/3552/hci1
bluetoothd[3552]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/3552/hci1
bluetoothd[3552]: headset_server_probe: path /org/bluez/3552/hci1
bluetoothd[3552]: audio.conf: Key file does not have key 'Master'
bluetoothd[3552]: Adding record with handle 0x1000a
bluetoothd[3552]: Record pattern UUID 00000003-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001108-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001112-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001203-0000-1000-8000-00805f9
bluetoothd[3552]: audio.conf: Key file does not have key 'SCORouting'
bluetoothd[3552]: a2dp_server_probe: path /org/bluez/3552/hci1
bluetoothd[3552]: audio.conf: Key file does not have key 'Disable'
bluetoothd[3552]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[3552]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[3552]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[3552]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[3552]: audio.conf: Key file does not have key 'Master'
bluetoothd[3552]: SEP 0xb93cb2e0 registered: type:0 codec:0 seid:1
bluetoothd[3552]: Adding record with handle 0x1000b
bluetoothd[3552]: Record pattern UUID 00000019-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 0000110a-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 0000110d-0000-1000-8000-00805f9
bluetoothd[3552]: avrcp_server_probe: path /org/bluez/3552/hci1
bluetoothd[3552]: audio.conf: Key file does not have key 'Master'
bluetoothd[3552]: Adding record with handle 0x1000c
bluetoothd[3552]: Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 0000110c-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[3552]: Adding record with handle 0x1000d
bluetoothd[3552]: Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[3552]: Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[3552]: Creating device /org/bluez/3552/hci1/dev_00_07_61_0F_4A_60
bluetoothd[3552]: Probe drivers for /org/bluez/3552/hci1/dev_00_07_61_0F_4A_60
bluetoothd[3552]: hid_device_probe: path /org/bluez/3552/hci1/dev_00_07_61_0F_4A_60
bluetoothd[3552]: Registered interface org.bluez.Input on path /org/bluez/3552/hci1/dev_00_07_61_0F_4A_60
bluetoothd[3552]: Creating device /org/bluez/3552/hci1/dev_11_11_11_11_17_95
bluetoothd[3552]: Probe drivers for /org/bluez/3552/hci1/dev_11_11_11_11_17_95
bluetoothd[3552]: hid_device_probe: path /org/bluez/3552/hci1/dev_11_11_11_11_17_95
bluetoothd[3552]: Registered interface org.bluez.Input on path /org/bluez/3552/hci1/dev_11_11_11_11_17_95
bluetoothd[3552]: Creating device /org/bluez/3552/hci1/dev_00_07_61_8A_1A_AA
bluetoothd[3552]: Probe drivers for /org/bluez/3552/hci1/dev_00_07_61_8A_1A_AA
bluetoothd[3552]: hid_device_probe: path /org/bluez/3552/hci1/dev_00_07_61_8A_1A_AA
bluetoothd[3552]: Registered interface org.bluez.Input on path /org/bluez/3552/hci1/dev_00_07_61_8A_1A_AA
bluetoothd[3552]: Creating device /org/bluez/3552/hci1/dev_00_07_61_8A_42_DF
bluetoothd[3552]: Probe drivers for /org/bluez/3552/hci1/dev_00_07_61_8A_42_DF
bluetoothd[3552]: hid_device_probe: path /org/bluez/3552/hci1/dev_00_07_61_8A_42_DF
bluetoothd[3552]: Registered interface org.bluez.Input on path /org/bluez/3552/hci1/dev_00_07_61_8A_42_DF
bluetoothd[3552]: Adapter /org/bluez/3552/hci1 has been enabled
bluetoothd[3552]: Starting security manager 1
bluetoothd[3552]: child 3553 exited
bluetoothd[3552]: child 3554 exited
bluetoothd[3552]: Computer is classified as laptop
bluetoothd[3552]: Current device class is 0x0a010c
bluetoothd[3552]: Setting 0x00010c for major/minor device class
bluetoothd[3552]: Computer is classified as laptop
bluetoothd[3552]: Current device class is 0x0a010c
bluetoothd[3552]: Setting 0x00010c for major/minor device class
bluetoothd[3552]: Agent registered for hci0 at :1.18:/org/bluez/agent/hci0
bluetoothd[3552]: Agent registered for hci1 at :1.18:/org/bluez/agent/hci1
bluetoothd[3552]: Discovery session 0xb93be870 with :1.20 activated
bluetoothd[3552]: session_ref(0xb93be870): ref=1
bluetoothd[3552]: session_unref(0xb93be870): ref=0
bluetoothd[3552]: Discovery session 0xb93be870 with :1.20 deactivated
bluetoothd[3552]: Stopping discovery
bluetoothd[3552]: create_device(00:1E:3D:15:0A:4F)
bluetoothd[3552]: adapter_create_device(00:1E:3D:15:0A:4F)
bluetoothd[3552]: Creating device /org/bluez/3552/hci0/dev_00_1E_3D_15_0A_4F
bluetoothd[3552]: adapter_get_device(00:1E:3D:15:0A:4F)
bluetoothd[3552]: Probe drivers for /org/bluez/3552/hci0/dev_00_1E_3D_15_0A_4F
bluetoothd[3552]: hid_device_probe: path /org/bluez/3552/hci0/dev_00_1E_3D_15_0A_4F
bluetoothd[3552]: Registered interface org.bluez.Input on path /org/bluez/3552/hci0/dev_00_1E_3D_15_0A_4F
------------------------------------------------------------------------
hcitool scan
Scanning ...
00:1E:3D:15:0A:4F BD Remote Control
------------------------------------------------------------------------
sudo hcitool info 00:1E:3D:15:0A:4F
Requesting information ...
BD Address: 00:1E:3D:15:0A:4F
Device Name: BD Remote Control
LMP Version: 2.0 (0x3) LMP Subversion: 0x229
Manufacturer: Broadcom Corporation (15)
Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
<encryption> <slot offset> <timing accuracy> <role switch>
<sniff mode> <RSSI> <power control> <enhanced iscan>
<interlaced iscan> <interlaced pscan> <AFH cap. slave>
------------------------------------------------------------------------
sdptool browse 00:1E:3D:15:0A:4F
Browsing 00:1E:3D:15:0A:4F ...
Service Name: BD Remote Control
Service Description: BD Remote Control
Service Provider: Sony Computer Entertainment Inc
Service RecHandle: 0x10000
Service Class ID List:
"Human Interface Device" (0x1124)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 17
"HIDP" (0x0011)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Human Interface Device" (0x1124)
Version: 0x0100
------------------------------------------------------------------------
On Fri, 2008-11-28 at 22:43 +0000, Simon Kenyon wrote:
> Bastien Nocera wrote:
<snip>
> > You need to press buttons on the remote for it to connect to the
> > computer. It will disconnect automatically after some time of idleness.
> >
> > After that you need to use a new enough X server, or LIRC to get the
> > events to your X applications.
> >
> what causes the /dev/input/eventX file to be created?
> ie. is it bluetoothd or hidd?
It is obviously bluetoothd (actually bluetoothd's input plugin) as I've
said a couple of days ago (and on numerous occasions on this list) that
hidd has no code to handle the PS3 BD remote's protocol. If you're using
hidd, it won't ever work, period.
If the PS3 remote isn't connected properly, it won't show up in
bluetooth-properties.
Bastien Nocera wrote:
> On Fri, 2008-11-28 at 10:54 +0000, Simon Kenyon wrote:
>
>> Simon Kenyon wrote:
>>
>>> so i decided to start working my way through the code and found
>>> references to uinput in input/device.c
>>> this gave me another keyword to use in google and lo and behold this
>>> popped up:
>>>
>>> Fri Oct 17 2008 - Bastien Nocera <[email protected]
>>> <mailto:[email protected]>> - 4.14-2
>>> - Add script to autoload uinput on startup, so the PS3 remote
>>> works out-of-the-box
>>>
>>>
>>> sure enough i did not have this module in my kernel.
>>> just building now in hope that this might be the issue
>>>
>> well that got me nowhere - still no events
>> but at least i now have a /dev/input/uinput
>>
>
> You need to press buttons on the remote for it to connect to the
> computer. It will disconnect automatically after some time of idleness.
>
> After that you need to use a new enough X server, or LIRC to get the
> events to your X applications.
>
what causes the /dev/input/eventX file to be created?
ie. is it bluetoothd or hidd?
On Fri, 2008-11-28 at 10:54 +0000, Simon Kenyon wrote:
> Simon Kenyon wrote:
> > so i decided to start working my way through the code and found
> > references to uinput in input/device.c
> > this gave me another keyword to use in google and lo and behold this
> > popped up:
> >
> > Fri Oct 17 2008 - Bastien Nocera <[email protected]
> > <mailto:[email protected]>> - 4.14-2
> > - Add script to autoload uinput on startup, so the PS3 remote
> > works out-of-the-box
> >
> >
> > sure enough i did not have this module in my kernel.
> > just building now in hope that this might be the issue
> well that got me nowhere - still no events
> but at least i now have a /dev/input/uinput
You need to press buttons on the remote for it to connect to the
computer. It will disconnect automatically after some time of idleness.
After that you need to use a new enough X server, or LIRC to get the
events to your X applications.
Simon Kenyon wrote:
> Jelle de Jong wrote:
>> Hi Simon, I share your frustrations :-p. I will do some testing with the
>> latest git this weekend. You may want to look at my previous postings in
>> the archive.
>>
>> I advice you to give it a few hours rest and let me do some tesing on
>> Debian SID with the latested bluez-git. I don't know for sure if the
>> manatory xorg patch made it into the experimental packages...
>>
> it is rather frustrating
> i've had this remote for 6 months now and would like to get it working
> "properly"
>
> what i would love to getis a description of a working configuration
> (config files in particular)
> i don't know if i'm supposed to put something into one or more of the
> /etc/bluetooth config files.
> or something in hal or dbus for that matter
>
> we've both been told "it just works" but it doesn't
> --
> simon
I know it is frustrating, and I also got this device a while and spent
way to much time getting it working "out of the box"
As I said in my first response it does not yet just works, but I am not
an developer of bluez, just an heavy user and tester. BTW you should not
have to make any changes to the bluez config files.
I will look into it, this weekend and report back.
If you really want to try out right now, use the latest bluez git of
bluez-utils and bluez-gnome and the latest xorg git and try to get an
input event.
Best regards,
Jelle
Jelle de Jong wrote:
> Hi Simon, I share your frustrations :-p. I will do some testing with the
> latest git this weekend. You may want to look at my previous postings in
> the archive.
>
> I advice you to give it a few hours rest and let me do some tesing on
> Debian SID with the latested bluez-git. I don't know for sure if the
> manatory xorg patch made it into the experimental packages...
>
it is rather frustrating
i've had this remote for 6 months now and would like to get it working
"properly"
what i would love to getis a description of a working configuration
(config files in particular)
i don't know if i'm supposed to put something into one or more of the
/etc/bluetooth config files.
or something in hal or dbus for that matter
we've both been told "it just works" but it doesn't
--
simon
Simon Kenyon wrote:
> Simon Kenyon wrote:
>> Simon Kenyon wrote:
>>> Simon Kenyon wrote:
>>>> so i decided to start working my way through the code and found
>>>> references to uinput in input/device.c
>>>> this gave me another keyword to use in google and lo and behold this
>>>> popped up:
>>>>
>>>> Fri Oct 17 2008 - Bastien Nocera <[email protected]
>>>> <mailto:[email protected]>> - 4.14-2
>>>> - Add script to autoload uinput on startup, so the PS3 remote
>>>> works out-of-the-box
>>>>
>>>>
>>>> sure enough i did not have this module in my kernel.
>>>> just building now in hope that this might be the issue
>>> well that got me nowhere - still no events
>>> but at least i now have a /dev/input/uinput
>>>
>>> will have to dig further and see what bluetoothd does with it
>> do i have to have something in one of the /etc/bluetooth/*.conf files
>> specific to the BD Remote?
>>
>> could somebody who has this working please post the contents of
>> /etc/bluetooth/*.conf?
>> or do i need something to be configured in dbus?
>>
>> i cannot see how any of the code in input/fakehid.c gets called. i've
>> put a lot of debug statements in there; trying to understand the logic.
>> i don't see any devices getting registered
>
> i left bluetooth-wizard running for 10 minutes while i did something else
> maybe i pressed <start> and <enter> during that period. i cannot remember.
>
> anyway, the BD Remote appeared in the bluetooth-wizard setup window.
> when i typed forward it said it was successful. what did it do?
>
> now i try again and the remote is in the window from the start, but when
> i select it and go forward, it now says "Pairing with BD Remote Control
> failed".
> what does that mean?
>
> still don't know what has happened to /dev/input/event<x> where <x> is
> usually 7 in my case. i only ever see it if i type hidd --search and
> <start> and <enter>
> if i should not use it, why is it built and installed?
>
> regards
> --
> simon
Hi Simon, I share your frustrations :-p. I will do some testing with the
latest git this weekend. You may want to look at my previous postings in
the archive.
I advice you to give it a few hours rest and let me do some tesing on
Debian SID with the latested bluez-git. I don't know for sure if the
manatory xorg patch made it into the experimental packages....
Best regards,
Jelle
Simon Kenyon wrote:
> Simon Kenyon wrote:
>> Simon Kenyon wrote:
>>> so i decided to start working my way through the code and found
>>> references to uinput in input/device.c
>>> this gave me another keyword to use in google and lo and behold this
>>> popped up:
>>>
>>> Fri Oct 17 2008 - Bastien Nocera <[email protected]
>>> <mailto:[email protected]>> - 4.14-2
>>> - Add script to autoload uinput on startup, so the PS3 remote
>>> works out-of-the-box
>>>
>>>
>>> sure enough i did not have this module in my kernel.
>>> just building now in hope that this might be the issue
>> well that got me nowhere - still no events
>> but at least i now have a /dev/input/uinput
>>
>> will have to dig further and see what bluetoothd does with it
>
> do i have to have something in one of the /etc/bluetooth/*.conf files
> specific to the BD Remote?
>
> could somebody who has this working please post the contents of
> /etc/bluetooth/*.conf?
> or do i need something to be configured in dbus?
>
> i cannot see how any of the code in input/fakehid.c gets called. i've
> put a lot of debug statements in there; trying to understand the logic.
> i don't see any devices getting registered
i left bluetooth-wizard running for 10 minutes while i did something else
maybe i pressed <start> and <enter> during that period. i cannot remember.
anyway, the BD Remote appeared in the bluetooth-wizard setup window.
when i typed forward it said it was successful. what did it do?
now i try again and the remote is in the window from the start, but when
i select it and go forward, it now says "Pairing with BD Remote Control
failed".
what does that mean?
still don't know what has happened to /dev/input/event<x> where <x> is
usually 7 in my case. i only ever see it if i type hidd --search and
<start> and <enter>
if i should not use it, why is it built and installed?
regards
--
simon
Simon Kenyon wrote:
> Simon Kenyon wrote:
>> so i decided to start working my way through the code and found
>> references to uinput in input/device.c
>> this gave me another keyword to use in google and lo and behold this
>> popped up:
>>
>> Fri Oct 17 2008 - Bastien Nocera <[email protected]
>> <mailto:[email protected]>> - 4.14-2
>> - Add script to autoload uinput on startup, so the PS3 remote
>> works out-of-the-box
>>
>>
>> sure enough i did not have this module in my kernel.
>> just building now in hope that this might be the issue
> well that got me nowhere - still no events
> but at least i now have a /dev/input/uinput
>
> will have to dig further and see what bluetoothd does with it
do i have to have something in one of the /etc/bluetooth/*.conf files
specific to the BD Remote?
could somebody who has this working please post the contents of
/etc/bluetooth/*.conf?
or do i need something to be configured in dbus?
i cannot see how any of the code in input/fakehid.c gets called. i've
put a lot of debug statements in there; trying to understand the logic.
i don't see any devices getting registered
thanks in advance
--
simon
Simon Kenyon wrote:
> so i decided to start working my way through the code and found
> references to uinput in input/device.c
> this gave me another keyword to use in google and lo and behold this
> popped up:
>
> Fri Oct 17 2008 - Bastien Nocera <[email protected]
> <mailto:[email protected]>> - 4.14-2
> - Add script to autoload uinput on startup, so the PS3 remote
> works out-of-the-box
>
>
> sure enough i did not have this module in my kernel.
> just building now in hope that this might be the issue
well that got me nowhere - still no events
but at least i now have a /dev/input/uinput
will have to dig further and see what bluetoothd does with it
--
simon