From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000651]: via82xxx No Sound Kernel 2.6.10-rc2
Date: Fri, 30 Dec 2005 04:53:36 +0100 [thread overview]
Message-ID: <339fdbf5eb81d46d436ac84b03d99688@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=651>
======================================================================
Reported By: glen
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 651
Category: PCI - via82xx
Reproducibility: always
Severity: major
Priority: normal
Status: closed
Distribution: Slackware 10.0 + Dropline Gnome 2.8.0
Kernel Version: 2.6.10-rc2
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 11-17-2004 19:03 CET
Last Modified: 12-30-2005 04:53 CET
======================================================================
Summary: via82xxx No Sound Kernel 2.6.10-rc2
Description:
Upgraded to kernel 2.6.10-rc2 from 2.6.10-rc1 with identical config. No
compile problems. No boot up problems. No sound.
======================================================================
----------------------------------------------------------------------
jdthood - 03-23-05 15:25
----------------------------------------------------------------------
Submitter: What happens if you build ALSA modules from the alsa-driver
tarball and use those instead of the modules that come with your kernel?
----------------------------------------------------------------------
rlrevell - 12-30-05 04:53
----------------------------------------------------------------------
No response
Issue History
Date Modified Username Field Change
======================================================================
11-17-04 19:03 glen New Issue
11-17-04 19:03 glen File Added: config-2.6.10-rc2
11-17-04 19:03 glen Distribution => Slackware 10.0 +
Dropline Gnome 2.8.0
11-17-04 19:03 glen Kernel Version => 2.6.10-rc2
11-17-04 19:05 glen Note Added: 0002439
11-17-04 19:06 glen File Added: lspci.txt
11-18-04 19:48 tiwai Note Added: 0002466
11-19-04 01:04 glen File Added: asound.state
11-19-04 01:04 glen File Added: ac97#0-0
11-19-04 01:04 glen File Added: ac97#0-0+regs
11-19-04 01:20 glen Note Added: 0002473
03-23-05 15:25 jdthood Note Added: 0004159
12-30-05 04:53 rlrevell Status new => closed
12-30-05 04:53 rlrevell Note Added: 0007228
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2005-12-30 3:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 3:53 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-23 14:25 [ALSA - driver 0000651]: via82xxx No Sound Kernel 2.6.10-rc2 bugtrack
2004-11-19 0:20 bugtrack
2004-11-18 18:48 bugtrack
2004-11-17 18:05 bugtrack
2004-11-17 18:03 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=339fdbf5eb81d46d436ac84b03d99688@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