From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001708]: Onboard sound using the intel-hda driver does not work on P5GD1-VM motherboards
Date: Fri, 21 Jul 2006 02:32:15 +0200 [thread overview]
Message-ID: <f50c9740d9743e7dc765ec6ab3644e37@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1708>
======================================================================
Reported By: keith81
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 1708
Category: PCI - hda-intel
Reproducibility: always
Severity: major
Priority: normal
Status: closed
Distribution:
Kernel Version:
Resolution: unable to duplicate
Fixed in Version:
======================================================================
Date Submitted: 01-04-2006 10:57 CET
Last Modified: 07-21-2006 02:32 CEST
======================================================================
Summary: Onboard sound using the intel-hda driver does not
work on P5GD1-VM motherboards
Description:
I raised this issue back in July or August and received no helpful
feedback. If you google the P5GD1-VMmobo name, along with alsa, you see
that many people with this mobo have not been able to get sound to work on
their installations of various distributions of linux.
Are there any future plans to include support for P5GD1-VM motherboards?
No sound is a deal-breaker for me when it comes to migrating.
I appreciate any feedback, whether it's getting sound to work on my
system, or someone saying support is in the pipes, or someone explaining
why support won't be coming.
Thanks! Happy new year!
======================================================================
----------------------------------------------------------------------
tiwai - 01-04-06 17:07
----------------------------------------------------------------------
First, try the latest ALSA release (1.0.11rc2 o CVS version).
Issue History
Date Modified Username Field Change
======================================================================
01-04-06 10:57 keith81 New Issue
01-04-06 17:07 tiwai Note Added: 0007435
07-21-06 02:32 Adrian Bunk Status assigned => closed
07-21-06 02:32 Adrian Bunk Resolution open => unable to
duplicate
======================================================================
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2006-07-21 0:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 0:32 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-04 16:07 [ALSA - driver 0001708]: Onboard sound using the intel-hda driver does not work on P5GD1-VM motherboards bugtrack
2006-01-04 9:57 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=f50c9740d9743e7dc765ec6ab3644e37@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