ET9000 newbie : Bootloader, image, audio issues

[Reidy]

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

[kunmun23]

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 ??

[kunmun23]

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/sh...-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 ?

[beson]

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

[Sicilian]

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]

ahh right thanks for clearing that up sic didnt realise that

[kunmun23]

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 ??

[Sicilian]

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!

[kunmun23]

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?

[Sicilian]

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.

[kunmun23]

Got it...thanks !!

[machare]

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?

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?

[Sicilian]

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?

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

[machare]

Read my posts above

Please would you explain what the boot loader does, and what is its relationship to the kernel and drivers.

[Cucosat]

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.