From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000937]: No sound unless using OSS driver
Date: Sat, 31 Dec 2005 04:06:49 +0100 [thread overview]
Message-ID: <6fc01d968f24cf46217aa9561abf309a@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=937>
======================================================================
Reported By: ruffasdagut
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 937
Category: PCI - via82xx
Reproducibility: always
Severity: crash
Priority: normal
Status: closed
Distribution: Fedora
Kernel Version: 2.6
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 02-24-2005 01:14 CET
Last Modified: 12-31-2005 04:06 CET
======================================================================
Summary: No sound unless using OSS driver
Description:
I have no sound from the system unless using the OSS option in gstreamer
properties. If I do this I get sound but no control over the volume or
mute. I dont really need all the digital parts, but just the Basic sound
would be nice. I am going to include the ouput from the alsa debug program
I found online. Thanks for looking into this issue.
======================================================================
----------------------------------------------------------------------
jdthood - 04-13-05 17:24
----------------------------------------------------------------------
Submitter: Any improvement in the 1.0.9rc2 release?
----------------------------------------------------------------------
rlrevell - 12-31-05 04:06
----------------------------------------------------------------------
No response
Issue History
Date Modified Username Field Change
======================================================================
02-24-05 01:14 ruffasdagut New Issue
02-24-05 01:14 ruffasdagut File Added: debug.log
02-24-05 01:14 ruffasdagut Distribution => Fedora
02-24-05 01:14 ruffasdagut Kernel Version => 2.6
02-24-05 22:00 tiwai Note Added: 0003725
02-24-05 23:27 ruffasdagut Note Added: 0003730
02-24-05 23:29 ruffasdagut Issue Monitored: ruffasdagut
02-24-05 23:29 ruffasdagut Issue End Monitor: ruffasdagut
04-13-05 17:24 jdthood Note Added: 0004475
12-31-05 04:06 rlrevell Status new => closed
12-31-05 04:06 rlrevell Note Added: 0007337
======================================================================
-------------------------------------------------------
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-31 3:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-31 3:06 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-13 15:24 [ALSA - driver 0000937]: No sound unless using OSS driver bugtrack
2005-02-24 22:27 bugtrack
2005-02-24 21:00 bugtrack
2005-02-24 0:14 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=6fc01d968f24cf46217aa9561abf309a@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