Enigma 2 by The_ripper - TEST -

[The_Ripper]

@all
For all people who got stuck just in BOOTING in vfd display, box isnt dead, but to back in original state there is 2 more posible ways:
1. Is serial cable and hardware interface to hook up to receiver board, user "telesat" put schematic diagram here on forum, just search it ...
2. Is to remove DOM from receiver/board and hook it up to external IDE rack. "telesat" is writing right now some tutorial because power connection isnt the same, so it will need some explanation what to do about that, plus he will upload what to put in DOM and with what partition app. So pls stay tuned .

If this 2 posibility is hard for someone, then unfortunately there is no other way, I can just apologize to everyone and to ashure that their receiver isnt damaged in terms of hardware.

---------
I added now in new kernel build initramfs root filesystem, so if needed rescue shell it will enable ftp/telnet and show you your IP address from dhcp app on VFD so backup original FW will not be the problem any more.

[wullieb25]

first of all a big thanks to the ripper and all the team who are working on this and bringing new life to the azbox. respect to you guys.

i installed the image and its great but i have no network access to the box to put the origional firmware back on. i have tried everything but i cant connect or even see the box over my network.

at the moment i cant do anything with it.

any help from anyone on this matter would be very much apprichiated

thanks in advance

[sattommy]

@all
For all people who got stuck just in BOOTING in vfd display, box isnt dead, but to back in original state there is 2 more posible ways:
1. Is serial cable and hardware interface to hook up to receiver board, user "telesat" put schematic diagram here on forum, just search it ...
2. Is to remove DOM from receiver/board and hook it up to external IDE rack. "telesat" is writing right now some tutorial because power connection isnt the same, so it will need some explanation what to do about that, plus he will upload what to put in DOM and with what partition app. So pls stay tuned .

If this 2 posibility is hard for someone, then unfortunately there is no other way, I can just apologize to everyone and to ashure that their receiver isnt damaged in terms of hardware.

---------
I added now in new kernel build initramfs root filesystem, so if needed rescue shell it will enable ftp/telnet and show you your IP address from dhcp app on VFD so backup original FW will not be the problem any more.

Hello The_Ripper,

Could you maybe provide us with some steps howto compile mrua with gcc 4.3, so the compiled executables will run on your kernel? This way somepeople could work on media stuff.

[hfmls]

@all
For all people who got stuck just in BOOTING in vfd display, box isnt dead, but to back in original state there is 2 more posible ways:
1. Is serial cable and hardware interface to hook up to receiver board, user "telesat" put schematic diagram here on forum, just search it ...
2. Is to remove DOM from receiver/board and hook it up to external IDE rack. "telesat" is writing right now some tutorial because power connection isnt the same, so it will need some explanation what to do about that, plus he will upload what to put in DOM and with what partition app. So pls stay tuned .

If this 2 posibility is hard for someone, then unfortunately there is no other way, I can just apologize to everyone and to ashure that their receiver isnt damaged in terms of hardware.

---------
I added now in new kernel build initramfs root filesystem, so if needed rescue shell it will enable ftp/telnet and show you your IP address from dhcp app on VFD so backup original FW will not be the problem any more.

thank you very much for the backup thing
when will u release it?
i got a question mower, what's your next step, or what do u expect from users/coders before u release sourcecode/svn ?

thank you so much again.

[single]

TO Coders:

To try to made drives can some of the coders compile I2CTools to see what kind of chips/ic's we have on this kernel?

You can find ic2 tools here:w3w.lm-sensors.org/wiki/I2CTools

With this tool we can have some info to see if is possible work on kernel drives.

CU

@sattommy

Did you try media programs compile on this kernel, like the one you have on NAS "boxes"?

CU

@The_Ripper
"
I added now in new kernel build initramfs root filesystem, so if needed rescue shell it will enable ftp/telnet and show you your IP address from dhcp app on VFD so backup original FW will not be the problem any more."

On Busybox?

[single]

Kernel used in this release of E2 ( 2.6.22-19 patched by Sigma ) :

http://support.wdc.com/product/download.asp?groupid=1003&sid=120&lang=en

Here is make file for OE od DM 800 , 2 small diff files for sources which have to be changed ( for FB , and for priority of process for Kernel 2.6.22-19 ) and .config file for Kernel 2.6.22-19 .

Makefile-opendreambox-1.5 ( for whole image , crosscompiler, and all lib's etc. )

All files provided by the_ripper, thanks goes to him.

What version of GPL Code?

EDIT:
Back to do one more question...

Because of kernel can't see usb stick's....

If usb modules are incompatibility with kernel, then they can't be loaded, then if you compile new usb-storage ...bla bla for this kernel how usb drive can be compatibility with this new kernel?....

Modules can be linked with kernel (M) or can not, what is the best choise?...



WDTV_Live_GPL_code_package_1.0?.? ?.zip

[tonybam]

@all
For all people who got stuck just in BOOTING in vfd display, box isnt dead, but to back in original state there is 2 more posible ways:
1. Is serial cable and hardware interface to hook up to receiver board, user "telesat" put schematic diagram here on forum, just search it ...
2. Is to remove DOM from receiver/board and hook it up to external IDE rack. "telesat" is writing right now some tutorial because power connection isnt the same, so it will need some explanation what to do about that, plus he will upload what to put in DOM and with what partition app. So pls stay tuned .

If this 2 posibility is hard for someone, then unfortunately there is no other way, I can just apologize to everyone and to ashure that their receiver isnt damaged in terms of hardware.

---------
I added now in new kernel build initramfs root filesystem, so if needed rescue shell it will enable ftp/telnet and show you your IP address from dhcp app on VFD so backup original FW will not be the problem any more.

Salam
Thanks for your extreme effort to help those who stuck in booting station
is this the schem of serial interface if that what is file we would sent and how?


https://www.satpimps.co.uk/showthrea...389#post728389

[The_Ripper]

@single
Yes it works over busybox ...

@sattommy
I use mrua_SMP8634_2.8.5.1-celrun-08062009-2.6.15K_facsprod_legacy_dev.mips, this MRUA packet, but now for compilation part , you will need gcc over glibc and to add this switches
L=/MMP/tmp -> for example
gcc ********** -Wl,--dynamic-linker,$L/ld-uClibc.so.0 -Wl,-rpath-link,$L/
With this you will tell what LD library to use and on start where to search for libs
So all MRUA uClibc libs/main uCLibc libs must be in that paths.

This is how should look after for example you open binary in IdaPro

.init:00401208  # Format      : ELF (Executable)
.init:00401208  # Imagebase   : 400000
.init:00401208  # Interpreter '/MMP/tmp/ld-uClibc-0.9.27.so'
.init:00401208  # Needed Library 'librmcw.so'
.init:00401208  # Needed Library 'librmcore.so'
.init:00401208  # Needed Library 'libruahdmi.so'
.init:00401208  # Needed Library 'librua.so'
.init:00401208  # Needed Library 'libllad.so'
.init:00401208  # Needed Library 'librmhdmi.so'
.init:00401208  # Needed Library 'librmedid.so'
.init:00401208  # Needed Library 'librmi2c.so'
.init:00401208  # Needed Library 'libruai2c.so'
.init:00401208  # Needed Library 'librmsha1.so'
.init:00401208  # Needed Library 'librmcec.so'
.init:00401208  # Needed Library 'libstdc++.so.6'
.init:00401208  # Needed Library 'libm.so.0'
.init:00401208  # Needed Library 'libgcc_s.so.1'
.init:00401208  # Needed Library 'libc.so.0'
.init:00401208  # Library Search Path '/MMP/tmp'

EDIT: Not gcc over glibc, it's gcc over uClibc, sorry for confuse ...

[The_Ripper]

@tonybam
Yes that's it, that post show some YAMON commands too,after you break boot and enter YAMON.


You have on first post "backup_kernel" file


After you set all networks data (for example)
setxenv y.gateway "192.168.1.1"
setxenv y.subnetmask "255.255.255.0"
setxenv y.ipaddr "192.168.1.5"
net up
net init
/* You will need working tftp server on PC machine */
load -b tftp://192.168.1.3/backup_kernel 0xb0100000
pflash write -f 0x80000 0xb0100000 0x680000
After that you should see Erasing and Writing, it will take a while, but after it finish you just reboot and you are back with original kernel and you can continue to upgrade FW over USB ....

[aspava]

ma ku..c bi ovi nesta sami napravili da nije nasih mozgova.svaka vam cast,nije da mi je do E2,nego mi je drago da ste uspjeli:respect-067:

[4@@@@]

@The_Ripper: Excelleent work.
The git is ready to use for some devs - you know where to have a look.
If all works well we will open it ro for the public.

[sattommy]

@single
Yes it works over busybox ...

@sattommy
I use mrua_SMP8634_2.8.5.1-celrun-08062009-2.6.15K_facsprod_legacy_dev.mips, this MRUA packet, but now for compilation part , you will need gcc over glibc and to add this switches
L=/MMP/tmp -> for example
gcc ********** -Wl,--dynamic-linker,$L/ld-uClibc.so.0 -Wl,-rpath-link,$L/
With this you will tell what LD library to use and on start where to search for libs
So all MRUA uClibc libs/main uCLibc libs must be in that paths.

This is how should look after for example you open binary in IdaPro

.init:00401208  # Format      : ELF (Executable)
.init:00401208  # Imagebase   : 400000
.init:00401208  # Interpreter '/MMP/tmp/ld-uClibc-0.9.27.so'
.init:00401208  # Needed Library 'librmcw.so'
.init:00401208  # Needed Library 'librmcore.so'
.init:00401208  # Needed Library 'libruahdmi.so'
.init:00401208  # Needed Library 'librua.so'
.init:00401208  # Needed Library 'libllad.so'
.init:00401208  # Needed Library 'librmhdmi.so'
.init:00401208  # Needed Library 'librmedid.so'
.init:00401208  # Needed Library 'librmi2c.so'
.init:00401208  # Needed Library 'libruai2c.so'
.init:00401208  # Needed Library 'librmsha1.so'
.init:00401208  # Needed Library 'librmcec.so'
.init:00401208  # Needed Library 'libstdc++.so.6'
.init:00401208  # Needed Library 'libm.so.0'
.init:00401208  # Needed Library 'libgcc_s.so.1'
.init:00401208  # Needed Library 'libc.so.0'
.init:00401208  # Library Search Path '/MMP/tmp'

EDIT: Not gcc over glibc, it's gcc over uClibc, sorry for confuse ...

Can I use the debian install you explained earlier? Where do I get the uclibc files, can i get them from you enigma2 image. Where do i put the dynamic linker stuff?

Thnx for the hassle

[4@@@@]

@The_Ripper and Mickey_Sa: Please post the unpacked software to install on the internal HDD with the vmlinux.bin or compile the kernel with nfs to test over nfs.

[The_Ripper]

@sattommy
Find and download smp86xx toolchain and MRUA I mentioned,just extract it and export toolchain environment script "toolchain-path.env" and you have ready uclibc compiler.
For where to hold libs files on receiver DOM it's up to you, when compiling ,with -L switch you will need to point location to MRUA libs , they are in "extracted folder/lib" of the MRUA packet.


@4@@@@
I will see to upload somewhere just vmlinux.bin ....

[4@@@@]

@The_Ripper. Thanx - the files are already on my nfs mount. So please compile nfs support in the kernel.

[tonybam]

@tonybam
Yes that's it, that post show some YAMON commands too,after you break boot and enter YAMON.


You have on first post "backup_kernel" file


After you set all networks data (for example)
setxenv y.gateway "192.168.1.1"
setxenv y.subnetmask "255.255.255.0"
setxenv y.ipaddr "192.168.1.5"
net up
net init
/* You will need working tftp server on PC machine */
load -b tftp://192.168.1.3/backup_kernel 0xb0100000
pflash write -f 0x80000 0xb0100000 0x680000
After that you should see Erasing and Writing, it will take a while, but after it finish you just reboot and you are back with original kernel and you can continue to upgrade FW over USB ....

Hi
can this procedure run in windows or it should be in linux, which nightmare for my self as i am only windows user.
i will try in the week-end to try this. and will post my result.

[tx0]

I've missed all the fun. and now "The uploader has removed this file from the server." How was that? HD support? recording? everything was OK? :(

[digihoe]

I've missed all the fun. and now "The uploader has removed this file from the server." How was that? HD support? recording? everything was OK? :(

What file? All files are uploaded in this thread.

[single]

What version of GPL Code?

EDIT:
Back to do one more question...

Because of kernel can't see usb stick's....

If usb modules are incompatibility with kernel, then they can't be loaded, then if you compile new usb-storage ...bla bla for this kernel how usb drive can be compatibility with this new kernel?....

Modules can be linked with kernel (M) or can not, what is the best choise?...



WDTV_Live_GPL_code_package_1.0?.? ?.zip

Ok looks like is hard to tell things...

And all you now I don't have this box... rrrrrrrrrr

Anyway i will make my posts because Helder is a good friend...

On filesystem i have from Opensat, i don't extract this one yeat, I saw the linux used is 2.6.15 here we can find the modules:

Ralink 3070 chipset r**070sta.ko (wireless) - this can be compiled on new kernel because of android port.

RaLink RT2561/RT61 PCI Wireless Card rt61.ko (wireless) - this can be compiled on new kernel because of android port.

sckernel.ko - is smartcard used by Opensat, then have no use here...

em8xxx.ko - processor (no use have no DirectFB) is need a em8xxxfb.ko.

sr_mod.ko - for RHEL 6 to see CD-ROM devices

fuse.ko - Fuse

ftdi_sio.ko - Linux FTDI USB

cdrom.ko - Usb Cdrom (in this stb)

usbserial.ko -USB

llad.ko - llad kernel module for standalone configuration (can someone type modinfo llad.ko on shell and put here output???)

....

What is missing here?

azbox_frontend.ko (Frontend device)

azbox_dvb-core.ko (DVB)

azbox_dvbs2tuner.ko (Tuner for Sat)

azbox_dvbts2.ko (Tuner for TDT).

azbox_control.ko (remote control).

azbox_rf.ko (RF).

azbox_frontpanel.ko (Frontpanel).

azbox_ic2.ko (ic2). (For example: PI5V330 Low ON-Resistance Wideband/Video Quad 2-Channel MUX/DEMUX or MAX11506, MAX11507 Low-Cost, 6-Channel SD Plus HD/SD Selectable or The TVP5150 device is an ultralow-power video decoder for NTSC and PAL video signals...)

Note: TVP5150 can be find on android.


Well, this is missing, correct?...

(I my forget something...)

Somewhere we have too:
em8xxxoss.ko
em8xxxalsa.ko

[oguzhak]

my azbox's problem continous. the box shows BOOTING and doesn't go any further. Also it doesn't detect the stick, which would be useless anyway.
tell me please how this problem will be solved. Could you pls explain