[OS] nvOC easy-to-use Linux Nvidia Mining

[Godm0de]

When I run dmesg, I got a lot of those lines:

Code:

[133920.746977] nvidia-modeset: Freed GPU:5 (GPU-12f9f4a9-0b6a-feef-b2d6-93e0ce5428cd) @ PCI:0000:09:00.0
[133920.901801] nvidia-modeset: Freed GPU:4 (GPU-15387c93-2a5d-b45c-77b0-cb88e629425e) @ PCI:0000:08:00.0
[133921.032925] nvidia-modeset: Freed GPU:3 (GPU-c6762bb7-6a0e-486b-6878-ecfc6eb1f7ef) @ PCI:0000:07:00.0
[133921.142072] nvidia-modeset: Freed GPU:2 (GPU-f256d3d8-c898-c915-3106-76e808cc362e) @ PCI:0000:06:00.0
[133921.236166] nvidia-modeset: Freed GPU:1 (GPU-a3452d3f-ed35-5125-c8af-481622d9adf9) @ PCI:0000:03:00.0
[133922.043551] nvidia-modeset: Freed GPU:0 (GPU-df08cdf1-b3ff-f312-4a54-74f401f5e4be) @ PCI:0000:01:00.0
[133973.039094] nvidia-modeset: Allocated GPU:0 (GPU-df08cdf1-b3ff-f312-4a54-74f401f5e4be) @ PCI:0000:01:00.0
[133973.694116] nvidia-modeset: Allocated GPU:1 (GPU-a3452d3f-ed35-5125-c8af-481622d9adf9) @ PCI:0000:03:00.0

Any idea what causes this issue? The rig doesn't mine.

Is there a way how I can detect a faulty GPU/Riser, without removing the GPUs one by one? I thought maybe the GPU utilization log could do it, but I don't know if the GPU numbering there is the same like the numbering of slots of my motherboard?

[papampi]

Same PSU, too? You can tell if they are using identical power with:

Code:

nvidia-smi --query-gpu=temperature.gpu,fan.speed,power.draw,power.limit --format=csv

Hope this helps.

Same PSU too

Are all the BIOS settings the same? Same on the PCI speeds, etc?

Same bios settings


lol ... going crazy ...

Removed all cards and restart rig with only 1 card direct connect to motherboard no risers,
Same low speed, 18-19 MH/s on eth

If everything is same and you swapped card from the "fast" rig and it perform worst on the "slow" rig it must be something wrong with the "slow" rig's motherboard or some bios settings are not exactly same. Are bios versions of the mobo's same?

On the "slow" rig reflash the bios, load bios default (or optimized) settings, save and reboot (F10), go into bios again and set everything same as on the "fast" mobo. Don't skip any options, open and check all settings are same. Take one GPU from the fast rig and try it. If it still underperform RMA the motherboard, I can't think of anything else.

Already done flash, erase, ... of bios ... no go.
I was suspected of mobo too, gonna send it back and see how it goes.

[ComputerGenie]

Already done flash, erase, ... of bios ... no go.
I was suspected of mobo too, gonna send it back and see how it goes.

That was my 1st thought. 'Twas my reason for asking about the drive, I wasn't quite following what you wrote.

[Havesovgosh]

Hi,
v0019-1.3 is now "STABLE" or still "BETA" version??

[Stubo]

Hi,
v0019-1.3 is now "STABLE" or still "BETA" version??

That version was and always will be a BETA. The latest stable version is 19 and the next planned is 20. The latest BETA is 19-1.4 and was released yesterday. I have been mining with it on all of my rigs for about 24 hours with no issues. At present, there is no upgrade path to it - you have to start with the full release (link on first page).

Hope this helps.

[sergixc]

Hi, what about full support of Asus b250 mining expert.

What does it mean "partly supported"?

Is it a hard limit of 13 standard GPU + 6 P106? or will be possible to use 19 regular GPU?

My mobo does not even post bios messages when Iam inserting 14th regular GPU

Could anybody comment on this?

Thank you in advance!

[Stubo]

Hi, what about full support of Asus b250 mining expert.

What does it mean "partly supported"?

Is it a hard limit of 13 standard GPU + 6 P106? or will be possible to use 19 regular GPU?

My mobo does not even post bios messages when Iam inserting 14th regular GPU

Could anybody comment on this?

Thank you in advance!

I think that means it is supported but there are known issues when going beyond a certain number of GPUs. I am running that mobo but with only 7 GPU ATM and everything is great. Take a look at previous posts like this one for more information:

https://bitcointalk.org/index.php?topic=1854250.msg23785755#msg23785755

Hope this helps.

[leenoox]

Hi, what about full support of Asus b250 mining expert.

What does it mean "partly supported"?

Is it a hard limit of 13 standard GPU + 6 P106? or will be possible to use 19 regular GPU?

My mobo does not even post bios messages when Iam inserting 14th regular GPU

Could anybody comment on this?

Thank you in advance!

Have you attached 3rd PSU?
One PSU = 7 GPU
Two PSU's = 13 GPU
Three PSU's = 19 GPU

Partial support means that not all GPU's can be overclocked, first 16 GPU can be overclocked, last 3 GPU will work on stock settings. See the post from two pages back regarding TB250

https://bitcointalk.org/index.php?topic=1854250.msg23785755#msg23785755

[zimmix]

Thank you very much for your kindly explanation, I'll give it a try!

[Havesovgosh]

Hey Everyone,

If you have more than 16 GPUs, the key is to have no more than 16 cards listed in the ServerLayout part of your xorg.conf. Those are the ones that will OC. You will have all 19 listed in the Device and Screen sections and the three that remain will run but won't OC. If you add a 17th under ServerLayout, the miner will not be able to OC any because X will crash when it starts when it hits the 17th card.

If you look at nvidia-smi output, you *should* see, at the bottom an instance of X AND a miner process for each GPU. The ones that only have a miner process attached cannot be OC'd. For me this is GPUs 17, 18, 19.

I've had to edit my rclocal.sh to copy a custom xorg.conf from ~ into /etc/X11 to keep it correct. The problem (for me) is that the script that auto creates the xorg.conf won't stop at 16 in the ServerLayout section and thus makes it so that X won't start and thus none of them OC.

Also, for my Gigabyte P106 cards (I'm running 19) for those first 16 (which will OC), I've not been able to get beyond 100 core and 250 mem, producing 18-18.1 MH/s for ETH only.

Let me know if this helps!
-z

```
# xorg.conf for 19 P106 on Asus ME that gets me 16 OC and 3 non-OC

Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidiascreen-00"
    Screen 1 "nvidiascreen-01"
    Screen 2 "nvidiascreen-02"
    Screen 3 "nvidiascreen-03"
    Screen 4 "nvidiascreen-04"
    Screen 5 "nvidiascreen-05"
    Screen 6 "nvidiascreen-06"
    Screen 7 "nvidiascreen-07"
    Screen 8 "nvidiascreen-08"
    Screen 9 "nvidiascreen-09"
    Screen 10 "nvidiascreen-10"
    Screen 11 "nvidiascreen-11"
    Screen 12 "nvidiascreen-12"
    Screen 13 "nvidiascreen-13"
    Screen 14 "nvidiascreen-14"
    Screen 15 "nvidiascreen-15"
    Inactive "intel"
EndSection

Section "Device"
    Identifier "intel"
    Driver "modesetting"
    BusID "PCI:0@0:2:0"
    Option "AccelMethod" "None"
EndSection

Section "Screen"
    Identifier "intel"
    Device "intel"
EndSection

Section "Device"
    Identifier "nvidia-00"
    Driver "nvidia"
    BusID "PCI:1@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-00"
    Device "nvidia-00"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-01"
    Driver "nvidia"
    BusID "PCI:2@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-01"
    Device "nvidia-01"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-02"
    Driver "nvidia"
    BusID "PCI:3@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-02"
    Device "nvidia-02"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-03"
    Driver "nvidia"
    BusID "PCI:6@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-03"
    Device "nvidia-03"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-04"
    Driver "nvidia"
    BusID "PCI:7@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-04"
    Device "nvidia-04"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-05"
    Driver "nvidia"
    BusID "PCI:8@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-05"
    Device "nvidia-05"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-06"
    Driver "nvidia"
    BusID "PCI:9@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-06"
    Device "nvidia-06"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-07"
    Driver "nvidia"
    BusID "PCI:10@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-07"
    Device "nvidia-07"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-08"
    Driver "nvidia"
    BusID "PCI:11@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-08"
    Device "nvidia-08"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-09"
    Driver "nvidia"
    BusID "PCI:12@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-09"
    Device "nvidia-09"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-10"
    Driver "nvidia"
    BusID "PCI:13@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-10"
    Device "nvidia-10"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-11"
    Driver "nvidia"
    BusID "PCI:14@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-11"
    Device "nvidia-11"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-12"
    Driver "nvidia"
    BusID "PCI:15@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-12"
    Device "nvidia-12"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-13"
    Driver "nvidia"
    BusID "PCI:16@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-13"
    Device "nvidia-13"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-14"
    Driver "nvidia"
    BusID "PCI:17@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-14"
    Device "nvidia-14"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-15"
    Driver "nvidia"
    BusID "PCI:18@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-15"
    Device "nvidia-15"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-16"
    Driver "nvidia"
    BusID "PCI:19@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-16"
    Device "nvidia-16"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-17"
    Driver "nvidia"
    BusID "PCI:20@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-17"
    Device "nvidia-17"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-18"
    Driver "nvidia"
    BusID "PCI:21@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-18"
    Device "nvidia-18"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

```

Hello,
what version is NVOC, 0019 or 0019 1.2

[Havesovgosh]

Hi,
v0019-1.3 is now "STABLE" or still "BETA" version??

That version was and always will be a BETA. The latest stable version is 19 and the next planned is 20. The latest BETA is 19-1.4 and was released yesterday. I have been mining with it on all of my rigs for about 24 hours with no issues. At present, there is no upgrade path to it - you have to start with the full release (link on first page).

Hope this helps.

Thanks.

[JayneL]

Still great mining OS for me thanks for all the effort guys.

Just want to know is it possible to have an individual Overclock if I'm using Nicehash or Mining pool hub autoswitch?

Thanks

God Bless

More Power

[joshuajones02]

I'm a newb linux user, not sure if this is the best place to ask but I'm having issues with one of my systems running nvOC.. My rig keeps rebooting itself after a few hours of running and when I go to access it to see what happened all my mobo settings have been reset to default and it asks me if I want to run setup or to boot as normal. Anyways, I'm unsure where to go to access linux crash logs or how to read them.

Once I reboot the rig back into Linux everything runs as normal.

Still having issues with this if anyone has a moment to help me out locating/interpreting logs

[papampi]

I was suspected of mobo too, gonna send it back and see how it goes.

So the problem was not mobo either, and it was cards from different manufacturing patch.
What I got from the seller was 2 big boxes with 10 cards in each + 4 cards, seems like one of the big boxes have different memory type.
So I got 14 good ones and 10 not so good ones ... lol

So now the question is which combo is better ?
6+6 in each rig
or go with one fully good and the other 4 good and 8 not so good ?

[papampi]

I'm a newb linux user, not sure if this is the best place to ask but I'm having issues with one of my systems running nvOC.. My rig keeps rebooting itself after a few hours of running and when I go to access it to see what happened all my mobo settings have been reset to default and it asks me if I want to run setup or to boot as normal. Anyways, I'm unsure where to go to access linux crash logs or how to read them.

Once I reboot the rig back into Linux everything runs as normal.

Still having issues with this if anyone has a moment to help me out locating/interpreting logs

Are you using usb or ssd ?
It seems your rig restarted too many times and mobo gone to safe mod to keep it from restarting more.
Which version you have?
Check your OC settings.

[Stubo]

I was suspected of mobo too, gonna send it back and see how it goes.

So the problem was not mobo either, and it was cards from different manufacturing patch.
What I got from the seller was 2 big boxes with 10 cards in each + 4 cards, seems like one of the big boxes have different memory type.
So I got 14 good ones and 10 not so good ones ... lol

So now the question is which combo is better ?
6+6 in each rig
or go with one fully good and the other 4 good and 8 not so good ?

I generally like to keep all cards in a rig the same so I would go with 1 rig with all good and the other as a mix so that you only end up with one "funky" rig.

[mibjt]

I am facing this issue when I install NVOC and boot up, tweaking the 1bash file setting, during the startup in terminal, I get stuck at "There is no screen to be resumed matching miner" for a while, after that the rig will restart on its own and ask me to log in the password for m1. I have 2 rigs to mine zcash and somehow the other one works just fine with the same 1bash file config. Does anyone face this issue? Would appreciate if anyone can help me on this.

https://imgur.com/YiXpK1y
https://imgur.com/VCFUZx9

[burntone]

I can`t seem to be able to mine in ethermine pool. Can someone help me figure out how to fix this?

https://lh3.googleusercontent.com/TXmLRrrT5IQoZT-UiMq-Osch2NoJeN1jyU20srZQa55ysKMEKw9L5Y9LJFkGZPi7KwYjlmi9z1QwFcNvTYpW7LvTZDKZXMXZiUeXz1cyk3ZhgcgiDu7VacelKOD_lArBWnwM4u-6nnQUJdxOeWCjHwJVaCt3bnFFc_4bcnLNSOMqQhziB5o170tcjWgt4j5VbYSf-6OR1nFAuqPdkl9VHcokltVzwp1kuudKb0Ibk8Yf6doIsg4l-32gZPjrj7hPjOir2p9OBLsAkiyVp5ERCoPPmCuTCqdLF9fD9U2VYDEvjD049uh8oqzCdnWWz3Tx-jod3yef2K4_z1W1llEw2F54Eo5cdAPVsuEm_eHnPapZZwUIpS9f0cVSf5pB2RFYlxI7byOBkM6X8FXNp12g85XVGzw3vwd2KS6t5rYKlmhonO4xSrNcmjJYDwwZ8LlaR6fLllsThKqTN5SGcKgXWSIYqT7kD4ZGWdHHBnbWlX9EddCyJ1LrRAUASAmqyrbmSHF-bOMSB9m74N9YMRvTRyTbbwKNsDbpuq458M6ENBBFSZSEssr8uPF6ZaQZQO4ZhLKOD_sB4WnknUCuxRUfmCIQKN-YpeTYXFAb7WUx9M3mJbiSxi-aUwvIx6HmZEXf9jGdfzLZT48kbBcBM1wKi3u3r7z380Zgpbz0=w639-h452-no

These are my ETH settings in 1bash:
https://lh3.googleusercontent.com/bYQQ8glhCF8Fnv56VezD531YgEreSZiS973t3MWDu_jCixJXKpAyAVXxWcbKWAfQZDPGLneLsf4bcnVCTUSJDGTcvaw3sq0ZzPBVz-35-HrC6ERdoL_5l56kAETycrdLdfRDOElnXdZ8OaEUOam-7aJjKfDXHnx1HDqm0g8q6l5PILcdlPM0beI9iVhvjQbA6xb_xNTYvQGl09uw337xoZh3oDDMvPrv-PelPgFddKm6iuhdPf9F9hNScd4sRkU56qZXTdEkrAPRohRnWJvNEU2L03yZPqIdvfso1lJW_OaQlmx84aGpsSQYj1rLthdDz8eiTSY4WwInXDQpzqUWy0UTGNOqaH_a7WYqzLRq8Nt9TOYHl8osASTGGFazXQ_x2fLvTr7CWAJaYrErEWnpDJCXSl10FnQC4JnE0PDYBlvBvMThGz20FbioxSgT6AXxyAfg6XRT3enhegUlG5ejYv7HcGUDdOSlcMQdRbhAbEDLU2bOsi1_kpohX2WzyBdNvM8O-T06PEFL0RrqY5CL5R5kAJtK6tJrNU8TQdhOZGwIyg_9zBwTYGONVn7VcdjVI1V9tPQPX3KgNmiwJKRr4JVXSnzkzvRJ--8um4TteyZSMlyRCGpIoyphll3wj72SFrPbw-TlE8H4r6FSuEMIJsW0-aoNCeYH7gWd=w638-h477-no

All working well in nanopool:
https://lh3.googleusercontent.com/ODCY3-CAulSwMYjrgQsdHnhlIz77lpLI2VNJ1OhLPMPGjQCQlLa1jdiGIYqSOozNnrtMvcjrECoX2uk3TbZXDd9QVwP1l06VNdBmQeR4jnZ0xwDKC7_1pb9oz2XA_Mn2bSXuJjToHG-1gMWoqBu5SmLTIeGC65hZtqXtsHZORUk1eVNgeEWBd7S-f7xFSebXL1O1tkiMojO-30y9FRZGL3u9CZYCB2JSrcjskyci80H8bbKqmWH2RZteWdPPzdfwuo1bKLQerJ5qcErffTE0qFkRXBIkyYcSTD4Cwv8RgEBgvagWe01dTWCin9-RZXHbOQB2AR6K_G-IqxGzVPD7b8H6hr1hjIjsdnDtI7QmQr7TCSdOwP8lukVzRcwpDT10b40nhhrN8I3qJahdSdDLBTlHQypa0MPrG1Zf4GEQrK_aT1DnpOM67zHj7UMUdMYTBSR3fpb_1EVmz7xz4rYC1q4paOBMc-_ahjJrcm8AMX-_ntreqY9ozMbIhTn_OpAm2-IZvjSuenwMs5-r89ohtr2BVc4GWAGOO5DLjGTqZzAxN3q35GEyhrBvRZXFOUDtr7Mzzz1gUWJGHU79DEwSmW4FKXFbhDmNNkldbrO_H-CLZOrxXwYzYw3GEfSk5S2GSIcsNGtcHvSZxqoSvlEWY0ZGVv4Hqlb3BGDB=w638-h479-no

Also, can I update to the latest Claymore`s (https://bitcointalk.org/index.php?topic=1433925.0) without breaking something in nvOC?

Thanks!

[leenoox]

I was suspected of mobo too, gonna send it back and see how it goes.

So the problem was not mobo either, and it was cards from different manufacturing patch.
What I got from the seller was 2 big boxes with 10 cards in each + 4 cards, seems like one of the big boxes have different memory type.
So I got 14 good ones and 10 not so good ones ... lol

So now the question is which combo is better ?
6+6 in each rig
or go with one fully good and the other 4 good and 8 not so good ?

argh... but you stated before that all cards had same memory... I assumed that you tested each and every one with gpu-z under windows... that's what I did with mine...

Anyway, at least you know where the problem lies now... if you can't return the cards with "bad" memory I suppose it is best to make one rig with all "good" cards and the other one mixed

[leenoox]

I can`t seem to be able to mine in ethermine pool. Can someone help me figure out how to fix this?



These are my ETH settings in 1bash:


All working well in nanopool:


Also, can I update to the latest Claymore`s (https://bitcointalk.org/index.php?topic=1433925.0) without breaking something in nvOC?

Thanks!

There is an option DOT or SLASH in 1bash. Set it to DOT for ethermine