johnambush
|
|
March 22, 2016, 03:19:21 PM |
|
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
|
|
|
|
noobtrader
Legendary
Offline
Activity: 1456
Merit: 1000
|
|
March 22, 2016, 03:48:29 PM |
|
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
|
"...I suspect we need a better incentive for users to run nodes instead of relying solely on altruism...", satoshi@vistomail.com
|
|
|
mangox
|
|
March 22, 2016, 04:49:58 PM |
|
I love Python ,glad you didn't pick up any other language.
|
|
|
|
almond
|
|
March 22, 2016, 05:15:53 PM |
|
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-&-restoreAnd there is a backup button on the mist wallet.
|
Freedom of the press is guaranteed only to those who own one
|
|
|
johnambush
|
|
March 22, 2016, 05:41:14 PM |
|
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-&-restoreThanks man
|
|
|
|
Mrpumperitis
Legendary
Offline
Activity: 2800
Merit: 1075
|
|
March 23, 2016, 02:25:02 AM Last edit: March 23, 2016, 02:40:02 AM by Mrpumperitis |
|
need more eth man......i needs it reaaaal bad...cant sleep...need eth now...eth... 17k btc worth ETH for sale till new ath,lol...time to nom nom nom shoutout to the crew all ETHeads ....Ice Cube - Roll Call https://www.youtube.com/watch?v=q6zds_956No
|
Bitcoin - Blockchain 1.0 (2009) Ethereum - Blockchain 2.0 (2015) Partisia - Blockchain 3.0 (2021)
|
|
|
bardacuda
|
|
March 23, 2016, 04:17:08 AM |
|
Hey guys. About 2 hours ago now I started getting this error: 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: 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: 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.
|
The future will rely on AI. SingularityNET lets anyone create, monetize, and use AI at scale. From the creators of Sophia the Robot.
|
|
|
noobtrader
Legendary
Offline
Activity: 1456
Merit: 1000
|
|
March 23, 2016, 04:25:45 AM |
|
Hey guys. About 2 hours ago now I started getting this error: 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: 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: 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.
|
"...I suspect we need a better incentive for users to run nodes instead of relying solely on altruism...", satoshi@vistomail.com
|
|
|
bardacuda
|
|
March 23, 2016, 04:52:49 AM |
|
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.
|
The future will rely on AI. SingularityNET lets anyone create, monetize, and use AI at scale. From the creators of Sophia the Robot.
|
|
|
bardacuda
|
|
March 23, 2016, 05:22:23 AM |
|
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: 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: 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?
|
The future will rely on AI. SingularityNET lets anyone create, monetize, and use AI at scale. From the creators of Sophia the Robot.
|
|
|
mangox
|
|
March 23, 2016, 07:57:14 AM |
|
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.
|
|
|
|
Toninho
|
|
March 23, 2016, 08:27:44 AM |
|
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
|
|
|
|
z0n0
Legendary
Offline
Activity: 1274
Merit: 1006
|
|
March 23, 2016, 09:17:09 AM |
|
Hey guys. About 2 hours ago now I started getting this error: 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: 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: 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.
|
|
|
|
alienesb
|
|
March 23, 2016, 09:59:40 AM |
|
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
|
|
|
|
zmhaha
|
|
March 23, 2016, 01:01:34 PM |
|
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.
|
|
|
|
jed78
Newbie
Offline
Activity: 18
Merit: 0
|
|
March 23, 2016, 01:06:02 PM |
|
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: 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: 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!
|
|
|
|
madmartyk
Legendary
Offline
Activity: 2702
Merit: 1030
Yes I am a pirate, 300 years too late!
|
|
March 23, 2016, 01:07:34 PM |
|
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.
|
|
|
|
zmhaha
|
|
March 23, 2016, 01:10:28 PM |
|
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?
|
|
|
|
madmartyk
Legendary
Offline
Activity: 2702
Merit: 1030
Yes I am a pirate, 300 years too late!
|
|
March 23, 2016, 01:17:05 PM |
|
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
|
|
|
|
malekbaba
Legendary
Offline
Activity: 1526
Merit: 1026
SellDefi.com | Earn by selling files
|
|
March 23, 2016, 01:23:39 PM |
|
Anyone here suffering from DAG allocation problem with 3gb cards?!
|
|
|
|
|