Topic: [ANN] Ethereum: Welcome to the Beginning - page 982. (Read 2007090 times)
http://www.coindesk.com/bitgo-engineers-ethereum-wallet-ether-li/ big btc boys are wanting in on the ETH,lol yeaaaa
Last time I do this… just got a message from the beyond
DUDE COINBASE VERRY LIKELY TO ADD ETH,LOL, oops caps by accident,lol. if eth / usd margin bitfinex this week, and coinbase do eth/usd, im goin 100% eth as it will only keep goin up from this week onwards imo, then i go on holiday with a big freakin smiley,lol
BTW: Ethereum does not need a presence in BTT, its just a bonus…
true DUDE COINBASE VERRY LIKELY TO ADD ETH,LOL, oops caps by accident,lol. if eth / usd margin bitfinex this week, and coinbase do eth/usd, im goin 100% eth as it will only keep goin up from this week onwards imo, then i go on holiday with a big freakin smiley,lol
BTW: Ethereum does not need a presence in BTT, its just a bonus…
what's the best desktop wallet for ETH? Thanks.
Check this one: https://github.com/ethereum/mist/releases
Thanks bro.
what's the best desktop wallet for ETH? Thanks.
Check this one: https://github.com/ethereum/mist/releases
Another two new dapps that have awesome potential..Makerdao and Dapple, along with Augur, Slockit and Plutus, things are looking real good for crypto 2016.
Anyone here suffering from DAG allocation problem with 3gb cards?!
Answered few post earlier - yes I have 3gb (280x) and had that problem.
what's the best desktop wallet for ETH? Thanks.
Anyone here suffering from DAG allocation problem with 3gb cards?!
No, 280x , all is ok
I have question too, anyone can show me hash for eth on NVIDIA cards ?
https://www.ethereum.org/, click chat at the bottom right...lots of ETHeads chatting away, might get u quicker response m8
Anyone here suffering from DAG allocation problem with 3gb cards?!
No, 280x , all is ok
I have question too, anyone can show me hash for eth on NVIDIA cards ?
Anyone here suffering from DAG allocation problem with 3gb cards?!
It has been asked probably numerous times, but what's the easiest way to check my computer's time and where to check it. Also how do I sync the time in the easiest way? My client has been stuck and it's not updating.
If you are using Windows, select the clock, change time date and settings, Internet time, Change settings, (select server) update now.Thanks, yes I am on Windows. Which server should I choose?
I used time.nist.gov
It has been asked probably numerous times, but what's the easiest way to check my computer's time and where to check it. Also how do I sync the time in the easiest way? My client has been stuck and it's not updating.
If you are using Windows, select the clock, change time date and settings, Internet time, Change settings, (select server) update now.Thanks, yes I am on Windows. Which server should I choose?
It has been asked probably numerous times, but what's the easiest way to check my computer's time and where to check it. Also how do I sync the time in the easiest way? My client has been stuck and it's not updating.
If you are using Windows, select the clock, change time date and settings, Internet time, Change settings, (select server) update now. Hey guys. About 2 hours ago now I started getting this error:
snip
snip
yes im stating this problem few weeks ago, the solution is i now mining other coin for the 270 card.
Haha I suppose that works, but until the DAG file gets bigger than 2GB I feel like it's worth trying to find a solution. I've only been at it a couple hours after all.
Okay not sure exactly what I did but I was playing around with the "setx" command and rebooted and now I have the following reg keys in
HKEY_USERS\S-1-5-21-xxxx...\Environment:
Code:
CL_DEVICE_MAX_MEM_ALLOC_SIZE 1800000000
GPU_MAX_MEM_ALLOC_SIZE 1800000000
Along with the other setx parameters I listed earlier. Not sure what, if anything, either of those 2 environment variables did, but anyway ethminer works again now, and when I check "ethminer --list-devices" I get the following output:
Code:
Listing OpenCL devices.
FORMAT: [deviceID] deviceName
[0] Hawaii
CL_DEVICE_TYPE: GPU
CL_DEVICE_GLOBAL_MEM_SIZE: 4294967296
CL_DEVICE_MAX_MEM_ALLOC_SIZE: 4025449564
CL_DEVICE_MAX_WORK_GROUP_SIZE: 256
[1] Pitcairn
CL_DEVICE_TYPE: GPU
CL_DEVICE_GLOBAL_MEM_SIZE: 2147483648
CL_DEVICE_MAX_MEM_ALLOC_SIZE: 1878490204
CL_DEVICE_MAX_WORK_GROUP_SIZE: 256
Not sure exactly what it was that changed the amount of allocated vram but anyway it works now in case anyone else was having the same problem maybe setting one of those 2 environment variables will help? Maybe someone has more insight on a more elegant solution?
Thanks Man, had the same issues on dual R9-270's, this did the trick! took a couple of restarts but hashing away!
It has been asked probably numerous times, but what's the easiest way to check my computer's time and where to check it. Also how do I sync the time in the easiest way? My client has been stuck and it's not updating.
Same thing happened to me few hours ago although I have 3GB GPU (280x). I deleted all my files in Ethash folder and restarted a miner - works normaly now.
That worked for me thanks
Hey guys. About 2 hours ago now I started getting this error:
I am mining on an r9 270 2GB using cpp-ethereum v1.2.2 for Windows on Windows 7 64-bit.
I did some digging and apparently it has something to do with the DAG being one single chunk that is too large for the GPUs memory. I also have an r9 290 with 4GB memory in my system and mining still works fine on that.
When i type "ethminer --list-devices" I get the following output:
I can see that the DAG file is now 1417674752 bytes so it would seem the DAG has just grown beyond the allocated memory. I have tried deleting and building a new DAG, uninstalling my drivers with display driver uninstaller and re-installing the crimson 15.12 drivers. Also I have tried setting all the following evironment variables, and rebooting, and setting them again:
as was suggested in this thread on github but it had no effect.
I suppose I can try the 16.x drivers (in fact I will do that next) but I used those before and they dropped my hash rate by 25 or 30%.
Is anyone else having this issue on 2GB AMD cards all of a sudden. Any foolproof way of allocating more mem?
Any help would be appreciated. Thanks.
Code:
Allocating/mapping single buffer failed with: clCreateBuffer(-61). GPU can't allocate the DAG in a single chunk. Bailing.
clEnqueueWriteBuffer(-38)
I am mining on an r9 270 2GB using cpp-ethereum v1.2.2 for Windows on Windows 7 64-bit.
I did some digging and apparently it has something to do with the DAG being one single chunk that is too large for the GPUs memory. I also have an r9 290 with 4GB memory in my system and mining still works fine on that.
When i type "ethminer --list-devices" I get the following output:
Code:
Listing OpenCL devices.
FORMAT: [deviceID] deviceName
[0] Hawaii
CL_DEVICE_TYPE: GPU
CL_DEVICE_GLOBAL_MEM_SIZE: 4294967296
CL_DEVICE_MAX_MEM_ALLOC_SIZE: 3019087173
CL_DEVICE_MAX_WORK_GROUP_SIZE: 256
[1] Pitcairn
CL_DEVICE_TYPE: GPU
CL_DEVICE_GLOBAL_MEM_SIZE: 2147483648
CL_DEVICE_MAX_MEM_ALLOC_SIZE: 1408867653
CL_DEVICE_MAX_WORK_GROUP_SIZE: 256
I can see that the DAG file is now 1417674752 bytes so it would seem the DAG has just grown beyond the allocated memory. I have tried deleting and building a new DAG, uninstalling my drivers with display driver uninstaller and re-installing the crimson 15.12 drivers. Also I have tried setting all the following evironment variables, and rebooting, and setting them again:
Code:
GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100
as was suggested in this thread on github but it had no effect.
I suppose I can try the 16.x drivers (in fact I will do that next) but I used those before and they dropped my hash rate by 25 or 30%.
Is anyone else having this issue on 2GB AMD cards all of a sudden. Any foolproof way of allocating more mem?
Any help would be appreciated. Thanks.
Same thing happened to me few hours ago although I have 3GB GPU (280x). I deleted all my files in Ethash folder and restarted a miner - works normaly now.
Hi,2 days to mine without problems but about 4 hours ago now I started getting this error:
Creating one big buffer for the DAG
Allocating/mapping single buffer failed with: clCreateBuffer(-61). GPU can't all
ocate the DAG in a single chunk. Bailing.
clEnqueueWriteBuffer(-38)
Creating buffer for header.
Creating mining buffer 0
Creating mining buffer 1
I have 2 ring with some error:
1--» 280x + 270x with 4 g ram
2--» 280x + 260x with 4 g ram
Need Help
Creating one big buffer for the DAG
Allocating/mapping single buffer failed with: clCreateBuffer(-61). GPU can't all
ocate the DAG in a single chunk. Bailing.
clEnqueueWriteBuffer(-38)
Creating buffer for header.
Creating mining buffer 0
Creating mining buffer 1
I have 2 ring with some error:
1--» 280x + 270x with 4 g ram
2--» 280x + 260x with 4 g ram
Need Help
Rootstock enters the autumn of 2016 also ethereum touches are painfully.In contrast, RSK Labs plans a launch of Rootstock in a private test network in late April and a public beta release in September. The ultimate goal is a 1.0 version of the block chain end of the year. The previously mentioned Funding will be used to realize these timelines.
Hey guys. About 2 hours ago now I started getting this error:
snip
snip
yes im stating this problem few weeks ago, the solution is i now mining other coin for the 270 card.
Haha I suppose that works, but until the DAG file gets bigger than 2GB I feel like it's worth trying to find a solution. I've only been at it a couple hours after all.
Okay not sure exactly what I did but I was playing around with the "setx" command and rebooted and now I have the following reg keys in
HKEY_USERS\S-1-5-21-xxxx...\Environment:
Code:
CL_DEVICE_MAX_MEM_ALLOC_SIZE 1800000000
GPU_MAX_MEM_ALLOC_SIZE 1800000000
Along with the other setx parameters I listed earlier. Not sure what, if anything, either of those 2 environment variables did, but anyway ethminer works again now, and when I check "ethminer --list-devices" I get the following output:
Code:
Listing OpenCL devices.
FORMAT: [deviceID] deviceName
[0] Hawaii
CL_DEVICE_TYPE: GPU
CL_DEVICE_GLOBAL_MEM_SIZE: 4294967296
CL_DEVICE_MAX_MEM_ALLOC_SIZE: 4025449564
CL_DEVICE_MAX_WORK_GROUP_SIZE: 256
[1] Pitcairn
CL_DEVICE_TYPE: GPU
CL_DEVICE_GLOBAL_MEM_SIZE: 2147483648
CL_DEVICE_MAX_MEM_ALLOC_SIZE: 1878490204
CL_DEVICE_MAX_WORK_GROUP_SIZE: 256
Not sure exactly what it was that changed the amount of allocated vram but anyway it works now in case anyone else was having the same problem maybe setting one of those 2 environment variables will help? Maybe someone has more insight on a more elegant solution?
Jump to: