Quote from: MentalNomad on November 05, 2017, 09:10:44 PM

Quote from: maxvan1 on November 04, 2017, 03:32:08 AM

Quote

Try

Code:

screen -list

To get a list of active screens. What does that give you?

It gives me:

Code:

No sockets found in /var/run/screen/S-m1.

Definitely no miners to be opened on other screens, then... I have my only AMD rig racked and headless right now, but when I have it out on the bench, I'll see if I can figure out how to help.

Is it throwing any errors? And did you make any mods to oneBash besides setting your coin/address/wallet? You're mining ETH, right? (I'm guessing from the Claymore versions you mention.)

Afterthought:

Set oneBash for Claymore, but turn on logging by doing it like this:

Code:

GENOILorCLAYMORE="CLAYMORE" # choose GENOIL or CLAYMORE

ETH_WORKER="$IP_AS_WORKER"
ETH_ADDRESS="youraddress"
ETH_POOL="yourpool"
ETH_EXTENTION_ARGUMENTS=" -dbg 0" # add any additional claymore arguments desired here

The -dbg 0 will tell Claymore's debugger to turn on some basic logging.

Reboot and let it fire up.

Then, go look in the folder:
/home/m1/eth/10_1/
for files named like this:

1509915035_log.txt

These log files will show you if Claymore is starting up properly, or crapping out, or what. If there are NO log files, then Claymore isn't trying to start at all, and the problem is somewhere else.

There is a problem I have found when using 7 or more GPUs; x will not start. This prevents the auto start execution code from running when the rig boots. To get it going one can either use:

Code:

ctrl + alt + f1

to enter console mode then login in as:

Code:

m1

miner1

then manually launch 2unix or oneBash.

or you can ssh in and manually launch 2unix or 1bash

I know this is very annoying; but it does work and is a work around for this version.

the other problem involved when using 7 or more GPUs in this version is at first boot the oneBash in the windows partition will not be copied to the home folder so you will have to manually do this. The easiest way should be to manually run the cmd:

Code:

bash 2unix

on the first boot.

You can also boot the usb or SSD on another rig and it will copy the oneBash over. Then shutdown and attach that usb or ssd to the intended rig and manually launch 2unix or oneBash.

Code:

bash 2unix

or

Code:

bash oneBash