Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Page 2 of 12 FirstFirst 1234 ... LastLast
Results 16 to 30 of 177

Thread: VU+ Solo 2 - VIX image Hades / VIX 3.2 - Crashing

  1. #16

    Title
    Member
    Join Date
    Jan 2014
    Location
    Spain
    Posts
    55
    Thanks
    5
    Thanked 4 Times in 4 Posts
    Hi Sicilian, could you please move this thread to the right place, please.
    Thank you.
    Vu+ Solo2

  2. #17

    Title
    ViX Beta Tester
    Join Date
    Jan 2011
    Posts
    14,099
    Thanks
    3,389
    Thanked 4,102 Times in 3,198 Posts
    Quote Originally Posted by Davitat View Post
    Sorry to say, but it finally crashed (v. 3.2.013) with again same error message.
    One little difference is before this error message I've got another one for a few seconds but no time to read, just something to do with softcam.

    Strangely, it run hours before crashing but after this first crash I reloaded some images made during the afternoon which crashed after very few minutes. Very strange.
    Which cam are you using?

  3. #18

    Title
    Member
    Join Date
    Jan 2014
    Location
    Spain
    Posts
    55
    Thanks
    5
    Thanked 4 Times in 4 Posts
    Hi scar0x,
    Does v. 3.2.013 solved the problem for you?
    Vu+ Solo2

  4. #19

    Title
    Member
    Join Date
    Jan 2014
    Location
    Spain
    Posts
    55
    Thanks
    5
    Thanked 4 Times in 4 Posts
    Quote Originally Posted by judge View Post
    Which cam are you using?
    Hi judge, thanks for your help.

    I use cccam221(2.2.1-r5).
    I've used this cam for a long time without a problem. In fact, the 'big crash' I got as described by scar0x (no more ftp, nor telnet, no more plugins, etc. with the error message he reported) produced earlier this week with v. 3.2.010 and without any cam as I've tried lots of configs during days as I explain in my early posts.
    Vu+ Solo2

  5. #20

    Title
    ViX Beta Tester
    Join Date
    Jan 2011
    Posts
    14,099
    Thanks
    3,389
    Thanked 4,102 Times in 3,198 Posts
    Quote Originally Posted by Davitat View Post
    I use cccam221(2.2.1-r5).
    I've used this cam for a long time without a problem. In fact, the 'big crash' I got as described by scar0x (no more ftp, nor telnet, no more plugins, etc. with the error message he reported) produced earlier this week with v. 3.2.010 and without any cam as I've tried lots of configs during days as I explain in my early posts.
    Maybe not a cam issue so. However cccam221 isn't suitable for current images on multi tuner boxes.

  6. #21

    Title
    Member
    Join Date
    Jan 2014
    Location
    Spain
    Posts
    55
    Thanks
    5
    Thanked 4 Times in 4 Posts
    Quote Originally Posted by judge View Post
    Maybe not a cam issue so. However cccam221 isn't suitable for current images on multi tuner boxes.
    I just have one tuner (Solo 2).
    In fact it seems like the crash is corrupting the flash memory and the only thing you can do after that is to flash it again.
    But more strangely, after having had this crash one of the first things I do was to go back to backuped images of prior versions that worked (I tried back to Apollo 166), and this versions working in the past, now crashed (exactly same 'big crash')!

    Is like something get changed and 'memorized' or an hardware problem.
    So I flashed the legacy Vu+ image and had no crashes (but I cant be sure because they are random and can come after more than ten hours working ok).
    Then I googled and find this thread with exactly the same error that make me think it wasn't an hardware problem.
    Vu+ Solo2

  7. #22
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,541
    Thanks
    6,517
    Thanked 9,224 Times in 6,287 Posts
    The Solo 2 is a twin tuner receiver.

  8. #23

    Title
    Member
    Join Date
    Jan 2014
    Location
    Spain
    Posts
    55
    Thanks
    5
    Thanked 4 Times in 4 Posts
    Quote Originally Posted by judge View Post
    Maybe not a cam issue so. However cccam221 isn't suitable for current images on multi tuner boxes.
    Ah, and of course, nothing plugged into the usb ports and I reformatted my hdd to be sure that nothing could 'hide' there.
    Is there some areas of internal flash (low level drivers or so) that can be changed and not updated by the images? (try to understand where a change could had been made ans memorized).
    Vu+ Solo2

  9. #24

    Title
    Member
    Join Date
    Jan 2014
    Location
    Spain
    Posts
    55
    Thanks
    5
    Thanked 4 Times in 4 Posts
    Excuse me, you are right. But I dont think it has something to do with softcams because as I've explained I had this crash also without any cam.
    Vu+ Solo2

  10. #25
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,541
    Thanks
    6,517
    Thanked 9,224 Times in 6,287 Posts
    Are you able to get a crash log from /home/root/logs/ ? If so, please upload as an attachment.

    Purely speculation here, do you get the crash without the USB tuner?

  11. #26

    Title
    Member
    Join Date
    Jan 2014
    Location
    Spain
    Posts
    55
    Thanks
    5
    Thanked 4 Times in 4 Posts
    Quote Originally Posted by abu baniaz View Post
    Are you able to get a crash log from /home/root/logs/ ? If so, please upload as an attachment.

    Purely speculation here, do you get the crash without the USB tuner?
    Hi,
    Sorry but impossible to have access to the box after the crash so impossible to get logs (look please to the #6 post of this thread by scar0x with pictures).
    And yes I got this crash without any usb tuner (dvb-t) connected, nor any usb-dvb-xxx driver installed.
    Vu+ Solo2

  12. The Following User Says Thank You to Davitat For This Useful Post:

    abu baniaz (17-10-15)

  13. #27

    Title
    Member
    Join Date
    Jan 2014
    Location
    Spain
    Posts
    55
    Thanks
    5
    Thanked 4 Times in 4 Posts
    Quote Originally Posted by abu baniaz View Post
    Are you able to get a crash log from /home/root/logs/ ? If so, please upload as an attachment.

    Purely speculation here, do you get the crash without the USB tuner?
    How can I redirect the logs to the hdd in order to preserve them?
    Vu+ Solo2

  14. #28
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,541
    Thanks
    6,517
    Thanked 9,224 Times in 6,287 Posts
    In the logs settings.

    Menu > Setup > System > Logs > Settings > Logs location

  15. The Following User Says Thank You to abu baniaz For This Useful Post:

    Davitat (17-10-15)

  16. #29

    Title
    Member
    Join Date
    Jan 2014
    Location
    Spain
    Posts
    55
    Thanks
    5
    Thanked 4 Times in 4 Posts
    Quote Originally Posted by abu baniaz View Post
    In the logs settings.

    Menu > Setup > System > Logs > Settings > Logs location
    Oooops! Excuse me, it was in settings... I thought I had to create some sort of link. This OpenVix is fantastic, he has everything we can need
    Ok, I'll make some tests and report the logs here.

    Thank you very much.
    Vu+ Solo2

  17. #30

    Title
    Member
    Join Date
    Jan 2014
    Location
    Spain
    Posts
    55
    Thanks
    5
    Thanked 4 Times in 4 Posts
    Bad news...
    I've changed Logs Location to hdd and also activated 'debug mode'.

    I had 2 crashes with v.3.2.013 but every time the '/media/hdd/logs' was empty!
    First time I thought that perhaps for some reason, software have had no time to write log data before the program hanged, but it'worse... At the second crash I had some debug log files into '/media/hdd/logs' before the crash and they where wiped after the crash. Blank directory, nothing.

    Crazy.
    If not because the creator of this thread reported exactly the same issue, I'll would think that this is an hardware random problem.
    Any idea?
    Vu+ Solo2

Page 2 of 12 FirstFirst 1234 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.