** Bug watch added: Debian Bug tracker #525220
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525220
** Package changed: linux-latest-2.6 (Debian) = linux-2.6 (Debian)
** Changed in: linux-2.6 (Debian)
Importance: Undecided = Unknown
** Changed in: linux-2.6 (Debian)
Status: New
I'm fighting the same issues with the same dongle. Mine looks exactly
like the Sabrent unit, except the Sabrent name is missing.
http://www.sabrent.com/category/wireless/BT-USBT/
lapdog ~ # lsusb
Bus 002 Device 009: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)
lapdog ~
Hi to everyone, (for Gustavo... I sent you a message abput the same
argument... sorry for the duplication)
I hope there are new about this bug
I am using a board (VDX6318D) by Icop Technologies with their linux
2.6.34.1-vortex86-sg.
The dongle I use is Sena Parani UD100 (that uses Cambridge
Dear Mark,
I am sorry I cannot open my dongle with a screwdriver, it is the only one I
have. But my dongle seems to work and it says that is a
ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
The only problem is that once is connected does not appear as a possible
output of sound.
I am
After opening up one of my dongles with a screwdriver, I discovered that there
is a marking on the board AS3620QA1. This appears to be a code for Accel
Semiconductor, so the devices that are causing an error may not be made by
Cambridge Silicon Radio after all, even though the devices list as
Gustavo, could you test if your dongle can wake system up from S3 suspend?
If so, it would be cool to get full model name, so that I can find it's foto.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
bam,
I've tried it and didn't work. Maybe I need to install some package or
configure something else.
I'm running Ubuntu 10.10 64 bits and I put the computer in S3 through
SSH using this command (after a sudo su):
echo -n mem /sys/power/state
I could see that the system went in sleep and then
Today I bought a new dongle. It's ID 0a12:0001 Cambridge Silicon Radio, Ltd
Bluetooth Dongle (HCI mode) too, but it works well. I've no tx timeout errors
and all the packages are from de offical repos.
It's a dongle made in China too, it's mini as the other one, but the format
is different.
I'm doing some tests on Ubuntu Maverick server 10.10 64 bits
2.6.35-28-generic.
My dongle is:
ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
I've removed all packages related to bluetooth. Then, I installed ONLY
bluez and bluez-alsa (with libbluetooth3). All version 4.69
No luck. After installing bluez-gstreamer and start to use aplay and mplayer,
the problem arise.
So, I went back to the original state having only bluez and bluez-alsa, but the
problem persisted.
I can't believe this problem still exists. I've read a lot of posts on
the net and they are from a
Using a 2.6.39 series kernel and bluez 4.93-1, a timeout error occurs as
I try to bring the interface into operational mode:
hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO
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
Hello,
I believe the problem is with the configuration.
I have 2 ubuntus (2HDD) in my pc in one (ubuntu 10.10) is working the bluetooth
in the other not (ubuntu 11.04), I am geting the following error Connection
refused (111). how may I copy the configuration of the bluettoth that is
working in
Hello,
I have tried with new kernel 2.6.32-29-generic #58-Ubuntu SMP Fri Feb 11
19:00:09 UTC 2011 i686 GNU/Linux
I have the following problem: Failed to find Bluetooth netlink family
here is the output:
06/03/2011:
Dear all,
the bluetooth adapter ID 0a12:0001 Cambridge Silicon Radio, is working,
I have just tested this again with experimental kernel 2.6.38-rc6. The
problem does not occur during intial status enquiry, but a timeout
occurs, when an attempt is made to activate the bluetooth device:
hciconfig -a
hci0: Type: BR/EDR
FWIW hcitool does nothing for me:
hcitool dev
Devices:
(nothing is listed here)
hcitool scan
Device is not available: No such device
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
cannot pair ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI
mode) in ubuntu 10.04
i have a USB Bluetooth dongle of the Cambridge Silicon Radio type, USB ID
0a12:0001. When I plug it into my machine it's detected properly, Bluetooth
services
are started, I get the icon in the
** 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/460743
Title:
[LucidKarmic] Cambridge Silicon Radio, Bluetooth Dongles do not work
--
** Changed in: linux
Status: Unknown = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/460743
Title:
[LucidKarmic] Cambridge Silicon Radio, Bluetooth Dongles do not work
--
I have just tested this again in Debian using experimental kernel
version 2.6.37 (rc5). The timeout error still occurs, so this does not
appear to be fixed.
hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address:
Appears to be host dependent.
I have 2 machines 1: Acer 4315 laptop 2:emachines (acer) em350 netbook
(recently acquired).
Both intel based, both running current 10.04 kernel 2.6.32-25-generic
I have a bag of 10 identical bluetooth dongles.
On #1, I almost always get the timeout error and can
I have this device working on an Asus P5VD2-VM based machine running
10.10 32 bit. Strangely however it works only if plugged in a front USB
port. It does not work either in the motherboard's rear ports or in a
PCI-to-USB card's. I am available to test if useful.
** Attachment added: lspci.txt
** Attachment added: lsusb.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/460743/+attachment/1695718/+files/lsusb.txt
--
[LucidKarmic] Cambridge Silicon Radio, Bluetooth Dongles do not work
https://bugs.launchpad.net/bugs/460743
You received this bug notification because you are a
I confirm it, it's not a hardware issue. Triad the same dongle under
Windows, worked fine. Under Ubuntu 10.04 it responds to hciconfig eth1
up hciconfig eth1 down hciconfig eth1 up for a few seconds and
then throws the Can't init device hci1: Connection timed out (110)
error.
--
[LucidKarmic]
I have Maverick i386 beta (updated today, and the micro dongle listed below
works) but with my Lucid x86_64 also updated today, I get the same timed out
error as listed by all above.
I have run 'apport-collect -p linux 460743'
Maverick beta is on Acer Aspire One A110 Atom N270, 1.5 Gig RAM, 8
I have just tested this in Debian using 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
I'm facing the same problem on Lucid 64.with latesr official kernel.
The dongle seems to work after booting, can pair bt devices but suddenly
doesn't respond anymore and give connection timed out.
I want to add that I was able to test another dongle from my friend with the
same chipset, and
** Also affects: linux-latest-2.6 (Debian)
Importance: Undecided
Status: New
--
[LucidKarmic] Cambridge Silicon Radio, Bluetooth Dongles do not work
https://bugs.launchpad.net/bugs/460743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I am using Debian kernel linux-image-2.6.32-5-486.
I get the following error in /var/log/kern.log:
Jul 14 13:36:53 foobar kernel: [ 1229.790869] hci_cmd_task: hci0 command
tx timeout
(Ticket #144)
--
[LucidKarmic] Cambridge Silicon Radio, Bluetooth Dongles do not work
FWIW: The following bluetooth adapters are not working:
NANO TINY USB 2.0 BLUETOOTH ADAPTER DONGLE EDR WIRELESS
Part number 500792110001
Barcode 200529837
Bus 003 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)
--
[LucidKarmic] Cambridge Silicon Radio,
In a Hardy too,
sil...@mrburns:~$ lsusb
...
Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)
...
dmesg
[ 62.067574] Clocksource tsc unstable (delta = -191287866 ns)
[ 62.400430] Bluetooth: L2CAP ver 2.9
[ 62.400435] Bluetooth: L2CAP socket
The bluetooth worked fine two hours ago.
--
[LucidKarmic] Cambridge Silicon Radio, Bluetooth Dongles do not work
https://bugs.launchpad.net/bugs/460743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same dongle, same problem. Any news?
--
[LucidKarmic] Cambridge Silicon Radio, Bluetooth Dongles do not work
https://bugs.launchpad.net/bugs/460743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have reproduced this bug in Lucid running a mainstream kernel:
Linux shaneubuntu 2.6.34-020634-generic #020634 SMP Mon May 17 19:27:49 UTC
2010 x86_64 GNU/Linux
I tried disabling the autosuspend temporarily for my device but that didn't
seem to make any difference.
echo on | sudo tee
in lucid too
--
[LucidKarmic] Cambridge Silicon Radio, Bluetooth Dongles do not work
https://bugs.launchpad.net/bugs/460743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Tried the workaround listed above usbcore.autosuspend=0, and am afraid
it didn't work for me. Symptoms are the same, Connection timed out.
--
[LucidKarmic] Cambridge Silicon Radio, Bluetooth Dongles do not work
https://bugs.launchpad.net/bugs/460743
You received this bug notification because you
There is a workaround: adding usbcore.autosuspend=0 to Kernel command line.
But that solution unacceptable for portable machines and should be treated in
Linux.
--
[LucidKarmic] Cambridge Silicon Radio, Bluetooth Dongles do not work
https://bugs.launchpad.net/bugs/460743
You received this bug
** Bug watch added: Linux Kernel Bug Tracker #10126
http://bugzilla.kernel.org/show_bug.cgi?id=10126
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=10126
Importance: Unknown
Status: Unknown
--
[LucidKarmic] Cambridge Silicon Radio, Bluetooth Dongles do not
** 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
--
[LucidKarmic] Cambridge Silicon Radio, Bluetooth Dongles
39 matches
Mail list logo
