Anyone have a USB Bluetooth adapter working?

Message

edoc · #1 Post by **edoc** » Wed 21 Feb 2007, 01:51

I bought a generic brand Bluetooth-to-USB adapter to add Bluetooth to my laptop.

The specs said that it required a driver only for Win98 (because Win98 doesn't
know what USB is) and I understand that the absence of required Win2000 &
WinXP drivers suggests that a device is likely to be Linux-friendly.

I plugged it into my Puppy 2.13 laptop and the yellow light came on but have no idea
what to do next!

I have a just-received Bluetooth GPS which I know to be Linux and gpsdrive -friendly
... so I just need the Bluetooth-to-USB adapter to work!

Help?

edoc · #2 Post by **edoc** » Tue 27 Feb 2007, 21:18

edoc wrote:I bought a generic brand Bluetooth-to-USB adapter to add Bluetooth to my laptop.

I have upgraded to 2.14

USB View shows the adapter in red.

I am not sure how to proceed -- this is preventing use of my Bluetooth GPS.

Any ideas out there, please?

edoc · #3 Post by **edoc** » Mon 05 Mar 2007, 17:25

sh-3.00# mount
/dev/root on /initrd type ext2 (rw)
/dev/hda1 on /initrd/pup_rw type ext2 (rw)
tmpfs on /initrd/mnt/tmpfs type tmpfs (rw)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
none on / type unionfs (rw,dirs=/initrd/pup_rw=rw:/initrd/pup_ro2=ro,debug=4294967295,delete=whiteout)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
none on /proc/bus/usb type usbfs (rw)

edoc · #4 Post by **edoc** » Mon 12 Mar 2007, 04:55

Bump!

Sure could use some direction on this.

Is any successful work being done to get Bluetooth-USB adapters
working for all of the laptops and handhelds out there without
Bluetooth functionality?

Or have I chased down another dead-end rabbit trail?

edoc · #5 Post by **edoc** » Wed 14 Mar 2007, 01:37

The device is highlighted in red in USB Viewer and here is the data provided in the
right column of USB Viewer:

Bluetooth USB Adapter
Speed: 12Mb/s (full)
USB Version: 1.0
Device Class: e0(unk.)
Device Subclass: 01
Device Protocol: 01
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Is: 07b8
Product Id: b02a
Revision Number: 5.25

John Doe · #6 Post by **John Doe** » Wed 14 Mar 2007, 03:04

Hey doc,

I don't know if the kernel driver is in there, but give this a try:

# modprobe hci_usb
# dmabt
# modprobe rfcomm
# hciconfig hci0 up

If that seems to work, you can get the rest here:

http://www.jeremythompson.uklinux.net/RH8-0/Bluez.html

Start around where it says "Testing Time..." after the first horizontal line.

The part above that is for compiling the module in the kernel. We can jump into that later on if it's not already there.

lotech · #7 Post by **lotech** » Wed 14 Mar 2007, 03:11

I've been using Kubuntu with BT DUN to access the internet via my cell phone, I hope Puppy can do the same too.....

John Doe · #8 Post by **John Doe** » Wed 14 Mar 2007, 03:53

Looks like hci_usb (obviously) and rfcomm are there, but dmabt and hciconfig aren't.

I'll see if I can find them.

John Doe · #9 Post by **John Doe** » Wed 14 Mar 2007, 05:31

Here are some alien packages if anyone wants to try and get it to work (I don't have anything bluetooth).

Seems that dmabt is only for Toshiba Laptops (try the above commands and just leave that one out).

Here are the three I got compiled. Let us know what happens.

*Edit. Discussion is moving here with better packages.

tempestuous · #10 Post by **tempestuous** » Wed 14 Mar 2007, 08:42

I compiled those bluetooth libraries and utilities in December -
http://www.murga-linux.com/puppy/viewto ... 5384#85384

But forum member daemon reports that an earlier version WITHOUT dbus is necessary to get his gprs working -
http://www.murga-linux.com/puppy/viewto ... 6314#86314

And forum member debernardis reported how to create the necessary device /dev/rfcomm0 in that same thread, and later created a wiki page -
http://puppylinux.org/wikka/ExperimentalBT/

John Doe · #11 Post by **John Doe** » Wed 14 Mar 2007, 09:20

Thanks for jumping in. I had recalled there were some good threads around here on this but my 10 second attention span prevented me from finding them when searching the forum.

Your packages would be better than mine, as they include the firmware. I downloaded the source for that but forgot to build it. Made it as far as typing 'hciconfig --help' but as I don't have any hardware that slipped my mind.

Looks like a maze in there for setting up different device types. Hopefully we can get some testers in here reporting what they are trying and what is working or not with what type of device they are using.

edoc · #12 Post by **edoc** » Wed 14 Mar 2007, 14:40

John Doe wrote:Thanks for jumping in. I had recalled there were some good threads around here on this but my 10 second attention span prevented me from finding them when searching the forum.

I tried Seach but didn't find it either.

Plus there is a serious problem where a second Search immediately following the first
is not allowed without a waiting period, or has that been fixed?

Anyhow, will see what I can do about getting this working using the suggestions ...
then, of course breaking it!

edoc · #13 Post by **edoc** » Mon 26 Mar 2007, 01:44

John Doe wrote:Hey doc,

I don't know if the kernel driver is in there, but give this a try:

# modprobe hci_usb

Stopped dead at the first step:

sh-3.00# modprobe hci_usb
FATAL: Module hci_usb not found.
sh-3.00#

tempestuous · #14 Post by **tempestuous** » Mon 26 Mar 2007, 10:34

Puppy 2.14 definitely has the hci_usb module.
If you have a frugal HD install, or are running from CD, then Puppy just needs to access the "zdrv" file which contains all additional modules.

But if you have a full HD installation, the zdrv file is not accessed properly, so you need to uncompress the zdrv file and copy its contents into the correct locations.
WhoDo explained how to do this here http://www.murga-linux.com/puppy/viewto ... 1735#91735
When Puppy first gained the new "zdrv" feature with version 2.12, this issue was frequently discussed on the forum.

Beware of older versions, though. The zdrv file in 2.12 does NOT contain bluetooth modules, but the zdrv file in 2.14 DOES.

Alternatively, you could just install the bluetooth modules which I provided here -
http://www.murga-linux.com/puppy/viewto ... 5384#85384

edoc · #15 Post by **edoc** » Mon 26 Mar 2007, 15:41

tempestuous wrote:Puppy 2.14 definitely has the hci_usb module.
If you have a frugal HD install, or are running from CD, then Puppy just needs to access the "zdrv" file which contains all additional modules.

I have no idea what this means. javascript:emoticon(':oops:')

I have a frugal install of 2.14 on my laptop and although USB Viewer
recognizes the USB-Bluetooth adapter it is highlighted in RED and my
Bluetooth GPS fails to connect with it.

tempestuous wrote:Alternatively, you could just install the bluetooth modules which I provided here -
http://www.murga-linux.com/puppy/viewto ... 5384#85384

OK, I loaded all three:

bluetooth-modules-k2.6.18.1.pup
dbus-1.0.2.pup
bluetooth-libs-utils-firmware.pup

No change in the yeoow light on the USB-Bluetooth adapter and no
connection between it and my Bluetooth GPS.

Did I need to do a reboot?

John Doe · #16 Post by **John Doe** » Mon 26 Mar 2007, 15:54

edoc wrote:Did I need to do a reboot?

Give it a try, then do those commands above:

modprobe rfcomm
hciconfig hci0 up

try just 'hciconfig' to probably get a list of rf (bluetooth) devices and make sure it's hci0

edoc · #17 Post by **edoc** » Mon 26 Mar 2007, 16:32

John Doe wrote:
edoc wrote:Did I need to do a reboot?
Give it a try, then do those commands above:

modprobe rfcomm
hciconfig hci0 up

try just 'hciconfig' to probably get a list of rf (bluetooth) devices and make sure it's hci0

sh-3.00# modprobe rfcomm

sh-3.00# hciconfig hci0 up
Can't get device info: No such device
sh-3.00# hciconfig
sh-3.00#

tempestuous · #18 Post by **tempestuous** » Wed 28 Mar 2007, 00:31

You probably need to create the necessary device node first, as debernardis explained.

mknod -m 666 /dev/rfcomm0 c 216 0

edoc · #19 Post by **edoc** » Wed 28 Mar 2007, 01:16

tempestuous wrote:You probably need to create the necessary device node first, as debernardis explained.

mknod -m 666 /dev/rfcomm0 c 216 0

I am afraid that my eyes kinda glazed over before I got that far down his
text, sorry. javascript:emoticon(':oops:')

I ran all of these without error but since the rest of the text was related
to cellphone use I am not certain how to proceed for GPSdrive.

I did observe that the hcid command moved the location of the device
up one level in USB Viewer.

modprobe bluetooth
modprobe l2cap
modprobe rfcomm
modprobe hci_usb

mknod -m 666 /dev/rfcomm0 c 216 0

hcid

edoc · #20 Post by **edoc** » Sat 07 Apr 2007, 00:59

Here is the output of my /proc/bus/usb/devices file:

T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.18.1 ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:1d.7
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms

T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.18.1 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=16 #Cfgs= 1
P: Vendor=0483 ProdID=1307 Rev= 1.70
S: Manufacturer=Generic
S: Product=USBMass Storage Device
S: SerialNumber=ABCDEF0123456789
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 93/900 us (10%), #Int= 1, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.18.1 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.1
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=062a ProdID=0000 Rev= 0.00
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=10ms

T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=07b8 ProdID=b02a Rev= 5.25
S: Product=Bluetooth USB Adapter
C:* #Ifs= 3 Cfg#= 1 Atr=80 MxPwr= 86mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
I: If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.18.1 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=03f0 ProdID=3d11 Rev= 1.00
S: Manufacturer=hp
S: Product=officejet 4200 series
S: SerialNumber=CN555GH39X
C:* #Ifs= 3 Cfg#= 1 Atr=c0 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=cc Prot=00 Driver=(none)
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=81(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms
E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
I: If#= 1 Alt= 0 #EPs= 3 Cls=07(print) Sub=01 Prot=02 Driver=usblp
E: Ad=03(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms
E: Ad=83(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms
E: Ad=84(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
I: If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=07(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms
E: Ad=87(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms
E: Ad=88(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
I: If#= 2 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=d4 Prot=00 Driver=(none)
E: Ad=07(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms
E: Ad=87(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms
E: Ad=88(I) Atr=03(Int.) MxPS= 8 Ivl=10ms

T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=067b ProdID=2303 Rev= 3.00
S: Manufacturer=Prolific Technology Inc.
S: Product=USB-Serial Controller
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 10 Ivl=1ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms

The problem is that it is not correct!

This file has devices recorded that are not currently connected.

Currently connected are a USB mouse, USB printer, USB bluetooth adapter,
and USB-to-CAT adapter cable to an Amateur Radio.

Is there a way to refresh this list? I am guessing that the unnecessary
device information may be interfering with the proper operation of the
USB-Bluetooth adapter and the USB-to-CAT adapter cable.

WDYT, please?

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Anyone have a USB Bluetooth adapter working?

Anyone have a USB Bluetooth adapter working?

Re: Anyone have a USB Bluetooth adapter working?

Re: Anyone have a USB Bluetooth adapter working?

Re: Anyone have a USB Bluetooth adapter working?

Re: Anyone have a USB Bluetooth adapter working?