On Thursday 22 July 2010, Carmelo Ferrante wrote:
> Thanks a lot, but no luck!
>
> > > Hi,
> > >
> > > I flashed the latest image of SHR Unstable and now I can't make
> > >
> > > bluetooth to work. Can anyone help me to understand what's my problem,
> > > please?
> > > Some useful information:
> > >
> > > # cat /etc/shr-version
> > > SHR -20100721
> > > Built from branch: org.openembedded.dev
> > > Revision: 8f57e8ee924f945f8d56b74ad3f609de6deaef4c
> > >
> > >
> > > # ps ax | grep bluetooth
> > >
> > > 15 ? S 0:00 [bluetooth]
> > >
> > > 299 pts/0 S+ 0:00 grep bluetooth
> > >
> > > # hcitool scan
> > > Device is not available: No such device
> >
> > Did you turn bluetooth on? The settings app or quick settings is probably
> > easiest.
>
> Bluetooth is on:
>
> # cat /sys/bus/platform/devices/gta02-pm-bt.0/power_on
> 1
>
> > > # ls /etc/init.d/bluetooth
> > >
> > > ls: /etc/init.d/bluetooth: No such file or directory
> >
> > iirc this disappeared with the change to bluez4. It gets started by a
> > combination of hotplugging and/or dbus as necessary.
>
> I read about this on trac:
> http://trac.shr-project.org/trac/ticket/777
> "As BillK fould out, requesting bluethooth resource is now enough to
> start bluez daemon."
>
> But I can't find the bluez daemon on my freerunner:
>
> # find / | grep bluez
> /usr/lib/opkg/info/bluez4.prerm
> /usr/lib/opkg/info/bluez4.control
> /usr/lib/opkg/info/bluez4.list
> /usr/lib/opkg/info/bluez4.postrm
> /usr/lib/opkg/info/bluez4.postinst
> /usr/lib/libebluez-ver-pre-svn-07.so.0
> /usr/lib/enlightenment/modules/bluez
> /usr/lib/enlightenment/modules/bluez/module.desktop
> /usr/lib/enlightenment/modules/bluez/linux-gnueabi-arm-ver-pre-svn-07
> /usr/lib/enlightenment/modules/bluez/linux-gnueabi-arm-ver-pre-svn-07/modul
> e.so /usr/lib/enlightenment/modules/bluez/e-module-bluez.edj
> /usr/lib/libebluez-ver-pre-svn-07.so.0.5.0
It's /usr/sbin/bluetoothd on mine.
> > > # opkg list-installed | grep blue
> > >
> > > bluez4 - 4.59-r7.0.5
> > > task-base-bluetooth - 1.0-r89.5
> > >
> > > # opkg list-installed | grep obex
> > >
> > > libopenobex1 - 1.5-r2.5
> > > obexd - 0.22-r0.5
> > > obexftp - 0.23-r1.5
> >
> > If emtooth isn't already installed then you probably want to install it.
> > It's a finger friendly GUI for pairing, and perhaps more by now (I've
> > not checked it for a while).
>
> I've installed it, but stop on "Discovering Devices" so I tried to do it
> from terminal.
It does that if there's nothing to discover. Hit the 'Stop discovery' button
and it'll change to '0 devices found' or similar. The 'Settings' button should
show a screen with MAC, name and controls for discoverability and pairability.
At least that's what the oldish version I have does. It doesn't show devices
you're already paired with or their current status though.
> I tried also specifying the device to use for bluetooth (I think it is
> /dev/btrfs-control), but no luck:
>
> # hcitool -i /dev/btrfs-control scan
> Invalid device: No such device
That device is for the btrfs filesystem!
> Is it only me to have this problem? Do you think that flashing SHR-U again
> would solve it?
Make sure bluetooth is enabled, then run these in the terminal and report back
what you get:
mdbus -s org.bluez
hciconfig
> Thanks again for all your helps!
>
> Carmelo
>
>
> _________________________________________________________________
> Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
> https://signup.live.com/signup.aspx?id=60969
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user
