[Announce] Community Firmware for Squeezebox Radio/Touch/Controller and LMS 8

[ralphy]

Had a second and third attempt with no joy. The download attempt lasted around a second before the ‘attempt failed’ message displayed with nothing downloaded.

Log attached....hopefully!

Thanks. From your log it appears you are running on piCorePlayer.

The problem is related to an attempt to reduce disk space usage in how pCP handles downloading firmware or doesn't rather.

Michael has provided a change request to the pCP team to resolve the issue.

[ralphy]

> I believe I suggested doing the direct download at the time to save the
> precious diskspace in a pCP environment.

Is there a way to tell pCP to exclude some files from being backed up? I
know there's filetool or something to tell it what to _include_. But
exclude?

--

Michael

Yes the exclude file is /opt/.xfiletool.lst

[mherger]

[Announce] Community Firmware forSqueezebox Radio/Touch/Controller and LMS 8

> Yes the exclude file is /opt/.xfiletool.lst

Ok, great. Maybe I'll find some time to power up a pCP with LMS (mine is
in the office - collecting dust...) to create a pull request to exclude
the firmware images from the backup.

--

Michael

[tw99]

What would be the advantage of moving to the latest firmware from a user's point of view ? Currently both my Radio and Touch work well enough, apart from the reboot-every-24?-days bug.

Or is this more of a future-proofing thing at the moment ?

[paul-]

Depends on where it downloads too. The Cache folder would be on a persistent drive or the /tmp drive. Neither location would be included in a backup.

[mherger]

[Announce] Community Firmware forSqueezebox Radio/Touch/Controller and LMS 8

> Depends on where it downloads too. The Cache folder would be on a
> persistent drive or the /tmp drive. Neither location would be included
> in a backup.

It's LMS' cache folder (where the library.db lives). That's persistent
drive then?

--

Michael

[paul-]

> Depends on where it downloads too. The Cache folder would be on a
> persistent drive or the /tmp drive. Neither location would be included
> in a backup.

It's LMS' cache folder (where the library.db lives). That's persistent
drive then?

--

Michael

Yes.

[mherger]

[Announce] Community Firmware forSqueezebox Radio/Touch/Controller and LMS 8

> Had a second and third attempt with no joy. The download attempt lasted
> around a second before the ‘attempt failed’ message displayed with
> nothing downloaded.

Please give the latest nightly build another try (8.0.1 or 8.1.0).

--

Michael

[whitman]

What would be the advantage of moving to the latest firmware from a user's point of view ? Currently both my Radio and Touch work well enough, apart from the reboot-every-24?-days bug.

Or is this more of a future-proofing thing at the moment ?

I've got a Radio and so this thread intrigued me. Like tw99, though, I have no idea what this is or what it does, and nowhere does it seem to tell us. An explanation wold be nice... or maybe it's a nerd-only thing, where if you need to ask you obviously don't qualify.

[kidstypike]

> Had a second and third attempt with no joy. The download attempt lasted
> around a second before the ‘attempt failed’ message displayed with
> nothing downloaded.

Please give the latest nightly build another try (8.0.1 or 8.1.0).

--

Michael

Updated to latest nightly 22/12/2020 (8.1.0) and the Touch downloaded and installed the update (8.0.1 r16817) no problem.

Playing music now.

[gegen]

Updated to latest nightly 22/12/2020 (8.1.0) and the Touch downloaded and installed the update (8.0.1 r16817) no problem.

Playing music now.

+1 for Squeezebox Radio, thanks.

Running LMS 8.1.0 on piCoreplayer v7.0.0b6

[slartibartfast]

After the update I notice there are no patches listed under the patch installer. Is that expected?
If the Alsa buffer patch for the Radio is included in the firmware is there a setting for buffer size?

Sent from my Pixel 3a using Tapatalk

[mherger]

[Announce] Community Firmware forSqueezebox Radio/Touch/Controller and LMS 8

> After the update I notice there are no patches listed under the patch
> installer. Is that expected?

I'd say so. Patches are even more sensitive to version numbers than LMS
plugins, as they directly change files. If a file changes, the patch
might fail to apply.

That said I would believe that most patches should still work, as most
of the changes in the firmware are lower level than what most patches
would touch. Authors will need to test and update their repositories.

--

Michael

[mherger]

[Announce] Community Firmware forSqueezebox Radio/Touch/Controller and LMS 8

> I've got a Radio and so this thread intrigued me. Like tw99, though, I
> have no idea what this is or what it does, and nowhere does it seem to
> tell us. An explanation wold be nice... or maybe it's a nerd-only thing,
> where if you need to ask you obviously don't qualify.

You'd have to carefully read the announcement, or you could easily miss
the link to the changelog ;-). Here it is:

https://ralph_irving.gitlab.io/lms-c...changelog.html

But as so often: if you didn't encounter any issues before, then there
is no _need_ to update.

One possible positive side-effect of the removal of some legacy stuff is
more free memory on the units. If you were using the image screensaver,
then this might save you a bunch of reboots due to memory restrictions.

--

Michael

[slartibartfast]

> After the update I notice there are no patches listed under the patch
> installer. Is that expected?

I'd say so. Patches are even more sensitive to version numbers than LMS
plugins, as they directly change files. If a file changes, the patch
might fail to apply.

That said I would believe that most patches should still work, as most
of the changes in the firmware are lower level than what most patches
would touch. Authors will need to test and update their repositories.

--

Michael

I checked the patches available for a Radio running 7.7.3 firmware and there were also none available. Would that be because the patch for LMS 8 had already been installed?

Sent from my Pixel 3a using Tapatalk