I have, about 20% of the time, a bluetooth lashup that looks like an rs232 null modem cable, between this bluetooth button:
7.594193] usb 1-10.4.2.3: new full speed USB device using ehci_hcd and address 18
[ 7.682292] usb 1-10.4.2.3: New USB device found, idVendor=0a5c, idProduct=2148
[ 7.682297] usb 1-10.4.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7.682300] usb 1-10.4.2.3: Product: BCM92046DG-CL1ROM
[ 7.682302] usb 1-10.4.2.3: Manufacturer: Broadcom Corp
[ 7.682304] usb 1-10.4.2.3: SerialNumber: 000272A176A4
And an a7 eb-301 module attached to an sc5661 ACIA in a serial comm pack plugged into a 20+ year old trs-80 Color Computer running todays version of the microware os9 operating system.
What can I add/correct in this /etc/bluetooth/rfcomm.conf:
# RFCOMM configuration file.
# this was ALL commented out
# # Automatically bind the device at startup
# # Bluetooth address of the far end eb301 device
# # RFCOMM channel for the connection
# # Description of the connection
# comment "Example Bluetooth device";
comment "connection to coco3's eb-301 device";
that will bring this up at bootup time without the aggravation of unplugging the button, waiting for linux to clean things up, then plugging it back in so the bluetooth stuff runs for about 10 seconds, during which I can sometimes catch it with blueman-manager and configure it to work for a few hours. But if I don't get blueman-manager running quick enough after plugging it back in and seeing the discovery in a tail of the syslog, the bluez daemon has gone away and blueman-manager will not then run.
It seems to me there has got to be a way that Just Works(TM), so any and all suggestions will be gratefully accepted & results posted.
FWIW, kernel is now a 32 bit build of 2.6.37-rc8 from kernel.org, with as much of the bluetooth stuff built in as can be arranged in a make xconfig.
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)