View Full Version : ET9000 newbie : Bootloader, image, audio issues
Hi All,
I have recently acquired my first ET9000 box. At the moment I am exploring different images that would give me ...
a. Media-box capabilities - None of the images seem to be able to give me audio on some of the mkvs that I have on my hard drive. ViX media player is a bit rough
b. User-friendliness for UK user - wifey and kids would be using it extensively as the primary box
c. Multi-boot option - I can experiment with different images while wifey and kids use the image they are used to (ViX).
d. DLNA - Saw this option in Blackhole image. Good to have but not a must
I tried installing Egami 1.3 for the multi-boot option. Everything went well and I installed the Vix image through the multi-boot plugin. However, when I boot the multiboot option does not give me the options to boot into the ViX image. I am suspecting its to do with the bootloader JFFS2 or UBFIS (not sure which one I have).
Q1. How do I find out which bootloader version do I have ?
Q2. How do I decide whether to change/update the bootloader ?
Q3. What can I do to play the mkvs that don't give me audio? How do I get the file info to post for the great developers to check?
Q4. Is there a way to get DLNA in ViX image ?
Q5. Did not find a way to install CCcam 2.2.1 on Egami image. I searched the forum and the cam pack for Egami image seems to be deleted. Can somebody PM please.
Thanks in advance !!
silverfox0786
30-09-11, 11:19
a. Read answer 3. possible reencoding needed
b. very user friendly you will enjoy using
c. VIX and many other images dont support multiboot. but a backup and restore takes minutes
d. DLNA Support VIA UShare will be included in VIX 2.3
1. telnet in and type
uname -r
2. always update to latest bootloader it has new features for newer images [VIX will need latest bootloader] and its backwards compatible
3. MKV's work well just make sure audio codec is of one that is within the ET Drivers
4. Cams cannot be held on site sorry. But VIX image has premade IPK cams here
http://www.4shared.com/dir/wnyHV50A/VIX_CAMS.html
3. It's like that those files are DTS audio ... This is not currently supported, but ET are trying to create a down mix option I do believe to support this (on vu+ it can down mix, but only to stereo, not 5.1).
4. I've been looking in to getting media tomb installed on to the ViX image, and seemed to work ok. So maybe it might be available in the next image...
Hi M8s,
Thanks for the prompt response and useful info.
I observe the audio problem is only with mkvs that have a DTS 5.1 audio. I read a thread on the forum where it mentions a re-encoding method. However, I have really TOO MANY of such videos. If I know that in upcoming images this would work without any re-encoding required, I am happy to wait. Else, I need to find a simple batch mechanism to re-encode all these mkvs
I checked the boot-loader version. It shows 2.6.18-7.4
Do I need to upgrade ? Would really appreciate if you can share the link.
Great to hear that ViX would have DLNA support soon !!
Btw, when I back-up and restore an image, I am hoping it restores all my plugins/extensions/bouquets/satellites.xml/CCcam.cfg/picons/settings etc as well ? Do I need to do an auto-scan or after the restore the box is good to go ? I guess the auto-scan also stores found channels, data etc somewhere on the flash so it should get backup up as well ? Asking because the most painstaking part after flashing each image is running the autoscan. Is there a way to avoid it ?
silverfox0786
30-09-11, 14:28
the MKV issue is a driver one and we need to await ET do release new ones, its possible but when we don't know
the boot loader needs updating to 2.6.30 - 3.2 its in ET9000 section flash as you would a normal image
the backup manager is awesome
it backs up everything
and you can select other bits and bobs to add
when i re-flash and restore i don't need to do anything after i even get the last channel i was watching when i made the backup
so all is there no rescan needed
Does this tool does the full back as mentioned above ??
http://www.world-of-satellite.com/showthread.php?7815-Make-Full-backup-of-your-image
silverfox0786
30-09-11, 14:30
backup manager is build into VIX and will deploy from within there backup and restore
so as my son says when its 3pm at school
yr GOOD TO GO
to access the backup options within ViX press the blue button > ViX > backup manager and img manager. these two options will create a full working backup of your system that can be flashed back to the receiver within minutes.
Thanks again for the great info.
So the backup manager takes a backup of all settings/extensions and img manager takes a backup of the image
and when I need to restore, I first restore the image and then the settings/extensions, right ??
to access the backup options within ViX press the blue button > ViX > backup manager and img manager. these two options will create a full working backup of your system that can be flashed back to the receiver within minutes.
ok I have just flashed the latest vix image...i'm gonna take a backup, flash the new bootloader and then restore my image...guess that'd teach me the basics !! :)
the boot loader needs updating to 2.6.30 - 3.2 its in ET9000 section flash as you would a normal image
Thanks again for the great info.
So the backup manager takes a backup of all settings/extensions and img manager takes a backup of the image
and when I need to restore, I first restore the image and then the settings/extensions, right ??
pretty much yeah. also you can customize exactly you want the backup manager to backup by pressing menu while in that section.
I have now updated to the latest bootloader given in Post#13 in
http://www.world-of-satellite.com/showthread.php?6380-Latest-ET9000-Bootloader-and-Drivers-updates/page2
When I restart the box, the startup screen shows "Bootloader 2.6.31 UFIBS"
However, on telnet it still shows 2.6.18-7.4
I recall reading somewhere that although the uname shows the older version, the bootloader is now updated. Is this correct ?
Also, Post#12 on the above link has new drivers. Do I need to install these too ? How ?
Thanks again for the great info.
So the backup manager takes a backup of all settings/extensions and img manager takes a backup of the image
and when I need to restore, I first restore the image and then the settings/extensions, right ??
to access the backup options within ViX press the blue button > ViX > backup manager and img manager. these two options will create a full working backup of your system that can be flashed back to the receiver within minutes.
silverfox0786
30-09-11, 15:36
my boot loader shows the correct one under uname -r
when u dlash bootloader you must go straight into a reflash of the image aswell
here is mine
Welcome to ViX for ClarkeTech
ViX v2.3
ClarkeTech login: root
Password:
root@ClarkeTech:~# uname -r
2.6.31-3.2
root@ClarkeTech:~#
Ok I have updated the bootloader given in Post#13 of the below :
http://www.world-of-satellite.com/showthread.php?6380-Latest-ET9000-Bootloader-and-Drivers-updates/page2
The TV startup screen shows "bootloader 2.6.31 UFIBS". However, uname -r still shows 2.6.18. I recall reading somewhere that this happens...has my bootloader updated correctly ?
Also, there is a new driver in Post#12. Do I need to update that too ? How??
the MKV issue is a driver one and we need to await ET do release new ones, its possible but when we don't know
the boot loader needs updating to 2.6.30 - 3.2 its in ET9000 section flash as you would a normal image
the backup manager is awesome
it backs up everything
and you can select other bits and bobs to add
when i re-flash and restore i don't need to do anything after i even get the last channel i was watching when i made the backup
so all is there no rescan needed
I will have to do this, always best to be able to get up and running straight away :)
No matter what I do uname is still showing 2.6.18-7.4 :(
The splash screen continues to show 2.6.31
I even tried flashing ViX 2.2 afresh right after a flash of the bootloader.
Suggestions ??
Can anybody confirm that the file in Post#13 of this thread indeed has bootloader version 2.6.31 instead of 2.6.18-7.4 ?
http://www.world-of-satellite.com/showthread.php?6380-Latest-ET9000-Bootloader-and-Drivers-updates/page2
Just want to be sure that I am using the right bootloader flashing file....because whenever I flash using it uname shows me 2.6.18 :(
Also, how do I update the drivers ? Do I need to ftp it somewhere ?
Yes, same thing for me.
Splash screen shows 2.6.31, but seems to be 2.6.18-7.4
Welcome to ViX for et9000
ViX v2.2
et9000 login: root
root@et9000:~# uname -r
2.6.18-7.4
root@et9000:~#
root@et9000:~#
BTW silverfox, are you using VIX v 2.3?
beson
Ignore what the splash screen says when your using the latest bootloader, its misleading, its just an image with test on it.
If you guys are using ViX 2.2 you will be using kernal 2.6.18-7.4, not the latest kernel as the splash screen says. Its just a splash screen, not the actual kernel.
You will only be using the latest kernel if you use the latest PLi 2.1 or when 2.3 is released you will then be using the latest kernel.
silverfox0786
30-09-11, 17:12
ahh right thanks for clearing that up sic didnt realise that
So I guess I'm not the only one...
Btw, I found out that to update the drivers I need to copy the drivers to
/lib/modules/2.6.18-7.4/extra
and reboot. Can anybody confirm this works ?
Btw, that pbbly also means that the bootloader is 2.6.18-7.4 ...otherwise the path would have been /lib/modules/2.6.31-x.x/extra
Silverfox can you confirm what do you see on the above path ??
So I guess I'm not the only one...
Btw, I found out that to update the drivers I need to copy the drivers to
/lib/modules/2.6.18-7.4/extra
and reboot. Can anybody confirm this works ?
Btw, that pbbly also means that the bootloader is 2.6.18-7.4 ...otherwise the path would have been /lib/modules/2.6.31-x.x/extra
Silverfox can you confirm what do you see on the above path ??
Read what its says in post 12 of that thread. Just wait for ViX2.3 and please be patient.
THESE MUST ONLY BE USED WITH IMAGES THAT CONTAIN KERNAL 2.6.31!
Sorry..didn't "refresh" the webpage before my previous post and hence missed Sicilian's clarifications above.
Do I need to update the drivers for ViX 2.2 (21-07-2011) image ?? Or does it have the latest drivers?
Sorry..didn't "refresh" the webpage before my previous post and hence missed Sicilian's clarifications above.
Do I need to update the drivers for ViX 2.2 (21-07-2011) image ?? Or does it have the latest drivers?
Just press Blue button > ViX > Software update. Thats all you need to do.
After that just wait for ViX 2.3 or use an image that uses the latest kernal.
After reading this thread, I flashed my box with the new boot loader.
The initial splash panel now shows Xtrend in red and 2.6.31 UBIFS.
However when I enter uname -r I get : 2.6.18-7.4 (as before) Why does this not show 2.6.31?:confused:
I am running Vix 2.2.100. What benefit does the new boot loader provide - i.e. how might I notice the difference in normal operations?
After reading this thread, I flashed my box with the new boot loader.
The initial splash panel now shows Xtrend in red and 2.6.31 UBIFS.
However when I enter uname -r I get : 2.6.18-7.4 (as before) Why does this not show 2.6.31?:confused:
I am running Vix 2.2.100. What benefit does the new boot loader provide - i.e. how might I notice the difference in normal operations?
Read my posts above :rolleyes:
Read my posts above :rolleyes:
Please would you explain what the boot loader does, and what is its relationship to the kernel and drivers.
As I understand it:
The bootloader and the kernel are two different things. "uname -r" shows you the version of the kernel, not the version of the bootloader. The drivers are compiled for a specific kernel version and therefore cannot be used for other versions.
The new OpenPLI images use a new filesystem that the old bootloader didn't support, this is why you need to update the bootloader. It has nothing to do with the linux kernel version as such, except for the fact that the new file system must be supported.
The original bootloader also did not support flashing of images larger than 60MB, so without an updated bootloader you wouldn't be able to re-flash a large backup image (look at the size of the rootfs.bin file, it will tell you the size of your image).
Therefor, if you're able to re-flash a large backup image: don't worry, you have the new bootloader.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.