Latest posts of: aurigae

Show Posts
Pages: [1]

Alternate cryptocurrencies / Mining (Altcoins) / AMD VII VEGA 20 - Linux OpenCL

on: August 20, 2019, 06:28:40 PM

Anybody here with a vega 20 vii gpu and detected openCL device in linux? I tried 18.04.03 xubuntu with amdgpu pro and headless, also tried rocm from github - all on different kernels with dffierent grub settings - always ending up with a black screen on boot or no opencl device detected. Even contacted the amd support, got a reply, filed the bug report, got another reply theyre trying to figure if the problem is on my side ... Edit: - * main ubuntu 18.04.03 did not boot off usb with this card, black screen. - same result with arch and debian 10.

Bitcoin / Bitcoin Technical Support / Bitcoin hardfork - full node - what / when todo?

on: December 28, 2017, 11:23:06 AM

Ive got a bitcoin node , where can i read what todo for the hardfork? Do i have to delete local blocks and and git pull a specific branch?

Other / Off-topic / git poc diff - Hiding content from Git

on: December 16, 2017, 11:35:15 PM

Found this, interesting enough for a share since every coin is hosted on github. https://www.twistlock.com/2017/12/13/hiding-content-git-escape-sequence-twistlock-labs-experiment/

Economy / Services / [For Hire] Anything Linux

on: December 15, 2017, 04:22:10 PM

Short on cash, looking for work. I know Linux / Bash inside out. PM if interested.

Local / Trading und Spekulation / Bitcoin.de - support reagiert nicht

on: December 15, 2017, 05:09:07 AM

Habe versucht meinen alten Account bei bitcoin den über den Support wieder herzustellen. Der Support antwortet nicht da wohl geglaubt wird ich wäre ein Betrüger oder so Ich war von 2012 bis 2014 als die asic miner kamen mit bitcoin aktiv, hab damals nicht an asics geglaubt und zu lange in gpu rigs investiert, dann 2014 die Community verlassen... Aus der Zeit stammt auch mein Account bei bitcoin de. Nun hat sich in der Zwischenzeit mein Bankkonto und meine E-Mail geändert. Lange rede kurzer Sinn, bitcoin.de ist offenbar nicht in der Lage oder willens ein postident Verfahren oder eine Ausweiskopie mit offiziellen Briefen zu akzeptieren. Der Account bei bitcoin.de besteht noch, mein Name ist fest mit meinem alten Bankkonto verknüpft - der Support hat eingeräumt das es einen Account gibt der mit meiner alten Kontonummer übereinstimmt. Darüber hinaus musste ich 5€ überweisen damit dann der Support feststellt, dass es von meinem neuen Bankaccount überweisen wurde - obwohl ich ganz klar geschrieben hatte das mein Bankkonto und meine Email sich geändert hat. Jetzt hab ich den crypto rush komplett verpasst obwohl ich einer der ersten war (mtgox, bitcoinbets von coinjedi und bitclockers haben ihr übriges dazu getan hehe ), und der einzige Account wo vielleicht noch ein coin drauf ist kann ich nicht wieder herstellen.

Economy / Services / Linux Sysadmin looking for paid tasks

on: December 15, 2016, 07:59:59 PM

Can solve problems on linux, anything shell related. Will do for coins: ssh administration, setup, problem solving, building, pentesting if ownership of system is proven. Wont do system intrusion. Offers PM only, if its interesting ill reply. Do not post here, posts will be ignored. BTC & XMR accepted.

Alternate cryptocurrencies / Mining (Altcoins) / SGMINER - OpenCL.so location

on: December 10, 2016, 07:22:02 AM

Is there any way to a define custom OpenCL.so dir for sgminer building on linux?

Alternate cryptocurrencies / Mining (Altcoins) / UNOMP setup problems

on: November 24, 2016, 03:18:33 PM

Ive just setup a UNOMP poolserver , however, it appears something goes wrong. There appear to be two issues:

1. Difficulty, ive no clue what goes wrong ...
2. Stratum message

Code:

" Pool vertcoin Thread 1 Unknown stratum method from Vmg3ssendQp8aUXPB46yS65s5cdQMFkdxJ [127.0.0.1]: mining.extranonce.subscribe"

Coin setup is vertcoin, ive tried multiple difficulty settings but always receive the same result:

Code:

/opt/crypto/POOLS/UNOMP/unified-node-open-mining-portal [master|✚ 2…1] 
16:04 $ sudo node init.js
[2016-11-24 16:04:26.688] [INFO] [default] - New Relic
[2016-11-24 16:04:26.690] [DEBUG] [default] - NewRelic Monitor New Relic initiated
[2016-11-24 16:04:26.692] [INFO] [default] - POSIX Not Installed
[2016-11-24 16:04:26.692] [DEBUG] [default] - POSIX Connection Limit (Safe to ignore) POSIX module not installed and resource (connection) limit was not raised
[2016-11-24 16:04:26.692] [INFO] [default] - Run Workers
[2016-11-24 16:04:26.951] [DEBUG] [default] - Master PoolSpawner Spawned 1 pool(s) on 1 thread(s)
[2016-11-24 16:04:27.379] [INFO] [default] - New Relic
[2016-11-24 16:04:27.382] [INFO] [default] - POSIX Not Installed
[2016-11-24 16:04:27.382] [INFO] [default] - Run Workers
[2016-11-24 16:04:27.390] [INFO] [default] - Switching Setup Thread 1 Loading last proxy state from redis
[2016-11-24 16:04:27.400] [DEBUG] [default] - Pool vertcoin Thread 1 Share processing setup with redis (127.0.0.1:6379)
[2016-11-24 16:04:27.426] [DEBUG] [default] - Pool vertcoin Thread 1 started for vertcoin [VTC] {scrypt-n}
						Network Connected:	Mainnet
						Detected Reward Type:	POW
						Current Block Height:	619183
						Current Connect Peers:	16
						Current Block Diff:	45410376.99596288
						Network Difficulty:	45433348.83065856
						Network Hash Rate:	17.25 GH
						Stratum Port(s):	3008, 3032, 3256
						Pool Fee Percent:	1.6%
						Block polling every:	1000 ms
[2016-11-24 16:04:27.430] [DEBUG] [default] - Switching Setup scrypt-n Setting proxy difficulties after pool start
[2016-11-24 16:04:36.700] [DEBUG] [default] - Master CLI CLI listening on port 17117
[2016-11-24 16:04:44.102] [DEBUG] [default] - Pool vertcoin Thread 1 Authorized Vmg3ssendQp8aUXPB46yS65s5cdQMFkdxJ:x [127.0.0.1]
[2016-11-24 16:04:44.103] [DEBUG] [default] - Pool vertcoin Thread 1 Unknown stratum method from Vmg3ssendQp8aUXPB46yS65s5cdQMFkdxJ [127.0.0.1]: mining.extranonce.subscribe
[2016-11-24 16:05:22.427] [DEBUG] [default] - Pool vertcoin Thread 1 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[2016-11-24 16:05:28.499] [DEBUG] [default] - Pool vertcoin Thread 1 getting block notification via RPC polling
[2016-11-24 16:06:23.500] [DEBUG] [default] - Pool vertcoin Thread 1 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[2016-11-24 16:07:18.505] [DEBUG] [default] - Pool vertcoin Thread 1 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[2016-11-24 16:08:04.506] [FATAL] [default] - Pool vertcoin Thread 1 Share rejected: {"job":"5","ip":"127.0.0.1","worker":"Vmg3ssendQp8aUXPB46yS65s5cdQMFkdxJ","difficulty":756,"error":"low difficulty share of 0.000029056754730504036"}

Code:

found => 85b849ef ef49b885
[2016-11-24 16:11:13] DEBUG: job_id=8370302 9 xnonce2=02000000 time=16:10:58
[2016-11-24 16:11:13] GPU#1:start=7fffffff end=ffffffff range=80000000
[2016-11-24 16:11:13] [S/A/T]: 0/0/5, diff: 3.488, 51.86MH/s booooo
[2016-11-24 16:11:13] reject reason: low difficulty share of 0.000025572947909740987

Alternate cryptocurrencies / Mining (Altcoins) / CCminer tpruvot - cuda | benchmark errors

on: November 14, 2016, 02:56:13 PM

Anybody who can tell me what this errors / warnings mean?

Code:

 possible 16 MB memory leak in heavy! 7817 MB free

Code:

Cuda error in func 'neoscrypt_hash_k4' at line 1517 : misaligned address

Code:

✔ /opt/crypto/MINER/CCMINER/tpruvot/ccminer [cuda-8|…2] 
15:49 $ ./ccminer --benchmark
*** ccminer 1.8 for nVidia GPUs by tpruvot@github ***
    Built with the nVidia CUDA Toolkit 8.0

  Originally based on Christian Buchner and Christian H. project
  Include some of the work of djm34, sp, tsiv and klausT.

BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)

[2016-11-14 15:49:39] Starting benchmark mode with blakecoin
[2016-11-14 15:49:39] NVML GPU monitoring enabled.
[2016-11-14 15:49:39] 2 miner threads started, using 'blakecoin' algorithm.
[2016-11-14 15:49:40] GPU #0: Gigabyte GTX 1080, 5961.59 MH/s
[2016-11-14 15:49:40] GPU #0: Gigabyte GTX 1080, 5943.97 MH/s
[2016-11-14 15:49:40] GPU #1: MSI GTX 1080, 6000.20 MH/s
[2016-11-14 15:49:40] GPU #1: MSI GTX 1080, 6166.50 MH/s
[2016-11-14 15:49:40] GPU #1: blakecoin hashrate = 6083.35 MH/s
[2016-11-14 15:49:40] GPU #0: blakecoin hashrate = 5952.78 MH/s
[2016-11-14 15:49:40] Benchmark algo blake...
[2016-11-14 15:49:41] GPU #0: Gigabyte GTX 1080, 3431.57 MH/s
[2016-11-14 15:49:42] GPU #0: Gigabyte GTX 1080, 3388.90 MH/s
[2016-11-14 15:49:42] GPU #1: MSI GTX 1080, 3500.63 MH/s
[2016-11-14 15:49:42] GPU #1: MSI GTX 1080, 3494.29 MH/s
[2016-11-14 15:49:43] GPU #1: blake hashrate = 3497.46 MH/s
[2016-11-14 15:49:43] GPU #0: blake hashrate = 3410.23 MH/s
[2016-11-14 15:49:43] Benchmark algo blake2s...
[2016-11-14 15:49:45] GPU #0: Gigabyte GTX 1080, 2453.84 MH/s
[2016-11-14 15:49:45] GPU #1: MSI GTX 1080, 2450.98 MH/s
[2016-11-14 15:49:45] GPU #0: Gigabyte GTX 1080, 2423.51 MH/s
[2016-11-14 15:49:45] GPU #1: MSI GTX 1080, 2450.36 MH/s
[2016-11-14 15:49:45] GPU #1: blake2s hashrate = 2450.67 MH/s
[2016-11-14 15:49:45] GPU #0: blake2s hashrate = 2438.67 MH/s
[2016-11-14 15:49:46] Benchmark algo bmw...
[2016-11-14 15:49:47] GPU #0: Gigabyte GTX 1080, 2353.50 MH/s
[2016-11-14 15:49:47] GPU #1: MSI GTX 1080, 2394.96 MH/s
[2016-11-14 15:49:48] GPU #0: Gigabyte GTX 1080, 2343.01 MH/s
[2016-11-14 15:49:48] GPU #1: MSI GTX 1080, 2391.49 MH/s
[2016-11-14 15:49:48] GPU #1: bmw hashrate = 2393.22 MH/s
[2016-11-14 15:49:48] GPU #0: bmw hashrate = 2348.25 MH/s
[2016-11-14 15:49:49] Benchmark algo deep...
[2016-11-14 15:49:52] GPU #0: Gigabyte GTX 1080, 49.43 MH/s
[2016-11-14 15:49:52] GPU #1: MSI GTX 1080, 49.16 MH/s
[2016-11-14 15:49:58] GPU #0: Gigabyte GTX 1080, 49.44 MH/s
[2016-11-14 15:49:58] GPU #1: MSI GTX 1080, 49.20 MH/s
[2016-11-14 15:49:58] GPU #1: deep hashrate = 49.18 MH/s
[2016-11-14 15:49:58] GPU #0: deep hashrate = 49.44 MH/s
[2016-11-14 15:49:58] Benchmark algo decred...
[2016-11-14 15:50:00] GPU #0: Gigabyte GTX 1080, 3574.74 MH/s
[2016-11-14 15:50:01] GPU #0: Gigabyte GTX 1080, 3560.69 MH/s
[2016-11-14 15:50:01] GPU #1: MSI GTX 1080, 3685.93 MH/s
[2016-11-14 15:50:02] GPU #1: MSI GTX 1080, 3685.87 MH/s
[2016-11-14 15:50:02] GPU #1: decred hashrate = 3685.90 MH/s
[2016-11-14 15:50:02] GPU #0: decred hashrate = 3567.72 MH/s
[2016-11-14 15:50:03] Benchmark algo fresh...
[2016-11-14 15:50:07] GPU #0: Gigabyte GTX 1080, 17.70 MH/s
[2016-11-14 15:50:08] GPU #1: MSI GTX 1080, 17.73 MH/s
[2016-11-14 15:50:08] GPU #0: Gigabyte GTX 1080, 17.66 MH/s
[2016-11-14 15:50:18] GPU #1: MSI GTX 1080, 17.71 MH/s
[2016-11-14 15:50:18] GPU #1: fresh hashrate = 17.72 MH/s
[2016-11-14 15:50:18] GPU #0: fresh hashrate = 17.68 MH/s
[2016-11-14 15:50:18] Benchmark algo fugue256...
[2016-11-14 15:50:20] GPU #0: Gigabyte GTX 1080, 580.27 MH/s
[2016-11-14 15:50:20] GPU #1: MSI GTX 1080, 582.72 MH/s
[2016-11-14 15:50:24] GPU #1: MSI GTX 1080, 584.55 MH/s
[2016-11-14 15:50:27] GPU #0: Gigabyte GTX 1080, 586.90 MH/s
[2016-11-14 15:50:27] GPU #0: fugue256 hashrate = 583.58 MH/s
[2016-11-14 15:50:27] GPU #1: fugue256 hashrate = 583.63 MH/s
[2016-11-14 15:50:28] Benchmark algo groestl...
[2016-11-14 15:50:29] GPU #1: MSI GTX 1080, 48.93 MH/s
[2016-11-14 15:50:29] GPU #0: Gigabyte GTX 1080, 46.49 MH/s
[2016-11-14 15:50:37] GPU #1: MSI GTX 1080, 49.41 MH/s
[2016-11-14 15:50:37] GPU #0: Gigabyte GTX 1080, 46.99 MH/s
[2016-11-14 15:50:37] GPU #0: groestl hashrate = 46.74 MH/s
[2016-11-14 15:50:37] GPU #1: groestl hashrate = 49.17 MH/s
[2016-11-14 15:50:37] Benchmark algo heavy...
[2016-11-14 15:50:38] GPU #1: MSI GTX 1080, 57.07 MH/s
[2016-11-14 15:50:38] GPU #1: MSI GTX 1080, 54.68 MH/s
[2016-11-14 15:50:40] GPU #0: Gigabyte GTX 1080, 59.51 MH/s
[2016-11-14 15:50:44] GPU #0: Gigabyte GTX 1080, 58.67 MH/s
[2016-11-14 15:50:45] GPU #0: heavy hashrate = 59.09 MH/s
[2016-11-14 15:50:45] GPU #1: heavy hashrate = 55.87 MH/s
[2016-11-14 15:50:45] GPU #0: possible 16 MB memory leak in heavy! 7817 MB free
[2016-11-14 15:50:45] GPU #1: possible 16 MB memory leak in heavy! 7974 MB free
[2016-11-14 15:50:46] Benchmark algo keccak...
[2016-11-14 15:50:47] GPU #0: Gigabyte GTX 1080, 414.92 MH/s
[2016-11-14 15:50:47] GPU #1: MSI GTX 1080, 408.94 MH/s
[2016-11-14 15:50:49] GPU #1: MSI GTX 1080, 750.21 MH/s
[2016-11-14 15:50:52] GPU #0: Gigabyte GTX 1080, 762.75 MH/s
[2016-11-14 15:50:52] GPU #0: keccak hashrate = 588.83 MH/s
[2016-11-14 15:50:52] GPU #1: keccak hashrate = 579.57 MH/s
[2016-11-14 15:50:52] Benchmark algo jackpot...
[2016-11-14 15:50:54] GPU #1: MSI GTX 1080, 8948.20 kH/s
[2016-11-14 15:50:54] GPU #0: Gigabyte GTX 1080, 8843.07 kH/s
[2016-11-14 15:50:56] GPU #1: MSI GTX 1080, 9755.32 kH/s
[2016-11-14 15:50:57] GPU #0: Gigabyte GTX 1080, 9582.89 kH/s
[2016-11-14 15:50:57] GPU #0: jackpot hashrate = 9212.98 kH/s
[2016-11-14 15:50:57] GPU #1: jackpot hashrate = 9351.76 kH/s
[2016-11-14 15:50:57] Benchmark algo lbry...
[2016-11-14 15:50:58] GPU #0: Gigabyte GTX 1080, 329.16 MH/s
[2016-11-14 15:50:58] GPU #1: MSI GTX 1080, 344.88 MH/s
[2016-11-14 15:50:58] GPU #1: MSI GTX 1080, 344.89 MH/s
[2016-11-14 15:50:59] GPU #0: Gigabyte GTX 1080, 323.70 MH/s
[2016-11-14 15:51:00] GPU #0: lbry hashrate = 326.43 MH/s
[2016-11-14 15:51:00] GPU #1: lbry hashrate = 344.89 MH/s
[2016-11-14 15:51:00] GPU #0: possible 514 MB memory leak in lbry! 7319 MB free
[2016-11-14 15:51:00] GPU #1: possible 514 MB memory leak in lbry! 7476 MB free
[2016-11-14 15:51:00] Benchmark algo luffa...
[2016-11-14 15:51:00] GPU #0: Gigabyte GTX 1080, 13.84 GH/s
[2016-11-14 15:51:08] GPU #1: MSI GTX 1080, 404.06 MH/s
[2016-11-14 15:51:10] GPU #0: Gigabyte GTX 1080, 453.56 MH/s
[2016-11-14 15:51:14] GPU #1: MSI GTX 1080, 403.95 MH/s
[2016-11-14 15:51:16] GPU #1: luffa hashrate = 404.01 MH/s
[2016-11-14 15:51:16] GPU #0: luffa hashrate = 7147.46 MH/s
[2016-11-14 15:51:16] Benchmark algo lyra2...
[2016-11-14 15:51:23] GPU #0: Gigabyte GTX 1080, 1980.78 kH/s
[2016-11-14 15:51:24] GPU #1: MSI GTX 1080, 1987.32 kH/s
[2016-11-14 15:51:24] GPU #0: Gigabyte GTX 1080, 1956.24 kH/s
[2016-11-14 15:51:33] GPU #1: MSI GTX 1080, 2193.18 kH/s
[2016-11-14 15:51:33] GPU #1: lyra2 hashrate = 2090.25 kH/s
[2016-11-14 15:51:33] GPU #0: lyra2 hashrate = 1968.51 kH/s
[2016-11-14 15:51:33] Benchmark algo lyra2v2...
[2016-11-14 15:51:34] GPU #0: Gigabyte GTX 1080, 41.61 MH/s
[2016-11-14 15:51:34] GPU #1: MSI GTX 1080, 43.63 MH/s
[2016-11-14 15:51:34] GPU #0: Gigabyte GTX 1080, 43.08 MH/s
[2016-11-14 15:51:43] GPU #1: MSI GTX 1080, 46.21 MH/s
[2016-11-14 15:51:43] GPU #1: lyra2v2 hashrate = 44.92 MH/s
[2016-11-14 15:51:43] GPU #0: lyra2v2 hashrate = 42.34 MH/s
[2016-11-14 15:51:43] Benchmark algo myr-gr...
[2016-11-14 15:51:44] GPU #1: MSI GTX 1080, 88.74 MH/s
[2016-11-14 15:51:44] GPU #0: Gigabyte GTX 1080, 85.72 MH/s
[2016-11-14 15:51:54] GPU #1: MSI GTX 1080, 92.01 MH/s
[2016-11-14 15:51:54] GPU #0: Gigabyte GTX 1080, 87.02 MH/s
[2016-11-14 15:51:54] GPU #0: myr-gr hashrate = 86.37 MH/s
[2016-11-14 15:51:54] GPU #1: myr-gr hashrate = 90.37 MH/s
[2016-11-14 15:51:54] GPU #1: Using 65536 cuda threads
[2016-11-14 15:51:54] Benchmark algo neoscrypt...
[2016-11-14 15:51:55] GPU #0: Using 65536 cuda threads
Cuda error in func 'neoscrypt_hash_k4' at line 1517 : misaligned address.

Alternate cryptocurrencies / Mining (Altcoins) / Ubuntu dual geforce 1080

on: November 10, 2016, 02:27:06 PM

Got a second geforce 1080, first card isa gigabyte, second msi - running on ubuntu 16.04 with nvda pro driver 367.57. Heres the issue: My net adaper only has 2*8 pcie The first card, has 8 pin connectors (gigabyte 1080) The second has 8 & 6 (msi 1080 gamingx) ive put in the second msi card, botted up - fired up the ccminer and eth miner, both failed to detect the second card and refused to mine. Do i need to make additional software changes or is just the power connector missing - as i was told the card should run without the second 6 pin pcie. PS: i cant put on a cuda bridge right now as the cards have very different dimensions. thx4 any help!

Alternate cryptocurrencies / Mining (Altcoins) / CCMINER tpruvot - 16.04.1 - upgrade 4.4.0-47-generic | does not validate on CPU!

on: November 10, 2016, 02:47:25 AM

Code:

Just dist-upgraded to the recent [b]4.4.0-47[/b] on ubuntu [b]16.04.1[/b] and tpruvot ccminer stopped working, [b]only tested lyra2v2 thus far[/b
[b]
GPU #0: result for XXXXX does not validate on CPU![/b]

[code]
make[2]: Leaving directory '/opt/crypto/MINER/CCMINER/tpruvot/ccminer'
make[1]: Leaving directory '/opt/crypto/MINER/CCMINER/tpruvot/ccminer'
droidx@droidx:/opt/crypto/MINER/CCMINER/tpruvot/ccminer$ ./ccminer -a lyra2v2 -o stratum+tcp://url:port -u user -p x 
*** ccminer 1.8 for nVidia GPUs by tpruvot@github ***
    Built with the nVidia CUDA Toolkit 8.0

  Originally based on Christian Buchner and Christian H. project
  Include some of the work of djm34, sp, tsiv and klausT.

BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)

[2016-11-10 03:39:54] Starting on stratum+tcp://url:port
[2016-11-10 03:39:54] NVML GPU monitoring enabled.
[2016-11-10 03:39:54] 1 miner thread started, using 'lyra2v2' algorithm.
[2016-11-10 03:39:55] Stratum difficulty set to 8
[2016-11-10 03:39:59] GPU #0: Gigabyte GTX 1080, 47.29 MH/s
[2016-11-10 03:40:04] GPU #0: result for 17364f41 does not validate on CPU!
[2016-11-10 03:40:07] GPU #0: result for 1dfa3d4f does not validate on CPU!
[2016-11-10 03:40:07] GPU #0: result for 1fa17748 does not validate on CPU!
[2016-11-10 03:40:08] Stratum difficulty set to 35.324
[2016-11-10 03:40:08] url:port lyra2v2 block 610832
^C[2016-11-10 03:40:18] SIGINT received, exiting

Code:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.1 LTS
Release:	16.04
Codename:	xenial

Code:

$ uname -a
Linux droidx 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Code:

droidx@droidx:/opt/crypto/MINER/CCMINER/tpruvot/ccminer$ nvidia-smi
Thu Nov 10 03:41:13 2016       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 375.10                 Driver Version: 375.10                    |
|-------------------------------+----------------------+----------------------+
| 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 1080    Off  | 0000:01:00.0      On |                  N/A |
| 35%   48C    P0    45W / 200W |    126MiB /  8113MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      1197    G   /usr/lib/xorg/Xorg                             124MiB |
+-----------------------------------------------------------------------------+

Code:

$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2016 NVIDIA Corporation
Built on Sun_Sep__4_22:14:01_CDT_2016
Cuda compilation tools, release 8.0, V8.0.44

[/code]

Alternate cryptocurrencies / Altcoin Discussion / Ubuntu 16.10 - build source - libboost version

on: November 08, 2016, 02:27:48 AM

Which libboost version are currently supported/working? trying to build on ubuntu 16.10 with libboost 1.61 but failing somehow, expecting libbost to be the issue.

Alternate cryptocurrencies / Mining (Altcoins) / CCMINER tpruvot cuda8 branch on nvda 367.57 Cuda error in func 'neoscrypt_hash_k

on: November 07, 2016, 12:55:20 AM

CCMINER tpruvot cuda8 branch on nvda 367.57 Cuda error in func 'neoscrypt_hash_k on xubuntu 16.10 The error occured after upgrading from the previous nvda prop driver. Rebuild error: 1. Default installation of Xubuntu 16.10 2. install nvidia prop driver 367.57 3. Clone and compile CCminer tpruvot cuda 8 branch with gcc 4.8 (http://askubuntu.com/questions/724872/downgrade-gcc-from-5-2-1-to-4-9-ubuntu-15-10) and the Cflags / symlinks for the prop driver https://github.com/tpruvot/ccminer/blob/linux/INSTALL. 4. run ./build.sh from the git repository directory 5. Run ./ccminer -a neoscrypt Code: [2016-11-07 01:52:42] Starting on stratum+tcp://MININGPOOLADDRESS:PORT [2016-11-07 01:52:42] NVML GPU monitoring enabled. [2016-11-07 01:52:42] 1 miner thread started, using 'neoscrypt' algorithm. [2016-11-07 01:52:42] Stratum difficulty set to 256 [2016-11-07 01:52:43] GPU #0: Using x cuda threads Cuda error in func 'neoscrypt_hash_k4' at line 1517 : misaligned address. Any idea how to fix that without downgrading to the previous nvda driver?

Alternate cryptocurrencies / Mining (Altcoins) / Geforce 1080 debian jessie - what to mine?

on: October 31, 2016, 12:54:58 AM

HI BT, got a geforce 1080 just recently, and why not put it to work My Sys is debian jessie, would prefer to stay that way but could flip to win OS. Haven’t mined for a while, no problem to do the setup stuff, just not up to date. Currently mining eth but thats probably not that profitable?

Bitcoin / Bitcoin Discussion / How many nodes?

on: May 09, 2016, 08:30:30 PM

How many nodes would an attacker need to control to take full control of a blockchain network? Im not in any way a blochchain dev - But the question seems quite interesting. Lets hypothetically consider an attacker could gaincontrol of x% of active nodes - is there a treshhold where the attacker could be considered in full control of the blockchain network?

Pages: [1]