From: Eliot Blennerhassett <linux@audioscience.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: [ALSA - driver 0001310]: Driver cant find firmware for Layla24
Date: Mon, 8 Aug 2005 21:04:47 +1200 [thread overview]
Message-ID: <200508082104.47991.linux@audioscience.com> (raw)
In-Reply-To: <b1aafa7d69ffb16052ad659919fac4a8@bugtrack.alsa-project.org>
I may be completely off track here but...
I was caught out recently because FC4 for example expects firmware in a
different directory than /usr/lib/hotplug (from memory /lib/firmware ?)
take a look at /etc/hotplug/firmware.agent, and see which path it is using to
look for the firmware
-- Eliot
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-08 9:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 16:31 [ALSA - driver 0001310]: Driver cant find firmware for Layla24 bugtrack
2005-08-08 9:04 ` Eliot Blennerhassett [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 23:07 bugtrack
2005-08-09 23:06 bugtrack
2005-08-09 22:57 bugtrack
2005-08-09 9:42 bugtrack
2005-08-08 21:07 bugtrack
2005-08-08 20:23 bugtrack
2005-08-08 19:40 bugtrack
2005-08-08 7:22 bugtrack
2005-08-08 2:32 bugtrack
2005-08-07 22:06 bugtrack
2005-08-07 16:27 bugtrack
2005-08-07 7:46 bugtrack
2005-08-05 21:10 bugtrack
2005-08-05 18:36 bugtrack
2005-08-05 17:43 bugtrack
2005-08-05 13:09 bugtrack
2005-08-05 11:26 bugtrack
2005-08-05 6:48 bugtrack
2005-08-05 4:03 bugtrack
2005-08-05 3:25 bugtrack
2005-08-05 3:20 bugtrack
2005-08-05 3:00 bugtrack
2005-08-05 2:57 bugtrack
2005-08-04 21:48 bugtrack
2005-08-04 20:50 bugtrack
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=200508082104.47991.linux@audioscience.com \
--to=linux@audioscience.com \
--cc=alsa-devel@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.