Cirrus Logic Audio Card working on the Raspberry Pi 2

For good measure, I've put together a tar archive of the 3.18 kernels with Cirrus Logic drivers, that can be installed on top of an existing Raspbian 3.18 installation.

Download the archive file kernel_3_18_9_W_CL.tgz from here: https://drive.google.com/file/d/0BzIaxMH3N5O1S1FfSGpqYjEwaVk/view?usp=sharing

To install:
Become root: sudo -s
Go to root directory: cd /
Untar the archive: tar xvzf /path/to/where/you/saved/kernel_3_18_9_W_CL.tgz
Add these lines

dtparam=spi=on
dtparam=i2c_arm=on
dtoverlay=rpi-cirrus-wm5102-overlay

to the file /boot/config.txt

On a RPi2B, also add

kernel=kernel7_CL.img

or, on all others, add

kernel=kernel_CL.img

to /boot/config.txt

Put these lines into /etc/modprobe.d/raspi-blacklist.conf  (create the file if it doesn't exist.)

softdep arizona-spi pre: arizona-ldo1
softdep spi-bcm2708 pre: fixed

Reboot.

If it doesn't work, you can revert to your original kernel by just removing the "kernel=kernel_CL.img" line from /boot/config.txt

--

Ragnar

I cant put lines into /etc/modprobe.d/raspi-blacklist.conf 

When I try to put lines into this directory I open a (only read) and I cant save it. Or it adds a textfile extesion

Who can give me a guideline to add lines to this directory?

And can you add to the  /boot/ config.text in the same way?l

Hugo50

I cant put lines into /etc/modprobe.d/raspi-blacklist.conf 

When I try to put lines into this directory I open a (only read) and I cant save it. Or it adds a textfile extesion

Who can give me a guideline to add lines to this directory?

And can you add to the  /boot/ config.text in the same way?l

Hugo50

Hugo

It sounds as if you do not have write permission of these files.

Are you new to working with Linux?  If so, let me help.  If not, then ignore me.

If I run the long version of the file list command on the /etc/modprobe.d directory I get ...

pi@raspberrypi ~ $ ls -l /etc/modprobe.d

total 24

-rw-r--r-- 1 root root  229 May  8  2013 alsa-base-blacklist.conf

-rw-r--r-- 1 root root 1186 May  8  2013 alsa-base.conf

-rw-r--r-- 1 root root  456 Apr 29  2013 fbdev-blacklist.conf

-rw-r--r-- 1 root root   65 Feb 15  2015 ipv6.conf

-rw-r--r-- 1 root root  357 Mar 27  2015 oss-compat.conf

-rw-r--r-- 1 root root   70 Mar 27  2015 raspi-blacklist.conf

pi@raspberrypi ~ $

This shows that these files are owned by the user 'root'  (The second 'root' tells you that they are also in group root.)

The -rw-r--r-- tells you the permissions on these files.  Ignore the first dash for now.  The remaining nine characters form three groups of three.  Each group is Read, Write  , eXecute.

The groups are Owner, group, others in that order.

So the pattern on all these files tells us that the owner, that is root, has read and write permission on the files, but not execute permission.  (rw-)

Both the group and others only have read permission (r--).

In order to change these files you therefore need to be user root.  You can use the 'su' command to change which user you are - providing that you know root's password, or you can use the sudo command to temporally change who you are while running the command.

So to edit the raspi-blacklist.conf file you could run the command :-

sudo nano /etc/modprobe.d/raspi-blacklist.conf

OK?

David