Launchpad has imported 45 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=519176.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/268502
Title:
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
To manage notifications about this
** Changed in: bluez (Debian)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/268502
Title:
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
To
found the same issue still,
#sudo hciconfig hci0 down
nothing happened-- no logs in hcidump, shouldn't device should send any
DOWN/reset command to controller ?
#sudo hciconfig hci0 up
from the hcidump logs , device host sends reset command but controller does
not respond with hci command
any news on this? I have ubuntu 12.10 and latest kernel:
Linux Roller 3.2.0-39-generic #62-Ubuntu SMP Thu Feb 28 00:28:53 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ubuntu 12.04
3.2.0-30-generic-pae
lsusb
Bus 004 Device 004: ID 1131:1001 Integrated System Solution Corp. KY-BT100
Bluetooth Adapter
syslog
Aug 25 12:38:28 apple bluetoothd[4008]: HCI dev 0 unregistered
Aug 25 12:38:28 apple bluetoothd[4008]: Stopping hci0 event socket
Aug 25 12:38:28 apple
Users of Cambridge Silicon Radio bluetooth devices should also be aware
that there is another bug (launchpad #460743) that causes a problem with
these devices. We may be experiencing compounded problems with those
devices.
--
You received this bug notification because you are a member of Ubuntu
Still happens here, while we're stuck on 2.6.31, the userspace is
Maverick at today's latest updates. It can't be an HCI 1.1 problem
because this one is 2.1, and it has a default link policy :)
hci0: Type: BR/EDR Bus: USB
BD Address: 00:22:43:D9:D7:84 ACL MTU: 1021:8 SCO MTU: 64:1
** Changed in: linux
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/268502
Title:
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
--
ubuntu-bugs
** Changed in: bluez (Debian)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/268502
Title:
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
--
I just tried the bluez 4.32 downgrade workaround on Ubuntu 10.10 and the
basics work ok with Blueman but I hit a serious issue:
Dec 21 21:14:21 linux bluetoothd[1375]: link_key_request
(sba=00:22:43:D3:50:4D, dba=00:23:7F:81:DC:01)
Dec 21 21:14:21 linux bluetoothd[1375]: link_key_request
I have tested this on Karmic, Lucid and Maverick and continued to find
this problem (timeout). After some googling and debugging, I found this
bug #453885 specifying in detail and also the workaround from that bug.
First, here's the workaround for those (like me) who want to get
bluetooth working
Workaround does not work for Lucid 32bit running 2.6.35.4 kernel.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I just tried the above workaround that I posted (going back to
bluez-4.32) on plain Maverick amd64 (actually a Kubuntu 10.10
installation) and it did work (which was not working earlier with the
same timeout problem). On Kubuntu, since bluedevil does not have any
dependencies with bluez -- unlike
I tried your workaround on Maverick @Srinivasa here. No luck here.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@Srinivasa What kernel are you using? Others mentioned that this also
seems to have an effect on the bug.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Matt - Karmic kernel version was amd64 2.6.31-16-generic. Maverick
kernel version was amd64 2.6.35-22-generic.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs,
I can confirm this issue for Ubuntu Lucid x86-64. I have a Super Mini Bluetooth
2.0 Adapter USB Dongle which is identified as Accel-OB2, Manufacturer
Cambridge Silicon Radio (10). After booting the dongle works, but after a
while the connection is lost and I get the time out message. I also
Sorry to be the bearer of bad news, but the problem persists here as
well. Please note that there is a bug in linux-firmware-nonfree. In
order to get even this far, I had to manually symlink
/lib/firmware/bcm2033-fw.bin and /lib/firmware/bcm2033-md.hex to
BCM2033-FW.bin and BCM2033-MD.hex.
Crap, forgot to mention - Lucid x86-64.
Linux shadwickt-desk 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20
14:21:58 UTC 2010 x86_64 GNU/Linux
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are
Same issue with usb BT dongle from Cambridge Silicon Radio (0a12:0001)
and kernel 2.6.31 (x86_64 arch).
$ uname -a
Linux oem-desktop 2.6.31-22-generic #60-Ubuntu SMP Thu May 27 02:41:03 UTC 2010
x86_64 GNU/Linux
$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002
Sorry, I am same user as comment #288 (previous one), I forgot:
$ hciconfig -a
hci0: Type: USB
BD Address: 00:1F:81:00:02:50 ACL MTU: 1021:4 SCO MTU: 180:1
UP RUNNING PSCAN
RX bytes:1477 acl:0 sco:0 events:54 errors:0
TX bytes:426 acl:0 sco:0 commands:39
I am using Debian (squeeze/testing) and I am testing with kernel 2.6.32-5-486
. I am getting the timeout here, so I reckon this is still broken in Debian
(squeeze) testing:
# hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address:
same issue on kernel 2.6.34. I've just tested.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have the same problem
distribution: Ubuntu 10.04 LTS
kernel: 2.6.32-23-generic
bluez 4.60-0ubuntu8
Bus 002 Device 004: ID 0a5c:2021 Broadcom Corp.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification
No changes with last bluez version:
Package: bluez
State: installed
Automatically installed: no
Version: 4.65-0ubuntu1
I've also tried 4.66 - same problem.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug
Can confirm this - Lucid 10.04, Version: 4.60-0ubuntu8 2.6.32-22-generic
Bus 005 Device 022: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug
Hmm... Same PC, another dongle (noname):
Integrated System Solution Corp. Bluetooth Device
- works like a charm.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs,
I have same bug. Ubuntu 10.04, bluez 4.60-0ubuntu8.
ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
# hciconfig -a
hci0: Type: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX
i had no problem with karmic. since update to lucid it doesn't work. i
will try clean install, bue i doubt it will solve something
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member
opposite experience here: finally works in Lucid for the first time
ever, All seems to work, from file browsing and moving filesa across to
one-click internet connection via mobile phone
On 20/05/10 19:07, Selmi wrote:
i had no problem with karmic. since update to lucid it doesn't work. i
will
You don't have to reinstall to do a clean test. You can just boot the
livecd session and test there.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch added: Red Hat Bugzilla #519176
https://bugzilla.redhat.com/show_bug.cgi?id=519176
** Also affects: linux (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=519176
Importance: Unknown
Status: Unknown
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx
Bug is still in Lucid as 14May2010.
If fix released, where it is?
LP #460743 (https://bugs.edge.launchpad.net/fedora/+source/linux/+bug/460743)
Should be merged with this one.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received
** Changed in: linux (Ubuntu)
Assignee: Brian Rogers (brian-rogers) = (unassigned)
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The latest I have tried is to uninstall gnome-bluetooth and install
bluez-gnome. This allowed me to actually connect to the serial port
with the '1234' code. It now shows up in BT manager with a totally
different dialog graphics and commands, but it seems to be more robust
at least for this pair.
Hi Keith :)
I think you thought that by clicking on Fix Commited it would have an
effect on your machine. I guess you know now that bug-report threads
are a convenient way for people working on solving the bug to
communicate with each other and keep track of progress and the current
state of
Tom ,
Thanks! I did not think that the 'fix committed' worked like that, but
was looking through the thread for a fix that someone said worked and
a response saying, yes, worked for me, too.
On a whim, I added the repository
http://ppa.launchpad.net/blueman/ppa/ubuntu karmic main and then ran
an
Well, I just tried the serial port. I do not think this is part of this
bug, though, as it will not allow me to select the 1234 paring number
that my serial port needs. What I did was click on the device in the BT
manager, then select the pin option and select 1234 then clicked
connect. At that
** Changed in: linux (Ubuntu)
Status: Fix Released = Fix Committed
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Please don't change bug statuses without explanation.
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of
Ok, I have read tons of these posts about defective bluetooth support in
gnome/kernel. What is the fix? Can I try something? Do we have any idea
as to when this may be pushed to the updater for 9.10? I have been
patient for a couple of months and still nothing works. Dongle shows up,
It can see
On Sun, Mar 28, 2010 at 12:59:57AM -, KeithG wrote:
Ok, I have read tons of these posts about defective bluetooth support in
gnome/kernel. What is the fix? Can I try something? Do we have any idea
as to when this may be pushed to the updater for 9.10?
The fix for this bug was present in
This bug is present for at least 9.4, it is still present, no actual
bug fix was posted.
Never explained, the issue persist allways, execpt for a few persons
that i was able to see that posted that somehow, with some device
worked, never for me.
2010/3/27 Steve Langasek
Steve Langasek wrote: The fix for this bug was present in Ubuntu 9.10
when it released. If you are having issues with bluetooth in 9.10, you
should file a separate bug report.
For me and probably most others effected by that original general bug
the problem was solved. So it is time to focus on
Hi, I confirm this bug.
I've done a full report on Bug #493747:
[KARMIC] Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
(Broadcom dongle)
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/493747
Didn't work on Lucid too (19.04 alpha)
--
Bluetooth doesn't work
** Changed in: linux (Ubuntu Intrepid)
Assignee: Stefan Bader (stefan-bader-canonical) = (unassigned)
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm still getting hci_cmd_task: hci0 command tx timeout on Karmic.
I can transfer one file, but as soon as a second file starts, it stops the
transfer after 2 seconds or ~50 KB of transmitted data.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
** Changed in: bluez (Ubuntu Jaunty)
Status: Invalid = Fix Committed
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: bluez (Ubuntu Jaunty)
Status: Fix Committed = Invalid
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I think I rebooted after installing blueman from PPA. But it is not
clear how exactly did it help, so I guess it can be not helpful in your
case. Just had to share my experience.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received
Thanks diskin, i just installed from PPA and rebooted but still not
working..
REgards!
2010/1/13 Dmitry Diskin dis...@gmail.com:
I think I rebooted after installing blueman from PPA. But it is not
clear how exactly did it help, so I guess it can be not helpful in your
case. Just had to share
BT (KY-BT100 dongle) worked right after fresh install of Karmic, then I
installed blueman from Karmic repositories, and seems that it caused the
above problems. Tried to remove blueman completely - did not help.
Booting from standard Karmic live CD - BT worked. The problem was solved
after
I've added deb http://ppa.launchpad.net/blueman/ppa/ubuntu karmic main
and ran apt-get update;apt-get install blueman, it removed
gnome-bluetooth but i'm still having timeout messages.
Could you please explain a bit longer how did you manage to solve it?
Thanks!
2010/1/12 Dmitry Diskin
Mythbuntu 9.10 here. Same problems as everyone else.
$ lsusb | grep -i blue
Bus 004 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.10
DISTRIB_CODENAME=karmic
DISTRIB_DESCRIPTION=Ubuntu 9.10
$
** Tags added: iso-testing
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same symptoms here after an upgrade from 9.04 to 9.10 and same detected device
for my BT dongle.
What I do to have it work is
* unplugging the usb dongle,
* $ sudo modprobe -r btusb
* plugg the donggle again
* pray for the BT applet to become enabled
* else unplugging
* ...
After a moment I
I just upgraded my distribution from 9.04 to 9.10 and I'm still
experiencing kinda the same as in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268502/comments/252.
My bluetooth dongle is:
$ lsusb | grep -i blue
Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
Success! Fixed for me on Ubuntu 9.10 Karmic-beta Live-CD
See Bug #133690
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: bluez (Debian)
Status: Fix Committed = New
** Changed in: bluez-utils (Debian)
Status: Fix Committed = New
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a
Hi, I'm also affected by this bug. This seems to have been fixed. Where
to I find the fix? What do I need to do? I'm quite new to launchpad so
please excuse me I'm missing something. I'm using Ubuntu 9.04.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
If you have an up-to-date kernel in Intrepid or Jaunty, you should have
the fix that was released. Unfortunately, the error message is rather
generic, and could indicate just about any problem with communicating
with the dongle. I was hoping the one fix would cover most people who
were getting
Confirmed on 2.6.28-15 with the following dongle:
Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)
I can pair a device using the dongle, but any time I attempt any kind of
communication, I get the timeout.
--
Bluetooth doesn't work (hci_cmd_task: hci0
This bug was fixed in the package linux - 2.6.27-14.41
---
linux (2.6.27-14.41) intrepid-proposed; urgency=low
[ Stefan Bader ]
* Revert SAUCE: input: Blacklist digitizers from joydev.c
- LP: #300143
linux (2.6.27-14.40) intrepid-proposed; urgency=low
[ Amit Kucheria ]
Have updated kernel to 2.6.28-11-generic but still get:
Connecting to device 00:07:61:05:91:90.
Can't get device information Device information: Connection
timed out
Tried the various codes like , 1234, , etc. to no avail.
Can't tell you much about the dongle except it's a cheap,
I am running jaunty 9.04 2.6.28-15 with bluez 4.42 and still having issues.
tryied with several kernel ranging from 2.6.27-11 , 2.6.28-11 and 2.6.29.6 with
bluez 4.32 and bluez 4.42 having the same results.
Sometimes the dongle is well recognized and can pair, and transfer files, some
other
Bruce,
The fix is in Jaunty's 2.6.28-11.39 Linux kernel. If you have all the
updates, then you should have the fix. To double-check, uname -r
should report something newer than 2.6.28-11-generic. So if you still
have problems, then you're being affected by a separate issue and should
file a new
Brian,
I still have this problem with my dongle (0a12:0001 Cambridge Silicon
Radio, Ltd Bluetooth Dongle (HCI mode)). What bug should I subscribe to?
Jaunty 2.6.28-14-generic right now.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You
Ok. Yesterday, a new kernel as well as a new bluez version came to
karmic, and then I was able to send a picture to my phone as well as
listening to music via A2DP. so either these updates fixed it, or it's
another problem.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
I am running Karmic 64bit - 2.6.31-5-generic #24-Ubuntu SMP Sat Aug 1
12:47:58 UTC 2009 x86_64 GNU/Linux
A word of warning I found the latest release of Bluez, 4.48 very
unstable and have reverted back to 4.45-0ubuntu4, this was in
combination with kernel 2.6.31-6, in combination with
** Changed in: linux (Ubuntu Jaunty)
Status: Fix Released = Fix Committed
** Changed in: linux (Ubuntu Jaunty)
Status: Fix Committed = New
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification
** Changed in: linux (Ubuntu Jaunty)
Status: New = Fix Released
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
A fix for one Bluetooth issue has already been committed and released,
so Fix Released is the proper state for this bug report.
If you still have the same symptoms even with the fix and have reported
one of the bugs that is marked as a duplicate of this one, you can
undupe your own bug report and
Am I stupid or something? Where, pray tell, can I find this fix?
Bruce
On Aug 16, 2009, at 7:45 AM, Brian Rogers wrote:
A fix for one Bluetooth issue has already been committed and released,
so Fix Released is the proper state for this bug report.
If you still have the same symptoms even
Hi!
I have one of these dongles:
ID 1131:1004 Integrated System Solution Corp. Bluetooth Device
I saw this message: hci_cmd_task: hci0 command tx timeout
and several of these: btusb_bulk_complete: hci0 urb ef171800 failed to resubmit
(1)
I am running karmic with linux 2.6.31-5-generic. Is
Exactly the same as Matthijs.
Same dongle, same hciconfig status (UP RUNNING ... strange) and same dmesg.
Jaunty x86_64
I've installed 2.6.29 kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29.6/
Having read that patches have been applied to 2.6.29-rc3
Is it the good place to
** Attachment removed: rc_local-bluetooth.diff
http://launchpadlibrarian.net/24206436/rc_local-bluetooth.diff
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs,
I also have this problem in 9.04.
dmesg:
[ 1572.852058] usb 2-1: new full speed USB device using uhci_hcd and address 4
[ 1573.008758] usb 2-1: configuration #1 chosen from 1 choice
[ 1578.026633] hci_cmd_task: hci0 command tx timeout
[ 1583.031905] hci_cmd_task: hci0 command tx timeout
** Changed in: bluez-utils (Debian)
Status: New = Fix Committed
** Changed in: bluez (Debian)
Status: New = Fix Committed
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a
** Branch linked: lp:ubuntu/karmic/linux-rt
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Another one with a not working Bluetooth connection:
bluez-4.45
kernel-2.6.30.1
When I try to connect to my Playstatio 3 remote i often get this
problem. I'm really tiered of this.:
input: Sony Computer Entertainment Inc BD Remote Control as
Thanks Håkon!
The script does not work, but adding one more command makes it work on
my Sony-Ericsson K850i. I'll be adding details to bug #336012, which is
the proper place for it.
I had it confused with the hci_cmd_task: hci0 command tx timeout
because I have seen that too, occasionally,
** Branch linked: lp:ubuntu/karmic/linux-ports
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Jamie: Did you try using the script that I have attached to bug #336012:
http://bugs.launchpad.net/ubuntu/+source/bluez/+bug/336012/comments/4
The point is to enable encryption before making the PAN connection. Note
that you have to use a script because timing is very important, baseband
Unfortunately updating Bluez doesn't work for me.
I've tried updating Bluez from 4.32 to 4.40 as per the suggestion.
Specifically, these packages from Debian:
bluetooth_4.40-2_all.deb
bluez_4.40-2_i386.deb
bluez-alsa_4.40-2_i386.deb
bluez-compat_4.40-2_i386.deb
I can confirm that Bluez 4.32 to 4.40 fixed my problem, as per Dominique
Meeùs' suggestion. This is with a Broadcom dongle, USB ID: 0a5c:200a.
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you
Good news:
I bought a Belkin Mini Bluetooth Adapter (only 12€) and hooked it up to my USB
port on my PC.
And guess what? Everything ran flawless!
- USB/Bluetooth device automatically detected. (Bluetooth applet showed
automatically in the top pannel)
- Bluetooth user/password sequence passed
** Tags added: hw-specific
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Problem solved with bluez 4.40 - My Broadcom dongle now works.
lsusb output:
Bus 003 Device 002: ID 0a5c:200a Broadcom Corp. Bluetooth dongle
Ubuntu 9.04 Jaunty
kernel 2.6.28-13-generic
I can now connect to my Nokia N70 phone, my Nokia 770 Internet Tablet
and my Nokia LD-3W Bluetooth GPS
I can also confirm that bluez 4.40 fixed my bluetooth after months of
not working (9.04 AMD64 with latest kernel). All I did was follow
Dominique's instructions above and used 'amd64' instead of 'i386'.
lsusb:
Bus 001 Device 008: ID 047d:105d Kensington PocketMouse Bluetooth
Bus 001 Device 005:
DBT-122 also working here now, with Debian packages (AMD64, 9.04)
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
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.
--
output from lsusb:
ID 0a5c:200a Broadcom Corp. Bluetooth dongle
Still does not work with kernel 2.6.28-13-generic on jaunty
# hcitool scan
Scanning ...
Inquiry failed: Connection timed out
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
I just did boot back in 2.6.28 (2.6.28-12-generic #43-Ubuntu SMP Fri May 1
19:27:06 UTC 2009 i686).
My D-Link DBT-122 (ID 2001:f111) works as expected. This confirms that, for
this dongle, Bluez 4.00 to 4.32 was the problem and Bluez 4.40 the solution,
not the kernel. (Mind the fact that there
For some dongles (as my D-Link DBT-122), there little or no kernel
problem, but a Bluez problem.
This is what I did concretely:
— display http://http.us.debian.org/debian/pool/main/b/bluez/
— click libbluetooth3_4.40-2_i386.deb and simply accept installation by GDebi
— idem with
Accepted linux into intrepid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
Bluez 4.40 works for me, using this:
gnome-obex-send -d XX:XX:XX:XX:XX:XX '/home/maximi89/Foto curriculo.png'
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi, bluez 4.40 fix my problem, please closes this bug, i use gnome-obex-
send:
gnome-obex-send -d XX:XX:XX:XX:XX:XX '/home/maximi89/Foto curriculo.png'
works mostly, kernel 2.6.30-rc6 fix the problem of hci0 tx timeout
ID 1131:1004 Integrated System Solution Corp. Bluetooth Device
[
** Changed in: bluez (Debian)
Status: Unknown = New
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
i update to kernel 2.6.30-rc6 on Debian, and bluez 4.34-0exp1 and now i
can ping and scan devices, and the error hci0 tx timeout disappear, but
still not working...
i can't use or transfers files...
ID 1131:1004 Integrated System Solution Corp. Bluetooth Device
--
Bluetooth doesn't work
1 - 100 of 261 matches
Mail list logo
