And what about their poor hardware that can't support twin tuner functionality? Also a poor cpu that can't handle heavy tasks therefore the network limitations? And what about their poor support? It took you almost two years to realise?Originally Posted by chrissat
I already mentioned the box not living up to it's promises i.eTwin tuner and network limitations.
Poor support I've mentioned with the firmware.
I haven't had my box for two years.
But these aside, the box gives me HD and good picture quality.
I also use it more for a media box and it works great for that.
My azbox has replaced three other pieces of equipment I had. A media player, a satellite box and a dvd recorder. That's what I bought it for and in the main it does a good job.
But there are areas where it could be improved and its here I feel let down that it hasn't developed like I thought it would.
But this thread is not about hwat opensat can or cannot do. Development of two things were followed here. Directfb and Enigma2.
Enigma2 seems either to be developped secretly, or not at all.
Directfb is claimed to be working by Telesat, which I think is a developper himself. So my question is wether directfb is finished, only private, or will see the surface soon.
Thnx
chrissat
But if anything you have said has nothing to do with enigma 2,as you posted,why are you posting in the enigma 2 thread?
What is relevant to the subject how you use the box for?
You should have opened a new thread about the poor firmware support and broken promises,and as a fact,there are many of those your rant would fit perfectly,but not here.
What I originally said was about enigma 2.
Just that a small proportion of my post was taken out of context and I clarified myself.
But Im more than happy to get back on topic.
bla bla bla bla, firm ko, emus ko, cardreader ko, lan speed ko, e2 ko, az ko, opensat ko. bla bla bla
Mayo 2010 tic tac tic tac
We must respect those who work for others :respect-055:
I told you that raskino is a simple user that collects information on the forums and not a developer but you have believed.:cuss:
We all hope that "the Ripper" and other teams develop enigma2 on AZBox.
**** liars, **** opensat. Shame on you raskino !!!:18:
Here are more Posts about that E2 is impossible than Posts about E2.
This is a Discussions Thread about E2 and news about the Work.
Maybe you "dont believer" open yourself a new thread for these posts.
If I were a programmer and I have to read those posts, I would dont like to share my work for such a community.
Enigma on Azbox is only a dream i got my hands on a Sigma manual showing the way they new proccessors work and after carefully reading all i found out that is impossible to make enigma native boot on azbox couse the microprocessor is closed key protected and bios checks all firmware files if they comply to original ones. Keys for sigma proccessors will never be released couse it's their main feature against piracy and ace in the sleewe. only way to have enigma on azbox is the hybrid way this means original FW with Enigma TV API, wich for me is even better then enigma standalone. here is the link to the manual i'we read, read it carefully before posting more nonsense.
http://www.multiupload.com/4MFCLXB5OE
That's what I said already before. How can you develop something if Opensat doesn't develop and doesn't own anything from the hardware.
It's impossible and they are not devs, they are reseller.
R&D is done in Asia, not by Opensat.
If they need coder for quick fixes they fly them in from Korea.
Luckily this slideshow slightly differ from what we have in reality. :respect-050:
Interesting - all seems to have a 'glass bowl'.
We now try to make it by our own.
"fread tftp://" it is possible to load a unsigend kernel and this one is also possible to be flashed but you have to modify the yamon and add a script with setxenv that the raw kernel is loaded to the ram
First of all we can use this
setxenv a.linux_cmd "console=ttyS0 root=/dev/nfs nfsroot=(nfs_server_ip):/some/dir/nfsroot ip=(my_ip_addr):(server_ip_addr): (gateway):(netmask):(hostname)"
the start. No signing is needed.
If wee have a running image with that, we can go futher to get the rest running.
I have no idea if we will get to a working E2. neutrino or VDR but we are working on it. First try will be VDR.
We do not fake any Youtube - we just try to get it working.
So stop with negative stuff. If we see some light in the tube I will tell it to you.
Maybe we will rest with a Linux system on the AZBox and not more - but we will see.
The hope is dying at last.
Last edited by 4@@@@; 08-05-2010 at 09:50 PM.
Can you tell me more about VDR please?
Thanks for your efforts, it's what is so special about the satellite community. It's people coming together and trying.
Success or failure doesn't matter, it's all about the journey.
Recently there's been a more negative influence, a move towards "this box is better" "your box is crap" etc... Such posts do nothing for the community.
It's not about better boxes, it's about community. Learning from each other, learning from other boxes and trying to make the satellite experience better for us all.
In that I thank you for your work, because people like you keep the satellite community alive. :respect-023:
what do you mean "differ" ?
the actual keys are smaller, filled with zeroes, can be cracked easily, and as was said before the booting procedure can be changed.. the problem is nobody want to spend their time to support this box. opensat don't want to hire experienced programmers and there are no enthusiasts cause its easy to buy dm or clone and forget problems. Even if opensat will hire programmers it would be a such PITA to fix someone's source code.. sorry for these guys.. I'm not promoting dm and wish all the best for this box but the way opensat "support" fw development leads to nowhere. The best what they can do now is to release all source code they done so far. They have a huge mess in firmware features - that should be sorted out.
HOW IS THE ISSUE?
anyway for failure, there is no official signature of azbox these are holidays.
greetings from Barbate (Cádiz) Spain
Is there a AZbox yamon expert around?
How is the boot process made?
Which environment stuff is used/needed (setenv setxenv)
- I don't want to always set this nfs stuff by hand
- Where is the kernel (which mtd device and how could it be extracted)? Or does I have to take it out of the loader.bin with offset of 0x80000?
Any help which saves me time appreciated.
Well I know there's rtfm, but time is money
The kernel is on the fourth partition of the NOR flash.
Here you get my post about the flash partitions distibution.
cat /proc/mtd
dev: size erasesize name
mtd0: 00800000 00010000 "CS2: Physically mapped flash"
mtd1: 00020000 00010000 "CS2-Part1"
mtd2: 00020000 00010000 "CS2-Part2"
mtd3: 00040000 00010000 "CS2-Par**"
mtd4: 00680000 00010000 "CS2-Part4"
mtd5: 00100000 00010000 "CS2-Part5"
and the 5 partition is of jffs2 filesystem and actually mounted on DISK1:
$ mount|grep mtdblock5
/dev/mtdblock5 on /DISK1 type jffs2 (ro,noatime)
something new?
regards
yes, interesting news: I finally sold my AZ BOX last week :-D sorry for OT but this box was the worstest buy in my life, poor guy who wanted it! Good luck guys, this was my first and definetly last post after months of believes. Bye all, bye crappy AZ BOX
Posting Permissions
Reply With Quote
Bookmarks