ViX 029 and 147 drivers

[ant500]

hi guys just a quick question are you trying to make a backup for sunray or Lonrison v4

 

[IAmATeaf]

I'm trying to create an image for a lonrison v4 box.

 

[ketmp]

I'm trying to create an image for a lonrison v4 box.

You would probably find it quicker and easier using your original box and then swapping drivers that way.

 

[IAmATeaf]

You would probably find it quicker and easier using your original box and then swapping drivers that way.

I hate to admit this but for some reason doing that actually slipped my mind, I'm keen to know how to mount and recreate images anyway so I suppose I could say where would be the fun in that

 

[ketmp]

I hate to admit this but for some reason doing that actually slipped my mind, I'm keen to know how to mount and recreate images anyway so I suppose I could say where would be the fun in that

I wanted to know how to easily be able to replace drivers but found out it is more hassle, hard work and time consuming so gave up

Good luck

 

[dubliner]

@IAmATeaf @ketmp i,ve uploaded backupsuite ipk 18.0 to the download section tested on openatv today .

 

[ketmp]

@IAmATeaf @ketmp i,ve uploaded backupsuite ipk 18.0 to the download section tested on openatv today .

Thanks but I already have that.

It was posted on dreamoem site below:

You don't have permission to view the code content. Log in or register now.

 

[dubliner]

No worrys ketmp i,ll pm you link for a few version from 18.0 back to 14.4 if needed in the future as some version work better on different images .

As talnet backup does not always work .

 

[ketmp]

@IAmATeaf, you said the dvb driver in vix 029 matches the one that was in Vix 078 didn't you?

In that case then those at vu-hd must have patched the drivers in their vix 029 as I couldn't find a match to original drivers released 15/07/14, 29/08/14 or 25/09/14. These drivers were patched to work with v4 flashed boxes presumably!

If they've patched it once then they obviously can patch it again with xbmc drivers released now as it wont be long before main images move over (Open ATV/Vix already have)!!

I think maybe Lonrison customers should email and complain to their seller as they are only ones that can put pressure on whomever updates vu-hd website.

I asked a seller what images to use and was naturally referred to vu-hd website. I then replied that those images are over 6 months old are they being updated as I don't want to buy a box where there are no images updated for it. Naturally, I didn't get a response at this point!!

 

[dubliner]

lads when i did the vti 8 clone image i took the drivers from vti 7 from vu-hd site and there is 5 drivers in that image is this normal as that was the last image uploaded over there and when first uploaded they made a mistake and they change this weeks later .

 

[ketmp]

lads when i did the vti 8 clone image i took the drivers from vti 7 from vu-hd site and there is 5 drivers in that image is this normal as that was the last image uploaded over there and when first uploaded they made a mistake and they change this weeks later .

Was one file cdfs.ko? This file is used to read filesystem of an audio CD and is included in some images and not others. I know it's included in OpenATV but not OpenVix

 

[SpaceRat]

Creating OpenATV images is rather easy and doesn't require any additional software or plugins:

Do at your own risk:
1. Prepare the clone safe drivers somewhere at but not on the box (e.g. HDD or USB, but not flash obviously)
2. Disconnect the network and satellite cables from your Vu+ Solo² (SE) clone (Prevents box from catching the time)
3. Flash the original image as you would on an original box
4. Let the box fully boot with network and satellite cables still disconnected (Prevents box from catching the time)
5. If unsure better wait even longer, better safe than sorry, with the cables still disconnected
6. Note: It's normal the box will not really work or even crash at this point. You can still work on Linux level, just ignore E2 failing again and again.
7. Connect network cable
8. Quickly ssh/telnet into the box
9. Replace driver files and write protect them
10. Reboot
11. Test
12. Wipe the content of /etc/enigma2 and without reboot create an image backup using the build in "Software Management"

Such an image will start with the setup wizard for the user flashing it on a new box and it will sucessfully import setting backups made through the Software Management if you are flashing this OpenATV as an update for an older OpenATV.

Boxes get the time over DVB-S (Thus disconnect satellite cables) and/or ntp sync on start (Thus also disconnect the network cable on boot to let this fail).
They happily do not include an ntp daemon so they are not capable of getting the time later.


I'm currently running an OpenATV 4.2 which was built before 2015-02-07 but fully updated (except of the drivers).
I've even recompiled the kernel

You don't have permission to view the code content. Log in or register now.

with the r4.6 settings so the box is happy with the r4.7 kernel it sees, although it actually is the same kernel as it was built until 2015-02-06.

I made this to aid users who need additional kernel modules and can not install them else due to the mix of r4.7 modules on the feed and r.3.x-r4.6 kernel/modules inside the image.

I have investigated the driver behaviour further and I'll try to create a new image (post 2015-02-07) from scratch, downgrading the kernel to my version and the drivers to the latest Lonrisun version later.

Endlessly updating older images isn't really a solution for eternity, as sometimes boxes updated from feed only do not really catch up the latest changes.

 

[SpaceRat]

Obviously if you have an original Solo² at hand, it's safer to use that for creating the clone safe image:
It won't work with the clone drivers though so perform only steps 1,3,8,9 and 12 in that case.

 

[ketmp]

Obviously if you have an original Solo² at hand, it's safer to use that for creating the clone safe image:
It won't work with the clone drivers though so perform only steps 1,3,8,9 and 12 in that case.

I do similar to those steps on my Sunray clone except step 12. Does removing files within /etc/enigma2 force the image to go through setup procedure again once then flashed and started?

 

[ant500]

ok was going to give this a bash today so thought i check my box was v4 but laptop and box not talking to each other lol do i have to run the fpga_update tools again first to up date box to v4 all i get is the black window with the flashing cursor evan after swiching on sat box

 

[SpaceRat]

I do similar to those steps on my Sunray clone except step 12. Does removing files within /etc/enigma2 force the image to go through setup procedure again once then flashed and started?

For OpenATV it does.

However something has changed about the default channel setup in OpenATV:
Originally the images came pre-loaded with default bouquets through the package
enigma2-plugin-settings-defaultsat
and the only way to get rid of them permanently (To keep it from overwriting own channel settings whenever that package was updated) was to remove that package.

Current images however are "own setup friendly". The same package now contains the default bouquets within
/etc/defaultsat.tar.gz
and they get only extracted/installed when there is no lamedb in /etc/enigma2, so if you restore own settings, there is your own lamedb and it prevents default channels from being applied and if you don't, the defaults get installed.

So when blanking /etc/enigma2 you should make sure that
/etc/defaultsat.tar.gz
exists, in case users want to start from scratch.
That file might be missing when you just opkg update && opkg upgrade from older images (i.e. to preserve the old kernel/drivers).

 

[SpaceRat]

PS:
It would be pretty helpful if people could help me to reach 5 USEFUL posts so that I can download this file
https://www.digitalworldz.co.uk/index.php?resources/2874/
which I need for further tests (Sunray drivers on Lonrisun V4).

 

[SpaceRat]

I'm also going to add a special script e2up for doing online updates on clones:

You don't have permission to view the code content. Log in or register now.

See how the script notifies the user about unsafe packages being upgradable (or in this case: not being part of the upgrade) and how it upgrades the whole myriad of other packages just fine.

It protects the enigma2 binary and the startup script from being replaced in the process and at the end it also replaces the enigma2 binary with the very same version number but that of a Vu+ Duo, because that one doesn't have gles support built-in.
This update protection/replacement keeps E2 from crashing whenever you try to shut down or restart the whole box.
Besides the gles support, the enigma2 binaries of Solo² and Duo do not differ, so it's the perfect replacement.

The old Solo had only 1 tuner, so the old Solo actually is the precedessor of the Vu+ Zero, while the Duo is the precedessor of the Solo² and the Ultimo is the precedessor of the Duo².

So for a Vu+ Duo² clone one would use the Ultimo binary.

 

[ketmp]

...further tests (Sunray drivers on Lonrisun V4).

Sunray drivers on most non-Sunray boxes just end up with blank screen (but no bricking) as a lot of people have tried (some accidently). That's at least what I understand from posts on this forum.

Those files are just bootloader files. It has been tried to recover from brick state but been unsuccessful (again that's what I read in this forum).

 

[ketmp]

@SpaceRat, if you read my post here, the drivers in Vix 029 from vu-hd website must have been patched because they don't match any drivers released since Kernel was updated to 3.13.5.

This confirms my suspicion that Lonrison could patch newer drivers and/or update flash but they clearly don't want to. Instead getting everyone to either buy new box or flash chips.