From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001335]: No sound on first probe
Date: Sun, 9 Apr 2006 02:49:57 +0200 [thread overview]
Message-ID: <8be5a0c9b62165b36c5449b24a047ebf@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1335>
======================================================================
Reported By: cpx
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1335
Category: PCI - via82xx
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Distribution: Slackware 10.0
Kernel Version: 2.6.13-rc6
======================================================================
Date Submitted: 08-14-2005 08:31 CEST
Last Modified: 04-09-2006 02:49 CEST
======================================================================
Summary: No sound on first probe
Description:
The first probe of the snd-via82xx module results in no sound from the
speakers/headphone jack. Removing the module and reloading it fixes the
problem. Upon reloading (sometimes when removing) a small bit of feedback
is audible (i.e. suggesting the hardware's been "initialized").
The module seems to have to be removed for it to work though... just
rebooting and having it reload the module that way doesn't work.
After performing the above to make it work the system can then be warm
booted with the sound continuing to work until powering off.
======================================================================
----------------------------------------------------------------------
cpx - 01-06-06 19:10
----------------------------------------------------------------------
So... this is still happening with the latest kernel, only sometime around
2.6.14 the rmmod trick stop working. Now I have to boot to winders first
to get the hardware initialized.
----------------------------------------------------------------------
cpx - 04-09-06 02:49
----------------------------------------------------------------------
Still no luck with kernel 2.6.16... can someone help please? :)
Issue History
Date Modified Username Field Change
======================================================================
08-14-05 08:31 cpx New Issue
08-14-05 08:31 cpx Distribution => Slackware 10.0
08-14-05 08:31 cpx Kernel Version => 2.6.13-rc6
01-06-06 19:10 cpx Note Added: 0007493
01-10-06 20:10 mysticxhiro Issue Monitored: mysticxhiro
04-09-06 02:49 cpx Note Added: 0009176
======================================================================
-------------------------------------------------------
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-04-09 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 0:49 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-06 18:10 [ALSA - driver 0001335]: No sound on first probe bugtrack
2005-08-14 6: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=8be5a0c9b62165b36c5449b24a047ebf@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