Kodi Community Forum

Full Version: [LINUX] Sony PlayStation 3 Blu-ray Disc Remote (PS3 BD) + LIRC + XBMC = SUCCESS
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
LAGMonkey Wrote:*facepalm*

Yep, that did the trick. Although i have added the command "hciconfig hci0 reset" to my rc.local (at the bottom just above "exit 0") im still having to issue it once ive loaded to desktop in order to get everything going. Any ideas about how i can get the command issued later in the boot cycle?

I've noticed that the "Prev" and "Next" buttons are the opposite way round (Prev skips forward - Next skips backward).

But apart from all that, thank you for the effort. Its really appreciated Nod

If you still need help with getting hci reset during startup, remove it from rc.local and instead add

"options hci_usb reset=1" to /etc/modprobe.d/options
I completely reinstalled my ASRock ION, but still have the unable to get on d-bus problem. Will this be easier to install when I do a full Ubuntu install?? And is it going to work then when I start Xbmc direct after the boot.
I guess at first you need to get bluez working. What tells
ps axu | grep dbus
? what is content of /etc/dbus-1/system.d/bluetooth.conf ?
Output of ps axu | grep dbus
Quote:103 2338 0.2 0.0 2672 1096 ? Ss 21:58 0:00 /bin/dbus-daemo n --system
xbmc 2911 0.0 0.0 4784 604 ? Ss 21:58 0:00 /usr/bin/ssh-ag ent /usr/bin/dbus-launch --exit-with-session sh /home/xbmc/.xsession
xbmc 2914 0.0 0.0 3144 688 ? S 21:58 0:00 /usr/bin/dbus-l aunch --exit-with-session sh /home/xbmc/.xsession
xbmc 2915 0.0 0.0 2672 736 ? Ss 21:58 0:00 //bin/dbus-daem on --fork --print-pid 5 --print-address 7 --session
xbmc 2995 0.0 0.0 3356 816 pts/0 S+ 21:59 0:00 grep dbus

And this is the content of bluetooth.conf
Quote:<!-- This configuration file specifies the required security policies
for Bluetooth core daemon to work. -->

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>

<!-- ../system.conf have denied everything, so we just punch some holes -->

<policy user="root">
<allow own="org.bluez"/>
<allow send_destination="org.bluez"/>
<allow send_interface="org.bluez.Agent"/>
</policy>

<policy at_console="true">
<allow send_destination="org.bluez"/>
</policy>

<!-- allow users of lp group (printing subsystem) to
communicate with bluetoothd -->
<policy group="lp">
<allow send_destination="org.bluez"/>
</policy>

<policy context="default">
<deny send_destination="org.bluez"/>
</policy>

</busconfig>
and now
awk -F: '/x:103:/ {print $0; system("grep " $4 " /etc/group")}' /etc/passwd
Output:
Quote:messagebus:x:103:111::/var/run/dbus:/bin/false
messagebus:x:111:
that looks ok, now try to execute bluetoothd with
sudo /usr/sbin/bluetoothd -nd
and see if it runs successfully or exits with error
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
what do
dbus-send --print-reply --system --dest=org.bluez / org.bluez.Manager.DefaultAdapter
and
ps axu | egrep 'blue|hci'
say?
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
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
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
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)
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.
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-as...e-control/

Maybe I have to wait for the new Ubuntu to get it working from the CLI.