Pages:
Author

Topic: [ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 28. (Read 85791 times)

member
Activity: 658
Merit: 86
The --list_devices might have worked if the application window would stay open long enough to read anything, it closes in under 3 seconds though.

Attempted removing each gpu of 3 using the -d 0,1,2 cn_config etc..     Again, window closes to fast to even see an error message.

Please, I know there has got to be just some switch/call that will enable the application to bypass the unsupported device and stay open.

Closing so fast due to 1 piece of unsupported hardware being attached to the machine and giving no error message, that is surely a bug being re-branded as a feature anyway.

You need to learn to use the console/terminal, rather than just double clicking stuff w/ your mouse.  Run 'command prompt' (press the windows button or click on the windows icon, and type 'command' - then click on the 'Command prompt' item at the top of the list.) . Change to the directory of the miner software (type 'cd ' followed by path to your miner directory.)  Type the name of your start bat file, and press enter.  You'll see the output, including whatever errors occurred.

A window closing after the program has exited is not a bug of the miner - it's the way Windows (and most OS') work.

P.S.  I used to have a 7950 (and a 580) installed on a 6-vega rig running TRM - worked perfectly fine using -d to exclude those devices.

I know how to use it, when instructed to I do, have, will. Otherwise, why do things the hard way, all the time, its just not logical?

Using the bat file via cmd prompt did "help".
[2018-12-27 14:47:45] Auto-detected AMD OpenCL platform 0
[2018-12-27 14:47:46] Initialize error, unknown platform 03fd
[2018-12-27 14:47:46] Failed to initialize device number 0 (-20)
[2018-12-27 14:47:46] Successful clean shutdown.

'-d' is not recognized as an internal or external command,
operable program or batch file.

So where to from here?

Yeah, not saying all the time - just in situations like yours, for debugging purposes, terminal is your friend.  'teamredminer.exe --help' is also useful.  As someone else already stated, try the parameter --platform=1.

The correct platform is detected just fine. It's an unfortunate choice of reusing the term "platform" in the error message. I'm guessing your Tahiti is device zero, but you're not applying the -d param correctly though. It seems to me like it's placed on a new line in the bat file, since the shell tries to execute the "program" called "-d" after the miner exists.

Do these two things and we'll get this sorted: (1) from the cmd prompt, in the directory where teamredminer.exe resides, run "teamredminer.exe --list_devices". Dump the output here and we'll verify the device list. Then (2) dump the content of your start.bat here as well, with any private data anonymized.

If you want to keep the window open when running the miner from e.g. Windows Explorer in a .bat file, add "pause" on a separate line at the end of the .bat.
member
Activity: 340
Merit: 29
The --list_devices might have worked if the application window would stay open long enough to read anything, it closes in under 3 seconds though.

Attempted removing each gpu of 3 using the -d 0,1,2 cn_config etc..     Again, window closes to fast to even see an error message.

Please, I know there has got to be just some switch/call that will enable the application to bypass the unsupported device and stay open.

Closing so fast due to 1 piece of unsupported hardware being attached to the machine and giving no error message, that is surely a bug being re-branded as a feature anyway.

You need to learn to use the console/terminal, rather than just double clicking stuff w/ your mouse.  Run 'command prompt' (press the windows button or click on the windows icon, and type 'command' - then click on the 'Command prompt' item at the top of the list.) . Change to the directory of the miner software (type 'cd ' followed by path to your miner directory.)  Type the name of your start bat file, and press enter.  You'll see the output, including whatever errors occurred.

A window closing after the program has exited is not a bug of the miner - it's the way Windows (and most OS') work.

P.S.  I used to have a 7950 (and a 580) installed on a 6-vega rig running TRM - worked perfectly fine using -d to exclude those devices.

I know how to use it, when instructed to I do, have, will. Otherwise, why do things the hard way, all the time, its just not logical?

Using the bat file via cmd prompt did "help".
[2018-12-27 14:47:45] Auto-detected AMD OpenCL platform 0
[2018-12-27 14:47:46] Initialize error, unknown platform 03fd
[2018-12-27 14:47:46] Failed to initialize device number 0 (-20)
[2018-12-27 14:47:46] Successful clean shutdown.

'-d' is not recognized as an internal or external command,
operable program or batch file.

So where to from here?

Yeah, not saying all the time - just in situations like yours, for debugging purposes, terminal is your friend.  'teamredminer.exe --help' is also useful.  As someone else already stated, try the parameter --platform=1.
member
Activity: 418
Merit: 21
newbie
Activity: 4
Merit: 0
The --list_devices might have worked if the application window would stay open long enough to read anything, it closes in under 3 seconds though.

Attempted removing each gpu of 3 using the -d 0,1,2 cn_config etc..     Again, window closes to fast to even see an error message.

Please, I know there has got to be just some switch/call that will enable the application to bypass the unsupported device and stay open.

Closing so fast due to 1 piece of unsupported hardware being attached to the machine and giving no error message, that is surely a bug being re-branded as a feature anyway.

You need to learn to use the console/terminal, rather than just double clicking stuff w/ your mouse.  Run 'command prompt' (press the windows button or click on the windows icon, and type 'command' - then click on the 'Command prompt' item at the top of the list.) . Change to the directory of the miner software (type 'cd ' followed by path to your miner directory.)  Type the name of your start bat file, and press enter.  You'll see the output, including whatever errors occurred.

A window closing after the program has exited is not a bug of the miner - it's the way Windows (and most OS') work.

P.S.  I used to have a 7950 (and a 580) installed on a 6-vega rig running TRM - worked perfectly fine using -d to exclude those devices.

I know how to use it, when instructed to I do, have, will. Otherwise, why do things the hard way, all the time, its just not logical?

Using the bat file via cmd prompt did "help".
[2018-12-27 14:47:45] Auto-detected AMD OpenCL platform 0
[2018-12-27 14:47:46] Initialize error, unknown platform 03fd
[2018-12-27 14:47:46] Failed to initialize device number 0 (-20)
[2018-12-27 14:47:46] Successful clean shutdown.

'-d' is not recognized as an internal or external command,
operable program or batch file.

So where to from here?
member
Activity: 340
Merit: 29
The --list_devices might have worked if the application window would stay open long enough to read anything, it closes in under 3 seconds though.

Attempted removing each gpu of 3 using the -d 0,1,2 cn_config etc..     Again, window closes to fast to even see an error message.

Please, I know there has got to be just some switch/call that will enable the application to bypass the unsupported device and stay open.

Closing so fast due to 1 piece of unsupported hardware being attached to the machine and giving no error message, that is surely a bug being re-branded as a feature anyway.

You need to learn to use the console/terminal, rather than just double clicking stuff w/ your mouse.  Run 'command prompt' (press the windows button or click on the windows icon, and type 'command' - then click on the 'Command prompt' item at the top of the list.) . Change to the directory of the miner software (type 'cd ' followed by path to your miner directory.)  Type the name of your start bat file, and press enter.  You'll see the output, including whatever errors occurred.

A window closing after the program has exited is not a bug of the miner - it's the way Windows (and most OS') work.

P.S.  I used to have a 7950 (and a 580) installed on a 6-vega rig running TRM - worked perfectly fine using -d to exclude those devices.
newbie
Activity: 4
Merit: 0
Start with -d 0. If it runs, start again with -d 0,1 and so on. When it crashs, you have your unsupported device. Easy  Wink

... I know which device is not supported, Tahiti HD 7950. It makes no differecne which (-d) it shows up as, if it is installed on the machine the application will not run.
member
Activity: 418
Merit: 21
Start with -d 0. If it runs, start again with -d 0,1 and so on. When it crashs, you have your unsupported device. Easy  Wink
newbie
Activity: 4
Merit: 0
The --list_devices might have worked if the application window would stay open long enough to read anything, it closes in under 3 seconds though.

Attempted removing each gpu of 3 using the -d 0,1,2 cn_config etc..     Again, window closes to fast to even see an error message.

Please, I know there has got to be just some switch/call that will enable the application to bypass the unsupported device and stay open.

Closing so fast due to 1 piece of unsupported hardware being attached to the machine and giving no error message, that is surely a bug being re-branded as a feature anyway.
member
Activity: 658
Merit: 86
I'm new so, sry 4 new b Q.

Is there a switch to bypass unsupported devices? I.e. Do not use AMD (Tahiti) HD 7950.

Obviously want to use my Vegas, just don't think I should have to completely uninstall the unsupported card just to use the miner.
  Cry


Run "teamredminer.exe --list_devices" to list your available devices on the auto-detected AMD platform. Check the OpenCL column and run the miner with -d 0,1,2,4 to skip device 3. Let me know if you still have issues Smiley.

newbie
Activity: 4
Merit: 0
I'm new so, sry 4 new b Q.

Is there a switch to bypass unsupported devices? I.e. Do not use AMD (Tahiti) HD 7950.

Obviously want to use my Vegas, just don't think I should have to completely uninstall the unsupported card just to use the miner.
  Cry
member
Activity: 658
Merit: 86
Planning to add the mtp algo?

Not sure we'll spend time on MTP as things stand right now. We'll see though, nothing is written in stone!
member
Activity: 658
Merit: 86
GPU 5: detected DEAD (03:00.0), no restart script configured, will continue mining.
Please use command line argument --watchdog_script to handle dead GPUs.

How to do it ?

You need to have a script called watchdog.bat in the same directory as the miner .exe that handles the situation. It's up to you to decide what should happen, and it depends on how your rig normally behaves when a gpu dies. For some people, they can just restart the miner. For most, they rather reboot the machine using e.g. "shutdown /r now" on Windows.

I believe the TeamRedMiner CN thread has a few examples of use restart scripts as well.
jr. member
Activity: 75
Merit: 1
Planning to add the mtp algo?
newbie
Activity: 103
Merit: 0
GPU 5: detected DEAD (03:00.0), no restart script configured, will continue mining.
Please use command line argument --watchdog_script to handle dead GPUs.

How to do it ?
newbie
Activity: 19
Merit: 0
Hello, I love your miner and I have been using this on many lyra2z coins!
Im wondering is it possible to add the miner to support Lyra2zz, its Lapo Blockchain's own algo modified from lyra2z. This would be the first amd miner to support this algo. Let me know you are interested to help.
newbie
Activity: 82
Merit: 0
the optimizations for older cards for mining MNX- minexcoin, R9 290X and hd 7970 are always strange, they are not in pair. When r9 290x is best optimized, then hd 7970 is not at its peak, and when hd 7970 is at its peak, then r9 290x is not at its peak...for example.
With  alpha 3 version. the hashrate for r9 290 is around 16 000 and for hd 7970 is around 9900...now
in alpha 4 version, hd 7970 is around 12 000, but r9 290x is aroung 15 000....no matter what workbatch i use.
And it was also in older version's like this...
member
Activity: 176
Merit: 76
any plans to include lyra2rev3?

Yep, we've looked at it and we're hoping to have it ready by the time of the fork.
full member
Activity: 729
Merit: 114
any plans to include lyra2rev3?
member
Activity: 164
Merit: 13
awesome! can you disable or change the watchdog?

What are you looking to do? The watchdog checks for a number of things: shuts on/off a gpu if the temp go out of range, executes your watchdog script if a gpu dies, then some internal checks as well.

just change temp settings/cutoff.
newbie
Activity: 12
Merit: 0
What's the command for fan control? (say I want it to set it to 50% all the time)

me too Smiley

thanks

Hey guys! Sorry to disappoint, it's only sensors and watchdog in this release, can't control fans/clocks. We print and react to the temp, but no support for changing fans for now. Fan control is much simpler than clocks though, I'm sure we can slot that in for an upcoming release.

To save you some work you can probably use/apply/take parts from this scrypt for AMD fans ( http://drakyla.org/atifans.sh ) . I didn't create it , but i`m using it often on my rigs . Should be easy to adopt it since its only 3.3kb .

Regards


Edit: The command to use it (after you chmod it to 755) is ./atifans.sh -s 50                         (where 50 is 50% of the total fan speed)
Pages:
Jump to: