From: Marcel Holtmann <marcel@holtmann.org>
To: axs203dd@excite.com
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] HCI Stops responding
Date: Mon, 11 Oct 2004 11:59:05 +0200 [thread overview]
Message-ID: <1097488745.9474.8.camel@notepaq> (raw)
In-Reply-To: <20041010175639.E7B58B6D5@xprdmailfe17.nwk.excite.com>
Hi,
> I am using Slackware 10 with bluetooth support compiled as modules and bluez-libs-2.10 & bluez-utils-2.10. My box is an Athlon AMD K7 600MHz and the motherboard is Gigabyte 7IXE.
>
>
>
> I can;t get bluez to work properly. After some packets transmission the link breaks down and I have to unplug the dongle and plug it back again. It happened once to load the uhci (or usb-uhci) module and the PAN worked fine. However it is impossible to load these modules in the new distribution of Slackware, so I have to use usb-ohci instead.
send in more information. What does "hciconfig -a" say?
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-10-11 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 17:56 [Bluez-users] HCI Stops responding mr
2004-10-11 9:59 ` Marcel Holtmann [this message]
2004-10-11 11:22 mr
2004-10-11 12:32 ` Marcel Holtmann
2004-10-11 12:52 mr
2004-10-11 14:00 ` Marcel Holtmann
2004-10-11 14:44 mr
2004-10-11 15:23 ` Marcel Holtmann
2004-10-11 15:31 mr
2004-10-11 15:41 mr
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=1097488745.9474.8.camel@notepaq \
--to=marcel@holtmann.org \
--cc=axs203dd@excite.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.