-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
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
Linux - suddenly exits nanominer after launching #428
Comments
Heres the coredump from the systemctl service, no core is dumped due to some default system settings when running from the cmdline.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
trying to run this on Arch-Linux and getting exit code 139, and SIGSEGV segmetntation (segfault) fault error 4 in
libc.so.6
What's weird is I have working nanominers with the same coins on EndeavourOS, an Arch based distro. With the same parameters, i also have these parameters working on a windows machine through cmd. So i feel like this should be solveable, im just unsure at this point what could be causing the issue
i've attached the logs from
journalctl
and the console output of nanominer when it worksArch_Server_NanoMiner_Journal.log
Arch_Server_NanoMiner.log
What Happens:
Launching from the cmd line, nanominer makes it to the "Detected 2 devices" line then abruptly exits. Sometimes if run immediately after rebooting and logging on, the program runs for a few seconds then exits, the
Arch_Server_NanoMiner.log
file has the console output of what happened, just before crashing it complains aboutAMD platform initialization hang up
When launching as a service it appears it just abruptly exits shortly after starting, very little is logged. The
..._Journal.log
file attached displays what little info is garnered from the service, namely a coredump and segfault error 4 mentioninglibc.so.6
The text was updated successfully, but these errors were encountered: