public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* [Bluez-users] cannot find device
@ 2006-12-30  0:33 Nerijus Baliunas
  2006-12-31 10:05 ` Paul Gardiner
  2007-01-09  2:04 ` Nerijus Baliunas
  0 siblings, 2 replies; 4+ messages in thread
From: Nerijus Baliunas @ 2006-12-30  0:33 UTC (permalink / raw)
  To: bluez-users

Hello,

My PDA used to find the device when I had Fedora Core 5, but cannot
when I upgraded to FC6. hcid.conf is default from FC6 (bluez-utils-3.7-2):

options {
        autoinit yes;
        security user;
        pairing multi;
        passkey "BlueZ";
}
device {
        name "%h-%d";
        class 0x120104;
        #pkt_type DH1,DM1,HV1;
        iscan enable; pscan enable;
        lm accept;
        lp rswitch,hold,sniff,park;
}

I launched bluetooth-properties and selected
"Visible and connectable for other devices",
"Make adapter invisible after" set to never.

hciconfig -a
hci0:	Type: USB
	BD Address: 00:13:46:00:12:CB ACL MTU: 377:10 SCO MTU: 16:0
	UP RUNNING PSCAN ISCAN AUTH ENCRYPT 
	RX bytes:8639 acl:0 sco:0 events:249 errors:0
	TX bytes:5296 acl:0 sco:0 commands:202 errors:0
	Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
	Packet type: DM3 DM5 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH HOLD SNIFF PARK 
	Link mode: SLAVE ACCEPT 
	Name: 'xxx-0'
	Class: 0x120104
	Service Classes: Networking, Object Transfer
	Device Class: Computer, Desktop workstation
	HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x309
	Manufacturer: Broadcom Corporation (15)

Any ideas why PDA cannot find the device? I found in mailing list archives and tried
unsuccessfully:
apitest SetDiscoverableTimeout 0
apitest SetMode discoverable

"to make this work you need to set discovto to 0, because otherwise hcid
will automatically switch you device into non-discoverable mode to
protect you." - where do I need to set discovto to 0?

Regards,
Nerijus

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-users] cannot find device
  2006-12-30  0:33 [Bluez-users] cannot find device Nerijus Baliunas
@ 2006-12-31 10:05 ` Paul Gardiner
  2007-01-09  2:04 ` Nerijus Baliunas
  1 sibling, 0 replies; 4+ messages in thread
From: Paul Gardiner @ 2006-12-31 10:05 UTC (permalink / raw)
  To: BlueZ users

Nerijus Baliunas wrote:
> Hello,
> 
> My PDA used to find the device when I had Fedora Core 5, but cannot
> when I upgraded to FC6. hcid.conf is default from FC6 (bluez-utils-3.7-2):
 >
 >    .
 >    .
 >    .
 >
> hciconfig -a
> hci0:	Type: USB
> 	BD Address: 00:13:46:00:12:CB ACL MTU: 377:10 SCO MTU: 16:0
> 	UP RUNNING PSCAN ISCAN AUTH ENCRYPT 
> 	RX bytes:8639 acl:0 sco:0 events:249 errors:0
> 	TX bytes:5296 acl:0 sco:0 commands:202 errors:0
> 	Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
> 	Packet type: DM3 DM5 DH3 DH5 HV1 HV2 HV3 
> 	Link policy: RSWITCH HOLD SNIFF PARK 
> 	Link mode: SLAVE ACCEPT 
> 	Name: 'xxx-0'
> 	Class: 0x120104
> 	Service Classes: Networking, Object Transfer
> 	Device Class: Computer, Desktop workstation
> 	HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x309
> 	Manufacturer: Broadcom Corporation (15)
> 
> Any ideas why PDA cannot find the device? I found in mailing list archives and tried
> unsuccessfully:
> apitest SetDiscoverableTimeout 0
> apitest SetMode discoverable
> 
> "to make this work you need to set discovto to 0, because otherwise hcid
> will automatically switch you device into non-discoverable mode to
> protect you." - where do I need to set discovto to 0?

I was me having similar problems, but it looks to be with a different
cause, because hciconfig didn't list PSCAN and ISCAN in my case.

Cheers,
	Paul.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-users] cannot find device
  2006-12-30  0:33 [Bluez-users] cannot find device Nerijus Baliunas
  2006-12-31 10:05 ` Paul Gardiner
@ 2007-01-09  2:04 ` Nerijus Baliunas
  2007-01-10 20:02   ` Nerijus Baliunas
  1 sibling, 1 reply; 4+ messages in thread
From: Nerijus Baliunas @ 2007-01-09  2:04 UTC (permalink / raw)
  To: BlueZ users

Hello,

found more info - https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=212825
but running passkey-agent didn't help. I also noticed that even if I change
class in hcid.conf, hciconfig hci0 down, service bluetooth restart,
hciconfig -a still displays Class: 0x120100. Why?
BTW, hcidump -X -V does not display anything when I search for devices from
my Palm.

Nerijus

On Sat, 30 Dec 2006 02:33:45 +0200 Nerijus Baliunas <nerijus@users.sourceforge.net> wrote:

> Hello,
> 
> My PDA used to find the device when I had Fedora Core 5, but cannot
> when I upgraded to FC6. hcid.conf is default from FC6 (bluez-utils-3.7-2):
> 
> options {
>         autoinit yes;
>         security user;
>         pairing multi;
>         passkey "BlueZ";
> }
> device {
>         name "%h-%d";
>         class 0x120104;
>         #pkt_type DH1,DM1,HV1;
>         iscan enable; pscan enable;
>         lm accept;
>         lp rswitch,hold,sniff,park;
> }
> 
> I launched bluetooth-properties and selected
> "Visible and connectable for other devices",
> "Make adapter invisible after" set to never.
> 
> hciconfig -a
> hci0:	Type: USB
> 	BD Address: 00:13:46:00:12:CB ACL MTU: 377:10 SCO MTU: 16:0
> 	UP RUNNING PSCAN ISCAN AUTH ENCRYPT 
> 	RX bytes:8639 acl:0 sco:0 events:249 errors:0
> 	TX bytes:5296 acl:0 sco:0 commands:202 errors:0
> 	Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
> 	Packet type: DM3 DM5 DH3 DH5 HV1 HV2 HV3 
> 	Link policy: RSWITCH HOLD SNIFF PARK 
> 	Link mode: SLAVE ACCEPT 
> 	Name: 'xxx-0'
> 	Class: 0x120104
> 	Service Classes: Networking, Object Transfer
> 	Device Class: Computer, Desktop workstation
> 	HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x309
> 	Manufacturer: Broadcom Corporation (15)
> 
> Any ideas why PDA cannot find the device? I found in mailing list archives and tried
> unsuccessfully:
> apitest SetDiscoverableTimeout 0
> apitest SetMode discoverable
> 
> "to make this work you need to set discovto to 0, because otherwise hcid
> will automatically switch you device into non-discoverable mode to
> protect you." - where do I need to set discovto to 0?
> 
> Regards,
> Nerijus


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-users] cannot find device
  2007-01-09  2:04 ` Nerijus Baliunas
@ 2007-01-10 20:02   ` Nerijus Baliunas
  0 siblings, 0 replies; 4+ messages in thread
From: Nerijus Baliunas @ 2007-01-10 20:02 UTC (permalink / raw)
  To: BlueZ users

OK, it works now - I connected the same bluetooth adapter to another PC, and my Palm
showed its name in Trusted devices list (and so I thought that Palm does not see adapter
connected to my Linux PC). After I tried to connect to it, it changed its name to a correct
one and now it works.

Nerijus

On Tue, 9 Jan 2007 04:04:28 +0200 Nerijus Baliunas <nerijus@users.sourceforge.net> wrote:

> Hello,
> 
> found more info - https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=212825
> but running passkey-agent didn't help. I also noticed that even if I change
> class in hcid.conf, hciconfig hci0 down, service bluetooth restart,
> hciconfig -a still displays Class: 0x120100. Why?
> BTW, hcidump -X -V does not display anything when I search for devices from
> my Palm.
> 
> Nerijus
> 
> On Sat, 30 Dec 2006 02:33:45 +0200 Nerijus Baliunas <nerijus@users.sourceforge.net> wrote:
> 
> > Hello,
> > 
> > My PDA used to find the device when I had Fedora Core 5, but cannot
> > when I upgraded to FC6. hcid.conf is default from FC6 (bluez-utils-3.7-2):
> > 
> > options {
> >         autoinit yes;
> >         security user;
> >         pairing multi;
> >         passkey "BlueZ";
> > }
> > device {
> >         name "%h-%d";
> >         class 0x120104;
> >         #pkt_type DH1,DM1,HV1;
> >         iscan enable; pscan enable;
> >         lm accept;
> >         lp rswitch,hold,sniff,park;
> > }
> > 
> > I launched bluetooth-properties and selected
> > "Visible and connectable for other devices",
> > "Make adapter invisible after" set to never.
> > 
> > hciconfig -a
> > hci0:	Type: USB
> > 	BD Address: 00:13:46:00:12:CB ACL MTU: 377:10 SCO MTU: 16:0
> > 	UP RUNNING PSCAN ISCAN AUTH ENCRYPT 
> > 	RX bytes:8639 acl:0 sco:0 events:249 errors:0
> > 	TX bytes:5296 acl:0 sco:0 commands:202 errors:0
> > 	Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
> > 	Packet type: DM3 DM5 DH3 DH5 HV1 HV2 HV3 
> > 	Link policy: RSWITCH HOLD SNIFF PARK 
> > 	Link mode: SLAVE ACCEPT 
> > 	Name: 'xxx-0'
> > 	Class: 0x120104
> > 	Service Classes: Networking, Object Transfer
> > 	Device Class: Computer, Desktop workstation
> > 	HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x309
> > 	Manufacturer: Broadcom Corporation (15)
> > 
> > Any ideas why PDA cannot find the device? I found in mailing list archives and tried
> > unsuccessfully:
> > apitest SetDiscoverableTimeout 0
> > apitest SetMode discoverable
> > 
> > "to make this work you need to set discovto to 0, because otherwise hcid
> > will automatically switch you device into non-discoverable mode to
> > protect you." - where do I need to set discovto to 0?
> > 
> > Regards,
> > Nerijus


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2007-01-10 20:02 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-12-30  0:33 [Bluez-users] cannot find device Nerijus Baliunas
2006-12-31 10:05 ` Paul Gardiner
2007-01-09  2:04 ` Nerijus Baliunas
2007-01-10 20:02   ` Nerijus Baliunas

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox