new client ver 8.8 working well after taking a day off mining with a single diamond saphire 7970 although i got lucky & hit a block of feathercoin :-)
getting 2.8 ghs with cg miner
--shaders 2048 --blake256 --gpu-engine 1175 --gpu-memclock 700 --threadconcurrency 22392 -w 264 -s 1 - E 3 -I 14
other settings i had used with reaper i mentioned in this post on another forum
https://cryptocointalk.com/topic/1446-if-you-want-to-mine-blake-coin-with-a-gpu-here-is-some-information/
thanks Blue for such a fast fix. I like blake coin !
Appears difficulty is lower tonight at 960 so hopefully I hit a few blocks !
Topic: [ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net - page 173. (Read 409569 times)
November 04, 2013, 07:36:38 PM
November 04, 2013, 03:17:04 PM
http://imgur.com/DEcOktK
It might be just me guys....but I dont think I'm getting 200Mh/S
(Wont let me put a strait image link. That blows.)
your doing better than the cgminer port. 40 MH on a 560ti It might be just me guys....but I dont think I'm getting 200Mh/S
(Wont let me put a strait image link. That blows.)
November 04, 2013, 02:49:27 PM
Well I should have a Enterpoint Cairnsmore1 Bitcoin miner later this week just to play around with. I'll use it for fireflycoin and cubits until we are ready for testing on Blake.
November 04, 2013, 01:25:10 PM
http://imgur.com/DEcOktK
It might be just me guys....but I dont think I'm getting 200Mh/S
(Wont let me put a strait image link. That blows.)
It might be just me guys....but I dont think I'm getting 200Mh/S
(Wont let me put a strait image link. That blows.)
Thank you for testing not a lot of miners are using Nvidia cards due to the need to write specific Cuda code rather than the OpenCL code
I would like to see more from Nvidia they are powerful cards but it takes some specific optimisation to be able to tap into that hashing power
November 04, 2013, 10:07:05 AM
It might be just me guys....but I dont think I'm getting 200Mh/S
more info would help. what graphics card are you using? and what settings for reaper?
I am using a AMD 7950 @ 1000Mhz/ 600Mhz and my blakecoin.conf for reaper currently has these settings:
Quote
worksize 256
aggression 26
threads_per_gpu 1
cpu_mining_threads 0
vectors 1
worksize 32
aggression 26
threads_per_gpu 1
cpu_mining_threads 0
vectors 1
worksize 32
With this card and configuration I'm getting ~1.98Gh/s
[edit]LOL i didnt look at your pic closely enough, I see now that its an Nvidia 550. Don't know what hashrate should be expected from it but i'm not surprised its much less since Nvidia cards just aren't designed for hashing
[/edit] November 04, 2013, 02:37:30 AM
http://imgur.com/DEcOktK
It might be just me guys....but I dont think I'm getting 200Mh/S
(Wont let me put a strait image link. That blows.)
It might be just me guys....but I dont think I'm getting 200Mh/S
(Wont let me put a strait image link. That blows.)
November 04, 2013, 01:09:17 AM
before i posted my last message it said "currently building linux wallet", and by the time i posted you had the link for the linux 0.8.8 up. so i have switched to that and so far it seems to be working fine. thanks for the update 
perhaps my previous post will still be useful if anyone else had some blocks show up as orphans while using 0.8.7; i think they just showed up as orphans due to the sync error and not due to actually being orphans.
perhaps my previous post will still be useful if anyone else had some blocks show up as orphans while using 0.8.7; i think they just showed up as orphans due to the sync error and not due to actually being orphans.I do both x64 and x86 for Linux so it just takes me a little longer to compile, I could not get to sleep thinking about a possible bug and it was a bug in the way I was trying to increase the interval to 120 blocks
In the future I will have to write an if statement in each function that calls the interval and do a block height check but for now I will leave it working rather than add more random features
Sorry about the issues in 0.8.7 it did not show up in my testing I will make some additions to how I am testing to try and avoid this happening
Ref:
Reason for wanting the change to 30 seconds is to lower the overall difficulty and help the average it is using for the re-target
the TargetSpacing (this is what I was changing from 3mins - 30secs) this is the target time that the wallet uses to calculate the difficulty in relation to the TargetTimespan and the Interval is the amount of blocks between re-targets.
Edit:
always feel free to post errors, issues, solutions or just to check everyone else is getting similar results I do appreciate the feedback
and like you said the info might be useful to others
November 04, 2013, 12:24:31 AM
before i posted my last message it said "currently building linux wallet", and by the time i posted you had the link for the linux 0.8.8 up. so i have switched to that and so far it seems to be working fine. thanks for the update perhaps my previous post will still be useful if anyone else had some blocks show up as orphans while using 0.8.7; i think they just showed up as orphans due to the sync error and not due to actually being orphans.
perhaps my previous post will still be useful if anyone else had some blocks show up as orphans while using 0.8.7; i think they just showed up as orphans due to the sync error and not due to actually being orphans. November 04, 2013, 12:12:26 AM
after updating to 0.8.7, i had several blocks found but some of which appeared to be orphans. since there was no 0.8.8 for linux yet, i reverted to 0.8.6 and it said all my recent blocks were orphans. however 0.8.6 seemed to sync fine, so when i then switched again to 0.8.7 it showed that none were orphans and each had several confirmations. so perhaps going back to 0.8.6 allowed my blockchain to synchronize properly, but at any rate hopefully the 0.8.8 will clear it all up. if you have gotten orphans after updating to 0.8.7 i would suggest trying going back to 0.8.6 to synchronize, as a possible solution if anyone else is having similar issue
try 0.8.8 might need to rebuild your chain
November 04, 2013, 12:11:12 AM
(edit) this post was before the 0.8.8 wallet for linux was available, pls update instead of reverting to 0.8.6 (/edit)
after updating to 0.8.7, i had several blocks found but some of which appeared to be orphans. since there was no 0.8.8 for linux yet, i reverted to 0.8.6 and it said all my recent blocks were orphans. however 0.8.6 seemed to sync fine, so when i then switched again to 0.8.7 it showed that none were orphans and each had several confirmations. so perhaps going back to 0.8.6 allowed my blockchain to synchronize properly, but at any rate hopefully the 0.8.8 will clear it all up. if you have gotten orphans after updating to 0.8.7 i would suggest trying going back to 0.8.6 to synchronize, as a possible solution if anyone else is having similar issue
after updating to 0.8.7, i had several blocks found but some of which appeared to be orphans. since there was no 0.8.8 for linux yet, i reverted to 0.8.6 and it said all my recent blocks were orphans. however 0.8.6 seemed to sync fine, so when i then switched again to 0.8.7 it showed that none were orphans and each had several confirmations. so perhaps going back to 0.8.6 allowed my blockchain to synchronize properly, but at any rate hopefully the 0.8.8 will clear it all up. if you have gotten orphans after updating to 0.8.7 i would suggest trying going back to 0.8.6 to synchronize, as a possible solution if anyone else is having similar issue
November 03, 2013, 11:28:36 PM
Sync bug in 0.8.7 fixed in 0.8.8
Blakecoin Wallet Release 0.8.8
Github updated
Windows
http://blakecoin.org/Blakecoin-0.8.8-WIN.7z
Linux
http://blakecoin.org/Blakecoin-0.8.8-LIN.7z
Blakecoin Wallet Release 0.8.8
Github updated
Windows
http://blakecoin.org/Blakecoin-0.8.8-WIN.7z
Linux
http://blakecoin.org/Blakecoin-0.8.8-LIN.7z
November 03, 2013, 08:41:07 PM
Odd had reloaded and I had green checkmark. Opened debug to info tab and it said Block 19709.
closed window and I'm syncing again 3 hrs behind.
closed window and I'm syncing again 3 hrs behind.
November 03, 2013, 08:27:11 PM
Same problem here - tried with wallet & without / Tried everything / Now fresh install the blockchain is at 19 of 19762 :-(
November 03, 2013, 07:35:15 PM
it loaded under win7 64 for me
v0.8.7.0-g8c5e74e-beta
v0.8.7.0-g8c5e74e-beta
i had to redownload the chain and stuck at 19... second client is probably on different chain as I am finding blocks but block height is 19731
November 03, 2013, 06:55:26 PM
it loaded under win7 64 for me
v0.8.7.0-g8c5e74e-beta
v0.8.7.0-g8c5e74e-beta
November 03, 2013, 06:47:26 PM
Blakecoin wallet version 0.8.7 Released
Github updated
Windows
http://blakecoin.org/Blakecoin-0.8.7-WIN.7z
Linux
http://blakecoin.org/Blakecoin-0.8.7-LIN.7z
Please update Your wallets before sending any Blakecoin!
edit:
the wallet might re-sync a few times as everyone updates, if it gets stuck for more than 5 minutes try to close and reopen
Github updated
Windows
http://blakecoin.org/Blakecoin-0.8.7-WIN.7z
Linux
http://blakecoin.org/Blakecoin-0.8.7-LIN.7z
Please update Your wallets before sending any Blakecoin!
edit:
the wallet might re-sync a few times as everyone updates, if it gets stuck for more than 5 minutes try to close and reopen
windows client dont want to download the blockchain, and link to 8.6 version downloads 8.7 actually
November 03, 2013, 06:39:32 PM
i am curious what the motivation is for switching to 30 second block? Will the block reward change, or stay at 25blc + inflation? also does changing the block target time actually change much, or just make it look faster?
November 03, 2013, 06:16:11 PM
I appreciate the feedback you never know if it is a bug so always best to report weird behavior after an update
I was just about to grab some sleep so any problems backup your wallets, revert to 0.8.6 and post a report of the error, this was a small update and is not supposed to create any issues beyond a few hours while everyone updates
sync bug fixed in 0.8.8 please update
sync bug fixed in 0.8.8 please update
November 03, 2013, 05:47:27 PM
of course as soon as i say something about, the block number goes up
I was also wondering if it is possible to compile the linux wallet with dependencies included? i had to install libdb and several libboost packages before blakecoin-qt would launch. If not having them included in the binary, a list of dependencies at least would be helpful.
November 03, 2013, 02:27:26 PM
Blakecoin wallet version 0.8.7 Released
Sync Bug Please use 0.8.8
Sync Bug Please use 0.8.8
Jump to: