TNAP-7 Image Discussion

What is the output of lsusb in telnet or putty terminal?
Does this exact same usb stick work in other images? If it does then boot to one of them and run lsusb in terminal for comparison purposes.
The lsusb lists all usb devices connected to the receiver, and is very helpful in solving usb related problems.
 
el bandido said:
What is the output of lsusb in telnet or putty terminal?
Does this exact same usb stick work in other images? If it does then boot to one of them and run lsusb in terminal for comparison purposes.
The lsusb lists all usb devices connected to the receiver, and is very helpful in solving usb related problems.
Click to expand...
Now the tnap doesn load: box display shows "boot", but no pic !
here are the "lsusb" tests from tnap & vix:
 

Attachments

  • vix-lsusb.webp
    vix-lsusb.webp
    34.8 KB · Views: 5
  • tnap-lsusb.webp
    tnap-lsusb.webp
    35.2 KB · Views: 4
???
What does not boot? TNAP-7? Explain as I thought you were using it? If the box does not boot, remove Both usb devices, then try to boot.

Also, your screenshot is labeled vix and the other is tnap? tnap what? tnap-7? I assume you are comparing OpenVix and TNAP-7 which is OK. Just need to clarify as the output is the same, which is good. Thanks.
 
I'm talking about tnap7, as the title of the menu says; if it was about tnap6, I will post in that menu not here.
I run "lsusb" in tnap & openvix images, as you suggested in post #23.
It looks like there are no differences on the output of the command !
Now, tnap7 does not load (as I mentioned in #24), but I can connect to the box: box display shows "boot" & the screen is black !
I'm thinking to do fresh flash.
 
I'm talking about tnap7, as the title of the menu says; if it was about tnap6, I will post in that menu not here.
I run "lsusb" in tnap & openvix images, as you suggested in post #23.
It looks like there are no differences on the output of the command !
Now, tnap7 does not load (as I mentioned in #24), but I can connect to the box: box display shows "boot" & the screen is black !
I'm thinking to do fresh flash.
 
OK thanks for clarifying.
It may not be booting because of the usb drive or the usb wifi. Disconnect both of those and see if it boots.
Wait a bit, probably late this evening or tomorrow and a rebuilt image with updates will be available.
 
Same thing with usb drive, here also on osmini4k. After remove it booted, with shutdown -r now from telnet
I did an update of 3 packages, full reboot and stuck on boot, removed power plug and booted again
 
TNAP-7 Dated 0131 Is on the feeds, and also available at tnapimages.com.
Missing Blindscan module Added. tested on osmini4k
Channel changing crashes Made edits to correct
Revert to TNAP PlutoTV plugin Let's see if that helps
Attempted to fix the wifi issue in OSmini4k.

As for the usb problem and image backup problems in osmini4k, I have no clue. My usb drive works, and I am able to backup images. If the image stops or fails to boot after installing 0131 image, wait 2-3 minutes for everything to stop, then in terminal run:
init 4
ENIGMA_DEBUG_LVL=5 enigma2 > /tmp/debug.log 2>&1
Then navigate to /tmp of the receiver, get debug.log and attach it here.
 
Installed new version, osmini4k-20260131 multiboot.zip

Blindscan works, yellow button works

I have problems with booting, usb removed, above command does not complete

Code: 
TNAP 7 osmini4k

osmini4k login: root
Password:
root@osmini4k:~# init 4
root@osmini4k:~# ENIGMA_DEBUG_LVL=5 enigma2 > /tmp/debug.log 2>&1
Segmentation fault         ENIGMA_DEBUG_LVL=5 enigma2 > /tmp/debug.log 2>&1
root@osmini4k:~#
 
The provided command runs. Segmentation fault error Is Not Good!
My receiver:
Code: 
pli@pli-Precision-T5610:~$ telnet 192.168.1.193

Trying 192.168.1.193...

Connected to 192.168.1.193.

Escape character is '^]'.


TNAP 7 osmini4k


osmini4k login: root

root@osmini4k:~# init 4

root@osmini4k:~# ENIGMA_DEBUG_LVL=5 enigma2 > /tmp/debug.log 2>&1





Corrupted installation/flashing
Hardware issue (bad RAM )
Incompatible plugin causing instant crash


Possible solutions.
Reflash the image cleanly --Do not let autorestore run or restore anything.
Or try a different multiboot slot
 
Back
Top