No bugs to fix, but I saw you applied all my precious advices for your web-interface.

But don't worry, I'm now on 7025 and we'll be far for a long long long while ... until you succeed to code a webif for 7025

So... are you ready for the second fighting-summer?

FlashWizard works with ANY image in flash.
The point is different:
if you want to install a recent image with LZMA compression, then you CAN'T use any official DMM image in flash, because the official images are too old and don't support LZMA

Zitat

Originally posted by pcd

You are of course the Master

Hi, thank you for all new improvements in 7025's actual cvs.

Btw, I am reporting an actual bug in timeshift (cvs from today):
when you press yellow button the picture stops (as should be).
But when you press again the button to restart the timeshifted recorded channel, the timeshift is immediately aborted and the vision continues from live channel data.

Thank you for an advice
MB

Hi

FlashWizard does NOT support flash installation of images in NAND memories, such have the 7020 and 7025.

Thanks tmbinc, it's corrected in today's cvs
:]

Yep, I can confirm

sorry, delete

Zitat

Originally posted by thowi
Maybe all these problems with the NAND memory are also the reason why musicbob doesn't want to port the flash wizzard to the 7025 or hasn't succeeded so far

7025 is OE, just like 7020, so there are no major problems in porting FlashWizard.
You wont believe it, but the only reason that actually delay the porting of FlashWizard to 7025 is the boot menu porting.
And, to be honest, there is not a big need of a multiboot solution for the moment, as there are very few firmwares to install I can count 2 actually

The FlashWizard's boot-menu is library-aware and font-aware, and that's the reason which allowed it to work on all developed firmwares around, from tuxbox 1.07 to 7020's OE nowadays.

FlashWizard last np beta is currently able to unpack and install images on 7025 (and do backup-restores as well) on CF, HDD, USB devices, just like other dreamboxes.

As soon as I will port the boot-menu to new fb, then FW 7025 will be released.... but I'm actually involved in some other projects for 7025...
Cu

Zitat

Originally posted by musicbob
@developers
I also found a string that can not be translated in python file enigma2/lib/python/Plugins/SystemPlugins/ConfigurationBackup/plugin.py at line 208, should be fixed as follows to let it being translated:

self.session.openWithCallback(self.startRestore, MessageBox, _("are you sure you want to restore\nfollowing backup:\n") + self.sel + _("\nEnigma2 will restart after the restore"))

Can I kindly ask again to fix it in CVS?

I actually fix it manually when I build a new image, but it's better to have it fixed officially, for other languages translations too.

Thanks once again
MB

@developers
Hi, I make a full translation for enigma2 to italian language.
Please find the it.po file in the attached zip.
I compiled and tested it on today's CVS image for 7025 and it is working ok.

I also found a string that can not be translated in python file enigma2/lib/python/Plugins/SystemPlugins/ConfigurationBackup/plugin.py at line 208, should be fixed as follows to let it being translated:

self.session.openWithCallback(self.startRestore, MessageBox, _("are you sure you want to restore\nfollowing backup:\n") + self.sel + _("\nEnigma2 will restart after the restore"))

Thank you and best regards
MB

Thanks DieMade

Got a enigma2 crash everytime it goes to stand-by, I use a CVS from today with latest commits.
Please find here the log:

enter standby
Screen <class 'Screens.Standby.Standby'>((<mytest.PowerKey instance at 0x2c432b70>,), {}): exceptions.NameError
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/mytest.py", line 150, in create
    return screen(self, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/Screens/Standby.py", line 55, in __init__
    setLCD("                             ")
NameError: global name 'setLCD' is not defined
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 47, in action
    self.actions[action]()
  File "/usr/lib/enigma2/python/mytest.py", line 346, in powerup
    self.standby()
  File "/usr/lib/enigma2/python/mytest.py", line 349, in standby
    self.session.open(Standby, self)
  File "/usr/lib/enigma2/python/mytest.py", line 227, in open
    dlg.isTmp = True
AttributeError: 'NoneType' object has no attribute 'isTmp'

Thank you in advance for advice.
Best regards

Hi, this is with latest CVS update from yesterday.
(I think there was a kernel update too)

root@dm7025:/# more /proc/meminfo              
MemTotal:        92764 kB                      
MemFree:          1700 kB                      
Buffers:           568 kB                      
Cached:          61780 kB                      
SwapCached:          0 kB                      
Active:          25148 kB                      
Inactive:        53996 kB                      
HighTotal:           0 kB                      
HighFree:            0 kB                      
LowTotal:        92764 kB                      
LowFree:          1700 kB                      
SwapTotal:           0 kB                      
SwapFree:            0 kB                      
Dirty:            1360 kB                      
Writeback:           0 kB                      
Mapped:          25036 kB                      
Slab:             5344 kB                      
CommitLimit:     46380 kB                      
Committed_AS:    42416 kB                      
PageTables:        428 kB                      
VmallocTotal:  1048560 kB                      
VmallocUsed:      4100 kB                      
VmallocChunk:  1044456 kB

CVSDATE = "20060312"
enigma2.bb is set to tomorrow

Zitat

Original von noggie
BTW, to me it seems like running ext3 on CF is actually a little bit faster than running jffs2 on internal flash. Can anyone confirm or deny this?

In my experience, this is true since ever.
Images running on external ext3 devices are quite faster than the same booted from internal flash.
I noticed it by booting images from usb/cf/hdd on 7000 and 7020 as well.

dnuos

how do you did it?
You had no bad blocks yesterday on your dm7020... that's incredible!

Here's the little utility to test bad blcks.
I compiled it static, so it's image-aware

FYI my 7020 has a bad block

root@dm7020:/var/tmp# prova
*** bad block list: 01b8c000 (1 blocks, 16 kB total)
root@dm7020:/var/tmp#

That's a good point.

As for old Mechatron's Dreamflash, if FW is installed on a official DMM image, then no broken warranty issues should arise, as the flash memory of dreambox is unchanged, and all the installed images will reside on external devices (usb/cf/hdd) that cannot damage hardware or internal memory in any way.

The point is:
the last official image by DMM for DM7000 is very old.
You have no chances to install actual LZMA images having one official image in flash.
You must use an actual CVS image instead, as BoxMan's ones, but you can't use any official image from DMM.

So I think that warranty issues are not so simple to handle, looking from DMM point of view.