hi everyone,
i've gotten working on laptop bluetooth on 10.10 setup. know system detects there internal bluetooth adapter isn't correctly configuring or using it. here background, dm1z comes ralink wifi / motorola bc8 3.0+ adapter bluetooth. combo wasn't detected system on fresh install i've managed confgure wifi driver bluetooth thing. problem have dm1z internal bluetooth not turning on bluetooth discovering something. here feedback bluez stack.
code:$ hciconfig -a hci0: type: br/edr bus: usb bd address: 90:00:4e:a4:63:ec acl mtu: 310:10 sco mtu: 64:8 running pscan iscan rx bytes:1579 acl:0 sco:0 events:45 errors:0 tx bytes:1874 acl:0 sco:0 commands:43 errors:0 features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x87 packet type: dm1 dm3 dm5 dh1 dh3 dh5 hv1 hv2 hv3 link policy: rswitch hold sniff park link mode: slave accept name: 'user-hp-dm1z-0' class: 0x580100 service classes: capturing, object transfer, telephony device class: computer, uncategorized hci version: 3.0 (0x5) revision: 0x1aa1 lmp version: 3.0 (0x5) subversion: 0x1aa1 manufacturer: cambridge silicon radio (10)code:$ hcitool dev devices: hci0 90:00:4e:a4:63:eccode:$ hcitool info 90:00:4e:a4:63:ec device not available or not connected.code:$ hcitool name 90:00:4e:a4:63:ec device not available.which leads me believe bluez stack can't configure combo wifi/bluetooth driver. have similar problem or fix? responses!!!code:$ hcitool scan scanning ... $
-red
i think i've found fix it, based on information bug registered meego at: https://bugs.meego.com/show_bug.cgi?id=3498
solution execute following command (needs executed sudo):
bccmd psset -s 0x0000 0x028c 0x0001
doing allows bt adapter see other devices turning on radio, appears bt device active, radio not. setting appears stay in device long remains powered on. in order avoid having manually input command every time power on machine, embedded command within init.d script bluetooth daemon, @ /etc/init.d/bluetooth. i'm running ubuntu 11.04 64-bit, , here's script looks (the modification right below comment containing "ralink"):
#! /bin/sh
### begin init info
# provides: bluetooth
# required-start: $local_fs $syslog $remote_fs dbus
# required-stop: $local_fs $syslog $remote_fs
# default-start: 2 3 4 5
# default-stop: 0 1 6
# short-description: start bluetooth daemons
### end init info
#
# bluez bluetooth subsystem starting , stopping
#
# bluez's scripts/bluetooth.init
#
# edd dumbill <ejad@debian.org>
# lsb 3.0 compilance , enhancements filippo giunchedi <filippo@debian.org>
#
# updated bluez 4.7 mario limonciello <mario_limonciello@dell.com>
#
# note: older daemons dund pand hidd shipped inside the
# bluez-compat package
path=/sbin:/bin:/usr/sbin:/usr/bin
desc=bluetooth
daemon=/usr/sbin/bluetoothd
test -f /usr/sbin/bluetoothd || exit 0
test -f /etc/default/rcs && . /etc/default/rcs
. /lib/lsb/init-functions
set -e
case "$1" in
start)
#currently init script exists because of appears be
#an egg , chicken problem
# bluetoothd starts udev rules. needs dbus function,
# dbus doesn't start until after udev finishes triggering
#
log_daemon_msg "starting $desc"
# powers on bluetooth radio. needed the
# ralink bluetooth facilities in order work properly.
bccmd psset -s 0x0000 0x028c 0x0001
if [ ! -f /sbin/udevadm.upgrade ]; then
udevadm trigger --subsystem-match=bluetooth --action=add
log_progress_msg "bluetoothd"
fi
log_end_msg 0
;;
stop)
log_daemon_msg "stopping $desc"
pkill -term bluetoothd || true
log_progress_msg "bluetoothd"
log_end_msg 0
;;
restart|force-reload)
$0 stop
sleep 1
$0 start
;;
status)
status_of_proc "$daemon" "$desc" && exit 0 || exit $?
;;
*)
n=/etc/init.d/bluetooth
# echo "usage: $n {start|stop|restart|reload|force-reload|status}" >&2
echo "usage: $n {start|stop|restart|force-reload|status}" >&2
exit 1
;;
esac
exit 0
# vim:noet
Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [SOLVED] dm1z : bluetooth not discoverable
Ubuntu
Comments
Post a Comment