Home of the Squeezebox™ & Transporter® network music players.
Page 2 of 5 FirstFirst 1234 ... LastLast
Results 11 to 20 of 45
  1. #11
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    4,606
    Quote Originally Posted by coyrls View Post
    As discussed in this thread: https://forums.slimdevices.com/showt...re-cannot-save, saved ALSA settings for a USB DAC are not restored successfully. A workaround is to put "su alsactl restore" as a user command in the Tweaks tab.
    I had completely forgotten that thread

    Name:  facepalm.png
Views: 163
Size:  114.3 KB

    But I have knocked up (on a rpi3b+) a pCP v7.0.1 player with a usb dac I have which uses volume control.

    I set volume to 100% for 0.0db in alsamixer and saved the setting via Card Control on the Squeezelite page.

    In LMS > Sewttings > Player > Audio I set Volume controls adjust outputs.

    Started playing fip radio

    After reboot this is a snip from the boot log file

    Code:
    Waiting for network. Done (1).
    Starting ALSA configuration...alsactl: init:1787: Cannot find soundcard 'USB'...
    alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
     ALSA restore error!
     Done (7).
    Starting Openssh server... Done.
    Starting Squeezelite and/or Shairport-sync...
    [ INFO ] Starting Squeezelite player: Squeezelite...

    The player started playback on reboot.

    I added su alsactl restore to the Tweaks page, saved (did a backup for good measure) and rebooted

    I got the same error message on boot but the dac started playing

    So "Starting user commands" has no effect in this user case

    I don't have time to try a rpi4b

    ronnie

    ronnie

  2. #12
    Junior Member
    Join Date
    Feb 2021
    Posts
    16
    Quote Originally Posted by Man in a van View Post
    Try this

    On the WiFi page scroll down to Network wait and set it at 100, reboot
    Done, no change for the moment.

  3. #13
    Junior Member
    Join Date
    Feb 2021
    Posts
    16
    Quote Originally Posted by Man in a van View Post
    Next time it does not work from startup or reboot paste the boot log

    Main Page > Diagnostics > Logs
    As I can see, the problem is here:

    Waiting for soundcard USB to populate. Done (1).
    Waiting for network. Done (1).
    Starting ALSA configuration...alsactl: init:1787: Cannot find soundcard 'USB'...
    alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    ALSA restore error!
    Done (7).


    So it is necessary to restore alsa config with putting alsactl restore into tweaks commands?

  4. #14
    Junior Member
    Join Date
    Feb 2021
    Posts
    16
    So tried adding sudo alsactl restore, but it didn't help. The situation is the same.
    Afetr re-plugging works good.

  5. #15
    Senior Member
    Join Date
    Feb 2011
    Posts
    171
    Try saving manually at the command line (su alsactl backup) and then backing up (pcp bu), then rebooting with the "su alsactl restore" in Tweaks.

  6. #16
    Senior Member
    Join Date
    Feb 2011
    Posts
    171
    Quote Originally Posted by bigq View Post
    As I can see, the problem is here:

    Waiting for soundcard USB to populate. Done (1).
    Waiting for network. Done (1).
    Starting ALSA configuration...alsactl: init:1787: Cannot find soundcard 'USB'...
    alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    .alsactl: load_state:1763: Cannot find soundcard 'USB'...
    ALSA restore error!
    Done (7).


    So it is necessary to restore alsa config with putting alsactl restore into tweaks commands?
    Only if you need to restore an alsactl setting, if you do, try manually saving as above after you have set the level with alsamixer.

  7. #17
    Junior Member
    Join Date
    Feb 2021
    Posts
    16
    Man in a van and coyrls, thanks for your advises.
    So I tried to save (sudo alsactl store), backup and then reboot.
    The same situation, only replugging helps after boot.

    As far as I can see the problem is in initializing 'USB' soundcard on boot. For some reason it's not found.
    May be there is a command to add in tweaks that could initialize it manually?

  8. #18
    Senior Member
    Join Date
    Feb 2011
    Posts
    171
    Quote Originally Posted by bigq View Post
    Man in a van and coyrls, thanks for your advises.
    So I tried to save (sudo alsactl store), backup and then reboot.
    The same situation, only replugging helps after boot.

    As far as I can see the problem is in initializing 'USB' soundcard on boot. For some reason it's not found.
    May be there is a command to add in tweaks that could initialize it manually?
    No, I don't think that's the problem. I think alsactl is a red herring, unless you are setting an ALSA level, which you are not, it's not needed. The error messages you are seeing are to do with part of a script that is only executed when ALSAlevelout is set to "Custom". Your problem was happening before this change was made and, as you are not setting an ALSA level it is not needed. Everybody with a USB DAC who sets ALSAlevelout to "Custom" will see this problem but the only consequence is that the ALSA level is not restored on reboot, not that the USB DAC doesn't function.

    Your USB card is found, as that is confirmed by the message "Waiting for soundcard USB to populate. Done (1)." that you have reported. The only odd thing that I can see in what you've posted is that alsamixer shows two dbGain bars for your DAC, I have only ever seen one. What output setting do you have under Squeezelite settings? Have you tried: "hw:CARD=v12,DEV=0"?

  9. #19
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    4,606
    @bigq

    Load up pCP v6.0.1 and see how you go

    ronnie

  10. #20
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    4,606
    So, I took my own suggestion (Edit, this is on a rpi3b+)

    pCP v6.0.1 Boot log

    Starting piCorePlayer v6.1.0 startup...
    Checking for boot files on mmcblk0p1...
    Trying to mount /dev/mmcblk0p1.
    ssh file found on mmcblk0p1.
    newpcp.cfg not found on mmcblk0p1.
    Setting default piCorePlayer repository...
    Generating sound card drop-down list...
    Loading configuration file... Done.
    Loading pcp-lms-functions... Done.
    Waiting for soundcard USB to populate. Done (1).
    Waiting for network............... Done (15).
    Starting Openssh server... Done.
    Starting Squeezelite and/or Shairport-sync...
    [ INFO ] Starting Squeezelite player: Squeezelite...
    Done.
    Starting httpd web server... Done.
    Setting CPU scaling governor to ondemand... Done.
    Creating static footer... Done.

    Finished piCorePlayer v6.1.0 startup.

    To setup piCorePlayer, use the web interface via a browser:
    - http://192.168.1.122

    Press [Enter] to access console.

    In the background, ntpd is syncing time between piCorePlayer and the internet.
    A large offset between 1970 and now is normal.

    Then did an insitu update to v7.0.0

    Be careful of space, I just squeezed in
    [ INFO ] You are installing piCorePlayer7.0.0
    [ OK ] Free space: 15636k - Required space: 15000k

    Starting piCorePlayer v7.0.0 startup...
    Starting rngd using /dev/hwrng... Done.
    Checking for boot files on mmcblk0p1...
    Trying to mount /dev/mmcblk0p1.
    ssh file found on mmcblk0p1.
    newpcp.cfg not found on mmcblk0p1.
    Setting default piCorePlayer repository...
    Generating sound card drop-down list...
    Loading configuration file... Done.
    Loading pcp-lms-functions... Done.
    Waiting for soundcard USB to populate. Done (1).
    Waiting for network....... Done (7).
    Starting Openssh server... Done.
    Starting Squeezelite and/or Shairport-sync...
    [ INFO ] Starting Squeezelite player: Squeezelite...
    Done.
    Starting httpd web server... Done.
    Starting to Advertise picoreplayer.local... Done.
    Setting CPU scaling governor to ondemand... Done.
    Creating static footer... Done.

    Finished piCorePlayer v7.0.0 startup.

    To setup piCorePlayer, use the web interface via a browser:
    - http://192.168.1.122

    Press [Enter] to access console.

    In the background, ntpd is syncing time between piCorePlayer and the internet.
    A large offset between 1970 and now is normal.
    I ran the minor update to v7.0.1

    Starting piCorePlayer v7.0.1 startup...
    Starting rngd using /dev/hwrng... Done.
    Checking for boot files on mmcblk0p1...
    Trying to mount /dev/mmcblk0p1.
    ssh file found on mmcblk0p1.
    newpcp.cfg not found on mmcblk0p1.
    Setting default piCorePlayer repository...
    Generating sound card drop-down list...
    Loading configuration file... Done.
    Loading pcp-lms-functions... Done.
    Waiting for soundcard USB to populate. Done (1).
    Waiting for network....... Done (7).
    Starting Openssh server... Done.
    Starting Squeezelite and/or Shairport-sync...
    [ INFO ] Starting Squeezelite player: Squeezelite...
    Done.
    Starting httpd web server... Done.
    Starting to Advertise picoreplayer.local... Done.
    Setting CPU scaling governor to ondemand... Done.
    Creating static footer... Done.

    Finished piCorePlayer v7.0.1 startup.

    To setup piCorePlayer, use the web interface via a browser:
    - http://192.168.1.122

    Press [Enter] to access console.

    In the background, ntpd is syncing time between piCorePlayer and the internet.
    A large offset between 1970 and now is normal.

    All good

    ronnie

    I have copies of the respective dmesg logs if anyone is interested
    Last edited by Man in a van; 2021-02-10 at 02:16.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •