cliveb wrote:
> The power supply wall-wart is fine, supplying 5.08V.
Was that measured with the PSU connected to the SB2? A common failure
mode of these are to measure fine on open output but buckling when asked
to drive any load.
Ah - I thought the meaning was it was only used in Ethernet not that
there was never any Wi-fi available on that particular device at all.
That does explain a couple of recovered SB2 devices that I have with
holes in the back ... I had thought that the card and antenna had been
taken out to use
Paul Webster wrote:
> You can try taking out the wifi board even if not using it.
> I have a SB Radio that will not boot with the wifi board in it but will
> if I take it out (and then use it from ethernet).
The wireless on the SB2 was an option, the board may not have been
fitted
Jeff
regularly takes much more than *20 hours* for the same.
20 hours is too much. Check the scanner.log file and the server's status
page. Where is it spending all this time?
--
Michael
___
discuss mailing list
discuss@lists.slimdevices.com
You can try taking out the wifi board even if not using it.
I have a SB Radio that will not boot with the wifi board in it but will
if I take it out (and then use it from ethernet).
Paul Webster
http://dabdig.blogspot.com
Author Radio France (FIP etc) plugin
My SB2 (bought back in 2005) seems to have finally turned up its toes.
A few weeks ago the display apparently failed, but the unit was still
working and playing OK.
Yesterday I went to use it and it was totally unresponsive, and not
showing as a player in LMS.
The power supply wall-wart is fine,
Dont want to hijack the thread but a close friend and I observe a
similar difference: On the same ~150k tracks library (mixed FLAC/MP3), I
usually get between *815 minutes* for an update scan, while his machine
regularly takes much more than *20 hours* for the same.
We both use the same LMS
pinkdot wrote:
> Difference in scanned files could be a permission issue on the server.
> So, check the top folder's permission and apply these setting to all
> underlying folders. This can easily be done in Files.
>
Very interesting tip this, didn't try it until now, I assumed everything
was
