Quote from: HaloGenius on May 27, 2018, 11:01:43 PM

Quote from: superminator on May 27, 2018, 09:08:13 PM

Quote from: dadashali on December 18, 2017, 10:06:46 AM

Quote from: dadashali on December 16, 2017, 07:03:56 PM

There is still some matters yet.
1. For the first time (first run), if i get a rig id and enter it the setup would be completed successfully but if i delete that rig id in the website and make another one and then use "firstrun -f" command to setup a fresh rig once again, it would not be successful while info on "rig.conf" file will be changed to new info that i entered from fresh setup and the rig will stay to works with old rig id that was deleted before!

2. While i made setup miner software and wallet via video tutorial to mine XMR via nanopool server with claymore dual (i've RX 470), i don't know why the miner start to mine only for Ethereum while i didn't define any eth address at all!! In the Hiveos XMR mining not possible with claymore? I must mention that i'll click on the "rocket" after choosing the miner and wallet but after restart mining it will mine ethereum again ... i'm very confused Undecided

3. For failing on memory overclock there is an error like below:
Jul 9 23:58:37 test-rig kernel: [ 1399.017519] VM fault (0x01, vmid 6) at page 135290427, read from 'TC3' (0x54433300) (196)
Jul 9 23:58:37 test-rig kernel: [ 1399.017554] amdgpu 0000:04:00.0: GPU fault detected: 147 0x01c84801
Jul 9 23:58:37 test-rig kernel: [ 1399.017557] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E39
Jul 9 23:58:37 test-rig kernel: [ 1399.017559] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C048001

I see Hiveos does not show this error on it website or miner console (via ssh or shellinabox) and it will shown on the connected monitor to the rig only! please explain about this matter or fix it on the Hiveos error report.

Regards

It would be great if you can resolve this matter for me. @dimafern

Hi!,

Have you solved this error? I also have it and I do not know how to solve it:

Best regards.

It's simplest error. Memory too overclocked or has wrong timings

I dont overclocked memory. The default value is set.