2009-06-18 11:24:36 Alsa problem in trunk (before 2.6.30 update) on bf527
Stefan Wanja (GERMANY)
Message: 75976
Hello,
I try to get Alsa working but there is a strange problem.
Kernel is 2.6.28-10-ADI-2009R1-pre-svn6316, uclinux-dist revision is 8277. Board is bf527 EZkit and I'm using the internal codec (ssm2602)
It builds fine, but when I load the module snd-ssm-2602 it says:
modprobe snd-ssm2602
dma rx:3 tx:4, err irq:15, regs:ffc00800
ssm2602 Audio Codec 0.1<6>asoc: SSM2602 <-> bf5xx-i2s mapping ok
lsmod gives me:
Module Size Used by
snd_ssm2602 1292 0
snd_soc_bf5xx_i2s 2600 1 snd_ssm2602
snd_bf5xx_i2s 3604 1 snd_ssm2602
snd_soc_bf5xx_sport 13084 3 snd_ssm2602,snd_soc_bf5xx_i2s,snd_bf5xx_i2s
Running aplay -l gives me
aplay: device_list:222: no soundcards found
When I build the modules into the kernel ssm2602 appears it the ALSA device list at boot time, but aplay gives the same result. When I also compile oss emulation into the kernel, then I can hear noise by using cat /dev/urandom > /dev/dsp, but aplay doesn't find any device.
Can anyone give me a hint, what might be wrong?
QuoteReplyEditDelete
2009-06-18 11:42:34 Re: Alsa problem in trunk (before 2.6.30 update) on bf527
Mike Frysinger (UNITED STATES)
Message: 75982
if you dont want to upgrade to 2.6.30, then you should switch to the 2009R1 branch
what device nodes exactly do you have in /dev/ ? run like:
ls -R /dev/
QuoteReplyEditDelete
2009-06-18 11:52:58 Re: Alsa problem in trunk (before 2.6.30 update) on bf527
Stefan Wanja (GERMANY)
Message: 75983
Yeah, maybe I should switch to 2009R1 but I think I might need the 3.1.2 version of linphone.
Anyway, when I do ls -R /dev/ I get the following list:
ls -R /dev/
/dev/:
bfin-otp network_latency ram13 root
console network_throughput ram14 rtc0
controlC0 null ram15 stderr
cpu_dma_latency pcmC0D0c ram2 stdin
fd pcmC0D0p ram3 stdout
full ptmx ram4 timer
kmsg pts ram5 tty
log ram0 ram6 ttyBF0
mem ram1 ram7 urandom
mtdblock0 ram10 ram8 video0
mtdblock1 ram11 ram9 zero
mtdblock2 ram12 random
/dev/pts
Looks like pcmXXXXX is an alsa pcm, but aplay tells me that there is no soundcard.
Thanks for your reply!
QuoteReplyEditDelete
2009-06-18 11:58:24 Re: Alsa problem in trunk (before 2.6.30 update) on bf527
Stefan Wanja (GERMANY)
Message: 75985
another problem here seems to be mdev. I complains with:
mdev: bad line 10
when I remove the /etc/mdev.conf it doesn't fail. But only those device files as in the last post can be seen. Are those problems connected?
This is my /etc/mdev.conf
# see user/busybox/busybox-*/docs/mdev.txt
event.* 0:0 0664 >input/
input.* 0:0 0664 >input/
mice.* 0:0 0664 >input/
mouse.* 0:0 0664 >input/
controlC[0-9] 0:0 0664 >snd/
pcmC[0-9]D[0-9][cp] 0:0 0664 >snd/
timer 0:0 0664 >snd/
seq 0:0 0664 >snd/
Any ideas?
QuoteReplyEditDelete
2009-06-18 12:16:26 Re: Alsa problem in trunk (before 2.6.30 update) on bf527
Mike Frysinger (UNITED STATES)
Message: 75988
mdev creates the device nodes and your /dev output shows that you're missing the alsa ones (/dev/snd/)
check your busybox/mdev settings to make sure you didnt disable necessary options. the default BF527-EZKIT should work fine with both.
QuoteReplyEditDelete
2009-06-22 09:00:54 Re: Alsa problem in trunk (before 2.6.30 update) on bf527
Stefan Wanja (GERMANY)
Message: 76127
Ok that was it. Busybox was not configured correctly. Now the sound works again. Thank you!