Hello,

 

I have just built an image with the default parameters of the Lime A20 board. It seems that the system does not detect any sound card.

 

aplay -l

aplay: device_list:268: no soundcards found...

 

uname -a

Linux lime 4.13.6-sunxi

 

lsmod

Module Size Used by

cfg80211 376832 0

rfkill 20480 1 cfg80211

sun4i_gpadc_iio 16384 0

evdev 20480 1

at24 16384 0

sun4i_ts 16384 0

sun4i_gpadc 16384 0

nvmem_sunxi_sid 16384 0

sun4i_ss 24576 0

uio_pdrv_genirq 16384 0

uio 16384 1 uio_pdrv_genirq

 

As you can see above, there is no module related to sound.

 

If i use the same SD card with this image built in a Cubieboard2, i get the same error.

 

Any advice would be greatly appreciated,

 

Thanks in advance.

 

 

If a board does not have an audio connector that is almost always disabled in board DT by default.

I am not sure if audio is possible to enable with overlay, but check it:
https://docs.armbian.com/User-Guide_Allwinner_overlays/

Thank you Igor, I will check this information about Device Tree overlays

The solution was found some time ago 

 

forum.armbian.com/index.php?/topic/4224-analog-audio-on-lime2-with-stable-kernel-version-49/

Hello Igor, 

 

According to the previous link, i add the following code segment to the dts :

&codec { status = "okay"; };

 

The dts file is located in: 

build/cache/sources/linux-mainline/linux-4.13.y/arch/arm/boot/dts/sun7i-a20-olinuxino-lime.dts

 

After that, i run compile.sh , but if i check the dts file again, i can't see the code segment that i added. 

 

So, how can i modify the device tree of the lime board or any other board?  (mainline kernel)

 

Thank you very much in advance

51 minutes ago, OpenglMan said:

After that, i run compile.sh , but if i check the dts file again, i can't see the code segment that i added. 

 

A source is checked out by default. You need to switch to "edit" mode. CREATE_PATCHES=yes ...  

https://docs.armbian.com/Developer-Guide_Build-Options/

 

This will prompt you to make changes to the source code. Then you make them. After you are done, return and press ENTER. This will also create a patch in output/patches ... which you can move later to appropriate userpatches directory or submit upstream.

Thank you very much, the whole process worked correctly