Re: [Alsa-user] snd-via82xx on EPIA-M - 0 analog subsections not ready

Re: [Alsa-user] snd-via82xx on EPIA-M - 0 analog subsections not ready

[Lee Revell]

On Thu, 2005-06-23 at 18:43 +0000, Sebastian Henschel wrote:
> 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

Re: snd-via82xx on EPIA-M - 0 analog subsections not ready

[Lee Revell]

On Thu, 2005-06-23 at 18:43 +0000, Sebastian Henschel wrote:
> 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

Re: [Alsa-user] snd-via82xx on EPIA-M - 0 analog subsections not ready

[Sebastian Henschel]

[-- Attachment #1.1: Type: text/plain, Size: 1585 bytes --]

hello Lee...

thanks for your reply...

* Lee Revell <rlrevell@joe-job.com> [2005-06-24 08:51 +0000]:
> On Thu, 2005-06-23 at 18:43 +0000, Sebastian Henschel wrote:
> > 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.



> 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.

 
> 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
-- 
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

[-- Attachment #1.2: asound.conf --]
[-- Type: text/plain, Size: 67 bytes --]

pcm.via82xx {
	type hw
	card 0
}

ctl.via82xx {
	type hw
	card 0
}

[-- Attachment #1.3: dmesg.oss --]
[-- Type: text/plain, Size: 298 bytes --]

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 64
ac97_codec: AC97 Audio codec, id: ICE82 (Unknown)
via82cxxx: board #1 at 0xE400, IRQ 10

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Re: [Alsa-user] snd-via82xx on EPIA-M - 0 analog subsections not ready

[Takashi Iwai]

At Fri, 24 Jun 2005 10:59:42 +0000,
Sebastian Henschel wrote:
> 
> hello Lee...
> 
> thanks for your reply...
> 
> * Lee Revell <rlrevell@joe-job.com> [2005-06-24 08:51 +0000]:
> > On Thu, 2005-06-23 at 18:43 +0000, Sebastian Henschel wrote:
> > > 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?

Yes, please.


> > 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

Re: Re: [Alsa-user] snd-via82xx on EPIA-M - 0 analog subsections not ready

[Sebastian Henschel]

[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]

hello....

* Takashi Iwai <tiwai@suse.de> [2005-06-24 22:18 +0000]:
> At Fri, 24 Jun 2005 10:59:42 +0000,
> Sebastian Henschel wrote:
> > 
> > * Lee Revell <rlrevell@joe-job.com> [2005-06-24 08:51 +0000]:
> > > On Thu, 2005-06-23 at 18:43 +0000, Sebastian Henschel wrote:
> > > > 
> > > > 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.

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.


> > > 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.

> Try acpi=off boot option once.

this used to be the default behaviour, there is no difference between on
and off.

thanks,
 Sebastian
-- 
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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]