Bitcoin Forum
June 21, 2024, 07:18:38 AM *
News: Voting for pizza day contest
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 [5] 6 7 8 9 »
81  Alternate cryptocurrencies / Announcements (Altcoins) / Re: COINDASH - Future of trading - Token Sale 17th July 2017 on: July 09, 2017, 11:24:05 PM
I'm going to have to take a early lunch break to get in on this ICO Cheesy
82  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0017 on: July 08, 2017, 09:25:40 PM
I went to try to add the watchdog script, I made both scripts but I guess I am a bit confused on how to get it to work between the system booting up running terminal and these two.

As if you try to launch the second, it will error out with the original terminal running.
83  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0017 on: July 08, 2017, 08:20:42 PM
I just copied the content of the claymore 9.7 into 9.5 folder and run the miner. So far I'm getting 190mh/s mining eth from 6 nvidia gtx 1070 as for the 9.5 - the version on the 0017 onebash I was getting 183mh/s. Thinking this is a must to be implemented as soon as possible. PS- sry for my english Wink)

I will add 9.7 to the next version;

right now it should be simple to do what you have done.

download:

https://drive.google.com/drive/folders/0B69wv2iqszefdFZUV2toUG5HdlU

then extract the miner into the 9.5 folder

replacing the 9.5 version



Just did this and confirmed that it works well. I went from 180mh/s dual mining to 186 on ETH, 1200 on SC and now 1400. About a 3-4% upgrade. Not bad at all.
84  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0017 on: July 08, 2017, 07:33:52 PM
Got my second right up and running, currently tuning the 1060's with Ethminer, genoil fork on VER0017 nvOC.

So far getting around 149MH/s total on 6 cards with these settings. Short term stability is their, long term us currently unknown.

Getting about 24.83MH/s on each.

5 cards:
PL: 125
Core: -100
Mem: 1700

1 card:
PL: 125
Core: -100
Mem: 1700

Anybody else have settings for their 1060s as I am curious to what others have gotten so far.

Besides stability for the OC, going to be stepping down the power to optimize it.
Depending on the mobo I can get 25/26 MHs per 1060 under genoil with the watchdog script with -75 and +1450 with power limit at 82W.
With Claymore I was able to crank it up to 170/1700/82 and get another 1-2 MHs per card and it was relatively stable but when it did crash it did not recover without intervention  so for now I'm going with Genoil and finding different ways to deal with the remaining instability (which to me means a reboot ever 1-2 days at the moment).




That is awesome to hear! I am right below the 25MH/s. With your powerlimit you suggested, I haven't gotten to but it gave me a good baseline. I was not aware the 1060's are that power efficient even under a heavy OC. My 1070s I could barely go below 115 with such heavy OC on it.

Biggest reason I want Genoil is the no fee attached to the miner compared to claymore.

What watchdog script you talking about? Or did you make it?  

I linked IAmNotAJeep's script post on the OP.

I use an 85 powerlimit with 1060s currently.  I usually only test every 5 watts, and 80 began to effect hashrate, maybe 82 is the OPT.



Awesome, will get that script added to the rig! I completely overlooked it on the main page.
85  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0017 on: July 08, 2017, 07:32:21 PM
Got my second right up and running, currently tuning the 1060's with Ethminer, genoil fork on VER0017 nvOC.

So far getting around 149MH/s total on 6 cards with these settings. Short term stability is their, long term us currently unknown.

Getting about 24.83MH/s on each.

5 cards:
PL: 125
Core: -100
Mem: 1700

1 card:
PL: 125
Core: -100
Mem: 1700

Anybody else have settings for their 1060s as I am curious to what others have gotten so far.

Besides stability for the OC, going to be stepping down the power to optimize it.

these hashrates are better than the ones I am currently getting with my 1060 rigs; I will have to try these settings.  How long have they been stable?


One card was giving problems so its mem OC is now 1625 and the others are 1700. After the change going solid for about 4 hours now. Also dropped Power to 100 watts per card now. (3 of them are set at a min of 90, so going to drop them here in a few hours to see if 3 will go at 90 watts)
86  Economy / Computer hardware / Re: [WTS] Pre-built Mining Rigs on: July 08, 2017, 07:09:23 PM
The rig has been built! I am currently optimizing the rig!

Here is the link to it on nanopool: https://eth.nanopool.org/account/0xdc04faa92bb8fa95ed93a4a48bb72554985a97f2/Nex2

Here is a screen shot of the rig itself:

Current power draw per card is 110 watt ( I am pushing for around 100 watts per card with current OC)

Estimated power draw on ETH: (+/- 5%) 675 watts from wall

Screen shot of hash rate on ZEC: TBD

Current power draw on ZEC: TBD

Estimated power draw on ZEC: TBD

This item will be ready to ship within the next 72 hours, pending stability tests. If an individual is interested before hand and communicated I can setup their wallet addresses to make this unit plug and play for either ZEC or ETH! The final build will include settings for both pre-loaded on the flash drive. Also have original boxes of all equipment if individual also wants the boxes associated with the parts.

Price: $4400+shipping (Or can setup a pickup within Hampton Roads, Virginia Area)

Far too much money dude.
Just doing a quick look you could build the same rig for under $2500.

Good afternoon,

Giving a value just based on parts is quite inaccurate, their are many other aspects that are not being factored. As your statement of building the rig for under $2500, well from a parts perspective that is true depending on several factors however; it does not include labor time to configuration, optimization, troubleshooting(if necessary) to ultimately get a stable configuration with maximum performance. Secondly, you are also not considering the fact that even GTX 1060's as the prices have slightly inflated (not in comparison to 1070's) as most companies are restricting how many you are able to purchase or are completely out of stock.

You may have the expertise to build one, configure one, etc. but not everyone does. If I get the wallet information, this rig will be plug and play for whom ever purchases it. Nothing more needed to do.
87  Economy / Computer hardware / Re: [WTS] Pre-built Mining Rigs on: July 08, 2017, 04:42:52 PM
The rig has been built! I am currently optimizing the rig!

Here is the link to it on nanopool: https://eth.nanopool.org/account/0xdc04faa92bb8fa95ed93a4a48bb72554985a97f2/Nex2

Here is a screen shot of the rig itself:

Here is a screen shot of current hash rate on ETH:

Current power draw per card is 110 watt ( I am pushing for around 100 watts per card with current OC)

Estimated power draw on ETH: (+/- 5%) 675 watts from wall

Screen shot of hash rate on ZEC: TBD

Current power draw on ZEC: TBD

Estimated power draw on ZEC: TBD

This item will be ready to ship within the next 72 hours, pending stability tests. If an individual is interested before hand and communicated I can setup their wallet addresses to make this unit plug and play for either ZEC or ETH! The final build will include settings for both pre-loaded on the flash drive. Also have original boxes of all equipment if individual also wants the boxes associated with the parts.

Price: $4400+shipping (Or can setup a pickup within Hampton Roads, Virginia Area)
88  Alternate cryptocurrencies / Announcements (Altcoins) / Re: COINDASH - Future of trading - Token Sale 17th July 2017 on: July 08, 2017, 04:06:42 PM
Anyone else getting the MEW hack spam from users on the coindash slack? From my research it was ETC that got hacked not ETH.

I did not click on anything, I know better lol.
89  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0017 on: July 08, 2017, 03:59:20 PM
Got my second right up and running, currently tuning the 1060's with Ethminer, genoil fork on VER0017 nvOC.

So far getting around 149MH/s total on 6 cards with these settings. Short term stability is their, long term us currently unknown.

Getting about 24.83MH/s on each.

5 cards:
PL: 125
Core: -100
Mem: 1700

1 card:
PL: 125
Core: -100
Mem: 1700

Anybody else have settings for their 1060s as I am curious to what others have gotten so far.

Besides stability for the OC, going to be stepping down the power to optimize it.
Depending on the mobo I can get 25/26 MHs per 1060 under genoil with the watchdog script with -75 and +1450 with power limit at 82W.
With Claymore I was able to crank it up to 170/1700/82 and get another 1-2 MHs per card and it was relatively stable but when it did crash it did not recover without intervention  so for now I'm going with Genoil and finding different ways to deal with the remaining instability (which to me means a reboot ever 1-2 days at the moment).




That is awesome to hear! I am right below the 25MH/s. With your powerlimit you suggested, I haven't gotten to but it gave me a good baseline. I was not aware the 1060's are that power efficient even under a heavy OC. My 1070s I could barely go below 115 with such heavy OC on it.

Biggest reason I want Genoil is the no fee attached to the miner compared to claymore.

What watchdog script you talking about? Or did you make it?  
90  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0017 on: July 08, 2017, 01:27:27 PM
Got my second right up and running, currently tuning the 1060's with Ethminer, genoil fork on VER0017 nvOC.

So far getting around 149MH/s total on 6 cards with these settings. Short term stability is their, long term us currently unknown.

Getting about 24.83MH/s on each.

5 cards:
PL: 125
Core: -100
Mem: 1700

1 card:
PL: 125
Core: -100
Mem: 1700

Anybody else have settings for their 1060s as I am curious to what others have gotten so far.

Besides stability for the OC, going to be stepping down the power to optimize it.
91  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0017 on: July 05, 2017, 10:15:17 PM
What PCIe slots do you have them plugged into?

Tried changing all the slots because there are 3 cards, tried using 123, 456, 124, 235 etc.

Looking at your MB manual I would recommend slotting the GPUs into PCIX16, PCIEX4_1, PCIEX4_2 (from top to bottom slots 2, 4, 6) Also make sure the monitor is plugged into slot 2 or PCIEX16.

If it still isn't working may need to change some settings such as changing it all to Gen 2 or Gen 1 in the BIOS.

92  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0017 on: July 05, 2017, 09:59:39 PM
What with drivers under nvOC? Do we should use latest (newest) drivers? there is no problem in nvOC update, change, remove drivers? (in windows sometimes it is pain Sad )

BR and good job

v0017 uses the second to newest driver currently:

to Update the driver:

Click Ubuntu button on top left and type:

Code:
u

Click on software updater

Install updates

Click Ubuntu button on top left and type:

Code:
ad

Click on additional drivers

Select 381.22 driver

Click apply changes

Enter password and wait for it to finish applying changes

Reboot





Any hash difference on the new drivers ?
93  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0017 on: July 05, 2017, 09:58:49 PM
Heya man, awesome project but have two problems.

1) Have 6 rigs with 5 GPU on each ASUS 1060, and they work well with v0017.

Trying to make another rig with 3x ASUS 1070 dual OC but getting the following error in dmesg, it randomly sees and unsees a GPU - sometimes two GPU after reboot. If I start mining, the load jumps to 10-15 / 5sec and the system goes to unresponsive state. Tried replacing risers, no luck.

Rig with 3x 1070 is running exactly same hardware specs as any other 1060 that works great.
- Gigabyte Z270X Gaming K3
- 4GB RAM
- G4400 CPU

Code:
[   11.554804] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   11.554855] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   11.554883] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   11.554907] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   11.554932] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   11.554955] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   11.554979] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901585] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901630] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901656] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901681] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901705] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901728] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901751] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   81.820739] NVRM: RmInitAdapter failed! (0x24:0x65:1060)
[   81.825027] NVRM: rm_init_adapter failed for device bearing minor number 2
[   98.031090] alx 0000:06:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [1c:1b:0d:91:b4:91]
[   98.036072] alx 0000:06:00.0 enp6s0: renamed from eth0
[   98.055932] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[   98.056746] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[   98.057522] alx 0000:06:00.0 enp6s0: NIC Up: 100 Mbps Full
[   98.057743] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
[   99.017089] nvidia-modeset: Allocated GPU:0 (GPU-dc2aec1a-94de-a009-4336-d4a879e5da36) @ PCI:0000:01:00.0
[   99.747611] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.747654] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.747681] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.747705] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.747729] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.747752] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.747776] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.374992] nvidia-modeset: Allocated GPU:1 (GPU-6d1a8ede-d79a-6ad6-a2a5-f1d449b6b5dd) @ PCI:0000:07:00.0
[  100.554810] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.554854] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.554881] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.554905] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.554929] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.554952] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.554976] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.959944] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  100.959980] NVRM: rm_init_adapter failed for device bearing minor number 2
[  102.860179] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  102.860181] Bluetooth: BNEP filters: protocol multicast
[  102.860184] Bluetooth: BNEP socket layer initialized
[  109.907211] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  109.908095] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  109.908142] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  109.908170] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  109.908194] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  109.909014] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  109.909053] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  110.326085] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  110.326118] NVRM: rm_init_adapter failed for device bearing minor number 2
[  180.997458] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  180.997504] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  180.997531] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  180.997556] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  180.997579] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  180.997603] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  180.997627] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.400594] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  181.400629] NVRM: rm_init_adapter failed for device bearing minor number 2
[  181.413439] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.413485] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.413513] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.413538] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.413562] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.413586] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.413609] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.816764] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  181.817572] NVRM: rm_init_adapter failed for device bearing minor number 2
[  182.084881] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.084928] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.084956] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.084981] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.085004] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.085028] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.085051] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.505188] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  182.505231] NVRM: rm_init_adapter failed for device bearing minor number 2
[  182.713761] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.713807] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.713835] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.713860] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.713884] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.713908] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.713932] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  183.124177] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  183.124217] NVRM: rm_init_adapter failed for device bearing minor number 2
[  184.089772] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.089820] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.089848] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.089873] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.089898] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.089922] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.089946] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.527141] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  184.527174] NVRM: rm_init_adapter failed for device bearing minor number 2
[  184.888148] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.888196] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.888223] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.888248] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.888272] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.888295] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.888319] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.303152] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  185.303187] NVRM: rm_init_adapter failed for device bearing minor number 2
[  185.776271] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.776316] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.776343] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.776368] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.776392] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.776416] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.776440] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.190421] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  186.193080] NVRM: rm_init_adapter failed for device bearing minor number 2
[  186.363417] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.363462] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.363488] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.363513] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.363536] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.363559] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.363583] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.766576] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  186.766616] NVRM: rm_init_adapter failed for device bearing minor number 2
[  186.880321] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.880366] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.880393] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.880418] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.880441] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.880465] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.880488] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.288080] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  187.288120] NVRM: rm_init_adapter failed for device bearing minor number 2
[  187.390639] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.390683] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.390710] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.390734] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.390757] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.390781] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.390804] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.794130] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  187.794240] NVRM: rm_init_adapter failed for device bearing minor number 2
root@rig7:/home/m1# dmesg | less
root@rig7:/home/m1# uname -a
Linux rig7 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
root@rig7:/home/m1# nvidia-smi
Wed Jul  5 17:19:42 2017      
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 378.13                 Driver Version: 378.13                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1070    Off  | 0000:01:00.0      On |                  N/A |
|  0%   48C    P8     7W / 151W |    142MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 1070    Off  | 0000:07:00.0     Off |                  N/A |
|  0%   44C    P8     7W / 151W |      1MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
                                                                              
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      1232    G   /usr/lib/xorg/Xorg                             117MiB |
|    0      1704    G   compiz                                          22MiB |
+-----------------------------------------------------------------------------+

Code:
root@rig7:/home/m1# nvidia-smi
Wed Jul  5 17:55:47 2017       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 378.13                 Driver Version: 378.13                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1070    Off  | 0000:01:00.0      On |                  N/A |
| 32%   49C    P2    35W / 151W |    219MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 1070    Off  | 0000:07:00.0     Off |                  N/A |
|ERR!   49C    P8    N/A /  N/A |    106MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      1232    G   /usr/lib/xorg/Xorg                             105MiB |
|    0      1704    G   compiz                                           6MiB |
|    0      3166    C   /home/m1/SPccminer/ccminer                      95MiB |
|    1      3166    C   /home/m1/SPccminer/ccminer                      95MiB |
+-----------------------------------------------------------------------------+
WARNING: infoROM is corrupted at gpu 0000:07:00.0


2) Another problem is that on none of my rigs can't run custom fan speed and get the following error:

Code:
ERROR: Error assigning value 75 to attribute 'GPUTargetFanSpeed' (rig1:0[fan:0]) as specified in assignment '[fan:0]/GPUTargetFanSpeed=75' (Unknown Error).

Tried making changes in /etc/X11/xorg.conf but no luck, the devices (GPUs) are already there.


Thanks

What PCIe slots do you have them plugged into?
94  Economy / Computer hardware / [WTS] Pre-built Mining Rigs on: July 05, 2017, 08:30:13 PM
Hello everyone,

Do not have a technical background? Want to get into mining? Want some consulting or a whole rig built? I can help you!

I have built several rigs going all the way back to Scrypt mining with 7950s, 280x, 290s to present day on 1070s!

If you are interested in consulting services, please PM me details and we can go over prices.

This is my current build in my own house!

Link to nanopool https://eth.nanopool.org/account/0xdc04faa92bb8fa95ed93a4a48bb72554985a97f2/Nex

Link of rig: https://cdn.discordapp.com/attachments/282220913674551306/329605411378298882/20170628_085228.jpg

I will have a second rig ready to go by next week and to be sold! I am estimating it around 150-160mh/s for this build.

I will optimize power and overclocking for both ETH and ZEC for the rig. If interested please PM me. I am willingly to ship within the USA, prices for shipping will be negotiated.

I am also more then willing to use an escrow, I pick or buyer picks (just needs to be a reputable one)

Once rig is running, I will take a picture of the rig to be sold.
Parts of the rig:
PSU: Corsiar 1000 watt
CPU: Intel Celron G3930
MB: MSI 270A Pro
RAM: Crucial 4GB
USB: 32GB Sandisk Extreme
PCI risers: VER007 (6Pin GPU->SATA)
GPUs: 6x 1060s
OS: nvOC
Miner: Ethminer Genoil fork
Pre-built open airframe case (as seen in photo of my other rig)

95  Economy / Computer hardware / Re: (CANADA) Buying prebuilt mining rigs on: July 05, 2017, 06:06:35 PM
Please PM me to get more details I would be willingly to work with you.

I have built multiple rigs and different setups.
96  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0017 on: July 04, 2017, 07:41:43 PM
Putting up another rig here soon. Going to test out the mining Algo switching that was just put out a few pages back.

Anyone have suggested settings for 1060s? Saw some on the first page but wanted to see if anyone else has some.
97  Alternate cryptocurrencies / Announcements (Altcoins) / Re: COINDASH - Future of trading - Token Sale July 2017 on: July 03, 2017, 09:08:06 PM
I am really looking forward to this in several ways not just a ICO but also where it will go once it launches. I will likely use this as well Smiley
98  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0017 on: July 03, 2017, 03:50:58 PM
This is an AWESOME idea! I was curious though, do you really make more it being converted to BTC right away or mining the coins directly? Anyone with some feedback would be greatly appreciated.

The last time I had lots of miners running, I was mining coins directly (first with CryptoSwitcher, then with MinerSwitcher) and exchanging them manually.  With transaction fees from my altcoin wallets to the exchange, conversion fees at the exchange, and transaction fees from the exchange to my Bitcoin wallet, they would've all added up to a decent chunk of mining revenue.  With many of these (especially the transaction fees) being fixed fees instead of percentages, the effective percentage of fees would be even higher.  I also hadn't gotten around to automating

While I haven't yet run the numbers to quantify it, I suspect that if BTC is your goal, a service such as NiceHash is likely to work out better for a small-time operator like me.  Economies of scale work in their favor...when they go to exchange altcoins for Bitcoin, your holdings are sent along with everyone else's and processed in one transaction.  That's one transaction fee to send to the exchange and one fee to receive the results back.  It seems intuitive that this should result in more BTC in your wallet.  Whether it actually does, of course, would be an interesting test to run.

One way to minimize the impact of transaction fees if you mine directly would be to have your altcoin proceeds sent directly to exchange accounts.  Not all pools are compatible with this approach, though; in particular, any arrangement in which miners are paid out of a coinbase transaction (P2Pool, Eligius, etc.) is likely not going to work with an exchange wallet.  Beyond that, keeping substantial funds in an exchange wallet has never been a good idea.

These are very valid points, I am going to have to do some pondering on this idea.

Your sentence should be highlight and bolded lmao. One reason why I got my Trezor is the offline hardware wallet.
99  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0017 on: July 03, 2017, 03:47:13 PM
Seems like 6x pin powered risers solved my issue with 1050ti's crashing. Thanks a lot @fullzero and others

Now, I'm interested, is there a way to see all rigs on API and to be able to see that from outside network? If so, how to configure it with router? I got a MikroTik behind the 24-port switch.

Best way to do this is to setup a OpenVPN into the network and allowing it on the same subnet. Once you VPN, the connection will act just like if you were on the home network. It will also be secure if you use higher level of encryption like AES256-CBC.
100  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0017 on: July 03, 2017, 12:59:55 PM
I didn't change any IPv6 settings with nvOC.  I'm not sure what the problem might be.  If you figure it out let me know, so I can apply it for the next version.

The cmd:

Code:
sudo dhclient -v -r 

(might help solve the problem, but probably not)

As you guessed, it didn't help.

Quote
there is a website:

test-ipv6.com

it attempts to help you identify the source of IPv6 problems; it might help, but probably will only tell you what you already know.

I tried bringing this up in Links, but it needs JavaScript to work.  I'd need to move the rig closer to where I can plug in a monitor, keyboard, and mouse to see what SJWfox says...maybe tomorrow, as I also want to move nvOC off of an SD card in a USB reader stick to the mining rig's M.2 SATA SSD.

In the meantime, I've gotten enough of a workaround set up that (1) apt-get upgrade works and (2) I have an auto-switcher up and running, as mentioned in my previous post.

It will be nice when there is no more NAT to deal with; although there will need to be better parameter security.

This afternoon, I knocked together a simple profitability auto-switcher that works with nvOC and NiceHash:

https://gitlab.com/salfter/nvoc-nicehash-switcher

It might also work if you're mining elsewhere, though profitability is determined by NiceHash (as exposed through their API).  It's a Python script that gathers information about what's profitable and calls shell scripts to reconfigure overclocking settings and launch miners on a per-algorithm basis.  It replaces oneBash for normal operation; oneBash is only needed for initial setup or to add/remove GPUs (it manages /etc/X11/xorg.conf).

Nice work  Smiley

I will integrate this into the next oneBash / v0018. 

I will keep your default BTC address and ensure it is clear you implemented the instantaneous profit switching algorithm.

I do think with when using different algos in makes sense to have different clocks; however I don't think the settings for those should be spread out over a bunch of different bash files.

I will bring all the settings inside oneBash and make a:

SALFTER_NICEHASH_PROFIT_SWITCHING="YES"    YES / NO switch

Using your implementation; it should only require a few modifications to implement other targets such as 'lowest difficulty out of a given set of coins' and more. 

Thanks for providing another tool to the community,  Smiley

This is an AWESOME idea! I was curious though, do you really make more it being converted to BTC right away or mining the coins directly? Anyone with some feedback would be greatly appreciated.
Pages: « 1 2 3 4 [5] 6 7 8 9 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!