From: Jared J. <jje...@gm...> - 2008-02-19 02:47:50
|
hello all, when I boot my verdex xm4bt with audiostix2 and netwifiuSD-vx-FCC, my dmesg says (among other things) <6>AC97 SoC Audio Codec 0.6 <6>asoc: AC97 HiFi <-> pxa2xx-ac97 mapping ok <6>pxa2xx_ac97_cold_reset: cold reset timeout (GSR=0x0) <3>pxa2xx_ac97_read: read error (ac97_reg=7c GSR=0x444) <3>pxa2xx_ac97_read: read error (ac97_reg=7e GSR=0x444) <3>AC'97 0 access is not valid [0xffffffff], removing mixer. <4>soc-audio: probe of soc-audio failed with error -5 When I remove all sound-related modules - root@gumstix-custom-verdex:~$ lsmod | grep snd | awk '{print $1}' | xargs rmmod and reprobe - root@gumstix-custom-verdex:~$ modprobe snd-pxa2xx-ac97 the new messages in the dmesg go like so - <6>pxa2xx_ac97_reset: cold reset timeout (GSR=0x0) <6>pxa2xx_ac97_reset: warm reset timeout (GSR=0x0) <3>pxa2xx_ac97_read: read error (ac97_reg=124 GSR=0x444) <3>pxa2xx_ac97_read: read error (ac97_reg=126 GSR=0x444) <3>AC'97 0 access is not valid [0xffffffff], removing mixer. <4>pxa2xx-ac97: probe of pxa2xx-ac97 failed with error -5 Tried it with my own custom build rootfs+kernel, then with stock r224 glibc, then with r218 uclibc; same results each time. Any ideas? (Fun unique word to search for later: Cortana.) |
From: Simon F. <Sim...@im...> - 2008-02-20 08:14:32
|
Hi, I saw an error just like this when I took too much current out of a GPSStix board (so the supply power dropped enough to turn the chips off). This message seems to be the default one if the gumstix board can't "see" the audio chip. You could try checking that the boards aren't touching, are clipped together properly and if possible that the supply voltage on the board is at a reasonable level. If doing all the obvious things doesn't fix it then it sounds like its probably a faulty board... Simon On Tuesday 19 February 2008 02:47:54 Jared Jennings wrote: > hello all, when I boot my verdex xm4bt with audiostix2 and > netwifiuSD-vx-FCC, my dmesg says (among other things) > > <6>AC97 SoC Audio Codec 0.6 > <6>asoc: AC97 HiFi <-> pxa2xx-ac97 mapping ok > <6>pxa2xx_ac97_cold_reset: cold reset timeout (GSR=0x0) > <3>pxa2xx_ac97_read: read error (ac97_reg=7c GSR=0x444) > <3>pxa2xx_ac97_read: read error (ac97_reg=7e GSR=0x444) > <3>AC'97 0 access is not valid [0xffffffff], removing mixer. > <4>soc-audio: probe of soc-audio failed with error -5 > > When I remove all sound-related modules - > root@gumstix-custom-verdex:~$ lsmod | grep snd | awk '{print $1}' | xargs > rmmod > > and reprobe - > root@gumstix-custom-verdex:~$ modprobe snd-pxa2xx-ac97 > > the new messages in the dmesg go like so - > > <6>pxa2xx_ac97_reset: cold reset timeout (GSR=0x0) > <6>pxa2xx_ac97_reset: warm reset timeout (GSR=0x0) > <3>pxa2xx_ac97_read: read error (ac97_reg=124 GSR=0x444) > <3>pxa2xx_ac97_read: read error (ac97_reg=126 GSR=0x444) > <3>AC'97 0 access is not valid [0xffffffff], removing mixer. > <4>pxa2xx-ac97: probe of pxa2xx-ac97 failed with error -5 > > Tried it with my own custom build rootfs+kernel, then with stock r224 > glibc, then with r218 uclibc; same results each time. > > Any ideas? > > (Fun unique word to search for later: Cortana.) > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Jared J. <jje...@gm...> - 2008-02-24 22:54:37
|
> I saw an error just like this when I took too much current out of a GPSStix > board (so the supply power dropped enough to turn the chips off). This > message seems to be the default one if the gumstix board can't "see" the > audio chip. > > You could try checking that the boards aren't touching, are clipped together > properly and if possible that the supply voltage on the board is at a > reasonable level. If doing all the obvious things doesn't fix it then it > sounds like its probably a faulty board... tried reseating and inspecting several times; power supply is from the supplied wall wart so i'm assuming it's the right voltage and current. :/ thanks for the pointer. |