266 replies to this topic

[guirigui]

Hello,

last update mentionned flashing new image recommanded after february 22th...

Does that mean the linguage of the image had changed.. again????

I have flashed my ET 6000 recently to be compatible..

I am puzzled with this date..

Please clarify..

Thanks...

Edited by guirigui, 25 February 2015 - 11:48.

[WanWizard]

If there is an operating system update (compare with Windows7 => Windows8) you need to flash. Such a change happened a few days ago.

 

Theoretically you can update, but you'll have to download over 300 packages (which overloads our download servers), and there is a big chance that you'll have problems (for example if the network package updates, you loose network connection, causing the rest of the update to fail).

 

So for most users, flashing is a lot easier, done in 5 minutes, and if you have the autobackup plugin active, even without loosing any settings.

[ian1095]

The autobackup plugin is cool and does work quite well,but it fails to backup anything that you have in init.d to start at bootup such as livestreamersrv or inadyn.the files are saved,but they will never again autostart at bootup.

 

So these always have to be installed again after reflashing which is a pain.

 

Any symlinks that the user has created have to be created again too,such as moving the extensions folder to hdd.

 

Ian.

Edited by ian1095, 25 February 2015 - 19:19.

[zeros]

This old software upgrades generally succeed, but it is a very bad idea. There are many packages that should be in addition to update manually, or else things are working much worse.
Examples-
New dvb-usb-em28xx (1.0-r0.10) DVB-T2 driver (old was r0.9)
New cccam (2.3.0-r0.10) (old was r0.9)
New softcamsetup (1.0+git169) (old was git0)
etc., etc.
In addition, quite a number of packages remain non-renewal because dependences are non-completed. Thus firmly fresh new software for this time.

[MiLo]

The workaround that has been floating around this forum has been implemented by MiLo.

Actually, that wasn't a workaround. That "mipsel" was dropped from the arch list was a bug in our distro configuration that has been around for many years but never surfaced up until the moment that the feed config was properly done in OpenEmbedded.

[WanWizard]

Ah, I thought I'd understood the "mipsel" arch was no longer used, and replaced by "mips32el". Misunderstood then...

[Erik Slagter]

mipsel is still obsolete though, but still "compatible" so it shouldn't have been dropped.