Octagon SF8 crashing after manual scan

[mmoloch]

Just finish installing the latest openvix version and updated the satellite.xml with the XML Notepad, sent it to the receiver via FTP and restarted E2.

Now I'm doing manual scans to all sats, when the manual scan ends and I click on the green button to store the receiver crash...

Any ideas?

[Sicilian]

Can you post the crashlog please. Will be in /home/logs/

[mmoloch]

Can you post the crashlog please. Will be in /home/logs/

My last crashlog:




I found that after a manual scan and a crash when the receiver turns back on if I go directly to the menu and do another manual scan the receiver will crash again when clicking the green button... but when the receiver turns back on if I first change the channel using Channel UP/DOWN key and then enter the menu for scanning the receiver don't crash after the green button...

[Sicilian]

Add the log as an attachment.

Re-flash build 775, tested here and scanned fine.

[Larry-G]

Just finish installing the latest openvix version and updated the satellite.xml with the XML Notepad, sent it to the receiver via FTP and restarted E2.

Now I'm doing manual scans to all sats, when the manual scan ends and I click on the green button to store the receiver crash...

Any ideas?

There is no need for you to touch the satellites.xml file in the image now adays as we build our own from our own database which is updated on every image update.

our satellites.xml file is built from our own site here. http://satellites-xml.org/

now where did you FTP the satellites.xml file to on the receiver and do you have a copy of the crash logs that accompany these incidents ?.

[mmoloch]

All my crash logs:

enigma2_crash_1383612751.log
enigma2_crash_1383612173.log
enigma2_crash_1383611097.log
enigma2_crash_1383610685.log
enigma2_crash_1383609791.log
enigma2_crash_1383602299.log
enigma2_crash_1383601375.log
enigma2_crash_1383600657.log
enigma2_crash_1383613147.log

There is no need for you to touch the satellites.xml file in the image now adays as we build our own from our own database which is updated on every image update.

our satellites.xml file is built from our own site here. http://satellites-xml.org/

now where did you FTP the satellites.xml file to on the receiver and do you have a copy of the crash logs that accompany these incidents ?.

The first image I tested used a satellite.xml from lyngsat completely out of date so I updated it using XML Notepad, only have sats and beams that I can capture in Portugal.

Used DCC to send it to the receiver... /etc/tuxbox/satellites.xml

[Larry-G]

The first image I tested used a satellite.xml from lyngsat completely out of date so I updated it using XML Notepad

Which image and build number exactly ?.

Used DCC to send it to the receiver... /etc/tuxbox/satellites.xml

You should not be touching the satellites.xml file in this location as it is the "master" file which is updated with the image, touching this file can easily corrupt it. Instead if you want to use a custom satellites.xml file you should FTP it directly to /etc/enigma2/ then reboot the receiver.

Once the receiver has booted back up it will default to this new "user" file, if you later decide to remove this file the image will again default to it's "master" file once rebooted. Another thing is how your editing the file, using notepad can corrupt the file, best use Notepad++ for editing .xml files. you can get a copy from here.

http://notepad-plus-plus.org/

[mmoloch]

Which image and build number exactly ?.

The first image I tested was not Openvix, (OpenPLi-4.0-beta-xp1000-20131101_usb.zip) was always crashing.

You should not be touching the satellites.xml file in this location as it is the "master" file which is updated with the image, touching this file can easily corrupt it. Instead if you want to use a custom satellites.xml file you should FTP it directly to /etc/enigma2/ then reboot the receiver.

Once the receiver has booted back up it will default to this new "user" file, if you later decide to remove this file the image will again default to it's "master" file once rebooted. Another thing is how your editing the file, using notepad can corrupt the file, best use Notepad++ for editing .xml files. you can get a copy from here.

http://notepad-plus-plus.org/

I'm still learning how Enigma 2 work , in a few days I'll do a fresh install of Openvix and follow your suggestions.

[mmoloch]

There is no need for you to touch the satellites.xml file in the image now adays as we build our own from our own database which is updated on every image update.

our satellites.xml file is built from our own site here. http://satellites-xml.org/

now where did you FTP the satellites.xml file to on the receiver and do you have a copy of the crash logs that accompany these incidents ?.

I did a quick check of the original satellites.xml from the 775 build and is not updated, Hispasat 30ºW have TP's out dated for more than three months...