+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Help and Support (/forumdisplay.php?fid=33)
+--- Forum: XBMC General Help and Support (/forumdisplay.php?fid=111)
+---- Forum: Linux and Live support (/forumdisplay.php?fid=52)
+---- Thread: [LINUX] Sony PlayStation 3 Blu-ray Disc Remote (PS3 BD) + LIRC + XBMC = SUCCESS (/showthread.php?tid=50717)
- Amelandbor - 2009-10-25 23:47
Output:
Quote:messagebus:x:103:111::/var/run/dbus:/bin/false
messagebus:x:111:
- ruff - 2009-10-25 23:55
that looks ok, now try to execute bluetoothd with
sudo /usr/sbin/bluetoothd -nd
and see if it runs successfully or exits with error
- Amelandbor - 2009-10-26 00:02
hmm
Quote:sudo: /usr/sbin/bluetoothd: command not found
I do have bluetoothd in /usr/local/sbin
which gives the exact same error.
Quote:bluetoothd[3510]: Bluetooth daemon 4.54
bluetoothd[3510]: Enabling debug information
bluetoothd[3510]: parsing main.conf
bluetoothd[3510]: discovto=0
bluetoothd[3510]: pairto=0
bluetoothd[3510]: pageto=8192
bluetoothd[3510]: name=%h-%d
bluetoothd[3510]: class=0x000100
bluetoothd[3510]: discov_interval=0
bluetoothd[3510]: Key file does not have key 'DeviceID'
bluetoothd[3510]: Unable to get on D-Bus
- ruff - 2009-10-26 08:10
what do
dbus-send --print-reply --system --dest=org.bluez / org.bluez.Manager.DefaultAdapter
and
ps axu | egrep 'blue|hci'
say?
- Amelandbor - 2009-10-26 08:41
dbus-send --print-reply --system --dest=org.bluez / org.bluez.Manager.DefaultAdapter
Quote:method return sender=:1.7 -> dest=:1.14 reply_serial=2
object path "/org/bluez/2887/hci0"
ps axu | egrep 'blue|hci'
Quote:root 2887 0.0 0.0 3464 1532 ? Ss 07:38 0:00 /usr/local/sbin/bluetoothd
xbmc 3079 0.0 0.0 3348 824 pts/0 R<+ 07:41 0:00 egrep blue|hci
- ruff - 2009-10-26 14:43
so you have another instance of bluetoothd already running. Try to shut that instance down and run it manually with debug, i.e.
sudo kill -9 `ps ax|grep bluetoothd | grep -v grep | awk '{print $1}'`
sudo /usr/local/sbin/bluetoothd -nd
- Amelandbor - 2009-10-26 15:11
After that I don't get back to the command line.
This is the output:
Quote:xbmc@ION:~$ sudo /usr/local/sbin/bluetoothd -nd
bluetoothd[5460]: Bluetooth daemon 4.54
bluetoothd[5460]: Enabling debug information
bluetoothd[5460]: parsing main.conf
bluetoothd[5460]: discovto=0
bluetoothd[5460]: pairto=0
bluetoothd[5460]: pageto=8192
bluetoothd[5460]: name=%h-%d
bluetoothd[5460]: class=0x000100
bluetoothd[5460]: discov_interval=0
bluetoothd[5460]: Key file does not have key 'DeviceID'
bluetoothd[5460]: Starting SDP server
bluetoothd[5460]: Loading builtin plugins
bluetoothd[5460]: Loading audio plugin
bluetoothd[5460]: Loading input plugin
bluetoothd[5460]: Loading serial plugin
bluetoothd[5460]: Loading network plugin
bluetoothd[5460]: Loading service plugin
bluetoothd[5460]: Loading hciops plugin
bluetoothd[5460]: Loading hal plugin
bluetoothd[5460]: Loading storage plugin
bluetoothd[5460]: Loading plugins /usr/local/lib/bluetooth/plugins
bluetoothd[5460]: register_interface: path /org/bluez/5460/any
bluetoothd[5460]: Registered interface org.bluez.Service on path /org/bluez/5460 /any
bluetoothd[5460]: Parsing /etc/bluetooth/network.conf failed: No such file or di rectory
bluetoothd[5460]: Config options: InterfacePrefix=bnep%d, PANU_Script=(null), GN _Script=(null), NAP_Script=(null), GN_Interface=pan0, NAP_Interface=pan1, Securi ty=true
bluetoothd[5460]: Can't create GN bridge
bluetoothd[5460]: Parsing /etc/bluetooth/input.conf failed: No such file or dire ctory
bluetoothd[5460]: Parsing /etc/bluetooth/audio.conf failed: No such file or dire ctory
bluetoothd[5460]: Unix socket created: 9
bluetoothd[5460]: Telephony plugin initialized
bluetoothd[5460]: HFP AG features: "Ability to reject a call" "Enhanced call sta tus" "Extended Error Result Codes"
bluetoothd[5460]: HCI dev 0 registered
bluetoothd[5460]: child 5461 forked
bluetoothd[5460]: btd_adapter_ref(0xb8feda90): ref=1
bluetoothd[5460]: HCI dev 0 up
bluetoothd[5460]: Starting security manager 0
bluetoothd[5460]: Changing Major/Minor class to 0x000104
bluetoothd[5460]: Stopping Inquiry at adapter startup
bluetoothd[5460]: register_interface: path /org/bluez/5460/hci0
bluetoothd[5460]: Registered interface org.bluez.Service on path /org/bluez/5460 /hci0
bluetoothd[5460]: network_server_probe: path /org/bluez/5460/hci0
bluetoothd[5460]: btd_adapter_ref(0xb8feda90): ref=2
bluetoothd[5460]: Adding record with handle 0x10000
bluetoothd[5460]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001115-0000-1000-8000-00805f9
bluetoothd[5460]: register_server_record: got record id 0x10000
bluetoothd[5460]: Registered interface org.bluez.NetworkPeer on path /org/bluez/ 5460/hci0
bluetoothd[5460]: network_server_probe: path /org/bluez/5460/hci0
bluetoothd[5460]: Adding record with handle 0x10001
bluetoothd[5460]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001117-0000-1000-8000-00805f9
bluetoothd[5460]: register_server_record: got record id 0x10001
bluetoothd[5460]: Registered interface org.bluez.NetworkHub on path /org/bluez/5 460/hci0
bluetoothd[5460]: network_server_probe: path /org/bluez/5460/hci0
bluetoothd[5460]: Adding record with handle 0x10002
bluetoothd[5460]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001116-0000-1000-8000-00805f9
bluetoothd[5460]: register_server_record: got record id 0x10002
bluetoothd[5460]: Registered interface org.bluez.NetworkRouter on path /org/blue z/5460/hci0
bluetoothd[5460]: proxy_probe: path /org/bluez/5460/hci0
bluetoothd[5460]: btd_adapter_ref(0xb8feda90): ref=3
bluetoothd[5460]: Registered interface org.bluez.SerialProxyManager on path /org /bluez/5460/hci0
bluetoothd[5460]: Parsing /etc/bluetooth/serial.conf failed: No such file or dir ectory
bluetoothd[5460]: btd_adapter_ref(0xb8feda90): ref=4
bluetoothd[5460]: headset_server_probe: path /org/bluez/5460/hci0
bluetoothd[5460]: btd_adapter_ref(0xb8feda90): ref=5
bluetoothd[5460]: audio_adapter_ref(0xb8fef098): ref=1
bluetoothd[5460]: Adding record with handle 0x10003
bluetoothd[5460]: Record pattern UUID 00000003-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001108-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001112-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001203-0000-1000-8000-00805f9
bluetoothd[5460]: Adding record with handle 0x10004
bluetoothd[5460]: Record pattern UUID 00000003-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 0000111e-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 0000111f-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001203-0000-1000-8000-00805f9
bluetoothd[5460]: a2dp_server_probe: path /org/bluez/5460/hci0
bluetoothd[5460]: audio_adapter_ref(0xb8fef098): ref=2
bluetoothd[5460]: SEP 0xb8ff0218 registered: type:0 codec:0 seid:1
bluetoothd[5460]: Adding record with handle 0x10005
bluetoothd[5460]: Record pattern UUID 00000019-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 0000110a-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 0000110d-0000-1000-8000-00805f9
bluetoothd[5460]: avrcp_server_probe: path /org/bluez/5460/hci0
bluetoothd[5460]: audio_adapter_ref(0xb8fef098): ref=3
bluetoothd[5460]: Adding record with handle 0x10006
bluetoothd[5460]: Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 0000110c-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[5460]: Adding record with handle 0x10007
bluetoothd[5460]: Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[5460]: Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[5460]: Adapter /org/bluez/5460/hci0 has been enabled
bluetoothd[5460]: Failed to open RFKILL control device
bluetoothd[5460]: Entering main loop
bluetoothd[5460]: Inquiry Failed with status 0x12
bluetoothd[5460]: child 5461 exited
bluetoothd[5460]: Computer is classified as desktop
bluetoothd[5460]: Setting 0x000104 for major/minor device class
- ruff - 2009-10-26 23:13
so daemon runs ok, it is able to get dbus connection and you can proceed with registering the remote, since I don't see any org.bluez.Input device created.
Just in case, fyi - you can get can get console back by hitting ctl-c.
And then run it in normal way (/etc/init.d/bluetooth or whatever is written in manual)
- Amelandbor - 2009-10-27 00:32
Well I did get the remote connected finally.
First I did get another problem.
Quote:"DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."But I was able to fix this by adding:
Quote: <limit name="max_connections_per_user">256</limit>to /etc/dbus-1/system.conf
But after registering the device, I don't get any output from it.
- Amelandbor - 2009-10-27 03:32
Well I thought I might try it in a full Ubuntu installation and there it works like a charm.
I used this tutorial: http://popey.com/blog/2009/08/06/acer-aspire-revo-ubuntu-boxee-and-remote-control/
Maybe I have to wait for the new Ubuntu to get it working from the CLI.