 Show Posts
|
|
Pages: [1]
|
All, Was working great in 16 but having issues dual mining ETC and SC with Claymore in 18. Got ETC working and working WELL (yay higher hashrate for my 1060) but whenever I try to connect to siamining.com I'm getting an error:
SC: Stratum - connecting to 'us-east.siamining.com' <45.79.159.167> port 7777
SC: Stratum - Connected (us-east.siamining.com:7777)
SC: Authorization failed
: {"id":2,"error":null,"result":false}
Stratum - reading socket failed, disconnect
SC: Job timeout, disconnect, retry in 20 sec...
GPU0 t=65C fan=60%
Here's my 1bash config: SC_WORKER="nv$IP_AS_WORKER"
SC_ADDRESS="c4fa3fa4acf1a317752204d730888c755367d8e81092a944f6727d06251f1fd1a752576afac6"
SC_POOL="us-east.siamining.com:7777"
SC_GW_POOL="us-east.siamining.com:9980"
I'm using port 7777 to reach siamining.com on a dual mining claymore config on Windows 10 with no problem. It's not clear to me what I should be setting the SC_GW_POOL value to. Any insight there? Thanks! this pool uses the syntax: -dpool stratum+tcp://us-east.siamining.com:7777 -dwal YourSiacoinAddress.YourWorkerName -dcoin sc on or near line 2764: SCADDR="$SC_ADDRESS/$SC_WORKER" need to be changed to SCADDR="$SC_ADDRESS.$SC_WORKER" for this pool. for the next 1bash; I will make a YES/NO switch to make this easier to change in the future. Let me know if this solves the problem. That did the job. A switch would be awesome but even just a comment somewhere relevant in the config would be a good pointer. |
|
|
|
All, Was working great in 16 but having issues dual mining ETC and SC with Claymore in 18. Got ETC working and working WELL (yay higher hashrate for my 1060) but whenever I try to connect to siamining.com I'm getting an error:
SC: Stratum - connecting to 'us-east.siamining.com' <45.79.159.167> port 7777
SC: Stratum - Connected (us-east.siamining.com:7777)
SC: Authorization failed
: {"id":2,"error":null,"result":false}
Stratum - reading socket failed, disconnect
SC: Job timeout, disconnect, retry in 20 sec...
GPU0 t=65C fan=60%
Here's my 1bash config: SC_WORKER="nv$IP_AS_WORKER"
SC_ADDRESS="c4fa3fa4acf1a317752204d730888c755367d8e81092a944f6727d06251f1fd1a752576afac6"
SC_POOL="us-east.siamining.com:7777"
SC_GW_POOL="us-east.siamining.com:9980"
I'm using port 7777 to reach siamining.com on a dual mining claymore config on Windows 10 with no problem. It's not clear to me what I should be setting the SC_GW_POOL value to. Any insight there? Thanks! |
|
|
|
Waiting for Biostar tb250 pro and 12 Zotac P106-100 to start mining using this OS.
Is it possible to quickly update to the latest version if it is installed on hdd/ssd?
I will release v0018 soon. Currently you must reimage to upgrade; I will add an updater in a later version. You can change v0017 into almost v0018 by following this post:
https://bitcointalk.org/index.php?topic=1854250.msg20099702#msg20099702However; v0018 will support any storage type; USB key, SSD, HDD, m2 SSD ect. So, I would recommend waiting to download v0018 if you don't have your components yet and plan on using a HDD or SSD. Excellent! Was just going to post about some challenges I was having getting the 0017 image running (oneBash loops repeatedly before ever starting the miner). But sounds like we're close to 0018--which I hope solves my issues. Sent you some hashes last night testing gear. You're doing awesome work here! |
|
|
|
Let me begin by joining the chorus of miners praising this effort. I spent a week working towards the same goal before finding this thread. I think you've probably saved me a month of evenings developing something similar. Sending some hashes your way as I test!
I'm using an msi z170a m5 with 4 Asus GTX 1060 6G GPUs on an 850w PSU. I'm also running a single gtx 1060 on a muuuuch older board Asus p5n-d (yes that old) and nvOC still works like a charm.
One thing I've noticed with nvOC versus my own Linux install is that I can't seem to get the same hashrate in nvOC. Even if I set the pl to 140 for the card, push memory all the way to 2000 and the GPU clock offset to 130, I can't break 21 MHS in nvOC. Comparatively, if I just load Ubuntu 16.04 with xorg, gnome and latest drivers with Claymore dual mining ETH and SC, I can sustain 23 MHS for days. Same if I put a card on my Win10 box and use MSI Afterburner to contro OC there. I've tried throwing configurations at my nvOC node manually with nvidia-settings -a and it just doesn't seem to get beyond 20 MHS. I can open the nvidia control panel and verify all the settings took. The only difference I can find so far between nvOC and my own build is that I was still using 375.66 version of the driver and nvOC appears to be using 378.13.
Anyone have any thoughts or suggestion of what else I could try? I'd love to switch all my gear to this but right now I'm getting better hash rates out of a 1060 in win10 and 1060s on Ubuntu not using nvOC. And across multiple 8 GPU rigs, the delta adds up.
Thanks!
From most data sets you will get slighly better hashrate from Windows still, even some 1070's I have seen pushing 31-33 while on Ubuntu I have only gotten 29-31. The biggest advantage though I will say is stability, Ubuntu has shown more constant and stable hashrate by far then any Windows PC (this is beyond the Win 10 auto update on home edition) Agreed on Windows vs Linux mining. I've observed greater stability in Linux. However, comparing a fresh Ubuntu install to nvOC, I still observe a 3+ MHS difference per card per node. Using nvOC is like taking a card out of every one of my nodes. I'm continuing to investigate, b/c this is a great offering. Only other things I've noticed so far: 1) the xorg.conf on both my test machines lists the cards as 1050s instead of 1060s. Also, my multi GPU test node seems to have a problem with any windows on the console showing up off monitor. My working hypothesis is that it's b/c I plugged in a DVI monitor rather than HDMI but that seems pretty thin to me. Anyone else run into that issue? Google searches so far have not been fruitful. Nvidia is weird; I did use a 1080p hdmi monitor when building nvOC, so it is possible that it freaks out with DVI. Yes, I know HDMI is essentially; DVI + digital audio. However, there are about 14 different types of DVI; they are not all interpreted the same as HDMI on linux (primarily if they are analog DVI). The GPU title is meaningless in any systemic capacity in the xorg.conf; so its not a problem that it doesn't list 1060s there. Different drivers will have different OPT clocks; I would try my suggested clocks and mc bumping: if you still don't get comparable hashrates then I would use whatever OS gives you the best results. I will make a 375 driver version eventually (it is on the list); but I am trying to focus first on helping users resolve problems, then with implementing the most requested improvements first. Zero, Understood with regard to card titles. Looking through oneBash I saw some logic that appeared predicated upon the title and took a guess without testing it. I normally use HDMI for everything but have an OOOOOLD VGA/DVI only monitor mounted above my test rack. Will test out with a more current monitor and report back my results. Looking forward to testing the 375 driver when you're ready to release! |
|
|
|
Let me begin by joining the chorus of miners praising this effort. I spent a week working towards the same goal before finding this thread. I think you've probably saved me a month of evenings developing something similar. Sending some hashes your way as I test!
I'm using an msi z170a m5 with 4 Asus GTX 1060 6G GPUs on an 850w PSU. I'm also running a single gtx 1060 on a muuuuch older board Asus p5n-d (yes that old) and nvOC still works like a charm.
One thing I've noticed with nvOC versus my own Linux install is that I can't seem to get the same hashrate in nvOC. Even if I set the pl to 140 for the card, push memory all the way to 2000 and the GPU clock offset to 130, I can't break 21 MHS in nvOC. Comparatively, if I just load Ubuntu 16.04 with xorg, gnome and latest drivers with Claymore dual mining ETH and SC, I can sustain 23 MHS for days. Same if I put a card on my Win10 box and use MSI Afterburner to contro OC there. I've tried throwing configurations at my nvOC node manually with nvidia-settings -a and it just doesn't seem to get beyond 20 MHS. I can open the nvidia control panel and verify all the settings took. The only difference I can find so far between nvOC and my own build is that I was still using 375.66 version of the driver and nvOC appears to be using 378.13.
Anyone have any thoughts or suggestion of what else I could try? I'd love to switch all my gear to this but right now I'm getting better hash rates out of a 1060 in win10 and 1060s on Ubuntu not using nvOC. And across multiple 8 GPU rigs, the delta adds up.
Thanks!
From most data sets you will get slighly better hashrate from Windows still, even some 1070's I have seen pushing 31-33 while on Ubuntu I have only gotten 29-31. The biggest advantage though I will say is stability, Ubuntu has shown more constant and stable hashrate by far then any Windows PC (this is beyond the Win 10 auto update on home edition) Agreed on Windows vs Linux mining. I've observed greater stability in Linux. However, comparing a fresh Ubuntu install to nvOC, I still observe a 3+ MHS difference per card per node. Using nvOC is like taking a card out of every one of my nodes. I'm continuing to investigate, b/c this is a great offering. Only other things I've noticed so far: 1) the xorg.conf on both my test machines lists the cards as 1050s instead of 1060s. Also, my multi GPU test node seems to have a problem with any windows on the console showing up off monitor. My working hypothesis is that it's b/c I plugged in a DVI monitor rather than HDMI but that seems pretty thin to me. Anyone else run into that issue? Google searches so far have not been fruitful. |
|
|
|
|
Let me begin by joining the chorus of miners praising this effort. I spent a week working towards the same goal before finding this thread. I think you've probably saved me a month of evenings developing something similar. Sending some hashes your way as I test!
I'm using an msi z170a m5 with 4 Asus GTX 1060 6G GPUs on an 850w PSU. I'm also running a single gtx 1060 on a muuuuch older board Asus p5n-d (yes that old) and nvOC still works like a charm.
One thing I've noticed with nvOC versus my own Linux install is that I can't seem to get the same hashrate in nvOC. Even if I set the pl to 140 for the card, push memory all the way to 2000 and the GPU clock offset to 130, I can't break 21 MHS in nvOC. Comparatively, if I just load Ubuntu 16.04 with xorg, gnome and latest drivers with Claymore dual mining ETH and SC, I can sustain 23 MHS for days. Same if I put a card on my Win10 box and use MSI Afterburner to contro OC there. I've tried throwing configurations at my nvOC node manually with nvidia-settings -a and it just doesn't seem to get beyond 20 MHS. I can open the nvidia control panel and verify all the settings took. The only difference I can find so far between nvOC and my own build is that I was still using 375.66 version of the driver and nvOC appears to be using 378.13.
Anyone have any thoughts or suggestion of what else I could try? I'd love to switch all my gear to this but right now I'm getting better hash rates out of a 1060 in win10 and 1060s on Ubuntu not using nvOC. And across multiple 8 GPU rigs, the delta adds up.
Thanks!
|
|
|
|
|
