Bluetooth support in Oleg's firmware?

Moreover I'm getting the following error:

Code:

---

[admin@(none) dbus-1]$ dbus-daemon --system
Unknown username "root" in message bus configuration file

---

I've changed /opt/etc/dbus-1/system.conf file as described but this doesn't help for me:

Code:

---

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

  <!-- Our well-known bus type, do not change this -->
  <type>system</type>

  <!-- Run as special user -->
  <user>admin</user>

  <!-- Fork into daemon mode -->
  <fork/>

  <!-- Write a pid file -->
  <pidfile>/opt/var/run/dbus/pid</pidfile>

  <!-- Only allow socket-credentials-based authentication -->
  <auth>EXTERNAL</auth>

  <!-- Only listen on a local socket. (abstract=/path/to/socket
      means use abstract namespace, don't really create filesystem
      file; only Linux supports this. Use path=/whatever on other
      systems.) -->
  <listen>unix:path=/opt/var/run/dbus/system_bus_socket</listen>

  <policy context="default">
    <!-- Deny everything then punch holes -->
    <deny send_interface="*"/>
    <deny receive_interface="*"/>
    <deny own="*"/>
    <!-- But allow all users to connect -->
    <allow user="*"/>
    <!-- Allow anyone to talk to the message bus -->
    <!-- FIXME I think currently these allow rules are always implicit
        even if they aren't in here -->
    <allow send_destination="org.freedesktop.DBus"/>
    <allow receive_sender="org.freedesktop.DBus"/>
    <!-- valid replies are always allowed -->
    <allow send_requested_reply="true"/>
    <allow receive_requested_reply="true"/>
  </policy>

  <!-- Config files are placed here that among other things, punch
      holes in the above policy for specific services. -->
  <includedir>system.d</includedir>

  <!-- This is included last so local configuration can override what's
      in this standard file -->
  <include ignore_missing="yes">system-local.conf</include>

  <include if_selinux_enabled="yes" selinux_root_relative="yes">contexts/dbus_contexts</include>

</busconfig>

---

After adding user name "root" I managed to start dbus. But I still have a problem with pairing

In this case PIN is not requested at all:

Code:

---

[admin@(none) 00:0B:0D:21:33:61]$ hcitool cc 00:01:E3:5F:BC:58
[admin@(none) 00:0B:0D:21:33:61]$ hcitool auth 00:01:E3:5F:BC:58
HCI authentication request failed: Connection timed out

---

When trying rfcomm PIN is asked on phone but is not accepted.

Code:

---

[admin@(none) 00:0B:0D:21:33:61]$ rfcomm connect /dev/ttyU0 00:01:E3:5F:BC:58
Can't connect RFCOMM socket: Connection refused

---

How to solve my problem?

Moreover I tried to define pin_helper in hcid.conf and got in syslog:

Code:

---

Jul 31 21:20:28 hcid[199]: Bluetooth HCI daemon
Jul 31 21:20:28 hcid[199]: Unknown option 'pin_helper' line 26
Jul 31 21:20:28 hcid[199]: syntax error line 26

---

Any ideas?

How's this going I would love to have my mobile connect to the internet via bluetooth.

Jippie

Hi folks,

thanks to the hints in this thread I got my dongle working. I can search for other devices and the ASUS is recognized by others.

But as I'm not that familiar with linux I had no idea where to put the module-files. I insmod-ed them from opt-temp. but where to put them correctly?

And how to manage that the bluetooth-device works after a reboot?
do I have to put all that in the postboot?

Code:

---

insmod /opt/tmp/modules/bluez.o #main
insmod /opt/tmp/modules/l2cap.o #for pinging
insmod /opt/tmp/modules/rfcomm/rfcomm.o #virtal serial port
#insmod /opt/tmp/modules/bnep.o #Sound (I don't need that)
insmod /opt/tmp/modules/hci_usb.o #driver

rm /opt/var/run/dbus/pid #if you don't delete it, dbus won't start!
dbus-daemon --system
hcid
hciconfig hci0 up piscan
sdpd
sdptool add --channel 2 SP

---

hm, I just made a reboot and executed all that commands manually - but it only worked when I unplugged the bt-dongle, replugged it and excecuted the lines again.

-->Isn't there a more comfortable way to enable BT after a reboot?

(My final goal is to have an interface on my mobile for controlling the music the router plays (over JAMSE & a bemused-server). I will open up another thread for that - but now i have to go to the cinema :) )