original home.htm file

[justin_gib]

still not working going to need the whole of the htdocs folder :( sorry for the bother

[justin_gib]

got it working with the file :) thanks! a million! now for the firmware updates :) is there a recommendedupgrade path or can i go direct to your latest firmware?

[fvdw]

In principle it should work to go directly to the latest firmware using the original firmware upgrade menu of Philips

[justin_gib]

no joy, tried with 14-0 and 10-0 after reading another post, but no joy, what i am doing is, unzipping the firmeware file and trying to update the firmware with the .img file i wait a while and then it comes back to me with an "ERROR!" on the page. Any ideas

[fvdw]

mmm...

connect with Putty ssh en give command

Code: Select all

fdisk -l

This will give as output the partition table of the disk
post it here to check if is ok.
it could be that you are the unlucky owner of a spd8020 version with small system partition. The system partions must be at least 250 MB to be able to store the firmware. We have seen in the past soem sp8020's with a small system partiton of only 100 MB.
If the partition size is ok then there is another way to install the firmware.

[justin_gib]

fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 32 257008+ 83 Linux
/dev/sda2 33 64 257040 83 Linux
/dev/sda3 65 96 257040 82 Linux swap
/dev/sda4 97 60801 487612912+ 5 Extended
/dev/sda5 97 144 385528+ 83 Linux
/dev/sda6 145 60801 487227321 83 Linux
#

[fvdw]

the partition size is not the problem, these are tthe normal settings :scratch
Maybe you have changed som more files previnting the scrips from working normally.

Anyhow. Lets see if we can upgrade it manually.
Boot the spd8020 and perform the firmware upgrade procedure using the the web interface.
Do NOT reboot after you get the error
Connect with ssh and check content of the the folder /rw_fs/tmp

Code: Select all

cd /rw_fs/tmp
ls -al

check if the list contains a file with exenstion .img ait should have a size of about 250 MB.
if it is there then writing the firmware to disk fails for some reason. We will no try to write it manually to a system partition.

From the output you posted I see that your current firmware is running from sda1 (note the little star behind it)
So we are going to write the firmware to partition sda2.
use this command (replace "name" by actual name of the .img file)

Code: Select all

dd if=/rw_fs/tmp/name.img of=/dev/sda2 bs=1M

This can take some minutes. Wait until it completes and specifies how which blocks it has written. This should match with the the size in MB of the image file. If it is not then don't proceed as the image file was then not complete.
To verify if writing was ok try to read the partition using this command

Code: Select all

dd if=/dev/sda2 of=/dev/null

If this completes without giving read error then the partition is ok and no write errors were made.

If thats ok we are going to change the partition that the spd8020 uses for booting from sda1 to sda2
To do this give command

Code: Select all

fdisk /dev/sda

Ypu will get a line mentioioning

Code: Select all

Command (m for help):

give command "p" (without the quotes), this should list the partition table.
Check if the * is behind sda1.
Change it by using the "a" command and entering the partition number (this is 1 in this case)
Check with p command the star should be gone now behind sda1 partition
enter again the "a" command and now give partition number 2
Check with "p" if the star is now behind partition 2
if ok leave fdisk with entering the "w" command to write the changes to disk.
If you leave fdisk without giving the "w" command the changes you made will not be written to disk and everything remains unchanged.

Now reboot your spd8020 and keep your fingers crossed that it comes up. if it fails to come up nothing is lost but then you need to remove the HDD from the casing to correct the error as when it fails to boot there is no ssh access possible.