Re: [Openvortex-dev] Driver initialization problem for au8810 in Asus Laptop

[Jeff Muizelaar]

On Sun, 25 May 2003, Raffaele Brancaleoni wrote:

> Hi all,
>
> Just to inform you I've run into a problem with the driver
> initialization on my Asus laptop (L8400-B, equipped with an AU8810).
>
> I retreived the CVS version of the alsa driver three days ago.
> Compilation succeeded without any hassles (cards enabled: mpu401 & au8810).
>
> Usual infos:
> #uname -a
> Linux nightawk.tenebrae.be 2.4.20 #1 Sat May 17 22:14:54 CEST 2003 i686
> Pentium III (Coppermine) GenuineIntel GNU/Linux
>
> #gcc --version
> gcc (GCC) 3.2.2 20030322 (Gentoo Linux 1.4 3.2.2-r2)
> Copyright (C) 2002 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> When I try to load the driver (modprobe snd-au8810) I get the following
> messages:
>
> Vortex: hardware shutdown...removed last mix
> bad wt fifo reset (0x0001607c, 0x0002dead)!
> bad wt fifo reset (0x00016078, 0x0002dead)!
> bad wt fifo reset (0x00016074, 0x0002dead)!
> bad wt fifo reset (0x00016070, 0x0002dead)!
> bad wt fifo reset (0x0001606c, 0x0002dead)!
> bad wt fifo reset (0x00016068, 0x0002dead)!
> bad wt fifo reset (0x00016064, 0x0002dead)!
> bad wt fifo reset (0x00016060, 0x0002dead)!
> bad wt fifo reset (0x0001605c, 0x0002dead)!
> bad wt fifo reset (0x00016058, 0x0002dead)!
> bad wt fifo reset (0x00016054, 0x0002dead)!
> bad wt fifo reset (0x00016050, 0x0002dead)!
> bad wt fifo reset (0x0001604c, 0x0002dead)!
> bad wt fifo reset (0x00016048, 0x0002dead)!
> bad wt fifo reset (0x00016044, 0x0002dead)!
> bad wt fifo reset (0x00016040, 0x0002dead)!
> bad wt fifo reset (0x0001603c, 0x0002dead)!
> bad wt fifo reset (0x00016038, 0x0002dead)!
> bad wt fifo reset (0x00016034, 0x0002dead)!
> bad wt fifo reset (0x00016030, 0x0002dead)!
> bad wt fifo reset (0x0001602c, 0x0002dead)!
> bad wt fifo reset (0x00016028, 0x0002dead)!
> bad wt fifo reset (0x00016024, 0x0002dead)!
> bad wt fifo reset (0x00016020, 0x0002dead)!
> bad wt fifo reset (0x0001601c, 0x0002dead)!
> bad wt fifo reset (0x00016018, 0x0002dead)!
> bad wt fifo reset (0x00016014, 0x0002dead)!
> bad wt fifo reset (0x00016010, 0x0002dead)!
> bad wt fifo reset (0x0001600c, 0x0002dead)!
> bad wt fifo reset (0x00016008, 0x0002dead)!
> bad wt fifo reset (0x00016004, 0x0002dead)!
> bad wt fifo reset (0x00016000, 0x0002dead)!
> done.
>
> The driver stays loaded, but I cannot play anything (audio devices
> exist in /dev/sound/). I tried to load OSS emulation modules, and tried
> again, no success again. I checked the mute status with alsa mixer,
> mixer failed to start.
>
> Just to clear doubts, the old driver works fine with my laptop
> (beside the "ticks" problems).
>
> I checked the driver source but I lack chip knowledge and driver
> programming practice. From the messages, it looks like a WT DMA fifo
> initialization problem (base address problem ?).

This is now fixed in cvs, the code that was causing the message shouldn't
be run on the au8810.

> I'll recompile the driver with debugging enabled and try again.
>
> In the meantime, can any of you tell me what I should have a look at or
> is there a way to verify the base address value on my particular machine?
>
> If you need further info, do not hesitate to let me know!

The results of an lspci -vv -d 12eb:0003 would be nice, along with a dmesg
starting at driver load.

-Jeff