A strange thing has just happened. I plugged the dongle in to get some
information from it, and when I ran hciconfig, it showed as up running:
hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
UP RUNNING PSCAN
RX
I attached a system trace against #628454, so hopefully, someone can interpret
this and tell us what is going wrong.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I upgraded the kernel to 2.6.39-1 from experimental and rebooted the system.
Initially, After typing hcitool inq, the system showed that my mobile phone was
present, so it appeared as though bluetooth was at least momentarily partially
working. However, from the mobile phone, the computer was
I have just tested this again with experimental kernel 2.6.39-rc4-486 (Debian
2.6.39~rc4-1~experimental.1). The problem is still occuring with that kernel
build:
# hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
DOWN
I have just tested this again with kernel version 2.6.38-rc6-486.
This time, no timeout occurs with hciconfig:
hciconfig -a hci0
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
DOWN
RX bytes:342 acl:0 sco:0 events:10
A! When I try to bring the device into operational mode, the timeout error
occurs, so I guess this is still not fixed in 2.6.38-rc6-486:
hciconfig hci0 up
Can't init device hci0: Connection timed out (110)
Mark.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
I have retested this again. This time with experimental kernel version
2.6.37-rc5 (Debian 2.6.37~rc5-1~experimental.1).
The timeout error is still occuring, so the latest attempts at fixing this have
not worked. THE KERNEL IS STILL BROKEN:
hciconfig -a
On Sat, 2010-12-11 at 21:17 +, Mark Hobley wrote:
I have retested this again. This time with experimental kernel version
2.6.37-rc5 (Debian 2.6.37~rc5-1~experimental.1).
The timeout error is still occuring, so the latest attempts at fixing
this have not worked. THE KERNEL IS STILL
I have just tested this with the experimental kernel version 2.6.36-rc5-486.
I am still getting the timeout error:
hciconfig -a hci0
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
UP
Moritz Muehlenhoff wrote:
The next release of Debian (6.0, code name Squeeze) will be based
on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
us whether the problem persists.
Hello Moritz. I am testing with kernel 2.6.32-5-486
I am getting the timeout here, so I reckon
Mind the fact that there may be different bug with same (hci0 command tx
timeout) symptoms. Mind the fact that it maybe (in some cases) a Bluez
software bug, not necessarily a kernel (btusb) bug.
uname -a : Linux library 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17
01:57:59 UTC 2009 i686
Package: Linux-image-2.6.29-1-686
Version: 2.6.29-3
I try with the commands of
http://www.rolfs.no/2006/08/23/kernel-hci_cmd_task-hci0-command-tx-timeout/
[14797.649773] Bluetooth: Generic Bluetooth USB driver ver 0.4
[14797.649872] usbcore: registered new interface driver btusb
[14807.840215]
12 matches
Mail list logo
