snd-via82xx on EPIA-M - 0 analog subsections not ready
Quoted 4 lines · Sebastian Henschel
hi list,
i am working on a machine with an EPIA-M mainboard and the ICEensemble VT1616i sound chip (see attached lspci -v).
Thanks, this is an excellent bug report. It sounds like a not quite fully supported device.
On a related topic, it seems like a lot of users waste hours and hours changing settings before they even consider that they might have a hardware variation we have not seen before.
Since these problems will not go away until every vendor gives us full hardware specs, aka when hell freezes over, it would probably help to add to those printks ('Unknown codec', etc) some text to the effect that it's possibly an unknown device and they should contact alsa-devel ASAP. Other subsystems do things like this and it works, everyone knows to check dmesg, and they will do what you tell them to ;-)
I'll see if I can identify the specific errors that could indicate an unknown device, or anything other situation where something very strange has happened and we want the user to contact us with the details. Any suggestions?
Lee
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 4 lines · Sebastian Henschel
hi list,
i am working on a machine with an EPIA-M mainboard and the ICEensemble VT1616i sound chip (see attached lspci -v).
Thanks, this is an excellent bug report. It sounds like a not quite fully supported device.
On a related topic, it seems like a lot of users waste hours and hours changing settings before they even consider that they might have a hardware variation we have not seen before.
Since these problems will not go away until every vendor gives us full hardware specs, aka when hell freezes over, it would probably help to add to those printks ('Unknown codec', etc) some text to the effect that it's possibly an unknown device and they should contact alsa-devel ASAP. Other subsystems do things like this and it works, everyone knows to check dmesg, and they will do what you tell them to ;-)
I'll see if I can identify the specific errors that could indicate an unknown device, or anything other situation where something very strange has happened and we want the user to contact us with the details. Any suggestions?
Lee
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
hello Lee...
thanks for your reply...
Quoted 8 lines · Lee Revell
Quoted 4 lines · Sebastian Henschel
hi list,
i am working on a machine with an EPIA-M mainboard and the ICEensemble VT1616i sound chip (see attached lspci -v).
Thanks, this is an excellent bug report. It sounds like a not quite fully supported device.
so should i open a bug report on that?
btw, i forgot to attach the dmesg for the OSS driver and my /etc/asound.conf. here you got.
Quoted 3 lines
On a related topic, it seems like a lot of users waste hours and hours changing settings before they even consider that they might have a hardware variation we have not seen before.
given that the BIOS is dated from somewhere from 2004 and that the EPIA-M is not unpopular, i would have thought it is well-known. but perhaps this is just another hardware revision (rev 50 in this case) which might do something slightly different than the revisions before.
Quoted 4 lines
I'll see if I can identify the specific errors that could indicate an unknown device, or anything other situation where something very strange has happened and we want the user to contact us with the details. Any suggestions?
check for the hardware revision, if possible.
thanks,
Sebastian
Signature · 4 lines
Oo.....................
wer ein ganzer mensch ist, braucht keine autoritaet zu sein.
OpenPGP key ID: 0x4A1F5E81 Geekcode: GCSd-s:a-C++ULB+++W++M+PS+++
..................oOpcm.via82xx {
type hw
card 0
}
ctl.via82xx {
type hw
card 0
}
Via 686a/8233/8235 audio driver 1.9.1-ac4-2.5
ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 10 (level, low) -> IRQ 10
via82cxxx: Six channel audio available
PCI: Setting latency timer of device 0000:00:11.5 to 64ac97_codec: AC97 Audio codec, id: ICE82 (Unknown)
via82cxxx: board #1 at 0xE400, IRQ 10
At Fri, 24 Jun 2005 10:59:42 +0000,
Quoted 9 lines · Sebastian Henschel
hello Lee...
thanks for your reply...
Quoted 3 lines · Lee Revell
Quoted 2 lines · Sebastian Henschel
hi list,
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
i am working on a machine with an EPIA-M mainboard and the ICEensemble VT1616i sound chip (see attached lspci -v).
Thanks, this is an excellent bug report. It sounds like a not quite fully supported device.
so should i open a bug report on that?
Yes, please.
Quoted 8 lines
Quoted 3 lines
On a related topic, it seems like a lot of users waste hours and hours changing settings before they even consider that they might have a hardware variation we have not seen before.
given that the BIOS is dated from somewhere from 2004 and that the EPIA-M is not unpopular, i would have thought it is well-known. but perhaps this is just another hardware revision (rev 50 in this case) which might do something slightly different than the revisions before.
Also, this kind of bug depends pretty upon the BIOS. Try acpi=off boot option once.
Takashi
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
hello....
Quoted 9 lines · Takashi Iwai
At Fri, 24 Jun 2005 10:59:42 +0000,
Quoted 7 lines · Sebastian Henschel
Quoted 5 lines · Lee Revell
Quoted 3 lines · Sebastian Henschel
i am working on a machine with an EPIA-M mainboard and the ICEensemble VT1616i sound chip (see attached lspci -v).
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Thanks, this is an excellent bug report. It sounds like a not quite fully supported device.
so should i open a bug report on that?
Yes, please.
ok, done: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1213
the contents of /proc/asound/card0/codec97#0/ will follow when i have access to the machine again.
Quoted 10 lines
Quoted 8 lines
Quoted 3 lines
On a related topic, it seems like a lot of users waste hours and hours changing settings before they even consider that they might have a hardware variation we have not seen before.
given that the BIOS is dated from somewhere from 2004 and that the EPIA-M is not unpopular, i would have thought it is well-known. but perhaps this is just another hardware revision (rev 50 in this case) which might do something slightly different than the revisions before.
Also, this kind of bug depends pretty upon the BIOS.
will try to upgrade the BIOS.
Quoted 1 line
Try acpi=off boot option once.
this used to be the default behaviour, there is no difference between on and off.
thanks,
Sebastian
Signature · 4 lines
Oo.....................
wer ein ganzer mensch ist, braucht keine autoritaet zu sein.
OpenPGP key ID: 0x4A1F5E81 Geekcode: GCSd-s:a-C++ULB+++W++M+PS+++
..................oO