Memory limit parameter not working ?

Encounter a problem related to the pool or have a request for a feature? Post your issue here and we will help you out.
Forum rules
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.

Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.

We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Locked
nicodemus
Posts: 7
Joined: Sat Feb 13, 2021 8:15 pm

Memory limit parameter not working ?

Post by nicodemus » Sat Feb 13, 2021 8:22 pm

Hello,

I've been mining Ethash with 4GB GPUs with proswitching enabled, as it was balancing between Nekonium and Expanse. Today proswitching started sending work for Ethereum, so I added the "l" parameter in the ethminer command so that proswitching would skip Ethereum on my rig, but it appears to be ignored.

I've fixed the coins with the "c" parameter, is someone else experiencing such an issue? I tried with "l=4" and "l=3" to no avail. My password looked like the following:

Code: Select all

a=ethash,n=570,o=armor,l=3
Thanks a lot!

Cheers
Top
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Memory limit parameter not working ?

Post by Steve Sokolowski » Sun Feb 14, 2021 3:52 pm

I'll take a look at this issue and get back to you before tomorrow morning. You might have discovered a mining server bug. Thanks for the report!
Top
Nosferatu272
Posts: 5
Joined: Mon Feb 15, 2021 12:19 pm

Re: Memory limit parameter not working ?

Post by Nosferatu272 » Mon Feb 15, 2021 12:23 pm

Bumping, this parameter doesn't work for me either :/
Top
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Memory limit parameter not working ?

Post by Steve Sokolowski » Mon Feb 15, 2021 4:02 pm

I wanted to post that Vance is working on this issue, but so far he has not been able to reproduce the problem. He found another unrelated issue, which he will work on and hopefully he'll come to a resolution for this issue at the same time.

Hopefully we'll have more information by tomorrow. In the meantime, you can select a static coin to mine using "c=" if you're affected by this issue.
Top
nicodemus
Posts: 7
Joined: Sat Feb 13, 2021 8:15 pm

Re: Memory limit parameter not working ?

Post by nicodemus » Tue Feb 16, 2021 6:40 pm

Hello Steve,

First of all thanks for your reply. For now I've worked around this issue by fixing the coint with the "c=" parameter. However, once per day my workers stop due to authorization error (as if the fixed coin was disabled for a period of time).
I'm able and willing to provide any troubleshooting information you require, just let me know.

Cheers
Top
cryptomined
Posts: 19
Joined: Fri Feb 05, 2021 11:13 am

Re: Memory limit parameter not working ?

Post by cryptomined » Thu Feb 18, 2021 2:31 pm

I have set my parameter to l=8 because all my cards are 8GB, and I'm still hashing Expanse as if I was not on proswitching. I also set the difficulty to h=1 and it seems to ignore this and can go all the way down to 0.25
------------------------------------------------------
The Crypto Mined
https://cryptomined.net
https://www.youtube.com/channel/UCMHCRY ... 5OAtekY7g
-------------------------------------------------------
Top
nicodemus
Posts: 7
Joined: Sat Feb 13, 2021 8:15 pm

Re: Memory limit parameter not working ?

Post by nicodemus » Wed Feb 24, 2021 8:18 pm

Hello Steve,

Are there any news about this issue? Fixing the coin results in periodic disconnects...

Thanks a lot, kind regards.

Cheers
Top
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Memory limit parameter not working ?

Post by Steve Sokolowski » Thu Feb 25, 2021 7:29 am

nicodemus wrote: ↑Wed Feb 24, 2021 8:18 pm Hello Steve,

Are there any news about this issue? Fixing the coin results in periodic disconnects...

Thanks a lot, kind regards.

Cheers
This issue was resolved. The changes were released on February 23, as indicated in the posts in the "News" section.
Top
nicodemus
Posts: 7
Joined: Sat Feb 13, 2021 8:15 pm

Re: Memory limit parameter not working ?

Post by nicodemus » Thu Feb 25, 2021 8:47 am

Thanks a lot! Guess I'll start paying attention to the news section from now on :)

Cheers
Top
nicodemus
Posts: 7
Joined: Sat Feb 13, 2021 8:15 pm

Re: Memory limit parameter not working ?

Post by nicodemus » Thu Feb 25, 2021 9:39 am

Steve,

I hate to be a nuisance, but in my rig the parameter seems to be ignored still. I'm currently using ethminer v0.17.1, and if I execute it without the "l" parameter I get the following output:

Code: Select all

ethminer -G --opencl-devices 1 -P stratum+tcp://nicodemus:a=ethash,n=560,o=armor@prohashing.com:3339
 m 11:34:39 ethminer ethminer 0.17.1
 m 11:34:39 ethminer Build: linux/release
 i 11:34:39 ethminer OpenCL device Ellesmere has insufficient GPU memory.17,469 MB GB of memory found < 1.023,998 MB of memory required
 i 11:34:39 ethminer Found suitable OpenCL device [Baffin] with 3,942 GB of GPU memory
 i 11:34:39 ethminer Configured pool prohashing.com:3339
 i 11:34:39 main     Selected pool prohashing.com:3339
 i 11:34:39 stratum  Stratum mode detected: STRATUM
 i 11:34:39 stratum  Subscribed!
 i 11:34:39 stratum  Job: #58f5d4a7…  [50.220.121.209:3339]
 i 11:34:39 stratum  Pool difficulty: 2.15K megahash
 i 11:34:39 stratum  New epoch 397
 i 11:34:40 stratum  Authorized worker nicodemus
 i 11:34:40 stratum  Established connection with prohashing.com:3339 at  [50.220.121.209:3339]
 i 11:34:40 stratum  Spinning up miners...
cl 11:34:40 cl-0     No work. Pause for 3 s.
 i 11:34:40 stratum  Job: #58f5d4a7… prohashing.com [50.220.121.209:3339]
 i 11:34:41 stratum  Job: #26fc79d4… prohashing.com [50.220.121.209:3339]
cl 11:34:43 cl-0     Platform: AMD Accelerated Parallel Processing
cl 11:34:43 cl-0     Device:   Baffin / OpenCL 1.2 AMD-APP (3110.6)
 i 11:34:43 cl-0     Adjusting CL work multiplier for 16 CUs.Adjusted work multiplier: 29.128
 m 11:34:44 ethminer Speed 0.00 Mh/s gpu0 0.00 A0 Time: 00:00
 i 11:34:44 stratum  Job: #c0b0cc85… prohashing.com [50.220.121.209:3339]
cl 11:34:46 cl-0     OpenCL kernel
 i 11:34:47 stratum  Job: #24321220… prohashing.com [50.220.121.209:3339]
cl 11:34:48 cl-0     Loading binary kernel /usr/local/bin/kernels/ethash_baffin_lws192.bin
cl 11:34:48 cl-0     Build info success:
 i 11:34:48 cl-0     OpenCL device baffin has insufficient GPU memory.3,942 GB of memory found, 4,102 GB of memory required
Segmentation fault (core dumped)
If I try with either "l=4", "l=3" or even "l=2", I get the following output:

Code: Select all

ethminer -G --opencl-devices 1 -P stratum+tcp://nicodemus:a=ethash,n=560,o=armor,l=3@prohashing.com:3339
 m 11:33:59 ethminer ethminer 0.17.1
 m 11:33:59 ethminer Build: linux/release
 i 11:33:59 ethminer OpenCL device Ellesmere has insufficient GPU memory.11,402 MB GB of memory found < 1.023,998 MB of memory required
 i 11:33:59 ethminer Found suitable OpenCL device [Baffin] with 3,942 GB of GPU memory
 i 11:33:59 ethminer Configured pool prohashing.com:3339
 i 11:33:59 main     Selected pool prohashing.com:3339
 i 11:33:59 stratum  Stratum mode detected: STRATUM
 i 11:33:59 stratum  Subscribed!
 i 11:33:59 stratum  Job: #30835962…  [50.220.121.209:3339]
 i 11:33:59 stratum  Pool difficulty: 2.15K megahash
 i 11:33:59 stratum  New epoch 397
 i 11:34:00 stratum  Authorized worker nicodemus
 i 11:34:00 stratum  Established connection with prohashing.com:3339 at  [50.220.121.209:3339]
 i 11:34:00 stratum  Spinning up miners...
cl 11:34:00 cl-0     No work. Pause for 3 s.
 i 11:34:00 stratum  Connection remotely closed by prohashing.com
 i 11:34:00 main     Disconnected from prohashing.com [50.220.121.209:3339]
 i 11:34:00 main     Suspend mining due connection change...
 i 11:34:00 main     Selected pool prohashing.com:3339
 i 11:34:00 stratum  Stratum mode detected: STRATUM
 i 11:34:00 stratum  Subscribed!
 i 11:34:00 stratum  Job: #30835962… prohashing.com [50.220.121.209:3339]
 i 11:34:01 stratum  Authorized worker nicodemus
 i 11:34:01 stratum  Established connection with prohashing.com:3339 at  [50.220.121.209:3339]
 i 11:34:01 stratum  Connection remotely closed by prohashing.com
 i 11:34:01 main     Disconnected from prohashing.com [50.220.121.209:3339]
 i 11:34:01 main     Suspend mining due connection change...
 i 11:34:01 main     Selected pool prohashing.com:3339
 i 11:34:01 stratum  Stratum mode detected: STRATUM
 i 11:34:01 stratum  Subscribed!
 i 11:34:01 stratum  Job: #30835962… prohashing.com [50.220.121.209:3339]
 i 11:34:02 stratum  Job: #87a646aa… prohashing.com [50.220.121.209:3339]
 i 11:34:02 stratum  Authorized worker nicodemus
 i 11:34:02 stratum  Established connection with prohashing.com:3339 at  [50.220.121.209:3339]
 i 11:34:02 stratum  Connection remotely closed by prohashing.com
 i 11:34:02 main     Disconnected from prohashing.com [50.220.121.209:3339]
 i 11:34:02 main     Suspend mining due connection change...
 i 11:34:02 main     Selected pool prohashing.com:3339
 i 11:34:02 stratum  Stratum mode detected: STRATUM
 i 11:34:02 stratum  Subscribed!
 i 11:34:02 stratum  Job: #fcce58e4… prohashing.com [50.220.121.209:3339]
 i 11:34:03 stratum  Authorized worker nicodemus
 i 11:34:03 stratum  Established connection with prohashing.com:3339 at  [50.220.121.209:3339]
 i 11:34:03 stratum  Connection remotely closed by prohashing.com
 i 11:34:03 main     Disconnected from prohashing.com [50.220.121.209:3339]
cl 11:34:03 cl-0     Platform: AMD Accelerated Parallel Processing
cl 11:34:03 cl-0     Device:   Baffin / OpenCL 1.2 AMD-APP (3110.6)
 i 11:34:03 cl-0     Adjusting CL work multiplier for 16 CUs.Adjusted work multiplier: 29.128
 i 11:34:03 main     Suspend mining due connection change...
 i 11:34:03 main     Selected pool prohashing.com:3339
 i 11:34:03 stratum  Stratum mode detected: STRATUM
 i 11:34:03 stratum  Subscribed!
 i 11:34:03 stratum  Job: #fcce58e4… prohashing.com [50.220.121.209:3339]
 i 11:34:04 stratum  Authorized worker nicodemus
 i 11:34:04 stratum  Established connection with prohashing.com:3339 at  [50.220.121.209:3339]
 i 11:34:04 stratum  Connection remotely closed by prohashing.com
 i 11:34:04 main     Disconnected from prohashing.com [50.220.121.209:3339]
 m 11:34:04 ethminer not-connected
 i 11:34:04 main     Suspend mining due connection change...
 i 11:34:04 main     Selected pool prohashing.com:3339
 i 11:34:04 stratum  Stratum mode detected: STRATUM
 i 11:34:04 stratum  Subscribed!
 i 11:34:04 stratum  Job: #fcce58e4… prohashing.com [50.220.121.209:3339]
 i 11:34:05 stratum  Authorized worker nicodemus
 i 11:34:05 stratum  Established connection with prohashing.com:3339 at  [50.220.121.209:3339]
 i 11:34:05 stratum  Connection remotely closed by prohashing.com
 i 11:34:05 main     Disconnected from prohashing.com [50.220.121.209:3339]
 i 11:34:05 main     Suspend mining due connection change...
 i 11:34:05 main     Selected pool prohashing.com:3339
 i 11:34:05 stratum  Stratum mode detected: STRATUM
 i 11:34:05 stratum  Subscribed!
 i 11:34:05 stratum  Job: #c220f7a8… prohashing.com [50.220.121.209:3339]
 i 11:34:06 stratum  Authorized worker nicodemus
 i 11:34:06 stratum  Established connection with prohashing.com:3339 at  [50.220.121.209:3339]
 i 11:34:06 stratum  Connection remotely closed by prohashing.com
 i 11:34:06 main     Disconnected from prohashing.com [50.220.121.209:3339]
 i 11:34:06 main     Suspend mining due connection change...
 i 11:34:06 main     Selected pool prohashing.com:3339
 i 11:34:06 stratum  Stratum mode detected: STRATUM
 i 11:34:06 stratum  Subscribed!
 i 11:34:06 stratum  Job: #c220f7a8… prohashing.com [50.220.121.209:3339]
cl 11:34:07 cl-0     OpenCL kernel
 i 11:34:07 stratum  Authorized worker nicodemus
 i 11:34:07 stratum  Established connection with prohashing.com:3339 at  [50.220.121.209:3339]
 i 11:34:07 stratum  Connection remotely closed by prohashing.com
 i 11:34:07 main     Disconnected from prohashing.com [50.220.121.209:3339]
 i 11:34:07 main     Suspend mining due connection change...
 i 11:34:07 main     Selected pool prohashing.com:3339
 i 11:34:07 stratum  Stratum mode detected: STRATUM
 i 11:34:07 stratum  Subscribed!
 i 11:34:07 stratum  Job: #c220f7a8… prohashing.com [50.220.121.209:3339]
 i 11:34:08 stratum  Authorized worker nicodemus
 i 11:34:08 stratum  Established connection with prohashing.com:3339 at  [50.220.121.209:3339]
 i 11:34:08 stratum  Connection remotely closed by prohashing.com
 i 11:34:08 main     Disconnected from prohashing.com [50.220.121.209:3339]
 i 11:34:08 main     Suspend mining due connection change...
 i 11:34:08 main     Selected pool prohashing.com:3339
 i 11:34:08 stratum  Stratum mode detected: STRATUM
 i 11:34:08 stratum  Subscribed!
 i 11:34:08 stratum  Job: #5f61f83c… prohashing.com [50.220.121.209:3339]
 i 11:34:09 stratum  Job: #547fd472… prohashing.com [50.220.121.209:3339]
cl 11:34:09 cl-0     Loading binary kernel /usr/local/bin/kernels/ethash_baffin_lws192.bin
cl 11:34:09 cl-0     Build info success:
 i 11:34:09 cl-0     OpenCL device baffin has insufficient GPU memory.3,942 GB of memory found, 4,102 GB of memory required
Segmentation fault (core dumped)
Needless to say, fixing the coin allows me to mine nekoniums. Am I missing something?

Cheers
Top
Locked

Return to “System support”