Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[VU+ Duo] New ViX Team VU+ Duo OE3.0 Discussion

Status
Not open for further replies.
Has anyone had issues with the 339 build mounting internal hdd to a different mount point from normal?

After I auto updated, the recording list was looking at my usb flash drive I also got an error about timeshift as it was also trying to use the usb flash drive.

I've fixed it by editing all the mount points for epg, timeshift and recording.

Just seems weird this is the first time I've had this issue.

Cheers

Davie.

p.s. keep up the great work love this image!

easy fix if this happens menu>setup>vix>mount manager>green button and change it there
 
ha, didn't spot it was a ping from lappy...

this time using Putty. :)



Welcome to OpenViX for vuduo
openvix 3.0 vuduo


vuduo login: root
root@vuduo:~# ping www.world-of-satellite.com
PING www.world-of-satellite.com (94.75.215.25): 56 data bytes
64 bytes from 94.75.215.25: seq=0 ttl=55 time=26.714 ms
64 bytes from 94.75.215.25: seq=1 ttl=55 time=24.984 ms
64 bytes from 94.75.215.25: seq=2 ttl=55 time=24.370 ms
64 bytes from 94.75.215.25: seq=3 ttl=55 time=24.270 ms
64 bytes from 94.75.215.25: seq=4 ttl=55 time=26.656 ms
64 bytes from 94.75.215.25: seq=5 ttl=55 time=25.799 ms
64 bytes from 94.75.215.25: seq=8 ttl=55 time=25.750 ms
64 bytes from 94.75.215.25: seq=9 ttl=55 time=24.648 ms
64 bytes from 94.75.215.25: seq=10 ttl=55 time=24.046 ms
64 bytes from 94.75.215.25: seq=11 ttl=55 time=26.904 ms
64 bytes from 94.75.215.25: seq=12 ttl=55 time=25.089 ms
64 bytes from 94.75.215.25: seq=14 ttl=55 time=25.658 ms
64 bytes from 94.75.215.25: seq=15 ttl=55 time=25.267 ms
64 bytes from 94.75.215.25: seq=16 ttl=55 time=24.188 ms
64 bytes from 94.75.215.25: seq=17 ttl=55 time=24.338 ms
64 bytes from 94.75.215.25: seq=19 ttl=55 time=24.893 ms
64 bytes from 94.75.215.25: seq=20 ttl=55 time=24.788 ms
^C
--- www.world-of-satellite.com ping statistics ---
21 packets transmitted, 17 packets received, 19% packet loss
round-trip min/avg/max = 24.046/25.197/26.904 ms
root@vuduo:~# ping www.world-of-satellite.comping www.world-of-satellite.comping
www.world-of-satellite.comping www.world-of-satellite.com
 
Hmm, so your box does see the outside world indeed.
One last suggestion: what are the outputs of
Code:
opkg update
and
Code:
opkg remove enigma2-plugin-extensions-mediaplayer
 
@player1

might I surgest you start a new thread, we are up to speed on your problem, ( well those looking into it ) my worry is, if this problem persist untill tomorrow, it could be lost in the very long thread

but this is of course upto you
 
Hmm, so your box does see the outside world indeed.
One last suggestion: what are the outputs of
Code:
opkg update
and
Code:
opkg remove enigma2-plugin-extensions-mediaplayer

in thick person's English are you asking me to try those commands in Telnet ?

edit...

Ok Basil.
 
Hmm, so your box does see the outside world indeed.
One last suggestion: what are the outputs of
Code:
opkg update
and
Code:
opkg remove enigma2-plugin-extensions-mediaplayer

opkg update =


Welcome to OpenViX for vuduo
openvix 3.0 vuduo


vuduo login: root
root@vuduo:~# opkg updateopkg update
opkg: unknown sub-command updateopkg
usage: opkg [options...] sub-command [arguments...]
where sub-command is one of:

Package Manipulation:
update Update list of available packages
upgrade Upgrade installed packages
install <pkgs> Install package(s)
configure <pkgs> Configure unpacked package(s)
remove <pkgs|regexp> Remove package(s)
flag <flag> <pkgs> Flag package(s)
<flag>=hold|noprune|user|ok|installed|unpacked (one per invocation)

Informational Commands:
list List available packages
list-installed List installed packages
list-upgradable List installed and upgradable packages
list-changed-conffiles List user modified configuration files
files <pkg> List files belonging to <pkg>
search <file|regexp> List package providing <file>
info [pkg|regexp] Display all info for <pkg>
status [pkg|regexp] Display all status for <pkg>
download <pkg> Download <pkg> to current directory
compare-versions <v1> <op> <v2>
compare versions using <= < > >= = << >>
print-architecture List installable package architectures
depends [-A] [pkgname|pat]+
whatdepends [-A] [pkgname|pat]+
whatdependsrec [-A] [pkgname|pat]+
whatrecommends[-A] [pkgname|pat]+
whatsuggests[-A] [pkgname|pat]+
whatprovides [-A] [pkgname|pat]+
whatconflicts [-A] [pkgname|pat]+
whatreplaces [-A] [pkgname|pat]+

Options:
-A Query all packages not just those installed
-V[<level>] Set verbosity level to <level>.
--verbosity[=<level>] Verbosity levels:
0 errors only
1 normal messages (default)
2 informative messages
3 debug
4 debug level 2
-f <conf_file> Use <conf_file> as the opkg configuration file
--conf <conf_file>
--cache <directory> Use a package cache
-d <dest_name> Use <dest_name> as the the root directory for
--dest <dest_name> package installation, removal, upgrading.
<dest_name> should be a defined dest name from
the configuration file, (but can also be a
directory name in a pinch).
-o <dir> Use <dir> as the root directory for
--offline-root <dir> offline installation of packages.
--add-arch <arch>:<prio> Register architecture with given priorit y
--add-dest <name>:<path> Register destination with given path

Force Options:
--force-depends Install/remove despite failed dependencies
--force-maintainer Overwrite preexisting config files
--force-reinstall Reinstall package(s)
--force-overwrite Overwrite files from other package(s)
--force-downgrade Allow opkg to downgrade packages
--force-space Disable free space checks
--force-postinstall Run postinstall scripts even in offline mode
--force-remove Remove package even if prerm script fails
--noaction No action -- test only
--download-only No action -- download only
--nodeps Do not follow dependencies
--force-removal-of-dependent-packages
Remove package and all dependencies
--autoremove Remove packages that were installed
automatically to satisfy dependencies
-t Specify tmp-dir.
--tmp-dir Specify tmp-dir.

regexp could be something like 'pkgname*' '*file*' or similar
e.g. opkg info 'libstd*' or opkg search '*libop*' or opkg remove 'libncur*'
root@vuduo:~# opkg update



opkg remove enigma2-plugin-extensions-mediaplayer =


Welcome to OpenViX for vuduo
openvix 3.0 vuduo


vuduo login: root
opkg remove enigma2-plugin-extensions-mediaplayerroot@vuduo:~# opkg remove enigma2-plugin-extensions-mediaplayer
Collected errors:
* opkg_conf_load: Could not lock /var/lib/opkg/lock: Resource temporarily unavailable.
root@vuduo:~#
 
Code:
root@vuduo:~# opkg updateopkg update
That's the command 2 times......

Please just copy and paste
Code:
opkg update
nothing else please. This could give us a clue.

And if you get
Code:
Collected errors:
* opkg_conf_load: Could not lock /var/lib/opkg/lock: Resource temporarily unavailable.
for an answer, the box probably has just come out of standby and is executing a backgroundcheck. Than you should wait a couple of minutes and try again.
 
Hi,

I have to say that at this point I am really confused....

How does it work? An unstable update becomes stable if no problem is found , or a different version is marked stable if it's only a fix of an unstable with problems and no new stuff?

What is the latest stable version? I still have the 2something (not sure which, maybe 264?) and no green flash.. even if you talk about 339 and more.

The one listed in the thread "OpenViX image updates and changelogs" are the stable or unstable updates? Thre is no mention of it. Maybe a Stable thread and an Unstable one would be more clear, so if you like to be on the stable branch you know what you should load...

You are doing a great work, but there is a LOT of stuff going around and it's confusing for the casual user.

G
 
I've just updated my image to 339 and have found that my channel zapping is running very slow (compared to earlier versions of vix) just wondered if anybody else had this issue or if i am only one???
 
Code:
root@vuduo:~# opkg updateopkg update
That's the command 2 times......

Please just copy and paste
Code:
opkg update
nothing else please. This could give us a clue.

And if you get
Code:
Collected errors:
* opkg_conf_load: Could not lock /var/lib/opkg/lock: Resource temporarily unavailable.
for an answer, the box probably has just come out of standby and is executing a backgroundcheck. Than you should wait a couple of minutes and try again.


Welcome to OpenViX for vuduo
openvix 3.0 vuduo


Box has NOT just come out of standby mode. It's been running with a clean install of 339 for about 15 minutes. No settings installed at all.


vuduo login: root
root@vuduo:~# opkg update
Collected errors:
* opkg_conf_load: Could not lock /var/lib/opkg/lock: Resource temporarily unava ilable



Welcome to OpenViX for vuduo
openvix 3.0 vuduo


vuduo login: root
root@vuduo:~# opkg remove enigma2-plugin-extensions-mediaplayer
Collected errors:
* opkg_conf_load: Could not lock /var/lib/opkg/lock: Resource temporarily unavailable.
root@vuduo:~#
 
Thanks: that does give a clue. We'll look into that, but we need your debuglogs. Could you enable them, restart the box and do the same as above? And than post the log please.
 
Thanks: that does give a clue. We'll look into that, but we need your debuglogs. Could you enable them, restart the box and do the same as above? And than post the log please.

strange happenings .... it actually went through the motions of trying to download plugins but hung in that screen for about 15 before I broke it up.

All further attempts went back to the usuall feeds down for maintenance.
 

Attachments

strange happenings .... it actually went through the motions of trying to download plugins but hung in that screen for about 15 before I broke it up.

All further attempts went back to the usuall feeds down for maintenance.

if you stopped it halfway though checking, this why yu are getting issues, as the lock file is still in place as opkg did not complete so did not clear the lock file, only one copy of opkg can be run at a time.

please delete file '/var/lib/opkg/lock' and try again.
 
Another crash on my 321 Duo, now using graphical EPG with the EPg button.

Code:
FATAL: dvb/epgcache.cpp:238 ASSERTION pos <= 4108 FAILED!

looks like a corrupt epg.dat file.
 
Quick one. I'm on the latest stable release of Open ViX 3.0 (installed from feeds yesterday evening).

I have a problem with the system going into reboot or perhaps enigma restart when I run the XEPGDB - France download from CrossEPG. Never did this under Vix2.4

EPG.Dat is on my USB drive. I also have a Nova Win DVB-T usb tuner running under the dib0700 driver*. Other than that all is standard - OpenTV EPG data for 28.2E works fine. No swap file in use.

Any quick pointers to resolve? If not I'll get the logs later when I'm home and provide more detailed info.

*Separate issue is that after it crashes and reboots the DVB-T tuner is dropped. Sometimes system also restarts in a mode when one of the 28.2 channels is displayed but red 'startup' LED is still showing on Vu+ display and system refuses to respond. To clear this I need to do a hard reboot...sometimes several (generally works if I leave it a few minutes).
 
SalteeDog, how did you get the Nova Win DVB-T usb tuner working with 3.0?
I have not managed to do that.
 
Status
Not open for further replies.

OpenViX Feeds Status

Back
Top