[TM-TWIN-OE] TM-TWIN Random Reboots

[stilts]

Feeling disappointed!

Less than 12 hours back on Vix and another reboot.

Going back to 4D simply for the stability.

I really can't understand what's going wrong here.

My friend has just upgraded his too from an older version of Apollo (3) to 71, his has been totally stable on that old version, so, I'm actually hoping his starts behaving like mine just so I can say it's something wrong with Vix.

Cheers


Sent from my iPhone using Tapatalk

 

[abu baniaz]

The 4d image uses old kernel and drivers.

 

[stilts]

Is there anything else I can do in order to use Vix?


Sent from my iPhone using Tapatalk

 

[stilts]

Surely they should be quite a lot of owners of these boxes reporting similar problems, just can't understand it


Sent from my iPhone using Tapatalk

 

[Larry-G]

Surely they should be quite a lot of owners of these boxes reporting similar problems, just can't understand it


Sent from my iPhone using Tapatalk

If there was a ViX image issue with this receiver or any other for that matter you would have seen multiple reports about it, as it stands you are so far the only one I know of. Why that is I don't know but I don't have any such issue with my own TM Twin.


Sent from my iPad Air using Tapatalk

 

[kegnkiwi]

I wondering if there is some mixmatch of bootloader and vix image, 4D uses different bootloaders to the latest vix images as stated earlier. If some time soul could point you to the correct boot loader vix image match it would be a good starting point. I know I use 4d image but I went though a little process of finding the correct boatloader to match the image and along with a 1/2 gigg swap file i installed my box has been rock solid.

 

[Larry-G]

I wondering if there is some mixmatch of bootloader and vix image, 4D uses different bootloaders to the latest vix images as stated earlier. If some time soul could point you to the correct boot loader vix image match it would be a good starting point. I know I use 4d image but I went though a little process of finding the correct boatloader to match the image and along with a 1/2 gigg swap file i installed my box has been rock solid.

The main problem is that TM like Vu+ build their images from a very old OE and their drivers / boot loaders are built for the same old OE, so when they are ported by TM to work with images using more upto date OE's unforeseen problems can arise.


Sent from my iPad Air using Tapatalk

 

[kegnkiwi]

I know previousley when i've visited the forum that has been threads telling people they must update there bootloaders to make the latest images work as I know vix use your own code. Honestly it can be a little confusing trying to find the correct bootloader for the correct image. If as admin you know where both could be found that shoud in theory make his box the most stable it would be a least something to try.

 

[judge]

All the currently released bootloaders recommended for ViX images are on the image server.
http://www.openvix.co.uk/index.php?dir=Bootloaders/

 

[Larry-G]

All images and bootloaders can be found on our download site www.openvix.co.uk. It's not rocket science to navigate and find what you need there.


Sent from my iPad Air using Tapatalk

 

[kegnkiwi]

These could be the two you need to make a stable image?

http://www.openvix.co.uk/index.php?dir=Bootloaders/Technomate-Bootloaders/TM-TWIN-OE/

and

http://www.openvix.co.uk/index.php?dir=TM-Twin-OE/

Maybe admin would advise if this is a good mix and match

 

[stilts]

Thanks everyone for your comments, all feedback is appreciated!!!

I'm very familiar with the downloads section of the site and I've flashed the latest bootloader too.

I flashed my friends TWIN yesterday with Apollo 071 and his is also fine, his is pretty much an identical setup to that of mine, the only thing I know that is different between them is that he uses and external USB hard disk for recordings/timeshift whereas I'm using an internal disk.

Is there any limitation with the size of internal hard disk, I'm using a 1Tb, as mentioned early on in the thread, I had been using Vix successfully for quite sometime before encountering the problem but couldn't say for sure which release I first got the problem.

Is the size of the hard disk I'm using the problem, is it too big, I know for sure last night during the first reboot I was recording two channels and I would have also been in timeshift?


Cheers!

 

[abu baniaz]

Where you using time shift during your earlier Vix tests?

There is an issue with playback?

 

[stilts]

Hi Abu,

I did disable timeshift during one of the tests and still encountered a reboot.

I'm happy to try another flash of the latest Vix and bootloader, do you have to do this in any specific order, pretty sure in the past I've flashed with the bootloader first then the Vix image, is this correct?

 

[abu baniaz]

You flashed in the correct sequence. Stick to the August 4D image for now. They are using the old kernel and drivers. When Apollo was released, a new kernel and driver set was incorporated.If you find a copy of Helios, it will be stable, but there will be no feeds for you.

 

[stilts]

Hi Abu,

Thanks for that feedback, sounds interesting.

Surely though as I previously mentioned and Phoenix also agreed, others should be encountering this issue too.

Is it all related to the usage of an internal hard disk, and, is this planned to be further investigated?


Sent from my iPhone using Tapatalk

 

[abu baniaz]

Technomate were informed of this issue months back. You will have to contact TM about updates.

It is not intereesting, it is frustrating. They were made aware of playback issue a few months ago.

 

[stilts]

Hi Abu,

Agreed, interesting from my point of view as I've not had any feedback to give me an idea of where the problem might be.

Also agreed that it's frustrating (I know only too well), how will I know when the problem has been remedied, just lookout for the updates relating to Technomate in the Vix Updates/Changelogs?

Is it the same problem though, as mentioned, I had previously disabled timeshift and it still rebooted (the hard disk was still installed and connected though)?

And is the playback problem only related to internal hard disks (apologies for all the questions, just trying to get all the info I can)?


Sent from my iPhone using Tapatalk

 

[abu baniaz]

The way it should work is that TM supply test kernels and drivers to image teams. They test and report back. As with all manufactures, you fix some things and get adverse results elsewhere. That's just life. But they can then deal with them and resolve as they go along.

Sadly this is not happening. Look out for Dags in the changelogs. Changes get committed by other team members with no prior notification.

I have not played back from a USB device for a long time. Will test soon for you. I can only test on the Nano-OE though, they use the same drivers.

 

[stilts]

I have not played back from a USB device for a long time. Will test soon for you. I can only test on the Nano-OE though, they use the same drivers.

Thanks again Abu,

Just to clarify, my hard disk is a 1Tb internal.


Sent from my iPhone using Tapatalk