dongle recognized as keyboard (?)

Maksim Yevmenkin maksim.yevmenkin at savvis.net
Wed Nov 17 11:55:17 PST 2004


Hi,

> My bluetooth dongle is automatically being recognized has a keyboard
>  (a /dev/ukbd0 is created but NO /dev/ubt0),  whereas I want to use
> it to connect to a mobile phone (see log bellow).
> 
> This is a real nag since I am left without keyboard and have no way
> to type whenever I plug the dongle.
> 
> I am using 5.3-release. In 5.2.1 this did not happen.
> 
> Any ideas, please? Am I am missing something?

well, for once adjust your /etc/devd.conf (or /etc/usbd.conf if you are 
running usbd(8)) to NOT activate usb keyboard by default. you should be 
looking for lines like

# When a USB keyboard arrives, attach it as the console keyboard
attach 100 {
         device-name "ukbd0";
         action "test -c /dev/kbd1 && kbdcontrol -k /dev/kbd1 < 
/dev/console";
};
detach 100 {
         device-name "ukbd0";
         action "kbdcontrol -k /dev/kbd0 < /dev/console";
};

same for the usb mouse

# The entry below starts moused when a mouse is plugged in. Moused
# stops automatically (actually it bombs :) when the device disappears.

device "Mouse"
         devname "ums[0-9]+"
         attach "/etc/rc.d/moused start ${DEVNAME}"

> I have two USB plugs (Compaq laptop): one has a Tecom BT3033A dongle,
> the other has nothing:
> 
> uhci0: <VIA 83C572 USB controller> port 0x1800-0x181f irq 5 at device
> 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: <VIA 83C572 USB controller>
> on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0,
> rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered 

ok that is hub on motherboard

> uhub1: Broadcom product 0x3535, class 9/0, rev 2.00/1.00, addr 2 
> uhub1: 3 ports with 0 removable, bus powered ubt0: Broadcom Corp

ok that is hub(!) on your dongle

> Bluetooth Transceiver, rev 1.10/1.00, addr 3
 > ubt0: Broadcom Corp Bluetooth Transceiver, rev 1.10/1.00, addr 3 
ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
> ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320

ok that looks like normal bluetooth dongle

 > ukbd0: Broadcom product 0x0099, rev 1.10/1.00, addr 4, iclass 3/1 
kbd1 at ukbd0

whoa! that looks like usb keyboard!

 > ums0: Broadcom product 0x0097, rev 1.10/1.00, addr 5, iclass 3/1 
ums0: 3 buttons

whoa! that looks like usb mouse!

well, i got to have this specimen in my lab. from what i can see the 
dongle gives 3 (!) interfaces.

1) bluetooth usb dongle (ubt0)

2) bluetooth keyboard (ukbd0)

3) bluetooth mouse (ums0)

all 3 appears active at the same time. this dongle has 'bluetooh hid 
proxy' feature active by default *and* at the same time is still 
accessible via hci. i've never seen anything like this before.

from what i can see all 3 interfaces are recognized, so everything 
should work. and, btw there is no /dev/ubt0, so dont worry about it. try 
to run

# ngctl li

and you should see ubt0 netgraph node. if you do then just run

# rc.bluetooth start ubt0

everything should be working.

your keyboard is switched to ukbd0 (by default) and that is why you have 
to change /etc/devd.conf and/or /etc/usbd.conf. if you had bluetooth 
keyboard then it would work just like usb keyboard.

hope that helps,
max


More information about the freebsd-bluetooth mailing list