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 0000879]: (snd_)opl3sa2 (isa) doesn't work (fails on playback) on 2.6.x kernels
Date: Thu, 4 Aug 2005 13:25:49 +0200	[thread overview]
Message-ID: <e195ea1f845feadce2edb1dd50d88e45@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=879> 
======================================================================
Reported By:                iive
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   879
Category:                   ISA - opl3sa2
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     new
Distribution:               Slackware 10
Kernel Version:             all 2.6.x kernel version (current 2.6.10)
======================================================================
Date Submitted:             02-03-2005 03:42 CET
Last Modified:              08-04-2005 13:25 CEST
======================================================================
Summary:                    (snd_)opl3sa2 (isa) doesn't work (fails on playback)
on 2.6.x kernels
Description: 
It doesn't work on all 2.6.x kernel I have tried (current 2.6.10)
alsaconf doesn't detect the card as PnP, and fails to find it with
bruteforce.

When module is loaded by hand it shows no error, but on `aplay samle.wav`
I got
"ALSA /work/install/alsa-driver-1.0.5a/alsa-kernel/core/pcm_lib.c:2172:
playback
write error (DMA or IRQ trouble?"

on boot with 2.4.x kernel, everything magically works (alsaconf, aplay
etc..)

the bug is reported 4 months ago on
http://bugzilla.kernel.org/show_bug.cgi?id=3117
that's why some versions are old (but I had tried alsa-1.0.8 before
reposting this bug here)

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0001296 isapnp is incompatible with pnpbios and...
======================================================================

----------------------------------------------------------------------
 ahaning - 08-04-05 12:52 
----------------------------------------------------------------------
When I compile all drivers (not just --with-cards=opl3sa2) none of them
work.

I have now enabled kernel and BIOS support for PnP. With
alsa-driver-1.0.9b compiled with --with-cards=opl3sa2, no PnP or PCI cards
are found.

I don't see why I should need drivers other than opl3sa2.

----------------------------------------------------------------------
 perex - 08-04-05 13:25 
----------------------------------------------------------------------
Please, follow my instructions. I have not written to recompile other
drivers. I meant that in alsaconf should be selected the pnp card not
probing of legacy cards.

Also, follow ALL requests from
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=879#5608 and
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=879#5641. If you do
only partial steps, it avoids me to do proper conclusions. I don't have
opl3sa2 system around, so I rely on your input.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
02-03-05 03:42 iive           New Issue                                    
02-03-05 03:42 iive           File Added: isa_opl3sa2.tgz                    
02-03-05 03:42 iive           Distribution              => Slackware 10    
02-03-05 03:42 iive           Kernel Version            => all 2.6.x kernel
version (current 2.6.10)
04-13-05 21:59 jdthood        Note Added: 0004478                          
04-14-05 00:02 iive           Note Added: 0004485                          
07-09-05 06:26 ahaning        Note Added: 0005438                          
07-09-05 06:38 ahaning        Note Edited: 0005438                         
07-09-05 11:13 jdthood        Note Added: 0005439                          
07-09-05 11:14 jdthood        Note Added: 0005440                          
07-28-05 05:17 ahaning        Note Added: 0005577                          
08-02-05 00:02 iive           Note Added: 0005599                          
08-02-05 03:00 ahaning        Note Added: 0005600                          
08-02-05 03:05 ahaning        Note Added: 0005601                          
08-02-05 03:05 ahaning        Note Deleted: 0005600                        
08-02-05 22:08 perex          File Added: alsaconf-isapnp-2.6.patch             
      
08-02-05 22:14 perex          Note Added: 0005607                          
08-02-05 22:16 perex          Note Added: 0005608                          
08-03-05 02:46 ahaning        Note Added: 0005610                          
08-03-05 11:42 perex          File Added: alsaconf                         
08-03-05 11:42 perex          Note Added: 0005615                          
08-03-05 13:42 ahaning        Note Added: 0005625                          
08-03-05 15:17 ahaning        Note Added: 0005631                          
08-04-05 08:51 perex          Note Added: 0005641                          
08-04-05 08:52 perex          Relationship added       related to 0001296  
08-04-05 12:52 ahaning        Note Added: 0005644                          
08-04-05 13:25 perex          Note Added: 0005645                          
======================================================================




-------------------------------------------------------
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-04 11:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 11:25 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-10 11:30 [ALSA - driver 0000879]: (snd_)opl3sa2 (isa) doesn't work (fails on playback) on 2.6.x kernels bugtrack
2005-08-09 10:51 bugtrack
2005-08-09 10:48 bugtrack
2005-08-09  9:31 bugtrack
2005-08-09  1:00 bugtrack
2005-08-08 11:45 bugtrack
2005-08-07 13:24 bugtrack
2005-08-06 16:32 bugtrack
2005-08-06  6:37 bugtrack
2005-08-05 21:58 bugtrack
2005-08-05 11:47 bugtrack
2005-08-05 10:47 bugtrack
2005-08-05  6:44 bugtrack
2005-08-05  0:35 bugtrack
2005-08-04 12:51 bugtrack
2005-08-04 12:42 bugtrack
2005-08-04 10:52 bugtrack
2005-08-04  6:52 bugtrack
2005-08-04  6:51 bugtrack
2005-08-03 13:17 bugtrack
2005-08-03 11:42 bugtrack
2005-08-03  9:42 bugtrack
2005-08-03  0:46 bugtrack
2005-08-02 20:16 bugtrack
2005-08-02 20:14 bugtrack
2005-07-28  3:17 bugtrack
2005-07-09  9:14 bugtrack
2005-07-09  9:13 bugtrack
2005-07-09  4:26 bugtrack
2005-04-13 22:02 bugtrack
2005-04-13 19:59 bugtrack
2005-02-03  2:42 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=e195ea1f845feadce2edb1dd50d88e45@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