Udayan Singh wrote: >> What does "hciconfig -a" say? > > hci0: Type: USB > BD Address: 11:11:11:11:11:11 ACL MTU: 678:8 SCO MTU: 48:10 > UP RUNNING PSCAN ISCAN > RX bytes:701 acl:0 sco:0 events:23 errors:0 > TX bytes:335 acl:0 sco:0 commands:23 errors:0 > Features: 0xbf 0xfe 0x8d 0x78 0x08 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: 'BlueZ (0)' > Class: 0x3e0100 > Service Classes: Networking, Rendering, Capturing, Object Transfer, Audio > Device Class: Computer, Uncategorized > HCI Ver: 1.2 (0x2) HCI Rev: 0x1fe LMP Ver: 1.2 (0x2) LMP Subver: 0x1fe > Manufacturer: Integrated System Solution Corp. (57) > > but how do i know which driver would it be using and how can i see > which other bluetooth devices has it located ? There is only one standard Linux driver, bluez, which in your case appears to be running. But some chips require firmware to be installed on your computer - you'd have to check the bluez documentation to see if this applies to your ISS chip. You could try "hcitool scan". If this actually finds something then your bluetooth device _is_ working. You have to "pair" it with another device to do anything useful. -- Timothy Murphy e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
