yup, once I tried bcsp it worked. Now, how can I fix it so that when the bluetooth card is plugged in, hciattach is run automagically?
On 07/06/07, Paul M <[EMAIL PROTECTED]> wrote: > ah-ha, found an old IRC log of Koen and others talking about the card. > > http://purl.rikers.org/%23oe/20050524.html.gz > > I'll try out what it suggested. > > On 07/06/07, Paul M <[EMAIL PROTECTED]> wrote: > > CF bluetooth type PANBT0101M, worked fine on Cacko, mostly OK on OZ, > > doesn't work with A. > > > > I have to run hciattach myself: > > > > # hciattach -p /dev/ttyS4 any 921600 > > # tail /var/log/messages > > Jun 6 22:58:56 spitz user.err kernel: h4_recv: Unknown HCI packet type 01 > > Jun 6 22:58:56 spitz user.err kernel: h4_recv: Unknown HCI packet type 0a > > Jun 6 22:58:56 spitz user.err kernel: h4_recv: Unknown HCI packet type 09 > > > > and so on until I force eject > > > > ever so grateful for any ideas > > > > thanks > > Paul > > > _______________________________________________ Angstrom-distro-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
