From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: RE: [Bluez-users] FW: bt3c_cs Module & bluez-bluefw
Date: Wed, 22 Jun 2005 16:54:30 +0200 [thread overview]
Message-ID: <1119452070.26772.174.camel@pegasus> (raw)
In-Reply-To: <006c01c5772d$595a7020$3202010a@acselection.local>
Hi Andy,
> Hotplug has always been installed, the firmware is in /lib/firmware and
> I'm still getting the below error.
> I think it's looking at the wrong directory for the firmware, are there
> any ways to debug what's happening?
> If you have any other suggestions they would be really appreciated.
since Ubuntu is Debian based there should no problem unless they changed
something in the hotplug package. Check if /etc/hotplug/firmware.agent
exists and in what directories it expects the firmware file. Also check
that your firmware file is really present and is not a zero size file.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-06-22 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 12:09 [Bluez-users] FW: bt3c_cs Module & bluez-bluefw Andrew Jones
2005-06-22 12:14 ` Marcel Holtmann
2005-06-22 12:57 ` Andrew Jones
2005-06-22 13:05 ` Marcel Holtmann
2005-06-22 13:21 ` Andrew Jones
2005-06-22 14:54 ` Marcel Holtmann [this message]
2005-06-22 15:50 ` Andrew Jones
2005-06-22 15:55 ` Marcel Holtmann
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=1119452070.26772.174.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