Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001310]: Driver cant find firmware for Layla24
Date: Sun, 7 Aug 2005 18:27:47 +0200	[thread overview]
Message-ID: <399dcd330466554345fc4b021c557546@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1310> 
======================================================================
Reported By:                oxi
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   1310
Category:                   PCI - echoaudio
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               Debian Sarge AMD64
Kernel Version:             2.6.12.3
======================================================================
Date Submitted:             08-04-2005 22:50 CEST
Last Modified:              08-07-2005 18:27 CEST
======================================================================
Summary:                    Driver cant find firmware for Layla24
Description: 
Hello,

After modprobe snd-layla24 ,
in dmesg|tail:

ACPI: PCI Interrupt 0000:00:0e.0[A] -> GSI 19 (level, low) -> IRQ 19
ALSA /usr/src/alsa-driver-1.0.9b/pci/echoaudio/echoaudio.c:41:
get_firmware(): Firmware not available (-2)
Echoaudio Layla24: probe of 0000:00:0e.0 failed with error -2

Same issue that another guy is experiencing with a Layla20:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1244
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0001244 error with firmware with echo layla20
======================================================================

----------------------------------------------------------------------
 pochini - 08-07-05 09:46 
----------------------------------------------------------------------
I didn't know I'm not the official maintainer anymore :))

The driver simply does:

	if ((err = request_firmware(fw_entry, name, pci_device(chip))) < 0)
		snd_printk(KERN_ERR "get_firmware(): Firmware not available (%d)\n",
err);
	return err;

So I don't think there is something wrong there. Btw an other user had a
similar problem some days ago. I quote the relevant part:

----------------------------------------
From: indigo@bitglue.com (Phil Frost)
To: alsa-user@lists.sourceforge.net
Cc: alsa-devel@lists.sourceforge.net
Subject: [Alsa-devel] Re: [Alsa-user] need help getting echo indigo io to
work
Date: Tue, 19 Jul 2005 19:14:44 -0400

> Error -2 is -ENOENT (No such file or directory). request_firmware()
returns
> that error code if the file has zero size of if the script aborted the
> operation. Please check if /usr/lib/hotplug/firmware/ea/indigo_io_dsp.fw
is
> empty.

It's 17 kb away from empty. Also, firmware.agent seems to complete
successfuly from what I can tell. Lee Revell suggested on alsa-devel
that I should try with 2.6.12 since there have been changes in the
driver model since 2.6.10 (what i'm using). Indeed that seems to have
been the cause of the problem. With 2.6.12 I was able to play audio
nicely.
----------------------------------------

P.S.: my email is pochini@shiny.it

----------------------------------------------------------------------
 oxi - 08-07-05 18:27 
----------------------------------------------------------------------
Hey thank you all for your replies!

My mistake, Pochini! I saw "Discontinued" in the notes field in ALSA
soundcard matrix and thus concluded you were not supporting them anymore!
:D

Anyways, I already have kernel version 2.6.12.3. So I dont have a clue if
im missing something somehow, since im just a newbie linux user. If you
think of something obvious i might be missing please let me know!

Again, thank you all for your support and patience. :)

Issue History
Date Modified  Username       Field                    Change              
======================================================================
08-04-05 22:50 oxi            New Issue                                    
08-04-05 22:50 oxi            Distribution              => Debian Sarge AMD64
08-04-05 22:50 oxi            Kernel Version            => 2.6.12.3        
08-04-05 23:48 rlrevell       Note Added: 0005653                          
08-05-05 04:57 oxi            Note Added: 0005656                          
08-05-05 04:59 oxi            Issue Monitored: oxi                         
08-05-05 05:00 rlrevell       Note Added: 0005657                          
08-05-05 05:20 oxi            Note Added: 0005658                          
08-05-05 05:25 oxi            Note Added: 0005659                          
08-05-05 06:03 rlrevell       Note Added: 0005660                          
08-05-05 08:48 perex          Relationship added       related to 0001244  
08-05-05 13:26 oxi            Note Added: 0005666                          
08-05-05 15:09 hennewou       Note Added: 0005668                          
08-05-05 19:43 oxi            Note Added: 0005671                          
08-05-05 19:46 oxi            Note Edited: 0005671                         
08-05-05 20:36 rlrevell       Note Added: 0005675                          
08-05-05 23:10 hennewou       Note Added: 0005677                          
08-07-05 09:46 pochini        Note Added: 0005688                          
08-07-05 18:27 oxi            Note Added: 0005695                          
======================================================================




-------------------------------------------------------
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

             reply	other threads:[~2005-08-07 16:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 16:27 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-09 23:07 [ALSA - driver 0001310]: Driver cant find firmware for Layla24 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:31 bugtrack
2005-08-08  9:04 ` Eliot Blennerhassett
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=399dcd330466554345fc4b021c557546@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /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