+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52)
+---- Thread: [LINUX] Sony PlayStation 3 Blu-ray Disc Remote (PS3 BD) + LIRC + XBMC = SUCCESS (/showthread.php?tid=50717)
- ruff - 2009-11-13
logistiker Wrote:Hey Ruff, any word yet on your patches from bluez? Also, do you know why bluetoothd is tacking the CPU to 100%?
Not a single word since submission. And as it works for me I'm not so eager to go through all that bureaucracy to re-state what has already been told %)
As for the load - seems you're using not the latest patch. In previous patch there was an issue with load when either bluez or glib is not correctly handling IO Channel closure causing event loop.
http://www.mediafire.com/file/dzymtdnmemn/my.patch.gz - this is the latest patch i'm using
- kitlaan - 2009-11-13
ruff Wrote:Not a single word since submission. And as it works for me I'm not so eager to go through all that bureaucracy to re-state what has already been told %)
What was the procedure for submission, if you don't mind summarizing? I might give it a shot with my modification to your patch, just to see how it goes.
ruff Wrote:As for the load - seems you're using not the latest patch. In previous patch there was an issue with load when either bluez or glib is not correctly handling IO Channel closure causing event loop.
When I was developing my code-set, I figured out why the udelay() was put in there. That was fun
- menno - 2009-11-13
(T: XBMCLive)root@XBMCLive:/home/xbmc# bluetoothd stop
(T: XBMCLive)root@XBMCLive:/home/xbmc# bluetoothd -nd
bluetoothd[6236]: Bluetooth daemon 4.57
bluetoothd[6236]: Enabling debug information
bluetoothd[6236]: Parsing /etc/bluetooth/main.conf failed: No such file or directory
bluetoothd[6236]: Unable to get on D-Bus
- kitlaan - 2009-11-13
menno Wrote:(T: XBMCLive)root@XBMCLive:/home/xbmc# bluetoothd stop
(T: XBMCLive)root@XBMCLive:/home/xbmc# bluetoothd -nd
You need to run the full command: "/etc/init.d/bluetoothd stop" (to stop the existing bluetooth service). Without running that, the next command "bluetoothd -nd" can't actually take over. (Hence the DBus error).
- menno - 2009-11-13
(T: XBMCLive)root@XBMCLive:/home/xbmc# /usr/sbin/bluetoothd stop
(T: XBMCLive)root@XBMCLive:/home/xbmc# /usr/sbin/bluetoothd -nd
bluetoothd[7206]: Bluetooth daemon 4.57
bluetoothd[7206]: Enabling debug information
bluetoothd[7206]: Parsing /etc/bluetooth/main.conf failed: No such file or directory
bluetoothd[7206]: Unable to get on D-Bus
thats my location for bluetoothd,
whats about main.conf?
- kitlaan - 2009-11-14
menno Wrote:(T: XBMCLive)root@XBMCLive:/home/xbmc# /usr/sbin/bluetoothd stop
(T: XBMCLive)root@XBMCLive:/home/xbmc# /usr/sbin/bluetoothd -nd
bluetoothd[7206]: Bluetooth daemon 4.57
bluetoothd[7206]: Enabling debug information
bluetoothd[7206]: Parsing /etc/bluetooth/main.conf failed: No such file or directory
bluetoothd[7206]: Unable to get on D-Bus
thats my location for bluetoothd,
whats about main.conf?
...
/etc/init.d/bluetoothd stop. As in the init script, that runs bluetoothd on boot (and not the actual bluetoothd executable).
I'm surprised main.conf isn't in /etc/bluetooth/ (there should be many files), but it shouldn't matter.
- menno - 2009-11-14
I dont have /etc/init.d/bluetoothd
there is no bluetoothd in that dir... what should have installed it?
- Amelandbor - 2009-11-14
Well I've got only 2 files in that directory. Only main and rfcomm.conf
Found out because I wanted to edit my controls.
- Amelandbor - 2009-11-14
menno Wrote:I dont have /etc/init.d/bluetoothdMe neither and it's working for me
there is no bluetoothd in that dir... what should have installed it?
- kitlaan - 2009-11-14
Weird...
Is there a "/etc/init.d/bluetooth" ?
If all else fails, we can just do a "killall bluetoothd".
Here's my personal input.conf
- menno - 2009-11-14
[quote=kitlaan]Weird...
Is there a "/etc/init.d/bluetooth" ?
=> NO!!
If all else fails, we can just do a "killall bluetoothd".
====================
Code:
(T: XBMCLive)root@XBMCLive:/home/xbmc# killall bluetoothd
(T: XBMCLive)root@XBMCLive:/home/xbmc# sudo bluetoothd -nd
bluetoothd[7564]: Bluetooth daemon 4.57
bluetoothd[7564]: Enabling debug information
bluetoothd[7564]: Parsing /etc/bluetooth/main.conf failed: No such file or direc tory
bluetoothd[7564]: Starting SDP server
bluetoothd[7564]: Loading builtin plugins
bluetoothd[7564]: Loading audio plugin
bluetoothd[7564]: Loading input plugin
bluetoothd[7564]: Loading serial plugin
bluetoothd[7564]: Loading network plugin
bluetoothd[7564]: Loading service plugin
bluetoothd[7564]: Loading hciops plugin
bluetoothd[7564]: Loading hal plugin
bluetoothd[7564]: Loading storage plugin
bluetoothd[7564]: Loading plugins /usr/lib/bluetooth/plugins
bluetoothd[7564]: Can't load plugin /usr/lib/bluetooth/plugins/netlink.so: /usr/ lib/bluetooth/plugins/netlink.so: undefined symbol: debug
bluetoothd[7564]: register_interface: path /org/bluez/7564/any
bluetoothd[7564]: Registered interface org.bluez.Service on path /org/bluez/7564 /any
bluetoothd[7564]: Parsing /etc/bluetooth/network.conf failed: No such file or di rectory
bluetoothd[7564]: Config options: InterfacePrefix=bnep%d, PANU_Script=(null), GN _Script=(null), NAP_Script=(null), GN_Interface=pan0, NAP_Interface=pan1, Securi ty=true
bluetoothd[7564]: bridge pan0 created
bluetoothd[7564]: input.conf: Key file does not have key 'IdleTimeout'
bluetoothd[7564]: Unix socket created: 9
bluetoothd[7564]: audio.conf: Key file does not have key 'AutoConnect'
bluetoothd[7564]: Telephony plugin initialized
bluetoothd[7564]: HFP AG features: "Ability to reject a call" "Enhanced call sta tus" "Extended Error Result Codes"
bluetoothd[7564]: HCI dev 0 registered
bluetoothd[7564]: child 7569 forked
bluetoothd[7564]: btd_adapter_ref(0xb8137f00): ref=1
bluetoothd[7564]: Failed to open RFKILL control device
bluetoothd[7564]: Entering main loop
bluetoothd[7564]: child 7569 exited
bluetoothd[7564]: HCI dev 0 up
bluetoothd[7564]: Starting security manager 0
bluetoothd[7564]: Changing Major/Minor class to 0x000104
bluetoothd[7564]: register_interface: path /org/bluez/7564/hci0
bluetoothd[7564]: Registered interface org.bluez.Service on path /org/bluez/7564 /hci0
bluetoothd[7564]: network_server_probe: path /org/bluez/7564/hci0
bluetoothd[7564]: btd_adapter_ref(0xb8137f00): ref=2
bluetoothd[7564]: Adding record with handle 0x10000
bluetoothd[7564]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001115-0000-1000-8000-00805f9
bluetoothd[7564]: register_server_record: got record id 0x10000
bluetoothd[7564]: Registered interface org.bluez.NetworkPeer on path /org/bluez/ 7564/hci0
bluetoothd[7564]: network_server_probe: path /org/bluez/7564/hci0
bluetoothd[7564]: Adding record with handle 0x10001
bluetoothd[7564]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001117-0000-1000-8000-00805f9
bluetoothd[7564]: register_server_record: got record id 0x10001
bluetoothd[7564]: Registered interface org.bluez.NetworkHub on path /org/bluez/7 564/hci0
bluetoothd[7564]: network_server_probe: path /org/bluez/7564/hci0
bluetoothd[7564]: Adding record with handle 0x10002
bluetoothd[7564]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001116-0000-1000-8000-00805f9
bluetoothd[7564]: register_server_record: got record id 0x10002
bluetoothd[7564]: Registered interface org.bluez.NetworkRouter on path /org/blue z/7564/hci0
bluetoothd[7564]: proxy_probe: path /org/bluez/7564/hci0
bluetoothd[7564]: btd_adapter_ref(0xb8137f00): ref=3
bluetoothd[7564]: Registered interface org.bluez.SerialProxyManager on path /org /bluez/7564/hci0
bluetoothd[7564]: Parsing /etc/bluetooth/serial.conf failed: No such file or dir ectory
bluetoothd[7564]: btd_adapter_ref(0xb8137f00): ref=4
bluetoothd[7564]: headset_server_probe: path /org/bluez/7564/hci0
bluetoothd[7564]: btd_adapter_ref(0xb8137f00): ref=5
bluetoothd[7564]: audio_adapter_ref(0xb8138378): ref=1
bluetoothd[7564]: audio.conf: Key file does not have key 'Master'
bluetoothd[7564]: Adding record with handle 0x10003
bluetoothd[7564]: Record pattern UUID 00000003-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001108-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001112-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001203-0000-1000-8000-00805f9
bluetoothd[7564]: audio.conf: Key file does not have key 'SCORouting'
bluetoothd[7564]: Adding record with handle 0x10004
bluetoothd[7564]: Record pattern UUID 00000003-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 0000111e-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 0000111f-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001203-0000-1000-8000-00805f9
bluetoothd[7564]: a2dp_server_probe: path /org/bluez/7564/hci0
bluetoothd[7564]: audio_adapter_ref(0xb8138378): ref=2
bluetoothd[7564]: audio.conf: Key file does not have key 'Enable'
bluetoothd[7564]: audio.conf: Key file does not have key 'Disable'
bluetoothd[7564]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[7564]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[7564]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[7564]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[7564]: audio.conf: Key file does not have key 'Master'
bluetoothd[7564]: SEP 0xb8139508 registered: type:0 codec:0 seid:1
bluetoothd[7564]: Adding record with handle 0x10005
bluetoothd[7564]: Record pattern UUID 00000019-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 0000110a-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 0000110d-0000-1000-8000-00805f9
bluetoothd[7564]: avrcp_server_probe: path /org/bluez/7564/hci0
bluetoothd[7564]: audio_adapter_ref(0xb8138378): ref=3
bluetoothd[7564]: audio.conf: Key file does not have key 'Master'
bluetoothd[7564]: Adding record with handle 0x10006
bluetoothd[7564]: Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 0000110c-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[7564]: Adding record with handle 0x10007
bluetoothd[7564]: Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[7564]: Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[7564]: Creating device /org/bluez/7564/hci0/dev_00_24_33_98_D2_E3
bluetoothd[7564]: btd_device_ref(0xb813a530): ref=1
bluetoothd[7564]: Probe drivers for /org/bluez/7564/hci0/dev_00_24_33_98_D2_E3
bluetoothd[7564]: Adapter /org/bluez/7564/hci0 has been enabled
bluetoothd[7564]: Computer is classified as desktop
bluetoothd[7564]: Setting 0x000104 for major/minor device class
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)
bluetoothd[7564]: adapter_get_device(00:24:33:98:D2:E3)seems to work now what?
- Amelandbor - 2009-11-14
kitlaan Wrote:Weird...
Is there a "/etc/init.d/bluetooth" ?
If all else fails, we can just do a "killall bluetoothd".
Here's my personal input.conf
Should I be able to just put that file in the directory??
- ould - 2009-11-14
Can anyone recommend a known working dongle to purchase. I have one that refuses to work with the PS3 remote for some reason and I have another one that came with my MS Mouse/Keyboard that works fine on the same computer with the same settings, basically I just swap the dongles and the remote magically works, problem is I need the MS dongle to use with the keyboard/mouse on another PC. So before I buy another one just wanted to see if anyone had one they can recommend that is easy to come by. I see lots of cheap prices ones on ebay but again I don't want to buy another one to have the same issue.
Thanks,
Kevin
- kitlaan - 2009-11-14
@ould:
I've been using a kensington mini adapter: http://us.kensington.com/html/14409.html
@Amelandbor:
You should be able to create the file "input.conf" there and be able to use it fine.
@menno:
I'm looking through the code to try to match up what's in your log. It looks like it is going through the right steps, but it never gets to device registration. I may put out a new jaunty package that has a lot more debugging prints later, if I get lost in the code.
- Amelandbor - 2009-11-14
Well it didn't work for me. But I'll wait till the new xbmc stable release and then I will do a fresh install for my complete system.