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 0002286]: SB Audigy LS - no sound from line-in
Date: Sun, 16 Jul 2006 12:31:34 +0200	[thread overview]
Message-ID: <436cc601226962e2fd775fd385d97a93@bugtrack.alsa-project.org> (raw)


The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2286> 
======================================================================
Reported By:                brazso
Assigned To:                jcdutton
======================================================================
Project:                    ALSA - driver
Issue ID:                   2286
Category:                   PCI - ca0106
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Distribution:               
Kernel Version:             2.6.17-r2
======================================================================
Date Submitted:             07-16-2006 12:31 CEST
Last Modified:              07-16-2006 12:31 CEST
======================================================================
Summary:                    SB Audigy LS - no sound from line-in
Description: 
Last time when I used the line-in connector of my SB Audigy LS card a half
year ago, there was no problem with it. By now I wanted to digitalise some
stuff, but my line-in is dumb. Since I often update my gentoo portage tree
included the alsa-drivers, I'm sure that with alsa-driver-1.0.11rc1 dated
on 12/13/05 it still worked. Unfortunately I cannot say more when it went
wrong precisely, because all of my attempts to restore an earlier alsa
version than 1.0.11 were failed. With kernel 2.6.17-r2 alsa 1.0.10,
1.0.11rc1 and 1.0.11rc2 cannot be compiled, and although I could install
alsa 1.0.11rc3, but the mixer did not include my line-in for unknown
reason.

======================================================================

Issue History
Date Modified  Username       Field                    Change              
======================================================================
07-16-06 12:31 brazso         New Issue                                    
07-16-06 12:31 brazso         Kernel Version            => 2.6.17-r2       
======================================================================




-------------------------------------------------------------------------
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-07-16 10:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-16 10:31 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-16 20:18 [ALSA - driver 0002286]: SB Audigy LS - no sound from line-in bugtrack
2006-07-16 21:01 bugtrack
2006-07-17  8:16 bugtrack
2006-07-30 16:39 bugtrack
2006-07-30 21:31 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=436cc601226962e2fd775fd385d97a93@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