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

Hi

Thanks a lot~!

I'll try it.

Yesterday I use runeaudio with wolfson kernel is work well.

Now I want to find out,what the difference between runeaudio and volumio?

Whitch one sound quality is the best?

Not sure about RuneAudio. I tried it when I was using a USB Dac (before getting the Wolfson card), but it was early in its development, and didn't work well. Nice graphics, but they don't seem to have done any development work for 3 months, looking at the date of the download files. They designed the graphic interface that Volumio uses as well, but I wonder if Michelangelo, the current developer on Volumio, is the one who did most of the development work on the audio side of things?

Thanks for that. Unfortunately, the macports unzip didn't work either:

$ /opt/local/bin/unzip -?

UnZip 6.00 of 20 April 2009, by Info-ZIP.  Maintained by C. Spieler.  Send

bug reports using http://www.info-zip.org/zip-bug.html; see README for details.

...

$ /opt/local/bin/unzip -l wolfson_3.10_master.zip

Archive:  wolfson_3.10_master.zip

warning [wolfson_3.10_master.zip]:  418149653 extra bytes at beginning or within zipfile

  (attempting to process anyway)

error [wolfson_3.10_master.zip]:  start of central directory not found;

  zipfile corrupt.

  (please check that you have transferred or created the zipfile in the

  appropriate BINARY mode and that you have compiled UnZip properly)

$ /usr/bin/unzip -l wolfson_3.10_master.zip

Archive:  wolfson_3.10_master.zip

warning [wolfson_3.10_master.zip]:  418149653 extra bytes at beginning or within zipfile

  (attempting to process anyway)

error [wolfson_3.10_master.zip]:  start of central directory not found;

  zipfile corrupt.

  (please check that you have transferred or created the zipfile in the

  appropriate BINARY mode and that you have compiled UnZip properly)

$

However, I was able to install ez7z and THAT was able to deal with the zip64 extensions.

Thanks again for your suggestions.

Hi Ragnar!

I just began to learn about raspberry pi. Now I can record from shell instruction using arecord, but I want record by using C code, can you tell me how to do that ?

Thanks!

Well, that is a big and complex  subject...

I would suggest you start out by checking out these links:

A tutorial on using the ALSA Audio API

Study the source code of arecord/aplay and the other ALSA utilities. https://gitorious.org/alsa/alsa-utils

And, of course the API reference: ALSA project - the C library reference: Index Preamble and License

--

Ragnar

Thanks a lot!

You are so cool!

Andy,

     It has been a couple more months, any progress?  For me the board is more or less useless if it can not be used with the standard up to date kernel.  This just run a froozen kernel is a trap I cannot afford to fall into again.  I appreciate the work Ragnar has done here and he is to be commended, but for this to be usable their needs to be a deb with the drivers for the current release available.

Hi Andy (or other Colleagues at E14)

Any news on the Wolfson Drivers deb package? I fully endorse Richard's post of 25th May and cannot understand why there hasn't even been a response to it during the three weeks since his posting. Surely the deb packages should have arrived shortly after your posting on March 24, not that we should be waiting for a further 3 months. Is it even still being worked on by Wolfson/E14? please advise us of the current expected timing for these to be added to the Raspbian repository?

Thanks & regards

Paul

I tried the Wolfson provided Raspian image with success. The audio output was excellent. But I couldn't expand the file system from 6GB to 16GB, which was disappointing.

I also tried your patched image but didn't get any sound. For example, VLC player claims the audio output for wolfson is already occupied and busy. (I can give verbatim error messages if needed) And I changed the VLC output settings too. And Music Player won't give me any audio either. I understand a reboot is required for the drivers to start working. Is this where I could've gone wrong? Because I updated and installed apps before rebooting. Any advice? Thanks.

You say you 'updated'. If you mean you updated Raspian that might not be a good idea, as the Wolfson drivers are not yet included in the standard Raspian distribution, so updating the OS might produce unexpected results.

You don't say what output you are trying to use (line-out, SPDIF etc). It might be an idea to connect to the Pi from your main computer via SSH, and run the 'alsamixer' command (if you are running 'headless'). Maybe your outputs are currently 'muted'?

You say you 'updated'. If you mean you updated Raspian that might not be a good idea, as the Wolfson drivers are not yet included in the standard Raspian distribution, so updating the OS might produce unexpected results.

You don't say what output you are trying to use (line-out, SPDIF etc). It might be an idea to connect to the Pi from your main computer via SSH, and run the 'alsamixer' command (if you are running 'headless'). Maybe your outputs are currently 'muted'?