On Wednesday 08 April 2009, Zygo Blaxell wrote: >On Wed, Apr 08, 2009 at 11:06:11AM -0400, Gene Heskett wrote: >> >Or you can use gnome-bluetooth which has those problems fixed. >> >> If you are referring to 'bluetooth-wizard', it will not show me a device. >> I'm told it will not show devices which are already paired. > >gnome-bluetooth is a fork of bluez-gnome. You'd probably have to build it > out of svn at svn://svn.gnome.org/svn/gnome-bluetooth unless someone's > making binary packages somewhere. > I see. Since I've built and installed bluezx-4.34, am I new enough? >> I get what I assume is the same message from a: >> >> [root@coyote test]# ./simple-agent hci0 00:0C:84:00:86:F8 >> Creating device failed: org.bluez.Error.AlreadyExists: Bonding already >> exists >> >> I just found /var/lib/bluetooth/11:11:11:11:11:11 which has a group of >> small files in it, 2 or 3 being subjected to an updated timestamp (data in >> these files is kept in GMT). >> >> Is this the directory I need to mv someplace in order to rerun the >> bluetooth- wizard? Ok, did that, bluetooth-wizard did show me the device, >> but then the pin screen only showed for an almost subliminal time & then >> reported that it failed. >> >> That generated a new /var/lib/bluetooth tree, so I nuked that, and ran >> "simple-agent hci0 <bdaddr of this dongle>" >> That asked me for just one PIN and I gave it the default of 0000. No >> errors. And a new /var/lib/bluetooth tree was created. >> >> An l2ping <bdaddr of remote> >> Ping: 00:0C:84:00:86:F8 from 11:11:11:11:11:11 (data size 44) ... >> 4 bytes from 00:0C:84:00:86:F8 id 0 time 16.93ms >> 4 bytes from 00:0C:84:00:86:F8 id 1 time 10.86ms >> 4 bytes from 00:0C:84:00:86:F8 id 2 time 27.87ms >> 4 bytes from 00:0C:84:00:86:F8 id 3 time 28.87ms >> 4 bytes from 00:0C:84:00:86:F8 id 4 time 25.93ms >> 4 bytes from 00:0C:84:00:86:F8 id 5 time 25.89ms >> >> Is this normal? > >All of that looks good. Do you have a line in /var/lib/bluetooth/*/linkkeys >that looks like: > >00:12:47:00:00:01 547603D831DB77377F203B74921E2F1A 0 4 00:0C:84:00:86:F8 8601686DF51140E7989038D3E35430E2 0 4 > >(with a different bdaddr and key value, of course ;). > >Actually it might be a good idea to post /var/lib/bluetooth/*/* here. It >will contain the information that bluetoothd grabs at pairing time that is >often unavailable from utilities like sdptool later. I'll attach it as a tarball. Done. > >> But a second minicom -s, check to see the serial port is /dev/rfcomm0, >> which does exist, select exit to minicom's main screen and it exits, >> reporting: minicom: cannot open /dev/rfcomm0: No route to host > >And that doesn't. > >> So that is where I am at. Last Saturday morning it Just Worked(TM) >> without all this hassle. I would like it to work again. What is the next >> troubleshooting step here?, I'll go at your pace this time. > >Did you manage to get at the configuration variables of the eb101 from the >Coco3 side? It looks like it's working (you can pair with it and ping it) >but somehow it has been configured to reject serial port connections. > >Maybe the Coco3 is asserting a modem control line that makes the eb101 think >it should be offline? > >> To those who suggested I use cu, or screen: I don't have a cu, and >> 'screen' cannot open any device I've named. From a lengthy read of the >> manpage, 'screen' is a VT100 terminal, but without the ability to work >> with anything but the local system, so I don't see as it could be useful >> here. > >If you run 'screen /dev/rfcomm0' it will open a window on /dev/rfcomm0. >For a real serial port you may need something like >'screen /dev/ttyS0 9600 cs8 -parenb'. It's a fairly minimal terminal >program which doesn't mess around trying to send modem AT commands or >assert modem control lines unnecessarily. > >> I'll go see if I can find this cu. Thanks everybody. > >'cu' is part of 'uucp'. On Debian it's packaged separately, on other >systems you'll need the rest of the uucp package as well. It's a fairly >minimalist terminal program that I used to use for serial consoles >on headless systems and embedded devices, until I discovered that the >functionality was built into screen. Got it, cu doesn't know the port(s) I named with the -p option. And the manpage doesn't seem to describe that part either. :( -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Love isn't only blind, it's also deaf, dumb, and stupid.
Attachment:
11:11:11:11:11:11.tar
Description: Unix tar archive
