From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000365]: No audio with Asus p4p800-vm
Date: Thu, 8 Jul 2004 20:30:44 +0200 [thread overview]
Message-ID: <c0a7ecb72b119d3bbde5e1a652942661@bugtrack.alsa-project.org> (raw)
A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000365
======================================================================
Reported By: Anlar
Assigned To:
======================================================================
Project: ALSA - driver
Bug ID: 365
Category: PCI - intel8x0
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Gentoo - up to date stable
Kernel Version: 2.6.7
======================================================================
Date Submitted: 07-04-2004 20:53 CEST
Last Modified: 07-08-2004 20:30 CEST
======================================================================
Summary: No audio with Asus p4p800-vm
Description:
I have new Asus P4P800-VM motherboard (865G) that has i8x0 (x=1?) (ADI1980)
builtin. Alsa does seem to initialize, the required modules load and
something gets fed to the device but nothing comes out. I have played
around with the mixer volumes and done other known usual stuff as well.
A googling session revealed that some people have had success with this
motherboard but most of the people have failed. I thought that something
on this motherboard might be non-standard and require attention.
(If it is trivial, something t be added to the wikis. I doubt though since
couple guys have tried already and none of them were complete newbies.)
======================================================================
----------------------------------------------------------------------
Anlar - 07-06-2004 22:04 CEST
----------------------------------------------------------------------
Tried also with 2004-06-02 cvs version. Still playing mute. This sound chip
isn't listed as one that requires some "quirks" thingy, whatever that
means..
Something interesting in dmesg though:
ALSA /tmp/alsa/alsa-driver/alsa-kernel/pci/ac97/ac97_codec.c:1922: AC'97 0
analog subsections not ready
intel8x0_measure_ac97_clock: measured 49414 usecs
intel8x0: clocking to 48000
"not ready"?
Did some extensive googling.. Check these out?
http://www.mail-archive.com/freebsd-hackers@freebsd.org/msg41462.html
http://www.mail-archive.com/freebsd-hackers@freebsd.org/msg42365.html
Something of help there?
----------------------------------------------------------------------
Anlar - 07-07-2004 17:32 CEST
----------------------------------------------------------------------
I did the
ac97_quirk= 0-4
thingy just in case.. This time while playing with mixer I heard couple
faint cracks when I unmuted the channels. Very faint.
Tried something older, with a kernel 2.6.2 provided alsa. Still silent.
edited on: 07-07-04 17:32
----------------------------------------------------------------------
Anlar - 07-07-2004 22:02 CEST
----------------------------------------------------------------------
Played around with Knoppix, couldn't get working with its 2.4.26. Not even
on OSS, it seems to be btw failing too.
Updated the motherboard bios to the newest version, no improvement.
----------------------------------------------------------------------
Anlar - 07-08-2004 20:30 CEST
----------------------------------------------------------------------
Managed to stole me a spdif module. They seem to be mostly universal and
compatible amongst vendors - very simple. Guess what? I've got Hotel
California playing in my room! Whee! Still have to use iron saw to make
the pci back plate "low profile" to fit inside the case.
Didn't have to touch anything special. Just asked for the "default" sound
source to be used, enabled the digital output from the mixer and voila.
The analogs are still dead as stone. Been playing around with the mixer a
lot. Any ideas?
Bug History
Date Modified Username Field Change
======================================================================
07-04-04 20:53 Anlar New Bug
07-04-04 20:53 Anlar Distribution => Gentoo - up to date
stable
07-04-04 20:53 Anlar Kernel Version => 2.6.7
07-04-04 20:54 Anlar Bug Monitored: Anlar
07-06-04 22:04 Anlar Bugnote Added: 0001387
07-06-04 22:29 Anlar File Added: asound.state
07-06-04 22:58 Anlar Bugnote Added: 0001389
07-06-04 22:59 Anlar Bugnote Edited: 0001389
07-07-04 17:32 Anlar Bugnote Edited: 0001389
07-07-04 22:02 Anlar Bugnote Added: 0001394
07-08-04 20:30 Anlar Bugnote Added: 0001395
======================================================================
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next reply other threads:[~2004-07-08 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 18:30 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-01 0:02 [ALSA - driver 0000365]: No audio with Asus p4p800-vm bugtrack
2005-12-30 4:18 bugtrack
2005-03-25 18:40 bugtrack
2005-03-23 15:09 bugtrack
2004-07-16 18:09 noreply
2004-07-16 10:14 noreply
2004-07-07 20:02 noreply
2004-07-06 20:58 noreply
2004-07-06 20:04 noreply
2004-07-04 18:53 noreply
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=c0a7ecb72b119d3bbde5e1a652942661@bugtrack.alsa-project.org \
--to=noreply@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.