Wolfson modified Noobs raspbian zipped img  Cannot unzip new download

Please make the md5 checksum for this file available.

Thank you

Patrick

I have kept my original download, but I have downloaded the zip file again to compare them.

I'm running WinXP with Cygwin.

My old download from Feb 26 and today's are identical.

$ ls -ltr *wolfson*zip
-rwx------+ 1 ragnar Ingen 4713117059 Feb 26 12:16 wolfson_3.10_master.zip
-rwx------+ 1 ragnar Ingen 4713117059 Mar 17 21:12 new_wolfson_3.10_master.zip
$ md5sum wolfson_3.10_master.zip new_wolfson_3.10_master.zip
72d091a9b43e47a5b7b85432ec15611c *wolfson_3.10_master.zip
72d091a9b43e47a5b7b85432ec15611c *new_wolfson_3.10_master.zip

WinZip complains - "Archive is greater than 4 gigabytes."

WinRAR complains - "! ... wolfson_3.10_master.zip: Either multipart or corrupt ZIP archive"

Command line unzip complains - "warning [wolfson_3.10_master.zip]: 418149653 extra bytes at beginning or within zipfile...error [wolfson_3.10_master.zip]: start of central directory not found;...

7-zip works, it extracts the image OK.

There are Linux and OSX versions of 7-zip available at http://www.7-zip.org/download.html

--

Ragnar

./Playback_to_Headset.sh

bash: ./Playback_to_Headset.sh: No such file or directory

and when I typed "fuser -v /dev/snd/*" into terminal I get nothing

The use case scripts reside in the folder use_case_scripts.

Either

cd ~/use_case_scripts
./Playback_to_Headset.sh

or

~/use_case_scripts/Playback_to_Headset.sh

--

Ragnar

1. cd ~/use_case_scripts 
2. ./Playback_to_Headset.sh  

all I got was this as a result:

amixer: Cannot find the given element from control hw:0 (but the same thing for 11 lines)

It looks like the RPi has lost the connection to the Wolfson card.

Does any of the other scripts run without error messages?

Post the  output of these commands:

aplay -l

aplay -L

--

Ragnar

яков х wrote:

 

1. cd ~/use_case_scripts
2. ./Playback_to_Headset.sh 

 

all I got was this as a result:

 

amixer: Cannot find the given element from control hw:0 (but the same thing for 11 lines)

There was a thread about the same error message (on running './Playback_to_Headset.sh')  back in March

Problem getting Wolfson Audio Card working: "amixer: Cannot find the given element from control hw:0"

Yep, and that turned out to be a broken Wolfson card.

--

Ragnar

Oh how odd. It was working fine before with the official wolfson image. I just couldn't expand the filesystem to the entire 16gb card. I will have to retry the official image when I have time later... ugh I hate wearing down flash storage.

Although I must add something regarding the contact of the p5 connections on the wolfson card. This seems challenging considering there is soldering on the audio card above the blue RPI 3.5 mm audio jack that protrudes, preventing the audio card to fit easily. Could this be the culprit?

On the other hand I saw that someone performed an rpi-update, like myself. This could be the issue.

Ragnar Jensen wrote:

 

Yep, and that turned out to be a broken Wolfson card.

--

Ragnar

Well, one guy reckoned it was a faulty card, another said the problem occurred after doing an 'rpi-update'

Re: Problem getting Wolfson Audio Card working: "amixer: Cannot find the given element from control hw:0"

I don't see how one would not perform an rpi-update in order to install the required software to playback audio files. In other words, if I don't perform an update and try to install VLC, I get a bunch of error messages suggesting I run an rpi-update.

I considered the possibility that between the time I flashed the Wolfson image and yours, my card broke. I tried the original again and everything works fine. Which is great because I know my card is not broken. But I still can't get the one from this forum to work. I guess I'll wait for default raspbian driver support?

I considered the possibility that between the time I flashed the Wolfson image and yours, my card broke. I tried the original again and everything works fine. Which is great because I know my card is not broken. But I still can't get the one from this forum to work. I guess I'll wait for default raspbian driver support?