From: Takashi Iwai <tiwai@suse.de>
To: Ivica Ico Bukvic <ico@fuse.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: More issues with hdsp and 1.0.7 and 1.0.8 drivers
Date: Fri, 14 Jan 2005 20:48:56 +0100 [thread overview]
Message-ID: <s5h4qhjzt93.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050114193044.NHXT13012.gx4.fuse.net@64BitBadass>
At Fri, 14 Jan 2005 14:32:10 -0500,
Ivica Ico Bukvic wrote:
>
> > At Thu, 13 Jan 2005 22:16:56 -0500,
> > Ivica Ico Bukvic wrote:
> > >
> > > 1.0.8 driver install completely from scratch using sources has the
> > following
> > > problem:
> > >
> > > 1) hdsp card gets detected and everything goes fine until the firmware
> > needs
> > > to be loaded.
> > > 2) at that point if I run hdsploader I get the following undocumented
> > error:
> >
> > You need no longer to call hdsploader. The hdsp driver uses hotplug
> > firmware loader if available. So, installating firmware files to the
> > proper directory would suffice. (Note that the directory is different
> > from the path for hdsploader.)
> >
> > Did you install alsa-firmware 1.0.8, too?
>
> I tried to and made no difference. For more info please see my other
> e-mails. If the hotplug is supposed to do that, it certainly fails on my
> system as I have to either explicitly tell it to do it or if the snd-hdsp is
> being probed for the first time, I added the hdsploader to the "install"
> clause so that it is triggered with modprobing of the snd-hdsp module...
Invoking hdsploader does nothing with the driver with hotplug-fw
loader support. It's simply ignored.
> Of course, this only works on the 1.0.7 driver as 1.0.8 fails with the
> aforementioned error. Just to make things as clear as possible, when using
> 1.0.8 driver if I do not do anything, the firmware never gets loaded and the
> red HOST light never turns off on the multiface suggesting that nothing got
> to the card.
Did you get any kernel messages after loading snd-hdsp?
Anyway, please check the following:
- Whether your kernel supports CONFIG_FW_LOADER.
See /proc/config.gz (if any) or /usr/src/linux/.config file.
- If fw-loader is supported, the firmware files must be installed
properly. Check /usr/lib/hotplug/firmware directory whether
multiface*.bin files exist.
- Remove install in /etc/modprobe.conf to be sure.
If they are OK and the system still doesn't work, something wrong in
the driver or in the hotplug.
As a last resort, you can disable the fw-loader support in hdsp
driver. Remove the check in alsa-driver/pci/rme9652/hdsp.c
#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,0)
so that the following is enabled always.
#define HDSP_USE_HWDEP_LOADER
(don't forget to remove the corresponding #endif, too)
Takashi
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2005-01-14 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 3:16 More issues with hdsp and 1.0.7 and 1.0.8 drivers Ivica Ico Bukvic
2005-01-14 10:38 ` Takashi Iwai
2005-01-14 19:32 ` Ivica Ico Bukvic
2005-01-14 19:48 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-14 3:32 Ivica Ico Bukvic
2005-01-14 3:44 Ivica Ico Bukvic
2005-01-14 3:53 ` Ivica Ico Bukvic
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=s5h4qhjzt93.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ico@fuse.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