See if you have eth addres WITHOUT 0x .
Dwarfpool need eth address without 0x at the beginning (it is the most common problem)

Hello guys.
The production of Extension Boards is still in progress and we should have them in December.
I think that i wont do preorders on Extension Boards and they will be available in shop as soon as EVERYTHING will be tested, checked and software/firmware will be polished
In the same time as Extension Boards arrive there will be new firmware for SRRv1 and SRRv2 which will bring more features to devices
There is big demand on Extension Boards so i am expecting big delays in shipping at first.
Once i will have them ready to shipp i will release the in shop
Ofcourse i will inform all users who requested to be informed via email

Sometimes this happens for rare cases.
We are still investigating what is causing this in those rare cases.
Anyway please just write me email admin@simplemining.net with payment details and i will check it.
Also please give me few days to respond. I am getting too much emails these days....


Yes i will be adding few miners and dstm is one fo them.
All rigs are auto updating with new scripts or miner files.
Still i wont be making auto updates of drivers and kernel becasue this is dangerous.
Instead there will be optional updates for that cases
And also new images with applied new kernels and drivers such as this : http://download.simplemining.net/beta/simpleminer-RX-NV-rc2.img.zip

Please wait a little bit longer. I have oldest emails from 16 november to answer.
Still i am not blocking anything so far. Only alerts.

Here is 3 scripts that you want

If there is broken unit then it will be replaced by new one or ther will be made full refund including shipping costs from you to us.
We have not much cases, like less than 1% of devices with some problem like one port not working or one other strange problem.
From i remember tht would be only third device that had any problems the many more sold didn had any problems.
So if you will get second device and you will see that there is definitly problem with the first one then no problem.
Just write to shop@simplemining.net and we will solve your problem
No need to worry.

Also about Extension boards.
We finally made and fully tested 4th extension board prototype that finally dont have any flaws.
Now we ordered production line and production of first batch will be done in about 40-60 days.
Once i will have poduction units and they will be again tested, i will start sale process
Sorry it took so long but i want to sell only 100% good product.
With new extension boards there will be also new firmware for SRRv1 and SRRv2 with more features
Once this all process will be done i will try to send everyone email about new firmwre for SRR

Hi Calymore,
Do you have any ETA on version for linux ?
My users are waiting for Your release and many other part of the word
Thx for you well done job in all miners !

Update v1128
- changed start delay from 6seconds to 12seconds in nvidia rigs (temporay fix for slow usb and too slow initialisation). This shoudl fix some OC problems in some cases on Nvidia rigs
- changed verbose logging in xmr-stak-amd miner from 3 to 4 (more speed stats)

Only OC problems.
The GPU3 stopped could be becasue of:
- too much OC (most common)
- bad riser (most common)
- some incompatibility in linux or incompatible motherboard bios (sometimes this is becasue if this yes - worth to try after rulling out above problems)
- bad gpu (slight chance)

I probably know whats causing it and i just need to make some fix in my script.
Anyway if i am thinking right then this issue is only on slow pendrives.

The dummy and temporary fix could be:
/root/utils/rclocal.sh
change 31 line from
  sleep 6
to
sleep 20

The Xorg is starting too slow on slow pendrives and thats probably the issue.
I have pretty fast ones so i dont have this issue and this explains why reloading fixes this problem.

I will make some checkups first before miner starts.

If you mean the Loggin Out.
Then yes it was a problem and it should be fixed now.
Thx for report.


I will make longer cookie duration, for example 48h.
Thats should do it.

Ok wait for my reply. I need to answer alll of them

For some motherboard it is in deed causing problems !
20% of my motherboard are behaving like bad boys but rest are totally ok.
You should just try one by one and prepare for reflash or have already other pendrive with old image


No problem, still i admit that i implemented this update too late than i accually could and should, so sorry guys for that !


Then you Should make simple bash script and run it in rc.local

#!/bin/bash
ping something.com
# the -t parameter works only in windows, in linux you dont need to add anything to make it work in a loop.


This kernel has some problems on some motherboards. It could be it, It could be also some pendrive problems.
Try reflashing with dagfix image from website.
If it wont help then try to reflash with old stable image.


This update is showing in dashboard ONLY when rig doenst have dagfix kernel and it is RX OS and has at least one GPU connected.
In all other cases this update wont show up ofcourse

I will look into this thx.
No wifi support . Man i really need to make this FAQ

This motehrboard is known as really fucked up - meaning SMOS wont work on this motherboard and i cant help it

I didnt bringed memory undervolting feature to not make this more harder than it is now.
Accually memory undervolting can save about 1-2 watts per gpu. So i guess it isnt worth it !
Only thing that came to my mind is to make overvoltimg in memory which COULD make memory work more stable on very high overclocking.
Accually i am thinking about this but i still am gathering some more informations.
If you want to mess with it then you could manually edit one script and add static memory undervolting by editing:
root/utils/oc_dpm2.sh file
change line
/root/utils/wolfamdctrl -i $x --core-state $coreState --mem-state $memoryState --core-clock ${coreArray[$i]} --mem-clock ${memoryArray[$j]} --volt-state $coreState --vddc-table-set ${coreVoltArray[$i]} #--mem-state $memoryState --mvdd 950
to
/root/utils/wolfamdctrl -i $x --core-state $coreState --mem-state $memoryState --core-clock ${coreArray[$i]} --mem-clock ${memoryArray[$j]} --volt-state $coreState --vddc-table-set ${coreVoltArray[$i]} --mem-state $memoryState --mvdd 950
Or 1000 or whatevery you want
If anyone will have results such as "i saved 5 watts with memory undervolting" or "i make it more stable with 100 MHZ more and now gpus is making 0,5MH/s or something  - just let me here know and other people.
If this will really make sense then i will implement it. If it will save 1-2 watt then there is no point right ? I am not as much eco friendly - in other case i would not be mining at all

Yes.
Try to rule out cabling problems (bad cable or adapter) - use working one cable in the same slot.
Also try connecting other working rig to the port 2 in SRRv2.
If you see that for sure SRRv2 port 2 is causing problem and NOT motherboard itself or cables or adapter,
Please write me an email to admin@simplemining.net and lets start RMA - if its really broken then it will be replaced by new one
Please copy also your+my messages from bitcointalk. Waiting for your email with those 2 more tests

Its still ABOUT 2 months.
Once last prototype will be approved and no ANY flaws will be found then i we will need about month or 1,5 month for production.
I really dont want to release product with even slight flaw ...
So when last prototype will be good then i will have better release date

You need to experiment with it. I have mine on powerstage 3 and 900 .
You should watch powermeter and try to lower powerstage or undervolting and if it takes less wattage and its stable then ok.
If not then try to rise powerstage first.
Anyway this works as powestage+undervolt so if you have 900mv at powerstage 7 and second case on powerstage 3, then this 3 will take less wattage.
I dont know exactly what happening, i just know from experience that it behaves like that


Each GPU has own tolerance for undervolting.
Even 6 indentical GPUs from the same part are totally different. Once could undervolt to 900 while other to 850 remaining stable.
Every GPU is very separate case Also risers are important.
Bad risers i think can result in less stable voltage and can cause problems.
In this word there is milion cases that something will go wrong


I will add this to my TODO list and do it in some time yes.


Please write to me at admin@simplemining.net
I want to take a look on your rig.
Can you forward ssh port to your mining rig ang give it to me VIA EMAIN (not here !)
Or prepare team viewer to ay windows that is in he same network as your rig ?
Also send me rig name and email of this rig.
I have very little cases that this update fixed maaany cases but also caused new problems that didnt existed before.
Also try rebooting our rig and see if that will fix your problem ! (it might).
If not then write to me to email.


There is no such thing. RX OS is console only. Headless OS.

Mine have 1.7.3.1
Still i dont think this kind of difference in version could cause this.

Do you have this script exctly ? check it.

#!/bin/bash

## REQUIRED packages: socat (apt-get install socat)


## Other Linux Systems than SimpleMining OS - unhash 3 lines below and hash SimpleMiningOS ones
srrEnabled="1"
srrSerial="000055"
srrSlot="1"

## SimpleMining OS ## hash this section if you are using above variables
#CONFIG_FILE="/root/config.txt"
#source $CONFIG_FILE
#srrEnabled=`echo $JSON | jq -r .srrEnabled`
#srrSerial=`echo $JSON | jq -r .srrSerial | xargs`
#srrSlot=`echo $JSON | jq -r .srrSlot | xargs`
#####################

if [ "$srrEnabled" -eq 1  ]; then
    echo "SRR is Enabled"
else
    echo "SRR Not configured. SRR Agent will exit in 120 seconds"
    sleep 120
    exit
fi

################################
## Dont touch anything below
srrSlot=`printf %02X $(( ${srrSlot} - 1 ))`
firstByte="FF"
byteCount="0008"
action="55"
mac="485053$srrSerial"

checksum=`printf %02X $(( (0x${byteCount:0:2} + 0x${byteCount:2:2} + 0x$action + 0x${mac:0:2} + 0x${mac:2:2} + 0x${mac:4:2} + 0x${mac:6:2} + 0x${mac:8:2} + 0x${mac:10:2} + 0x$srrSlot)%0x100  ))`
packet="$firstByte$byteCount$action$mac$srrSlot$checksum"

while true
do
    echo "SRR, please dont kill me, i will ask again in 2 seconds $packet"
    echo -n "$packet" | xxd -r -p |socat - UDP-DATAGRAM:255.255.255.255:1051,broadcast > /dev/null
    sleep 2
done

You need to enter something like 900 . in undervolt.

Click it, you will see info in confirmation window.


Be sure you have even 850 and lets say 4 powerstage level and compare wattage.




Please send me email to admin@simplemining.net - best with team viewer to any . windows on the smae networ as your rig or forward 22 port to your rig and tell me the access.


Wifi is unsupported and wont be anytime soon.

Meaby you had dagfix already.
Hover on name of your rig.
If you will see .....compute-rocm... in kernel then you have dagfix.

Yes. Fisrt boot will be doing many little updates.

Try with ONE and see what happens Best to try at one