Dell True Mobile 350

Maksim Yevmenkin maksim.yevmenkin at savvis.net
Fri May 13 10:20:50 PDT 2005


Paolo,

> i just got a brand new Dell Inspiron 6000 with a 
> Dell Truemobile 350 card.
> 
> This is my verbose dmesg:

[...]

> ugen0: Dell product 0x8103, rev 2.00/16.57, addr 2

you need to load ng_ubt(4) driver. you can do it at loader prompt

load ng_ubt

or modify your /etc/loader.conf and add

ng_ubt_load="YES"

please see handbook for more details

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bluetooth.html

> and i thought it's my bluetooth device so i added
> 
> product DELL TRUEMOBILE350      0x8103   TrueMobile 350 (Bluetooth)
> 
> recompiled & installed a new kernel and the next boot i got:
> 
> ugen0: Dell TrueMobile 350 (Bluetooth), rev 2.00/16.57, addr 2

adding "product" line is only going to make usb to show device's human 
readable name instead of id.

> but even if i load ng_ubt i don't get any device in /dev.
> 
> [flag at longino ~]$ kldstat | grep ubt
> 15    1 0xc222d000 b000     ng_ubt.ko
> [flag at longino ~]$ ls /dev/*ubt*
> ls: /dev/*ubt*: No such file or directory
> [flag at longino ~]$

ng_ubt(4) _does_not_ create any nodes in /dev. it will only create 
netgraph(4) node. use "ngctl li" (as root) to see if you have "ubt0" 
netgraph node. also look into /var/log/messages to see if ng_ubt(4) 
attached to your device.

also if your device was already claimed by ugen(4) then ng_ubt(4) 
_will_not_ attach to it. you need to load ng_ubt(4) _before_ attaching 
the device, or re-plug the device to make sure ng_ubt(4) gets it.

thanks,
max


More information about the freebsd-bluetooth mailing list