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 0002234]: ISA sscape driver does not find Soundscape Elite
Date: Fri, 30 Jun 2006 02:10:26 +0200	[thread overview]
Message-ID: <fcf405609aa0159f9b006227061b17ea@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2234> 
======================================================================
Reported By:                tjallen
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   2234
Category:                   ISA - sscape
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               Slackware 10.2
Kernel Version:             2.6.17.1
======================================================================
Date Submitted:             06-26-2006 15:52 CEST
Last Modified:              06-30-2006 02:10 CEST
======================================================================
Summary:                    ISA sscape driver does not find Soundscape Elite
Description: 
The ALSA driver builds fine, both as a module and built-in but
the driver does not find the Soundscape Elite card.
======================================================================

----------------------------------------------------------------------
 tjallen - 06-30-06 01:45 
----------------------------------------------------------------------
I thought that I had found the problem when I just noticed that
/etc/modules.conf should have port=0x534 instead of port=0x539, but fixing
that goof didn't help
the snd-sscape module to find the hardware;
the kernel log still said "sscape: hardware not detected at 0x534".
I do have /dev/snd/hwC0D0, but with different owner and permissions:
crw-rw-r--  1 root audio 116, 4 2003-08-29 03:47 /dev/snd/hwC0D0
I did run the sscape_ctl program as root.

----------------------------------------------------------------------
 rankincj - 06-30-06 02:10 
----------------------------------------------------------------------
"sscape: hardware not detected at 0x534"

OK, this is expected because the driver is only testing port 0x534 for a
SoundScape PnP card, and not for a SoundScape Elite. ALSA's
detect_sscape() function is going to need extending with extra Voodoo code
from the OSS linux/sound/oss/sscape.c file. (At the very least...!) I'm
afraid you're going to have to tease the correct initialisation sequence
out of the OSS driver so we know what code to put in the ALSA version. I
suggest putting printk() statements in the OSS code so that you can follow
the code-path when the OSS driver loads.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
06-26-06 15:52 tjallen        New Issue                                    
06-26-06 15:52 tjallen        Distribution              => Slackware 10.2  
06-26-06 15:52 tjallen        Kernel Version            => 2.6.17.1        
06-26-06 22:57 Adrian Bunk    Issue Monitored: Adrian Bunk                    
06-28-06 23:25 rankincj       Note Added: 0010628                          
06-29-06 00:40 tjallen        Note Added: 0010630                          
06-29-06 17:57 tiwai          Note Added: 0010679                          
06-29-06 20:30 tjallen        Note Added: 0010701                          
06-29-06 23:14 rankincj       Note Added: 0010703                          
06-29-06 23:17 rankincj       Note Added: 0010704                          
06-30-06 01:45 tjallen        Note Added: 0010708                          
06-30-06 02:10 rankincj       Note Added: 0010710                          
======================================================================



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

             reply	other threads:[~2006-06-30  0:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-30  0:10 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-06  0:43 [ALSA - driver 0002234]: ISA sscape driver does not find Soundscape Elite bugtrack
2006-08-05 21:29 bugtrack
2006-08-05 21:09 bugtrack
2006-08-05 21:02 bugtrack
2006-08-05 20:50 bugtrack
2006-08-05 11:36 bugtrack
2006-08-02 23:40 bugtrack
2006-08-02 22:47 bugtrack
2006-07-31 14:59 bugtrack
2006-07-30 21:17 bugtrack
2006-07-30 19:45 bugtrack
2006-07-23  0:25 bugtrack
2006-07-02  1:19 bugtrack
2006-07-01 23:41 bugtrack
2006-06-30 20:47 bugtrack
2006-06-30 20:38 bugtrack
2006-06-30 12:46 bugtrack
2006-06-29 23:45 bugtrack
2006-06-29 21:17 bugtrack
2006-06-29 21:14 bugtrack
2006-06-29 18:30 bugtrack
2006-06-29 15:57 bugtrack
2006-06-28 22:40 bugtrack
2006-06-28 21:25 bugtrack
2006-06-26 13:52 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=fcf405609aa0159f9b006227061b17ea@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