Enigma 2 RTi core RC1

[mr3p]

As posted by MickeySa:


Code:
What is new :- New Kernel with better stability improvements.- New Overclock driver for SAFE overclocking of Sigma SMP8634 CPU up to 370 MHz . ( Overclocking is done On-Fly with step up size of 10 MHz, and this is VERY SAFE Method which allow You to overclock CPU of Your AzBox up to 370 MHz , if something goes wrong, on reboot there are routines which will reset CPU to default clock, so nothing can happen ).- Fixed A/V Settings, VFD and Standby plugins are separated now.- New Mediaplayer files, so DVD .iso and .ts files are supported now.- Added rescue mode, which allows You to go immidiatelly in Rescue mode from menu.- Overall stability and speed of Enigma 2 is better and improved.
Code:
What is comming in RC2 : - Recording and DVB Subtitles, and other stuff regarding functionality - You can expect RC2 before 31.12 or on New Year eve
Download:


Code:
http://www.azbox-enigma.eu

 

[AcWxRadar]

As posted by MickeySa:


Code:
What is new :- New Kernel with better stability improvements.- New Overclock driver for SAFE overclocking of Sigma SMP8634 CPU up to 370 MHz . ( Overclocking is done On-Fly with step up size of 10 MHz, and this is VERY SAFE Method which allow You to overclock CPU of Your AzBox up to 370 MHz , if something goes wrong, on reboot there are routines which will reset CPU to default clock, so nothing can happen ).- Fixed A/V Settings, VFD and Standby plugins are separated now.- New Mediaplayer files, so DVD .iso and .ts files are supported now.- Added rescue mode, which allows You to go immidiatelly in Rescue mode from menu.- Overall stability and speed of Enigma 2 is better and improved.
Code:
What is comming in RC2 : - Recording and DVB Subtitles, and other stuff regarding functionality - You can expect RC2 before 31.12 or on New Year eve
Download:


Code:
http://www.azbox-enigma.eu

Mr3p,

Thank you for the update. Personally, I am not going to try E2 for a while. I am sure it will be the next step up, but I am going to wait on it to be improved even more. I have no qualms with the last firmware from OpenSat (0.9.5020) and I will just stick with it while I learn some other avenues in detail, first. When I feel perfectly comfortable here, then I can move on to E2.

We should all keep our eyes on this advancement, it will most likely be necessary in the future.

RADAR

 

[mr3p]

Hi RADAR,
I completely understand your reservations about loading E2 as it is still in development. People should not install E2 RC1 and expect that it is ready to replace 5020. Installing E2 at this time really should be for someone who is interested in seeing whats new as there are features in 5020 that don't exist yet. Recording and Hardware Blindscan are two big things that you can't currently do with this release candidate. That being said, there are many things E2 does better than the factory firmware and it is going to be the firmware for the Azbox going forward. After using E2 for a while now, I definitely don't miss the factory firmware and look forward to being able to dump it... which unfortunately can't be done quite yet.

 

[crackt]

mr3p.... do you have any issues with ac3 audio ? with 1.0.3 i could not get audio from any channel with ac3 audio and when attempting to select a different audio stream there were none listed. i dont have time to test it tonight i got super bogged down lately but i sure am interested. thanks.

edit: i tested rc1 and the audio bug remains. tuning to a channel with mpeg audio is fine. tuning to a channel with ac3 audio produces no sound. the sound also fails on the next tune to an mpeg audio channel. a second channel zap is required to produce audio. ah well..... rc2 by the 31st apparently.

crackt out,.

 

[crackt]

after some testing.... it appears the service scanner does not log ac3 pids. after manually adding them with dreambox edit everything is working. definately alot more responsive then the factory software and highly configurable.

crackt out,.

 

[jwwbrennan]

I just wanted to see the interface of the future on an Ultra so I loaded it (twice) this morning. All went well, file system looked good through FTP, Telnet worked but there was nothing on the screen. I was using HDMI so tried composite - nada. I didn't have a lot of time and installed 5209 instead. The very brief instructions don't leave a lot of room for error but the inclusion of "wait for IP adress on VFD of AZBox" caused some doubts about the thoroughness of the specific testing. I wonder if anyone who has loaded it on an Ultra using HDMI has had similar problems and might recommend a solution.

 

[crackt]

you need to load the file via usb and then use azup (over the network) to load it again. the same when going from opensat to enigma.

crackt out,.

 

[jwwbrennan]

Unfortunately it is a bug reported on FS#80 : HDMI is not working out-of-box.. Fortunately the solution is reported as well.

Thanks.

 

[crackt]

must be "ultra" specific. works fine on my elite.

crackt out,.

 

[mr3p]

I had the same thing happen with my Ultra and its a pretty simple fix. Connect a composite video cable to a display, go into the video settings and change the output to HDMI 1080p 60hz, or whatever is appropriate for your display, and it will work fine. I suspect its an issue with the bootup file as the HDMI connection isn't being recognized so it appears to be defaulting to composite video output.

 

[jwwbrennan]

I tried composite and it didn't work either (apparently it did work in all but the latest releases) so I will wait until the next release or, if there is time, change the line in /etc/init.d/bootup. Telnet and FTP worked well but I didn't know what was causing the error at the time.

Thanks.

 

[mr3p]

To install E2, the steps should be:
1. Put E2 on USB stick, reboot Azbox by powering off then on. Will see the typical firmware update screens until first part completes and then it reboots. Leave USB stick in.
2. Ultra has no VFD but you will see lights cycle thru different colors on reboot and eventually be stable with no video output. Wait a minute or two after reboot to be sure.
3. Launch AZup. In the lower corner, there is a button find IP in LAN to confirm AZbox IP address. Enter that address at top. For most users, Device=DOM, Advanced Options both Format Extended partition and Copy kernal are checked. Click Update. You will see installation process log until completion. After completion (~3-5min?), pop-up on computer screen will tell you to remove USB drive and reboot (power off and on Azbox).

After the above, in prior betas my HDMI video came up fine but in PAL which my display could handle. With RC1, it came up blank screen so I connected a composite cable and could see that E2 was installed fine but was outputting composite. With the HDMI cable still connected to the display, changing E2 video settings to 1080p 60hz turned on the HDMI output and display was fine. If you are not seeing anything with a composite cable connected, my initial thought would be the install is not completed or is corrupt. As long as your PC sees the Azbox on the network, you can always stick USB drive back in the box and run AZup to restore clean install if E2 become unstable or corrupt.

Before we start going down the wrong path, or I start making suggestions on what to change in your booup file, can you tell us what exactly you've done so far? RC2 is anticipated today or tommorow but the install process is the same.

 

[jwwbrennan]

To install E2, the steps should be:
1. Put E2 on USB stick, reboot Azbox by powering off then on. Will see the typical firmware update screens until first part completes and then it reboots. Leave USB stick in.
2. Ultra has no VFD but you will see lights cycle thru different colors on reboot and eventually be stable with no video output. Wait a minute or two after reboot to be sure.
3. Launch AZup. In the lower corner, there is a button find IP in LAN to confirm AZbox IP address. Enter that address at top. For most users, Device=DOM, Advanced Options both Format Extended partition and Copy kernal are checked. Click Update. You will see installation process log until completion. After completion (~3-5min?), pop-up on computer screen will tell you to remove USB drive and reboot (power off and on Azbox).

After the above, in prior betas my HDMI video came up fine but in PAL which my display could handle. With RC1, it came up blank screen so I connected a composite cable and could see that E2 was installed fine but was outputting composite. With the HDMI cable still connected to the display, changing E2 video settings to 1080p 60hz turned on the HDMI output and display was fine. If you are not seeing anything with a composite cable connected, my initial thought would be the install is not completed or is corrupt. As long as your PC sees the Azbox on the network, you can always stick USB drive back in the box and run AZup to restore clean install if E2 become unstable or corrupt.

Before we start going down the wrong path, or I start making suggestions on what to change in your booup file, can you tell us what exactly you've done so far? RC2 is anticipated today or tommorow but the install process is the same.

I decided to wait as the time frame is so short. I did make one more discovery after reading your reply - I'm completely incorrect. Guilty by assumption. The television is mounted on the wall in a difficult location. I assumed three partially visible jacks on the back were composite. The Sony manual clearly states they are not. When I saw the post describing the same situation on the bugs list I stopped looking any further. Sorry for generating confusion and thank you for the help. I am now waiting for RC2.

 

[crackt]

mr3p... does the service scanner save ac3 pids for you ?

crackt out,.

 

[mr3p]

Can you give me specific transponder you want me to scan I'll see if I can replicate the same AC3 issue as you?

 

[crackt]

101w - 12060h 26700 enc11_ac3 and enc12_ac3 and 91w - 3820v 30000 fmc-dig. these are some of the few i tested. if you look at the pid info it shows na for apid and under the audio selection menu no audio streams are listed. as a flipside do you have any channels with ac3 audio that you scanned and are working i could test ?

crackt out,.

 

[mr3p]

Away for the weekend. Ill have a look when I get back

 

[mr3p]

I think my prior thoughts regarding AC3 may have been incorrect. Just spent some time trying to get AC3 audio from FMC-Dig. Looking at the PID's in my AZbox with factory firmware, FMC-Dig the Audio PID=1730. Manually entering that number in Dreamboxedit under AC3 and uploading has no effect, picture remains fine but no sound over HDMI in E2 RC1. In fact even after uploading, if you look under "services" the Audio PID remains "N/A" even with a numerical value entered in Dreamboxedit and confirmed to be present by downloading back to PC. I'll probably try another AC3 audio channel tommorow but there definitely still seems to be issue with AC3 audio feeds. I also noticed an issue with no audio from one of the CBS HD feeds on 97w (4160?) which I'm guessing is also AC3 but I'd need to recheck with factory firmware.

 

[crackt]

its nice to see the problem is reproduceable. in dreambox edit there is a pid flag under the edit channel menu (USE PIDs use cached instead of current), i had to set this option before it would use the pid i entered instead of search for one it wasnt finding. seems like this should get submitted to the bugtracker. ive noticed it for the last few releases anyways. im also sure the dmx channels @ 91w dont scan correctly and will bomb the audio service until you zap to 2 channels with valid audio. this may have been the bigger issue with peoples sound issues.

crackt out,.

 

[mr3p]

I did submit a bug report on bug tracker, please take a minute to add a comment that you agree with the bug so hopefully they will acknowledge it. I also tried that checkbox to use PIDs in Dreambox edit and it had no effect. I havn't spent a lot of time on 91 but you'r probably right ab out the dmx channels @ 91. I have been able to scan in all the GDMX (SD) and GDMX_HD feeds @99 (4:2:2) which all work fine