Show Posts
Hi fullzero,
thank you for keeping this project alive and the constant updates.
I've been running 017 version on z270-hd3p gigabyte motherboard + 3 x 1080TI and a 1070 for almost 2 weeks now with no issues.
meanwhile does anyone have the issue with 018 version not working at all? ewbf does not even start. Most settings have been the same as from the onebash file in 017. Turned off most of the new additional features like watchdog and auto temp.
I've tried booting from an ssd as well as a 32gb sandisk ultra flair thumbdrive; I keep getting the error [Screen is terminating] at the end.
I understand the issue is most likely a configuration somewhere gone wrong, therefore it terminated before even trying to load ewbf miner, but was there such a drastic change from 017 to 018 that I missed out?
Would really like to find out if anyone faced a similar issue, so I iron it out and run ver 018.
Thanks!
thank you for keeping this project alive and the constant updates.
I've been running 017 version on z270-hd3p gigabyte motherboard + 3 x 1080TI and a 1070 for almost 2 weeks now with no issues.
meanwhile does anyone have the issue with 018 version not working at all? ewbf does not even start. Most settings have been the same as from the onebash file in 017. Turned off most of the new additional features like watchdog and auto temp.
I've tried booting from an ssd as well as a 32gb sandisk ultra flair thumbdrive; I keep getting the error [Screen is terminating] at the end.
I understand the issue is most likely a configuration somewhere gone wrong, therefore it terminated before even trying to load ewbf miner, but was there such a drastic change from 017 to 018 that I missed out?
Would really like to find out if anyone faced a similar issue, so I iron it out and run ver 018.
Thanks!
I have received many pm's with similar questions.
I think 2 things may be the case when members have such an experience:
1
LOCALorREMOTE has been set to:
Code:
LOCALorREMOTE="REMOTE"
When this is the case; the miner launches in a screen which is a background process and is not automatically attached to a local terminal.
The purpose of this is to save time when SSHing in (mining process will not need to be restarted; it can just be attached).
If you are using a monitor always ensure:
Code:
LOCALorREMOTE="LOCAL"
or else you will have to manually enter:
Code:
screen -r miner
to attach the mining process to a terminal.
2
SALFTER_NICEHASH_PROFIT_SWITCHING has been set to:
Code:
SALFTER_NICEHASH_PROFIT_SWITCHING="YES"
When this is the case; the mining process launches in the guake terminal (press f12 to open)
when:
LOCALorREMOTE has been set to:
Code:
LOCALorREMOTE="LOCAL"
If:
LOCALorREMOTE has been set to:
Code:
LOCALorREMOTE="REMOTE"
When this is the case; the miner launches in a screen which is a background process and is not automatically attached to a local terminal.
Let me know if '1' is the case; if it not: please post your settings for:
Code:
COIN="ZEC"
SALFTER_NICEHASH_PROFIT_SWITCHING="NO"
Maxximus007_AUTO_TEMPERATURE_CONTROL="YES"
IAmNotAJeep_and_Maxximus007_WATCHDOG="YES"
LOCALorREMOTE="LOCAL"
I had a retard moment (must be the flu) and typed zec instead of zcash for the flypool server address. Everything is up and running fine off an Ssd. Glad it worked.
Thank you for your quick reply and great work.
