אינדקס
What is a Panic?
A Panic (kernel Panic) mostly occurs by these four reasons:
- The /var is too full - Solution: remove all files in the /var which you don't need, such as plugins, games and emu's
- Wrong database revision - Solution: use the right database version
- If the database is corrupted, then sometimes "ERROR" is displayed on the front panel instead of "PANIC". When this happens, on boot, the corrupted database is used again and then another "ERROR" is displayed. For this case, use USB flash to send a new database.
- If the webinterface is opened when powering on from a previous work session. For example, turn on STB, open webinterface, turn off the decoder and on again.
For info on flashing, see Flash images.
- When the application (or plugin) uses a null pointer. (a simple explanation: a null pointer is a bit of memory that hasn't been claimed by the application and therefor the application cannot use it).
A Panic (kernel Panic) mostly occurs by these four reasons:
- The /var is too full - Solution: remove all files in the /var which you don't need, such as plugins, games and emu's
- Wrong database revision - Solution: use the right database version
- If the database is corrupted, then sometimes "ERROR" is displayed on the front panel instead of "PANIC". When this happens, on boot, the corrupted database is used again and then another "ERROR" is displayed. For this case, use USB flash to send a new database.
- If the webinterface is opened when powering on from a previous work session. For example, turn on STB, open webinterface, turn off the decoder and on again.
For info on flashing, see Flash images.
- When the application (or plugin) uses a null pointer. (a simple explanation: a null pointer is a bit of memory that hasn't been claimed by the application and therefor the application cannot use it).
