From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000937]: No sound unless using OSS driver
Date: Wed, 13 Apr 2005 17:24:04 +0200 [thread overview]
Message-ID: <c9d7be625c8bb8dee519880c693ff4f5@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<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: new
Distribution: Fedora
Kernel Version: 2.6
======================================================================
Date Submitted: 02-24-2005 01:14 CET
Last Modified: 04-13-2005 17:24 CEST
======================================================================
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.
======================================================================
----------------------------------------------------------------------
ruffasdagut - 02-24-05 23:27
----------------------------------------------------------------------
Either I didnt install the CVS properly or it didnt fix the problem. I have
sound, but no control over the volume. I am not 100% I did the CVS install
correct. Also did I need to remove the version that Fedora put?
----------------------------------------------------------------------
jdthood - 04-13-05 17:24
----------------------------------------------------------------------
Submitter: Any improvement in the 1.0.9rc2 release?
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
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-04-13 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 15:24 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-31 3:06 [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=c9d7be625c8bb8dee519880c693ff4f5@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