From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] L2Ping / Rfcomm connect : Function not implemented
Date: Mon, 13 Dec 2004 13:14:51 +0100 [thread overview]
Message-ID: <1102940092.8750.151.camel@pegasus> (raw)
In-Reply-To: <200412131309.12167.wim.delvaux@adaptiveplanet.com>
Hi Wim,
> > > After a reboot (again a kernel freeze that I mailed about before) and a
> > > change in hcid.conf ... no result.
> >
> > We can't get any further without a protocol analyzer. However you might
> > wanna ask a Nokia Service Shop to update your mobile phone.
>
> The strange thing is
>
> 1. it has worked before
> 2. it works from my desktop
>
> with this hciconfig -a output
> hci0: Type: USB
> BD Address: 00:60:57:02:71:A2 ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN AUTH
> RX bytes:3133810 acl:37666 sco:0 events:87504 errors:0
> TX bytes:19406578 acl:115742 sco:0 commands:737 errors:0
> Features: 0xff 0xff 0x09 0x00 0x00 0x00 0x00 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: ACCEPT MASTER
> Name: 'buro-0'
> Class: 0x100000
> Service Classes: Object Transfer
> Device Class: Miscellaneous,
> HCI Ver: 1.1 (0x1) HCI Rev: 0xbc LMP Ver: 1.1 (0x1) LMP Subver: 0xbc
> Manufacturer: Cambridge Silicon Radio (10)
>
> I can connect with BNEP from the Ipaq to the desktop and actually
> AM connected to it
it looks like a link manager problem in some way. However this can't be
debugged without a protocol analyzer.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-12-13 12:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-12 22:56 [Bluez-users] L2Ping / Rfcomm connect : Function not implemented wim delvaux
2004-12-13 8:02 ` Marcel Holtmann
2004-12-13 10:47 ` wim delvaux
2004-12-13 11:01 ` Marcel Holtmann
2004-12-13 11:43 ` wim delvaux
2004-12-13 11:47 ` Marcel Holtmann
2004-12-13 11:59 ` wim delvaux
2004-12-13 12:04 ` Marcel Holtmann
2004-12-13 12:09 ` wim delvaux
2004-12-13 12:12 ` wim delvaux
2004-12-13 12:15 ` Marcel Holtmann
2004-12-13 12:18 ` wim delvaux
2004-12-13 12:31 ` Marcel Holtmann
2004-12-13 12:14 ` Marcel Holtmann [this message]
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=1102940092.8750.151.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/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