From: Gene Heskett <gene.heskett@verizon.net>
To: linux-bluetooth@vger.kernel.org
Subject: Newbie, can't find device
Date: Wed, 25 Mar 2009 20:37:02 -0400 [thread overview]
Message-ID: <200903252037.03024.gene.heskett@verizon.net> (raw)
Greetings;
gnubie to bluetooth that is. I bought some dongles to replace a cable that is
just long enough to present EMP surge problems between this box and a
bluetooth kit installed to replace the connector in an RS-232 pack for a
legacy computer, an old TRS-80 Color Computer 3 that has all the goodies in it
that 20 some years of development can give.
I get this from demsg:
[ 8.884948] Bluetooth: Core ver 2.14
[ 8.885051] Bluetooth: HCI device and connection manager initialized
[ 8.885054] Bluetooth: HCI socket layer initialized
[ 9.112240] Bluetooth: Generic Bluetooth USB driver ver 0.4
[ 21.015636] Bluetooth: L2CAP ver 2.11
[ 21.015639] Bluetooth: L2CAP socket layer initialized
[ 21.165128] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 21.165131] Bluetooth: BNEP filters: protocol multicast
[ 21.245887] Bluetooth: SCO (Voice Link) ver 0.6
[ 21.245890] Bluetooth: SCO socket layer initialized
[ 22.084606] Bluetooth: RFCOMM socket layer initialized
[ 22.084616] Bluetooth: RFCOMM TTY layer initialized
[ 22.084618] Bluetooth: RFCOMM ver 1.10
But no new devices are being created by udev.
hciconfig -a:
hci0: Type: USB
BD Address: 11:11:11:11:11:11 ACL MTU: 672:3 SCO MTU: 48:1
UP RUNNING PSCAN ISCAN
RX bytes:1104 acl:0 sco:0 events:45 errors:0
TX bytes:445 acl:0 sco:0 commands:45 errors:0
Features: 0xff 0x3e 0x85 0x38 0x18 0x18 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'coyote.coyote.den-0'
Class: 0x4a2100
Service Classes: Networking, Capturing, Telephony
Device Class: Computer, Uncategorized
HCI Ver: 2.0 (0x3) HCI Rev: 0x1f4 LMP Ver: 2.0 (0x3) LMP Subver: 0x1f4
Manufacturer: CONWISE Technology Corporation Ltd (66)
Where do I go from here. What I need to do is run a session of minicom to it
but minicom cannot find the device 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)
If a group of _\bN persons implements a COBOL compiler, there will be _\bN-1
passes. Someone in the group has to be the manager.
-- T. Cheatham
next reply other threads:[~2009-03-26 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 0:37 Gene Heskett [this message]
2009-03-26 10:59 ` Newbie, can't find device jayjwa
[not found] ` <200903261157.28413.gene.heskett@verizon.net>
2009-03-27 0:23 ` jayjwa
[not found] ` <200903262205.52669.gene.heskett@verizon.net>
2009-03-30 5:03 ` jayjwa
[not found] ` <200903300928.02545.gene.heskett@verizon.net>
2009-04-01 3:21 ` jayjwa
2009-04-03 3:20 ` Gene Heskett
2009-03-26 11:36 ` David Stockwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903252037.03024.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox