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 0001345]: microphone input does broken after upgrading from kernel 2.6.10 to 2.6.12
Date: Mon, 22 Aug 2005 12:20:22 +0200	[thread overview]
Message-ID: <1831da5345bd9efdb66a59bf749ac5d6@bugtrack.alsa-project.org> (raw)


The following issue is now in status NEW (again)
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1345> 
======================================================================
Reported By:                kayosiii
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   1345
Category:                   PCI - intel8x0
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Distribution:               Mepis
Kernel Version:             2.6.12 custom compiled
======================================================================
Date Submitted:             08-17-2005 08:13 CEST
Last Modified:              08-22-2005 12:20 CEST
======================================================================
Summary:                    microphone input does broken after upgrading from
kernel 2.6.10 to 2.6.12
Description: 
Basically When a boot using kernel 2.6.10 I can record using a microphone.
With 2.6.12 I get no input... I am running the latest alsa-base in debian
unstable. And have tried just about every setting in kmixer
======================================================================

Issue History
Date Modified  Username       Field                    Change              
======================================================================
08-17-05 08:13 kayosiii       New Issue                                    
08-17-05 08:13 kayosiii       Distribution              => Mepis           
08-17-05 08:13 kayosiii       Kernel Version            => 2.6.12 custom
compiled
08-22-05 12:20 perex          Assigned To              perex =>            
08-22-05 12:20 perex          Status                   assigned => new     
08-22-05 12:20 perex          Category                 0_compilation problem_!!!
=> PCI - intel8x0
======================================================================




-------------------------------------------------------
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-22 10:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22 10:20 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-13  4:26 [ALSA - driver 0001345]: microphone input does broken after upgrading from kernel 2.6.10 to 2.6.12 bugtrack
2005-09-11 19:40 bugtrack
2005-09-11  8:38 bugtrack
2005-09-11  5:07 bugtrack
2005-08-25  1:59 bugtrack
2005-08-23 14:50 bugtrack
2005-08-17  6:13 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=1831da5345bd9efdb66a59bf749ac5d6@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