It's slow going on this thread at the moment.
Any body know what the team are working on?
Sound bug? SVN? First beta?
Printable View
It's slow going on this thread at the moment.
Any body know what the team are working on?
Sound bug? SVN? First beta?
the devil never sleeps... they are working, safe.
I think this is the answer to your question, I presume when all is done there will be a new release.
Just wondering how many are stuck on the first test version of E2 because they don't get a VFD IP address on reboot...it's not just me is it?
If your were and you sorted it please post.
Thanks
James.
ok for a start switch box off from power and also network plug wait 5 minutes then restart box you should be able to see ip address in vft now!!
Use LAN (WiFi will not work at all) cable connected to a DHCP (computer or router) server, restart the box with the USB containing patch.bin. IP should show, if nothing has went bad.
Be sure to use a crossover cable if you connect to a computer and that DHCP really is working.
You can also try to get the box ip from the router logs,because if the box is connected to the lan,the router should have the box IP showing in the logs.
And the MAC too.
This happen if you have a router to split your network.
Or you can use DCC (dreambox control center) that has a function to search for all IP's present in the lan.
You surely can get the box IP by elimination (by knowing the IP of your connected devices)
btw. for the ones having problems with wlan ...
read the README included in wlan.zip also and edit rt61sta.dat to your needs as described in the file , reupload the file and restart your ra0.
The people with the VFD, count yourselves lucky! I have an Ultra with no VFD so had to guess the IP. hehe :)
That's because you didn't know about DCC.(and others)
The IP doesn;t need to be "guessed" ,only need to be found,and DCC can do that for you in a minute.
How could this help?
If your AzBox doesn't have an IP, where DCC/Angry IP Scanner will point?
Better you configure your DHCP server properly instead waste your time with all this workarounds.
Thanks for your advice M8...I think something has gone bad in my case, I never used WiFi always cable connected to a router, and I have crossover cable from my lappy to my router and the router is connected to the box, I can get the Azbox's IP address from DCC and can connect with every application except for Azup, I can even go into my router's attached devices and confirm connection and the box's IP address, but when I put the IP address in Azup and try to update I get "you have a new Kernel in your Azbox", but I then get a box saying "no rescue mode" "Put a patch.bin on your USB stick, reboot and try again"
Off and on been messing with this for a few days now and trying various things, but recently I have been getting a mosaic and then after that a green screen when using scart or component cable, I know I am using the correct IP address because I can filezilla, so I think that I need to force the patch somehow or to add something when in filezilla to get the Box to respond to the USB stick. The only other option is to format the DOM but I need an idiots type step by step guide to do this and I can't find one.
Thanks again,
James.
Try usig the other USB port.
What model of Azbox ... Premium or Elite?
Read this chance to recover! HERE
If you have a storage device that is seen, copy the patch.bin (ex. 0.9.5020) on /dev/xxxx and mount the cramfs on it ... and then reload the old kernel (Opensat) ... at new reboot ... you can regain access to USB Upgrade menu, where you can reformat DOM and reinstall what you want ! ;)
Regards
Arci
For my Ultra I just enter in router's web interface and check Ultra assigned IP by DHCP.
No guessing or workaround needings.
Also, as my router's DHCP remember devices by MAC, IP is always the same, using original fw or using E2 firmware.
Anyway, you could also install a bunch of other software to do that same thing. :) User's choice.
I didn't say that use a IP scanner or other tool are the wrong way for Ultra.
I meant that in cases where your box don't get an IP none of this tools should help.
We have recently been very much spoiled by the team it's so quiet, so nice if we had something new for the weekend to test. with all due respect natural
with what they have given us so far.
with best regards:001_005:
Patience.. Have patience. A new firmware will be along soon. :)
jamesjay
Try first to put an older version of the 2nd Enigma
Hello.
azbox Premium all the solutions did not succeeded in installing the wireless on my Give me another way
@ Satommy:
I tried the plugin enigma2-plugin-extensions-****center_experimental-cvs20101025-r0_dm800 and everything works fine.
I can go to the menus and I can select the video. Player opens. But I can not plays back any video. I think the problem is that all videos are *. mp4. A problem of codec?
Hi M8,
That would be impossible I cannot load anything with a USB stick, I have tried to load other versions of E2 but the USB ports are not responding on my box. I know how to use applications for FTP and Telneting but that was for only simple tasks with Opensat stuff, I have no real experience with Dreambox's and real coding.
If it was possible to override the E2 version I have by transfer another version of E2 via filezilla I would, but I don't know where to put the file, or for that matter what Telnet commands I would need to get it going. Having looked at a post that explained how to return to Opensat firmware by using Filezilla and Telnet, the Telnet commands looked very complicated for a novice, and I would probably do more harm than good.
I got this advice from Arcibald.
"If you have a storage device that is seen, copy the patch.bin (ex. 0.9.5020) on /dev/xxxx and mount the cramfs on it ... and then reload the old kernel (Opensat) ... at new reboot ... you can regain access to USB Upgrade menu, where you can reformat DOM and reinstall what you want !"
I can find dev, but don't know what xxxx or mount the cramfs means.
So following these instructions from Slarva,
You can recovery manually to original firmware like this, you must have harddisk inside the box and original patch.bin (copy it with ftp program like FileZilla) in there too:
telnet (use Putty or something else) to box
mkdir /hdb
mount /dev/hdb1 /hdb
dd if=/hdb/patch.bin of=/hdb/patch.cra bs=56 skip=1
then will be the cramfs be mounted whith loop
mkdir /Patch
mount -o loop /hdb/patch.cra /Patch
dd if=/Patch/FLASH/loader.bin skip=512 of=/dev/mtdblock4 bs=1024
reboot box
is not going to go well, I am sure if I had a better knowledge of coding then I could do it but I am not confident so could end up with a completely dead box.
Kind regards
James.
Did my first test with the latest E2 version, but no go.
Sharp tele couldn't find HDMI or SCART at all.
Went back one version to .30 and it worked but no sound at all.
Anyway my disecq was ok (10 lnb on WaveFrontier), scans ok.
Looks very promising.
I'm going to wait for the first Beta release.
Keep up the good work team thank fo so far !!
@jamesjay
Have you tried this... https://www.satpimps.co.uk/showthread.php?t=141544
I think you need Step. 7 onwards if you have read the tutorial, as you can already FTP/Telnet your box?
Step 7
Now let’s go to transfer the necessary files to the box using FTP
To do this, we connect with our favorite FTP client (I use filezilla). You have to enter the IP address we got on previous step. The user is root, and the password is azbox, as usual. Copy files (Files are in the Files folder of this tutorial):
backup_kernel : Copy it to /MMP on the box
update : Copy it to /tmp on the box
Step 8
Return to the putty windows, where it asks login and password.
The user is root, and the password azbox.
Type:
cd /tmp (We move to /tmp directory)
chmod a+x update (We give the file run permission)
./update /MMP/backup_kernel (start restoration)
The process will begin, and will show progress.
When the process completes, the decoder will reboot, and will come to life!
We have 100% operational box with the original firmware!
Now, we can flash the firmware we want. Don’t forget to make a “Format Application Area” to clean up remnants of previous firmware