From: Toni Erdmann <toni.erdmann-S0/GAf8tV78@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: mobo A7V600-F and problems with sound
Date: Tue, 24 Feb 2004 16:38:23 +0100 [thread overview]
Message-ID: <403B6FEF.1000609@web.de> (raw)
In-Reply-To: <1077518290.12669.49.camel-D2Zvc0uNKG8@public.gmane.org>
Len Brown wrote
>go ahead and file the bug and make the tar-ball an attachment.
>
>would be good if you can try a 2.6.3 kernel, I don't really know what is
>in suse's 2.4.21-166-athlon kernel.
>
>thanks,
>-Len
>
Hello,
I tried to post a bug at bugzilla.kernel.org for 'sound' and 2.6.3 but
got an internal
error : "THE MAINTAINER HAS NOT YET BEEN SET" and
"A legal Archtecture was not set".
Anyway, there's no hint in 'dmesg' for problems with ACPI, but sound does
not work with 2.6.3 either.
"ALSA sound/pci/via82xx.c:585: codec_read: codec 0 is not valid [0xfe0000]"
Same message (with 'codec_valid') appeard with 2.4.21-...
Thnaks,
Toni
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-02-24 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 19:07 mobo A7V600-F and problems with sound Toni Erdmann
[not found] ` <4038FDDB.8090807-S0/GAf8tV78@public.gmane.org>
2004-02-23 6:38 ` Len Brown
[not found] ` <1077518290.12669.49.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-24 15:38 ` Toni Erdmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-24 18:07 Brown, Len
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=403B6FEF.1000609@web.de \
--to=toni.erdmann-s0/gaf8tv78@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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