Spotify does not work.

[hondagx35]

Hi Ian,

please read my post again.

- go to MENU->MPD and select a different audio output
- change the output back to the old one.

Frank

[hondagx35]

Hi Pietpara,

Music plays fine fom nas. But I cannot change volume or any settings.

I have absolutely no idea what you did or what went wrong on your device.

Is your volume control greyed out?
If so please try to set the control to hardware or software on MENU->MPD.

You also can try to switch the output to Analog and then back to your DAC.

Frank

[ianhaynes]

Hi Frank,

Sorry, I couldn't get past the first part of your suggestion:

- switch to spotify
- select and play a song

As for switching to another audio output, I don't have any, just IQAudIODAC.

Ian

[hondagx35]

Hi Ian,

As for switching to another audio output, I don't have any, just IQAudIODAC.

With the latest stock image you should have Analog and HDMI as output options on a RP2/3.

If your kernel is updated you have to add
dtparam=audio=on
to your config.txt.

Frank

[pietpara]

Hi Pietpara,

Music plays fine fom nas. But I cannot change volume or any settings.

I have absolutely no idea what you did or what went wrong on your device.

Is your volume control greyed out?
If so please try to set the control to hardware or software on MENU->MPD.

You also can try to switch the output to Analog and then back to your DAC.

Frank

Thanks Frank,

well, it started when I opened Spotify from the Library screen. It said "Starting backend...." and just kept displaying this forever. I opened the settings menu, realizing that I had not activated spotify here. So I activated that and added (mispelt) username and password, and applied those settings. Nothing had changed, Spotify would still not launch. The I went back to settings menu and saw my username missed a letter, so I tried correcting that. That's when i noticed that I was unable to change any settings anymore.
I wanted to reboot, but through menu that did not work. I used Putty for a reboot command which rebooted it. But still no change in allowing any settings to be applied.
Volume control is visible and works graphically, but no volume change.

Does my debug log give no hints? http://pastebin.com/QC33Sb3i

Thanks
Pietpara

[pietpara]

Hi Frank,

If so please try to set the control to hardware or software on MENU->MPD.

You also can try to switch the output to Analog and then back to your DAC.

I tried this, but as said, I can change it but settings are not saved. After hitting apply or save, the settings revert to previous.
Very weird. Can it have anything to do with the error "cifs_mount failed" I see in the debug log?

cheers
Pietpara

[hondagx35]

Hi Pietpara,

Can it have anything to do with the error "cifs_mount failed" I see in the debug log?

No.

Please ssh to your device and check:
/var/log and /var/log/runeaudio
for any error.

It seems that something went terribly wrong on your device.
Have you ever done a hard reset (cut power)?

Your debug info looks good so far.

Frank

[pietpara]

Hi Frank,

I checked the logs and in /var/log there nothing peculiar.
However, in /var/log/runeaudio I see this in mpd.log:

Jan 13 21:47 : errno: Failed to open /var/lib/mpd/mpdstate: No such file or directory
Jan 13 21:47 : errno: Failed to save database: Failed to write to /var/lib/mpd/mpd.db: No space left on
device
Jan 13 21:47 : errno: Failed to write to /var/lib/mpd/mpdstate: No space left on device
Jan 13 21:47 : errno: Failed to open /var/lib/mpd/mpdstate: No such file or directory
Jan 13 21:47 : errno: Failed to save database: Failed to write to /var/lib/mpd/mpd.db: No space left on
device

Similarly in redis.log there are mentions of no space left to save DB on disk. With this message too:

WARNING overcommit_memory is set to 0! Background save may fail under low me
mory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or
run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

Shall I do this, or first find out the reason why the disk is full. A partition might have corrupted?

I tried running fsck, but since I see there are so many partitions, I am not sure how to run it. Could you give me some commands?

And yes, I had to use the button on the side of the RaspTouch twice because the UI hung up and a shutdown through SSH didn't work.

Many thanks!
Pietpara

[hondagx35]

Hi Pietpara,

Shall I do this, or first find out the reason why the disk is full. A partition might have corrupted?

Yes first we have to find the problem.
I think it was Spotify trying to connect and then filling up the log files.
Log files are stored on a RAM disk.

Your debug data looks good:

Code: Select all

###### Filesystem mounts - free space (df -h) ######
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       1.9G  1.6G  168M  91% /
devtmpfs        458M     0  458M   0% /dev
tmpfs           462M     0  462M   0% /dev/shm
tmpfs           462M  6.2M  456M   2% /run
tmpfs           462M     0  462M   0% /sys/fs/cgroup
tmpfs           462M  4.0K  462M   1% /tmp
logs            5.0M   32K  5.0M   1% /var/log
rune-logs       5.0M   28K  5.0M   1% /var/log/runeaudio
/dev/mmcblk0p1  100M   18M   83M  18% /boot

If i were you i would start with a fresh sd card.

Frank

[pietpara]

Thanks Frank,

could you point me to a thread or guide that tells me how to do that, please?

And where to download the build that I need for the RaspTouch, please

Cheers
Pietpara