Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Ricordeau <olivier.ricordeau@wanadoo.fr>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [BUG] buggy ali5451 driver
Date: Mon, 04 Nov 2002 16:53:59 +0100	[thread overview]
Message-ID: <3DC69817.80300@wanadoo.fr> (raw)
In-Reply-To: 3DC6903B.1070309@wanadoo.fr

Olivier Ricordeau wrote:
> drclaw@dogsolitude.org wrote:
> 
>> Try disabling "use dma by default" in the ide section.  If that then
>> fixes the problem I have a patch that can get you dma back.  I've got an
>> ali southbridge in my laptop as well and everything works fine. 
>> 784 - Michael C. Piantedosi - drclaw@dogsolitude.org
> 
> 
> OK...
> How can I disable dma in a shell??? Or do I need to recompile the kernel 
> or something?
> 

I've booted with the "nodma" option (I guess that what you wanted me to 
do), and now here is the new output for "modprobe ali5451":

"hda: status timeout: status=0x80 { Busy }
hda: drive not ready for command
ali mixer creating error.
Ali pci audio not found or device busy.
/lib/modules/2.4.19-18mdk/kernel/sound/pci/ali5451/snd-ali5451.o.gz: 
init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, 
including invalid IO or IRQ parameters.
	You may find more information in syslog or on the output from dmesg
mosprobe: insmod 
/lib/modules/2.4.19-18mdk/kernel/sound/pci/ali5451/snd-ali5451.o.gz failed
modprobe: insmod snd-ali5451 failed"

After that, all my commands result in:
"hda: status timeout: status 8x80 { Busy }
hda: DMA disabled
hda: drive not ready for command"

I've also tried the same modprobe in single-user mode after a "hdparm 
-d0 /dev/hda", and no error message is displayed, but all my command 
result in the same error message as above.

-- 

  -= *Olivier RICORDEAU* =-   |  ICQ: 65452304
  Ing1 EPITA Millesime 2005   | Phone: 0686720852
           olivier.ricordeau@wanadoo.fr
          _Might the source be with you_



-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com

  parent reply	other threads:[~2002-11-04 15:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04 11:47 [BUG] buggy ali5451 driver Thierry Vignaud
2002-11-04 13:37 ` Olivier Ricordeau
2002-11-04 14:12 ` Takashi Iwai
2002-11-04 14:25   ` Olivier Ricordeau
2002-11-04 14:45     ` Olivier Ricordeau
2002-11-04 11:20       ` drclaw
2002-11-04 15:20         ` Olivier Ricordeau
2002-11-04 11:49           ` drclaw
2002-11-04 15:53           ` Olivier Ricordeau [this message]
2002-11-04 12:28             ` drclaw
2002-11-04 16:31               ` Olivier Ricordeau
2002-11-05  8:36                 ` Thierry Vignaud
2002-11-06  7:41                   ` Olivier Ricordeau

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=3DC69817.80300@wanadoo.fr \
    --to=olivier.ricordeau@wanadoo.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox