OJO CON EL MAT 2.4 NO CAMBIAR EL KERNEL EN LOS AZBOX

[macmanolo]

De momento NO CAMBIAR EL KERNEL EN LOS AZBOX, hay que desmarcar la casilla del kernel, ya que al parecer el reconocimiento del mismo esta mal:

Hola chicos,
Se nos colo un maldito Bug - Porfavor borrar el MAT 2.4 - si flasheais con el un AzBox el receptor no volverá a arrancar!!!
Ya se han borrado los enlaces de descarga - y el fallo ya está corregido, tan pronto como este se pondrá una nueva versión 2.4.1
PERDONEN LAS MOLESTIAS....

Hi Leute,
böser Bug - bitte MAT 2.4 löschen - wenn ihr damit die AzBox flasht bootet die Box nicht mehr!!!
Hab den Download bereits entfernt - Fehler ist behoben, werde eine 2.4.1 hochladen!

Hi guys,
terrible bug - please delete MAT 2.4 - flashing your AzBox will brick your box (not booting anymore)
2.4.1 will fix this problem!

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 ([email protected]) (gcc version 4.9.1 (GCC) ) #1 PREEMPT Thu Mar 5 02:59:52 CET 2015

Ciao ...