Help - Duo won't boot

[Morini]

This happened over the weekend and I got round it by reflashing to VIX 1.3, doing an internet update and setting everything up from scratch. However, I have just had a repeat of exactly the same problem. The VU will boot up as far as the "loading enigma II" screen but doesn't get any further. I can ssh to the box and here are the last lines in /var/log/messages

Jan 1 00:18:49 vuplus user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0
Jan 1 00:18:49 vuplus user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 1
Jan 1 00:18:49 vuplus user.warn kernel: [VID]: VIDEO_PLAY 1 2 0
Jan 1 00:18:49 vuplus user.warn kernel: [VID]: VIDEO_CONTINUE 1 1
Jan 1 00:18:49 vuplus user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 1 1 0
Jan 1 00:18:49 vuplus user.warn kernel: [VID]: VIDEO_STOP 0 1
Jan 1 00:18:49 vuplus user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0
Jan 1 00:18:50 vuplus user.warn kernel: [CI]:ci_dev_release
Jan 1 00:18:50 vuplus user.warn kernel: [CI]:ci_dev_release
Jan 1 00:18:50 vuplus user.warn kernel: [CI]:ci_dev_open
Jan 1 00:18:50 vuplus user.warn kernel: [CI]:ci1_dev_open
Jan 1 00:18:50 vuplus user.warn kernel: [CI]:NEXUS_Remux_Start
Jan 1 00:18:50 vuplus user.warn kernel: [CI]:>>close_mpod tuner:0
Jan 1 00:18:50 vuplus user.warn kernel: [CI]:remux stop
Jan 1 00:18:50 vuplus user.warn kernel: [CI]:get_remux_startcnt() count : 0
Jan 1 00:18:50 vuplus user.warn kernel: [CI]:get_remux_startcnt() count : 0
Jan 1 00:18:50 vuplus user.warn kernel: [CI]:>>close_mpod tuner:1
Jan 1 00:18:50 vuplus user.warn kernel: [CI]:remux stop
Jan 1 00:18:50 vuplus user.warn kernel: [CI]:get_remux_startcnt() count : 0
Jan 1 00:18:50 vuplus user.warn kernel: [CI]:get_remux_startcnt() count : 0
Jan 1 00:18:51 vuplus user.err kernel: [DFP]: unknown cmd 0x0000
Jan 1 00:18:51 vuplus user.err kernel: [DFP]: unknown cmd 0x0009
Jan 1 00:18:56 vuplus user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0
Jan 1 00:18:56 vuplus user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 1
Jan 1 00:18:56 vuplus user.warn kernel: [VID]: VIDEO_PLAY 1 2 0
Jan 1 00:18:56 vuplus user.warn kernel: [VID]: VIDEO_CONTINUE 1 1
Jan 1 00:18:56 vuplus user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 1 1 0
Jan 1 00:18:56 vuplus user.warn kernel: [VID]: VIDEO_STOP 0 1
Jan 1 00:18:56 vuplus user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0
Jan 1 00:18:57 vuplus user.warn kernel: [CI]:ci_dev_release
Jan 1 00:18:57 vuplus user.warn kernel: [CI]:ci_dev_release
Jan 1 00:18:57 vuplus user.warn kernel: [CI]:ci_dev_open
Jan 1 00:18:57 vuplus user.warn kernel: [CI]:ci1_dev_open
Jan 1 00:18:57 vuplus user.warn kernel: [CI]:NEXUS_Remux_Start
Jan 1 00:18:57 vuplus user.warn kernel: [CI]:>>close_mpod tuner:0
Jan 1 00:18:57 vuplus user.warn kernel: [CI]:remux stop
Jan 1 00:18:57 vuplus user.warn kernel: [CI]:get_remux_startcnt() count : 0
Jan 1 00:18:57 vuplus user.warn kernel: [CI]:get_remux_startcnt() count : 0
Jan 1 00:18:57 vuplus user.warn kernel: [CI]:>>close_mpod tuner:1
Jan 1 00:18:57 vuplus user.warn kernel: [CI]:remux stop
Jan 1 00:18:57 vuplus user.warn kernel: [CI]:get_remux_startcnt() count : 0
Jan 1 00:18:57 vuplus user.warn kernel: [CI]:get_remux_startcnt() count : 0
Jan 1 00:18:58 vuplus user.err kernel: [DFP]: unknown cmd 0x0000
Jan 1 00:18:58 vuplus user.err kernel: [DFP]: unknown cmd 0x0009
Jan 1 00:19:03 vuplus daemon.info init: Id "e2" respawning too fast: disabled for 5 minutes

Anybody suggest how I can get going again? I really don't want to reflash again unless I absolutely have to.

Thanks in advance.

[jjp2701]

if i was you, i would factory reset, then reflash, with the latest original vu+duo firmware, after u have put the latest original one on, then reflash again with which image you want to use, then all should be good, i done this because i was having probs with alot of images, so i decided to do this and now all is well m8, i think sometimes when u flash, and then reflash with something else, it leaves stuff behind, people say it doesnt, but i think it does, so try this method m8, it only takes about 20 mins to do it all, and sat list and config and stuff, good luck m8

[Morini]

Thanks for the suggestion, but how do I do a factory rest when the box won't boot to the gui? I only have access via telnet / ssh currently.

[jjp2701]

then i would suggest putting the latest original firmaware on usb stick, then put it in front usb, turn box off on the back then turn on let it reflash the original one, then look for factory reset after it hasinstalled then put what image u r using, by the same method, and put all your stuff in like sat list config and the rest, all should be good then m8

[Morini]

OK, I'll give this a go. Lucky I am working from home today ;-)

[Morini]

Well, I flashed back to original, did a factory reset then flashed vix 1.3 again. All working at the moment, but then again it worked after I reflashed on the weekend so I'm not that hopeful it will stay working. Box is quite new and vix 1.3 is the only image I have run on it.

[silverfox0786]

when you flashed vix did you do it via usb and before anything else perform a full software update to get all the recent bug fixes

[Morini]

when you flashed vix did you do it via usb and before anything else perform a full software update to get all the recent bug fixes

Yes, did the online software update straight after flashing VIX 1.3 every time (3 times in total now).

[Sicilian]

Yes, did the online software update straight after flashing VIX 1.3 every time (3 times in total now).

Well your Duo must be booting if you managing to do software update! Have you scanned or transferred any Enigma 2 settings/bouquets?

[Morini]

Well your Duo must be booting if you managing to do software update! Have you scanned or transferred any Enigma 2 settings/bouquets?

Well it was always "booting" to the stage where I could ssh to it and get a shell, but the gui would not start and I'd just get the bootlogo with the vix spinners. The only way I could recover was reflash and set everything up from scratch. Reading another thread on here (in the vix image forum) I am wondering whether my problem has anything to do with having the swapfile on usb? Someone else was complaining that their box would hang with swapfile set up on usb.

Anyway,the problem has not reoccured since the last reflash. But then again the box has only been put into standby, not deep standby.