FC8 Bluetooth/hcid initialization at boot(forgot attachment)
Donald Reader
fc-list at reader.ws
Sat Jan 19 12:24:02 UTC 2008
On Fri, 2008-01-18 at 19:22 -0800, Donald Reader wrote:
> Howdy All
>
> I have upgraded to FC8 to help solve some bluetooth issues
> that I posted about earlier. But now I seem to have a few
> issues with the start up of hcid at boot/reboot
>
> 1) For some reason the scanning modes are not activating
> properly which is causing other issues I believe.
> Although an easy work around is to just issue an
> hciconfig hci0 reset command and they show up.
> I am not sure if this is proper behavior or if it
> happens to be a bug in which case I have not idea
> how to report it LOL.
> Now while investigating this issue I also noticed this
>
> 2) hcid is not finding a file called /etc/bluetooth/audio.conf
> I have googled and tried every other avenue I know of
> to try and figure out if this is a missing file or if
> I need to create it myself. I have been able to figure
> out the functionality of the file but not how to do
> any editing of it or what the structure of the file is.
> 3) Can't read class of device on hci0: Input/output error
> Not sure this the real culprit of the issues or not.
> but the log reads like this.
> Jan 18 13:17:08 dads hcid[2124]: Can't read class of device on hci0:
> Input/output error (5)
> Jan 18 13:17:08 dads hcid[2124]: Getting name failed with status 0x0c
> Jan 18 13:17:08 dads hcid[2124]: Can't read class of device on hci0:
> Input/output error (5)
> Jan 18 13:17:08 dads hcid[2124]: Getting scan enable failed with status
> 0x0c
>
> Anyway I have included a txt file with log entries and some hciconfig
> output along with the hcid.conf and rfcomm.conf file contents in it for
> anyone to look at if they want to. I have kept the text file short as
> possible by putting only the most pertinent info in it.
>
> Once I do a hciconfig reset I do get sound out of my headset although
> I still have an issue with the mic and audio capturing. From what I
> have read online bluez has come up with an update in 3.24 so guess I
> need to wait till fedora releases that update to actually use my
> headset with skype but am getting closer.
>
> Any ideas or suggestions will be greatly appreciated.
>
> Thanks
> Donald Reader
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20080119/76555ff8/attachment-0001.htm>
-------------- next part --------------
Jan 18 13:17:08 dads kernel: usb 2-3.1: new full speed USB device using ohci_hcd and address 7
Jan 18 13:17:08 dads kernel: usb 2-3.1: configuration #1 chosen from 1 choice
Jan 18 13:17:08 dads kernel: Bluetooth: HCI USB driver ver 2.9
Jan 18 13:17:08 dads hcid[2124]: HCI dev 0 registered
Jan 18 13:17:08 dads kernel: usbcore: registered new interface driver hci_usb
Jan 18 13:17:08 dads hcid[2124]: HCI dev 0 up
Jan 18 13:17:08 dads hcid[2124]: Device hci0 has been added
Jan 18 13:17:08 dads hcid[2124]: Starting security manager 0
Jan 18 13:17:08 dads hcid[2124]: Can't read class of device on hci0: Input/output error (5)
Jan 18 13:17:08 dads hcid[2124]: Getting name failed with status 0x0c
Jan 18 13:17:08 dads hcid[2124]: Can't read class of device on hci0: Input/output error (5)
Jan 18 13:17:08 dads hcid[2124]: Getting scan enable failed with status 0x0c
Jan 18 13:17:17 dads gnome-keyring-daemon[2921]: Credentials byte was not nul
Jan 18 13:17:18 dads gnome-keyring-daemon[2921]:last message repeated 5 times
Jan 18 13:17:18 dads pulseaudio[2928]: module-x11-xsmp.c: X11 session manager not running.
Jan 18 13:17:18 dads pulseaudio[2928]: module.c: Failed to load module "module-x11-xsmp" (argument: ""): initialization failed.
Jan 18 13:17:19 dads gnome-keyring-daemon[2921]: Credentials byte was not nul
Jan 18 13:17:20 dads hcid[2124]: Can't read class of device on hci0: Input/output error (5)
Jan 18 13:17:20 dads hcid[2124]: Default passkey agent (:1.23, /org/kde/kbluetooth_1234) registered
Jan 18 13:17:20 dads hcid[2124]: Default authorization agent (:1.23, /org/kde/kbluetooth_auth_1234) registered
Jan 18 13:17:25 dads gnome-keyring-daemon[2921]: Credentials byte was not nul
Jan 18 13:17:25 dads gnome-keyring-daemon[2921]: Credentials byte was not nul
Jan 18 13:17:29 dads audio[2160]: Package PKT_TYPE_CFG_REQ:0
Jan 18 13:17:35 dads gnome-keyring-daemon[2921]: Credentials byte was not nul
Jan 18 13:18:09 dads gnome-keyring-daemon[2921]:last message repeated 2 times
Jan 18 13:18:09 dads hcid[2124]: connect(): Connection timed out (110)
Jan 18 13:18:09 dads audio[2160]: GetRemoteServiceHandles failed: 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.
Jan 18 13:18:09 dads audio[2160]: Unregistered device path:/org/bluez/audio/device1
Jan 18 13:18:09 dads audio[2160]: Package PKT_TYPE_CFG_REQ:0
Jan 18 13:18:34 dads audio[2160]: GetRemoteServiceHandles failed: 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.
Jan 18 13:18:34 dads audio[2160]: Unregistered device path:/org/bluez/audio/device2
Jan 18 13:18:34 dads audio[2160]: Package PKT_TYPE_CFG_REQ:0
Jan 18 13:18:34 dads audio[2160]: GetRemoteServiceHandles failed: Service search in progress
Jan 18 13:18:34 dads audio[2160]: Unregistered device path:/org/bluez/audio/device3
.
.
.
.
Jan 18 13:18:35 dads audio[2160]: Package PKT_TYPE_CFG_REQ:0
Jan 18 13:18:35 dads audio[2160]: GetRemoteServiceHandles failed: Service search in progress
Jan 18 13:18:35 dads audio[2160]: Unregistered device path:/org/bluez/audio/device67
Jan 18 13:18:35 dads audio[2160]: Package PKT_TYPE_CFG_REQ:0
Jan 18 13:18:35 dads audio[2160]: GetRemoteServiceHandles failed: Service search in progress
Jan 18 13:18:35 dads audio[2160]: Unregistered device path:/org/bluez/audio/device68
Jan 18 13:18:49 dads hcid[2124]: connect(): Connection timed out (110)
Jan 18 13:20:30 dads audio[2160]: Package PKT_TYPE_CFG_REQ:0
Jan 18 13:20:55 dads audio[2160]: GetRemoteServiceHandles failed: 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.
Jan 18 13:20:55 dads audio[2160]: Unregistered device path:/org/bluez/audio/device69
Jan 18 13:20:55 dads audio[2160]: Package PKT_TYPE_CFG_REQ:0
Jan 18 13:20:55 dads audio[2160]: GetRemoteServiceHandles failed: Service search in progress
Jan 18 13:20:55 dads audio[2160]: Unregistered device path:/org/bluez/audio/device70
.
.
.
.
Jan 18 13:20:56 dads audio[2160]: Package PKT_TYPE_CFG_REQ:0
Jan 18 13:20:56 dads audio[2160]: GetRemoteServiceHandles failed: Service search in progress
Jan 18 13:20:56 dads audio[2160]: Unregistered device path:/org/bluez/audio/device135
Jan 18 13:20:56 dads audio[2160]: Package PKT_TYPE_CFG_REQ:0
Jan 18 13:20:56 dads audio[2160]: GetRemoteServiceHandles failed: Service search in progress
Jan 18 13:20:56 dads audio[2160]: Unregistered device path:/org/bluez/audio/device136
Jan 18 13:21:10 dads hcid[2124]: connect(): Connection timed out (110)
.
.
.
.
Jan 18 15:16:18 dads audio[2202]: Package PKT_TYPE_CFG_REQ:0
Jan 18 15:16:18 dads audio[2202]: GetRemoteServiceHandles failed: Service search in progress
Jan 18 15:16:18 dads audio[2202]: Unregistered device path:/org/bluez/audio/device272
Jan 18 15:16:32 dads hcid[2166]: connect(): Connection timed out (110)
as can be seen there are also a couple of other interesting things here like
the pulseaudio messages and then there is the gnome-keyring messages (which fill up my log files)
hciconfig shows these results
hci0: Type: USB
BD Address: 00:02:76:0C:D6:03 ACL MTU: 1017:8 SCO MTU: 64:0
UP RUNNING
RX bytes:195 acl:0 sco:0 events:25 errors:0
TX bytes:379 acl:0 sco:0 commands:25 errors:0
hciconfig hci0 reset then hciconfig shows properly
hci0: Type: USB
BD Address: 00:02:76:0C:D6:03 ACL MTU: 1017:8 SCO MTU: 64:0
UP RUNNING PSCAN ISCAN
RX bytes:1137 acl:0 sco:0 events:49 errors:0
TX bytes:972 acl:0 sco:0 commands:49 errors:0
hciconfig -a shows
hci0: Type: USB
BD Address: 00:02:76:0C:D6:03 ACL MTU: 1017:8 SCO MTU: 64:0
UP RUNNING PSCAN ISCAN
RX bytes:1137 acl:0 sco:0 events:49 errors:0
TX bytes:972 acl:0 sco:0 commands:49 errors:0
Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'HeadSet Dongle'
Class: 0x180104
Service Classes: Capturing, Object Transfer
Device Class: Computer, Desktop workstation
HCI Ver: 2.0 (0x3) HCI Rev: 0x4116 LMP Ver: 2.0 (0x3) LMP Subver: 0x430e
Manufacturer: Broadcom Corporation (15)
Now we show the /etc/bluetooth/hcid.conf
options {
autoinit yes;
security user;
pairing multi;
passkey "0000";
}
device {
name "%h-%d";
#class 0x000100;
class 0xff0100;
#pkt_type DH1,DM1,HV1;
iscan enable; pscan enable;
lm accept;
lp rswitch,hold,sniff,park;
}
Contents of /etc/bluetooth/rfcomm.conf
rfcomm0 {
bind no;
device bt_headset_address;(yes it is correct just omitting)
channel 1;
comment "Headset Bluetooth device";
}
More information about the fedora-list
mailing list