That's the big problem with ESS cards, there is no official driver for
them. I don't have any cards to test with either.
If you go to the diagnostics, and look at dmesg (or just ssh in and use
dmesg) you might get a clue as to why the ESS9023 driver is failing to
register the card. When you
Never mind, I derived from "Perl 5.24 libraries for Debian Stretch/9
armhf (Download included)" where to copy the compiled files. In my case
from
$src/slimserver-vendor-public-7.9/CPAN/build/arch/5.24/arm-linux-gnueabihf-thread-multi-64int/auto
to /usr/share/squeezeboxserver/CPAN/arch/5.24/
Hi, I tried to install Logitech Mediaserver 7.9 on Raspbian Stretch but
the server won't start. I followed the steps in the thread
Problems-running-LMS-on-Debian-Stetch to build the binaries for Perl
5.24.1 that is shipped with Stretch, but this does not help. The build
finishes and ends with an
paul- wrote:
> Second. What is the output of /usr/local/bin/squeezelite -l
>
> (or aplay -L )
pCP 3.21 Audio
Audio outputGeneric/simple ESS9023 DAC
Code:
tc@Goldfinger:~$ /usr/local/bin/squeezelite -l
Output devices:
null -
card is a cheap "Audiophonics DAC Sabre ES9023 I2S" from china.
I tried a few other cards in the Audio Output setting, but none got
squeezelite running.
I just changed in-situ from 3.21 audio to 3.21 standard.
Both ESS9023 and Generic/Simple ESS9023 work here.
Have to go back to audio to
First of all, What card do you actually have? And what card is
selected in the drop down box on the squeezelite page.
Second. What is the output of /usr/local/bin/squeezelite -l
(or aplay -L )
paul-'s Profile:
updated from pcp 3.20 to 3.21 via the web gui.
saved my config to usb and my zero w came back online to WiFi.
so far so good.
problem is that squeezelite is not running, even after reboot.
I found a different output setting on the squeezelite page of the web
gui and changed it to the one that
paul- wrote:
> I get what you are saying but using google doesn't work either, since
> there are providers that block DNS requests to googles DNS servers.
> Defaulting to the local DNat router is still the safest default.
I suppose it is whatever you consider the lesser of two evils. Anyway
I get what you are saying but using google doesn't work either, since
there are providers that block DNS requests to googles DNS servers.
Defaulting to the local DNat router is still the safest default.
paul-'s Profile:
paul- wrote:
> Have you looked at the static IP setup page? There are fields for
> nameserver. you just have to fill them out. And if you let DHCP do
> it's work, then the router will tell the remote devices what to use.
Yes I know Paul. I do networking stuff for a living. I know it's
d6jg wrote:
> I think this is a buggette in pCP. It assumes that everyone's router
> works as a dns relay. Some don't. It would be safer to have 8.8.8.8 and
> 8.8.4.4 as the default IMHO
Have you looked at the static IP setup page? There are fields for
nameserver. you just have to fill them
jfo wrote:
> This worked...it's proceeding through the update process now. I tried
> the google dns earlier but didn't reboot. Out of curiosity, I'll switch
> to my Open DNS and reboot to see if that was the issue. I had changed
> the nameserver to the OpenDNS but didn't reboot before.
>
>
They do continue to tinker with the USB stuff. Perhaps there is
something kernel related, but unless you can repeat the problem it's
doubtful it could be found. USB on the rpi's is just not very good.
paul-'s Profile:
paul- wrote:
> Your boot partition is not large enough. Have you saved anything else
> to the boot partition. There is a boot partition space check, but I
> have it set very tight.obviously too tight. Starting with pCP
> 3.20, we increased the boot partion size to 32MB as the kernels
paul- wrote:
> Anytime I've had a kernel crash, it was power supply related.
Strange been using the Koppla with my setup and 3.11 from when it was
released without any problems "will have a tinker"
Eyerex's Profile:
Anytime I've had a kernel crash, it was power supply related.
paul-'s Profile: http://forums.slimdevices.com/member.php?userid=58858
View this thread: http://forums.slimdevices.com/showthread.php?t=107352
Hello just had a lockup while i was using 3.21 at the time i playing an
album and clicked on the next track button via the web page GUI also
couldn't get into the PiCorePlayer settings page to do a restart so had
to pull the plug which when it restarted gave me see image, turned off
again and
Ubuntu should work. I use linux mint 18 it to works very well and is
small enough i run that in esxi
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x
MeridianDSP5200 MeridianDSP5200HC 2 xMeridianDSP3100
Greg Erskine wrote:
> hi mff,
>
> Great news! I have booked marked this for future reference. :D
>
> Thanks
> Greg
FYI and BTW, I had to run 2 instances of squeezelite on PCP to test
something.
I have noticed that PCP reports "squeezelite is not running" when the 2
instances run. When any of
LMS can run on piCorePlayer, that is piCore, that is Tiny Core Linux.
Use the OS you want that runs well on your host, LMS should run.
Especially if "ubuntu" matches your definition of a svelte system :)
3 SB 3 Libratone Loop, Zipp Mini iPeng (iPhone + iPad) LMS 7.9
(linux) with plugins:
jfo wrote:
> Interestingly, both versions return the following...
>
> tc@piCorePlayer:~$ nslookup picorplayer.sourceforge.net
>
You typed it wrongyour first try, you typed it right, then after you
tried fixing it, you started to type it wrong.
I upgraded in-situ from 3.20 to 3.21 Audio.
Everything went through and the version is working fine, including
built-in WiFi of RPi 3.
Thanks, guys, awesome work!
schup011's Profile:
22 matches
Mail list logo
