HifiBerry DAC+ Pro [solved for Raspberry B+]

°pdi°

Raspberry B+
RuneAudio: 0.3-beta (3.12.26-1-ARCH)

Hi,

HifiBerry DAC+ Pro: Kernel version should be at least 4.1.10

How to update my RuneAudio?

Best Regards

Klaus
http://support.hifiberry.com/hc/en-us/community/posts/201496242-DAC-Pro-clocks?page=1#comments

[solution: #295416 ]

hondagx35

Hi Klaus,

you can try this:

pacman -Sy --force raspberrypi-firmware-bootloader linux-raspberrypi

But be warned, this may brake your installation.
I did this on the RP2 but not on a RP B+.

Frank

°pdi°

Hi Frank,

hondagx35 wroteBut be warned, this may brake your installation.

O.k., no problem...

I tried it, and get this message after installation:

This kernel provides updated config.txt and cmdline.txt files.
         Check for pacnew files in /boot and merge or replace the existing files
         with the new versions.

Yes, there is a new file, named "config.txt.pacnew" in /boot. And the new folder "overscans".

But there is no new kernel.img in /boot. And no new cmdline.txt...

I can't understand it.

Also reinstalling without succes

Packages (2): linux-raspberrypi-4.1.12-1
              raspberrypi-firmware-bootloader-20151028-1
Total Installed Size:   33.61 MiB
Net Upgrade Size:       0.00 MiB
:: Proceed with installation? [Y/n] y
(2/2) checking keys in keyring                     [######################] 100%
(2/2) checking package integrity                   [######################] 100%
(2/2) loading package files                        [######################] 100%
(2/2) checking for file conflicts                  [######################] 100%
(2/2) checking available disk space                [######################] 100%
(1/2) reinstalling raspberrypi-firmware-bootloader [######################] 100%
(2/2) reinstalling linux-raspberrypi               [######################] 100%
>>> Updating module dependencies. Please wait ...

btw.: After reboot RuneAudio is still running... (with kernel 3.12.26-1-ARCH)

Klaus

hondagx35

Hi,

btw.: After reboot RuneAudio is still running... (with kernel 3.12.26-1-ARCH)

Please post the output from:

uname -a

and

ls -la /boot

Frank

°pdi°

uname -a

Linux runeaudio 3.12.26-1-ARCH #1 PREEMPT Fri Aug 8 17:40:14 MDT 2014 armv6l GNU/Linux

ls -la /boot

total 53604
drwxr-xr-x  4 root root   16384 Nov  7 16:50 .
drwxr-xr-x 18 root root    4096 Jan  1  1970 ..
-rwxr-xr-x  1 root root   18693 Feb 23  2014 COPYING.linux
drwxr-xr-x  2 root root    2048 Jul 18  2014 System Volume Information
-rwxr-xr-x  1 root root   10125 Oct 28 02:19 bcm2708-rpi-b-plus.dtb
-rwxr-xr-x  1 root root    9846 Oct 28 02:19 bcm2708-rpi-b.dtb
-rwxr-xr-x  1 root root    9850 Oct 28 02:19 bcm2708-rpi-cm.dtb
-rwxr-xr-x  1 root root   17900 Oct 29 02:31 bootcode.bin
-rwxr-xr-x  1 root root     175 Oct 28 02:19 cmdline.txt
-rwxr-xr-x  1 root root     471 Oct  5  2014 cmdline_linux-arch-rpi_3.12.26-1-ARCH.txt
-rwxr-xr-x  1 root root     239 Apr 30  2014 cmdline_linux-rune-rpi_3.12.13-rt21_wosa.txt
-rwxr-xr-x  1 root root     471 Aug 31  2014 cmdline_linux-rune-rpi_3.12.19-2-ARCH.txt
-rwxr-xr-x  1 root root     617 Nov 26  2013 cmdline_linux-rune-rpi_3.6.11-18-ARCH+.txt
-rwxr-xr-x  1 root root    1837 Nov  7 16:34 config.txt
-rwxr-xr-x  1 root root    4445 Nov  7 16:33 config.txt.pacnew
-rwxr-xr-x  1 root root    1724 Oct  1  2014 config_linux-arch-rpi_3.12.26-1-ARCH.txt
-rwxr-xr-x  1 root root    1673 Jan  7  2013 config_linux-rune-3.6.11-18-ARCH+.txt
-rwxr-xr-x  1 root root     200 Apr 30  2014 config_linux-rune-rpi_3.12.13-rt21_wosa.txt
-rwxr-xr-x  1 root root    6445 Oct 29 02:31 fixup.dat
-rwxr-xr-x  1 root root    2469 Oct 29 02:31 fixup_cd.dat
-rwxr-xr-x  1 root root    9680 Oct 29 02:31 fixup_db.dat
-rwxr-xr-x  1 root root    9176 Sep 22  2014 fixup_x.dat
-rwxr-xr-x  1 root root 5703808 Oct 28 02:19 kernel.img
-rwxr-xr-x  1 root root 9790472 Feb 23  2014 kernel_emergency.img
-rwxr-xr-x  1 root root 9058732 Oct  1  2014 linux-arch-rpi_3.12.26-1-ARCH.img
-rwxr-xr-x  1 root root 3443096 Apr 30  2014 linux-rune-rpi_3.12.13-rt21_wosa.img
-rwxr-xr-x  1 root root 6637772 May 22  2014 linux-rune-rpi_3.12.19-2-ARCH.img
-rwxr-xr-x  1 root root 8325700 Oct 21  2013 linux-rune-rpi_3.6.11-18-ARCH+.img
drwxr-xr-x  2 root root    6144 Nov  7 16:48 overlays
-rwxr-xr-x  1 root root 2729368 Oct 29 02:31 start.elf
-rwxr-xr-x  1 root root  604024 Oct 29 02:31 start_cd.elf
-rwxr-xr-x  1 root root 4855176 Oct 29 02:31 start_db.elf
-rwxr-xr-x  1 root root 3573800 Sep 22  2014 start_x.elf

hondagx35

Hi,

the new kernel is kernel.img

Edit your /boot/config.txt and change the two lines
- kernel=
- cmdline=

to reference kernel.img and cmdline.txt

Frank

°pdi°

Hi,

thats right, "kernel.img" is new, i didn't see...

But now the raspberry did not boot with the changed config.txt . LED is flashing just for a short time an then nothing more.

Klaus

hondagx35

Hi Klaus,

can you connect a monitor to the pi?

Frank

°pdi°

Hi Frank,

maybe my TV. Unfortunately my wife is watching TV right now...

I test it tomorrow and post results here.

Klaus

bknarf

I'm also trying to get the specific drivers for the HifiBerry DAC+ Pro. I have a RPi2.

uname -a

Linux runeaudio 3.18.7-3-ARCH #1 SMP PREEMPT Fri Feb 13 06:23:21 MST 2015 armv7l GNU/Linux

I've executed the update for the kernel and bootloader, with the command hondagx35 provided. The update itself is successful.

:: Proceed with installation? [Y/n] 
:: Retrieving packages ...
 linux-raspberrypi-4.1.12-2-armv7h                           23.4 MiB   716K/s 00:34 [#################################################] 100%
 raspberrypi-firmware-bootloader-20151107-1-any               2.6 MiB   414K/s 00:07 [#################################################] 100%
(2/2) checking keys in keyring                                                       [#################################################] 100%
(2/2) checking package integrity                                                     [#################################################] 100%
(2/2) loading package files                                                          [#################################################] 100%
(2/2) checking for file conflicts                                                    [#################################################] 100%
(2/2) checking available disk space                                                  [#################################################] 100%
(1/2) upgrading raspberrypi-firmware-bootloader                                      [#################################################] 100%
(2/2) upgrading linux-raspberrypi                                                    [#################################################] 100%
warning: /boot/config.txt installed as /boot/config.txt.pacnew
>>> Updating module dependencies. Please wait ...
[root@runeaudio boot]#

ls -al /boot

total 17178
drwxr-xr-x  3 root root   16384 Nov  7 21:30 .
drwxr-xr-x 18 root root    4096 Mar  3  2015 ..
-rwxr-xr-x  1 root root   11113 Nov  7 17:23 bcm2709-rpi-2-b.dtb
-rwxr-xr-x  1 root root   17900 Nov  7 16:55 bootcode.bin
-rwxr-xr-x  1 root root     277 Feb 28  2015 cmdline.txt
-rwxr-xr-x  1 root root    6635 Nov  7 21:09 config.txt
-rwxr-xr-x  1 root root    4449 Nov  7 17:23 config.txt.pacnew
-rwxr-xr-x  1 root root    6445 Nov  7 16:55 fixup.dat
-rwxr-xr-x  1 root root    2469 Nov  7 16:55 fixup_cd.dat
-rwxr-xr-x  1 root root    9680 Nov  7 16:55 fixup_db.dat
-rwxr-xr-x  1 root root    9187 Feb 12  2015 fixup_x.dat
-rwxr-xr-x  1 root root 5685992 Nov  7 17:23 kernel7.img
drwxr-xr-x  2 root root    6144 Nov  7 21:30 overlays
-rwxr-xr-x  1 root root 2730008 Nov  7 16:55 start.elf
-rwxr-xr-x  1 root root  604184 Nov  7 16:55 start_cd.elf
-rwxr-xr-x  1 root root 4855848 Nov  7 16:55 start_db.elf
-rwxr-xr-x  1 root root 3599432 Feb 12  2015 start_x.elf

So there is a new kernel7.img.

After I reboot the Pi, without editing anything, it doesn't boot anymore. Should I edit the config.txt before rebooting? Or is something else going wrong?

bknarf

Ah wait. I've tried it again. Had to install RuneAudio again. Did the kernel update. And now it appears to boot correctly.

uname -a

Linux runeaudio 4.1.12-2-ARCH #1 SMP PREEMPT Sat Nov 7 09:20:07 MST 2015 armv7l GNU/Linux

aplay -l

card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: [b]HiFiBerry DAC+ Pro[/b] HiFi pcm512x-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

As the HiFiBerry DAC+ Pro is now specifically listed at card 1, does this mean the new driver has actually been loaded, and the clock from the Pro card is being used?

By the way, I haven't edited or renamed the config.txt or config.txt.pacnew (yet). I guess it is advisable to make the new version active?

bknarf

Bummer, now it appears that wireless is not working anymore

Can this be caused by the kernel update? In the RuneUI the WLAN connection is still visible, but status is not connected (No IP assigned). I've deleted the Wifi profile and tried to connect again, but without success. I find it strange that at WiFi stored profiles, under Show, there is no profile visible. When trying to Add a new profile, it still doesn't show up. Somehow it appears that the WiFi settings are not correctly stored anymore? (It did work before)

°pdi°

Raspberry B+
before RuneAudio: 0.3-beta (3.12.26-1-ARCH)
now RuneAudio: 0.3-beta (4.1.12-1-ARCH)

Hi Frank,

thank you! The pi boot with the new kernel.

I follow your advice and connect a monitor (tv) to the pi. The fault was an incorrect root-partiton entry in cmdline.txt. I had to change root-partition to "root=/dev/mmcblk0p5" (I take the right parameter from /boot/cmdline_linux-arch-rpi_3.12.26-1-ARCH.txt)

In the config.txt i had to add some entrys.

The config.txt is now:

device_tree_param=i2c_arm=on
device_tree_param=i2s=on
dtoverlay=hifiberry-dacplus
dtoverlay=lirc-rpi,gpio_in_pin=23
cmdline=cmdline.txt
kernel=kernel.img
gpu_mem=64

(Lirc is not working yet, but this is no problem at the moment.)

"aplay -l" print

card 1: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0

Fine. With "Pro" in the name, the new driver is running.

One issue at the moment: The volume knob won't work. The master-control appears in "alsamixer" as "Digital".

I changed the entry in output-section mpd.conf from "Playback Digital" to "Digital". Every reboot overwrites the entry to "Playback Digital".

edit: Volume knob works now. Solution was:

    redis-cli hset acards_details snd_rpi_hifiberry_dacplus "{\"sysname\":\"snd_rpi_hifiberry_dacplus\",\"extlabel\":\"HiFiBerry DAC+ (I&#178;S)\",\"mixer_numid\":\"1\",\"mixer_control\":\"Digital\",\"hwplatformid\":\"01\",\"type\":\"i2s\"}"

Klaus

hondagx35

Hi Klaus,

the file "mpd.conf" is controlled by rune audio.

Please search the forum (Hifiberry DAC+ hardware volume) and adapt the solution to your needs.

    [root@runeaudio ~]# redis-cli hset acards_details snd_rpi_hifiberry_dacplus "{\"sysname\":\"snd_rpi_hifiberry_dacplus\",\"extlabel\":\"HiFiBerry DAC+ (I&#178;S)\",\"mixer_numid\":\"1\",\"mixer_control\":\"Digital\",\"hwplatformid\":\"01\",\"type\":\"i2s\"}"
php /var/www/command/refresh_ao

Frank

°pdi°

Hi Frank,

you were faster, while i edit my post.

Klaus

°pdi°

In a brief (without warranty, may brake your installation)

Raspberry Pi B+ and HiFiberry DAC+ Pro with RuneAudio 0.3-beta

edit: Before upgrading, update RuneAudio (http://www.runeaudio.com/documentation/troubleshooting/updating/

Step 1: Upgrade the kernel

pacman -Sy --force raspberrypi-firmware-bootloader linux-raspberrypi

Step 2: Edit config.txt

    device_tree_param=i2c_arm=on
    device_tree_param=i2s=on
    dtoverlay=hifiberry-dacplus
    cmdline=cmdline.txt
    kernel=kernel.img
    gpu_mem=64

Step 3: Edit cmdline.txt. Set the right root-patition, e.g. given in your cmdline_linux-arch-rpi_3.12.26-1-ARCH.txt. E.g.:

 "root=/dev/mmcblk0p5"

Step 4: Make the right choises in Menu --> Settings = HiFiBerryDac+ and --> MPD-Configutations = HiFiBerryDac+

Step 5: Reboot.

Step 6: ssh to raspberry.

aplay -l

should print the HiFiBerry DAC+ with "Pro" in name.

Step 7: Change mixer-control to "Digital"

redis-cli hset acards_details snd_rpi_hifiberry_dacplus "{\"sysname\":\"snd_rpi_hifiberry_dacplus\",\"extlabel\":\"HiFiBerry DAC+ (I&#178;S)\",\"mixer_numid\":\"1\",\"mixer_control\":\"Digital\",\"hwplatformid\":\"01\",\"type\":\"i2s\"}"
php /var/www/command/refresh_ao

Step 8: Reboot (maybe not necessary)

Thats all.

Frank, thank you very much for your help.

Klaus

bknarf

Is it really needed to add the kernel and cmdline entries in the config.txt? I mean, the name of the files didn't changed after the kernel update, right? In my case, on a RPi2, it seems i can boot without a problem after doing the update and without editing the file.

BUT ... after the kernel update, it appears I cannot connect to my WiFI again. To be sure, I've tried it again. Started with a fresh install of RuneAudio. Set up my WiFi, which works then. But after the kernel update and reboot the wlan0 connection does not want to connect anymore. Tried to delete the profile and add a new one (via WebGUI), but doesn't help.

Is there a way to have the correct driver for the HifiBerry DAC+ Pro loaded AND have working WiFi?

FrankB

hondagx35

Hi bknarf,

Is it really needed to add the kernel and cmdline entries in the config.txt?

Not for the Pi2, it's only needed when you are on an older Pi.

Is there a way to have the correct driver for the HifiBerry DAC+ Pro loaded AND have working WiFi?

You can try to install crda and set the country code to yours.

pacman -S crda

This is not tested!

Frank

bknarf

Hi Frank,

Thanks for the suggestion. I installed crda and uncommented my country region in /etc/conf.d/wireless-regdom. After a reboot, nothing seems to be changed. Deleted the existing wireless profile again via the WebGUI and set up a new one, but still the same issue ...

FrankB

JeffD

bknarf wroteHi Frank,

Thanks for the suggestion. I installed crda and uncommented my country region in /etc/conf.d/wireless-regdom. After a reboot, nothing seems to be changed. Deleted the existing wireless profile again via the WebGUI and set up a new one, but still the same issue ...

FrankB

I have the same problem on my cubietruck. I cant connect to WiFi. Storing the profile is not possible. Maybe writing to the nand Memory is the problem?