From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001603]: via8235 no sound since kernel 2.6.13
Date: Wed, 1 Mar 2006 19:39:41 +0100 [thread overview]
Message-ID: <06f8f9f0d89d68c38ddfae3945ab30d1@bugtrack.alsa-project.org> (raw)
The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1603>
======================================================================
Reported By: picobyte
Assigned To: rlrevell
======================================================================
Project: ALSA - driver
Issue ID: 1603
Category: PCI - via82xx
Reproducibility: always
Severity: major
Priority: normal
Status: resolved
Distribution: slackware 10.2
Kernel Version: 2.6.13 - 2.6.14.2
Resolution: fixed
Fixed in Version: 1.0.11rc3
======================================================================
Date Submitted: 11-27-2005 15:06 CET
Last Modified: 03-01-2006 19:39 CET
======================================================================
Summary: via8235 no sound since kernel 2.6.13
Description:
I have no sound after a kernel upgrade. I seem to have lost it in 2.6.13.
Sound was available in 2.6.12. 2.6.14.2 didn't give sound either. The
problem is in 1.0.9b and 1.0.10. The modules are loaded as supposed
without error messages and alsamixer is set to volume.
======================================================================
----------------------------------------------------------------------
picobyte - 01-18-06 00:41
----------------------------------------------------------------------
yes, actually, the problem seems to have been resolved in 2.6.15 :)
Is there any way I can/should change this bugs' status?
----------------------------------------------------------------------
picobyte - 03-01-06 19:27
----------------------------------------------------------------------
It wasn't the kernel upgrade, but the upgrade to alsa 1.0.11-rc2.
Issue History
Date Modified Username Field Change
======================================================================
11-27-05 15:06 picobyte New Issue
11-27-05 15:06 picobyte Distribution => slackware 10.2
11-27-05 15:06 picobyte Kernel Version => 2.6.13 - 2.6.14.2
12-31-05 03:38 rlrevell Note Added: 0007330
01-18-06 00:38 picobyte Note Added: 0007704
01-18-06 00:38 picobyte Issue Monitored: picobyte
01-18-06 00:39 picobyte Issue End Monitor: picobyte
01-18-06 00:41 picobyte Note Edited: 0007704
03-01-06 19:27 picobyte Note Added: 0008287
03-01-06 19:39 rlrevell Status new => resolved
03-01-06 19:39 rlrevell Fixed in Version => 1.0.11rc3
03-01-06 19:39 rlrevell Resolution open => fixed
03-01-06 19:39 rlrevell Assigned To => rlrevell
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next reply other threads:[~2006-03-01 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 18:39 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-26 20:56 [ALSA - driver 0001603]: via8235 no sound since kernel 2.6.13 bugtrack
2006-06-17 8:14 bugtrack
2006-06-17 7:06 bugtrack
2006-06-03 14:02 bugtrack
2006-03-04 13:23 bugtrack
2006-03-01 18:27 bugtrack
2006-01-17 23:38 bugtrack
2005-12-31 2:38 bugtrack
2005-11-27 14:06 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=06f8f9f0d89d68c38ddfae3945ab30d1@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