CryptoDredge 0.27.0 — CUDA Miner - page 45.

superlative1974

newbie

Activity: 45

Merit: 0

Quote from: cryptodredge on August 05, 2018, 01:43:49 PM

Quote from: jebidia on August 05, 2018, 01:38:54 PM

CD .6 and up are no longer working on PHI2 after fork...please advise

Cryptodredge has problems with Lux's smart contracts.

We'll try to fix it as soon as possible. Sorry for the inconvenience!

Hello, PHI2 works great.
question. you can make under the algoritm HEX, it's possible, you would be the first))))

Vispilio

legendary

Activity: 2128

Merit: 1656

Some users reported hashrate drops for upper end cards like 1080 TI on 0.8.2, should we wait for future releases for improvements on 1080 TI ?..

Also what Overclock settings would you recommend for 1080 TI when mining Lyra2Rev2 ?..

All the Best

darkneorus

jr. member

Activity: 238

Merit: 3

Quote from: elkiki1 on August 06, 2018, 06:34:04 AM

using windows version here mixed with some autoswitch software that fail to read api response since 8.2, had no problem with version 8.0 or 7

same here. Windows + Awesome Miner.

elkiki1

newbie

Activity: 11

Merit: 0

using windows version here mixed with some autoswitch software that fail to read api response since 8.2, had no problem with version 8.0 or 7

cryptodredge

member

Activity: 157

Merit: 19

Quote from: sidog on August 05, 2018, 08:06:31 PM

the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?

Quote from: Burnie on August 05, 2018, 09:53:14 PM

Does CryptoDredge close the sockets properly before exiting?
I see a lot of TIME_WAITs when CryptoDredge is running, and they slowly disappear when CryptoDredge is stopped.
If CryptoDredge is started after 3-4 minutes, the api seems to start ok.

Quote from: darkneorus on August 05, 2018, 10:06:51 PM

yup, often the miner tries to use the default API bind address and port (127.0.0.1:4068) instead of using the address from its command line arguments.

Quote from: pgj69 on August 06, 2018, 12:20:09 AM

With 0.8.2 the API server is not always started as set by the command line.

Quote from: terryborg on August 06, 2018, 02:13:34 AM

Please help to fix API issue ASAP. without it , could not use the miner on awesome miner.
thanks

Quote from: elkiki1 on August 06, 2018, 05:25:05 AM

+1 on API fix, good miner but unusable by most of us in actual state!

Quote from: BartVanseer on August 06, 2018, 04:48:58 AM

It still mines correctly but you cannot see what you are making and awesome miner will restart the miner because the accepted share does not increase.. need a fix quickly

This bug has already been fixed, update will be delivered soon. What OS do you use?

elkiki1

newbie

Activity: 11

Merit: 0

+1 on API fix, good miner but unusable by most of us in actual state!

BartVanseer

newbie

Activity: 112

Merit: 0

Quote from: terryborg on August 06, 2018, 02:13:34 AM

Quote from: cryptodredge on August 05, 2018, 09:01:34 PM

Quote from: sidog on August 05, 2018, 08:06:31 PM

the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?

Yep, that is a known issue. The API often does not start since version 0.8.0. You might try to use 0.7.0 (Windows version is CUDA 9.2 only) Apologize!

Please help to fix API issue ASAP. without it , could not use the miner on awesome miner.

thanks

It still mines correctly but you cannot see what you are making and awesome miner will restart the miner because the accepted share does not increase.. need a fix quickly

terryborg

newbie

Activity: 18

Merit: 0

Quote from: cryptodredge on August 05, 2018, 09:01:34 PM

Quote from: sidog on August 05, 2018, 08:06:31 PM

the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?

Yep, that is a known issue. The API often does not start since version 0.8.0. You might try to use 0.7.0 (Windows version is CUDA 9.2 only) Apologize!

Please help to fix API issue ASAP. without it , could not use the miner on awesome miner.

thanks

pgj69

newbie

Activity: 3

Merit: 0

With 0.8.2 the API server is not always started as set by the command line.

cryptoteh

newbie

Activity: 34

Merit: 0

Quote from: cryptodredge on August 04, 2018, 04:21:35 AM

Quote from: cryptoteh on August 04, 2018, 02:53:30 AM

How to set the intensity of the first graphics card 3 and the second 6?

No way. As a workaround for this issue, you might use a few CryptoDredge instances with -d option.
e.g.:

Code: (first.bat)

CryptoDredge -a -o stratum+tcp:// -u -p -d 0 -i 3

Code: (second.bat)

CryptoDredge -a -o stratum+tcp:// -u -p -d 1

Can we expect this option? this is very important

darkneorus

jr. member

Activity: 238

Merit: 3

yup, often the miner tries to use the default API bind address and port (127.0.0.1:4068) instead of using the address from its command line arguments.

superlative1974

newbie

Activity: 45

Merit: 0

thanks to the development team. this is the best miner for the whole time, this is the best team.
Well done.

Burnie

newbie

Activity: 58

Merit: 0

Quote from: cryptodredge on August 05, 2018, 09:01:34 PM

Quote from: sidog on August 05, 2018, 08:06:31 PM

the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?

Yep, that is a known issue. The API often does not start since version 0.8.0. You might try to use 0.7.0 (Windows version is CUDA 9.2 only) Apologize!

Does CryptoDredge close the sockets properly before exiting?
I see a lot of TIME_WAITs when CryptoDredge is running, and they slowly disappear when CryptoDredge is stopped.
If CryptoDredge is started after 3-4 minutes, the api seems to start ok.

cryptodredge

member

Activity: 157

Merit: 19

Quote from: sidog on August 05, 2018, 08:06:31 PM

the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?

Yep, that is a known issue. The API often does not start since version 0.8.0. You might try to use 0.7.0 (Windows version is CUDA 9.2 only) Apologize!

jyakulis

sr. member

Activity: 469

Merit: 250

J

0.8 to 0.8.2 was a big boost on lyra2z for the gtx1070 (2500 kh/s to 3200 kh/s)

However, 0.8 to 0.8.2 the hashrate regressed on lyra2z for the gtx1070ti (3300 kh/s to 2700 kh/s)

sidog

member

Activity: 75

Merit: 10

the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?

jebidia

jr. member

Activity: 161

Merit: 1

Thank you!

cryptodredge

member

Activity: 157

Merit: 19

Thank you one and all for your generous support.

Regards,
The CryptoDredge Team.

cryptodredge

member

Activity: 157

Merit: 19

Quote from: jebidia on August 04, 2018, 05:20:02 PM

Using 0.8.0 with 3 1080ti's.

See the screen grab. Cards a showing 8.3 each but the total is 23.9??? 8.3 x 3 = 24.9 Where is the over 4% going? Or is there just a math issue on the latest version?

It's a little bug, the total hashrate uses the average one. The task for this was created with a low priority.

xlockdownx

newbie

Activity: 19

Merit: 0

Quote from: cryptodredge on August 05, 2018, 05:31:48 PM

Downloads
Windows Download (CUDA 9.2 version)
Linux Download (CUDA 9.2 version)
Mirror on GitHub (CUDA 9.1/9.2 version)

Release 0.8.2 - (August 6, 2018)

Fix Phi2 bug related to smart contracts
Improve Tribus

Release 0.8.1 - (August 3, 2018)

Improve Allium, Lyra2z, and Phi2 for low-end and middle-end graphics cards
Fix P2Pool bug related to many rejected shares
Fix TCP and WebSocket connections used for API
Add power consumption monitoring

Thx for fast work Wink

Topic: CryptoDredge 0.27.0 — CUDA Miner - page 45. (Read 86186 times)