From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001033]: hda sound 82801FB/FBM/FR/FW/FRW (ICH6 Family)
Date: Tue, 5 Apr 2005 14:52:41 +0200 [thread overview]
Message-ID: <41f56477ef62edede581d4ce37d98868@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1033>
======================================================================
Reported By: sjankie
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1033
Category: PCI - azx
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution:
Kernel Version: 2.6.11.6
======================================================================
Date Submitted: 04-03-2005 15:07 CEST
Last Modified: 04-05-2005 14:52 CEST
======================================================================
Summary: hda sound 82801FB/FBM/FR/FW/FRW (ICH6 Family)
Description:
0000:00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) High Definition Audio Controller (rev 04)
azx driver compliens about: NO AFG found.
alsmixer starts, but no sound.
======================================================================
----------------------------------------------------------------------
1g0R - 04-04-05 17:09
----------------------------------------------------------------------
Hi,
I have Asus p5Ad2-e Premium motherboard with intel HDA sound.
I use alsa 1.0.9rc2 with option "snd name" model=full_dig in
modprobe.conf
and its working SPDIF, and analog output.
Check your /usr/lib or /usr/local/lib alsa module files.
----------------------------------------------------------------------
sjankie - 04-05-05 14:52
----------------------------------------------------------------------
Can you give me your lspci output?
Can you be more spec. about the
model=full_dig, driver nags about: unknow word: model
TNX,
Sjankie
Issue History
Date Modified Username Field Change
======================================================================
04-03-05 15:07 sjankie New Issue
04-03-05 15:07 sjankie Kernel Version => 2.6.11.6
04-03-05 15:08 sjankie Issue Monitored: sjankie
04-03-05 15:08 sjankie Issue End Monitor: sjankie
04-03-05 15:08 sjankie Issue Monitored: sjankie
04-04-05 17:09 1g0R Note Added: 0004328
04-05-05 14:52 sjankie Note Added: 0004337
======================================================================
-------------------------------------------------------
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-05 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 12:52 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-24 2:42 [ALSA - driver 0001033]: hda sound 82801FB/FBM/FR/FW/FRW (ICH6 Family) bugtrack
2005-10-05 2:48 bugtrack
2005-09-29 19:59 bugtrack
2005-04-08 19:08 bugtrack
2005-04-05 17:50 bugtrack
2005-04-04 15:09 bugtrack
2005-04-03 13:07 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=41f56477ef62edede581d4ce37d98868@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