solo won't flash (need help please) vix 2.2

[lumberjack]

Hi

a working box has stopped, sticks on boot

showing green screen, vix spins left hand top corner, then it say loading, then vix spins then loading over and over

Sent him the files to retry but it wont flash.

root_cfe_auto.jffs2 - 40,569 KB - JFFFS file - 21/07/2011

this is the error log, appreciate if anyone can throw any light on the matter please
================================================


<?xml version="1.0" encoding="utf-8"?>
<openvix>
<enigma2>
<crashdate>Sat Jan 1 00:01:05 2000</crashdate>
<compiledate>Jul 21 2011</compiledate>
<contactemail>vixlogs@world-of-satellite.com</contactemail>

<skin>Default Skin</skin>
<sourcedate>Jul 21 2011</sourcedate>
<branch>(no branch)</branch>
<rev></rev>
<version></version>
</enigma2>
<image>
<dreamboxmodel>dm500hd</dreamboxmodel>
<kernelcmdline>rootfstype=jffs2 root=/dev/mtdblock0 rw mem=0x8000000 console=ttyS0,115200</kernelcmdline>
<nimsockets>NIM Socket 0:</nimsockets>
<imageversion>
<![CDATA[
box_type=vusolo
build_type=0
version=2.2.100
date=20110721101727
comment=ViX
target=9
creator=Team ViX
url=http://www.vuplus-support.co.uk
catalog=http://www.vuplus-support.co.uk
]]>
</imageversion>
<imageissue>
<![CDATA[
Welcome to ViX for %h
ViX v2.2
]]>
</imageissue>
</image>
<software>
<enigma2software>
<![CDATA[
Collected errors:
* opkg_conf_init: Could not create lock file /usr/lib/opkg/lock: No space left on device.
]]>
</enigma2software>
<vuplussoftware>
<![CDATA[
Collected errors:
* opkg_conf_init: Could not create lock file /usr/lib/opkg/lock: No space left on device.
]]>
</vuplussoftware>
<xtrendsoftware>
<![CDATA[
Collected errors:
* opkg_conf_init: Could not create lock file /usr/lib/opkg/lock: No space left on device.
]]>
</xtrendsoftware>
<gstreamersoftware>
<![CDATA[
Collected errors:
* opkg_conf_init: Could not create lock file /usr/lib/opkg/lock: No space left on device.
]]>
</gstreamersoftware>
</software>
<crashlogs>
<enigma2crashlog>
<![CDATA[
+ (1) Background File Eraser
+ (5) main http server
[NET] httpd server started on port 8080
+ (5) Tuxtxt
+ (8) graphics acceleration manager
+ (9) GFBDC
10800k video mem
- double buffering available!
5040kB available for acceleration surfaces.
resolution: 720 x 576 x 32 (stride: 5120)
+ (9) gLCDDC
found OLED display!
lcd buffer 0x6f7ad0 8448 bytes, stride 132
+ (9) Font Render Class
[FONT] initializing lib...
[FONT] loading fonts...
[FONT] Intializing font cache, using max. 4MB...
+ (10) gRC
RC thread created successfully
+ (15) eWindowStyleManager
+ (20) DVB-CI UI
+ (20) Hdmi CEC driver
+ (20) UHF Modulator
couldnt open /dev/rfmod0!!!!
+ (20) RC Input layer
+ (20) misc options
+ (20) AVSwitch Driver
+ (21) input device driver
Input device "dreambox advanced remote control (native)" is not a keyboard.
Found 1 input devices!
+ (21) Console RC Driver
failed to open /dev/vc/0
+ (30) eActionMap
+ (35) CI Slots
scanning for common interfaces..
CI Slot 0 setSource(0)
CI Slot 1 setSource(0)
eDVBCIInterfaces->setInputSource(0, 0)
eDVBCIInterfaces->setInputSource(1, 1)
cannot open /proc/stb/tsmux/input2
cannot open /proc/stb/tsmux/input3
done, found 2 common interface slots
+ (35) CA handler
+ (40) eServiceCenter
settings instance.
+ (41) eServiceFactoryDVD
+ (41) eServiceFactoryM2TS
eServiceFactoryM2TS aborted, no /usr/lib/libpassthrough.so
+ (41) eServiceFactoryMP3
+ (41) eServiceFactoryFS
+ (41) eServiceFactoryDVB
reached rl 70
---- opening lame channel db
reading services (version 4)
loaded 984 services
scanning for frontends..
opening frontend 0
detected satellite frontend
close frontend 0
found 1 adapter, 1 frontends(1 sim) and 5 demux, boxtype 2
RTC not ready... wait for transponder time
[EPGC] Initialized EPGCache (wait for setCacheFile call now)
Loading spinners...
found 19 spinner!

setIoPrio best-effort level 3 ok
main thread is non-idle! display spinner!
enumerating block devices...
new Harddisk sda -> /dev/sda -> /dev/sda
[ePopen] command: ('hdparm', 'hdparm', '-S0', '/dev/sda')
Traceback (most recent call last):
File "/usr/lib/enigma2/python/mytest.py", line 27, in <module>
import Screens.InfoBar
File "/usr/lib/enigma2/python/Screens/InfoBar.py", line 4, in <module>
File "/usr/lib/enigma2/python/Screens/MovieSelection.py", line 1, in <module>
File "/usr/lib/enigma2/python/Screens/Screen.py", line 4, in <module>
File "/usr/lib/enigma2/python/Components/GUISkin.py", line 1, in <module>
File "/usr/lib/enigma2/python/Components/GUIComponent.py", line 1, in <module>
File "/usr/lib/enigma2/python/skin.py", line 71, in <module>
IOError: [Errno 28] No space left on device: '/usr/share/enigma2/ViX_HD/skin.xml.tmp'
---- saving lame channel db
FATAL: couldn't save lame channel db!
]]>
</enigma2crashlog>
</crashlogs>
</openvix>

[judge]

IOError: [Errno 28] No space left on device: '/usr/share/enigma2/ViX_HD/skin.xml.tmp'
---- saving lame channel db
FATAL: couldn't save lame channel db!

Suggests that the flash is full.
What's happening when he tries to reflash?

[lumberjack]

that's when the error is happening.

because of a stuck box I sent him the files which has correctly placed on pen drive.
He reboots with it in front slot but the box does not go orange/red whilst flashing.

The pen drive lights up then stops and the box itself just boots as normal (then stays on the loop)
So it is not taking the flash

I had the same thing happen to me once when I tried by accident to flash a duo with THAT same "solo" image
it just ignored the pen drive it and rebooted.

In this case though it's a solo and the image is for a solo

[Larry-G]

The pen drive lights up then stops and the box itself just boots as normal (then stays on the loop)
So it is not taking the flash

It would appear that the receiver is not correctly picking up that particular USB stick, Vu receivers are known to be picky with the USB sticks they will work with to flash images etc, try another or several others just to be sure.



I had the same thing happen to me once when I tried by accident to flash a duo with THAT same "solo" image
it just ignored the pen drive it and rebooted.

In this case though it's a solo and the image is for a solo

In that case you are very very lucky, because if the receiver had correctly recognized the Stick and flashed the Solo bootloader to the Duo you would have permanently killed your receiver.

[lumberjack]

It would appear that the receiver is not correctly picking up that particular USB stick, Vu receivers are known to be picky with the USB sticks they will work with to flash images etc, try another or several others just to be sure.

I believe he has tried three but I am posting one I use tomorrow just to be sure.


In that case you are very very lucky, because if the receiver had correctly recognized the Stick and flashed the Solo bootloader to the Duo you would have permanently killed your receiver.

Yes indeed, twas a senior moment lol

[lumberjack]

he has tried different pen drives but no joy

sending back so will get tomorrow and advise once I use one of my pen drives that i used on it before sending.

thanks

[lumberjack]

received it today and flashed instantly so it was down to his different pen drives
3 the same from 7dayshop + another wou8ld not work for him.

sending him mine, annoying though £24.50 special delivery post each way ouch

[Larry-G]

tell him to buy a few cheap Sandisk cruzor blade USB sticks. I use half a dozen and every one of them work flawlessly on my 3 Vu receivers.

[judge]

I have a bunch of USB sticks, lots of cheap makes & none have failed me yet.
Always grab the nearest for a reflash & never had an issue.

[cactikid]

can i ask something i see in crash log it mentioned a dreambox ?
dreamboxmodel>dm500hd</dreamboxmodel>:confused: