MAT 2.4: Diskussionsthread

[morly]

Falsche libzip... 64bit version fuer die 32bit mat binary

[macmanolo]

Falsche libzip... 64bit version fuer die 32bit mat binary

Und gebs eine lössung? oder mus neuer binary her?

darkmantk sagt er hat die neue binary im alte folder getan und das ergebnis ist das selber.

mfg

[morly]

Schaus mir morgen am 32bit Rechner an

[arci]

Hi @morly

... Warning ...

On new MAT 2.4 ... check the verification code of the kernel (ULK or OLD) !!!

I installed the new HDMU_13909_AzboxHD_OE_1956_Flash ... and ... the MAT recognize it with OLD kernel version !!!

Result ... AZBox stop on "Booting" ...because the xenv "y.start" variable is wrong ...

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.04.01 20:14:20 =~=~=~=~=~=~=~=~=~=~=~=
......
Scanning ROMFS image at 0x8c040000 (0x48040000) .. Found.
ROMFS found at 0x8c040000, Volume name = YAMON_XRPC
Found 1 file(s) to be processed in ROMFS.
Processing xrpc_xload_yamon_ES4_prod.bin (start: 0x8c040090, size: 0x0002fe84)
  Checking zboot file signature .. Not found.
  Trying xrpc_xload format .. OK
  Checking zboot file signature at 0x13000000 .. OK
  Decompressing to 0x91200000 .. OK (453328/0x6ead0).
  Load time total 173/255 msec.
Execute final at 0x91200000 ..

**********************************

* YAMON ROM Monitor

* Revision 02.06-SIGMADESIGNS-01-2.8.0.1

**********************************
Memory:  code: 0x11000000-0x11040000, 0x11200000-0x11204000

reserved data: 0x11240000-0x12440000, PCI memory: 0x12440000-0x12840000

Environment variable 'start' exists. After 1 seconds

it will be interpreted as a YAMON command and executed.

Press Ctrl-C (or do BREAK) to bypass this.

xrpc failed (9)--- if a xtask is using a cipher or if you reboot

--- xrpc will fail with RM_BUSY

Checking zboot signature..  it's not zboot file.

Error : Internal, code = ffffffff

YAMON>

Cause MAT has set xenv y.start:

setxenv y.start "xrpc 0xac080090; load zbf 0xb3000000; go

while ... with unlicensed ULK 3.3.1 or 3.9.2 kernel version ... You have to use:

setxenv y.start "dump romfs 0xac080000;load zbf 0xac080090; go"

Scanning ROMFS image at 0x8c040000 (0x48040000) .. Found.
ROMFS found at 0x8c040000, Volume name = YAMON_XRPC
Found 1 file(s) to be processed in ROMFS.
Processing xrpc_xload_yamon_ES4_prod.bin (start: 0x8c040090, size: 0x0002fe84)
  Checking zboot file signature .. Not found.
  Trying xrpc_xload format .. OK
  Checking zboot file signature at 0x13000000 .. OK
  Decompressing to 0x91200000 .. OK (453328/0x6ead0).
  Load time total 173/255 msec.
Execute final at 0x91200000 ..

**********************************

* YAMON ROM Monitor

* Revision 02.06-SIGMADESIGNS-01-2.8.0.1

**********************************

Memory:  code: 0x11000000-0x11040000, 0x11200000-0x11204000

reserved data: 0x11240000-0x12440000, PCI memory: 0x12440000-0x12840000

Environment variable 'start' exists. After 1 seconds

it will be interpreted as a YAMON command and executed.

Press Ctrl-C (or do BREAK) to bypass this.

ROMFS found at 0xac080000, Volume name = MIPS_LINUX_XRPC

ac080040 : Name = ., Type = dir, Size = 00000000, Next = 00000040

ac080060 : Name = .., Type = hard link, Size = 00000000, Next = 00000060

ac080090 : Name = vmlinux_xload.zbf, Type = file, Size = 006676ad, Next = 00000000

  Checking zboot signature..  it's a zboot file, signature OK.

  Decompressing to 0x90020000 .. 

Output length: 0x00f7927c(16224892)

load compressed zboot file from 0xac080090 to 0x90020000 OK

[    0.000000] Linux version 3.3.1-opensat (bonkel@ns504582.ip-198-245-62.net) (gcc version 4.9.1 (GCC) ) #1 PREEMPT Thu Mar 5 02:59:52 CET 2015

Ciao ...

[morly]

Fuck... no idea why... will check it immediately...
Thx for telling me...

- - - Aktualisiert - - -

found it!

 Team name: HDMU
 Description: TEAM
 Version: .
 About: Enigma2
 Kernel: kernel_m1
 Kernel size: 6715392 (6.40 Mb) (komprimiert)
 Image size: 64413696 (61.43 Mb) (komprimiert)

new kernel description does not contain ULK anymore! therefor MAT means this is an old kernel!!

STOP FLASHING YOUR AZBOX WITH THIS VERSION!!!!

- - - Aktualisiert - - -

stupid me - did not remove a debugging line (changing the kernel description) - had this for testing purposes...
SORRY GUYS - build the new versions now - PLEASE DELETE THE 2.4.0!!!!

[morly]

OK - thanks once more arci. I thought I have checked everything before I released the new version and forgot this stupid one line of source code.
I hope no one destroyed the box and to fixed it soon enough...
MAT 2.4.1 works for the azbox as expected

OK - hab vorm Release vergessen eine Zeile Code zu entfernen - somit wurde die Kernelversion bei der azbox falsch gelesen und das Booten nach Flashen war nicht mehr möglich.
MAT 2.4.1 fixt den Blödsinn.
Ich hoffe der Fix kam früh genug und niemand hat ein gröberes Problem

[arci]

It seems that we have warned in time ... no one complain !!!

They ask me when they can get the new version ... but before ... I will test it by myself and then make public on our board !!!

For the moment good job ... when it will finish road test ... you can also think about managing the original OPENSAT FW in FW4USB modality ... with kexec vmlinux boot ... and if you want also for simple reverting to OpenSat FW on DOM !!!

Ciao ...

[morly]

New version for all os comes tomorrow during daytime...
Test it and afterwards we'll discuss further improvements

[arci]

Ok ...

From series ... tomorrow is another day !!!

Ciao ...

[macmanolo]

Morly, es gebt leute die keine verbindung zun reciber bekommen, es werd immer mit einen timeout geanworted, egal ob es Linux64 oder Windows, komischeweise der selbe rechner verbindet zum beispielt mit einen vu zero mit image von Drosat4.4 geths, dan verbindung getrent neuer verbindung mit vu duo-2 mit openspa3.2.1 un dan keine verbindung - timeout.

Bei morser mit Linux64 auch keine verbindung zu AzBox Me, eine idee??

mfg