We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enigma2 (e2)
13.1 (Python 3)
r549 (13.1)
atemionemesis
Atemio Nemesis - Image does boot to 49% and telnet is working, but it's stuck there. I tried all available images.
Unfortunately it also doesn't work if I install it via Openmultiboot or any other method. It's stuck before enigma2 loads.
Flash the image, the led will blank and access is only via ftp and telnet possible. After hard reset the LED is back on and it boots to 49%.
I also tried it without LAN or stick in internal flash, same issue. It is not obvious what the issue is, the logs are below.
How can I fix that?
init 4&& sleep 5&& ENIGMA_DEBUG_LVL=4 enigma2 Result: https://pastebin.com/DDK4AxfW dmesg Result: https://pastebin.com/cXpxq5xU /var/log/messages Result: https://pastebin.com/nxAbW2h6
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
OV image type
Enigma2 (e2)
OV version
13.1 (Python 3)
OV revision
r549 (13.1)
STB name
atemionemesis
Describe the bug and expected behavior
Atemio Nemesis - Image does boot to 49% and telnet is working, but it's stuck there. I tried all available images.
Unfortunately it also doesn't work if I install it via Openmultiboot or any other method. It's stuck before enigma2 loads.
Steps to reproduce
Flash the image, the led will blank and access is only via ftp and telnet possible. After hard reset the LED is back on and it boots to 49%.
I also tried it without LAN or stick in internal flash, same issue. It is not obvious what the issue is, the logs are below.
How can I fix that?
Enigma2 logs
Screenshot
No response
The text was updated successfully, but these errors were encountered: