[oe-issues] [Bug 1691] New: ALSA improperly configured on Akita

[bugzilla-daemon at tinman.treke.net]

http://bugs.openembedded.org/show_bug.cgi?id=1691

           Summary: ALSA improperly configured on Akita
           Product: Openembedded
           Version: Angstrom
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Distributions
        AssignedTo: openembedded-issues at lists.openembedded.org
        ReportedBy: armagon_ca at yahoo.ca
         QAContact: tinderbox-oe at gmx.net
                CC: armagon_ca at yahoo.ca


SUMMARY
-------

ALSA complains about things being improperly configured the first time after
booting up a newly-flashed version of Angstrom 20061214.

Koen thought it might be a zaurusd/ASoc mismatch.

STEPS
-----

I flashed the Angstrom testing build, available at
http://www.angstrom-distribution.org/unstable/images/20061214/akita/, onto my
Akita, following the instructions at
http://www.angstrom-distribution.org/c1000-install-instructions.

After flashing, the system booted up.  I waited until the splash screen
disappeared and I could log in.  On the screen, the following text appeared:

------------

dropbear.
Starting wpa_supplicant: done.
Starting advanced power management daemon: apmd[1433]: apmd 3.2.1 interfacing
with apm driver 1.13 and APM BIOS 1.2
apmd.
Starting IrDA: .
Starting syslogd/klogd: done
/usr/sbin/alsactl: set_control:991: warning: name mismatch (Out1 Playback ZC
Switch/Headphone Playback ZC Switch) for control #4
/usr/sbin/alsactl: set_control:993: warning: index mismatch (0/0) for control
#4
/usr/sbin/alsactl: set_control:991: warning: name mismatch (Out2 Playback ZC
Switch/Headphone Playback ZC Switch) for control #5
/usr/sbin/alsactl: set_control:993: warning: index mismatch (0/0) for control
#5
/usr/sbin/alsactl: set_control:995: failed to obtain info for control #5
(Interrupted system call)
Starting Zaurusd
/usr/sbin/alsactl: set_control:991: warning: name mismatch (Out1 Playback ZC
Switch/Headphone Playback ZC Switch) for control #4
/usr/sbin/alsactl: set_control:993: warning: index mismatch (0/0) for control
#4
/usr/sbin/alsactl: set_control:991: warning: name mismatch (Out2 Playback ZC
Switch/Headphone Playback ZC Switch) for control #5
/usr/sbin/alsactl: set_control:993: warning: index mismatch (0/0) for control
#5
/usr/sbin/alsactl: set_control:995: failed to obtain info for control #5
(Interrupted system call)
psplash.c:91,parse_command() got cmd PROGRESS 99
psplash.c:76,psplash_draw_progress() total w: 222, val :99, w: 219
psplash.c:91,parse_command() got cmd QUIT

Angstrom test-20061215 akita tty1

akita login: JFFS2 notice: (800) check_node_data: wrong data CBC in data node
at 0x03a24800: read 0x57ced80d, calculated 0xc1e047ac.

------------

[I should note that I flashed a second time, and pressed alt-left while the
splash screen was up.  This enabled me to record more text.  The second time
the psplash messages were not displayed.  Oh, and the JFFS2 notice was
different.]

Notice that there are a lot of warning messages from alsactl.


On subsequent reboots, the messages go away.  They can only be seen the first
time after flashing.

Afterwards, I see:

------------

Starting Dropbear SSH server: dropbear.
Starting wpa_supplicant: done.
Starting advanced power management daemon: apmd[1030]: apmd 3.2.1 interfacing
with apm driver 1.13 and APM BIOS 1.2
apmd.
Starting IrDA: .
Starting syslogd/klogd: done
Starting Zaurusd

Angstrom test-20061215 akita tty1

akita login: JFFS2 notice: (881) check_node_data: wrong data CBC in data node
at 0x03a24800: read 0x57ced80d, calculated 0xc1e047ac.

------------

DIAGNOSTICS
-----------

'lsmod' yielded:

Module                  Size  Used by
uinput                  7392  0 
snd_soc_spitz           5420  0 
snd_soc_pxa2xx_i2s      3512  1 snd_soc_spitz
snd_soc_wm8750         19396  1 snd_soc_spitz
snd_soc_pxa2xx          4256  1 snd_soc_spitz
snd_soc_core           34100  3 snd_soc_spitz,snd_soc_wm8750,snd_soc_pxa2xx
snd_pcm_oss            48800  0 
snd_pcm                81093  3 snd_soc_pxa2xx,snd_soc_core,snd_pcm_oss
snd_timer              22180  1 snd_pcm
snd_page_alloc          6216  1 snd_pcm
snd_mixer_oss          15456  1 snd_pcm_oss
snd                    51060  7
snd_soc_spitz,snd_soc_wm8750,snd_soc_core,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore               8100  1 snd
pxaficp_ir              8736  0 
ircomm_tty             21224  0 
ircomm                 11396  1 ircomm_tty
irda                  113128  3 pxaficp_ir,ircomm_tty,ircomm


A portion of 'dmesg > dmesg.txt' says:

<4>Empty flash at 0x00797ffc ends at 0x00798000
<4>Empty flash at 0x0079bffc ends at 0x0079c000
<4>VFS: Mounted root (jffs2 filesystem) readonly.
<6>Freeing init memory: 80K
<6>NET: Registered protocol family 23
<6>IrCOMM protocol (Dag Brattli)
<6>ASoC version 0.12.4
<6>WM8750: WM8750 Audio Codec 0.11
<6>asoc: WM8750 <-> pxa2xx-i2s mapping ok
<4>Empty flash at 0x00003ffc ends at 0x00004000


DESIRED RESULTS
---------------

Things should be configured properly.  Also, I assume that some sort of noise
is supposed to sound at bootup, but no such noise occurs.


-- 
Configure bugmail: http://bugs.openembedded.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.