Time to write of assets on the exchange, I guess....
Withdrawals aren't being processed....
|
|
|
Awesome miner firmware api(/api/v1/status) returns {"miner_state":"mining","miner_state_time":163.0,"find_miner":false,"restart_required":false,"reboot_required":false,"unlocked":true} and awesome miner api(/api/miners/{id}) [statusInfo] returns {'statusDisplay': 'Mining', 'statusLine3': '0h 4m', 'secondsSinceStart': 252, 'state': 3, 'stateExtra': 0, 'line3Ex': {'type': 'ParamShortTime', 'values': ['0', '4']}} But, after pausing minings with post to awesome mine api(/api/miners/{id}?action=pause) Awesome miner firmware api(/api/v1/status) returns {"miner_state":"stopped","miner_state_time":34.0,"find_miner":false,"restart_required":false,"reboot_required":false,"unlocked":true} and awesome miner api(/api/miners/{id}) [statusInfo] returns {'statusDisplay': 'Mining', 'statusLine3': '0h 0m', 'secondsSinceStart': 59, 'state': 3, 'stateExtra': 0, 'line3Ex': {'type': 'ParamShortTime', 'values': ['0', '0']}} Can you change the awesome miner statusDisplay based on the awesome miner firmware miner_state? Current behaviour is misleading.
|
|
|
And where is your proof? I will wait for your stupid answer.
Putin is attacking Ukraine. Millions are fleeing their homes to escape the bombs and slaughter. Until the aggression is stopped we should stop trading with Russian companies, block their money / funds. Gminer and the Team Red Miner is made in Russia and should not be supported until the war is over. How do you know its Russian??
|
|
|
hi, I've updated miner from 8.6 to 9 but now Windows 11 antimalware detects Program:Win32/Beareuws.A!ml dangerous app, which interest the miner path. Somebody with same problem?
https://github.com/todxx/teamredminer/releases/tag/v0.9.0TRM 0.9.0 was released with support for FPGA - Eth mining. It could be that the new code for FPGA triggers the warning. If you download from official sources, then it should be fine for whitlelisting the exe.
|
|
|
I feel like i just got trolled by a fury lover ... NSFW.. Had it not been fury, I would have questioned the legitimacy of the author
|
|
|
Can't connect to pool nicehash
teamredminer.exe -a autolykos2 -o stratum+tcp://autolykos.eu.nicehash.com:3390 -u xxxxxxx.3 -p x
[2021-08-19 10:41:23] Runtime Command Keys: h - help, s - stats, e - enable gpu, d - disable gpu, q - quit [2021-08-19 10:41:38] Pool autolykos.eu.nicehash.com connecting to address 172.65.200.133. [2021-08-19 10:41:38] Pool autolykos.eu.nicehash.com successfully connected to address 172.65.200.133. [2021-08-19 10:41:38] Pool autolykos.eu.nicehash.com connection was closed due to an error. [2021-08-19 10:41:43] Shutting down...
The stratum for autolykos is : stratum+tcp://autolykos.eu-west.nicehash.com:3390 stratum+tcp://autolykos.eu-north.nicehash.com:3390 https://www.nicehash.com/stratum-generator
|
|
|
Hi Trying to mine on RaveOS (8708-1983), on TRM 0.8.4 and I get "Bus error". Lol miner, Phoenix work fine on my rig. Can developers explain such behaviour of TRM 0.8.4? Thank you in advance. It should work fine, i have a feeling raveos is using a diff bus ordering. But it seems like an ez and already solved bug ni rave os if any. Try asking the rave os devs
|
|
|
Hello guys i hope you are all doing good one question: for ravencoin mining on windows 10, amd rx 570 4gb, what is the best way to control fans, voltages and clocks? can i do it from the miner (like eth mining on phoenix or old claymore, where i can control temps, fans, etc via a command) thanks As far as I know, you cant control voltage and clocks,.. I do it throug OverdriveNTool program. hi good sir, sorry to bother you. ive been using overdriveNtool, but when i have a power cut problem or something, and the rig restarts, it will restart on the default clocks, not the overdrive ones. how can i set them auto at win start? thanks You can setup overdriventool via its cli commands, once you have a working bat file, set it to autorun on boot via Windows Task Scheduler
|
|
|
I manage about 30 amd rigs in the birmingham area of the uk.
really like your miner - it does all you claim and is slightly better than the competition. its especially good on radeon VII and rx5700 .
at present the rigs all have the following set in the config.txt file core clock mem clock core volts mem volts fixed fan speed max temp before gpu throttles (this is vital)
theres other stuff but those 6 things are the main ones.
if your miner could set those 6 things within its config - i would dump the competition and use your miner on all rigs. yes i know about overdriventool and msi afterburner but in my experience on rigs with 470, 570,480,580,5500, 5700, radeon vii - those tools are hit and miss and too much trubble . we use windows 10 ghost spectre (no updates, bloat or telemetry) and mostly amd driver 20.9.1 the one rig that isnt 20.9.1 - has a vega frontier edition 16gb water cooled - i should do a video on that rig - what a palaver to get that card mining. but we did it with driver 19.7.1 and the registry hack
ghost spectre rocks - you will be amazed. no updates . rock solid . tiny ram usage . tiny disk usage. best wishes from manchester uk
Dev said they were working on, but no idea on eta !!
|
|
|
I have the same doubt with AMD cards, why do they use phoenix instead of teamredminer. As for most common replies, - Built in clock control
- AMD and Nvidia support
- Higher Hashrate, this is the crazy part, phoenix displays a higher hashrate than trm and trex, but way slower pool side, but i guess to the causal miner it doesnt matter !!
|
|
|
To the Teamredminer development team:
Is it possible to put in the Power throttle limit control to slow down the mining itself in order to protect GPU does not over temp under GPU temp/ Junction temp/ Vram temp , pls consider
Such a feature isnt there at the moment, but check if these commands help in your case to protect GPUs --temp_limit=TEMP Sets the temperature at which the miner will stop GPUs that are too hot. Default is 85C. --temp_resume=TEMP Sets the temperature below which the miner will resume GPUs that were previously stopped due to temperature exceeding limit. Default is 60C.
|
|
|
On the Autolykos protocol, when mining an ERGO coin (pool woolypooly), the miner constantly writes about duplicate work, is this not good? a lot of expired shares and as a result of rejections
To be clear, it's not a bug in the miner, it's just an unnecessary warning, the workaround is 100% safe and works. Basically, it means we don't refresh the nonce range we test since the pool job we just received is 100% identical to the previous one, we continue hashing from the last nonce used before the new job arrived. It's more that it's occuring much more often in the ERGO mining world, pools don't seem to refresh the job from the daemon when they send out a "new" job for the same network block height. The warning was inherited from other mining protocols where this doesn't really happen naturally but should be removed for ERGO for users since it adds zero value, only confusion.
|
|
|
Hey Team,any plans to add Ergo coin algo for AMD ?
Nvidia also
|
|
|
[2021-05-13 19:21:06] GPU 0 Gpu monitor stats refresh timed out, no data available. [2021-05-13 19:21:06] GPU 1 Gpu monitor stats refresh timed out, no data available. [2021-05-13 19:21:06] GPU 2 Gpu monitor stats refresh timed out, no data available. [2021-05-13 19:21:06] GPU 3 Gpu monitor stats refresh timed out, no data available. [2021-05-13 19:21:06] GPU 4 Gpu monitor stats refresh timed out, no data available. [2021-05-13 19:21:06] GPU 0 Gpu monitor stats refresh timed out, no data available.
Please help..
What OS, Driver, GPU and TRM Version
|
|
|
I understand that Claymore miner is done now, but using 1080 Ti cards with every other miner I get ~18MH/s instead of ~47MH/s if the DAG is over 4GB in benchmark modes (win 8.1). What am I missing? Linux works well so I'm guessing it's some driver or windows limitation? Is there a workaround?
You need to use the ETHEnlargement Pill. That tool will asjust the timing of the 1080ti to give 47+ mh/s. Most mining os support the pill by defualt.
|
|
|
Hello, does anyone know if there is a monitoring app for TRM? Or at least an API for miner info.
There are many tools to monitor miners including TRM. I suggest : foreman.mn( https://foreman.mn/), this is a pretty good, pure monitoring tool. Or you can use awesome miner.
|
|
|
Hi Patrike, Just tried benchmarking the new Lolminer, and found that of the algo's that I use, only ZHash works with the current settings. I ran Lolminer in a command prompt, and found that the algo's BEAMHASH I, Equihash 144/5, Equihash 192/7, and ZelHash now require the --pers parameter. I tried finding the arguments to the --pers parameter for each algo, but they aren't listed on github, so I raised an issue requesting them. I was able to get the algo's that I'm using to work in a command prompt, by using the --coin parameter with the following changes... For Equihash 125.4, --algo ZEL --devices 0 --pool <URL>:<Port> --user <User> --pass <Password> --apiport 4029 changed to --coin ZEL --devices 0 --pool <URL>:<Port> --user <User> --pass <Password> --apiport 4029 For Equihash Zero (192.7), --algo EQUI192_7 --devices 0 --pool <URL>:<Port> --user <User> --pass <Password> --apiport 4029 changed to --coin AUTO192_7 --devices 0 --pool <URL>:<Port> --user <User> --pass <Password> --apiport 4029 For Equihash 144.5, --algo EQUI144_5 --devices 0 --pool <URL>:<Port> --user <User> --pass <Password> --apiport 4029 changed to --coin AUTO144_5 --devices 0 --pool <URL>:<Port> --user <User> --pass <Password> --apiport 4029 Is it possible to use these commands in the custom command entry for each algo under Options -> Managed Software -> LolMiner, and have the --pool <URL>:<Port> --user <User> --pass <Password> parameters auto-fill like %URL% would be replaced in batch files? Thanks for your help. Hey lolminer has since version 1.0 updated the parameters. The --coin is also supported, but the newer algos are all using --algo. Like you said Equihash 144/5, Equihash 192/7, need --algo and --pers. The '--pers' is a string from the coin dev, not the miner dev, you can get the --pers based on the coin you want to mine. Its better to use this method to ensure future compatibity.
|
|
|
Bugfixes on lolminer compatibility: 1. Miner supports all c29 variants (29,d,m) and c31 2. Miner uses this format of algo support. I think it is done internally in AM and not via miner properties-command line arg. Adding support to do this via the deafult/user defined command line args would help --coin <coinToMine> --coin sets the coin you want to mine, e.g. BEAM,AION,BTG,... ... 3. Hashrates are not properly parsed in decimal from the api. The api gives proper 1.2 as values, but is parsed and displayed as 1 in am. Thanks for the details! There were a number of hardcoded mappings for Lolminer as it had a bit special concept for specifying algorithms - as it's typically the coin name you specify. I will change this to be more flexible where you can use the standard algorithm configuration for Lolminer as well. I will also correct the hashrate reporting. Hey, this still has some hardcoded mapping. MWC coin runs with --coin MWC instead of the standard algorithm overrides. Algo : C29D : MWC-C29D Rest of the C29M, C31, C32 work fine Can you please double check if you manually added "--coin MWC" or "MWC" somewhere like below? 1) In the Properties of your pool, command line. 2) Options dialog, Managed Software section, lolMiner algorithm mapping. When looking at how lolMiner is started by Awesome Miner, there are no hard coded coins. If I'm wrong - please let me know. MWC is mined with C31 and C29D algos. For lolminer, AM doesnt have builtin algo mapping for C29D algo, so adding custom mapping as MWC-C29D. Then starting the miner with no parameters in diagnostics shows, miner started with --coin MWC instead of the custom mapped --coin MWC-C29D Each time a new algo is added, AM need to be updated from your side... Can you pls make it more dynamic in the coin properties. Miner supports the common -a configuration like any other miner, the AM is still using the old --coin hard mappings. Suggestion: 1. Make -c [ --coin ] dynamic List of supported coin presets:
Preset Coin Algorithm AION Aion Equihash 210/9 AUTO144_5 Equihash Pool Selection Equihash 144/5 AUTO192_7 Equihash Pool Selection Equihash 192/7 BEAM BEAM BeamHash III BTCZ BitcoinZ Equihash 144/5 BTG Bitcoin Gold Equihash 144/5 CTXC Cortex Ai Cuckaroo 30 CTXC EXCC Exchange Coin Equihash 144/5 (EXCC) GRIN-C29M Grin CuckarooM 29 GRIN-C32 Grin Cuckatoo 32 MWC-C29D MimbleWimbleCoin CuckarooD 29 MWC-C31 MimbleWimbleCoin Cuckatoo 31 XSG Snowgem Equihash 144/5 YEC YCash Equihash 192/7 ZCL Zclassic Equihash 192/7 ZEL Zel Cash ZelHash ZER Zero Equihash 192/7 [OR] 2. Switch to -a [ --algo ] List of supported algorithms:
Parameter Algorithm Fee % Needs / Supports --pers BEAM-I BeamHash I 1.0 true BEAM-II BeamHash II 1.0 false BEAM-III BeamHash III 1.0 false C29AE Cuckoo 29 2.0 false C29D CuckarooD 29 2.0 false C29M CuckarooM 29 2.0 false C30CTX Cuckaroo 30 CTXC 2.5 false C31 Cuckatoo 31 2.0 false C32 Cuckatoo 32 2.0 false CR29-32 Cuckaroo 29-32 1.0 false CR29-40 Cuckaroo 29-40 1.0 false CR29-48 Cuckaroo 29-48 2.0 false EQUI144_5 Equihash 144/5 1.0 true EQUI192_7 Equihash 192/7 1.0 true EQUI210_9 Equihash 210/9 1.0 false ZEL ZelHash 1.0 true
|
|
|
NBMiner on ETH has multiple stratum support. But AM is defaulting to the proxy stratum, can you set AM to not define the statum-proxy:// part of the url and instead use the entire url as defined in the pool config?
What Awesome Miner do today for NbMiner in case of ETH mining is to replace any "stratum" string in the URL with "ethproxy" in the pool url that typically looks like stratum+tcp://poolurl. Can you please give an example of the complete URL you are using? If it doesn't contain the string "stratum" it shouldn't be modified. Actual Pool URL : stratum+tcp://eth.2miners.com:2020 But it be being converted to a ethproxy url which the pool rejects as invalid. NBMiner supports for ETH mining : nicehash+tcp:// ethproxy+tcp:// stratum+tcp:// I think AM should take the URL as is from pool config, so that the user can configure the miner as required instead of locking to ethproxy.
|
|
|
|