 Show Posts
|
|
Pages: [1] 2 3 4 »
|
RX550 2GB ethereum Mining Hash Rate?
DAG too large already for 2GB |
|
|
|
I wanted to push 1.6.2 today but it looks like it will be postponed, i have to check what has changed from 1.6.0 to 1.6.1 that could produce that crash. The problem is i can't reproduce that on any of my rigs, and i have win7, win8 and win10 rigs  I can help troubleshoot it on my rig if you come up with some kind of debugger to figure out the error. |
|
|
|
Is this occuring on v7 or heavy algo?
For me v7 and heavy worked ok, haven and stellite crashed. Didn't test others. |
|
|
|
Still same situation unfortunately
start with --adldisable with series R9 2xx,3xx it helps Thanks for the suggestion, unfortunately no improvement. sorry i have no idea, i tried on win7 and win10 machines and it's working ok. Ok no worries, only seems to happen with Stellite algo for now, I will try to investigate more during the weekend. Tried some more algos and seems to be the same issue for Haven also. The miner crashes when starting to send result back to pool. Also tried my r9 290s and r9 380s separately and they both crash with these algos. No problems with regular v7 or heavy. Can anyone with these cards try if their miner also crashes when mining stellite or haven? |
|
|
|
Does it work well on R9 290?
No tested on R290 only on r390. We will be thankful if you send your results I tested it on R9 290 and 290X, seem to work fine on regular v7. Are you planning to improve this software somehow or is this the final release? |
|
|
|
Still same situation unfortunately
start with --adldisable with series R9 2xx,3xx it helps Thanks for the suggestion, unfortunately no improvement. sorry i have no idea, i tried on win7 and win10 machines and it's working ok. Ok no worries, only seems to happen with Stellite algo for now, I will try to investigate more during the weekend. |
|
|
|
I tested the miner, v7 works ok but Stellite is only giving incorrect shares:
Device: #2 worker #0 share diff: 1.29969, needed: 50000.2
Anyone else having this problem when mining Stellite?
you probably have different algos in one config file, this dont work on current version. you need seperate config for each algo Thanks for the reply, but I had only Stellite algo in the config file, removed every other algo from there. |
|
|
|
Still same situation unfortunately
start with --adldisable with series R9 2xx,3xx it helps Thanks for the suggestion, unfortunately no improvement. |
|
|
|
Try this, if you have in start.bat:
setx GPU_FORCE_64BIT_PTR 1
change to :
setx GPU_FORCE_64BIT_PTR 0
Still same situation unfortunately Any more ideas what to try, doc? |
|
|
|
how often do you guys see Compute Error? i'm tuning OC and wonder how many Compute Errors are acceptable.
I never see any compute error. None is acceptable, compute error means you have a lot of memory errors, you may have random crashes &/or software malfunction. Over the course of 4 days, I get 19 errors for one card and 7 for the other. Tried turning up memory voltage and turning down memory clock. Doesn't seem to help a lot. That's just a few errrors, these shouldn't have any noticeable effect on hashrate. You could also try lowering the intensity if the errors are bothering you. |
|
|
|
Try this, if you have in start.bat:
setx GPU_FORCE_64BIT_PTR 1
change to :
setx GPU_FORCE_64BIT_PTR 0
Still same situation unfortunately |
|
|
|
Here is the log: [2018-06-26 23:43:06] Miner version: 1.6.1
[2018-06-26 23:43:07] AMD Platform ID: 0
[2018-06-26 23:43:07] AMD platform FOUND
[2018-06-26 23:43:07] Found 7 AMD devices
[2018-06-26 23:43:07] GPU0: AMD Radeon R9 200 Series [Hawaii] [4096 MB][Intensity 40.0][W: 8][T: 2][K: 1][BUS: 11]
[2018-06-26 23:43:07] GPU1: AMD Radeon (TM) R9 380 Series [Tonga] [4096 MB][Intensity 37.0][W: 8][T: 2][K: 1][BUS: 7]
[2018-06-26 23:43:07] GPU2: AMD Radeon (TM) R9 380 Series [Tonga] [4096 MB][Intensity 37.0][W: 8][T: 2][K: 1][BUS: 9]
[2018-06-26 23:43:07] GPU3: AMD Radeon (TM) R9 380 Series [Tonga] [4096 MB][Intensity 37.1][W: 8][T: 2][K: 1][BUS: 3]
[2018-06-26 23:43:07] GPU4: AMD Radeon (TM) R9 380 Series [Tonga] [4096 MB][Intensity 36.2][W: 8][T: 2][K: 1][BUS: 5]
[2018-06-26 23:43:07] GPU5: AMD Radeon (TM) R9 380 Series [Tonga] [4096 MB][Intensity 37.1][W: 8][T: 2][K: 1][BUS: 8]
[2018-06-26 23:43:07] GPU6: AMD Radeon R9 200 Series [Hawaii] [4096 MB][Intensity 39.8][W: 8][T: 2][K: 1][BUS: 10]
[2018-06-26 23:43:07] ADL is enabled
[2018-06-26 23:43:07] Cryptonight StelliteV4 mode enabled
[2018-06-26 23:43:07] DevFee pools loaded
[2018-06-26 23:43:07] DevFee pool SET
[2018-06-26 23:43:07] DevFee address SET
[2018-06-26 23:43:07] Starting init of mining threads
[2018-06-26 23:43:07] Loading kernel for DEVICE BUS ID 11 ...
[2018-06-26 23:43:08] Loading kernel for DEVICE BUS ID 11 ...
[2018-06-26 23:43:10] Loading kernel for DEVICE BUS ID 7 ...
[2018-06-26 23:43:11] Loading kernel for DEVICE BUS ID 7 ...
[2018-06-26 23:43:12] Loading kernel for DEVICE BUS ID 9 ...
[2018-06-26 23:43:13] Loading kernel for DEVICE BUS ID 9 ...
[2018-06-26 23:43:15] Loading kernel for DEVICE BUS ID 3 ...
[2018-06-26 23:43:16] Loading kernel for DEVICE BUS ID 3 ...
[2018-06-26 23:43:17] Loading kernel for DEVICE BUS ID 5 ...
[2018-06-26 23:43:18] Loading kernel for DEVICE BUS ID 5 ...
[2018-06-26 23:43:20] Loading kernel for DEVICE BUS ID 8 ...
[2018-06-26 23:43:21] Loading kernel for DEVICE BUS ID 8 ...
[2018-06-26 23:43:22] Loading kernel for DEVICE BUS ID 10 ...
[2018-06-26 23:43:23] Loading kernel for DEVICE BUS ID 10 ...
[2018-06-26 23:43:24] ADL initialised successfully!
[2018-06-26 23:43:24] Finished init of mining threads
[2018-06-26 23:43:24] Main pool: eu.XTL.CryptoPool.Space:7777
[2018-06-26 23:43:24] Gpu watchdog started
[2018-06-26 23:43:24] API disabled
[2018-06-26 23:43:24] json_send: {"method":"login","params":{"login":"Se2tnbEfRhqHqoYa4fym8QUAxuioM63Qha9dyYEzWS89i4W15WqBWqV72UrhEUzjkS6d3zLopAF2NWZ FVms8ubbH38a2ptr25","pass":"380x","agent":"SRBMiner Cryptonight AMD GPU miner/1.6.1","rigid":""},"id":1}
[2018-06-26 23:43:24] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"9fbe4dcb-2810-4cb2-a360-51805b6e21dd","job":{"blob":"04049bc6cad905a897baacc61f3e57fa121e758c83ffb337ca92eda4adc95224d7ea0fa28e68ec0 00000000d8ca099f0b4bd4fbf8815a387f37014638a80665c0c23d250bf013bf78e284302","algo":"cryptonight/xtl","variant":"xtl","job_id":"DJNMYtWIlt8Mtlq1Aq/Rac2pa6F/","target":"c5a70000","id":"9fbe4dcb-2810-4cb2-a360-51805b6e21dd"},"status":"OK"}}
[2018-06-26 23:43:24] Connected to eu.XTL.CryptoPool.Space:7777
[2018-06-26 23:43:24] sock_ready: User logged in
[2018-06-26 23:43:24] pool_have_job: Pool sent a new job (ID: DJNMYtWIlt8Mtlq1Aq/Rac2pa6F/)
Error message: https://files.fm/f/72r55u6f |
|
|
|
I tried to mine Stellite with the 1.6.1 but the miner crashes after 1 or 2 jobs sent from the pool. Any idea what can cause this?
Also sometimes with regular v7 my rig stops sending shares, I won't get any errors and new jobs keep coming from pool but no result are sent back and it can go on for hours.
just fixed this issue with jobs received but no results, some pools send blob 77 bytes instead of 76, it will be fixed in the next version in a few days. One of these pools is etn.spacepools.org, please send me other pools with this same problem so i can test/verify the fix. Regarding stellite, give me the pool and port so i can try. Ah yes, it was etn.spacepools.org which I had issues with. Regarding Stellite I used eu.XTL.CryptoPool.Space:7777 ok i am mining 5 minutes on eu.XTL.CryptoPool.Space:7777 got 7 new jobs, but no crash, everything fine. Does it crash for you every time? Yes, it crashes every time. Do you have any idea how to troubleshoot this issue? |
|
|
|
I tried to mine Stellite with the 1.6.1 but the miner crashes after 1 or 2 jobs sent from the pool. Any idea what can cause this?
Also sometimes with regular v7 my rig stops sending shares, I won't get any errors and new jobs keep coming from pool but no result are sent back and it can go on for hours.
just fixed this issue with jobs received but no results, some pools send blob 77 bytes instead of 76, it will be fixed in the next version in a few days. One of these pools is etn.spacepools.org, please send me other pools with this same problem so i can test/verify the fix. Regarding stellite, give me the pool and port so i can try. Ah yes, it was etn.spacepools.org which I had issues with. Regarding Stellite I used eu.XTL.CryptoPool.Space:7777 |
|
|
|
|
I tried to mine Stellite with the 1.6.1 but the miner crashes after 1 or 2 jobs sent from the pool. Any idea what can cause this?
Also sometimes with regular v7 my rig stops sending shares, I won't get any errors and new jobs keep coming from pool but no result are sent back and it can go on for hours.
|
|
|
|
|
I tested the miner, v7 works ok but Stellite is only giving incorrect shares:
Device: #2 worker #0 share diff: 1.29969, needed: 50000.2
Anyone else having this problem when mining Stellite?
|
|
|
|
|
Why have you still not decided the fork block if you are determined to change the algo this week already? This seems a bit rushed and not well communicated to miners.
|
|
|
|
I have now mined 340 ETN with this mobile miner from the beginning. Now need to find a real use for them...
Do you get more ETN when you log into 2 phones with your account and mine with both of them?
You can not login in two phones with same login credentials. Definitely can, I tried it and started mining on both of them, no issues there. But I was wondering if you also get more ETN this way? |
|
|
|
Hi, I tried out your miner and I like it.
Do you only plan to support timing mod for RX series?
What about older R9 series, no support planned for those?
I am getting a used 290X just for that purpose. Stay tuned! Nice, good to hear. I just got a couple and struggle to find good timings for them. Over 1375 the hashrate drops rapidly for some reason. |
|
|
|
|
I have now mined 340 ETN with this mobile miner from the beginning. Now need to find a real use for them...
Do you get more ETN when you log into 2 phones with your account and mine with both of them?
|
|
|
|
|
