From: Krisztian Mark Szentes <office@produktivIT.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bt3c_cs time out - no firmware loaded? - problem persists.
Date: Tue, 13 May 2003 03:16:56 +0200 [thread overview]
Message-ID: <200305130316.56691.office@produktivIT.com> (raw)
In-Reply-To: <5.1.0.14.2.20030512132833.0d19d8a0@unixmail.qualcomm.com>
On Monday 12 May 2003 22:29, Max Krasnyansky wrote:
> At 06:43 AM 5/8/2003, Krisztian Mark Szentes wrote:
> >May 8 15:02:20 tomcat cardmgr[1071]: socket 0: 3Com Bluetooth PC Card
> >May 8 15:02:20 tomcat cardmgr[1071]: executing: 'modprobe bt3c_cs'
> >May 8 15:02:21 tomcat hcid[1428]: HCI dev 0 registered
> >May 8 15:02:31 tomcat hcid[1616]: Can't init device hci0. Connection
> > timed out(110)
>
> Hmm, you should see bluefw messages before HCI dev 0 registered.
> I guess you'd need to ping Marcel on that one.
I observed cardmgr to cause a line
cardmgr[xxx]: executing: 'modprobe bt3c_cs' line
I deleted the /sbin/bluefw symlink to /usr/sbin/bluefw to see if it gets
invoked, which gives:
bt3c_cs: Failed to exec "/sbin/bluefw pccard 03f8".
in /proc/ioports bt3c_cs shows up at 000003f8-000003ff
if I manually call /usb/sbin/bluefw pccard 03f8 it gives no error; but it
does not touch the /etc/bluetooth/firmware/BT3CPCC.bin file either.
I tried the bluez-bluefw both in version 1.0-1 and 0.9-2 (powerpc) and
compiled 1.0 from source, but the firmware still does not even get
touched, let alone loaded. And I get no bluefw messages in syslog.
Any hints?
Mark
P.S. The /sbin/bluefw symlink is not included in the Debian packages but
the kernel module loads this and not /usr/sbin/bluefw.
--
produktivIT - Open-Source Solution Provider
Siebenbrunnengasse 55/7
A-1050 Wien
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2003-05-13 1:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53B03DA73719D5119E6A0008C71E1D78030EA9A3@svr-mail1.corp.home.nl>
2003-05-08 13:43 ` [Bluez-users] bt3c_cs time out - no firmware loaded? Krisztian Mark Szentes
2003-05-12 20:29 ` Max Krasnyansky
2003-05-13 1:16 ` Krisztian Mark Szentes [this message]
2003-05-13 0:17 ` Marcel Holtmann
2003-05-13 8:47 ` Krisztian Mark Szentes
2003-05-16 11:04 ` Marcel Holtmann
2003-05-16 12:38 ` Krisztian Mark Szentes
2003-05-16 13:16 ` Marcel Holtmann
2003-05-16 13:24 ` Benjamin Herrenschmidt
2003-05-16 13:30 ` Marcel Holtmann
2003-05-16 13:32 ` Benjamin Herrenschmidt
2003-05-16 13:39 ` Marcel Holtmann
2003-05-16 13:47 ` Benjamin Herrenschmidt
2003-05-16 13:57 ` Marcel Holtmann
2003-05-16 14:11 ` Benjamin Herrenschmidt
2003-05-16 14:25 ` Marcel Holtmann
2003-05-16 14:48 ` Benjamin Herrenschmidt
2003-05-16 14:22 ` Krisztian Mark Szentes
2003-05-16 14:32 ` Marcel Holtmann
2003-05-16 14:51 ` Krisztian Mark Szentes
2003-05-09 8:39 ` produktivIT
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=200305130316.56691.office@produktivIT.com \
--to=office@produktivit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox