I added that line to my modprobe.conf file, but saw no difference when I
rebooted. I have noticed, which may be just coincidence, that if I have
my usb mouse plugged in, the system seems to respond to hciconfig:
hci0: Type: USB
BD Address: 00:1C:26:F0:75:6D ACL MTU: 1017:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:59892 acl:3596 sco:0 events:89 errors:0
TX bytes:1166 acl:34 sco:0 commands:38 errors:0
Is there any way to restart without rebooting? The output from
/var/log/messages, first when the system configures and adds hci0, and
when it does not, is attached. Any help?
don
Donald Reader wrote:
On Thu, 2008-01-24 at 17:17 -0700, don fisher wrote:
I am running F8 on a Dell 1721 laptop. After I boot, and run hciconfig,
sometimes there is output, and other time none. Can anybody please
inform me if anything required in modprobe.conf. I would also like to
know where hcid is spawned from, etc. I have restarted
/etc/init.d/bluetooth and was not able to detect any change.
I have a Buetooth mouse and keyboard. When there is output from
hciconfig, I can connect the devices.
Can somebody please help me with what needs to be configured?
Thanks
don
Try putting this "options hci_usb reset=1" into /etc/modprobe.conf and
see if it
helps any for you. I was having a similar issue and that help clear it
up for me
Don R
Jan 22 20:12:41 dfpc64 acpid: starting up
Jan 22 20:12:42 dfpc64 hcid[2360]: Bluetooth HCI daemon
Jan 22 20:12:42 dfpc64 kernel: Bluetooth: L2CAP ver 2.8
Jan 22 20:12:42 dfpc64 kernel: Bluetooth: L2CAP socket layer initialized
Jan 22 20:12:42 dfpc64 hcid[2360]: HCI dev 0 registered
Jan 22 20:12:42 dfpc64 hcid[2360]: Starting SDP server
Jan 22 20:12:42 dfpc64 hcid[2360]: Created local server at unix:abstract=/var/run/dbus-28cB78Z6Gb,guid=bd5ed17957e80d89204a9c004796b0aa
Jan 22 20:12:42 dfpc64 kernel: Bluetooth: RFCOMM socket layer initialized
Jan 22 20:12:42 dfpc64 kernel: Bluetooth: RFCOMM TTY layer initialized
Jan 22 20:12:42 dfpc64 kernel: Bluetooth: RFCOMM ver 1.8
Jan 22 20:12:42 dfpc64 hcid[2360]: HCI dev 0 up
Jan 22 20:12:42 dfpc64 hcid[2360]: Device hci0 has been added
Jan 22 20:12:42 dfpc64 input[2373]: Bluetooth Input daemon
Jan 22 20:12:42 dfpc64 input[2373]: Registered input manager path:/org/bluez/input
Jan 22 20:12:43 dfpc64 hcid[2360]: Starting security manager 0
Jan 22 20:12:43 dfpc64 hcid[2360]: Device hci0 has been activated
Jan 22 20:12:43 dfpc64 input[2373]: Created input device: /org/bluez/input/pointing0
Jan 24 14:49:11 dfpc64 acpid: starting up
Jan 24 14:49:11 dfpc64 hcid[2271]: Bluetooth HCI daemon
Jan 24 14:49:11 dfpc64 kernel: Bluetooth: Core ver 2.11
Jan 24 14:49:11 dfpc64 kernel: NET: Registered protocol family 31
Jan 24 14:49:11 dfpc64 kernel: Bluetooth: HCI device and connection manager initialized
Jan 24 14:49:11 dfpc64 kernel: Bluetooth: HCI socket layer initialized
Jan 24 14:49:12 dfpc64 kernel: Bluetooth: L2CAP ver 2.8
Jan 24 14:49:12 dfpc64 kernel: Bluetooth: L2CAP socket layer initialized
Jan 24 14:49:12 dfpc64 hcid[2271]: Starting SDP server
Jan 24 14:49:12 dfpc64 hcid[2271]: Created local server at unix:abstract=/var/run/dbus-u2NYHuHWzi,guid=ff32772da081de9f6fc85b00479907d8
Jan 24 14:49:12 dfpc64 kernel: Bluetooth: RFCOMM socket layer initialized
Jan 24 14:49:12 dfpc64 kernel: Bluetooth: RFCOMM TTY layer initialized
Jan 24 14:49:12 dfpc64 kernel: Bluetooth: RFCOMM ver 1.8
Jan 24 14:49:12 dfpc64 input[2290]: Bluetooth Input daemon
Jan 24 14:49:12 dfpc64 input[2290]: Registered input manager path:/org/bluez/input
Jan 24 14:49:13 dfpc64 input[2290]: Created input device: /org/bluez/input/pointing0
