i do not think so.!
i have 3Gb GPU 280x and 16GB free memory for CPU usage.
when i plot with CPU i'm able to plot with 8000 stagger size!
the gpu it is working... up and down but it is working.
maybe be, the pauses, are while HD is writing nonces.
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 914. (Read 2171083 times)
September 09, 2014, 08:21:40 AM
hum..
i do not think so.!
i have 3Gb GPU 280x and 16GB free memory for CPU usage.
when i plot with CPU i'm able to plot with 8000 stagger size!
the gpu it is working... up and down but it is working.
maybe be, the pauses, are while HD is writing nonces.
i do not think so.!
i have 3Gb GPU 280x and 16GB free memory for CPU usage.
when i plot with CPU i'm able to plot with 8000 stagger size!
the gpu it is working... up and down but it is working.
maybe be, the pauses, are while HD is writing nonces.
September 09, 2014, 08:21:13 AM
drivers 13.9 and 280x works fine with 4000 stagger
i only have 8gb ram so thats probably why I cant go with 8000 stagger
i only have 8gb ram so thats probably why I cant go with 8000 stagger
September 09, 2014, 08:15:52 AM
Any problem if i mix in the same dir, plots generated with different stagger size?
maybe the miner will have some issue?
maybe the miner will have some issue?
i can't run gpuplotter for stagger size >4000
see below.
with 8000 i get bad_alloc error
To plot with a stagger size of 8000, you will need 2GB of RAM on the CPU side and 4GB of RAM on the GPU side.
Here, the error refers to the CPU side.
September 09, 2014, 08:08:45 AM
Did anyone compile dcct on freenas yet?
Quote
make
gcc -O3 -o dcct-miner dcct-miner.c shabal.o -lpthread
dcct-miner.c: In function 'work_i':
dcct-miner.c:191: error: 'O_LARGEFILE' undeclared (first use in this function)
dcct-miner.c:191: error: (Each undeclared identifier is reported only once
dcct-miner.c:191: error: for each function it appears in.)
*** [miner] Error code 1
gcc -O3 -o dcct-miner dcct-miner.c shabal.o -lpthread
dcct-miner.c: In function 'work_i':
dcct-miner.c:191: error: 'O_LARGEFILE' undeclared (first use in this function)
dcct-miner.c:191: error: (Each undeclared identifier is reported only once
dcct-miner.c:191: error: for each function it appears in.)
*** [miner] Error code 1
September 09, 2014, 08:07:59 AM
anyone got the gpu-plotter to work with a Nvidia card? just tried with my 660, but 64 thread did not work, and 16 thread crashed the driver so I had to reboot 
why dont u start with low thread first ? Like 4 ?
well, because it has 960 CUDA cores so I thought it would be safe ^^ I'll try once more with 4...
u are lucky ur card didn't blow up
always start low and work ur way up
if it can take 24/7 mining, it should also survive plotting ^^ but looks like the plotter is not optimized for nvidia (well...it's an OpenCL plotter, not CUDA). anyway, tried 4 threads, driver still crashes:
Code:
An OpenCL error occured in the generation process, aborting...
>>> [-5] Error in synchronous read
>>> [-5] Error in synchronous read
maybe u want to contact the nvidia master ?
https://bitcointalksearch.org/user/djm34-215787
September 09, 2014, 08:06:31 AM
anyone got the gpu-plotter to work with a Nvidia card? just tried with my 660, but 64 thread did not work, and 16 thread crashed the driver so I had to reboot
why dont u start with low thread first ? Like 4 ?
well, because it has 960 CUDA cores so I thought it would be safe ^^ I'll try once more with 4...
u are lucky ur card didn't blow up
always start low and work ur way up
if it can take 24/7 mining, it should also survive plotting ^^ but looks like the plotter is not optimized for nvidia (well...it's an OpenCL plotter, not CUDA). anyway, tried 4 threads, driver still crashes:
Code:
An OpenCL error occured in the generation process, aborting...
>>> [-5] Error in synchronous read
>>> [-5] Error in synchronous read
September 09, 2014, 08:06:10 AM
i just talked to them, they are going to update the wallet.
Though, admittedly, i dont know if that is the real issue.
Though, admittedly, i dont know if that is the real issue.
September 09, 2014, 08:05:43 AM
Anyone else having trouble with Polo withdrawls of Burst? They supposedly sent mine, but the TX id# isn't showing up...and neither are my coins...
BURST 12515.57534755 BURST-ZJ6P-GWDD-xxxxx-xxxxx 2014-09-09 04:19:26 COMPLETE: TXID# 16421789416147571369
Which is a shame, Thought Polo was stepping up? Now their losing coins?
BURST 12515.57534755 BURST-ZJ6P-GWDD-xxxxx-xxxxx 2014-09-09 04:19:26 COMPLETE: TXID# 16421789416147571369
Which is a shame, Thought Polo was stepping up? Now their losing coins?
No point posting here. Create support ticket on polo
September 09, 2014, 08:04:42 AM
Anyone else having trouble with Polo withdrawls of Burst? They supposedly sent mine, but the TX id# isn't showing up...and neither are my coins...
BURST 12515.57534755 BURST-ZJ6P-GWDD-xxxxx-xxxxx 2014-09-09 04:19:26 COMPLETE: TXID# 16421789416147571369
Which is a shame, Thought Polo was stepping up? Now their losing coins?
BURST 12515.57534755 BURST-ZJ6P-GWDD-xxxxx-xxxxx 2014-09-09 04:19:26 COMPLETE: TXID# 16421789416147571369
Which is a shame, Thought Polo was stepping up? Now their losing coins?
September 09, 2014, 08:02:36 AM
Why coinmarketcap.com dont show the total amount of burst ....
If now we have the 1.1.0 version with the API it is ok ?
If now we have the 1.1.0 version with the API it is ok ?
September 09, 2014, 08:01:46 AM
anyone got the gpu-plotter to work with a Nvidia card? just tried with my 660, but 64 thread did not work, and 16 thread crashed the driver so I had to reboot
why dont u start with low thread first ? Like 4 ?
well, because it has 960 CUDA cores so I thought it would be safe ^^ I'll try once more with 4...
u are lucky ur card didn't blow up
always start low and work ur way up
September 09, 2014, 08:01:12 AM
anyone got the gpu-plotter to work with a Nvidia card? just tried with my 660, but 64 thread did not work, and 16 thread crashed the driver so I had to reboot
why dont u start with low thread first ? Like 4 ?
well, because it has 960 CUDA cores so I thought it would be safe ^^ I'll try once more with 4...
September 09, 2014, 07:58:31 AM
anyone got the gpu-plotter to work with a Nvidia card? just tried with my 660, but 64 thread did not work, and 16 thread crashed the driver so I had to reboot
why dont u start with low thread first ? Like 4 ?
September 09, 2014, 07:56:42 AM
anyone got the gpu-plotter to work with a Nvidia card? just tried with my 660, but 64 thread did not work, and 16 thread crashed the driver so I had to reboot
September 09, 2014, 07:55:26 AM
Any problem if i mix in the same dir, plots generated with different stagger size?
maybe the miner will have some issue?
maybe the miner will have some issue?
UP UP UP UP
There is no problem. It will work
ty fane :-)
September 09, 2014, 07:54:15 AM
Any problem if i mix in the same dir, plots generated with different stagger size?
maybe the miner will have some issue?
maybe the miner will have some issue?
UP UP UP UP
There is no problem. It will work
September 09, 2014, 07:52:13 AM
Any problem if i mix in the same dir, plots generated with different stagger size?
maybe the miner will have some issue?
maybe the miner will have some issue?
UP UP UP UP
September 09, 2014, 07:52:00 AM
Any problem if i mix in the same dir, plots generated with different stagger size?
maybe the miner will have some issue?
maybe the miner will have some issue?
Same question.
Like i said before, don't know why not all the disk blink but blink alternately with simlinks (all plots in same folder) and only one miner. Where when i launch one miner for each disk they all blink in the same time.
Miner read one file at a time? if it, this is not better to read all in the same time?
September 09, 2014, 07:51:44 AM
Any problem if i mix in the same dir, plots generated with different stagger size?
maybe the miner will have some issue?
maybe the miner will have some issue?
i can't run gpuplotter for stagger size >4000
see below.
with 8000 i get bad_alloc error
September 09, 2014, 07:51:01 AM
I'm use gpuPlotGenerator 1.1.
I have error in two-videocards system (HD7850 & R9_270x with driver 14.6b):
I have error in two-videocards system (HD7850 & R9_270x with driver 14.6b):
Code:
Path: plots
Nonces: 68847637 to 69036053 (46 GB)
Process memory: 1024MB
Threads number: 256
--------------
Retrieving OpenCL platform
Retrieving OpenCL GPU device
Creating OpenCL context
Creating OpenCL command queue
Creating CPU buffer
Creating OpenCL GPU generation buffer
An OpenCL error occured in the generation process, aborting...
>>> [-61] Unable to create the OpenCL GPU generation buffer
and other error in system with HD5870 (driver 13.12):Nonces: 68847637 to 69036053 (46 GB)
Process memory: 1024MB
Threads number: 256
--------------
Retrieving OpenCL platform
Retrieving OpenCL GPU device
Creating OpenCL context
Creating OpenCL command queue
Creating CPU buffer
Creating OpenCL GPU generation buffer
An OpenCL error occured in the generation process, aborting...
>>> [-61] Unable to create the OpenCL GPU generation buffer
Code:
Path: plots
Nonces: 0 to 10000 (2 GB)
Process memory: 500MB
Threads number: 128
--------------
Retrieving OpenCL platform
Retrieving OpenCL GPU device
Creating OpenCL context
Creating OpenCL command queue
Creating CPU buffer
Creating OpenCL GPU generation buffer
Creating OpenCL GPU scoops buffer
Creating OpenCL program
Building OpenCL program
Creating OpenCL kernel
Setting OpenCL kernel arguments
Generating from nonce #0
An OpenCL error occured in the generation process, aborting...
>>> [-54] Error in kernel launch
Nonces: 0 to 10000 (2 GB)
Process memory: 500MB
Threads number: 128
--------------
Retrieving OpenCL platform
Retrieving OpenCL GPU device
Creating OpenCL context
Creating OpenCL command queue
Creating CPU buffer
Creating OpenCL GPU generation buffer
Creating OpenCL GPU scoops buffer
Creating OpenCL program
Building OpenCL program
Creating OpenCL kernel
Setting OpenCL kernel arguments
Generating from nonce #0
An OpenCL error occured in the generation process, aborting...
>>> [-54] Error in kernel launch
For the first error (-61 = CL_INVALID_BUFFER_SIZE), it is due to a lack of memory space in your GPU. Try with a lower stagger size.
For the second error (-54 = CL_INVALID_WORK_GROUP_SIZE), it is due to an incorrect threads number. Try with a lower threads number.
Jump to: