From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000552]: FATAL: Error inserting snd_azx
Date: Tue, 23 Nov 2004 22:04:14 +0100 [thread overview]
Message-ID: <a3e4e3d590a735e31b08cecb7f00fde8@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=552>
======================================================================
Reported By: footcow
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 552
Category: PCI - azx
Reproducibility: always
Severity: block
Priority: normal
Status: new
Distribution: Debian
Kernel Version: 2.6.8.1
======================================================================
Date Submitted: 09-30-2004 01:29 CEST
Last Modified: 11-23-2004 22:04 CET
======================================================================
Summary: FATAL: Error inserting snd_azx
Description:
Impossible to make running the AZX Alsa driver on my PC, ASUS P5GD2 Premium
motherbord with 0000:00:1b.0 0403: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) High Definition Audio Controller (rev 03) integrated sound.
======================================================================
----------------------------------------------------------------------
footcow - 11-23-04 22:01
----------------------------------------------------------------------
No sorry I put another bug report for last release 1.0.7 ...
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=666
I have no sound, no mixer ... more details in this bug report ...
But since 1.0.7rc2 ... the module loaded do not crash anymore my linux
:o)
But I will be really happy to give you some help for testing with my
configuration (AsusTek P5GD2) ... I really want to get sound ! ;o)
----------------------------------------------------------------------
rlrevell - 11-23-04 22:04
----------------------------------------------------------------------
OK then this one should be closed.
Issue History
Date Modified Username Field Change
======================================================================
09-30-04 01:29 footcow New Issue
09-30-04 01:29 footcow Distribution => Debian
09-30-04 01:29 footcow Kernel Version => 2.6.8.1
11-23-04 21:48 footcow Note Added: 0002529
11-23-04 21:54 rlrevell Note Added: 0002532
11-23-04 22:01 footcow Note Added: 0002533
11-23-04 22:04 rlrevell Note Added: 0002534
======================================================================
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
next reply other threads:[~2004-11-23 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 21:04 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-27 14:48 [ALSA - driver 0000552]: FATAL: Error inserting snd_azx bugtrack
2004-11-24 11:28 bugtrack
2004-11-23 21:01 bugtrack
2004-11-23 20:54 bugtrack
2004-11-23 20:48 bugtrack
2004-09-29 23:29 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=a3e4e3d590a735e31b08cecb7f00fde8@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 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.