Bug#525220:

Sorry Dominique, but i'm running Debian, and i have an another device: Bus 002 Device 003: ID 1131:1004 Integrated System Solution Corp. Bluetooth Device [ 57.235079] Bluetooth: Core ver 2.14 [ 57.236915] NET: Registered protocol family 31 [ 57.236977] Bluetooth: HCI device and connection manager i

Bug#525220:

Maximi89 a écrit ce qui suit, le 03/05/09 21:47 : maxim...@maximiliano:~$ sudo dpkg -l | grep bluez : ii bluez 4.35-0ubuntu1 I wrote this on one line to keep the message shorter. After : ii etc. is the result. You have to understand it as sudo dpkg -l | grep bluez iibluez4.35-0u

Bug#525220:

Works great on old kernel, Linux Maximiliano 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686 GNU/Linux [ 29.676030] eth0: no IPv6 routers present [ 30.792584] Bluetooth: L2CAP ver 2.9 [ 30.792584] Bluetooth: L2CAP socket layer initialized [ 30.844260] Bluetooth: RFCOMM socket layer initiali

Bug#525220:

2009/5/3 Dominique Meeùs > Maximi89 a écrit ce qui suit, le 03/05/09 21:47 : > >> maxim...@maximiliano:~$ sudo dpkg -l | grep bluez : ii bluez >> 4.35-0ubuntu1 >> > I wrote this on one line to keep the message shorter. After : ii etc. is > the result. You have to understand it as > sudo dpkg -l |

Bug#525220:

Le 04/05/09 05:20, Maximi89 a écrit : 2009/5/3 Dominique Meeùs > In your case too, there is no more "hci0 command tx timeout" with bluetooth stopped. in my case i have a lot if i try to transfers files with bluetooth-applet Do you mean to transfer files

Bug#525220:

Sorry Dominique, when i have hcid stopped i can't do nothing, i try with a tip, umount /proc/bus/usb works some times... but few minuts more later this stop to work too i still can't transfers files or do any thing. i hear some thing about in newer version of bluez this works... what do you k

Bug#525220:

Dominique, you can try to to transfers files umount /proc/bus/usb http://osdir.com/ml/linux.bluez.user/2003-07/msg00129.html https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268502 Greetings! -- Maximiliano Augusto Castañón Araneda Santiago, Chile Linux user # 394821

Bug#525220: End Of Year Promo!

The DOVE Foundation. 69 Chapel Street, London W1B 4DA. United Kingdom. Dear Recipient, RE: Grant Notification. This is an official notification to you by the board of trustees of The DOVE Foundation as one of the recipients of cash Grant Award for your personal business and community development.

Bug#525220: Bluetooth problem caused by fake dongles?

Hello! I also have a problem with Bluetooth. I have recently bought a new USB dongle in the store (instead of on ebay) that does not seem to have this problem. The funny thing is that the USB IDs are identical, so the two devices claim to be identical as well. What also makes me wonder is th

Bug#525220: Bluetooth problem caused by fake dongles?

--- On Tue, 21/6/11, Alexander Heinz wrote: > I also have a problem with Bluetooth. I have recently > bought a new USB dongle in the store (instead of on ebay) > that does not seem to have this problem. The funny thing is > that the USB IDs are identical, so the two devices claim to > be identica

Bug#525220: Bluetooth problem caused by fake dongles?

My mobile phone showed up as present on one of the release candidate kernels, so mine is not fake. We could always borrow a friends laptop that runs Micros~1youknowwhat and test the dongles for operation. I am not saying that my dongle does not work at all. What I am saying is that my dongle

Bug#525220: Bluetooth problem caused by fake dongles?

--- On Tue, 21/6/11, Alexander Heinz wrote: > The USB IDs corresponds to CSR but the > chip label says ASC AS3620QA. This is a counterfeit. > > Is very easy to tell. Just open your dongle and check the > label on the chip. Bloody hell Alex. I just took your advise and opened the dongle. And woa

Bug#525220: Bluetooth problem caused by fake dongles?

On Tue, 2011-06-21 at 22:07 +0100, Mark Hobley wrote: > --- On Tue, 21/6/11, Alexander Heinz wrote: > > > The USB IDs corresponds to CSR but the > > chip label says ASC AS3620QA. This is a counterfeit. > > > > Is very easy to tell. Just open your dongle and check the > > label on the chip. > >

Bug#525220: Bluetooth problem caused by fake dongles?

--- On Wed, 22/6/11, Ben Hutchings wrote: > There is a standard USB 'device class' for Bluetooth > adapters, which are all handled by the 'btusb' driver. Right. So does that mean that there is a chance that these devices might work in future? Or do we need to be shopping round for replacement a

Bug#525220: Bluetooth problem caused by fake dongles?

On Wed, Jun 22, 2011 at 04:07:00PM +0100, Mark Hobley wrote: > --- On Wed, 22/6/11, Ben Hutchings wrote: > > > There is a standard USB 'device class' for Bluetooth > > adapters, which are all handled by the 'btusb' driver. > > Right. So does that mean that there is a chance that these devices mi

Bug#525220: Nano Tiny USB 2.0 Bluetooth Adapter

orporation" in China. The first three bytes of the MAC address reflect these as being made by Accel Semiconductor Corporation. Currently, these devices do not work in Linux and cause an HCI Timeout error (as reported in Kernel bug #10126, Debian bug #525220 and Launchpad #460743). It appears

Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

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

Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

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 BR

Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

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 errors:0

Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

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-kernel-requ...@lists.debian.org with a

Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

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

Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

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 no

Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

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-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.o

Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

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

Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

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] h

Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

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 GNU/Li

Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

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 recko

Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

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 RU

Bug#525220: Bluetooth trouble with hci_cmd_task: hci0 command tx timeout

--- On Mon, 16/8/10, mailsanm...@gmx.li wrote: > I have the same problem with the same type of Bluetooth > dongle (even my MAC address is the same). Were you able to > work around this problem? Do you have any working > combination of kernel and bluez that enables you to actually > use this dongl

Bug#525220: Fw: Re: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

--- On Sat, 11/12/10, Ben Hutchings wrote: > Please report this bug upstream at under > product 'Drivers', component 'Bluetooth'.  Let us know > the bug number or URL so we can track it. Issue tracking numbers relating to this bug are: Linux kernel team #10126 Laun

Bug#525220: D-Link DBT-122 still does not work correctly

I am not shure, is this right place for my report, but i will try... Trying copy photo from my phone with FUSE obexfs: Bus 003 Device 003: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter bluez: Установлен: 4.63-2 Кандидат: 4.63-2 Таблица версий: *** 4.63-2 0 Linux home 2.6.32-

Bug#525220: D-Link DBT-122 still does not work correctly

On Sat, 2010-05-22 at 21:44 +0400, Sergey Burladyan wrote: > I am not shure, is this right place for my report, but i will try... > > Trying copy photo from my phone with FUSE obexfs: [...] Please report a separate bug against obexfs. Ben. -- Ben Hutchings Once a job is fouled up, anything don

Bug#525220: marked as done (Bluetooth Device: hci_cmd_task: hci0 command tx timeout)

system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 525220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: Linux-image-2.6.29-1-686 Version: 2.6.29-3 I tr

Bug#525220: D-Link DBT-122 DOES work OK with Bluez 4.40-2

In the case of ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter, it seems that it was not so much a kernel bug than a bluez bug: It still does NOT work with kernel 2.6.29 and the regular Bluez 4.3x from the Ubuntu distribution. It DOES work OK with Bluez 4.40-2 from Debian. -- To

Bug#525220: D-Link DBT-122 DOES work OK with Bluez 4.40-2

On Wed, Jun 10, 2009 at 12:07:56AM +0200, Dominique Meeùs wrote: > In the case of ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth > adapter, it seems that it was not so much a kernel bug than a bluez > bug: > > It still does NOT work with kernel 2.6.29 and the regular Bluez 4.3x > from the Ubunt