0

jessie changes for dac+

Greenejeremya

January 18, 2016 02:07

Completed

Follow

I am ready to send the dac+ back; even if I could get it to work.

The installation directions are not up to date for jessie. The comments on the forum are conflicting:
  dtoverlay=hifiberry-dacplus
or is it:
  dtoverlay+=hifiberry

neither work. aplay -l shows no device. 

And what about blacklists? Directions say to remove them. There aren't any.
And removing snd_bcm2835 from /etc/modules. Does not exist.
Or... do you remove that from config.txt????

I mean, to expect a clean install is insultingly annoying. Jesie has been out for months. How can the web site install directions not be up to date?

I made a clean install with many apps prior to getting to your website that has the full image. I am not going back, although the product probably will.

 

• Facebook
• Twitter
• LinkedIn

9 comments

• 0
  
  HiFiBerry team January 18, 2016 05:46

  Hi,

  there are so many different version of Raspbian out, and all are a bit different. Therefore there won't be a guide that fits all installation. To make it easy for HiFiBerry users, we have created the HiFiBerry installer:

  http://support.hifiberry.com/hc/en-us/articles/205389831-HiFiBerry-installer

  If there are no blacklists, you do not have to remove them. The overlay is dtoverlay=hifiberry-dacplus as written in the documentation. Where did you read the line dtoverlay+=hifiberry?

  Best regards
  Daniel

• 0
  
  Greenejeremya January 18, 2016 14:32

  I spent a day+ getting an install to the point I wanted, minus the dac+ since I didn't have it yet. Then I have it, go to your web site and spend another few hours trying to get your product to work. 

  I really can't buy the many releases issues. Can't you at least:
    google raspian download, which is what a huge number of people would do and make sure your instructions work for that?

  But even then, some strong note on your web site would be a wise business decision. Or a note in your instructions that indicate how unlikely they are to work.

  Anyway, I may try a different product; can I get instructions for sending this back for  a refund?

  Oh, and you can search for Stuart Maclean's response last Oct 26 about the += device tree comment.
  Or you can search your forum for "jessie" and look at what was the 1st post prior to mine.

   

• 0
  
  HiFiBerry team January 18, 2016 14:39

  Hi,

  we know of a lot of people that used our instructions and had no problems configuring the board. I don't know what is the problem in your installation. For beginners we created the installer to make it as easy as possible to install everything. I will create a ticket for your return.

  Best regards
  Daniel

• 0
  
  John Hagensieker January 18, 2016 16:46

  I just installed the latest Jessie, added   dtoverlay=hifiberry-dacplus to /boot/config.txt and it works.

   

  Some thoughts ....... are you root or user pi?  Did you create another user?  That user needs to be in the audio group. 

  Did you check alsa?

  sudo apt-get install alsa alsa-utils

   

  How about trying sudo aplay -l

  What pi are you using? 

  Also make sure you are getting Raspian from raspberrypi.org or the test image here.

  Is it possible your volume is all the way down?

  alsamixer

  Edited by John Hagensieker January 18, 2016 16:48
• 0
  
  Greenejeremya January 19, 2016 01:48

  Actually, I'm definitely not a beginner with RP or debian/ubuntu in general. And I am using raspberrypi,org releases, thinking that would be the most likely for vendors to clearly document.

  As it turns out, it was that I made a different account, but even though I did add it to the audio group, I did that AFTER, I had looked at the forum and followed a post by gis on January 08, 2016 18:35

  5. Modify the last rows of /boot/config.txt as follows:
  ##comment the following line
  #dtparam=audio=on
  ##add the following line
  dtoverlay=hifiberry-dacplus
  

  Which I found out was bad advice, at least for raspberrypi.org's latest release.

  That plus the other post about dtoverlay+= caused extra time, 

  In the end, this is a pretty simple thing to document:

  • One line in config.txt
  • Make sure your account is in the audio group

  I find it hard to believe that adding that to the website for the latest raspberrypi.org release wouldn't make for happier customers.

  And if you make comments in the forum, why wouldn't they go back in the installation directions on the website??

   

   

• 0
  
  John Hagensieker January 19, 2016 11:52

  So did you get it working?  My understanding of the directions was pretty much anything later than 3.18 kernel and you add the dtoverlay statement to config.txt

  I literally have maybe 10 Pi's off all variants, a HiFiBerry DAC, Digi, 2 DAC+ and now the AMP+.  I've never ever had a problem with them on Volumio, Rune, Arch, Raspbian, etc.

  Hope you got it working and hope you keep it.  I love hacking away on mine and now I'm figuring out how to work around it and add rotary encoders and LCD's and such.  Even if you discount it makes music it helped me learn those other skills out of necessity.

• 1
  
  Greenejeremya January 19, 2016 13:15

  Yes, it is working. I had followed the post that added the dtoverlay line (correct) but also commented out the dtparam=audio=on line, which is incorrect. That, along with creating a new account and not initially having it in the audio group and trying other poster's incorrect solutions, caused time consuming problems.

  Sorry for the frustration, but while I am used to spending lots of time getting a full ubuntu system working (and quite frankly finding more accurate forum comments regarding it), I was spoiled with wheezy -- really had no problems (had been using the internal RP dac -- had that up in an hour). Switching to jessie was a pain (systemd -- still have issues there) and then ran into the dac+ issues that I hadn't expected (being one of the two things I paid for, and almost as much as the RP!).

   

• 1
  
  John Hagensieker January 19, 2016 15:15

  I feel your pain.  Wheezy and Jesse are two different animals.  I had trouble getting Logitechmediaserver running on Jesse. It requires a patch that forever ties it to that version of Perl (unless you have a Pi 2, how weird is that).  I wanted to ditch Jesse and use Wheezy.  Much more stable platform for R Pi right now in my opinion.

• 1
  
  John Hagensieker January 19, 2016 15:19

  Systemd is not so bad once you get the hang of it.  I've been using Arch for some time though.  Whilst fumbling around in Jesse sometimes I ask myself "Why not just use Arch?"