View Full Version : ET5000 keeps crashing after trying to get a NFS mount
I've bought a Xtrend ET5000 about a month ago. I wanted to mount a NFS share last week and after some trying I ended up in a crashing ET5000. I installed a Vix image via USB again, updated it to the last version via internet and started over again. But I ran into the same problem. Has anybody encountered the same problem and how to solve it without flashing the ET5000 again?
The last part of the crash log is:
[NTPSync] Poll Started
[SoftcamManager] Poll occured at Thu Sep 22 11:00:43 2011
[OnlineVersionCheck] Downloading RELEASE online version file.
[SoftcamManager] Timer Check Enabled
RemovePopup, id = ZapError
[OnlineVersionCheck] No New online version found
[OnlineVersionCheck] No New online version found
[OnlineVersionCheck] No New online version found
child has terminated
pipes closed
child has terminated
pipes closed
[ePopen] command: route -n | grep eth0
poll: unhandled POLLERR/HUP/NVAL for fd 27(16)
poll: unhandled POLLERR/HUP/NVAL for fd 29(17)
child has terminated
pipes closed
[ePopen] command: None
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/Components/Console.py", line 41, in eBatchCB
File "/usr/lib/enigma2/python/Components/Console.py", line 26, in ePopen
TypeError: execute() argument after * must be a sequence, not NoneType
(PyObject_CallObject(<Tools.BoundFunction.boundFunction instance at 0x16f5170>,(1,)) failed)
getResolvedKey config.plugins.crashlogautosubmit.sendAnonCrashlog failed !! (Typo??)
getResolvedKey config.plugins.crashlogautosubmit.addNetwork failed !! (Typo??)
getResolvedKey config.plugins.crashlogautosubmit.addWlan failed !! (Typo??)
]]>
</enigma2crashlog>
</crashlogs>
</openvix>
Attached the complete crash log. More easy to get from the ET5000 then expected ;)
bobonthejob
22-09-11, 10:26
remove the file /etc/enigma2/automount.xml
and then let it restart...
I think is has something to do with the active flag set to 'false'. Is this bug already reported?
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.