PnP III v3.50: Enhance the standard OS - DOWNLOAD HERE!

[ilovemyjoggler]

yes.

[offbeatdave]

If you cannot remove the Dilbert icon by long pressing and selecting 'Remove' (I can't), you can either edit the applications.xml file in /media/appshop/ or Telnet in and enter the following:

Code: Select all

sed -i -e "/dilbert/d" /media/appshop/applications.xml
killall tango

[offbeatdave]

Updating LMS via the code in the opening post should now work more reliably. It looks clumsy but should be OK. As always, use at your own risk. Current update version is the nightly from 17th October 2013.

Edit: It should now all be much simpler cleaner as of 19th October (although the mechanics of it are relatively crude still!) and it seems to work OK. Also, currently updateable version is the nightly dated 18th October 2013.

[offbeatdave]

v3.34 should be uploaded in the next few minutes. It's not worth updating from recent versions to be honest, but it 'scratched an itch' as it were.

v3.34 (18th October 2013)
Removed Dilbert app - no longer functions
Updated Logitech Media Server to nightly build v7.8.0-1382017549 (17th October 2013)
Stopped 'Screenoff' icon from being replaced with rubbish version if installing 'Shutdown' icon
Added 'sound fix' for installing PnP III on an OpenFrame2 unit flashed with Roobarb's clean image!

[offbeatdave]

It's a minor update, but v3.35 should now have an option in SWF Manager to update Logitech Media Server to whatever nightly build I have streamlined for PnP III.

Add option to update Logitech Media Server to SWF Manager on pre-v3.35 installations
(Updated 19th October 2013)
Check the changelog to see which version of Logitech Media Server is currently installed with PnP III or available for update. To add update or add an option in SWF Manger to update LMS, you'll need to Telnet/Putty in and enter the following:

Code: Select all

cd /media/appshop/script
wget http://dl.dropboxusercontent.com/u/77534245/Updates%20and%20Fixes/LMS_Update.sh

Logitech Media Server can then be updated at this point via

Code: Select all

sh ./LMS_Update.sh

or via SWF Manager. The desktop should restart to indicate the process has completed.

[offbeatdave]

I should just add to the above post that there is a tiny risk it could go wrong and crash LMS and you'll need to reinstall PnP III (or the LMS part from the install script with a stick in). My tests indicate that this is unlikely though.

[gegs]

I should just add to the above post that there is a tiny risk it could go wrong and crash LMS and you'll need to reinstall PnP III (or the LMS part from the install script with a stick in). My tests indicate that this is unlikely though.

I'm assuming it would be better to stop LMS altogether, using the script in SWF Manager, before attempting the LMS update.

[offbeatdave]

It shouldn't make a difference as the update script should stop LMS anyway.

[MightyDob]

Hi, I wanted to say a big thanks for this wonderfull OS, after only really realising the potential of Joggler a few months ago I now have three! I find the joggler the perfect alarm clock / squeezebox etc.

I wondered is there a simple way to stop LMS from running when the Joggler starts? As I really don't need it as I have had it running from NAS for the last few years. I use Squeeze OS on my other Joggler and have chosen not to install LMS would love the option to permanently disable on PnP

No worries if not simple to do, I can stop it through the SWF script it's just the wife likes to unplug and move the joggler

Cheers again for your work

[offbeatdave]

I wondered is there a simple way to stop LMS from running when the Joggler starts? As I really don't need it as I have had it running from NAS for the last few years. I use Squeeze OS on my other Joggler and have chosen not to install LMS would love the option to permanently disable on PnP

Either reflash the Jogglers and reinstall PnP III, removing the sections starting

#INSTALL LOGITECH MEDIA SERVER TO WEBSERVER
#ADDING LOGITECH MEDIA SERVER PLUGINS (BBC iPlayer, BBC iPlayer extras, Play Real, Play WMA)
#INSTALL LAME CODEC - not sure if it has any benefit

in the files/pnp3op.sh file on the USB stick beforehand

or

delete the file /etc/init.d/boot.d/S98squeezebox.server on the Joggler via WinSCP or Telnet

Code: Select all

rm -r /etc/init.d/boot.d/S98squeezebox.server

and reboot the Joggler.

I wouldn't recommend too many switching on or offs - it can cause some Jogglers to corrupt and need a reflash! That said, some seem rock solid.

[offbeatdave]

I should just add to the above post that there is a tiny risk it could go wrong and crash LMS and you'll need to reinstall PnP III (or the LMS part from the install script with a stick in). My tests indicate that this is unlikely though.

I have just completed a successful test again on one of my Jogglers. You do need to be patient - it can take a couple of minutes, but the Joggler desktop will restart (not a full reboot) when it is complete and LMS is starting up again. It should maintain your LMS settings too.

[MightyDob]

I wouldn't recommend too many switching on or offs - it can cause some Jogglers to corrupt and need a reflash! That said, some seem rock solid.

Fantastic thanks, all removed and working great Fair point about turning it on and off, will just have to buy more so they are in every room

[roger l]

Have tried several O2 and Openpeak (roobarb) reflashes on a unit with unknown history with no luck. I have logged in with mint and used Gparted to clean the internal MMC carefully.
With the Openpeak restore Key version I get a message that stops at "unable to format P3". EFI format ok P2 format ok but unable to format P3 stalls the reflash. Is there anything I can do to manually format the MMC or do you reckon it is done in?
Any help apprecated.

[offbeatdave]

Try flashing with the original o2 image via roobarb's reflashing tool. That has got things working ready for an open peak reflash for me in the past.

[roger l]

Tried a fresh true O2 Roobarb image and it throws up hundreds of I/O buffer errors and then fails to go past the Openpeak. It has now locked out the Mint stick. I will try the Mint os stick when it is cold again just to get a picture of the MMC. Looks like a deeply corrupted MMC unless I am mistaken.

[pete]

"idle thoughts"

Or it could have been a deeply corrupted USB stick.

Odds are in the favor of a corrupted USB stick corrupting the MMC memory. (that whole optimist, pessimist and realist thoughts here).

But if the boot fat EFI parition is trashed then....

But which came first; the chicken or the egg.

[roger l]

Thanks Pete, but I have read and re read the threads on here and only ever used a Kingston brand new Data Traveller stick (two of them) totally fresh formatted. They had been unused before. The puzzling thing is that the Openpeak Restore key version reports "EFI format ok P2 format ok and then unable to format P3" and there ends!!!
I am not going to let it dominate my spare time, but it is getting tedious now.

[pete]

Its only a machine.

After a while of playing with the Joggler partitions; I would just DD each partition or DD the entire MMC drive then utilize Buzz's Ubuntu build to delete and format and delete the MMC partition then DD the MMC partition back to the Joggler.

Its really easier than it sounds. As the USB stick is mounted you can do anything you want with the MMC partitions.
Just don't leave it deleted and empty.

Write flash to USB ; here while in Ubuntu you mount the USB stick to the /mnt directory.

dd if=/dev/mmcblk0p1 of=/mnt/mmcblk0p1.img bs=1M
dd if=/dev/mmcblk0p2 of=/mnt/mmcblk0p2.img bs=1M
dd if=/dev/mmcblk0p3 of=/mnt/mmcblk0p3.img bs=1M
dd if=/dev/mmcblk0p4 of=/mnt/mmcblk0p4.img bs=1M

Write usb to flash; here you write each partition back to the MMC

dd if=/mnt/part4.img of=/dev/mmcblk0p4 bs=1M
dd if=/mnt/part3.img of=/dev/mmcblk0p3 bs=1M
dd if=/mnt/part2.img of=/dev/mmcblk0p2 bs=1M
dd if=/mnt/part1.img of=/dev/mmcblk0p1 bs=1M

I use the command line stuff for DD and the GParted program in the Ubuntu GUI.

[roger l]

Thanks again. I am going to follow that as soon as I get a USB booting again. (I had used G parted in mint on USB and followed guidance from this board). It appears that it now won't boot from USB. I had Mint and tried again to reflash both versions (because even though it did not get it to take the firmware, it did allow booting from USB again). Have reformatted and renewed the reflashing sticks. Now whatever USB is in it flickers grey from the Openpeak screen and then back to solid Openpeak screen with no further activity. I think it is hub and keyboard time?

[pete]

Here is the way I think the boot works and why you may have an issue. Someone please let me know if I am not understanding.

The EFI boot flash on the 1Mb removable flash always looks at the first EFI boot partition on the MMC.

Personally I have wiped that partition and have had a non booting Joggler.

The above said when you write new firmware to the MMC it formats and rewrites all of the partitions. If something gets messed up at this point writing to the MMC partitions; specifically the first MMC EFI boot partition; then you will have problems.

I am guessing here; the assumption is that the boot efi flash will not do anything if it doesn't find the boot EFI partition on the MMC flash drive and the only way to fix it is to rewrite it and the only way to rewrite it is to do a swap out of the boot EFI flash chip with a boot Seabios flash chip.

The above noted if the MMC drive gets damaged; its soldered into place; not an easy fix; the alternative is a boot PATA drive connected to the ZIF connector on the Joggler.

Playing with the boot EFI MMC partition I have created a non booting Joggler a few times in the last few months.

My personal fix has been to have two EFI boot flash chips. One that boots up using the seabios flash and one that boots up using the regular EFI boot flash.

I swap out the Joggler EFI boot flash for the Seabios boot flash. I have a Wintel SSD bootable image. (wish I had a seabios linux boot image though)

I then boot up in windows and rewrite the MMC partition using a backup image made from another Joggler running wintel via seabios. Wintel running from my SSD's do not utilize the 1Gb MMC drive such that I can do whatever with it.

I have been playing a bit with the original stock EFI boot partition so I have made it some 250-300Mbs such that I can do more with it.