View Full Version : [VU+ Duo2] update new version .10
why do I see version 10 in upgrade and only version 9 in download ? Same for download section as update section online ? I know a full clean install is necessairy for 09 .
et9200 Updated to 010 ,working super!!,great work from the VIX team,thanks a lot!!
after update my directory for oscam is gone ?
Hoopstroops
08-10-15, 18:37
Duo2 sick as a dog after 010 multiple crashing! Lost mounted drives aargh!
Sent from my iPhone using Tapatalk
working but seems oscam info is not working anymore.Updating to version 10 and otherwise going back to 07.
found solution : seems oscam config was changed.Need to put interface to reading oscam config to yes.
frozenfire
10-10-15, 09:08
omg. After sorting my box with the 009 reflash.
I go to update to 010 and its just stuck on updating screen!!!
Don't tell me I have to reflash! How much reflashing can my duo2 take? It will soon be bricked im sure.
How much reflashing can my duo2 take? It will soon be bricked im sure.
WHAT A LOAD OF SCARMONGERING ********. I have flashed my various receivers many hundreds even thousands of times with no ill effects what so ever.
There seems to be a complete lack of understanding among newcomers as to how these images work, and why a Flash is necessary and why.
On some forums, they scream for new daily updates, on others why do we have to flash?..... As long as they can get their ***** to work in the receiver they just don,t want to put in a little bit of reading to understand some of the basics:)
Don't tell me I have to reflash! How much reflashing can my duo2 take? It will soon be bricked im sure.
Good job you don't use some other images as they release daily updates :)
The choice of flashing is yours. If you're happy with your current image and you have no problems with it then why update?
There seems to be a complete lack of understanding among newcomers as to how these images work, and why a Flash is necessary and why.
On some forums, they scream for new daily updates, on others why do we have to flash?..... As long as they can get their ***** to work in the receiver they just don,t want to put in a little bit of reading to understand some of the basics:)
As has been noted in the past, in the first two years of ViX you would routinely wait any where from three months to at the longest nine months for a image update to be released and we got bombarded from users who demanded access to updates whether they were tested or not. The system you now have was built specifically to abate those users and the team now get complaints of too many updates. And people wonder why Andy decided to take a back step from ViX ???.
The more I have to use other images(Wetek) the more I am grateful for ViX, it also helps your understanding running your own builds :)
Personally, I think the ViX team should release a new build when they think its valuable and contributes, that might mean sometimes daily, sometimes not for months... People can always run their own builds if they are that impatient .. Or move to another image .. To which I wish them all the best:)
It may not only be an issue of less or more often apearing updated builds. As I wrote before, I rate openVix highly for it's stability and funcionalism :), but I give other images a chance if they have funtions I need (and can not find in VIX image). I realize, that some features strongly depend on the type of the receiver rather then on the image, and even if I use some other image, I very often read this forum to find the news and functions that would let me go back to openVIX.
frozenfire
10-10-15, 16:52
WHAT A LOAD OF SCARMONGERING ********. I have flashed my various receivers many hundreds even thousands of times with no ill effects what so ever.
Scaremongering? I think that you have chosen the wrong word, Who and why am i trying to scare monger? anyhow, I appreciate how much work it takes, I'm a true believer of hard work, especially when it pays off.
The only reason I was worried about constant reflashing was because of reading a post somewhere on this forum stating that we should use a USB stick to store EPG data so we don't keep writing to the internal flash.
And please excuse me when I come across as a newbie, I have read and re-read many posts relating to vix and all the other images and also have basic knowledge of linux etc. Problem is, because I do not apply this knowledge on a regular basis then I forget about it, like most humans. Don't get me wrong I have often solved a problem myself, even complex problems, just from reading forums etc.
I am also the go-to-guy for family and friends when it comes to anything related to technology and computers...
So why do I keep posting newbie questions when most of the answers are here or on the net? Well, you guys respond quicker than I can go through numerous threads looking for the right answer, and when you have two young children and run your own business and are also building your own extension then time is limited, massively limited. I don't have the time I used to.
I have used blackhole and can confirm, it was a nightmare from the word go, I hated it. I will always use VIX and am thankful for the support.
I am just sorry I have to moan every time I have to flash my box, I just don't have the time..... lol.
Andy_Hazza
10-10-15, 18:37
EPG best stored to your HDD.
Sent from my iPhone using Tapatalk
The reason epg data should not be written to the internal flash is so you don't fill up the flash memory and crash the box - it wont reduce the lifespan of the receiver. The hard drive is the best place for it if you have one installed - if not then use a usb stick. Unfortunately some people would believe anything that is written on a forum and there are too many old wives tales going around.
what is the advantage of storing epg on the HDD over the usb drive?
A usb drive may get removed from time to time - a hard drive is generally left in the receiver so there is less likelyhood of any problems. If you remove the usb drive and the receiver attempts to import epg data it will default back to internal flash as the storage device. Other than that I cant see any other reason. So if you have a hard drive then use it. Epg data is held in live memory after being read from the hard drive. Picons on the other hand are best stored on the usb stick as otherwise you will have to wait for the hard drive to spin up every time you change channel.
the reason i asked is because i have heard several times that epg is best stored on HDD, and others maintain that it's best on usb.
i have HDD that i use purely for recordings, i also have a usb stick for epg and picons, so it's never removed.
this works best for me but if theres a better way i'd be open to change.
If you always leave the stick plugged in then there is no reason to change if everything is working fine.
No real need for any USB stick on the Duo2 if it has an internal HDD.
Accidentally upgraded to v.9 from v.7 online as there were no warnings and I hadn't checked here, then read the posts about a fresh flash, after my duo2 started to play up! Fresh flashed to v.10, 24 hours running sweet, no crashes, settings imported no problem, redone plugins and just mindlna needed reconfiguring so well worth the effort. Personally i prefer usb for settings,epg, picons etc as corrupted my hard drive data a few times when ran out of disk space, not a problem since moving all to usb and investing in a 4tb hdd :) Thx to all at Vix for these amazing stable and highly workable images, really appreciated! As others have said, don't bother if everything running stable but when things stop working/won't update, go for it! ;-)
If you're happy with your current image and you have no problems with it then why update?Because all the people that give helpful advice are running the latest image.
Hoopstroops
11-10-15, 12:57
Duo2 sick as a dog after 010 multiple crashing! Lost mounted drives aargh!
Sent from my iPhone using Tapatalk
I now realise my problem relates to my usb external hard drive and possibly not build specific since I came straight from Hades image to the 010 build! If I connect external usb WD passport drive it isn't recognised and it appears as if my internal drive dismounts! In order to get internal hdd back I need then to remove the external drive and power cycle my box since a restart doesn't bring it back! I'm sure the solution to this is obvious to some and I do apologise if it is just me having a blonde moment! All was working fine on final Hades build!
Sent from my iPhone using Tapatalk
abu baniaz
11-10-15, 13:11
Set up the mounts again.
Blue Button > Vix > Mount Manager
Hoopstroops
11-10-15, 13:32
Set up the mounts again.
Blue Button > Vix > Mount Manager
Mount manager causes box to crash when external drive hooked up!
Sent from my iPhone using Tapatalk
Crash = crash log. Please add one to this thread.
Hoopstroops
11-10-15, 18:47
Crash = crash log. Please add one to this thread.
<?xml version="1.0" encoding="utf-8"?>
<openvix>
<enigma2>
<crashdate>Sun Oct 11 13:56:01 2015</crashdate>
<compiledate>Oct 7 2015</compiledate>
<contactemail>andyblac@o2.co.uk</contactemail>
<!-- Please email this crashlog to above address -->
<skin>ViX-Night-HD/skin.xml</skin>
<sourcedate>2015-10-07</sourcedate>
<version>3.0.0</version>
</enigma2>
<image>
<stbmodel>duo2</stbmodel>
<kernelversion>
<![CDATA[
Linux vuduo2 3.13.5 #1 SMP Sat Oct 3 14:29:16 BST 2015 mips GNU/Linux
]]>
</kernelversion>
<kernelcmdline>libata.force=1:1.5Gbps bmem=192M@64M bmem=384M@512M memc1=788M ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs rw rootflags=sync</kernelcmdline>
<nimsockets>NIM Socket 0:</nimsockets>
<imageversion>
<![CDATA[
box_type=vuduo2
build_type=
version=3.2
type=release
build=010
date=20151007171619
comment=OpenViX
target=9
creator=OpenViX
url=http://www.world-of-satellite.com
catalog=http://www.world-of-satellite.com
]]>
</imageversion>
<imageissue>
<![CDATA[
Welcome to OpenViX for %h
openvix 3.2 %h
]]>
</imageissue>
</image>
<crashlogs>
<enigma2crashlog>
<![CDATA[
ionReader] DMX_SET_FILTER pid=265
< 47.835775> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 47.835885> [eDVBSectionReader] DMX_SET_FILTER pid=258
< 47.845471> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 47.845598> [eDVBSectionReader] DMX_SET_FILTER pid=259
< 47.855413> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 47.855729> [eDVBSectionReader] DMX_SET_FILTER pid=260
< 47.865422> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 47.865553> [eDVBSectionReader] DMX_SET_FILTER pid=261
< 47.875580> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 47.875687> [eDVBSectionReader] DMX_SET_FILTER pid=256
< 47.885102> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 47.885240> [eDVBSectionReader] DMX_SET_FILTER pid=262
< 47.895476> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 47.895582> [eDVBSectionReader] DMX_SET_FILTER pid=266
[Dish] tuning failed
[VideoMode] setting aspect: 16:9
[VideoMode] setting wss: auto
[VideoMode] setting policy: panscan
[VideoMode] setting policy2: letterbox
< 48.465629> [eDVBServicePlay] timeshift
< 48.467290> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 48.468743> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 48.468872> [eDVBSectionReader] DMX_SET_FILTER pid=18
< 49.174187> [eEPGCache] start caching events(1444567263)
< 49.175060> [eDVBSectionReader] DMX_SET_FILTER pid=3842
< 49.175582> [eDVBSectionReader] DMX_SET_FILTER pid=3003
< 49.176094> [eDVBSectionReader] DMX_SET_FILTER pid=18
< 49.176984> [eDVBSectionReader] DMX_SET_FILTER pid=18
< 49.178555> [eDVBSectionReader] DMX_SET_FILTER pid=18
< 49.180485> [eDVBSectionReader] DMX_SET_FILTER pid=700
< 49.181887> [eDVBServicePMTHandler] sdt update done!
< 49.190465> [eDVBSectionReader] DMX_SET_FILTER pid=700
< 49.191887> [eDVBSectionReader] DMX_SET_FILTER pid=5000
< 49.192642> [eDVBSectionReader] DMX_SET_FILTER pid=5000
< 49.195162> [eDVBSectionReader] DMX_SET_FILTER pid=57
< 49.468121> [eDVBServicePlay] timeshift
< 49.468471> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
executing opkg --add-dest /:/ list-upgradable
< 49.552406> [eConsoleAppContainer] Starting /bin/sh
< 49.553690> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 70(16)
< 51.371768> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 101(16)
< 52.333513> [eDVBLocalTimerHandler] diff is -2
< 52.333605> [eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
< 52.333634> [eDVBLocalTimerHandler] set RTC Time
< 52.503142> [eDVBLocalTimerHandler] update RTC
< 52.503316> [eDVBLocalTimerHandler] time update to 13:41:05
< 52.503350> [eDVBLocalTimerHandler] m_time_difference is -2
< 52.503374> [eDVBLocalTimerHandler] set Linux Time
< 52.503893> [eDVBChannel] getDemux cap=00
[SoftcamManager] Couldn't find mgcamd.1.38 running, Starting mgcamd.1.38
< 53.482809> [eConsoleAppContainer] Starting /bin/sh
job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None
< 56.195760> [eEPGCache] abort non avail schedule reading
< 56.197449> [eEPGCache] abort non avail schedule other reading
< 56.198494> [eEPGCache] abort non avail virgin nownext reading
< 56.199173> [eEPGCache] abort non avail virgin schedule reading
< 56.199540> [eEPGCache] abort non avail netmed schedule reading
< 56.200221> [eEPGCache] abort non avail netmed schedule other reading
< 56.200591> [eEPGCache] abort non avail viasat reading
< 56.261848> [eEPGCache] nownext finished(1444567269)
[AutoTimer] Auto Poll
[AutoTimer] Auto Poll Started
job Components.Task.Job name=AutoTimer #tasks=0 completed with [] in None
< 365.725439> [eConsoleAppContainer] Starting sdparm
< 367.100776> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 104(16)
[SoftcamManager] mgcamd.1.38 already running
job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None
[SoftcamManager] mgcamd.1.38 already running
job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None
KEY: 352 OK
action -> InfobarShowHideActions toggleShow
< 888.743178> [eDVBServicePlay] timeshift
< 888.743487> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
KEY: 352 OK
KEY: 174 EXIT
action -> InfobarShowHideActions hide
KEY: 174 EXIT
KEY: 393 PVR
KEY: 393 PVR
action -> InfobarActions showMovies
< 890.846559> [eDVBServicePlay] timeshift
< 890.846825> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
[SKIN] processing screen MovieSelection:
[SKIN] processing screen MovieSelectionSummary:
[TRASHCAN DeBug path] /media/sda1/movie/
[TRASHCAN DeBug] /media/sda1/movie/.Trash
setPixmapNum(7) failed! defined pixmaps: [<enigma.gPixmapPtr; proxy of <Swig Object of type 'ePtr< gPixmap > *' at 0x5a482c08> >, <enigma.gPixmapPtr; proxy of <Swig Object of type 'ePtr< gPixmap > *' at 0x5a482cf8> >, <enigma.gPixmapPtr; proxy of <Swig Object of type 'ePtr< gPixmap > *' at 0x5a482d10> >, <enigma.gPixmapPtr; proxy of <Swig Object of type 'ePtr< gPixmap > *' at 0x5a482d28> >, <enigma.gPixmapPtr; proxy of <Swig Object of type 'ePtr< gPixmap > *' at 0x5a482d40> >, <enigma.gPixmapPtr; proxy of <Swig Object of type 'ePtr< gPixmap > *' at 0x5a482d58> >, <enigma.gPixmapPtr; proxy of <Swig Object of type 'ePtr< gPixmap > *' at 0x5a482d70> >]
KEY: 174 EXIT
action -> OkCancelActions cancel
< 899.467937> [eDVBServicePlay] timeshift
< 899.468288> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.468596> [eDVBCAService] free slot 0 demux 0 for service 1:0:1:1E14:809:2:11A0000:0:0:0:
< 899.468678> [eDVBCAService] free service 1:0:1:1E14:809:2:11A0000:0:0:0:
< 899.490775> [eDVBServicePlay] timeshift
< 899.491119> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.493281> [eDVBServicePlay] timeshift
< 899.493591> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.494662> [eTSMPEGDecoder] decoder state: play, vpid=ffffffff, apid=ffffffff
< 899.494756> [eDVBPCR0] DEMUX_STOP ok
< 899.494822> [eDVBPCR0] destroy
< 899.494852> [eDVBVideo0] DEMUX_STOP ok
< 899.495778> [eDVBVideo0] VIDEO_STOP ok
< 899.499455> [eDVBVideo0] destroy
< 899.499513> [eDVBAudio0] AUDIO_STOP ok
< 899.525799> [eDVBAudio0] DEMUX_STOP ok
< 899.525909> [eDVBAudio0] AUDIO_CONTINUE ok
< 899.534781> [eDVBAudio0] destroy
< 899.534823> [eDVBText0] DEMUX_STOP ok
< 899.536636> [eDVBText0] destroy
< 899.540207> [eDVBResourceManager] start release channel timer
playing 1:0:1:1E14:809:2:11A0000:0:0:0:
getResolvedKey config.usage.remote_fallback failed !! (Typo??)
< 899.601578> [eDVBServicePlay] timeshift
< 899.601868> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.612954> [eDVBServicePlay] timeshift
< 899.613333> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.614467> [eDVBServicePlay] timeshift
< 899.614758> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.616467> [eDVBServicePlay] timeshift
< 899.616753> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.617719> [eDVBServicePlay] timeshift
< 899.618046> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.619715> [eDVBServicePlay] timeshift
< 899.619994> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.620987> [eDVBServicePlay] timeshift
< 899.621336> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
RemovePopup, id = ZapError
< 899.623891> [eDVBResourceManager] use cached_channel
< 899.623962> [eDVBResourceManager] stop release channel timer
< 899.623995> [eDVBServicePMTHandler] allocate Channel: res 0
< 899.624322> [eDVBCIInterfaces] addPMTHandler 1:0:1:1E14:809:2:11A0000:0:0:0:
< 899.624389> [eDVBChannel] getDemux cap=00
< 899.624419> [eDVBServicePMTHandler] ok ... now we start!!
< 899.624448> [eDVBServicePlay] eventNewProgramInfo timeshift_enabled=0 timeshift_active=0
< 899.624495> [eDVBServicePlay] have 1 video stream(s) (092a), and 1 audio stream(s) (092b), and the pcr pid is 092a, and the text pid is 092d
< 899.624602> [eDVBChannel] getDemux cap=01
< 899.629509> [eTSMPEGDecoder] decoder state: play, vpid=092a, apid=092b
< 899.629619> [eDVBPCR0] DMX_SET_PES_FILTER pid=0x092a ok
< 899.629674> [eDVBPCR0] DEMUX_START ok
< 899.632931> [eDVBAudio0] DMX_SET_PES_FILTER pid=0x092b ok
< 899.633158> [eDVBAudio0] DEMUX_START ok
< 899.633276> [eDVBAudio0] AUDIO_SET_BYPASS bypass=1 ok
< 899.641321> [eDVBAudio0] AUDIO_PAUSE ok
< 899.645162> [eDVBAudio0] AUDIO_PLAY ok
< 899.651627> [eDVBVideo] Video Device: /dev/dvb/adapter0/video0
< 899.651708> [eDVBVideo] demux device: /dev/dvb/adapter0/demux0
< 899.655987> [eDVBVideo0] VIDEO_SET_STREAMTYPE 0 - ok
< 899.660178> [eDVBVideo0] DMX_SET_PES_FILTER pid=0x092a ok
< 899.660243> [eDVBVideo0] DEMUX_START ok
< 899.660376> [eDVBVideo0] VIDEO_FREEZE ok
< 899.664361> [eDVBVideo0] VIDEO_PLAY ok
< 899.673891> [eDVBText0] DMX_SET_PES_FILTER pid=0x092d ok
< 899.673946> [eDVBText0] DEMUX_START ok
< 899.677700> [eDVBVideo0] VIDEO_SLOWMOTION 0 ok
< 899.681143> [eDVBVideo0] VIDEO_FAST_FORWARD 0 ok
< 899.685821> [eDVBVideo0] VIDEO_CONTINUE ok
< 899.689918> [eDVBAudio0] AUDIO_CONTINUE ok
< 899.698471> [eDVBTeletextParser] Starting!
< 899.698513> [eDVBTeletextParser] disable teletext subtitles page ffffffffffffffff (und)
< 899.698546> [eDVBPESReader] Created. Opening demux
< 899.698573> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 899.698683> [eDVBTeletextParser] created teletext subtitle PES reader!
< 899.698748> [eDVBPESReader] Created. Opening demux
< 899.698777> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 899.698879> [eDVBTeletextParser] starting PES reader on pid=092d
< 899.698919> [eDVBPESReader] DMX_SET_PES_FILTER pid=092d
< 899.699875> [eDVBServicePlay] timeshift
< 899.700224> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.701300> [eDVBServicePlay] timeshift
< 899.701590> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.703292> [eDVBServicePlay] timeshift
< 899.703580> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.703848> [eDVBServicePlay] timeshift
< 899.704185> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.705269> [eDVBServicePlay] timeshift
< 899.705587> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.844723> [eDVBCAService] new service 1:0:1:1E14:809:2:11A0000:0:0:0:
< 899.844821> [eDVBCAService] add demux 0 to slot 0 service 1:0:1:1E14:809:2:11A0000:0:0:0:
< 899.845516> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 899.845661> [eDVBSectionReader] DMX_SET_FILTER pid=0
< 899.869193> [eDVBServicePlay] timeshift
< 899.869474> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 899.911819> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 899.911936> [eDVBSectionReader] DMX_SET_FILTER pid=18
RemovePopup, id = ZapError
< 899.915238> [eDVBChannel] getDemux cap=00
KEY: 174 EXIT
< 900.035700> [eDVBServicePMTHandler] PATready
< 900.035781> [eDVBServicePMTHandler] use pmtpid 0101 for service_id 1e14
< 900.035825> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 900.035904> [eDVBSectionReader] DMX_SET_FILTER pid=257
< 900.036454> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 900.036591> [eDVBSectionReader] DMX_SET_FILTER pid=0
< 900.102414> [eDVBServicePlay] eventNewProgramInfo timeshift_enabled=0 timeshift_active=0
< 900.104237> [eDVBServicePlay] have 1 video stream(s) (092a), and 2 audio stream(s) (092b, 092c), and the pcr pid is 092a, and the text pid is 092d
< 900.104732> [eTSMPEGDecoder] decoder state: play, vpid=092a, apid=092b
< 900.228803> [eDVBCIInterfaces] gotPMT
< 900.228894> [eDVBCAService] don't build/send the same CA PMT twice
< 900.229052> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 900.229162> [eDVBSectionReader] DMX_SET_FILTER pid=257
[Dish] tuning failed
< 900.726208> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 900.726365> [eDVBSectionReader] DMX_SET_FILTER pid=18
< 900.869871> [eDVBServicePlay] timeshift
< 900.870265> [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
KEY: 352 OK
action -> InfobarShowHideActions toggleShow
KEY: 352 OK
KEY: 174 EXIT
action -> InfobarShowHideActions hide
KEY: 174 EXIT
KEY: 139 MENU
action -> InfobarMenuActions mainMenu
[SKIN] processing screen Menu:
[SKIN] processing screen MenuSummary:
KEY: 139 MENU
KEY: 174 EXIT
action -> OkCancelActions cancel
KEY: 174 EXIT
KEY: 401 BLUE
KEY: 401 BLUE
action -> InfobarExtensions extensions
[SKIN] processing screen ChoiceBox:
[SKIN] processing screen ChoiceBox_summary:
KEY: 108 DOWN
action -> WizardActions down
unknown action WizardActions/down! typo in keymap?
action -> WizardActions down
KEY: 108 DOWN
KEY: 108 DOWN
action -> WizardActions down
unknown action WizardActions/down! typo in keymap?
action -> WizardActions down
KEY: 108 DOWN
KEY: 108 DOWN
action -> WizardActions down
unknown action WizardActions/down! typo in keymap?
action -> WizardActions down
KEY: 108 DOWN
KEY: 108 DOWN
action -> WizardActions down
unknown action WizardActions/down! typo in keymap?
action -> WizardActions down
KEY: 108 DOWN
KEY: 352 OK
action -> WizardActions ok
unknown action WizardActions/ok! typo in keymap?
action -> WizardActions ok
[SKIN] processing screen VIXMenu:
[SKIN] processing screen PluginBrowserSummary:
KEY: 352 OK
KEY: 108 DOWN
action -> WizardActions down
unknown action WizardActions/down! typo in keymap?
KEY: 108 DOWN
KEY: 108 DOWN
action -> WizardActions down
unknown action WizardActions/down! typo in keymap?
KEY: 108 DOWN
KEY: 108 DOWN
action -> WizardActions down
unknown action WizardActions/down! typo in keymap?
KEY: 108 DOWN
KEY: 352 OK
action -> WizardActions ok
[SKIN] processing screen VIXDevicesPanel:
[SKIN] processing screen VIXDevicesPanelSummary:
< 912.400086> [eConsoleAppContainer] Starting /bin/sh
new Harddisk sda1 -> /dev/sda1 -> /dev/sda1
< 912.914392> [eConsoleAppContainer] Starting sdparm
KEY: 352 OK
< 912.955409> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 105(16)
< 912.955512> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 108(17)
HOTPLUG connection!
hotplug: ACTION=add
complete ACTION=add
HOTPLUG connection lost!
hotplug: {'ACTION': 'add', 'PHYSDEVPATH': '/block/sr0/device', 'DEVPATH': '/block/sr0'}
main infobar is not execing... so we ignore hotplug event!
HOTPLUG connection!
hotplug: ACTION=add
complete ACTION=add
HOTPLUG connection lost!
hotplug: {'ACTION': 'add', 'PHYSDEVPATH': '/block/sdb/device', 'DEVPATH': '/dev/sdb'}
new Harddisk sdb -> /dev/sdb -> /dev/sdb
< 931.509538> [eConsoleAppContainer] Starting sdparm
< 931.523491> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 104(17)
HOTPLUG connection!
hotplug: ACTION=add
complete ACTION=add
HOTPLUG connection lost!
hotplug: {'ACTION': 'add', 'PHYSDEVPATH': '/block/sda/device', 'DEVPATH': '/dev/sdb1'}
KEY: 174 EXIT
action -> WizardActions back
KEY: 174 EXIT
KEY: 352 OK
action -> WizardActions ok
[SKIN] processing screen VIXDevicesPanel:
[SKIN] processing screen VIXDevicesPanelSummary:
< 948.414842> [eConsoleAppContainer] Starting /bin/sh
new Harddisk sda1 -> /dev/sda1 -> /dev/sda1
< 948.928373> [eConsoleAppContainer] Starting sdparm
Traceback (most recent call last):
File "/usr/lib/enigma2/python/Plugins/SystemPlugins/ViX/MountManager.py", line 94, in updateList2
File "/usr/lib/enigma2/python/Plugins/SystemPlugins/ViX/MountManager.py", line 148, in buildMy_rec
File "/usr/lib/enigma2/python/Components/Harddisk.py", line 144, in diskSize
OSError: [Errno 2] No such file or directory: '/media/sda1'
< 948.937730> [ePyObject] (CallObject(<bound method VIXDevicesPanel.updateList2 of <class 'Plugins.SystemPlugins.ViX.MountManager.VIXDevices Panel'>>,()) failed)
]]>
</enigma2crashlog>
</crashlogs>
</openvix>
Sent from my iPhone using Tapatalk
Hoopstroops
12-10-15, 20:09
Anyone confirm there's an issue with external drives?
Sent from my iPhone using Tapatalk
found solution : seems oscam config was changed.Need to put interface to reading oscam config to yes.
Cant find what to change, aany help appreciated as since update cant view any Oscam stats
IGNORE - FOUND IT
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.