Posts by paulthego

I have updated and so far no problems. Thank

I cant work the screen from work so I vpn'd home and got this

root@vusolo2:/etc# cat image-version
box_type=vusolo2
build_type=0
version=3.0
build=627
drivers=20130218
date=20130308221606
comment=ViX
target=9
creator=openViX
url=http://www.vuplus-support.co.uk
catalog=http://www.vuplus-support.co.uk

Hi all just confirming I have this problem using an Openvix image created by MrGMX I will try the brightness setting tonight and see if that fixes it. I am using a Solo2 as well.

I also use "0" which just switches between the 2 channels. Using a blackhole image

I have done numerous searches on this issue and the general consensus appears to be these problems are caused by TSPanel and the way its written. Lots of posts saying you shouldnt use it especially on VIX images. It appears to affect DUO's, Dreambox DM800 and others. Its annoying as I had switched to VIX. Maybe when I give it a go next time I will try it without TSPanel to see if I still get the problem.

This sounds just like the problem I was having on my Solo2 http://linuxsat-support.com/vu…rive-wont-initialize.html

It wouldnt mount the drive whenever I tried in the menus some python program would crash adding a line to fstab. I added my own entry into fstab and manually mounted the drive but on reset the line I put in fstab was gone. In the end I gave up and went back to BlackHole.

In my case the drive is not mounted and there is no entry in fstab. I was able to manually mount it and then I can record etc although it didnt pick up my picons. I have since reverted to your Blackhole image which is fine and the hard drive initialises and mounts fine.

Like Wiganfun notes if you reboot the box its not mounted which is not a surprise as there is no entry in fstab to mount it.

I am thinking of going back to blackhole 1.7.9-3 by MrGmx as that seemed stable and transcoding seemed better. I will probably do this friday if no one else comes up with an answer.

Hi I have been having a similar problem. I am running OpenVix backup image from MrGmx and I went into the Software update menu and tried to do an update. On completing this the Solo2 rebooted and my hard drive was gone. I tried various things from the menus including initialising the drive. I then tried to add it back in mountmanager which caused enigma2 to crash with an error in adding a line to fstab. In desparatiion I telneted into the box ran a "mkfs.ext4 /dev/sda1" then "mkdir /media/hdd" lastly mounted it by typing "mount /dev/sda1 /media/hdd". This all worked and I was able to timeshift programs etc. Unfortunately if I reboot then all is gone. So I now need to add a line in to fstab.

I thought I would check the forums first and encountered this post. So your not the only one. Just dont know the right resoloution yet. Here is the exert from the crash log

Traceback (most recent call last):
File "/usr/lib/enigma2/python/Tools/BoundFunction.py", line 9, in __call__
File "/usr/lib/enigma2/python/Components/Console.py", line 56, in finishedCB
File "/usr/lib/enigma2/python/Plugins/SystemPlugins/ViX/MountManager.py", line 224, in add_fstab