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

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?

Does it really suggest you should run rpi-update?

Before trying to install the player applications you should run "sudo apt-get update".

That command doesn't actually update any applications, it just makes sure the list of packages from all repositories is up to date.

I.e. it makes sure a subsequent "sudo apt-get install xxx" will find the xxx application out there on the Internet.

rpi-update is another beast altogether. It updates everything to the very latest bleeding-edge version, including firmware and kernel. It should be used with caution, because it may install experimental code.

--

Ragnar

Thank you Ragnar! The original image seemed to work, but the network was unstable and broke down before I could install anything. I also did not understand why they wasted so much place using NOOBS as a base for it, and unzipping directly to dd did not work because of a problem with archive. If they have not done so already, I do not understand why they have not asked you whether they could offer your version to download instead or at least include a link to it to make it easier to find.

I also find it quite ridiculous that the driver is still not officially included in the kernel, but I understand that the person originally working on that is not any more and the new guy probably needs some time to get into it [https://github.com/raspberrypi/linux/pull/705#issuecomment-61638834].

Thank you Ragnar! The original image seemed to work, but the network was unstable and broke down before I could install anything. I also did not understand why they wasted so much place using NOOBS as a base for it, and unzipping directly to dd did not work because of a problem with archive. If they have not done so already, I do not understand why they have not asked you whether they could offer your version to download instead or at least include a link to it to make it easier to find.

I also find it quite ridiculous that the driver is still not officially included in the kernel, but I understand that the person originally working on that is not any more and the new guy probably needs some time to get into it [https://github.com/raspberrypi/linux/pull/705#issuecomment-61638834].

I don't find it ridiculous, I find it appalling that this company could sell what appears to be an outstanding product hardware-wise, but totally skimp on the software/drivers side.  One software engineer is supporting this product now???  Seriously??  Did they sell so few they're just trying to contain costs?

What faith would I have in any other product sold by this company, honestly.

Feel free to advise in detail on how they can support it, assume perhaps that they don't know how to and, especially in the vast world of Linux with contradicting and ever increasing changes, can't find reference to the best practice guidelines to follow through with it, how to advise them on it?     

Seriously?

You don't see issue with them developing an add-on card for the Pi, marketing & selling it and then expecting the community to support it?  It's not an issue of us wanting to use some obscure hacked Linux release on our Pi's and then demanding their drivers to work.  We're talking about the official Raspian release.

How long can we expect Ragnar to continue helping us?  The poor guy is doing this for free and at some point he's going to have enough of it especially when folks continue to squawk at him that something broke with the latest Raspian release.

Wayne Westlake wrote:

 

Seriously?

 

I think you've side-stepped what I'm asking.

You don't see issue with them developing an add-on card for the Pi, marketing & selling it and then expecting the community to support it?  It's not an issue of us wanting to use some obscure hacked Linux release on our Pi's and then demanding their drivers to work.  We're talking about the official Raspian release.

Raspian is, amusingly a hacked Linux release considering it doesn't follow the Linux naming conventions for arm package/distro releases, apparently. Raspian isn't run by the Pi Foundation afaik it's run by independents with collaboration with the Pi Foundation.

Linux, frankly, is entirely expecting the community to support it - that's why Raspian is sat partly on github and Wolfson tried to make pull requests but had the Community challenge them (but no-one necessarily help). Which just shows it's easy to criticise.

I would have expected more expertise within Wolfson to be able to handle handle this following expected Linux procedures, having a repository at the very least rather than distributing a Linux image with a 'hacked kernel' and then that having to be re-packaged within an archive by the likes of the kind Ragnar (whom we don't know if he works for some company anyway) and such.

However as anyone knew to Linux finds out, getting appropriate direction to set all of this up isn't exactly easy, explained or straightforward and it can be even harder for companies whom mainly deal in hardware to try to breach into software support and this is evidence of that and the result of it the scapegoat of using Linux and 'having the community support it' and unless it gets easier for people in those companies to find the information on the best practices to support their products they're going to rely on other people - and with Linux that is the community.

So while I agree with what you're saying and I've said it myself, the ethos of Linux doesn't help itself and in instances like this is where it clashes. Please feel free to constructively link to any resources which would help - which was the point of my line of questioning in my previous reply; because assuming that everyone, especially in established businesses, know where to look is far-fetched and results in getting third party companies whom charge for Linux support to gain traction.

Hi Christopher!

IMHO the most important thing would be that Wolfson/Cirrus actually started to actively support this card:

Have someone with enough technical knowledge, plus ideally one of the devs, here on the forum to answer questions. Enable issue reporting on the github repository so people can submit bug reports. Setup a support email address where people can write to if they have issues. Communicate to the users which support channel is preferred for which kind of issue. Any or all of these options would really help a lot.

During the last 9-10 months people asked quite a lot of valid questions and reported bugs, both here on the forum and in the github comments of PR:705. Unfortunately most of these questions remained unanswered - which isn't the best way to establish confidence in the product and support...

C'mon, I'm sure you can do better, and once you get the software and support going you'll have a really nice product!

so long,

Hias

Yes, unfortunately this is the feedback I've pushed internally as well. I haven't had any clear answers as to what/where/why the hold-up on this is and the Github PR you cite is the only evidence I've seen so far.