ih8gates

Forum Replies Created

Viewing 12 posts - 1 through 12 (of 12 total)
  • 25. Februar 2022 at 2:30 #52098

    Looks like it was a hardware failure! Got my new Hifiberry today and everything’s working fine now. Thanks for your help!

    24. Februar 2022 at 14:27 #52096

    I’m pretty sure I’m on a recent image. I’ve got a new Hifiberry on its way to me (arriving today, hopefully). I’ll try that next.

    #### FILESYSTEM ####
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/root 60935408 2810348 55619572 5% /
    devtmpfs 414364 0 414364 0% /dev
    tmpfs 447644 0 447644 0% /dev/shm
    tmpfs 447644 23936 423708 6% /run
    tmpfs 5120 4 5116 1% /run/lock
    tmpfs 447644 0 447644 0% /sys/fs/cgroup
    /dev/mmcblk0p1 258096 54620 203476 22% /boot
    tmpfs 89528 8 89520 1% /run/user/1000

    #### LOAD AVERAGE ####
    0.02 0.02 0.00 1/232 18399

    #### KERNEL ####
    Linux PorchSpeakers 5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux

    #### LINUX-VERSION ####
    Distributor ID: Raspbian
    Description: Raspbian GNU/Linux 10 (buster)
    Release: 10
    Codename: buster

    23. Februar 2022 at 15:33 #52087

    Thanks. I went through these steps but I’m still not getting any sound through my Amp2.

    I set this option as the audio output for Squeezelite:
    sysdefault – snd_rpi_hifiberry_dacplus, HiFiBerry DAC+ HiFi pcm512x-hifi-0 – Default Audio Device, CARD=sndrpihifiberry

    And rebooted at each step. I can see Squeezelite syncing with the Logitech Media Server, but no sound.

    18. Februar 2022 at 15:44 #52063

    Ignore that last bit. It took longer that usual, but the web interface finally loaded.

    25. Oktober 2019 at 0:08 #47435

    Answering my own question. I figured it out once I started searching for Raspbian solutions rather than Max2Play solutions. The trick was to add

    hdmi_ignore_cec=1

    To /boot/config.txt and reboot.

    23. April 2018 at 17:24 #35283

    It only happened the first instance. After a reboot, the share works consistently.

    13. April 2018 at 15:23 #35170

    I’m pretty sure that I checked the debug info when I first had the problem and it did the same. Debug just repeated the mount info.

    It’s easy to reproduce the issue. At least on my install. If I create a new share, the folder is create, but it’s empty. Restart the Pi and the share works correctly. Could it be an issue with the move to Stretch to support the B+?

    13. April 2018 at 3:07 #35155

    The debug info just shows the mount info:

    
    //192.168.1.110/music /mnt/music cifs user=USER,password=PASS,sec=ntlm,iocharset=utf8,vers=1.0
    

    Same as it did when it failed.

    10. April 2018 at 22:14 #35112

    Since I’m no longer getting the error, where would I find that log?

    9. April 2018 at 21:15 #35089

    So, when it failed for me the 2nd time, it was after a fresh re-install. And failed the same way. I wonder if the script was creating the correct info to recreate the mount on reboot, but wasn’t properly executing the mount command when it created it the first time.

    9. April 2018 at 17:07 #35081

    Hmmm. I decided to reboot and now the mount is working!

    9. April 2018 at 17:04 #35080

    That didn’t work either. I created a simple user and password on the Windows machine. The mount folder is created, but it’s empty.

Viewing 12 posts - 1 through 12 (of 12 total)