Megatron817
Administrator
Got the SF8008 back connected up and flashed 0208 image. Looks good, I now have vfd display setup to show clock always and swapped to alternate display skin. 100% clock now, no letters at all on the front display. Thanks.
TNAP-7 Image Discussion
- Thread starter el bandido
- Start date
Yes, it's working; no more crash.
Thx.
el bandido
TNAP-Images
Analysis of All 5 Crash Logs:
You have TWO DIFFERENT RECEIVERS with TWO DIFFERENT PROBLEMS:
RECEIVER 1: osmini4k (2 crashes)
Crash Logs: 21:20:57 and 21:20:58
---------------------------------
Problem: Missing framebuffer devices - /dev/fb0 not found
Graphics drivers not loading at boot
Enigma2 cannot initialize display
This is a hardware/driver initialization issue
RECEIVER 2: osmio4kplus (3 crashes)
Crash Logs: 17:45:57, 17:46:03, 17:46:13
Problem: SkinSelector Python bug when accessing LCD skins
Root Cause (crash #1 - 17:45:57):
File "/usr/lib/enigma2/python/Screens/SkinSelector.py", line 304, in selectionChanged
TypeError: 'NoneType' object is not subscriptable
--------------------------------------------------
What happened:
1. User navigated to: Menu → LCD Setup → LCD Skin Selector
2. SkinSelector tried to load LCD skins from /usr/share/enigma2/display/
3. Line 128: [SkinSelector] Directory does not exist: /usr/share/enigma2/display
4. Code didn't handle missing directory properly
5. Tried to access None[something] causing TypeError
Secondary crashes (#2 and #3):
Enigma2 tried to show BSOD error screen
Failed because error handler can't open modal dialog from non-modal screen
Cascading failures...
Status: Receiver works fine UNTIL user tries to access LCD skin settings
For the MIO+, LCD skin settings, more enigma2 edits are added to keep this from happening. It is understood that folders or files are being added to the receiver manually to solve this problem. This is fine, but it should not be done right now. The image needs to be proven to work correctly before adding any missing files, else you will have several receivers working correctly, then others crashing. Allow the main or root problem to be fixed first, then add whatever you want.
As for the OSMini4k crashing and failing on boot:
The 0208 image was checked and ran on an osmini4k before the images were uploaded. After the images were uploaded, the osmini4k image was then downloaded again using receiver menus and reinstalled, with settings being automatically restored. No issues were found.
Reload the mini4k image. Just simply reload the image and do not put the first file in it. Reboot it two or three times. Does it work correctly? If the answer is yes, then start installing your files that you want to use. The main difference between the last mini4k image and this one are the python updates, and the preloading of all network drivers that are available. I doubt either one of these are causing the boot failure, but we need to narrow it down and solve it if possible.
You have TWO DIFFERENT RECEIVERS with TWO DIFFERENT PROBLEMS:
RECEIVER 1: osmini4k (2 crashes)
Crash Logs: 21:20:57 and 21:20:58
---------------------------------
Problem: Missing framebuffer devices - /dev/fb0 not found
Graphics drivers not loading at boot
Enigma2 cannot initialize display
This is a hardware/driver initialization issue
RECEIVER 2: osmio4kplus (3 crashes)
Crash Logs: 17:45:57, 17:46:03, 17:46:13
Problem: SkinSelector Python bug when accessing LCD skins
Root Cause (crash #1 - 17:45:57):
File "/usr/lib/enigma2/python/Screens/SkinSelector.py", line 304, in selectionChanged
TypeError: 'NoneType' object is not subscriptable
--------------------------------------------------
What happened:
1. User navigated to: Menu → LCD Setup → LCD Skin Selector
2. SkinSelector tried to load LCD skins from /usr/share/enigma2/display/
3. Line 128: [SkinSelector] Directory does not exist: /usr/share/enigma2/display
4. Code didn't handle missing directory properly
5. Tried to access None[something] causing TypeError
Secondary crashes (#2 and #3):
Enigma2 tried to show BSOD error screen
Failed because error handler can't open modal dialog from non-modal screen
Cascading failures...
Status: Receiver works fine UNTIL user tries to access LCD skin settings
For the MIO+, LCD skin settings, more enigma2 edits are added to keep this from happening. It is understood that folders or files are being added to the receiver manually to solve this problem. This is fine, but it should not be done right now. The image needs to be proven to work correctly before adding any missing files, else you will have several receivers working correctly, then others crashing. Allow the main or root problem to be fixed first, then add whatever you want.
As for the OSMini4k crashing and failing on boot:
The 0208 image was checked and ran on an osmini4k before the images were uploaded. After the images were uploaded, the osmini4k image was then downloaded again using receiver menus and reinstalled, with settings being automatically restored. No issues were found.
Reload the mini4k image. Just simply reload the image and do not put the first file in it. Reboot it two or three times. Does it work correctly? If the answer is yes, then start installing your files that you want to use. The main difference between the last mini4k image and this one are the python updates, and the preloading of all network drivers that are available. I doubt either one of these are causing the boot failure, but we need to narrow it down and solve it if possible.