Date: Sat, 22 Aug 2009 15:08:33 +0200 (CEST) From: Gheorghe Ardelean <ardelean@ww.uni-erlangen.de> To: Marius Strobl <marius@alchemy.franken.de> Cc: freebsd-sparc64@freebsd.org Subject: Re: Audio on Sunblade 100 Message-ID: <alpine.LNX.2.00.0908221457030.19124@servww6.ww.uni-erlangen.de> In-Reply-To: <20090821193740.GA66639@alchemy.franken.de> References: <4A7C6B50.3070503@networkz.ch> <20090817205340.GA75477@alchemy.franken.de> <20090817215612.GB75477@alchemy.franken.de> <20090818192748.GA6585@alchemy.franken.de> <20090819161410.GA19351@alchemy.franken.de> <4A8DC0DF.4040701@networkz.ch> <alpine.LNX.2.00.0908211010390.13578@servww6.ww.uni-erlangen.de> <4A8EDE72.6040703@networkz.ch> <20090821193740.GA66639@alchemy.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 21 Aug 2009, Marius Strobl wrote:
> On Fri, Aug 21, 2009 at 07:50:42PM +0200, Christian Ramseyer wrote:
>> Gheorghe Ardelean wrote:
>>>
>>> On Thu, 20 Aug 2009, Christian Ramseyer wrote:
>>>
>>> [...]
>>>> As it worked for Gheorghe, chances are that I'm doing something
>>>> wrong/different:
>>>
>>> Now I have tested also mpg321 and it has a not that good sound quality.
>>> A lot of noise is coming out but the sound is there all the time. The
>>> noise is coming always on the bass (maybe drums?) parts.
>>>
>>> Christian, could please also test mpg123 and let us know if you get
>>> different results?
>>>
>>
>> I've got maybe 10 seconds of sound, then silence and these messages:
>>
>> [audio.c:596] error: Error in writing audio (Invalid argument?)!
>> [mpg123.c:577] error: Deep trouble! Cannot flush to my output anymore!
>>
>> There was the "usual" message:
>> pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead
>>
>> Also, I have the impressions that the rare events where I get some
>> seconds of sound only occur when the box was powered down for some time
>> before, subsequent attempts (also after reboot without power cycle)
>> never seem to produce sound.
>
> Given that the driver works for Gheorghe with the same
> hardware model I suspect an initialization issue based
> on different firmware revsions. Could both of you please
> run `pciconf -lv` and report the two lines starting
> with isab0 and pcm0 (just these two lines, not the
> whole output from that command).
isab0@pci0:0:7:0: class=0x060100 card=0x153310b9 chip=0x153310b9
rev=0x00 hdr=0x00
vendor = 'Acer Labs Incorporated (ALi/ULi)'
device = 'ALI M1533 Aladdin IV ISA Bridge'
class = bridge
subclass = PCI-ISA
pcm0@pci0:0:8:0: class=0x040100 card=0x545110b9 chip=0x545110b9
rev=0x01 hdr=0x00
vendor = 'Acer Labs Incorporated (ALi/ULi)'
device = 'ALI M5451 PCI AC-Link Controller Audio Device'
class = multimedia
subclass = audio
> Then get a complete
> dump of the PCI configuration header by running
> `pciconf -rb <seletor> 0:255` on the selectors
> contained in the isab0 and pcm0 strings, for example:
> `pciconf -rb isab0@pci0:1:7:0 0:255`
blade100# pciconf -rb isab0@pci0:0:7:0 0:255
b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 b9 10 33 15
00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
11 13 49 80 83 09 00 07 00 00 00 10 00 00 fd 01
00 00 00 40 00 07 02 00 6e 03 09 00 00 00 00 08
00 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00
00 00 06 00 41 03 00 d3 04 02 00 04 00 00 01 10
07 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
blade100# pciconf -rb pcm0@pci0:0:8:0 0:255
b9 10 51 54 07 00 90 02 01 00 01 04 00 10 00 00
01 09 00 00 00 40 42 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 b9 10 51 54
00 00 00 00 dc 00 00 00 00 00 00 00 23 01 02 18
00 00 00 00 00 04 00 e2 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 01 00 22 e6
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Please also report the pcm0 parts of a verbose boot
> (stop the boot count-down by pressing space and
> issue a `set boot_verbose`, followed by `boot`, then
> get the pcm0 lines from for example the dmesg-output).
blade100# dmesg | grep ^pcm
pcm0: <Acer Labs M5451> port 0x900-0x9ff mem 0x424000-0x424fff at device
8.0 on pci0
pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x900
pcm0: <Analog Devices AD1881A AC97 Codec (id = 0x41445348)>
pcm0: Codec features headphone, 6 bit master volume, Analog Devices Phat
Stereo
pcm0: Primary codec extended features variable rate PCM
pcm0: ac97 codec dac ready count: 0
pcm0: Mixer "vol":
pcm0: Mixer "pcm":
pcm0: Mixer "speaker":
pcm0: Mixer "line":
pcm0: Mixer "mic":
pcm0: Mixer "cd":
pcm0: Mixer "rec":
pcm0: Mixer "igain":
pcm0: Mixer "line1":
pcm0: Mixer "phin":
pcm0: Mixer "phout":
pcm0: Mixer "video":
pcm0: [GIANT-LOCKED]
pcm0: [ITHREAD]
pcm0: M1533 0x7e: 0x1 -> 0x1
pcm0: clone manager: deadline=750ms flags=0x8000001e
pcm0: sndbuf_setmap c1140000, 10000; 0xc0c62000 -> c1140000
pcm0: sndbuf_setmap c1160000, 10000; 0xc0c82000 -> c1160000
>> From the symptoms Gheorghe reported for mpg321 I suspect
> it has some LP64 and/or endian bugs, while mpg123 hasn't.
> IIRC Yongari once also had a fix for such a bug in XMMS,
> which isn't necessarily the cause for the above problem
> though.
I have also a second blade 100. I wil test on monday on it (it's at work).
Regards,
Gheorghe Ardelean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LNX.2.00.0908221457030.19124>