Author

Topic: [ANN] Ethereum: Welcome to the Beginning - page 984. (Read 2006108 times)

legendary
Activity: 2702
Merit: 1030
Yes I am a pirate, 300 years too late!
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.
newbie
Activity: 18
Merit: 0
Hey guys. About 2 hours ago now I started getting this error:

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!
sr. member
Activity: 260
Merit: 250
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.
hero member
Activity: 868
Merit: 1000


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
legendary
Activity: 1274
Merit: 1006
Hey guys. About 2 hours ago now I started getting this error:

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.
hero member
Activity: 597
Merit: 500
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

sr. member
Activity: 364
Merit: 250
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.
sr. member
Activity: 430
Merit: 254
Hey guys. About 2 hours ago now I started getting this error:

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?
sr. member
Activity: 430
Merit: 254
Hey guys. About 2 hours ago now I started getting this error:

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.
legendary
Activity: 1456
Merit: 1000
Hey guys. About 2 hours ago now I started getting this error:

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.

yes im stating this problem few weeks ago, the solution is i now mining other coin for the 270 card.
sr. member
Activity: 430
Merit: 254
Hey guys. About 2 hours ago now I started getting this error:

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.
legendary
Activity: 2758
Merit: 1075
need more eth man......i needs it reaaaal bad...cant sleep...need eth now...eth...   Cheesy

17k btc worth ETH for sale till new ath,lol...time to nom nom nom  Grin

shoutout to the crew all ETHeads ....Ice Cube - Roll Call  Tongue
https://www.youtube.com/watch?v=q6zds_956No
full member
Activity: 228
Merit: 100
Sry for noob question but can someone tell me how to backup eth wallet

yes i wonder about this too, all i do was copying the wallet.key to flash disk and print it on paper. i wonder if there is easier and safer way

Where can I find wallet.key? There is no "wallet.key" file. Sry for been so unfamiliar with eth wallet

in linux, its in ".ethereum/keystore/"  folder, i guess in windows you can search for the folder name which is keystore, then copy the whole folder.

EDIT :  https://github.com/ethereum/go-ethereum/wiki/Backup-&-restore

Thanks man  Smiley
sr. member
Activity: 407
Merit: 254
Sry for noob question but can someone tell me how to backup eth wallet

yes i wonder about this too, all i do was copying the wallet.key to flash disk and print it on paper. i wonder if there is easier and safer way

Where can I find wallet.key? There is no "wallet.key" file. Sry for been so unfamiliar with eth wallet

in linux, its in ".ethereum/keystore/"  folder, i guess in windows you can search for the folder name which is keystore, then copy the whole folder.

EDIT :  https://github.com/ethereum/go-ethereum/wiki/Backup-&-restore
And there is a backup button on the mist wallet.
sr. member
Activity: 364
Merit: 250
I love Python ,glad you didn't pick up any other language.
legendary
Activity: 1456
Merit: 1000
Sry for noob question but can someone tell me how to backup eth wallet

yes i wonder about this too, all i do was copying the wallet.key to flash disk and print it on paper. i wonder if there is easier and safer way

Where can I find wallet.key? There is no "wallet.key" file. Sry for been so unfamiliar with eth wallet

in linux, its in ".ethereum/keystore/"  folder, i guess in windows you can search for the folder name which is keystore, then copy the whole folder.

EDIT :  https://github.com/ethereum/go-ethereum/wiki/Backup-&-restore
full member
Activity: 228
Merit: 100
Sry for noob question but can someone tell me how to backup eth wallet

yes i wonder about this too, all i do was copying the wallet.key to flash disk and print it on paper. i wonder if there is easier and safer way

Where can I find wallet.key? There is no "wallet.key" file. Sry for been so unfamiliar with eth wallet
legendary
Activity: 1456
Merit: 1000
Sry for noob question but can someone tell me how to backup eth wallet

yes i wonder about this too, all i do was copying the wallet.key to flash disk and print it on paper. i wonder if there is easier and safer way
full member
Activity: 228
Merit: 100
Sry for noob question but can someone tell me how to backup eth wallet
member
Activity: 94
Merit: 10
It looks like my wallet doesn`t want to download blocks. When I started i`m looking at this for 15mins +

https://gyazo.com/82df337190d49b66500e62da6fbe4a6b

Any ideas?

Your wallet stopped downloading right around the start of homestead and the graphics look older; make sure you're using the latest wallet, which is 0.5.2.

Yea I downloaded the 0.5.2. and I opened one time and everything was fine.

But now day later when i open wallet is stucked on 1,187,687 block...

Any thoughts?
The time on your PC has to be accurate, so double check that you're in sync with a universal time clock. Although the wallet usually gives an error if that is the issue.

It is syncronized. I guess you are talking about the munites right? My minutes and seconds are exactly like this one here: http://www.timeanddate.com/worldclock/timezone/utc 
I started today but it`s stucked again Sad
Jump to: