Oh yes, I am eternally greatful to the people who work on Volumio and the person who integrated the Wolfson kernel so it would work at all. I evaluated several music players and Volumio was by far the most polished out of the box. I don’t mind DIY but I’m also a fan if KISS where possible
I didn’t have any issues with clicking - that i could hear - but I am mostly listening at a low volume level right now. I was actually looking for something like the HiFiBerry but the Wolfson was in stock at a local place and I am interested in the more advanced features for other projects. I think if it had better integration with raspibian and some Volumio integration it would still be overkill but would at least be plug and play. If I had any real php skills I’d write a Wolfson settings page for Volumio…
I originally used an old cell phone charger for the power supply and found that I had to reboot if I went into Volumio a day later. I changed to an Apple ipad charge with 5.2 volts and 2.4 amps and that problem went away.
Last night I messed with the audio buffer and each time I did that the song would output by choosing a lower resampling rate - I got to 16 bit 92khz and each time I doubled the buffer the song would play a bit longer before sputtering. So then I had the brilliant idea of going way to to 92000 on the buffer (from approx 16000).
Yeah - had to reflash after that.
Tonight I’m going to bring in an old reciever that I found in the garage with spdif into the back room and see if I can stream the songs any better if I use ethernet to connect to the pi rather than usb.
Hello all,
I’ve no luck with the volumio 1.5.1 release and 3.12.29 wolfson kernel (github.com/manish-wolfsonmicro/linux);
all the system is instable and is impossible play anything.
I’ve resolved some stupid issues with the latest image and modified some settings as mentioned here: reddit.com/r/raspberry_pi/co … etup_guide
I’ve created a wiki page with infos and links for this new version:
first: thanks to michelangelo for his great work. a great improvement from 1.4 to 1.5 in soundquality!! and thanks to m3m3nto for
implementation the wolfson-card!
but in moment i have some problems with 1.5:
less stability in network. if i change too fast songs with bubbleupnp i loose the connection and volumio is hanging up. this was no problem in 1.4
some wav files could not be played, others could. i don´t know why.
after every reboot i first have to run the wolfson-scripts. first the Reset sricpt then the SPDIF_playback.sh (i only use the SPDIF output) Only SPDIF
script produces only crackle. System does not remember the last session output. this was no problem in 1.4.
Yes, I have the same sense of the 1.5 version being less stable and predictable than the 1.4 version. Not a criticism, just an observation. As you say, the card settings don’t seem to survive a reboot, and you have to run the Reset script and the SPDIF_playback script to get output to SPDIF working (the 1.4 version doesn’t need the Reset script to be run, only the SPDIF_playback script).
I’ve gone back to using the 1.4 version, which works fine for me.
I suspect Michelangelo is waiting until the Wolfson drivers are included in the main Raspian distribution. However, last time I looked the work on that seemed to have stalled somewhat, with not much feedback/input from Wolfson.
with your .img i have this error as soon has i do ‘apt-get update’
[ 417.760456] EXT4-fs error (device mmcblk0p3): ext4_validate_block_bitmap:368: comm apt-get: bg 13: block 425984: invalid block bitmap
[ 417.782692] Aborting journal on device mmcblk0p3-8.
[ 417.798967] EXT4-fs (mmcblk0p3): Remounting filesystem read-only
[ 417.809206] EXT4-fs error (device mmcblk0p3): ext4_validate_block_bitmap:368: comm apt-get: bg 14: block 458754: invalid block bitmap
and it does not boot at all after a reboot. ( it doesn’t answer to ping)
Im triying to setup and get it work Volumio on to rpi B+ and the new Cirrus Audio Card + element14.com/community/comm … wolfson_pi, that seems is the improved new version of wolfosn audio card for rpi B, but at today with no luck at all.
I tried the images from that post about Volumio 1.5 and Volumio 1.4, but its not working seems because that kernel used at least dont support new ethernet card for rpi B+ and others hardware changes of rpi B+.
I tried compiling kernel form offical github repo github.com/CirrusLogic/rpi-linu … g-the-code, but several errors raised each time i tried and seems its not working too this repo, and i dont know exactly how to integrate that compiled kernel (if some day i can make that compilation) with volumio.
Can anyone help me to make my rpi B+ and Cirrus Audio Card working with Volumio ?
Yup, I’m getting the same with the 1.5 Wolfson image. When it reboots, I have a keyboard and display connected to the Pi, and can see that it stops booting due to the errors and wants to check the disk, but needs the root password. At one stage I managed to get it to run fsck, which went through a zillion prompts for Yes/No, until I discovered that you could use fsck -y to answer yes to all of the prompts!
Seems to be working OK now, but the volume control in the web interface doesn’t affect the volume level coming out of the Wolfson line-out
(I’m using the SPDIF input, and playing it to the line-out – I presume that I should be able to adjust the volume coming out of the line-out using the web volume control?)
I was following the instructions provided here: reddit.com/r/raspberry_pi/co … tup_guide/
Oddly, the PI boots up without making any changes to the config.txt file, but when I make the changes as instructed, it doesn’t boot.
The message I posted on reddit is below.
I tried the image in your link and it looks exactly the same as the one I already tried. What I did do however is forget to update the config.txt file. The PI booted but then had an I2S sync error and stopped.
The current config.txt file is the following. kernel=kernel_wolfson.img gpu_mem=16 hdmi_drive=2 arm_freq=950 core_freq=250 sdram_freq=450 over_voltage=6
I then updated the kernel line in the file and it doesn’t boot. There is clearly a problem there. Please bear with me as I am a bit of NOOB but I would really like to get this working. Thanks again for the help.
Forgive me as I am new to all this, but is there something I am missing with the kernel file? Thanks much in advance for the help. I am using a Model B and the original Wolfson card.
Also of note, there is an interesting discussion going on at the link below in case folks haven’t seen it.
Let me thank you for your great work on pairing Wolfson with Volumio. I was able to play good sound using your Volumio 1.5 image.
There is still one glitch with your provided image: some areas on the image are corrupted so after touching these areas affected files are deleted. Here is a list of affected files:
Entry 'pkgcache.bin' in /var/cache/apt (17659) has deleted/unused inode 16341. Clear? yes
Entry 'srcpkgcache.bin' in /var/cache/apt (17659) has deleted/unused inode 15910. Clear? yes
Entry 'status' in /var/lib/dpkg (17823) has deleted/unused inode 18469. Clear? yes
Entry 'available' in /var/lib/dpkg (17823) has deleted/unused inode 18470. Clear? yes
Entry 'status-old' in /var/lib/dpkg (17823) has deleted/unused inode 18471. Clear? yes
Entry 'htop' in /usr/share/doc (20) has deleted/unused inode 103174. Clear? yes
Entry 'htop_1.0.3-1_armhf.deb' in /var/cache/apt/archives (15886) has deleted/unused inode 18453. Clear? yes
Entry 'htop' in /usr/bin (3977) has deleted/unused inode 37. Clear? yes
Entry 'htop.md5sums' in /var/lib/dpkg/info (17832) has an incorrect filetype (was 1, should be 5).
Entry 'htop.postinst' in /var/lib/dpkg/info (17832) has deleted/unused inode 103170. Clear? yes
Entry 'htop.postrm' in /var/lib/dpkg/info (17832) has deleted/unused inode 103171. Clear? yes
As you can see the most important part is that dpkg database is affected and I cannot install any additional software with apt-get. Would it be possible to get either those affected files from your Volumio 1.5 image or corrected image itself?
It worked for me too.
The kernel with volumio 1.55.
One thing that I’d love to learn is how to limit the max volume to a preset volume …
in my case I want to avoid clipping on the wolfson card ( that is around volume 81 ) and avoid clipping on my
amp that is around volume 70.
I am using Raspberry B and Wolfson DAC. I can hear slight pops when music is started. Is it normal and other users hear this as well? I tried all possible distro’s that support Wolfson (element14 provided distro, Volumio, Runeaudio, OpenElec), the result is the same.
I am out of ideas, so any thought is much appreciated.
I use the Rpi B and wolfson DAC with no such pops. I am using the 1.4 version of the software that was compiled for use with the woolfson dac. I had all kinds of problems that were all solved through this post.
Short update: I managed to compile new Cirrus Logic 3.18 kernel with Wolfson DAC support:
-> Good news: no pops when music starts!
-> Good news: I have 3.18 kernel which is compatible with B, B+ and B2
-> Bad news: rare pops are present when you stop playing
After tracking these pops these are my findings so far:
-> It is MPD related as I get them only from MPD (bad news for Volumio and Runeaudio)
-> It is codec related as pops for MP3 are more noticeable and happen more frequently
With the following MPD configuration pops happen rarely so they are tolerable, however I keep seeking for perfection
