Same here...Quote:
Originally Posted by naveh
Printable View
Same here...Quote:
Originally Posted by naveh
surely ip channels have got nothing to do with E2
There are 2 different situations:Quote:
Originally Posted by buyukbang
i) in the "hang" after the sleep the remote controller responds and I can navigate in the several modes (TV, youtube) but none of these modes works, the screen is black and only the navigation bar appears. I have to make a reboot for the sstem to work again. After 3-4 sleeps the same problem appears again.
ii) in the "hang", when watching sat tv, the box freezes. I don't remember if I can navigate in the several modes (I can't test it now), but the only solution is to restart the box and for the restart I use the remote command.
For the others with the same problems, do you Elite, or this problems are also observed with Preemum and Premium+?
Perhaps some hardware differences (between Elite and the other models) can explain the different behaviors...
IPTV channels don't work for me when I remove the http_streams from DISK2... another difference...
and some strange people here telling me that I am the only one that have these problems.Quote:
Originally Posted by fcis7000e+
and for all the people that are waiting for E2, keep dreaming !!!!
let the busturds for the beginning give us a good E1 ****ware.
Just small update from me,
I got OSD on screen from E2(startup -> language select) , so now for shure I know my low level EM8634 FB (with GFX acceleration) driver is working.
Thank you for the small update. Is this with the current, or now kernel? With glibc or uclibc?Quote:
Originally Posted by The_Ripper
Did you write the driver yourself for the framebuffer?
Do you have any idea regards directfb and hdmi? Is it already working?
Thnx,
Tommy
Quote:
Originally Posted by The_Ripper
I think it is just a matter of time before this box is blown wide open:respect-067:
Regards
A
@sattommy
Main rootfs is over glibc 2.7, bash 4.0v , busybox 1.16.1v, kernel 2.6.22.19-19. Uclibc is there too , but just for one program from MRUA, it's for video signal activation (analog/digital), I tried to put down activation in kernel driver but it will take to much long to convert because all code is coded for user space not for kernel space(maybe someone else will do that).Quote:
Thank you for the small update. Is this with the current, or now kernel? With glibc or uclibc?
E2 and other library files it use are on USB stick right now,but I hope in near future it will go on DOM (/MMP)
Yes.Quote:
Did you write the driver yourself for the framebuffer?
I dont know what happened to that or it will be released ...Quote:
Do you have any idea regards directfb and hdmi? Is it already working?
Does hdmi works as well? Would thid imply that we can still use the sigma video players?Quote:
Originally Posted by The_Ripper
That would be great, however i don't think really neccesarry.Quote:
Originally Posted by The_Ripper
Thank you for writing the driver, but this still means tuner drivers / dvbapi needs to be written right?Quote:
Originally Posted by The_Ripper
Overall thank you very much for the effort you put into the azbox
Good news. Maybe we can work together. At the moment I'm still not able to write pm's and I don't want posting around to get the needed amount.
I'm able to boot from internat HDD and this enought for the moment. Makeing a flashversion can wait.
Go on with your good work.
@sattommy
I will try HDMI too, I was occupied with GFX acceleration in driver and not on trying all video signal outsQuote:
Does hdmi works as well?
Yes if you recompile source code to work over libc or to point to uclibc libs. If you ask me this ?Quote:
Would thid imply that we can still use the sigma video players?
Yes, plus remote, VFD, etc ...Quote:
Thank you for writing the driver, but this till means, tuner drivers / dvbapi needs to be written right?
@4@@@@
Can you write linux kernel drivers ?
Maybe you can start writing remote driver or anything else ?
Some thoughts on this ?
No - I have some ideas - please send me a pm.
EDIT: **** I need 15 posts - what should this be. Are you able to post me an alternate email address?
@The_Ripper: I'm not able to post PN until I have 15 posts. Please send me via PN an alternate address. I will tell you my solution.
again e2 subject was started :) is there anyone who believe this?
there is a lot of technical terms no more .....
ohhhh not again.
someone here wants us to keep the box, and hopes that we don't sell it of eee****.
@Naveh:
Why writing this here? There are two options
1. You own a box and you are happy with it or interessed in alternate firmware.
2. You think the box is a bad solution; so sell it.
In both cases it is not needed to post stuff like you do.
Thanks.
@DeformE
Heheh, while we wait for other thing, you know what ;)
@naveh
Pls dont compare me with other members and their posts, I am not liar!
And I said, just OSD/graphic on screen,no other drivers/no functions !
I dont work in OPENSAT nor they are paying me something , so I dont give the f**k what you will do with receiver!
Please sell your box and leave us alone!
@The_Ripper - one post and I'm able to PN.
Sorry guy's one more post and I'll be quiet for a while.
@The_Ripper:
Well done, it's quite some progress. As you wrote, it's just a tiny step, no drivers etc, but on a personal/hobby level, it's quite an achievement!
:-)
what does this have to do with Enigma 2 - OSD Graphic on screen?Quote:
Originally Posted by The_Ripper
@naveh
Nothing at all, forget that I wrote something today ...
I will...
Bye.
Please ignore the likes of Naveh, People who have nothing postive to say or offer but just post to criticise are worthless to the sat community.Quote:
Originally Posted by The_Ripper
There are alot of Azbox users who are interested in your progress so please keep us informed. I always look forward to your updates. :respect-054:
good job ripper.
The_Ripper
thanks for everything you do.
greetings from Spain ( cadiz )
Thanx ripper for your hard work.Although i dont own now an azbox as i sold it ,if your work bring results and have a nice and stable firmware not like the ones provided by opensat ,i will buy azbox again
Yes thank you ripper for your work and please go on.
any chance of a alpha release or screenies mate.
cheers :king-042:
sorry meant to thank the ripper for all his hard work i didnt mean to click the thanks button on auldy's post
This one quite very stopped?
To seeing if soon we have good news, which already it touches not?
Regards
yes, the_ripper can u post some screens?
just out of curiosity
Oh come on. Even though I think it's a good achievement to get the OSD on screen, it's not really worth screenshots, is it?
You know what the OSD looks like.
For now I dont work anymore till I got some infos and help. I can upload here vmlinux.bin file(with kernel + rootfs over libc) so everyone who has rs232 cable can try OR I CAN SHOW YOU HOW TO CHANGE XENV SETTING IN FLASH MEMORY SO ON NEXT REBOOT YOU WILL BOOTING FROM TFTP SERVER THIS FILE, BUT IF IT FAILED TO BOOT YOU ARE STUCK WITHOUT RS232 CABLE TO CORRECT IT!
So people what have you decide ?
Anyone here with free time and knowledge in C++/Python to start patching E2 and Python code to adjust for Azbox receiver ?
The_Ripper FTW! :)
bring it on.
i for example can't help, don't have the knowledge but i bet there's a bunch of interested people and who still like this box and have hopes.
lets hope so.
the ripper upload all u can please, i think that there will be a lot of people interested and willing to help you.
btw, what kind of help do u need, and what are your goals now, next step?
btw, is this the time to make a svn or gitserver so all can give a hand, or too soon?
Before anyone starts to work. Do you think it is possible to get dvbapi working? Otherwise it is probably no use to start modifying e2.Quote:
Originally Posted by The_Ripper
Yes it is posible to write down kernel drivers, I menage like I said to get fully working FB with Sigma GFX acceleration.
But Azbox as you all know doesnt have nothing from drivers we can use in E2 (nothing at all), so all drivers must be coded to acomplish what E2 wants or to mimic in closest way like they do in SH4 based receivers, but then E2/Python code need to be patched.
So I will try till end of this day to write down how you all can boot my vmlinux.bin and then put back values in XENV flash part so you can back to original FW loading.
great work ripper and a big step forward.but i am afraid that closedsat must help also.they dont have the needed drivers,they cant code them .....at least they should give free boxes to developers to work on this.i am afraid that not a lot of people here are ready to test this.so closedsat u should show for first time that you care about your customers and not for their money and help on development. but i am again afraid that closedsat cares only for customers euros
from what we learn (specially me unfortunately) we can't wait for them to provide anything at all ...
Ok guys, as I promise,here is the links
hxxp://www.megaupload.com/?d=S9GC4UQR (vmlinux.bin)
hxxp://www.megaupload.com/?d=KZBRMLEK (files and modules)
hxxp://www.megaupload.com/?d=R88HACTT (MMP uclibc)
Ok first I use tftpd32 server for Windows,link to download hxxp://tftpd32.jounin.net/.
I put vmlinux.bin(from first link) file where is main tftp exe file is, and after start of the program just change "Current Directory" to point
there if allready not and change "Server interface" to your PC IP Address(mine is 192.168.1.3) and let it stay running.
Thats all to setup tftp on Windows.
Next, boot up receiver and transfer all files from second link in
/MMP/modules/2.6.22/ (make 2.6.22 folder)
chmod 755 all files
Pls make shure you have this files on DISK1 because I am using this files.
/DISK1/.passwd
/DISK1/.shadow
Next, download MMP uClibc tmp folder from third link.You must unpack it on receiver because of soft symlinks.
After extract you should have /MMP/tmp folder with uClibc based librarys files.We need uCLibc because of setting up video signal out with
small MRUA app.
SO, after this go into telnet console and write this command (ELITE MODEL tested!!!!!)
setxenv -f /dev/mtdblock0
it should list all XENV settings in flash. Our main interest for now is in 4 settings,
y.ipaddr,y.subnetmask,y.gateway and y.start,
unfortunaly YAMON boot loader doesnt have dhcp so you must manualy add all IP based datas.Pls be cerful with this, if you are wrong with this settings you will not be able to boot and no other way to repair
it, then to make your self rs232 cable like "telesat" user explain here.
So before you change pls write down default values for this 4 settings but main value y.start IS MUST so you can change it back after you want to load standard FW!!!!
Here is my values for IP datas. My router always give my Azbox receiver this IP address 192.168.1.5, Subnet mask for this range is 255.255.255.0 and my router gateway is 192.168.1.1.
So this is way I will change this values for mine IP settings
(It takes few seconds to change value)
setxenv -f /dev/mtdblock0 -k y.ipaddr -v "192.168.1.5"
setxenv -f /dev/mtdblock0 -k y.subnetmask -v "255.255.255.0"
setxenv -f /dev/mtdblock0 -k y.gateway -v "192.168.1.1"
-------------------------------
Next is to change boot up command for Yamon, default value on my receiver is
y.start on my receiver is "xrpc 0xac080090; load zbf 0xb3000000; go"
so pls write it down somewhere.
So, next step is to change startup boot command (y.start).
PLEASE CHANGE IP ADDRESS FOR YOUR TFTP SERVER, MINE TFTP SERVER PROGRAM IS ON PC(WINDOWS) WITH 192.168.1.3 IP ADDRESS!!!!!!!!!!!!!!!!!!!!!!!!!!
setxenv -f /dev/mtdblock0 -k y.start -v "net init; net initpci; net up; load -b tftp://192.168.1.3/vmlinux.bin 0***020000; go"
hmm 0x 9 0 0 2 0 0 0 0 ,just put it together instead of 0***020000 and without spaces!!!
after you change all just in case ./setxenv -f /dev/mtdblock0 check again if your values are okey,plus y.XXXX commands maybe some letter is missing while you type it!!!!!
It's just left to boot it, so type reboot in console and hope it will boot ;)
to go back after boot to standard firmware, go to /MMP/modules/2.6.22 , where setxenv program is and put back OLD y.start command value and just reboot it
./setxenv -f /dev/mtdblock0 -k y.start -v "xrpc 0xac080090; load zbf 0xb3000000; go"
-----------------------------------------------------------
If all goes well you should be able to telnet/ftp to Azbox receiver.If NO, sorry I dont have solution, you will need rs232 cable to fix it,
But if all okey, telnet and go to /MMP/modules/2.6.22 folder and use set_outport prog to activate video out signal, I just tested analog out
./set_outport -analog -f PAL_BG
for digital maybe this way
./set_outports -digital -f HDMI_1080i59 -dvi_hdmi siI9030 -hdmi2c 2
If anyone managed to come till here I will explain how to load FB driver, it's still in working process and it has fixed screen resolution 720x576, and maybe
letter upload E2 files but it needs alot of patching and fixing plus writing next driver(s).