Re: Newbie, can't find device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello...

----- Original Message ----- From: "Gene Heskett" <gene.heskett@xxxxxxxxxxx>
To: <linux-bluetooth@xxxxxxxxxxxxxxx>
Sent: Wednesday, March 25, 2009 7:37 PM
Subject: Newbie, can't find device


Greetings;


Core v2.14? Very, very old. I think we are on version 4.33, which has been completely re-architected on a DBus foundation. With DBus, the "devices" are created as object paths that handle defined messages via DBus.

What sort of box are you running on? Which kernel version? Which distro? I get a little concerned (and somewhat nostalgic/nauseous) when I see a "Trash-80" cited (I think you are wanting to use Bluetooth to talk to it).

Just my two cents and worth about that much.

DS

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 _N persons implements a COBOL compiler, there will be _N-1
passes.  Someone in the group has to be the manager.
-- T. Cheatham

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux