Print Page - AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool

Bitcoin => Mining software (miners) => Topic started by: lvlrdka22 on May 28, 2011, 01:48:58 AM

Title: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: lvlrdka22 on May 28, 2011, 01:48:58 AM

AutoIt OpenCL Bitcoin Foreman

Disclaimer: I'm not responsible for turning possessions (yours or otherwise) into paperweights/doorstops!
Read everything before asking for help!

Need feedback on:

If the link between OpenCL GPU list and OS Index is correct (if setting an OpenCL Device automatically selects the corresponding GPU correctly) (beta version only).
If ADL detects the same number of GPUs as OpenCL (if the OpenCL Device list has same number of GPUs as number of tabs for controlling GPU clocks).
If it detects multiple GPUs correctly, in particular the 5970 and the 6990 (should be one tab for each core, or two tabs for each 5970/6990).

http://i55.tinypic.com/2d6rtar.png

Supports Phoenix 1.50 and classic POCLBM 20110709 (and modded ones that use the exact same launch parameters and output).

Instructions:

Code:

Download it, extract it, place the contents in your POCLBM/Phoenix folder (where poclbm.exe/phoenix.exe is located). Run it to configure.

Client fields:

Code:

User ID: your user ID for your worker at a particular mining server.
Password: the password for your worker. Blank passwords are not allowed.
Server: the server you are mining at, e.g. btcguild.com and us.mining.eligius.st (yes, I'm advertising them!).
Port: the port to connect to the server at, 83xx from what I've seen.
Backup: enables miner running on a back up pool if the main pool is down.
Startup: starts miner on program start.
Device Name: the nick name for your device to mine on.
Vectors: uses vectors option. Can possibly increase mining speed if enabled.
HD5xxx+: checked means use BFI_INT, uncheck if your hardware doesn't support it (commonly, HD5k and HD6k series are supported, only present in Phoenix).
Fastloop: the fast loop argument. Can possibly increase mining speed if enabled (only present in Phoenix).
phatk: uses the phatk kernel, optimization for HD58xx series only I think? You MUST have phatk already inside the kernels folder (only present in Phoenix).
Aggression: how resource-intensive the mining is, 0 for least usage, 12+ for most usage (will probably make the computer unusable if you are using it for monitor display, only present in Phoenix).
OpenCL Device: also called Device Number (pre-1.7). "OpenCL Device" is not a valid device number. Click "Manual" to type in the Device Number manually.
Extra Flags: any other flags not mentioned can be added here, such as -q 2. "Extra Flags" is not a valid flag.
Temperature control: checked means monitors temperature range as well as temperature display on OSD (unchecked means it will show a ?). AMD/ATI only. Read bottom instructions on how to find GPU number.
Affinity: sets all of the workers to use one specific core (or all available cores).

GPU buttons:

Code:

Refresh: refreshes GPU clock/fan speeds.
Clock Speed: sets GPU clock speed and voltage to current values on the GUI.
Fan Speed: sets fan speed to current values on the GUI. If there is another application controlling fan speed (Afterburner), it may interfere with this.
Default: resets clock speed and voltage to default settings (on BIOS).
Core: minimum and maximum depends on BIOS limits, 1 MHz increment (type it in or click-drag/click-left-right-arrow slider). Maximum set to BIOS limit plus 200 MHz. If unable to set it higher, probably means you've hit BIOS limit.
Memory: minimum and maximum depends on BIOS limits, 1 MHz increment (type it in or click-drag/click-left-right-arrow slider). Maximum set to BIOS limit plus 200 MHz. If unable to set it higher, probably means you've hit BIOS limit.
Voltage: minimum and maximum depends on BIOS limits, 1 mV increment (type it in or click-drag/click-left-right-arrow slider). Maximum set to BIOS limit plus 200 mV. If unable to set it higher, probably means you've hit BIOS limit.
Fan: minimum 0%, maximum 100%, 1% increment (type it in or click-drag/click-left-right-arrow slider).

Main buttons:

Code:

Run: starts mining.
Stop: stops the mining and resets the share count.
Add Client: adds another row of configuration to the GUI.
Remove Client: removes a selected row of configuration from the GUI.
Save Settings: saves the current settings to an INI file. The read-onlyness is also saved.
Read Only: enables/disables all of the fields, in case of accidental click and typing (annoying if you have a generated password).
Click Through: toggles if click+drag works on the On Screen Display or not. If so, click+drag to move it around. If not, clicks will automatically translate to the next window below. When toggled on, it will also prevent the OSD from ever moving until untoggled.

A couple things to note:

Displays current statistics through On Screen Displays (OSD), namely the hash rate, accepted shares, and rejected shares (1.6 includes GPU temperature if "Pause mining when..." is checked).
Minimizes to tray, double-clicking on the tray icon shows/hides it.
Exit via "x" button, or right click on the tray icon.
If it crashes for any reason before all of the clients are stopped, you MUST manually end-task all poclbm.exe/phoenix.exe.
Auto restarts clients after a set amount of idle time. Idle starts counting when there are no update to the text output of POCLBM/Phoenix, or when the hash rate is 0. For multiple GPUs, only works with dummy plugs. Remember, don't set it too low! The time it takes to connect to server and start mining counts towards the idle time!
Sets affinity of all clients to one selected core, or all cores.
Can mine on an alternate pool if current pool is down.
When running on backup pool, it checks if primary pool is online every set seconds/minutes/hours, AND when restarting the backup pool (if it failed to connect for any reason).
Reads graphic card temperature through a DLL file that should be provided with every AMD driver install (sorry nVidia people), and has option to pause mining if temperature exceeds a certain number, and start again once it drops below a certain number. You must follow separate instructions to find the GPU number!
Separate tabs to control GPU clocks/voltages/fan speeds.
If you are getting blank fields for any of the drop-down boxes, delete the INI file and redo it! Or just open it, and delete the lines where it's blank after the equals sign. Some GUI modifications broke the INI saving/reading process a little.

Here's a sample of the OSD in action: http://oi56.tinypic.com/rrkv0p.jpg (http://oi56.tinypic.com/rrkv0p.jpg). Bottom right. The GPU statistics is a different script.

That should sum it up pretty well.

The important parts:
Source attached, in case you don't trust the precompiled version (32-bit only now, 64-bit compatibility broken with 1.4, but can still be run in 64-bit environment, just not compiled).
Yes, it's completely autoit (except for the POCLBM/Phoenix part, obviously).

Current version 1.75: http://www.mediafire.com/?s0b0mo0mbrlyg67.
Previous versions

1.74: http://www.mediafire.com/?yvm8el5lccudu7w
1.73: http://www.mediafire.com/?4djdpojrsd3n0kk (only for people who had trouble launching 1.72)
1.72: http://www.mediafire.com/?jnvnnp0q5fs6ngn
1.71: http://www.mediafire.com/?x2dbpei3t555em9
1.7: http://www.mediafire.com/?4gt5yxojxj2y8p9
1.62: http://www.mediafire.com/?tjc90npatisi35o
1.61: http://www.mediafire.com/?6tx6wewldrdr5p4
1.6: http://www.mediafire.com/?gu3wnan5e28a9o1
1.51: http://www.mediafire.com/?j96m4z751zrw3xj
1.5: http://www.mediafire.com/?ntsa37sjl7t6sc0
1.45: http://www.mediafire.com/?x5dr7n3j6vijvyd
1.44: http://www.mediafire.com/?rd47gbtu1p3xcwo
1.43: http://www.mediafire.com/?l3kop8q2wx0spj2
1.42: http://www.mediafire.com/?budubavlbb9uplf
1.41: http://www.mediafire.com/?5h3y5b6jq1azp13
1.32: http://www.mediafire.com/download.php?u1tmtamjekr8b9a
1.31b: http://www.mediafire.com/?c2jfam1cubkg1b3

IF you really feel the need to donate, too bad!

Oh, and inb4omgitsavirus!

History:
1.75 Updated with newest classic POCLBM syntax and parsing of newest output. The only clients supported are the ones that use same command line syntax and produces same output as the classic version. Fixed some of the options not loading correctly when adding a new client.
1.74 Updated to parse newest classic POCLBM output. Added an option to type in Device Number manually.
1.74b Made the OSD font non-bold.
1.74a Attempted a better solution at detecting adapter list. Hopefully this works for both people with on-board and dual GPUs.
1.73 Fixed an issue (possibly) with detecting non-existent/on-board GPUs. Let me know if it's still broken. Added some logging.
1.72 Apply-OC-on-startup should work correctly now. Switched from using device ID to OS index, since apparently device ID changes every time restarts happen ::).
1.71 Really added POCLBM parsing this time (1.7c only parsed the Luke-Jr's version that has more output).
1.7 Can now save and apply clocks on startup.
1.7c Added POCLBM parsing. Just place it in folder. If both poclbm.exe and phoenix.exe are in the same folder, it will run POCLBM. Otherwise it will look to see which EXE file is present, and use that.
1.7b Fixed a couple bugs with the GUI. Changed to different method of detecting parent/child processes.
1.7a Added detection of clock/fan-setting errors. Auto-detects OpenCL GPU devices and places them in drop-down menus for Phoenix Device Numbers. Detects Adapter Indices and places them in drop-down menus, for temperature monitoring. Experimentally linked the OpenCL GPU list to the GPUs detected by ADL through OS Indices for each of the GPUs (provided by ADL). The number of OpenCL GPUs must be the same number of GPUs detected by ADL. Renamed Device Number field to OpenCL Device.
1.62 A few GUI changes such as number-only in certain fields, disabled typing in text in drop-downs, passwords in dots, etc. Set the GPU sliders to BIOS max clock plus 200 MHz (for core and memory) and BIOS max VDDC plus 0.2 V. VDDC display is now in mV, rather than V.
1.61 Reads hard limits on each GPU placed by the GPU BIOS.
1.6 Added GPU clock/voltage/fan controllers. OSDs now display temperature if "Pause mining when..." is checked and the GPU number is filled in. The GPU number used in monitoring temperatures is changed to use Adapter Index.
1.51 Fixed an issue with some checkboxes.
1.5 Switched to tabs due to numerous requests. Made Aggression and Worker Size use drop-down-and-select controls. Added a checkbox for VECTORS since apparently quite a few people can't figure out the reason for the drop in hash rate between 1.3 and 1.4. Now kills all orphan (the ones that aren't in the "currently running" list) Phoenix instances.
1.45 Closes all launched phoenix instances on exit. Fixed a potential "bug" with new switch-to-backup method, so that the time in "number of restarts in x time before switching" can only be set to the minimum of (max idle+5 seconds)*number of restarts. The 5 seconds is a grace period for miner to start up.
1.44 Switched from using ping to check if server is online or not to x restarts per y seconds/minutes/hours. Let me know how it works.
1.43 Fixed a few random bugs (don't remember which, but I fixed them!). Save Settings now saves the current position of the OSDs (I thought it did with 1.42 already ???). Fixed the active window bug thing.
1.42 Fixed (not sure) a bug with spamming the Click Through button. Save Settings now saves the current position of the OSDs.
1.41 Fixed a bug that wasn't letting phoenix running (what's the point of adding a feature if it doesn't get implemented?).
1.4 Added an option to pick a random core to run on. Temperature control, as in setting it to stop when exceeding a certain temperature, and running again when below a certain temperature. Kills phoenix process directly instead of ctrl+break the CMD window (let me know if there are any side effects to killing the process, or if the hang bug still occurs). Broke 64-bit compatibility when I added DLL usage and process killing function, so only 32-bit binary from now on.
1.31 Added startup option. Fixed a bug that wasn't loading OSD font color from INI file correctly. Fixed a potential issue with two kernel-loading arguments. Removed VECTORS argument from the must-load arguments list. Add it to Extra Flags if you want to use it.
1.3 Adding ability to set a backup server in case current goes down (still need ideas on how to detect if a server is down). Replaced "worker size" field with "extra flags." Added field to choose a preset OSD color. Fixed an issue with fastloop, should work correctly now (when disabled).
1.3c Attempted fix of buggy click-throughness of OSD on some computers.
1.3b Fixed an issue with array index out of bounds (stupid me). Added a check for only one core.
1.3a Redid the GUI completely so that it looks neater. Added work size. No longer need to save before adding/removing a miner.
1.23 Fixed an issue with timers.
1.22 Sets affinity of all phoenix instances to one core.
1.21 OSD shows how much time until restart after miner idles for 5 seconds.
1.2 Fixed an OSD-moving bug. Added auto-restart after a set amount of time of idling.
1.1 Initial release.

Extras: Finding GPU Number. I think this is specific enough. Let me know if it's still confusing.
Also, let me know if temperature readings are off.
Post-1.7: should be automatic. If it selects a different card's temperature sensor, follow instructions below, and let me know that it doesn't work.
Post-1.6:

Code:

Go into the tabs for controlling GPU settings. It should list Adapter Index for each of the GPUs.
They should be in order, as in the Index listed on the first GPU tab should be Device 0 (for POCLBM/Phoenix itself), Index listed on second tab should be Device 1, etc.
To check, run one client and see if the temperature on the OSD goes up (or you can launch another temperature-monitoring application for this).
If that doesn't work, try rotating through the Index in each of the tabs, and see which Index corresponds to which Device Number (for POCLBM/Phoenix).

Pre-1.6:

Code:

Launch Device Finder.exe.
It should read out how many AMD GPUs you have in your system (one reading for each 5970, two for each 6990) with "Number of Devices Detected".
Check which temperature reading matches with which GPU (with 5970s, just use the one reading for both cores, couldn't figure out how to get the second reading).
Put the number in "Device # temperature" that corresponds to the Device Number of each client in the POCLBM/Phoenix Rising fields "Pause mining when GPU # reaches..." For example, if it reads "Device 2 temperature: 53.5°C." and that temperature corresponds to Client #3 with Device Number 1, put 2 so that it reads "Pause mining when GPU 2 reaches..." for Client #3.
For 5970s: there's only one reading for both cores, so use the same number for the two clients running on it.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: compro01 on May 28, 2011, 02:04:45 AM

this looks lovely. will have to try it.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: allinvain on May 28, 2011, 02:13:07 AM

Niice! good work!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Mechanizm on May 28, 2011, 03:26:58 AM

Works great, I love it! Thanks! ;D

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: um0rion on May 28, 2011, 03:49:52 AM

Just gave it a shot, looks like it sets up right, but the OSD doesnt work for me. The program looks like it is running, but Ive got no way to tell. Im running a single Sapphire 5850 Xtreme on Windows Vista 64. It might just be something with vista... Id love to get this working if it gives me a better hashrate than guiminer.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 28, 2011, 04:08:35 AM

Try alt+tabbing. Do you see their "windows" like this?
http://i52.tinypic.com/14rw9h.png

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on May 28, 2011, 04:15:48 AM

Does this gui restart phoenix if the connection drops? im looking for something that gets around the phoenix idle bug

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 28, 2011, 07:15:12 AM

What's the common way of mining on multiple GPUs? Fake plugs? As an example for fake plugs, for 2 GPUs, do you just set device number to 1, and it starts mining on GPU #2? If so, should be relatively simple. I can add it so that it automatically restarts after a set amount of time of 0 hash rate.
There probably won't be monitor-switching support though (as in plugging monitor in to a different card to start mining on it).

Also, fixed an issue on the OSDs moving by themselves when switching monitors that I'll include when I add the auto restart.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 28, 2011, 06:09:01 PM

Got some resistors and tested out how dummy plug works.
Updated with the OSD-moving fix, and with restart-on-idle.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 29, 2011, 01:14:38 AM

Bump.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kingfihserb90 on May 29, 2011, 02:56:27 AM

So when I get this going I get the phoenix miner box flashing saying:
Client #1:0
Restarting, please wait.

Then the black command line box flashes the screen repeatedly.

Anyone able to tell me what I am doing wrong?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: PoulGrym on May 29, 2011, 03:10:59 AM

Haven't tried this yet, but wanted to see if the starting video that uses GPU still hangs the comp? If not is it possible for the GUI to detect this and not hang the comp ;P that would be a great future to add!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 29, 2011, 03:38:40 AM

Quote from: Kingfihserb90 on May 29, 2011, 02:56:27 AM

Try this: http://www.mediafire.com/?v199npcn1jnocnt
I was getting them a little before, I thought I fixed it.
Also, make sure your idle time is not set too low, like 5 seconds. It takes a few seconds for the miner to connect to the server to start mining, which is counted as idle time.

Quote from: PoulGrym on May 29, 2011, 03:10:59 AM

It's an issue with drivers/phoenix I think. Not fixable with GUI.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kingfihserb90 on May 29, 2011, 03:42:32 AM

Yup thats the version I am presently using.

I literally just downloaded phoenix miner unzipped it then ran the gui front end.

Are there any other steps I need to take?

I would pay a bounty if we could get all my cards working.

isaac.mooers@gmail.com for email chat
kingfisherb90 for aim

Quote from: lvlrdka22 on May 29, 2011, 03:38:40 AM

Quote from: Kingfihserb90 on May 29, 2011, 02:56:27 AM

Quote from: PoulGrym on May 29, 2011, 03:10:59 AM

It's an issue with drivers/phoenix I think. Not fixable with GUI.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 29, 2011, 04:23:10 AM

Setting affinity of all instances to one core is coming soon.

Any preferences to start at 0 or 1, for the first core?
I'll have it start at 0 for now, since both Task Manager and Process Explorer start there.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kingfihserb90 on May 29, 2011, 04:26:04 AM

Well I got the miner going with 3 of my 4 cards, but when I enable my 4th card using "screen resolution" in windows.
Note catalyst can see the card as can device manager

I get the following error:
Problem signature:
Problem Event Name:   APPCRASH
Application Name:   phoenix.exe
Application Version:   0.0.0.0
Application Timestamp:   4918019b
Fault Module Name:   StackHash_0a9e
Fault Module Version:   0.0.0.0
Fault Module Timestamp:   00000000
Exception Code:   c0000005
Exception Offset:   72747369
OS Version:   6.1.7600.2.0.0.768.3
Locale ID:   1033
Additional Information 1:   0a9e
Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
Additional Information 3:   0a9e
Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

Kingfisherb90 on aim isaac.mooers@gmail.com on gmail
Will pay 1 btc to solve this error

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kingfihserb90 on May 29, 2011, 04:42:51 AM

Also how do I move the OSD # windows so they arent all on top of each other or to another part of the screen?

When I click the Click Through OSD. it doesn't toggle through them or let me drag them am I doing something wrong?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 29, 2011, 05:26:01 AM

Click and drag them. The last window created (last client running) is set on top, and gets dragged first, then the one below it, then the one below that, etc.
If that doesn't work, click the Click Through button, and repeat the process.
That button toggles the click-throughness of the OSDs, as in, click it, you can click on the OSDs, click again, clicking on OSDs translate to the window below it.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on May 29, 2011, 05:51:13 AM

Hi! I tried your GUI Miner and the only thing I can't seem to get working is the CliCk through OSD. When I click that nothing shows up. And btw, my card is running but only at 80%. I have a 6850 which runs perfectly with the Phoenix Miner @ 263 Mhash/sec @1000/300 1.155v. Maybe you could check? Thanks!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 29, 2011, 07:11:17 AM

It should automatically pop up when you hit the Run button, one OSD for each client.
If you've never moved them, they should be on the top left of the screen.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kingfihserb90 on May 29, 2011, 07:15:19 AM

Quote from: lvlrdka22 on May 29, 2011, 07:11:17 AM

It should automatically pop up when you hit the Run button, one OSD for each client.
If you've never moved them, they should be on the top left of the screen.

Yup, but as many times as I click the click through button it always lets me click through and not drag. I am hitting the click through button and dragging the icon underneath each time rather then the OSD window.

Also any idea about why the miner crashes when I enable my 4th card?

I get this error:
Problem signature:
Problem Event Name:   APPCRASH
Application Name:   phoenix.exe
Application Version:   0.0.0.0
Application Timestamp:   4918019b
Fault Module Name:   StackHash_0a9e
Fault Module Version:   0.0.0.0
Fault Module Timestamp:   00000000
Exception Code:   c0000005
Exception Offset:   72747369
OS Version:   6.1.7600.2.0.0.768.3
Locale ID:   1033
Additional Information 1:   0a9e
Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
Additional Information 3:   0a9e
Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 29, 2011, 07:54:38 AM

Hm, what OS are you using?
The crash doesn't seem related to the GUI at all, can't help there.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kluge on May 29, 2011, 09:17:42 AM

Am I missing something really obvious? Upon hitting "run" button:

"AutoIt Error
Line 4946 (...PR 1.22.exe):

Error: Array variable has incorrect number of subscripts or subscript dimension range exceeded."

Win7 x64, 2 5850s non-CFX w/dummy plug, ran as admin, using phoenix 1.48 and phatk (disabling phatk kernal [which is installed] does nothing helpful), Catalyst 11.5, trying to use btcmine.com. Same error when starting either card after switching all options on or off. It does successfully start up an instance of Phoenix (which becomes hidden -- there is no OSD popup), but only uses 73-75% GPU resources with aggression @ 12.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 29, 2011, 09:48:18 AM

I'm guessing it's because I didn't add a delay between execution of phoenix.exe and setting its affinity.
Try this: http://www.mediafire.com/?wb8a1df8mf0i6a0

If that doesn't work and you don't mind, install autoit with SciTE. Open the source with it (the .au3 file), hit F5. The client should run. Then start mining. It will show correctly where the error is occurring.

Off to sleep.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kluge on May 29, 2011, 10:05:56 AM

Quote from: lvlrdka22 on May 29, 2011, 09:48:18 AM

Thank you for your response. I get a similar message with the new file.

From SciTE:
C:\Phoenix\Phoenix Rising 1.22.au3 (167) : ==> Array variable has incorrect number of subscripts or subscript dimension range exceeded.:
$timer[$i]=0
^ ERROR
Traceback (most recent call last):
File "phoenix.py", line 123, in <module>
File "Miner.pyc", line 79, in start
File "ConsoleLogger.pyc", line 144, in log
File "ConsoleLogger.pyc", line 135, in say
IOError: [Errno 22] Invalid argument
->06:01:11 AutoIT3.exe ended.rc:1

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kluge on May 29, 2011, 10:21:52 AM

For problem of cards running @ 60-80%, enabling fastloop appears to solve it (for me, anyway).

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: bcpokey on May 29, 2011, 11:42:50 AM

Is it possible to use this tool set up a backup pool? That is to say run your cards to mine for pool A, but if pool A goes down to switch to pool B until pool A goes back up?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: happyland on May 29, 2011, 12:35:25 PM

It would be great to have a field to set worksize

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 29, 2011, 03:45:59 PM

Quote from: Kluge on May 29, 2011, 10:05:56 AM

Thank you for your response. I get a similar message with the new file.

From SciTE:
C:\Phoenix\Phoenix Rising 1.22.au3 (167) : ==> Array variable has incorrect number of subscripts or subscript dimension range exceeded.:
$timer[$i]=0
^ ERROR
Traceback (most recent call last):
  File "phoenix.py", line 123, in <module>
  File "Miner.pyc", line 79, in start
  File "ConsoleLogger.pyc", line 144, in log
  File "ConsoleLogger.pyc", line 135, in say
IOError: [Errno 22] Invalid argument
->06:01:11 AutoIT3.exe ended.rc:1

Weird, I'm resizing every variable related to number of clients, including the variable $timer. This shouldn't be happening.

Quote from: Kluge on May 29, 2011, 10:21:52 AM

For problem of cards running @ 60-80%, enabling fastloop appears to solve it (for me, anyway).

Were you able to fix it?
If not, try this: http://www.mediafire.com/?dx9aclhqjevvce2
I had an extra line that set it to a nonarray variable at the beginning of the program for some reason.

Quote from: bcpokey on May 29, 2011, 11:42:50 AM

Is it possible to use this tool set up a backup pool? That is to say run your cards to mine for pool A, but if pool A goes down to switch to pool B until pool A goes back up?

Yeah, if you want to run a back up pool, just set it to lower aggression than the primary pool, and it should work as usual. That's the solution for now.

Quote from: happyland on May 29, 2011, 12:35:25 PM

It would be great to have a field to set worksize

I can add that after I get back.

Anyways, anyone got any ideas on how to detect if a pool is down? I want to exclude the possibility of internet going down.
Well, pinging and telnet don't work, at least on BTC Guild.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: zimpixa on May 29, 2011, 06:21:18 PM

Maybe, if JSON API doesnt respond, means pool is down? But u need to add this first then...

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 29, 2011, 06:37:33 PM

Hm, nslookup? Not very good with this net stuff.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kluge on May 29, 2011, 09:41:05 PM

Quote from: lvlrdka22 on May 29, 2011, 03:45:59 PM

Quote from: Kluge on May 29, 2011, 10:05:56 AM

Weird, I'm resizing every variable related to number of clients, including the variable $timer. This shouldn't be happening.

Quote from: Kluge on May 29, 2011, 10:21:52 AM

For problem of cards running @ 60-80%, enabling fastloop appears to solve it (for me, anyway).

Were you able to fix it?
If not, try this: http://www.mediafire.com/?dx9aclhqjevvce2

I ended up removing a chunk of code and rebuilding to get it to run properly. I'll try again with your new file in a few hours when I have time and get back with you on the results. Thanks very much for this program, btw - it will save me a lot of time from how I normally get my miners up and running.

P.S. Just solved my first block using your GUI, btw :)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: hollajandro on May 30, 2011, 12:10:48 AM

I tried with your linked 1.23 fixed version and I still get this error:

Phoenix Rising 1.23.au3 (166) : ==> Array variable has incorrect number of subscripts or subscript dimension range exceeded.:
$timer[$i]=0

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: kakobrekla on May 30, 2011, 12:30:01 AM

Same here.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 30, 2011, 01:03:46 AM

Quote from: Kluge on May 29, 2011, 09:41:05 PM

Heh nice!

Quote from: hollajandro on May 30, 2011, 12:10:48 AM

Quote from: kakobrekla on May 30, 2011, 12:30:01 AM

Same here.

Sorry, got forced into attending some boring event for 6 hours http://www.blizzhackers.cc/images/smilies/icon_facepalm.gif. At least I thought about how to make it have a backup pool.
Try this: http://www.mediafire.com/?354wqiqny5rpmqz

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: kakobrekla on May 30, 2011, 01:17:57 AM

Hmm, i dunno, it seems like its running or is it not (im not sure). The gpu goes to 70% usage and stays there. I can't see hashrate or anything changing...

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 30, 2011, 01:44:37 AM

Quote from: kakobrekla on May 30, 2011, 01:17:57 AM

Hmm, i dunno, it seems like its running or is it not (im not sure). The gpu goes to 70% usage and stays there. I can't see hashrate or anything changing...

Is it crashing anymore from that array out of bounds thing?
By the way, OS? Seems like some people have problems with the OSD showing, not sure why.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Nythain on May 30, 2011, 01:49:50 AM

Future idea... option to change -q

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: kakobrekla on May 30, 2011, 01:56:59 AM

Quote from: lvlrdka22 on May 30, 2011, 01:44:37 AM

Quote from: kakobrekla on May 30, 2011, 01:17:57 AM

Hmm, i dunno, it seems like its running or is it not (im not sure). The gpu goes to 70% usage and stays there. I can't see hashrate or anything changing...

Is it crashing anymore from that array out of bounds thing?
By the way, OS? Seems like some people have problems with the OSD showing, not sure why.

Sorry, looks like its working fine now [I have missed the display of statistic since is so 'transparent'] :)

Im onlly getting 150mhash right now, instead of 210. Need to check the settings.

Edit: Ok, got it set now...

guiminer: 210mhash (-v -w128 -f0)
phoenix rising: 207mhash (lost the config and cant redo the result) :(

2.4sdk, 5770 @ 1000mhz/300mhz

Right now, anything I do - GPU usage is stuck at 82-84%.

How do i change worksize unit? (With 300 mem clock I get better speeds with worksize unit 128 than 256 (default for 2.4 SDK))

http://smpake.com/data/img/5770mem.png (http://smpake.com/data/img/5770mem.png)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: RedLine888 on May 30, 2011, 04:46:42 AM

Thanks for this piece of software but whet I tried to use it for the 1st time I got this:

http://img683.imageshack.us/img683/3889/errortto.jpg

WTF?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 30, 2011, 05:31:51 AM

Quote from: kakobrekla on May 30, 2011, 01:56:59 AM

Quote from: lvlrdka22 on May 30, 2011, 01:44:37 AM

Quote from: kakobrekla on May 30, 2011, 01:17:57 AM

Hmm, i dunno, it seems like its running or is it not (im not sure). The gpu goes to 70% usage and stays there. I can't see hashrate or anything changing...

Is it crashing anymore from that array out of bounds thing?
By the way, OS? Seems like some people have problems with the OSD showing, not sure why.

I'm adding worksize in the next version. Right now it's fixed at 128.
Have you tried using fastloop? Heard that it increased speed a bit for someone.

Quote from: RedLine888 on May 30, 2011, 04:46:42 AM

Thanks for this piece of software but whet I tried to use it for the 1st time I got this:

http://img683.imageshack.us/img683/3889/errortto.jpg

WTF?

Yeah, forgot to update the first post with the fixed version (it's a few posts above).

New version coming either tonight or tomorrow.
New GUI sample: http://i56.tinypic.com/mb0g34.png

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: kakobrekla on May 30, 2011, 01:16:38 PM

Hey,

ill play with the settings some more today.

Btw, what about 'VECTORS' and other switches? Maybe it would be better to have just one 'extra flags' field, so the GUI is independent from possible future phoenix changes/additions.

Regards

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Tukotih on May 30, 2011, 05:41:01 PM

Quote from: kakobrekla on May 30, 2011, 01:16:38 PM

Yeah, VECTORS and BFI_INT.
I thought they would be included in the HD58XX+ or whatever checkbox but when i put in VECTORS and BFI_INT after my specified aggression value my Mh/s got alot higher.
But not nearly as fast as the standalone phoenix (300Mh/s vs 345Mh/s, a 5850 clocked @ 875/300).

But now I get the strange subscript error that many gets so I've left your Phoenix GUI for now.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 30, 2011, 09:25:23 PM

Quote from: kakobrekla on May 30, 2011, 01:16:38 PM

Vectors is already included. I suppose I should do that flags field thing instead.

Quote from: Tukotih on May 30, 2011, 05:41:01 PM

Quote from: kakobrekla on May 30, 2011, 01:16:38 PM

5xxx+ checkbox is the BFI_INT argument. Not sure why you're getting lower hash rate. I'm getting about the same, about 330 Mhashes/s at 850/340.

I haven't gotten those subscript error for a while, so it can only get fixed when someone else other than me run it with debugging (in SciTE) and tell me where it's occurring.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: zimpixa on May 30, 2011, 09:25:57 PM

Little bug I guess. When Stopping minning, then starting it again idle timer doesnt reseting too. Had to manually add 'platform=1', so it would be mice if u could add it permanently ( means ability to choose which platform)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: V2-V3 on May 30, 2011, 09:29:47 PM

Sweet deal, thank you for the front end GUI!
I have been using Phoenix through command line and its kind of hard to show noobs for the first time :)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: zimpixa on May 30, 2011, 09:51:41 PM

Other bug. When using login zimpixa.CPU it stays idle, after registering new worker zimpixa.zimplap it goes normal

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 30, 2011, 10:07:57 PM

Quote from: zimpixa on May 30, 2011, 09:25:57 PM

Figured it out, apparently I was incrementing the same variable in a function that has that variable in it as argument http://www.blizzhackers.cc/images/smilies/icon_facepalm.gif http://www.blizzhackers.cc/images/smilies/icon_facepalm.gif http://www.blizzhackers.cc/images/smilies/icon_facepalm.gif http://www.blizzhackers.cc/images/smilies/icon_facepalm.gif http://www.blizzhackers.cc/images/smilies/icon_facepalm.gif (x1000).
What do you mean by platform=1?

Uploading the fix soon. Also disabled the affinity thing, in case of only 1 core.

Quote from: zimpixa on May 30, 2011, 09:51:41 PM

Other bug. When using login zimpixa.CPU it stays idle, after registering new worker zimpixa.zimplap it goes normal

Er, I'm sorry? I don't get what you mean by that.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: zimpixa on May 30, 2011, 10:27:39 PM

By platform flag I mean multiple SDK's installed on one rig. U ask why?
SDK 2.1 poclbm - 395 MHash
SDK 2.4 phoenix - 393 MHash
Depends on time and pool (with some phoenix creates little too many stales) I'm using various SDK's, various platforms.

By my second post I mean that Im idiot... Forgot to change password of worker... Found it just now.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 30, 2011, 10:37:39 PM

Quote from: zimpixa on May 30, 2011, 10:27:39 PM

Oh, I'll just add an "extra flags" field.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: zimpixa on May 30, 2011, 10:45:49 PM

Also consider renaming HD 5XXX to just BFI_INF

Any chance u'd do similar tool for poclbm?

Also any chance to ability to display Hashrate as OSD (consumes much CPU on higher aggression for me) or somewhere in GUI window?

EDIT:

Maybe just instead of restarting miner it should close current one and start backup one if available ( or checkbox whenever switch if idle or restart). Then after specified time return to check if its working.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: kynalvarus on May 31, 2011, 12:15:17 AM

I've been trying out the 1.3a beta. It's about 3% slower on my Radeon HD 6870 with the same settings than running phoenix directly, but I'm not sure why. Also, it seems to go to sleep when my PC is running the screen saver. My reported hashrate from the server drops way down, and when I come back from screensaver the OSD reads "Restarting...". It's possible that the underlying phoenix bug is biting me. Perhaps the GUI doesn't properly detect idleness when the screensaver is running?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 31, 2011, 12:50:41 AM

Try 1.3b, I fixed a couple unintended bugs.
If you're using multiple graphics cards, it could be setting affinity all to the same core (if you used that), which could result in a little loss of performance.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: bcpokey on May 31, 2011, 02:29:05 AM

Trying out the client now, so far I like it, the affinity setting is something I really like, and the backup option was just what I was looking for. One thing though is the OSD is always click-through for me no matter if I hit the button or try to alt-tab to the window or anything. I saw someone else had this problem but I didn't see any resolution, has anyone come up with anything for this?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 31, 2011, 03:23:13 AM

Try this, see if it's fixed: http://www.mediafire.com/?3oup7h2d6dtenbq

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on May 31, 2011, 03:25:31 AM

Finally I was able to show the OSD, it was on the upper left corner of the desktop and I just moved it before clicking "Click Through" to lock it's position. So far working good! Thanks for this GUI! The restart option is very handy indeed! I will be testing it with a dual card system. Have just tested it with a single card. I get the same Mhash/sec with the console version. :)

P.S.
Would there be a way to change the font color to like Green or White or Black or something? The red font is kind of hard to view ;). I know I may be asking too much but it would greatly help.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kingfihserb90 on May 31, 2011, 03:36:17 AM

Quote from: lvlrdka22 on May 29, 2011, 07:54:38 AM

Hm, what OS are you using?
The crash doesn't seem related to the GUI at all, can't help there.

I am using windows 7 64 bit, with SP

I have 3 dummy plugged cards into x1 slots, crossfire connected.

I have tried 11.3 11.4 and 11.5 catalyst.

Speaking of catalyst my crossfire option has disappeared from the performance menu.

Windows 7 sees the 4th card as does catalyst when I "extend the desktop" if I don't do that neither can see the card.

However when I try to run guimier.exe or a 4th miner in phoenix rising I get that crash.
I also get the crash when i run poclbm.py in command line and I have the 4rd card extended.

I will pay a bounty to whoever figures out how to make my 4th card usable.

Kingfisherb90 on aim
isaac.mooers@gmail.com for ghat email.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 31, 2011, 03:36:57 AM

Quote from: huayra.agera on May 31, 2011, 03:25:31 AM

Sure, it's an easy change:
Go to line 51 in the source, should read "$pen=_gdiplus_pencreate(0xffed1c24,2)"
Change the 0xffed1c24 to an RGB color you want.
Recompile!

I might include an option to select one of the common colors.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on May 31, 2011, 04:05:56 AM

Quote from: lvlrdka22 on May 31, 2011, 03:36:57 AM

Quote from: huayra.agera on May 31, 2011, 03:25:31 AM

I'm no programmer, thus I'll be waiting patiently for your update. Thanks!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Aprogas on May 31, 2011, 12:52:20 PM

It seems phoenix.exe is launched with incorrect parameters (i.e. lacking a space) when fastloop is disabled. In Process Explorer on phoenix.exe (Properties > Image):
phoenix -u http://user:pass@bitcoinpool.com:8332 -k poclbm VECTORS BFI_INT FASTLOOP=falseAGGRESSION=7 DEVICE=0 WORKSIZE=512 -q 2
This probably causes both the fastloop and aggression settings to not be parsed. For some reason when launching like this (also when launched manually in a command-prompt), on my system the miner only uses up to 82% GPU and thus a lower hashrate.

Tested on: Phoenix Rising 1.3c
Hardware: Radeon HD 6850
Workaround: enable fastloop

EDIT:
On second inspection it seems that FASTLOOP=false is still parsed even if another argument is directly attached to it, so only the aggression argument is ignored. Apparently my card needs fastloop to run at full-speed, so I should have just enabled it in the first place.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: patica on May 31, 2011, 03:58:56 PM

Hi, 10x for the good program. There is no drop in hashrate for me.
But if how, I would like to see an option for autostart the worker. Now if the PC reset accidentally, there's no way to resume mining.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: RedLine888 on May 31, 2011, 05:14:10 PM

Hi! Help me please to run your piece of software!

It seems to me that I fill in all the forms correctly but when I click START OSD appears saying that miner is idle than it automatically restarts in 10 secs and the procedure repeats again. The GUI is user-friendly and everything should be clear but I am obviously missing something.

Can you please post a how-to guide with some examples.

Thanks!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 31, 2011, 05:36:34 PM

Quote from: Aprogas on May 31, 2011, 12:52:20 PM

Yeah, apparently I missed a space after FASTLOOP=false :-\.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on May 31, 2011, 07:27:07 PM

1.3!
Backup pool should be functional now. Uses ping to check for online/offline.
Added some preset colors for the OSD.
Replaced work size field with extra flags.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Peao on May 31, 2011, 11:28:14 PM

Great job, lvlrdka22!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 01, 2011, 02:15:45 AM

:D Thanks.
Let me know if anyone thinks of a better way to check if servers are online, or if there are any bugs!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on June 01, 2011, 05:40:22 AM

Nice job! By the way, I think it's a good idea if when the original server is back online, Phoenix Rising would revert to the original server from the backup. Testing now! :)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 01, 2011, 06:17:14 AM

Heh, it does!
There's a field for that ;).
It checks every time timer reaches that length, and every time backup client restarts.
I tested by unplugging my LAN cable, then plugging it back in. Should work, provided ping is good enough to tell if a server is online or not.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on June 01, 2011, 06:20:36 AM

Ha! I overlooked, didn't read the fine text. I just registered with BTC Guild as you have mentioned on how we can say thanks. :)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 01, 2011, 06:22:26 AM

:D Thanks!
Maybe if there are no more bugs, I can rest for a bit now.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: vborets on June 01, 2011, 07:44:56 AM

Thanks for job!

But 1.3c not work at all ???

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 01, 2011, 07:57:03 AM

Oops, I failed.
Forgot to remove the 1.3c link.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Chef on June 01, 2011, 11:35:16 AM

I cannot connect to mediafire at all right now. Any chance to get a file mirror?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Peao on June 01, 2011, 11:40:57 AM

How about an address for donations? ;)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: tiberiandusk on June 01, 2011, 01:19:48 PM

Works great! Nice to be able to get rid of all the command line windows cluttering up my taskbar. Only thing I noticed is all the OSD colors are hard to read except the white one.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: mattpker on June 01, 2011, 04:32:11 PM

Wow! This GUI is awesome. I love the On-Screen display. Thank you so much!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: hchc on June 01, 2011, 05:25:49 PM

Great program :)
It would be nice if you could implement auto-start. Currently I can put it in the windows "Startup" folder but I still have to manually click "run"...

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: RedLine888 on June 01, 2011, 05:46:43 PM

I figured out what was wrong everything is working now except for the OSD moving! How to move those things? They do not react when I click on them!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: tiberiandusk on June 01, 2011, 05:51:31 PM

Quote from: RedLine888 on June 01, 2011, 05:46:43 PM

I figured out what was wrong everything is working now except for the OSD moving! How to move those things? They do not react when I click on them!

Make sure you are clicking directly on the txt in the window. If I click anywhere else it just thinks I'm clicking on the desktop.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: RedLine888 on June 01, 2011, 05:53:53 PM

Ohhhh, God! I mooved them! One should click on the 3rd line to move those OSDs

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: RedLine888 on June 01, 2011, 05:54:25 PM

THANX for the advice

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: tiberiandusk on June 01, 2011, 05:55:52 PM

No prob. I had two overlapping each other in the top left corner and it took me a couple minutes to figure it out. :P

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: keybaud on June 01, 2011, 08:36:14 PM

Can anyone help a software noob with instructions on how to compile this for 32 bit Windows?

Ta.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: inQ on June 01, 2011, 09:48:47 PM

32bit compile http://www.mediafire.com/?7guaddci9y1zb3k
works fine :)
thanks to Hollajandro

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: zimpixa on June 01, 2011, 10:21:54 PM

To compile!:
Download AutoIt
During installation check 'edit script'
Open the script
Tools>compile
It will compile to OS u are currently on.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Vwlopez3 on June 02, 2011, 12:40:41 AM

Quote from: hchc on June 01, 2011, 05:25:49 PM

Great program :)
It would be nice if you could implement auto-start. Currently I can put it in the windows "Startup" folder but I still have to manually click "run"...

I agree but great program all the way around switched over from GUIminer and am very pleased. I like the more industrial feel of it much more thought out and great software. Thanks

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: tiberiandusk on June 02, 2011, 07:12:10 AM

When this gets autostart mining it will be perfect. I love how easy it is to lock the processes to a core.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kluge on June 02, 2011, 07:37:00 AM

Quote from: tiberiandusk on June 02, 2011, 07:12:10 AM

When this gets autostart mining it will be perfect. I love how easy it is to lock the processes to a core.

+1. I have the problem where miners insist on taking up 100% of a core and can't seem to fix it with driver upgrades/downgrades, producing unnecessary heat and consuming costly electricity, so (after downclocking/downvolting the CPU via BIOS) being able to just start them off on one core instead of starting task manager and manually switching affinity of both programs saves me a lot of time.

After autostart feature is added, I just need to figure out a way to auto-restart my miners when the graphics drivers fail and can't restart. Ambient temperature varies up to 40*F day-to-day which causes hassles trying to volt/clock my GPUs as high as possible without crashing.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 03, 2011, 04:06:12 AM

Found a tiny bug that wasn't loading the OSD color from ini file correctly.
I'll update that along with an autostart option when I get around to it.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: tiberiandusk on June 03, 2011, 05:27:06 AM

Thank you for this awesome program and all the work it took to put it together.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Internet151 on June 03, 2011, 06:46:04 AM

Is there any way to hide the On Screen Display (OSD)?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kotty on June 03, 2011, 02:17:58 PM

Hi,

i've running the phoenix rising and watched into the processlist and the miner is started like this:

phoenix -u http://user:password@host:8337 -k poclbm VECTORS BFI_INT FASTLOOP=false AGGRESSION=12 DEVICE=0 -k phatk

why are there 2 kernels given? There should be only one kernel i think.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 03, 2011, 07:40:43 PM

Unintended, but apparently loads phatk kernel correctly anyways. I'll add that to 1.31.
Oh, and removed VECTORS from the must-load argument list. If you want to use it, just add that to Extra Flags field.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 03, 2011, 08:09:28 PM

1.31 up!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dhmcman on June 04, 2011, 01:50:57 AM

Fantastic program and I love the idea and that this restarts its self.

But i am having issues getting it to work. I have been playing around with the options and all it does is show a timer to restart. I have it in the same folder that i run Phoenix from. Ive tried the 1.23, 1.3, and 1.31 versions. Ive read this entire thread and checked all the link it and i cant figure out why it is not working

I'm running a single 5830 on win7 and
phoenix -u http://****@*****/ -k phatk DEVICE=0 AGGRESSION=10 VECTORS BFI_INT
when i run this i get around 300Mh/s.

any help that anyone can offer will be great.

Thanks.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: tiberiandusk on June 04, 2011, 08:04:17 AM

I switched to 1.31 and my hashrate for my 5870 went from 445 Mhash/s to 395 Mhash/s and my 5850 went from 342 Mhash/s to 320 Mhash/s with no settings changed. If I launch 1.3 it still runs at the original speed.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: zimpixa on June 04, 2011, 09:12:23 AM

@ up

Have you added VECTORS to extra flags field in 1.31?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Peao on June 04, 2011, 01:41:40 PM

I have to use argument "-q 3". It works if I put it in the "extra flags?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: hiVe on June 04, 2011, 03:57:52 PM

I've tried a lot of things. But whenever i start it, a cmd window pops up and disappears immediately, afterwards nothing happens. I wonder what am I doing incorrectly -.-

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: zimpixa on June 04, 2011, 04:57:52 PM

@ PEAO
Yes, it will work.

@hiVe

1. check if u entered correct login and password
2. make sure u put rising phoenix in phoenix miner folder
3. make sure u entered correct platform in extra flag field (if u are using multiple platform ofc)
If none of this happened please upload here screen with your settings so maybe I'll find that mistake (also specify your rig (OS,SDK,GPU)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: hiVe on June 04, 2011, 07:43:45 PM

Quote from: zimpixa on June 04, 2011, 04:57:52 PM

Yea, all is correct, but f*ck it doesn't work, thanks for the attempt to help me though.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 04, 2011, 07:45:45 PM

Quote from: tiberiandusk on June 04, 2011, 08:04:17 AM

I removed vectors from the must-load argument list, so you'll have to add that in Extra Flags.

Hm.
1.32: I have added an extra option under Affinity to pick a random core to use (that still makes every instance run on the same core, except it's randomized, as in, once every client stops, it repicks a core to run on).
Thinking about an AMD/ATI GPU monitor (can't figure out how to use ADL dll, so using a different one) that stops client once temperature reaches a certain point, and starts client again once it drops below a certain point.
Right now, I have it as an external script controlling Phoenix Rising, seems to work well.
In progress.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 05, 2011, 05:56:06 AM

^
|

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 05, 2011, 07:41:58 AM

I need some feedback on how well my temperature monitor is working (AMD/ATI GPUs only).
http://www.mediafire.com/?oyd7tj6ezvebaiz
Does it list both the slot the GPUs are plugged in and the temperature correctly?
Also, is Device 0 the one in first slot, Device 1 the GPU in the next-filled slot, etc.?
What I mean is, for example, I'm using slot 0 and 3, and Device 0 is the one in slot 0, Device 1 is the one in slot 3. Is the Device Number always incremented like that?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: namley on June 05, 2011, 07:43:19 AM

You just made my day!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kluge on June 05, 2011, 09:08:51 AM

Maybe not worth your time, but it would be nice to have an "export" feature where it writes up a .txt file giving the full line going to the cmd window when running Phoenix for debugging purposes.

I'm having trouble getting Phoenix to run using PR on a particular computer I'm running and can't figure out why. Since all I get is a blank command window and "xx seconds idle | xx seconds until restart" I'm having difficulty debugging it myself because I don't know exactly what Phoenix is being fed.

Edit: Found my problem -- I didn't capitalize a particular letter in password field :x

Edit2: And I'm using the 32-bit client :p

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 05, 2011, 09:35:28 AM

I can do that. Try this: http://www.mediafire.com/?d2wtoj47ufcgzwv

Oh, still need people to test out that separate script I wrote. Need to see if Device Number directly corresponds to which GPUs are in the top slots, as in, if Device 0 is the one in first slot, Device 1 the GPU in the next-filled slot, etc.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: MaSell on June 05, 2011, 11:14:46 AM

Any chance to hide OSD?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Chef on June 05, 2011, 01:59:24 PM

Just a quick bug report:

The backup pool feature seems to work nicely on 1.3 and 1.31. The get back to primary-pool feature however does not. I waited for over an hour now (it's set to 2 minutes), but i had to restart the worker to get it back to the original pool.

Anyways, thanks for the tool, it helps my uptime quite a lot!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 05, 2011, 03:05:20 PM

EXCELLENT

Nice GUI, only thing needed is tabbed interface.
I directly tried with 1.32, just for the past 30 minutes, giving correct values & its running with out me for past 5 minutes.
I see shadow behind OSD, causing letters to look double, instead of sharp, even after trying clear type in windows, that i can say bug now.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 05, 2011, 04:32:54 PM

Quote from: Peao on June 05, 2011, 11:35:04 AM

Quote from: lvlrdka22 on June 05, 2011, 07:41:58 AM

Tested in 3 rigs:

1x 6990 - ok - 2 devices detected - Device 0 and 1 worked properly;
1x 5970 - just onde device detected - Device 0
2x 5970 - just 2 devices detected - Device 0 and 3

Hm, mind trying this with the 5970s?
http://www.mediafire.com/?6fwbxckivpohml2

Quote from: Chef on June 05, 2011, 01:59:24 PM

It tries to tell using ping. If main server isn't pingable and is idling, it switches to backup until the primary becomes pingable again.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 05, 2011, 06:39:25 PM

Im noticing a bug where the miner doesnt always restart. it Just hangs with a blank command line window open and its stay hung until i close the window the the miner restarts. any body else seen this? i tested on 10 machines and 8 had the bug with in 8 hrs

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dikidera on June 05, 2011, 06:41:45 PM

So what are the good and bad parts about this program?

+GUI

-An OSD that stays in the top right corner of my screen without the ability to move it.
-The OSD stays on top of EVERY program.
-The OSD has barely visible words(impossible to read the text at all)
-Small fields when entering arguments
-Checkbox for phatk, but not for vectors and BFI_INT

Basically, although i appreciate the try, you should've tried harder.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 05, 2011, 06:50:26 PM

Quote from: dikidera on June 05, 2011, 06:41:45 PM

Yes, it can be moved. You aren't doing it correctly.
That's exactly what OSD means.
You can change colors of the text.
What?
Vectors, put in to Extra Fields, it's in the instructions. BFI_INT=5xxx+.

Basically, if you can't be bothered with figuring out how to use, don't use it.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dikidera on June 05, 2011, 06:53:56 PM

Then make the fields bigger lol. I am not some ant to try and read that. Also, why write 5Xxx+?? Just write BFI_INT so there are no misunderstandings then.
And also, if it stays on top of every program(the osd) then how the hell can i watch a movie without that thing??

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 05, 2011, 06:58:06 PM

Quote from: dikidera on June 05, 2011, 06:53:56 PM

Is that your complaint about GUIMiner as well? They're the same size.
5xxx+ because not everyone understand what BFI_INT means. And I did say that they're the same thing on the first post. Do you just hit "Download" and double click when finished?
Drag it off screen then.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 05, 2011, 06:59:48 PM

The OSD position can't be saved. Restart of phoenix rising causes OSD go back to top left corner & also OSD gets messed by displaying each card details in same place. I have 3 cards mining & all 3 at same place.

I also found a problem in version 1.32.
It just says restarting after phoenix crash in a cmd window but can't able to restart.
only way to restart, is to close that window manually & it automatically restarts miner then.
This problem is not with 1.31. In 1.31, it displays restarting & restarts in less than 10-20 seconds.

OSD overlapping & not saving last position is in both 1.31 & 1.32

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 05, 2011, 07:02:21 PM

Its been a bug since the very first version. only hiccup about the miner other than that it would be flawlessly functional...the asthetics (osd text size)..who cares just need it to mine without me hovering over it

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Peao on June 05, 2011, 07:08:54 PM

Quote from: FRanz33 on June 05, 2011, 06:39:25 PM

Same here. But not in 80% of the miners, like FRanz33.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 05, 2011, 07:09:14 PM

Quote from: FRanz33 on June 05, 2011, 06:39:25 PM

I too have same problem in 1.32

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 05, 2011, 07:14:12 PM

Quote from: lvlrdka22 on June 05, 2011, 07:41:58 AM

It displays wrongly. I have 3 cards in pcie_1, pcie_2 & pcie_3 slot thats Device 0,1 & 2, but temperature monitor shows as Device 0 temperature, Device 3 temperature & Device 6 temperature.
Only device number is wrong. But shows temperature correctly for each device.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 05, 2011, 08:35:20 PM

About the restart bug thing, try this: http://www.mediafire.com/?yy43ik6nr58a85t

Quote from: dishwara on June 05, 2011, 07:14:12 PM

Quote from: lvlrdka22 on June 05, 2011, 07:41:58 AM

Does it at least list the device numbers' order correctly? As in, Device 0 is Device 0 on the monitor, Device 1 is 3 on monitor, 2 is 6, etc.

Quote from: Peao on June 05, 2011, 07:16:38 PM

Quote from: lvlrdka22 on June 05, 2011, 04:32:54 PM

Quote from: Peao on June 05, 2011, 11:35:04 AM

Quote from: lvlrdka22 on June 05, 2011, 07:41:58 AM

Tested in 3 rigs:

1x 6990 - ok - 2 devices detected - Device 0 and 1 worked properly;
1x 5970 - just onde device detected - Device 0
2x 5970 - just 2 devices detected - Device 0 and 3

Hm, mind trying this with the 5970s?
http://www.mediafire.com/?6fwbxckivpohml2

Same result, lvlrdka22.

Bleh.
By the way, does the 5970 happen to only show 1 temperature for both cores?
The 6990 shows 2 temperatures, 1 per core, right?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dikidera on June 05, 2011, 08:38:38 PM

Quote from: lvlrdka22 on June 05, 2011, 06:58:06 PM

Quote from: dikidera on June 05, 2011, 06:53:56 PM

Most of the time.

Guiminer unlike this one has very readable text, and phoenixminer is coming for the phoenix which should allow even smoother mining. My advice is to add the speed on the gui itself.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Peao on June 05, 2011, 08:39:55 PM

I do not know, but is it essential to your plans to have the temperature information of the two GPUs?
Perhaps one measure is enough, because the card is the same and there is no big difference between the temperature of the two processors of a 5970 ...

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 05, 2011, 09:03:16 PM

Quote from: Peao on June 05, 2011, 08:46:30 PM

Quote

Bleh.
By the way, does the 5970 happen to only show 1 temperature for both cores?
The 6990 shows 2 temperatures, 1 per core, right?

5970 - 1 temp. But I do not know if it is the average of the two cores or it's the temperature of just one core.
6990 - yes - 2 temps, 1 per core.

Hm, do you happen to have GPUZ/Afterburner? They should list 2 GPUs for the 5970. If you just mine on one core, do they show different temperatures for the cores?

Quote from: Peao on June 05, 2011, 08:39:55 PM

There should be though, if you mine on 1 core and play games/idle on another, which is what I'm trying to avoid :-[ (mining on one core with a preset shutdown temperature, but the monitor reads temperature for the "idle" core).
Does this list two temperatures for the 5970? http://www.mediafire.com/?2rdbd97anpia8iw
Ignore the 10 devices thing, I'm having it list everything.
If not, I give up for now and probably will just throw a hacky fix that forces people to find out which "slot" each of the devices are on.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 05, 2011, 09:13:52 PM

Afterburner i am using to read temp now.

The order of device number is also different.
GPU1 temp in Afterburner = Device 6 temp
GPU2 temp in Afterburner = Device 0 temp
GPU3 temp in Afterburner = Device 3 temp

http://i56.tinypic.com/257175w.jpg

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 05, 2011, 09:29:05 PM

Quote from: dishwara on June 05, 2011, 09:13:52 PM

http://serve.mysmiley.net/mad/mad0177.gif

Quote from: Peao on June 05, 2011, 09:21:18 PM

Still the same results in both rigs... :(

1x5970 just device 0
2x5970 devices 0 and 3

If you don't mind, can you mine on one core and have the other core sitting idle for the 5970, and monitor temperatures using Afterburner or GPUZ (open 2 instances of it, the drop down menu on the bottom left should list 2 5900 series, one for each core)? Do they show different temperatures?

Because of dishwara, I think I'll have to have the user figure out which device is which GPU with an external script :'(.

By the way, did this fix the restart bug?

Quote from: lvlrdka22 on June 05, 2011, 08:35:20 PM

About the restart bug thing, try this: http://www.mediafire.com/?yy43ik6nr58a85t

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Peao on June 05, 2011, 09:49:38 PM

Hmm, was a little difficult, because even with only one core working, the temperature of the stopped core closely followed the temperature of the core that was @ 100%.
But I saw that appear different temperatures for each core (about 2 Celsius), and "Device Finder" catch one of them.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 05, 2011, 10:19:15 PM

I suppose that'll be enough as a temporary solution :-\.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 06, 2011, 12:10:55 AM

Nope it didnt. tried it on two machines with two 6970's in each. just checked one box was going the other hung up

EDIT: if your having trouble reproducing the bug just hit stop on the console and alot of time the box will pop up and sometimes itll just stay there and hang. its something to do with how phoenix process is shut down

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 06, 2011, 12:39:49 AM

Hm, try this (temperature monitor is still not implemented yet, ignore it for now): http://www.mediafire.com/?u1tmtamjekr8b9a
DO NOT USE THE 64-BIT. It doesn't kill phoenix processes correctly.
Switched from using ctrl+break to directly killing the process. Should not have the hanging bug anymore. Let me know if there are any side effects.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 06, 2011, 12:43:16 AM

OK will try. ur pretty quick on this man

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 06, 2011, 12:56:21 AM

ooo yea that kill is much cleaner than the last version...lets see how it does overnight

Edit: nope. Now when i hit the stop button it doesn't kill the process it just run in background. I dont know if it affects the auto restart but the manual stop and start is botched now. i have to go into task man. to kill it myself

Editx2: i can now confirm even on restart the process doent kill at all.. ever 30 sec another phoenix instance and piles up until computer crashes. take this version down asap

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 06, 2011, 01:13:35 AM

Maybe theres away to just kill phoenix then kill the window that pops up automatically?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 06, 2011, 01:21:02 AM

NEVERMIND, apparently the new kill process function I stole has broken compatibility with 64-bit.
From now on, only 32-bit binaries :'(.
Besides, AMD's DLLs for monitoring GPU temperature is 32-bit.

If the hang is finally fixed, I might be able to get temperature monitoring up (but that requires a bit of extra work on the user side, to figure out which devices are which).

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 06, 2011, 01:57:42 AM

Quote from: lvlrdka22 on June 06, 2011, 01:21:02 AM

ur right. 32bit works...im going to try all my unit tonight. Ill report back in the morning

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 06, 2011, 04:21:37 AM

I tired with 1.32 new now for hang testing.
I killed one phoenix.exe in task manager & it was restarted correctly, but with 4-5 retries of showing cmd windows restarting.
I did it only one time, so not sure.

Besides, yesterday night, i got strange problem.
I used 1.32 which u gave before, i never used your GUI, actually i was not aware a GUI for phoenix with phatk exists.
1.32 gave restart hang. So, i tried with 1.31 & at the same time i updated windows 7 32 bit to sp1.
After installing sp1, even 1.31 gave hang problem. So i uninstalled sp1 & then 1.31 worked fine by correctly restarting.

I think the new sp1 interfering with PR.
So, ask others also to uninstall sp1, if they have upgraded to sp1 & try with 1.32

EDIT:

Just know one miner crashed itself & after 4-5 restarts it restarted.
But it seems miner crashes itself with new version.
Within 10 minutes, 2 miners crashed.

So going back to 1.31 as my SH won't happy if i mine less.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 06, 2011, 05:12:35 AM

Quote from: dishwara on June 06, 2011, 04:21:37 AM

Did you try the 32-bit in this version? I've had it running for 4 hours now, no hangs so far. Only a few restarts, but that's because of my flaky net (need to replace router and modem).
Only one rig, and using only W7 Ultimate with no SP, so can't really test anything for bugs, sorry :-[.

Quote from: lvlrdka22 on June 06, 2011, 12:39:49 AM

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 06, 2011, 06:06:43 AM

I have windows 7 Ultimate, 32 bit only. I tested & ran with this file, Phoenix Rising 1.32 x32.exe.
The other file, Phoenix Rising 1.32.exe, gives me the following error,
"The version of this file is not compatible with the version of Windows you're running. Check your Computer's information..............................."

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 06, 2011, 06:35:25 AM

1.4! Let me know any and all bugs, as usual.

Quote from: dishwara on June 06, 2011, 06:06:43 AM

Did that version above your post still have the hang bug?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 06, 2011, 07:29:10 AM

I ran PR1.4. It does nothing. It says it starts miners by showing cmd windows & closing, but NO PHONEIX.EXE runs in task manager & no OSD & NO MINING AT ALL.
It shows everything as mining , but without mining actually.
Check it. Again going back to 1.31

Please, add tabbed interface SOOOOOOOOON.
With 6 clients, i actually can't able to see last client, due to now added pause, temp....
Only way to see, is to delete last 3 clients which i don't use now from phoenix.ini after taking backup of phoenix.ini.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 06, 2011, 08:18:01 AM

Eh, don't know what to say. I didn't change the launch function at all, and the OSD even shows up on my XP 32-bit laptop with only integrated (along with phoenix, which exits as soon as it launches since it couldn't find a GPU to run on).
I just downloaded from the link to test, works...
Try opening pr.log and check that the launch parameters are correct?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 06, 2011, 09:27:06 AM

Tried again downloading 1.4. Same error, no mining.
Also the pr.log shows everything correctly.
I don't know why not mining at all. hope some one will try & reply.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 06, 2011, 10:11:15 AM

Hm, if you have Process Explorer, mind opening that up, run PR, scroll down so that PR is visible in Process Explorer, and hit run?
Try to see if phoenix is created as a child process (should be a tree under PR.exe). It may disappear quickly, so as soon as you hit run, look on Process Explorer.

Also, try this: http://www.mediafire.com/?3qhx6ke2lpx0g29
All the that changed between the launching process in 1.31 and 1.4 is that I added logging (which I removed in this).

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Peao on June 06, 2011, 11:10:13 AM

Quote from: dishwara on June 06, 2011, 09:27:06 AM

Tried again downloading 1.4. Same error, no mining.
Also the pr.log shows everything correctly.
I don't know why not mining at all. hope some one will try & reply.

Same error here.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 06, 2011, 11:21:46 AM

1.4a also gives same problem.

http://i56.tinypic.com/25qaohv.jpg

1.31 working fine.

http://i53.tinypic.com/dce8mv.jpg

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on June 06, 2011, 12:10:59 PM

Hi! It's been a while since I've started using PR! Just having issues with my ISP's IP addresses being banned from the forum, I had to use proxy servers just to read threads here. =)

I think we should have a feature request, would that be asking a lot? =)
The whole idea is that the only thing that we'll launch is you're GUI.

Here's the list:
1. Temperature display (VRM, Core, Memory) OSD (since you were already able to tap into the temp control)
-addendum: Clock throttling to a certain profile when a temp is reached like for example, at night temps are cold, we could OC to like 911/300 5850 stock volts, but during daytime noontime when temps reach like 85-90C on core, it would throttle down to like 860/300.
2. Overclocking tool (like set the clocks at start/when the Run button is pressed)
3. Fan Speed display
4. GPU Core, Memory, VRM Clocks display
5. Maybe the Withdraw button for pools that support it (Same as with GUIminer)
6. Maybe the Miner Stats reporting (like the Widget) where in we enter the API Json from the pool and we get stats like current exchange rate, pool has rate, miner hash rate, BTC earned, workers, etc.

I would say a lot of us here is going to support you (donations, mine at you're suggested pools, bounty etc.)

We couldn't be even more thankful for all your work. =)

I would happily beta test your app!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 06, 2011, 02:01:24 PM

Quote from: huayra.agera on June 06, 2011, 12:10:59 PM

Most of the things u asked already in Afterburner.
Adding all these things to MINER will make it BLOAT-WARE & can cause severe performance decrease & mining efficiency.
Also, Its always good to use more than one tool, which will give space to work easily.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on June 06, 2011, 02:10:14 PM

It's pretty obvious all my feature request are already in afterburner, but my suggestion was that it would be very efficient if we only launch 1 program to monitor, OC, run the miners, etc. I think they wouldn't be too much bloatware either as they are all useful. How I wish I know how to code but ideas are the least I can contribute. And testing =).

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: LegitBit on June 06, 2011, 02:29:14 PM

So will 64bit binaries return in future versions past 1.4 or has that ship sailed?

I prefer to use 64bit apps, though I know there really isn't any kind of performance gain in this small of a program it still is a peeve of mine.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: rowbot on June 06, 2011, 02:50:25 PM

This is great. But without fail it crashes my entire desktop after about 10-15 minutes.

I have a 5830 running 2.4 SDK @ around 85C. I've tried both the phatk and poclbm kernels, and they both crash.

Independently running phoenix with the same args I have no problems, so I'm not sure what the issue is.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on June 06, 2011, 03:02:01 PM

Quote from: rowbot on June 06, 2011, 02:50:25 PM

I'm running the GUI on 3 machines crossfired and am having no issues. Maybe you can update your flags?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: xanadu on June 06, 2011, 03:03:13 PM

Quote from: lvlrdka22 on May 28, 2011, 01:48:58 AM

Current version 1.4: http://www.mediafire.com/?rw3f1kzgsav3ww7

The mediafire link is failing for me, it connects and says "Click here to start download from Mediafire"

The download never starts, the connection just times out (I've tried both IE and Firefox).

Thanks,
-X

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: xanadu on June 06, 2011, 03:25:32 PM

Quote from: xanadu on June 06, 2011, 03:03:13 PM

Quote from: lvlrdka22 on May 28, 2011, 01:48:58 AM

Current version 1.4: http://www.mediafire.com/?rw3f1kzgsav3ww7

Of course, half an hour later and the link works fine :)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 06, 2011, 05:57:17 PM

I don't know what happened.
But after trying 1.32 & 1.4 & 1.4 a, now even 1.31 crashes every 20-30 minutes.
Also, crash makes program to hang showing restarting cmd window.
Until manually close restarting window, mining is not happening.
I don't know, how i am going to sleep, coz miner may crash & won't mine at all.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 06, 2011, 06:19:31 PM

Quote from: huayra.agera on June 06, 2011, 12:10:59 PM

Eh, only temperature reading is available in the ATI-provided DLL I'm using, can't get ADL working.
I do have an external script that displays all current GPU statistics through GPUZ, but I would rather not release that (argh, need ADL working!).
Overclock tool, I've been thinking about it. Should be relatively simple, as long as I can get ADL working ::).
Most likely no on the Withdraw, since I don't want to ever be accused of stealing/changing bitcoin address :-\ (it'll need complete website log in to withdraw).
I was thinking about using JSON to detect if pool is down, but not too familiar with it.

Quote from: rowbot on June 06, 2011, 02:50:25 PM

This seems familiar. I think there might have been a bug with Catalyst 11.4 and the SDK that came with that, because it would blue screen if I ended phoenix process instead of ctrl+break.
Using 11.4?

Quote from: LegitBit on June 06, 2011, 02:29:14 PM

Yeah, no more 64-bit, since the DLLs are 32-bit :-\.
One of the functions I'm using to kill phoenix processes is also 32-bit only apparently.

For those people that 1.4 refuses to work, try this: http://www.mediafire.com/?qgz988s9ojx7j4n
I copy-pasted the entire phoenix-launching function from 1.4 over. See if this works.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: LegitBit on June 06, 2011, 06:22:14 PM

1.4 Fails to launch the GUI on WIn7 x64 SP1

Weird.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 06, 2011, 06:25:38 PM

I think the problem may be due to saving the settings & working in read only mode.
Since it is read only mode, new features may not be able to save & giving problem.
Have to test with NO read only.
Also, i now removed read only , added a client, removed a client & saved settings again with 1.31, hoping new save will make 1.31 work with out crash.
Also, now running with NO read only.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Internet151 on June 06, 2011, 06:30:36 PM

It would be nice if Phoenix Rising could show some more statistics, like how many times it's gotten work queue is empty from x pool, how many times it's been disconnected and reconnected from x pool, etc.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: hollajandro on June 06, 2011, 06:47:58 PM

Quote from: lvlrdka22 on June 06, 2011, 06:19:31 PM

For those people that 1.4 refuses to work, try this: http://www.mediafire.com/?qgz988s9ojx7j4n
I copy-pasted the entire phoenix-launching function from 1.4 over. See if this works.

This works for me as 1.4 wouldn't actually run phoenix.exe

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 06, 2011, 06:51:50 PM

Quote from: hollajandro on June 06, 2011, 06:47:58 PM

Quote from: lvlrdka22 on June 06, 2011, 06:19:31 PM

For those people that 1.4 refuses to work, try this: http://www.mediafire.com/?qgz988s9ojx7j4n
I copy-pasted the entire phoenix-launching function from 1.4 over. See if this works.

This works for me as 1.4 wouldn't actually run phoenix.exe

Yay! Now try this (pasted the kill function into the wrong window on the last link :(, updated now): http://www.mediafire.com/?c2jfam1cubkg1b3
I replaced the kill function with 1.4's.
Let me know if hitting stop successfully kills phoenix.exe or not (or if it blue screens).

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 06, 2011, 06:56:45 PM

used 1.32 version overnight and all day. no hang issues..will try 1.4 when the dust settles a lil

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 06, 2011, 07:18:47 PM

Quote from: FRanz33 on June 06, 2011, 06:56:45 PM

used 1.32 version overnight and all day. no hang issues..will try 1.4 when the dust settles a lil

Glad to hear it :D... finally!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 06, 2011, 08:01:08 PM

Well, fixed a stupid issue in 1.41. Phoenix should launch correctly now.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 06, 2011, 08:23:17 PM

will try soon..I think for the next version osd control should be a concern. Having a set place that they go each time so they dont pile up in the corner and an option to hide them. what do u think?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 06, 2011, 08:49:33 PM

PR 1.41 from this link http://www.mediafire.com/?5h3y5b6jq1azp13

I have in this order
cl1 device 0, gpu 0 in afterburner gpu2
cl2 device 1, gpu 3 in afterburner gpu3
cl3 device 2, gpu 6 in afterburner gpu1

The temp function works correctly, pausing & restarting.

But all the thing happened only after i removed "READ ONLY".
So, its better to avoid read only now.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Peao on June 06, 2011, 08:52:09 PM

Strange ... Has anyone noticed a drop of approximately 10% in hashrate these latest versions?
Tested 1.41 in two rigs and got the same problem...
When I use the 1.3, the hashrate is normal.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 06, 2011, 08:55:34 PM

Quote from: dishwara on June 06, 2011, 08:49:33 PM

Hacky temperature monitoring works for someone other than myself :o, amazing!

Quote from: Peao on June 06, 2011, 08:52:09 PM

Strange ... Has anyone noticed a drop of approximately 10% in hashrate these latest versions?
Tested 1.41 in two rigs and got the same problem...
When I use the 1.3, the hashrate is normal.

Yeah, did you add VECTORS to Extra Flags yet? It was already added in 1.3 when launching phoenix, but I removed it in later versions so people can have control over VECTORS or not.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 06, 2011, 09:08:33 PM

I am now running 1.41 & let it run until i woke up. Time here is 2:40 am & i may sleep at 3 or 4 or 5 or....don't ask.
For the past 20-30 minutes running with out a single crash.
I am not using temp function right now, cause i run fan at 75% & my temp stays below 74C even in daytime with 36C-40C, my city temperature.

Again, i repeat one thing, all working ONLY after i disabled Read only.

You can buy some of my shares to help me rise.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Peao on June 06, 2011, 09:11:11 PM

Quote

Yeah, did you add VECTORS to Extra Flags yet? It was already added in 1.3 when launching phoenix, but I removed it in later versions so people can have control over VECTORS or not.

Ooops! :-[

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 07, 2011, 03:07:20 AM

I am getting same speed 430+ Mhash/s for each 5870 card. No speed change.

Running 1.41 for past 4-5 hours. 3 clients running. & 2 shows 1700+ shares accepted.
When i woke up, i saw a Windows white error window saying, phoenix.exe gave problem something & asked to close it.
I clicked close then OSD showed up with 2 clients 1700+ accepted & another one 800+ accepted.
Seems one client crashed, but it restarted itself in background & was running. But in front widows showing crash error.
Once i closed the crash error window, it showed OSD.
So, seems working good.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: kwaaak on June 07, 2011, 04:45:46 AM

Good stuff, thank you.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: mosimo on June 07, 2011, 08:58:52 AM

Nice program, the only gripe I have atm is the OSD overlapping. I know I can click the "click through" button to make them movable, but when I do this the OSD goes to a solid colour, lets me move it and no matter how many times I press the click through button again it never actually gets any text or transparency back.

I've not looked into that at all, I'm at work and a bit busy atm. But I did edit the client so it offsets the clients down the side of the screen and adds a 5px gap between them.

Changed line 715 from:

Code:

$osd[$i]=guicreate("OSD #" & $i+1,200,64,0,0,-1,bitor($ws_ex_topmost,$ws_ex_layered,$ws_ex_toolwindow),$hidden)

To:

Code:

$osd[$i]=guicreate("OSD #" & $i+1,200,64,0, + $i * 90,-1,bitor($ws_ex_topmost,$ws_ex_layered,$ws_ex_toolwindow),$hidden)

Source + binary here:
http://www.megaupload.com/?d=AXN0MYRP
http://www.mediafire.com/?qfau02x6fc8qa2c

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Internet151 on June 07, 2011, 09:03:59 AM

Moving the GUI box seems to be unusually difficult if using the Windows 7 Basic Theme. There's only a tiny point on the box that actually allows you to drag it and the rest clicks through.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: mosimo on June 07, 2011, 09:28:28 AM

Connecting over logmein to a slow connection it's difficult at times to click and drag. With that changed I don't need to do anything, turn the pc on, PR launches and puts the OSD in the correct places.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kluge on June 07, 2011, 12:23:07 PM

Quote from: Internet151 on June 07, 2011, 09:03:59 AM

Moving the GUI box seems to be unusually difficult if using the Windows 7 Basic Theme. There's only a tiny point on the box that actually allows you to drag it and the rest clicks through.

Yeah - that's a bit of a pain in the ass. My W7 boxes change to basic when the VNC server receives a connection. OSD can be dragged if you take the time to make sure the pointer is exactly on text of the OSD.

Unrelated -- Switched to BTCGuild today :)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Peao on June 07, 2011, 12:29:45 PM

Quote from: Peao on June 07, 2011, 02:32:26 AM

Someone is also seeing a decline in some of hashrate GPUs in the new versions?
In my rig 2x5970, for example, the hashrate of two GPUs are constant at 388. But the other two are ranging between 340 and 370.
Do not understand why this is happening...
If I run the phoenix from the command line, all four GPUs running steady at 388.
Any ideas? ???

UPDATE:
This problem happens only in cards with two GPUs (5970 and 6990).
In version 1.3 this did not happen.
If I start mining in only one of GPUs, the hashrate is normal. When I start the second GPU, the problem starts.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: rowbot on June 07, 2011, 12:33:54 PM

Quote from: huayra.agera on June 06, 2011, 03:02:01 PM

Quote from: rowbot on June 06, 2011, 02:50:25 PM

I'm running the GUI on 3 machines crossfired and am having no issues. Maybe you can update your flags?

Flags? I'm using the same settings as I was using with phoenix command-line: namely, in Rising I have 5xxx checked (which turns on BFI_INT), AGGRESSION set to 7, and I have VECTORS in the Extras.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Internet151 on June 07, 2011, 12:58:15 PM

Another issue I found is the latest version (1.41) for some reason dropped the ability to set the color of the GUI text to none. Please add this back in.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 07, 2011, 02:28:18 PM

Quote from: Kluge on June 07, 2011, 12:23:07 PM

Quote from: Internet151 on June 07, 2011, 09:03:59 AM

Moving the GUI box seems to be unusually difficult if using the Windows 7 Basic Theme. There's only a tiny point on the box that actually allows you to drag it and the rest clicks through.

It's one of the "features" of the Basic theme, don't think I can fix that :-\.
What I can do is set an option to be able to save the places of the OSDs.

Quote from: Internet151 on June 07, 2011, 12:58:15 PM

Another issue I found is the latest version (1.41) for some reason dropped the ability to set the color of the GUI text to none. Please add this back in.

It wasn't intended to allow anything other than those colors listed.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Lelouch on June 07, 2011, 04:09:45 PM

Which extra flags option are supported? Can you list them please?. Thanks!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Internet151 on June 07, 2011, 04:43:37 PM

Quote from: lvlrdka22 on June 07, 2011, 02:28:18 PM

Quote from: Kluge on June 07, 2011, 12:23:07 PM

Quote from: Internet151 on June 07, 2011, 09:03:59 AM

Moving the GUI box seems to be unusually difficult if using the Windows 7 Basic Theme. There's only a tiny point on the box that actually allows you to drag it and the rest clicks through.

It's one of the "features" of the Basic theme, don't think I can fix that :-\.
What I can do is set an option to be able to save the places of the OSDs.

Quote from: Internet151 on June 07, 2011, 12:58:15 PM

Another issue I found is the latest version (1.41) for some reason dropped the ability to set the color of the GUI text to none. Please add this back in.

It wasn't intended to allow anything other than those colors listed.

Can you add some way to disable the GUI then if you won't add a function to set colors to none?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: brunoshady on June 07, 2011, 05:52:41 PM

I'm trying to run it and I can't get the OSD appers on the screen...

when I click run, the dos window popups and closes and nothing more happens...

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: LegitBit on June 07, 2011, 06:57:00 PM

Quote from: brunoshady on June 07, 2011, 05:52:41 PM

I'm trying to run it and I can't get the OSD appers on the screen...

when I click run, the dos window popups and closes and nothing more happens...

That sometimes is fixed by restarting. It can be caused by a bad overclock or invalid WORKSIZE as well.

Is it your first time running a client or does the card work with other miners?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Lelouch on June 08, 2011, 12:27:50 AM

It happens to me too. As I have set the same option and extra flags from the 1.31 which works great. With 1.41 the OSD just doesn't appear. Any solution?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 08, 2011, 02:16:54 AM

Mind posting a screenshot of the GUI, with ID/password blanked out, and post what Extra Flags you are using?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Lelouch on June 08, 2011, 02:54:32 AM

http://i54.tinypic.com/2uji8mv.jpg

Extra flags used: BFI_INT VECTORS WORKSIZE=128

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: pandemic on June 08, 2011, 03:41:10 AM

I've never used phoenix but I downloaded and extracted it. Then I extracted this GUI into the same folder. I have an ID, username, password. I put in the ID and password along with server and port. I also found that my GPU is 0 and put that in accordingly.

Pretty much all that happens is I press run, a window opens very quickly and then goes away. GPU never goes past 0-1%

edit: looks like it's running now. I've got no real way of knowing what rate it's going at though, unfortunately.

And I now see where it shows the mh/s too. Sweet.

Now I just have to look for some information on the 4870 to get higher mh/s out of it. Right now I'm at about 70-75

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 08, 2011, 05:19:54 AM

Quote from: Lelouch on June 08, 2011, 02:54:32 AM

http://i54.tinypic.com/2uji8mv.jpg

Extra flags used: BFI_INT VECTORS WORKSIZE=128

Quote

HD5xxx+: checked means use BFI_INT, uncheck if your hardware doesn't support it (commonly, HD5k and HD6k series are supported).

You should also check pr.log and make sure that it's exactly what you want.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: hiVe on June 08, 2011, 07:31:04 AM

Quote from: pandemic on June 08, 2011, 03:41:10 AM

I had the same problem, never quite found out what the problem was.
Care to share how did you solve it?

Thx.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: cowboyhank on June 08, 2011, 07:37:46 AM

I'm also getting the lower hashrates. Could it be related to the new heat monitoring? Perhaps it's overriding overclocks?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: snoopytime on June 08, 2011, 07:43:06 AM

I got this running today, very nice! I have 2x 5830s, im running the HD58xxx+, Fastloop, phatk.
ones at agress 11, the other at 12. Flags = VEVECTORS WORKSIZE=128

My question is, does the bitcoin client need to be running too for this (or any GPU miner) to work?

Also, i read you need the ATi 2.4 SDK to mine (with windows anyway) . . I got it and installed it but nothing extra happened . . like my Mhash is the same. Do you have to invoke it or tune it or some wakky shit?

Thxxx!

Snooop

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Lelouch on June 08, 2011, 12:01:42 PM

EDITED: Working good now! Thanks!
PD: I forgot to add the kernel module. Silly me and sorry!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: cowboyhank on June 08, 2011, 04:16:59 PM

No I have OC'd 5870 + 5830s, and the hashrate it changes to is non OC'd.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 08, 2011, 07:06:16 PM

@ lvlrdka22

Seems, after i confirmed that temp control works, u went to take rest.....
I badly need tabbed interface, soon i will be running with 8 cards, if windows supports.

Also, how to make it work with 2 platforms?
I have both Nvidia & AMD card in my system.
Nvidia card is 9400GT which can't mine, it takes care of all graphic things, so 6870 mines freely with out crash.
But it all happening in cmd prompt only.

When i try to run PR, it can't able to mine.
starts, goes to back up server, again comes to main server & same thing repeating.
Seems it cant able to find device. Also, your device finder shows only one device & that too seems nvidia card not amd.

PR doesn't support 2 platforms?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: brunoshady on June 08, 2011, 07:51:50 PM

try high values at idle time...

was this in my case

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 09, 2011, 01:29:55 AM

Quote from: Peao on June 08, 2011, 01:18:25 PM

Quote from: cowboyhank on June 08, 2011, 07:37:46 AM

I'm also getting the lower hashrates. Could it be related to the new heat monitoring? Perhaps it's overriding overclocks?

I'm having the same problem. Did you use a 5970 or 6990?

Quote from: cowboyhank on June 08, 2011, 04:16:59 PM

No I have OC'd 5870 + 5830s, and the hashrate it changes to is non OC'd.

See if the launching parameters logged in pr.log is exactly what you want to use.

Quote from: dishwara on June 08, 2011, 07:06:16 PM

As long as phoenix supports 2 platforms, it should. Just make sure you're using the correct arguments.
Forgot to say, as a temporary solution, make two folders and run one instance in each.

Oh, and 1.42.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: bitjet on June 09, 2011, 02:51:49 AM

running into a problem on one of my machines. when mining on more than one gpu i get really erratic gpu usage jumping around from 70% to 99%. Only with PR, I run the regular phoenix miner with no problems.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Vwlopez3 on June 09, 2011, 08:38:49 AM

Great software really quite impressive that you created this in such a short time span. There aren't many features that i can think of that would make this any better. Tried ubuntu but the lack of overclocking software mixed with frontend gui made windows the fall back. Will donate once my miner start producing again.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: karuso on June 09, 2011, 06:17:03 PM

I am mining at deepbit. What do i have to imput @server then? pit.deepbit.net?

And i want to use this settings. VECTORS BFI_INT FASTLOOP=false AGGRESSION=12 -k phatk WORKSIZE=256

So i have to uncheck fastloop, check hd5xxx, check phatk, write 12@agression and write "VECTORS WORKSIZE=256" at the extra flags?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 09, 2011, 08:00:49 PM

I see a problem with PR1.42
If i set Restart after an idle time, then the miner keeps on restarting only.
The only way to mine is make restarting to 0 or disabled.
Win 7, 64 bit.
Any other face same problem with PR 1.42 ?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: zale on June 09, 2011, 11:14:54 PM

Am I blind? I can't find the source code anywhere.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: smackdaddy on June 10, 2011, 12:13:32 AM

Great little app.

You know what would make it even better? If it also bound to a network port, providing a simple http-based interface, enabling people to remotely connect and determine miner status, statistics, change pools, etc.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 10, 2011, 01:06:52 AM

Quote from: bitjet on June 09, 2011, 02:51:49 AM

One way is to make sure that the launch parameters in pr.log matches the arguments in your batch file.

Quote from: karuso on June 09, 2011, 06:17:03 PM

Not sure on the server name for deepbit, but rest look fine.

Quote from: dishwara on June 09, 2011, 08:00:49 PM

It could be that the client is getting hammered with idles, or if server connection is a little erratic (e.g. flaky internet, DDoS, server bandwidth almost saturated, etc.). Those are the only cases that could cause it to keep restarting.

Quote from: zale on June 09, 2011, 11:14:54 PM

Am I blind? I can't find the source code anywhere.

Hm, there are only 3 types of files included, .exe, .au3, and .png. Take a rough guess ;).

Bleh, having a tough time figuring out the ADL DLL. This will probably take a while.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 10, 2011, 03:34:59 AM

Hey your doing great man. How about making vectors a check box instead of in the extra argument section. hell same for aggression and work size. they could be drop boxes like the affinity box maybe? what do you think PR 1.5??

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: karuso on June 11, 2011, 06:24:17 AM

Quote from: FRanz33 on June 10, 2011, 03:34:59 AM

Word.

And you should also be able to select the miner you're at like in the guiminer.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: bullox on June 11, 2011, 08:10:05 PM

Is there some sort of setting to NOT print out these client stats on top of everything else? I really like the easy config and backups and whatnot, but having the client spam on top of everything is not what I want.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: patica on June 11, 2011, 10:48:33 PM

PR works fine with one client & one video-card. But I have some pc's with 2-3 vga's and when I start PR on them, after 2-3 hours I have a freeze. Settings are:

client #1 - primary pool 1, backup pool 2
client #2 - primary pool 2, backup pool 1

client #1 - primary pool 1, backup pool 2
client #2 - primary pool 2, backup pool 3
client #3 - primary pool 3, backup pool 1

HD5xxx ON, fastloop Off, phatk ON, AGG 13, VECTORS WORKSIZE=128, affinity - core 0
HD5850, 900/300 MHz, Win 7 64 bit, Driver 11.4 + OCL 2.4

With these settings all of cards have no problem to work with phoenix+phatk in cmd. But PR freeze even on 850/300 MHz.

And last - can you put button "Start minimized" under "Startup" button?
... and password invisible with ******* :)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 12, 2011, 08:52:08 AM

can u make the color of the temperature showing in device finder from grey to RED or GREEN or BLUE.
Grey is very hard to see.
I opened devicefinder.au3 with notepad, but don't know how to change from grey to any color i want.
can u please tell or change file yourself.
It will be much appreciated.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: vborets on June 12, 2011, 09:09:39 AM

Hi!

Good job, and could you add a button to exchange places settings the primary and backup servers?

not convenient to keep changing .INI files

Thank you!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 12, 2011, 09:16:59 AM

Wow, what a great tool! Thank you!

Two things:
— There are some moments when OSD is constantly blinking almost every second (no matter is click-through on or off), which is kinda annoying. Didn't figure out what causes this. Windows 7, aero disabled.
— I'm sure you know that device finder doesn't really show the correct device numbers :)

And minor things:
— It would be good if password was stored like this: "*************".
— Maybe would be also good to let the user to hide OSD when he needs to. Like, some checkbox "show OSD" or something.
— Desktop lag is more significant compared to the usual phoenix with the same settings.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 12, 2011, 11:34:37 AM

Oh, and some more: is it possible not to switch focus to the new phoenix window? I mean, can it be done without losing focus to the application I'm currently in? Sorry for weird words, don't know how to correctly say that.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: bcpokey on June 12, 2011, 11:44:02 AM

I think I've discovered the reason why Phoenix Rising has started to put out such low hashrates compared to before. Checking the PR.log file the default argument is now missing the VECTOR flag.

Manually adding VECTOR into the "other flag" field brought hashrate back up to its original levels. If you could have it automatically add that flag in the next version that'd be great. Or a check box?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 12, 2011, 12:21:41 PM

Quote from: bcpokey on June 12, 2011, 11:44:02 AM

I think he actually told about it a couple of times :)
Checkbox's good. Autovectors - not good, I think, because I would want to set all flags by myself.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 12, 2011, 04:28:27 PM

Sorry for almost-quadruple-posting, but this is really important.
How long does it take to switch to the backup pool? I can't figure it out myself.
Considering some pools are experiencing ddos nowadays (especially deepbit), it becomes crucial to switch to another, backup pool at the right time.
Once I noticed that switching happened after one minute of idling. But now it takes much longer for some reason.
I would really appreciate if you, lvlrdka22, let users change this amount of time in settings.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 12, 2011, 04:55:38 PM

Quote from: 5tr1k3r on June 12, 2011, 09:16:59 AM

The blinking part is when its redrawing the text. It might be hardware acceleration-prone, not sure. I can turn down the refresh rates a bit so the blinking isn't as severe.
I'll get around to those eventually, still messing with ADL :-\.

Quote from: 5tr1k3r on June 12, 2011, 11:34:37 AM

Or, and some more: is it possible not to switch focus to the new phoenix window? I mean, can it be done without losing focus to the application I'm currently in? Sorry for weird words, don't know how to correctly say that.

Yeah, it's not as seamless as I liked, even when launching phoenix without the cmd window ever showing. I can set it to retrieve last-active application, and reactivate that after launching though.

Quote from: 5tr1k3r on June 12, 2011, 04:28:27 PM

If miner idles (hashrate~0 or phoenix hasn't sent out text updates, which it does every time it refreshes hashrate/accepted/rejected, etc.) more than the set time and not responsive to pings.
I'll eventually add an option to use x accepted shares in y minutes, unless someone has better ideas.

I did finally figure out how to initialize ADL (finally!).

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 12, 2011, 06:07:22 PM

Quote

The blinking part is when its redrawing the text. It might be hardware acceleration-prone, not sure. I can turn down the refresh rates a bit so the blinking isn't as severe.

Maybe it would be a nice idea to redraw the text when it actually needs to be redrawn (right now it redraws even without any needs)? When some stats have actually changed — accepted/rejected shares counter has increased or mhash/s performance has changed (with the given accuracy, like, 300 became 299 or so).

Quote

I guess that the problem is this: a pool is responsive to pings, but however (for any reason) it cannot offer you any mining work, so miner is idle. And your program decides to keep trying to mine here and not making an attempt to switch pools. Am I right on this? :)

Quote

I did finally figure out how to initialize ADL (finally!).

Well, that's truly great :)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 12, 2011, 07:22:56 PM

Quote from: 5tr1k3r on June 12, 2011, 06:07:22 PM

Yeah, I'll need to make another global constant then :-X, which I really don't want to do. I'll just make it refresh every half/one second or something.

Quote from: 5tr1k3r on June 12, 2011, 06:07:22 PM

Yeah, still can't figure out a better way of checking if pool is down or not. So, it's either ping or checking for share acceptance rate, unless someone comes up with a better idea, preferable one that doesn't need separate implementations for different pools.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: smackdaddy on June 12, 2011, 09:20:52 PM

Quote from: lvlrdka22 on June 12, 2011, 07:22:56 PM

Quote from: 5tr1k3r on June 12, 2011, 06:07:22 PM

I vote share acceptance rate, after all that's the true measure of the value of the mining process.

So, if it's share acceptance rate and not network reachability, how do you decide when to switch back to the primary pool? Perhaps in that scenario of handling failover, you would be able to set a time until the primary is tried again (similar to the current setting), and a configurable period of time during which the primary must accept a share or it goes back to the secondary.

You know what I'd really really love more than anything else for this program? A simple button to force a client to switch from primary to backup or backup to primary. Right now, I do it by swapping ini files.

The other thing I would love would be if the program remembered where your OSDs live. Having to reposition them every time is frustrating.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 13, 2011, 06:00:39 AM

Quote from: smackdaddy on June 12, 2011, 09:20:52 PM

Share acceptance rate probably will take longer to be able to determine if pool is up or not though, since you'll need to go on primary pool for a few minutes at least to determine if shares are accepted or not.
If you guys are fine with that, then sure. The side effect is that it wouldn't be feasible to have it check if primary is up say every 5 minutes anymore.

I suppose that it's time I upload 1.43, where I fixed some stuff (forgot what, but I did fix them 8)) and made Save Settings button save current position of OSDs.

Also, fun stuff :D:
http://i53.tinypic.com/v66lxs.png

Oh, pretty much have everything in the ADL DLL figured out, finally. I should be able to throw together a very rough GPU clock tool soon.

1.43.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 13, 2011, 07:18:22 AM

http://www.mediafire.com/?ko6eydbeph5itm4
If anyone's feeling like being guinea pigs, run that from command line, and let me know the output, along with how many GPUs you are running (and which GPU # printed from the program corresponds with which GPU number in mining, if you happen to know them or wouldn't mind trying to figure it out). Single GPUs should work fine, but not sure about duals (5970/6990).

Right now, just retrieves clock and temperature info, but it's not too hard to make it an OC tool. If it's reading GPU info correctly, that is.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: jhansen858 on June 13, 2011, 07:23:05 AM

Sorry i didn't read through all 12 pages of this but is there a linux version? Ubuntu plz!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 13, 2011, 07:41:30 AM

Quote from: jhansen858 on June 13, 2011, 07:23:05 AM

Sorry i didn't read through all 12 pages of this but is there a linux version? Ubuntu plz!

Autoit is, and always will be (I think), Windows only! Complain to the devs for that, I'm not good enough :-\.

Ninja'd a second version of 1.43 on, since I forgot to add the "fix" for the window activation "bug."
Going to ninja another version of 1.43 on http://www.blizzhackers.cc/images/smilies/icon_facepalm.gif, since I forgot to reduce the refresh rate.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 13, 2011, 08:30:11 AM

http://up.idiaths.ru/?id=b88aea398748f557

Temperatures are not the same as msi afterburner (or rivatuner) is showing. It shows higher values, 74 & 68 respectively. Obviously it uses another gpu sensor. Guess it'd be the right choice for you to use these sensors too :)
Device numbers are not the right numbers (that are used in settings of your program), they should be 0 and 1, not 0 and 3

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 13, 2011, 09:23:13 AM

The temperatures should be the core temperatures, at least they are for my 5850s.
And yeah, still not sure how device numbers are calculated. These numbers are assigned by the driver itself.
Does it at least report correct clock speeds and correct number of GPUs (counting 5970/6990 as 2)?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 13, 2011, 01:39:17 PM

Damn, deepbit's down again. I definitely vote for this solution: switch to backup after two-three (or more) periods of idling. For example, if I have "Restart after an idle time of 30 seconds" option, switching will be executed after 1+ minutes of idle time.
If you don't like the idea, then I definitely vote for button that forces a client to switch from primary to backup or backup to primary, it was mentioned before by smackdaddy.
That's just too sad to lose 10 minutes of mining when you can lose only one :)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 13, 2011, 03:02:41 PM

I want the option to switch back to the back up MANUALLY also.
Today slush pool was in attack & miner can't able to connect. I already gave deepbit as backup. It doesn't even switch to deepbit, instead keep on restarting in slush server only. Since there is no manual way to switch to back up, i just ran guiminer by giving all the deepbit data for my 3 miners & mining in deepbit so far fine. for the past 3-4 hours.
PR badly needs manual override. Just waiting it to automatically to back up doesn't seems to work when the pools are in Ddos attack.coz the pool responds ping & so the miner believes, it doesn't have to switch to back up.
Manually switching to back up is needed.
You can add a single check box, which will allow all miners to mine in backup miner only. This is the easiest way when pools are in attack.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Vwlopez3 on June 13, 2011, 04:37:56 PM

Quote from: dishwara on June 13, 2011, 03:02:41 PM

I agree at least as a temporary solution i think both an idle worker and manual override button are needed. But the most needed feature of all is donation address or link.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 13, 2011, 07:06:21 PM

Barely Clocked (http://forum.bitcoin.org/index.php?topic=16406.0): barebone clock/voltage tweaking.

Time to move back to working on the pool down thing then.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 13, 2011, 09:08:44 PM

1.44. Now uses x restarts per y time to check. It can potentially result in a little longer down time compared to a method that immediately tells if server is down or not, but is a much better indicator than pinging.
Oh, and if you were checking if main server is up every minute or so, it's now probably a better idea to make that interval longer, like at least 15 minutes.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Basiley on June 13, 2011, 10:01:42 PM

can someone mirror it somewhere w/o crapware of any kind on download page[and website "in general"] ?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 14, 2011, 07:44:33 AM

http://up.k10x.net/boqwmfhcqizel/PR1.44.rar

I didn't happen to test the new feature, because pool was never down since the beginning of testing.
Kind of can't get the whole logic of this: what happens if I have options "Restart after an idle time of 30 seconds" and "If 2 restarts occur in 20 seconds then switch to backup"?
Will it ever switch? :)
Seems to me like second time is pretty much unnecessary.
Anyway, good job, thanks.

By the way, is it possible to kill all phoenixes when quiting? I forget to stop them manually sometimes.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 14, 2011, 04:42:58 PM

Quote from: 5tr1k3r on June 14, 2011, 07:44:33 AM

Yeah, that's one of the "features" I was hoping people wouldn't notice.
I suppose I can make it so that it can't be below the value of # restarts times idle length.
Quitting thing, sure.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 14, 2011, 05:22:25 PM

1.45. Close on quit added, and made it so that the time in "number of restarts in x time before switching" can only be set to the minimum of (max idle+5 seconds)*number of restarts.

Side note:
http://i52.tinypic.com/m8lp5l.png
OMG scripts running all over the place!
/showoff

Also, is the forum moving like molasses, or is it just me?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 14, 2011, 07:04:48 PM

It just... doesn't create phoenix instances :D
Sorry :D

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 14, 2011, 07:50:18 PM

Eh what?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 15, 2011, 12:14:31 AM

Damn, forget it, I didn't put kernels folder o,o

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 16, 2011, 08:25:09 AM

1.5. Tabs. Vectors checkbox. Aggression and Work Size drop downs.
Move along. Nothing exciting to see here.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on June 16, 2011, 12:49:07 PM

Sweet changes! And I love the colors of the OSD, much easier on the eyes. Am still awaiting the integration of BarelyClocked. :)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 16, 2011, 04:31:29 PM

Quote from: lvlrdka22 on June 16, 2011, 08:25:09 AM

1.5. Tabs. Vectors checkbox. Aggression and Work Size drop downs.
Move along. Nothing exciting to see here.

Nice to here about tabs.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Vwlopez3 on June 16, 2011, 06:10:48 PM

The "backup" checkbox doesn't ungrey the input fields, nor does clicking the pause mining when gpu reaches.... checkbox
P.S Im not sure if i'm huge on the tabs i actually grew to like the one big field. Perhaps update both?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: brunoshady on June 16, 2011, 07:33:07 PM

that background of the bottom part of the program is in alpha mode (invisible)...

it was intended?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 16, 2011, 11:44:12 PM

Quote from: Vwlopez3 on June 16, 2011, 06:10:48 PM

Accidentally had event mode set on the labels instead of checkboxes http://www.blizzhackers.cc/images/smilies/icon_facepalm.gif.

Quote from: brunoshady on June 16, 2011, 07:33:07 PM

that background of the bottom part of the program is in alpha mode (invisible)...

it was intended?

Yeah. Let me know if it get's annoying.

http://i55.tinypic.com/4udg7s.png
Currently only reads the GPU values.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: brunoshady on June 17, 2011, 01:03:05 AM

Quote from: lvlrdka22 on June 16, 2011, 11:44:12 PM

Quote from: Vwlopez3 on June 16, 2011, 06:10:48 PM

Accidentally had event mode set on the labels instead of checkboxes http://www.blizzhackers.cc/images/smilies/icon_facepalm.gif.

Quote from: brunoshady on June 16, 2011, 07:33:07 PM

that background of the bottom part of the program is in alpha mode (invisible)...

it was intended?

Yeah. Let me know if it get's annoying.

http://i55.tinypic.com/4udg7s.png
Currently only reads the GPU values.

it's annoying =p

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 17, 2011, 04:05:05 AM

your kicking ass..best gui out right now! Ok umm for 1.55 minimize on start or x closes to tray? easy to hide on office computers if it restarts =-) damn i really cant think of anything else lol auto detect for device hell idunno its so damn close to purfect i cant even imagine 2.0 lol this is like less than a month

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 17, 2011, 06:47:50 AM

Quote from: brunoshady on June 17, 2011, 01:03:05 AM

it's annoying =p

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Mechanizm on June 17, 2011, 06:52:17 AM

Absolutely awesome - loving all the new features.. thanks again!!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 17, 2011, 07:28:55 AM

1.61. Forgot about the limits placed by GPU BIOS (in case some people downloaded 1.6 and were wondering about why over-volting doesn't work in some cases). Now detects these limits and has these set as max/min possible.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: tito13kfm on June 17, 2011, 07:29:41 AM

OSD doesn't display over VNC only. Displays fine on actual screen. I have absolutely no idea. The machine is sitting right next to me. I look at the monitor, OSD stats are there, look at the VNC viewer on my laptop, no OSD stats appear.

Was working on 1.41, gone now in 1.6

I haven't tried any version in between.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on June 17, 2011, 07:45:06 AM

Quote from: lvlrdka22 on May 28, 2011, 01:48:58 AM

http://i55.tinypic.com/64p839.png

Current version 1.61: http://www.mediafire.com/?6tx6wewldrdr5p4

IF you really feel the need to donate, switch pool to BTC Guild or Eligius (if you aren't there already)!

History:
1.61 Reads hard limits on each GPU placed by the GPU BIOS.
1.6 Added GPU clock/voltage/fan controllers. OSDs now display temperature if "Pause mining when..." is checked and the GPU number is filled in. The GPU number used in monitoring temperatures is changed to use Adapter Index.

Finally! I am a happy camper! Are you sure mining @ BTCGuild or Eligius is the only barter you'd like for your work? I bet many of us here are willing to donate some coins. :)

Oh, is the Temperature checkbox working now? With 1.5 I was not able to edit the temp values. Thanks again for heading my requests! Arguably the best GUI Miner out there.
EDIT: It's working now and the temperature OSD is great. However, it seems it is just reading the temp of 1 GPU for both (Crossfired Rig).

The OC clocks seem to limit to just 775 GPU Core from 725, I read here, you followed the lock or something. I hope you can like put a checkbox to lock/unlock for more overclocking headroom.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 17, 2011, 08:32:33 AM

Quote from: huayra.agera on June 17, 2011, 07:45:06 AM

EDIT: It's working now and the temperature OSD is great. However, it seems it is just reading the temp of 1 GPU for both (Crossfired Rig).

The OC clocks seem to limit to just 775 GPU Core from 725, I read here, you followed the lock or something. I hope you can like put a checkbox to lock/unlock for more overclocking headroom.

Do you see one tab for each of the GPUs?

Try using 1.6 (or this (http://forum.bitcoin.org/index.php?topic=16406.0)) and setting core above 775. If it works, I'll add make it go 200 MHz above limit or something. If not, can't help there :-\, it's a BIOS limit (I think) that I don't know how to bypass.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on June 17, 2011, 09:37:34 AM

It's kinda weird, on my other rig also crossfired 5850s although both non reference compared to the other, they go up to 900 on GPU core. I'll see what else I can find. Maybe yeah you can up the limit to like 1000 maybe. Because my 6850 can go up to 1021 on GPU core. Thanks a bunch!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 17, 2011, 11:54:32 AM

http://up.idiaths.ru/?id=ae8663b198fad34a
It can't detect temperatures. The rest works fine, thanks. Btw there are afterburner's temps in tray.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: testerx on June 17, 2011, 01:50:39 PM

How do you use this with Phoenix 1.50? Is there some way to show the Mhash/s rate?
Oh nevermind, just realized that it's not even running...getting 0% GPU usage =(

Nevermind, I'm a moron...forgot to unzip the kernels folder *facepalm*

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: brunoshady on June 17, 2011, 04:12:41 PM

Quote from: lvlrdka22 on June 17, 2011, 06:47:50 AM

Quote from: brunoshady on June 17, 2011, 01:03:05 AM

it's annoying =p

ihaiuhaiuahiau

btw, temp is show ? here... sapphire 5850 xtreme

and nice work dude

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 17, 2011, 04:56:51 PM

Quote from: huayra.agera on June 17, 2011, 09:37:34 AM

Eh, so does setting clocks above 775 work on 1.6?

Quote from: 5tr1k3r on June 17, 2011, 11:54:32 AM

http://up.idiaths.ru/?id=ae8663b198fad34a
It can't detect temperatures. The rest works fine, thanks. Btw there are afterburner's temps in tray.

Quote from: brunoshady on June 17, 2011, 04:12:41 PM

ihaiuhaiuahiau

btw, temp is show ? here... sapphire 5850 xtreme

and nice work dude

Yeah, check "Pause mining when..." It enables temperature monitoring. Otherwise temperatures show up as ?.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: brunoshady on June 17, 2011, 05:24:16 PM

Quote from: lvlrdka22 on June 17, 2011, 04:56:51 PM

Quote from: huayra.agera on June 17, 2011, 09:37:34 AM

Eh, so does setting clocks above 775 work on 1.6?

Quote from: 5tr1k3r on June 17, 2011, 11:54:32 AM

http://up.idiaths.ru/?id=ae8663b198fad34a
It can't detect temperatures. The rest works fine, thanks. Btw there are afterburner's temps in tray.

Quote from: brunoshady on June 17, 2011, 04:12:41 PM

ihaiuhaiuahiau

btw, temp is show ? here... sapphire 5850 xtreme

and nice work dude

Yeah, check "Pause mining when..." It enables temperature monitoring. Otherwise temperatures show up as ?.

true... thanks =)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: brunoshady on June 17, 2011, 05:25:22 PM

it could be interesting show in the OSD the core and memory clock

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 17, 2011, 05:46:51 PM

I guess would be cool to draw some mhash/s chart somewhere in the main window (additional tab maybe), to monitor performance and stuff like pool uptime. I haven't seen this in any miner I used.
Actually, afterburner's gpu temperature monitor works fine, but it would be more cool like this :)

Also I suggest to change textboxes type such way, so after clicking in there I don't need to erase all the words like "Device name" or "Pool's name" or whatever. The text remains there, but after clicking on textbox it disappears allowing me to write something. Just a minor thing though.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: klaaster on June 17, 2011, 06:00:15 PM

Very nice Program, thanks for that!
I'm mining since last week on Eligius, now even better if the server gets some hiccup. :)

Would be nice to have some script with a backup server like this for ubuntu through ssh, hmm, time to search the forum and write my own. i am off ;)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 17, 2011, 06:09:51 PM

http://up.idiaths.ru/?id=a1659025fb0fe858
Temperatures seem to be wrong, hm. I'll explain a little: as you can see, I have 2 graphic cards, 5770 and 5850. Their adapter indexes are 3 and 0 respectively. But in order to get them working I have to choose 1 as a device name for 5770 and 0 for 5850. When I put 1 and 0 in "Pause mining ..." I get pretty much the same temperatures (as you can also see), which can't be true. I tried 3 for 5770, it shows some 64, while it's supposed to be hotter than 5850. But for 5850 it works good, because it shows same values as msi afterburner (it's down there, in the tray). Maybe it's just a coincidence.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 17, 2011, 06:23:48 PM

And another minor thing. It's better not to write "at ?°C" at all, when "Pause mining ..." is unchecked.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 17, 2011, 08:21:47 PM

1.62. A few GUI changes. Clock speeds can now be set to BIOS limit plus 200 MHz, and VDDC max is BIOS limit plus 200 mV. If you can't set it higher, it probably means you've hit the limit.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: PoulGrym on June 17, 2011, 09:57:19 PM

Nice GUI. Just thought I'd say that I had an issue with backup server because of a typo of ":" semicolon. Good idea could be to make error box pop up if address fields have strange symbols in them. Took me a little while to figure it out as it was the first symbol in the field so I didn't see it.

Keep at it!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on June 18, 2011, 06:42:33 AM

The OC tool is now working properly (both Single GPU 6850, Dual/Crossfired 5850 config).

I have a suggestion regarding the fan control, just like in MSI Afterburner and Trixx, they have custom profiles wherein if the Temp goes up, fan speed goes up as well, and vice versa. Maybe you can pattern that custom profile to PR 1.63. :) Thanks!

Oh, and OSD for GPU Core, Memory, Volts, and VRM Temps would be great, too!

Regarding the temperature, it seems it's only reading the 2nd GPU's temperature and displaying as one (for multiple GPU config).

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 18, 2011, 07:01:01 AM

Quote from: huayra.agera on June 18, 2011, 06:42:33 AM

The OC tool is now working properly (for Single GPU config).

I have a suggestion regarding the fan control, just like in MSI Afterburner and Trixx, they have custom profiles wherein if the Temp goes up, fan speed goes up as well, and vice versa. Maybe you can pattern that custom profile to PR 1.63. :) Thanks!

Oh, and OSD for GPU Core, Memory, Volts, and VRM Temps would be great, too!

It should work for multi-card configurations. At least it's working on mine.

I was going to say, if you want a custom fan control, just use Afterburner or whatever. I'm too lazy to add that.
I also really don't want to have the OSDs cluttered with stuff, so what you see there will probably be the only stats I'll add.

Eh, trying to figure out how OpenCL device numbers are ordered (if they are listed the same way ADL lists adapters, but from what I've read, no correlation whatsoever) so maybe we can get one fixed set of numbering system.

Right now, got "clGetPlatformIDs" and "clGetPlatformInfo" working correctly I think.
"clGetPlatformInfo" returns "Advanced Micro Devices, Inc."
I hope that's what it's supposed to return.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on June 18, 2011, 07:13:04 AM

No problem man! But I guess the temp fix would be great. ;)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 18, 2011, 09:12:30 AM

Might be useful if people with different GPUs models (as in GPUs with first 2 numbers different, such as 5850 and 6990 in the same system) run this and post the stuff in adlocl.log: http://www.mediafire.com/?p9i80it24z879d6
All it does is print out the Device Numbers (and some other misc. information) for OpenCL (I think these numbers are what Phoenix uses) and the information provided by ADL.
What I'm interested in is the order OpenCL prints each device out, and the order of Adapter Indices, OS Display Indices, and Bus Numbers printed from ADL.

Neither OpenCL nor ADL print out the full GPU names, unfortunately (Cypress/Radeon 5800 Series, respectively, like those help), so it's most helpful if people with multiple GPUs that have first two model numbers different run this.

Side note: OpenCL's get-device-ID/number function isn't useful at all in determining which GPU corresponds to which ::). It changes every time I run it.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: RedLine888 on June 18, 2011, 03:26:04 PM

does the voltage control work?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 18, 2011, 06:22:02 PM

Works on mine, until it hits the BIOS limit.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: dishwara on June 18, 2011, 07:20:48 PM

I tired with OC & it works good.
But, it also needs save option as saving mining details.
Restart removes all OC info & have to apply again.
Also there is no way to apply voltage changes.
For clock & fan speed, after moving slider to required Mhz & % clicking clock & fan, changes the clock & fan speed.
But for to change voltage, no option is there.

I also had a strange problem.
2 nos. of ASUS EAH5870 cards let me OC to anywhere, well i so far only tried 993 & 331 for core & mem.
The same i did for Sapphire 5870. But with your software Sapphire refuses to increase core above 900 Mhz & if i go above 900 Mhz, clicking clock brings it back to 900 Mhz, while Asus goes up to 993.

All the above cards ran perfectly at 993/331 using Afterburner before.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: hollajandro on June 18, 2011, 08:57:23 PM

Do you think you could add in the color 0x00FFFFFF for the OSD so it is invisible? Have to modify this every time you release a new version and I have seen others ask for a way to hide the osd as well.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 18, 2011, 09:10:32 PM

yes, a No OSD option and minimize on start up...

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 19, 2011, 07:10:47 AM

1.7a. Read the release history. Let me know if it doesn't detect all of the GPUs in OpenCL Device drop-down list, or if the device list is out of order (means "not in order," not "broken"), as well as the following stuff:

Quote from: lvlrdka22 on May 28, 2011, 01:48:58 AM

Need feedback on:

If the link between OpenCL GPU list and OS Index is correct (if setting an OpenCL Device automatically selects the corresponding GPU correctly) (beta version only).
If ADL detects the same number of GPUs as OpenCL (if the OpenCL Device list has same number of GPUs as number of tabs for controlling GPU clocks).
If it detects multiple GPUs correctly, in particular the 5970 and the 6990 (should be one tab for each core, or two tabs for each 5970/6990).

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kuber on June 19, 2011, 09:26:17 AM

Since i'm using 1.62 i got bluscreens at some point - if the pool connection doesn't work for instance. The miners try to restart until it bluescreens (every 4 seconds, 3 miners)
I suspect my undervolted CPU to be the reason, needs testing though.

Noob question: how can I display some sort of console to know whats going on? Think its a stupid question, but i have no idea how to initiate one with PR, since I've no actual experience with Phoenix.

Besides, excellent work lvlrdka22 :)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: blck42 on June 19, 2011, 01:04:46 PM

Im having an issue with running pr. I downloaded 1.62 tried the 32bit client and I get the following error:

line 7405 error: array variable substcript badly formatted.

i try run the script after i compile the 64 bit version (I have a 64 bit system), I get this error:

line 7670:
Error subscript used with non-Array variable.

I can run older verisions, like 1.42 and 1.43, just none of the new scripts.

Anyone have any ideas?

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 19, 2011, 05:01:37 PM

to get to the console log go into the folder and open the file that says pr. its a logged text document i believe. for the script error delete the config file that says phoenix and you should be able to open it and reconfig your settings.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 19, 2011, 07:50:31 PM

Quote from: blck42 on June 19, 2011, 01:04:46 PM

You probably don't have all of the include files.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: O_Shovah on June 19, 2011, 07:58:25 PM

Hello everybody

First of all this gui platform helped me a lot regarding handling and the fall back server option. So thanks very much for that.

But im having an issue with the overclocking options.

I have a HD 5870 wich has 1250mhz memory and 875 mhz core by default.

Clocking down the memory to 300 mhz works just fine.

But when i try to overclock the core frequency higher than 900 it is not applied and the gui is just reset to the last value below 900 mhz.
I hardly doubt im beyond the 200 mhz from BIOS limit.

Could somebody please try to figure out where i made a mistake or has anybody a simmilar problem?

OS: Server 2008 R2
SDK:2.4

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 20, 2011, 09:05:54 AM

1.7b. Fixed a few bugs with the GUI. Changed the get-parent/child process method.

If any of the drop-down fields are blank, delete the INI file and redo it! Or just delete the lines where there's nothing after the equals sign and save.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on June 20, 2011, 09:46:19 AM

Just wanted to report the Temps are now reporting properly for multi-card config.
Maybe you can make PR save the OC and fan settings and only apply when we hit Run. Oh btw, a Single RUN button to run specified clients (checklist maybe) would be great, like a main page or something. Thanks a bunch for the work. :)

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: LegitBit on June 20, 2011, 05:23:30 PM

Man this has come a long way.. the jump from 1.45 to 1.62 is amazing.

So here comes a potential problem and fix :

I've noticed that closing PR 6.2 does not revert the clock settings till a restart, for a headless miner this is fantastic, since many other utilities screw up the fan settings if a monitor is disconnected/resolution changed, I have a fe windows-boxes that this util works excellently for..

Though for a gamer this is terrible, since they may forget to revert the settings and could potentially cause a hard freeze by running an intensive game. I have noticed that certain extreme overclocks work fine for mining, but I nearly burnt a card (required a bios flash) from my carelessness by forgetting to reset the clocks to default values.

So maybe adding an option to retain settings or revert them on close would be nice.

I currently have to record my preferred values manually, then re-enter them every time I launch PR.

Again, thanks so much for the work you have done, the work you coders do for all of us is fantastic, I have all four of my boxes aimed at Eligius 24/7 as gratitude.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 20, 2011, 06:04:38 PM

Quote from: huayra.agera on June 20, 2011, 09:46:19 AM

Yeah, I'm thinking about saving OC settings.

Quote from: LegitBit on June 20, 2011, 05:23:30 PM

I think I added the "Default" button for 1.62, which reverts everything to BIOS settings, including clocks and voltage in idle mode. Fan doesn't reset though, and it won't be unless some other program assigns a new fan profile.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: LegitBit on June 20, 2011, 10:29:31 PM

Quote from: lvlrdka22 on June 20, 2011, 06:04:38 PM

You did, though then you still must remember to hit that, then manually re-enter your settings every time you re-open the app after resetting to defaults.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Endeavour79 on June 20, 2011, 10:53:49 PM

Hi, maybe a silly question.. But how do I move or predefine the OSD position? I don't see anything when using alt+tab or task manager..
Win7 x64

Cheers
End

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: lvlrdka22 on June 21, 2011, 01:29:45 AM

Quote from: Endeavour79 on June 20, 2011, 10:53:49 PM

Hi, maybe a silly question.. But how do I move or predefine the OSD position? I don't see anything when using alt+tab or task manager..
Win7 x64

Cheers
End

Click+drag. With Aero on, clicking anywhere on the OSD works (I think), but without Aero, you must click on the text.

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: c_k on June 21, 2011, 01:57:09 AM

Running 1.7b and loving it :)

Can we get an option to run minimised upon opening?

I have a shortcut to the app in my startup folder.

Infact, an option for running at startup in the app would be good too :D

Cheers!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: FRanz33 on June 21, 2011, 02:42:58 AM

Does running the shortcut as minimized work for you? because it doesnt for me. just starts up open anyways :'(

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Departure on June 21, 2011, 07:33:20 AM

Yeah an auto start mining option at startup would be awsome for headless boxes

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: huayra.agera on June 21, 2011, 08:30:06 AM

Hi! I checked this thread : http://forum.bitcoin.org/index.php?topic=19169.new#new
It seems it is very stable and there is no loss in performance. Maybe you can integrate? How I really wish I have some coding skills. ;D

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: Kuber on June 21, 2011, 03:04:39 PM

Quote from: huayra.agera on June 21, 2011, 08:30:06 AM

Second that, would be awesome!

Title: Re: Phoenix Rising: Front End GUI to Phoenix Miner
Post by: 5tr1k3r on June 21, 2011, 03:34:14 PM

I thought phoenix developers fixed this freezing bug recently. Didn't they?

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 21, 2011, 05:42:37 PM

1.7c. Added POCLBM parsing. Let me know if anything is broken, as per usual.
Renamed the thing.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: huayra.agera on June 21, 2011, 07:12:49 PM

Now that was very quick! Downloading and testing right away. :D

Update: the poclbm with phatk fork from fpgaminer is working properly with your frontend. ;D

Is the OC now being saved? Great work!

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: c_k on June 21, 2011, 08:17:47 PM

Excellent work with integrating support for poclbm client with phatk kernel, many thanks! ;D

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: Kuber on June 21, 2011, 09:16:15 PM

Getting problems, won't run poclbm. Won't start any miner - strange.
Just downloaded 1.7c, put poclbm files in same directory and run aoclbf 1.7c.exe.
Text fields as usual.. but when I hit "Start" nothing happens, neither with or without flags. GUIminer poclbm runs without problems..

Maybe I'm just to tired at the moment, but am I doing anything wrong?

Update:
Oh, well, now i got this : Error: Array variable has incorrect number of subscripts or subscript dimension range exceeded.
Even if i delete the *.ini, either it does nothing or it crashes.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 21, 2011, 09:45:30 PM

Since nobody complained about temperature monitor thing.

1.7. Saves clock settings and can apply them on startup.

Hm, check the log file or try a fresh copy of it?

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: Kuber on June 21, 2011, 10:33:02 PM

Quote from: lvlrdka22 on June 21, 2011, 09:45:30 PM

Hm, check the log file or try a fresh copy of it?

Attempt Nr.2:

Downloaded poclbm here -> http://github.com/downloads/m0mchil/poclbm/poclbm_py2exe_20110428.7z
Downloaded aoclbf 1.7

Put aoclbf files in poclbm dir.
Run aoclbf 1.7.exe
1 client, login, server settings - nothing else.
Choose GPU0 worksize 128 (testing with 5770)

--> Run

http://img7.imagebanana.com/img/tjwcl7kk/errorJPG.JPG

:(

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 21, 2011, 11:08:51 PM

1.71. Really added POCLBM parsing this time. Didn't know it had different output from Luke-Jr's (and the one with phatk) version.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: 5tr1k3r on June 21, 2011, 11:41:11 PM

Here goes feedback:

Quote

If the link between OpenCL GPU list and OS Index is correct (if setting an OpenCL Device automatically selects the corresponding GPU correctly)

Yes, it works fine, GPU is correctly selected. Though it might be difficult for somebody to remember core codenames.

Quote

If ADL detects the same number of GPUs as OpenCL (if the OpenCL Device list has same number of GPUs as number of tabs for controlling GPU clocks).

Everything's good here too, same amount of tabs. If you're interested, adapter and OS indexes are the same for each card.

I made an insight on temperatures monitoring and found out something.
I have 5770 and 5850. According to GPU-Z (and some other sources), there are three temp sensors in each card. My sensors values for 5770: 71, 83 and 77. For 5850: 76, 82, 81.
Your monitoring seems to show values of the first sensors, which detect the temperature of a display controller. And these are the lowest values of all three.
MSI Afterburner has one general graph for each graphic card, they are called simply GPU1 temp and GPU2 temp. GPU-Z also has additional GPU temp graph for general GPU temp monitoring. I was surprised to know that both programs use different sensors to show general graphic card temperatures. It's the second sensor for 5770 and the first sensor for 5850. So temps they are showing are 83 and 76 respectively.
Anyway, last paragraph was kinda offtopic. I was just trying to elaborate what sensors are best to use. I propose second ones, they are showing the highest temperatures of the graphic cards. I could finally throw away that afterburner temps from my tray.

About drop-down menu after "Pause mining when GPU ..." — I happen to have three options for this: 0, second 0 and 3. Though I have two cards o,o

About clocks tab: I didn't quite get why do I have to click "Clock speed" every time I want to apply changes :) Same for "Fan speed". What about "Save settings" concept?

I think, "BFI_INT" would be more informative and appropriate than "HD5xxx+".

Huh, looks like I'm done for now :D Thanks for impressive work.

Update: oh, sorry, forgot to tell the version, it's 1.7c.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: huayra.agera on June 22, 2011, 07:05:53 AM

Hi! Is there a way for you to remove BIOS limit for all three (Core, Memory, Voltage)? Like a checkbox maybe (warning that it will remove BIOS limit may cause damage to card etc.)

I was getting BSOD after a couple of minutes when I OCed using Afterburner and I tweaked my 5850 to 1010/300/1.25v. It seems since AOCLBF is running with the BIOS limit, when I go past that, it will BSOD. When I'm using the traditional command line, I did not have that issue. I was able to replicate the issue several times.

Overall, when I keep my voltage at stock, do the usual OC, it's working fine, no BSOD. This is using AOCLBF alone. But together with Afterburner, I'm having the issue.

I hope I made sense. Just woke up. lol ;D

Again thanks for the work!

EDIT: And Yeah! I 2nd the motion for like an Apply/Save for OC settings. Thanks!

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: Kuber on June 22, 2011, 07:46:40 AM

Quote from: lvlrdka22 on June 21, 2011, 11:08:51 PM

1.71. Really added POCLBM parsing this time. Didn't know it had different output from Luke-Jr's (and the one with phatk) version.

Works for me now, thanks :)
Except "Stale rate unsupported" .. where the rejected hashes should be listed.
Besides that, got even more hashes than before (which are shown in kilohashes now).

Update:
I tried fpgaminer's version, this one runs even smoother - with supported stale rate.
I see my yesterdays mistake..
-> 15 mhashes boost! Will try it on my mining-rig now.

Update 2: no stales yet, pretty awesome. GPU detection + heat monitor works properly, good work!

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 22, 2011, 07:21:47 PM

Quote from: 5tr1k3r on June 21, 2011, 11:41:11 PM

I have 5770 and 5850. According to GPU-Z (and some other sources), there are three temp sensors in each card. My sensors values for 5770: 71, 83 and 77. For 5850: 76, 82, 81.
Your monitoring seems to show values of the first sensors, which detect the temperature of a display controller. And these are the lowest values of all three.
MSI Afterburner has one general graph for each graphic card, they are called simply GPU1 temp and GPU2 temp. GPU-Z also has additional GPU temp graph for general GPU temp monitoring. I was surprised to know that both programs use different sensors to show general graphic card temperatures. It's the second sensor for 5770 and the first sensor for 5850. So temps they are showing are 83 and 76 respectively.
Anyway, last paragraph was kinda offtopic. I was just trying to elaborate what sensors are best to use. I propose second ones, they are showing the highest temperatures of the graphic cards. I could finally throw away that afterburner temps from my tray.

It's the first one that's the core temperature though. Not sure what the rest are.

Quote from: 5tr1k3r on June 21, 2011, 11:41:11 PM

About drop-down menu after "Pause mining when GPU ..." — I happen to have three options for this: 0, second 0 and 3. Though I have two cards o,o

Huh, might be an extra space in your INI file or something, since OCL.dll clearly will only detect 2 cards, and it's not reporting a conflict in number of GPUs.

Quote from: 5tr1k3r on June 21, 2011, 11:41:11 PM

About clocks tab: I didn't quite get why do I have to click "Clock speed" every time I want to apply changes :) Same for "Fan speed". What about "Save settings" concept?

I did that for clock speeds in 1.7.

Quote from: huayra.agera on June 22, 2011, 07:05:53 AM

BIOS limit is just that, BIOS limit :-\. Don't know how to bypass it. When trying to OC past it, the DLL/driver should have just tossed an error, and reset the clocks to the OC before BIOS limit.
Not sure about the BSOD thing, it might be fighting with Afterburner. Try not using more than one tool to OC.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: huayra.agera on June 22, 2011, 11:40:50 PM

;)
No problem! Stock OC still is great and stable and should be safer. Thanks!

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: mjsbuddha on June 23, 2011, 12:47:35 AM

put the contents of the folder in my poclbm folder and get error "Line 8609 Error: Subscript used with non-Array variable"

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: Departure on June 23, 2011, 02:37:57 AM

awsome work love the features, it is the best front end for mining on windows with a dedicated box, Just some ideas...
can you make the OSD optional? and have a "summary" tab? the device selection box needs to be wider(drop down). it would be nice to have each client and GPU together in 1 or make the windows border expandable. For some weird reason I get 10 MH/s slower with this than GUIminer on each GPU, Using all the same phoenix riser version and the same settings. If I even get this worked out why I would use this full time.

//Edit

Is there any reason this is slower than GUIminer? I placed it in the GUIminer folder which has phoenix ect.. with all the same settings it was atleast 10 MH/s slower for each GPU

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: Waltibaba on June 23, 2011, 09:35:45 AM

Hi
First off, I LOVE your program! switched from guiminer and never looked back.
I have a problem with OC settings though, both with catalyst set to startup or not, aoclbf won't retain or apply OC settings (at startup).
Its a great tool for OCing, especially since I'm running a 6950 and a 5830 in one machine and have had loads of problems with the setup, until you added the GPU settings tab... hewever even when I get a stable OC manually set in aoclbf, apply and accept "set clocks on startup" box, it won't apply on a PC restart.
I'm running 1.71 btw.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 23, 2011, 04:03:24 PM

Quote from: Departure on June 23, 2011, 02:37:57 AM

Try looking into the launch parameters in aoclbf.log and see if you're missing anything.

Quote from: Waltibaba on June 23, 2011, 09:35:45 AM

Check that you do have clocks.ini in the same folder. It should have created when applying clock speeds. Also, make sure that "startup=true" for all of them.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: zimpixa on June 23, 2011, 06:21:02 PM

1. Need option to select miner please.
2. Convert speed of poclbm to Mhash (string to integer, value divided by 1000, integer to string)

Also, when share is submitted in poclbm speed at OSD is wrong (it needs some way to remember last displayed value and displays it when share accepted ( not when connection problems)).

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 23, 2011, 10:57:50 PM

1.72. Apparently device ID changes every time restarts occur. Now uses OS index.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: magicrat80 on June 24, 2011, 12:33:27 AM

Having a few issues with AOCLBF.

I've downloaded Pheonix 1.50 and placed/extracted into a AOCLBF folder
I've downloaded POCLBM 20110428 and placed/extracted into a AOCLBF folder
I've downlaoded AOCLBF 1.71 and placed/extracted into a AOCLBF folder

Upon starting AOCLBF it asks how many clients I would like to create. Input 1 and hit okay.
Then I get AutoIT Error

Line 8689 (File "C:\aoclbf\aoclbf 1.71.exe")
Error: Array variable subscript badly formatted.

I've looked through the release topic to find other people had similiar issues but not exactley the same.
I tried everything that they stated would fix the other error messages but no dice.

My system specs:
Windows 7 64bit
4GB Ram
Sapphire ATI HD5830
Catalyst 11.5
ATI SDK 2.4
Afterburner

Currently running GUIMiner and pheonix perfectly. Have closed GUIminer and Afterburner and still no dice.
I'm using the executable from the mediafire link (which I figure is the 32bit version) yet it is said to still
work on 64bit Windows.

Since I had no luck with that I looked at compiling myself.

Downloaded AutoIT and compiled AOCLBF myself but needed an include called _processlistfunctions.au3.
After some googling, found the source and put it inside the Includes folder (under the AutoIT directory).
Here's the link for those who need it.

http://sites.google.com/site/ascend4ntscode/processfunctions (http://sites.google.com/site/ascend4ntscode/processfunctions)

After doing that, compiled the 1.71 version without the X64 tick box and got a new error

Line 7912 (File "C:\aoclbf\aoclbf.exe"):
Error: Array variable subscript badly formatted.

Tried this with the X64 (which is apparantley broken since v1.4) and got this error message

Line 7832 (File "C:\aoclbf\aoclbf.exe"):
Error: Subscript used with non-Array variable.

So, still no luck but maybe someone else out there has a solution. Can anyone help?

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 24, 2011, 01:46:55 AM

Open .au3 to edit, hit F5. Do whatever (e.g. create clients). It should show exactly where it's crashing in the console log.
By the way, is this happening in both 1.7x and 1.5?

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: magicrat80 on June 24, 2011, 02:03:37 AM

Thanks for the reply. Here's the console response from within AutoIt

>"C:\Program Files (x86)\AutoIt3\SciTE\..\autoit3.exe" /ErrorStdOut "C:\aoclbf\aoclbf 1.71.au3"
C:\aoclbf\aoclbf 1.71.au3 (2044) : ==> Array variable subscript badly formatted.:
dim $plevels[$numberofperformancelevels][3]
dim $plevels[^ ERROR
>Exit code: 1 Time: 6.397

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 24, 2011, 02:29:49 AM

Hm, I added in a bit of debugging in this version: http://www.mediafire.com/?khssfhsrczgr3aa
Mind trying that, then posting the log (with personal info removed, if there are any)?

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: chaud on June 24, 2011, 02:37:55 AM

A tab that showed the raw console output would be great, as well as showing the hash rate/accepted/rejected info somewhere on the window. I remote desktop in during the day to check on things, and the overlay isn't as easy to deal with as the info in a window.

Also, is there a way to turn off the OSD?

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: magicrat80 on June 24, 2011, 02:42:04 AM

Here's the log:

06/24/2011 12:33:20 Killed all orphan Phoenix/POCLBM processes.
06/24/2011 12:33:20 Loaded ADL DLL.
06/24/2011 12:33:20 Retrieved OpenCL device list containing 1 GPUs.
06/24/2011 12:33:20 Initialized ADL.
06/24/2011 12:33:20 Retrieved ADL GPU list containing 2 GPUs.
06/24/2011 12:33:20 GPU list created.
06/24/2011 12:33:20 Tray icon created.
06/24/2011 12:33:22 Drawing 1 clients.
06/24/2011 12:33:22 Resized client information arrays.
06/24/2011 12:33:22 Created OSDs.
06/24/2011 12:33:22 GUI window created.
06/24/2011 12:33:22 Created client GUI elements.
06/24/2011 12:33:22 Resized GPU information arrays.
06/24/2011 12:33:22 Retrieved clocks and voltage ranges for adapter 0.
06/24/2011 12:33:22 Retrieved clocks and voltage ranges for adapter 3.
06/24/2011 12:33:22 Created GPU GUI elements.
06/24/2011 12:33:22 Retrieved current clocks and voltage for adapter 0.
06/24/2011 12:33:22 Retrieved fan speed for adapter 0.
06/24/2011 12:34:32 Killed all orphan Phoenix/POCLBM processes.
06/24/2011 12:34:32 Loaded ADL DLL.
06/24/2011 12:34:32 Retrieved OpenCL device list containing 1 GPUs.
06/24/2011 12:34:32 Initialized ADL.
06/24/2011 12:34:32 Retrieved ADL GPU list containing 2 GPUs.
06/24/2011 12:34:32 GPU list created.
06/24/2011 12:34:32 Tray icon created.
06/24/2011 12:34:34 Drawing 1 clients.
06/24/2011 12:34:34 Resized client information arrays.
06/24/2011 12:34:34 Created OSDs.
06/24/2011 12:34:34 GUI window created.
06/24/2011 12:34:35 Created client GUI elements.
06/24/2011 12:34:35 Resized GPU information arrays.
06/24/2011 12:34:35 Retrieved clocks and voltage ranges for adapter 0.
06/24/2011 12:34:35 Retrieved clocks and voltage ranges for adapter 3.
06/24/2011 12:34:35 Created GPU GUI elements.
06/24/2011 12:34:35 Retrieved current clocks and voltage for adapter 0.
06/24/2011 12:34:35 Retrieved fan speed for adapter 0.
06/24/2011 12:35:09 Killed all orphan Phoenix/POCLBM processes.
06/24/2011 12:35:09 Loaded ADL DLL.
06/24/2011 12:35:10 Retrieved OpenCL device list containing 1 GPUs.
06/24/2011 12:35:10 Initialized ADL.
06/24/2011 12:35:10 Retrieved ADL GPU list containing 2 GPUs.
06/24/2011 12:35:10 GPU list created.
06/24/2011 12:35:10 Tray icon created.
06/24/2011 12:35:11 Drawing 1 clients.
06/24/2011 12:35:11 Resized client information arrays.
06/24/2011 12:35:12 Created OSDs.
06/24/2011 12:35:12 GUI window created.
06/24/2011 12:35:12 Created client GUI elements.
06/24/2011 12:35:12 Resized GPU information arrays.
06/24/2011 12:35:12 Retrieved clocks and voltage ranges for adapter 0.
06/24/2011 12:35:12 Retrieved clocks and voltage ranges for adapter 3.
06/24/2011 12:35:12 Created GPU GUI elements.
06/24/2011 12:35:12 Retrieved current clocks and voltage for adapter 0.
06/24/2011 12:35:12 Retrieved fan speed for adapter 0.

Hope that helps. Got error on line 8706 this time if that helps.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: huayra.agera on June 24, 2011, 03:30:40 AM

I know I would be asking too much but would it be great if you could include in your package the "miners" (Poclbm with phatk / Phoenix 1.50). I also checked there is a new version of Poclbm : https://github.com/m0mchil/poclbm. A fusion of your frontend plus the miners in one package would be great so that it would be an extract and run configure mine approach. You can just put a link of your front end as standalone, and the other link for the package with miners.

I 2nd the motion for a console like tab as well as a summary tab (what is shown in OSD shown in Summary tab instead) where in we can run the clients without the need to switch to tabs (for multiple gpus). OSD disable as well. A one button run or autostart at program launch would be great.

Thanks for all the hard work! ;D

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 24, 2011, 03:35:36 AM

Quote from: magicrat80 on June 24, 2011, 02:42:04 AM

06/24/2011 12:35:10 Retrieved OpenCL device list containing 1 GPUs.
06/24/2011 12:35:10 Initialized ADL.
06/24/2011 12:35:10 Retrieved ADL GPU list containing 2 GPUs.

Hope that helps. Got error on line 8706 this time if that helps.

Weird. Haven't seen this before. Just one 5830, right?

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: magicrat80 on June 24, 2011, 03:51:32 AM

CPU: AMD Phenom II X6 1075T (6 cores)
Motherboard: ASRock 890GX-Extreme3 890G
Video Card: Sapphire ATI HD5830 1GB

Motherboard does have Integrated AMD Radeon HD 4290.

Output for computer is using HD5830's HDMI port with nothing connected to the onboard GPU.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 24, 2011, 04:03:50 AM

Try this: http://www.mediafire.com/?czuc36kt1zzt79p
By the way, did you ever have the 5830 plugged into another PCI-E slot?

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: magicrat80 on June 24, 2011, 04:39:17 AM

Thanks so much for that. It actually works.
GPU has never been in another PCI-E slot.
I imagine it was something to do with the onboard video.
Thanks for taking the time to look at the issue too.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 24, 2011, 04:44:39 AM

I just took a wild stab and guessed that it has something to do with an adapter being present or not, but yeah, looks like it has to do with that on-board.

1.73 is just that. Oh, and added a little logging.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: magicrat80 on June 24, 2011, 05:24:32 AM

Quote from: Waltibaba on June 23, 2011, 09:35:45 AM

In regards to the slower MH/s, I found after just playing around and setting it up for the first time that AOCLBF takes first preference to default to POCLBM so it may be doing that. I removed PCOLBM and it defaulted to PHOENIX which gave me heaps better MH/s. I had to manually set the FLAGS for BFI_INT (Couldn't choose even though I've got a 5830) and gave it a "-v" aswell. Can't remember what the -v does but I've always used it (might be for VECTORS which I have ticked but not 100% sure as I'm away from that computer). So try removing POCLBM, restart the program and you might see faster speeds (unless you have already done that)

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: Departure on June 24, 2011, 09:33:19 AM

Newest version is weird 1.73

It detects my GPU's but doesn't detect the device for tabs and temps..

example

[1] cayman
[2] cayman
[3] cayman
[4] cayman

Then in GPU temp monitoring it has 0, 0, 5 last version had 0, 0, 5, 10, 12 I assumed and always have assumed one of the 0's is the processor or something, anyway It is only showing 2 tabs now instead of 4, it shows for device 0 and 5, it use to show tabs for 0, 5, 10 and 12

Im using 2 x 6990's (4 GPU's)

wanring message was "Found 4 OpenCL Devices But ADL Detected 2 devices, Please notify and set GPU number manually" thats all fine I can live with that but I can't set the GPU temp monitor if the device number doesn't show up for the missing 2 devices...

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 24, 2011, 04:00:44 PM

It's a temporary fix for people who were having trouble with it crashing when detecting GPUs (with on-board ones). For now, just use 1.72/1.74a.

Oh, mind posting the log file? The part regarding GPUs.

Quote from: magicrat80 on June 24, 2011, 04:39:17 AM

Thanks so much for that. It actually works.
GPU has never been in another PCI-E slot.
I imagine it was something to do with the onboard video.
Thanks for taking the time to look at the issue too.

If you won't mind, try testing 1.74a for GPU detection.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: Departure on June 24, 2011, 06:03:29 PM

Code:

06/24/2011 17:30:44 Killed all orphan Phoenix/POCLBM processes.
06/24/2011 17:30:44 Loaded ADL DLL.
06/24/2011 17:30:45 Retrieved OpenCL device list containing 4 GPUs.
06/24/2011 17:30:45 Initialized ADL. Found 14 adapters.
06/24/2011 17:30:45 Retrieved ADL GPU list containing 2 GPUs.
06/24/2011 17:30:45 GPU list created.
06/24/2011 17:30:45 Tray icon created.
06/24/2011 17:30:48 Drawing 4 clients.
06/24/2011 17:30:48 Resized client information arrays.
06/24/2011 17:30:48 Created OSDs.
06/24/2011 17:30:48 GUI window created.
06/24/2011 17:30:49 Created client GUI elements.
06/24/2011 17:30:49 Resized GPU information arrays.
06/24/2011 17:30:49 Retrieved clocks and voltage ranges for adapter 0.
06/24/2011 17:30:49 Retrieved clocks and voltage ranges for adapter 5.
06/24/2011 17:30:49 Created GPU GUI elements.
06/24/2011 17:30:49 Retrieved current clocks and voltage for adapter 0.
06/24/2011 17:30:49 Retrieved fan speed for adapter 0.
06/24/2011 17:30:49 Retrieved current clocks and voltage for adapter 5.
06/24/2011 17:30:49 Retrieved fan speed for adapter 5.
06/24/2011 17:30:49 GUI drawing completed.
06/24/2011 17:30:49 Loaded settings.

OpenCl found 4 and ADL found 2...

Thanks for your fast response, I will try out version 1.74a and if you need a test machine which has 4 GPU's I would be more than happy to do what ever you require..

//Edit
Tested 1.74a and works as before < 1.73 showing 4 tabs (1 for each GPU)
many thanks for your work and effort...

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: zimpixa on June 24, 2011, 06:14:50 PM

Tried your tool with old poclbm, poclbm with phatk and phoenix 1.5.

Results:
All worked fine, but none of programs want work with 2.1 SDK (I have also installed 2.4 SDK), even when old poclbm is working fine on 2.1 SDK.

Second thing - when using old poclbm with same settings as via cmd or Guiminer I'm getting worse results. Its connected somehow with GPU usage, which was about 10% lower. Other programs had same issue (huge GPU throtling (up to 40%) compared to about 5% of Guiminer/cmd). I'm not sure, if its miners itself (phoenix and poclbm with phatk), cuz I didnt checked it via console, but I assume that its same issue as with old poclbm.

BTW got any idea, why miners are so much throthled down?

XP sp3 32 bit
C2D E7400 @2.8GHz
5850Xtreme as main
5870Vapor as second card
Settings old poclbm
5850X- -v -f30 -r5 SDK 2.1 (380MHash)
5870 - -v -f2 -r5 SDK 2.1 (421MHash)
Settings poclbm with phatk
5850X- -v -f30 -r5 SDK 2.4 (max 380MHash, avg 350MHash)
5870 - -v -f2 -r5 SDK 2.4 (max 415MHash, avg 405MHash)
Settings phoenix 1.5
5850X- VECTORS AGG=10 BFI_INT FASTLOOP=false (avg 320MHash)
5870 - VECTORS AGG=12 BFI_INT FASTLOOP=false (avg 390MHash)

Everywhere worksize - 256

Hope I helped somehow in testing.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 24, 2011, 06:40:42 PM

I remember hearing that there's an argument where you can specify which SDK you want to use.
Not sure about the speed difference. Could be heat, could be CPU bottleneck (doubt it), could be external tool limiting performance (check GPU usage).

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: zimpixa on June 24, 2011, 07:26:07 PM

Argument - platform - tried (otherwise it wouldnt start). But AOCLPM finds GPU as idle (compared to 370MHash on Guiminer with same settings and platform)
Heat - 62C lower card, 71C higher ( when it was alone i had it working at 76C with higher clocks)
Nothing is limiting performance, cuz when only one of cards is working its 99% usage all time.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 25, 2011, 12:49:50 AM

Were you using "--platform=PLATFORMID" for POCLBM and "PLATFORM=PLATFORMID" for Phoenix, where PLATFORMID is an index number (like Device Number)?
There's also a log file that shows what flags are being used to launch.

Yeah, it seems like that's the difference between SDKs (some guy sees about 10% difference between 2.1 and 2.4).

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: Departure on June 25, 2011, 06:36:18 AM

K new problem kinda...

Just tried with 6 GPU's running 11.6 drivers, It detects them in Temps and creates the correct amount of tabs per GPU(6) but now in the select device it only shows 4 of the 6 GPU's..

I know its possible because GUIminer detects all 6 in the select device and they all run, But GUIminer doesn't have the features you have with temp monitoring ect.. IF possible can we get an update for detecting the selected device?

Example ....
.[0] cayman
.[1] cayman
.[2] cayman
.[3] cayman

but shows 6 tabs and has all the GPUs in temp selection 0,0,5,10,12,14,15 ofcause one of these is the CPU.

it should show...

.[0] cayman
.[1] cayman
.[2] cayman
.[3] cayman
.[4] cayman
.[5] cayman

Thanks for your great effort and work ...

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 25, 2011, 06:55:19 AM

Try running this and pasting the output. http://www.mediafire.com/?p9i80it24z879d6
It probably has to do with the Windows limit on number of OpenCL GPUs. If you feel like it, you can try going to a much older version and putting in the Device Number manually, and see if it runs on all 6.

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: Departure on June 25, 2011, 07:12:26 AM

Code:

Platform 1 information: FULL_PROFILE
Platform 1 information: OpenCL 1.1 AMD-APP-SDK-v2.4 (650.9)
Platform 1 information: AMD Accelerated Parallel Processing
Platform 1 information: Advanced Micro Devices, Inc.
Platform 1 information: cl_khr_icd cl_amd_event_callback cl_amd_offline_devices cl_khr_d3d10_sharing
 Device 1 number: 40647040
 Device 1 vendor ID: 4098
 Device 1 information: Cayman
 Device 1 information: Advanced Micro Devices, Inc.
 Device 1 information: CAL 1.4.1417 (VM)
 Device 1 information: FULL_PROFILE
 Device 1 information: OpenCL 1.1 AMD-APP-SDK-v2.4 (650.9)
 Device 1 information: 
 Device 2 number: 74708088
 Device 2 vendor ID: 4098
 Device 2 information: Cayman
 Device 2 information: Advanced Micro Devices, Inc.
 Device 2 information: CAL 1.4.1417 (VM)
 Device 2 information: FULL_PROFILE
 Device 2 information: OpenCL 1.1 AMD-APP-SDK-v2.4 (650.9)
 Device 2 information: 
 Device 3 number: 40919024
 Device 3 vendor ID: 4098
 Device 3 information: Cayman
 Device 3 information: Advanced Micro Devices, Inc.
 Device 3 information: CAL 1.4.1417 (VM)
 Device 3 information: FULL_PROFILE
 Device 3 information: OpenCL 1.1 AMD-APP-SDK-v2.4 (650.9)
 Device 3 information: 
 Device 4 number: 40923264
 Device 4 vendor ID: 4098
 Device 4 information: Cayman
 Device 4 information: Advanced Micro Devices, Inc.
 Device 4 information: CAL 1.4.1417 (VM)
 Device 4 information: FULL_PROFILE
 Device 4 information: OpenCL 1.1 AMD-APP-SDK-v2.4 (650.9)
 Device 4 information: 
iSize: 0. iAdapterIndex: 0. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&380CAED&0&00200018A. iBusNumber: 7. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY6. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{1E8FC556-5060-4540-8CE1-FB3003307E1A}\0000. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0006. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&380CAED&0&00200018. iOSDisplayIndex: 5.
iSize: 0. iAdapterIndex: 1. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&380CAED&0&00200018&02A. iBusNumber: 7. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY7. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{1E8FC556-5060-4540-8CE1-FB3003307E1A}\0001. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0006. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&380CAED&0&00200018&02. iOSDisplayIndex: 6.
iSize: 0. iAdapterIndex: 2. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&380CAED&0&00200018&03A. iBusNumber: 7. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY8. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{1E8FC556-5060-4540-8CE1-FB3003307E1A}\0002. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0006. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&380CAED&0&00200018&03. iOSDisplayIndex: 7.
iSize: 0. iAdapterIndex: 3. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&380CAED&0&00200018&04A. iBusNumber: 7. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY9. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{1E8FC556-5060-4540-8CE1-FB3003307E1A}\0003. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0006. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&380CAED&0&00200018&04. iOSDisplayIndex: 8.
iSize: 0. iAdapterIndex: 4. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&380CAED&0&00200018&05A. iBusNumber: 7. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY10. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{1E8FC556-5060-4540-8CE1-FB3003307E1A}\0004. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0006. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&380CAED&0&00200018&05. iOSDisplayIndex: 9.
iSize: 0. iAdapterIndex: 5. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&BB5CB9D&0&00200010A. iBusNumber: 3. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY1. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{D6E4F12C-607D-437E-BDB0-BAB3C3284CA9}\0000. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0000. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&BB5CB9D&0&00200010. iOSDisplayIndex: 0.
iSize: 0. iAdapterIndex: 6. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&BB5CB9D&0&00200010&02A. iBusNumber: 3. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY2. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{D6E4F12C-607D-437E-BDB0-BAB3C3284CA9}\0001. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0000. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&BB5CB9D&0&00200010&02. iOSDisplayIndex: 1.
iSize: 0. iAdapterIndex: 7. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&BB5CB9D&0&00200010&03A. iBusNumber: 3. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY3. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{D6E4F12C-607D-437E-BDB0-BAB3C3284CA9}\0002. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0000. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&BB5CB9D&0&00200010&03. iOSDisplayIndex: 2.
iSize: 0. iAdapterIndex: 8. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&BB5CB9D&0&00200010&04A. iBusNumber: 3. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY4. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{D6E4F12C-607D-437E-BDB0-BAB3C3284CA9}\0003. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0000. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&BB5CB9D&0&00200010&04. iOSDisplayIndex: 3.
iSize: 0. iAdapterIndex: 9. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&BB5CB9D&0&00200010&05A. iBusNumber: 3. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY5. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{D6E4F12C-607D-437E-BDB0-BAB3C3284CA9}\0004. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0000. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&BB5CB9D&0&00200010&05. iOSDisplayIndex: 4.
iSize: 0. iAdapterIndex: 10. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&DF11A96&0&00200058A. iBusNumber: 13. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY11. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{4D86D783-151D-46CB-B94B-A3E500BC429E}\0000. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0001. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&DF11A96&0&00200058. iOSDisplayIndex: 10.
iSize: 0. iAdapterIndex: 11. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&DF11A96&0&00200058&02A. iBusNumber: 13. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY12. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{4D86D783-151D-46CB-B94B-A3E500BC429E}\0001. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0001. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&DF11A96&0&00200058&02. iOSDisplayIndex: 11.
iSize: 0. iAdapterIndex: 12. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&DF11A96&0&00200058&03A. iBusNumber: 13. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY13. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{4D86D783-151D-46CB-B94B-A3E500BC429E}\0002. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0001. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&DF11A96&0&00200058&03. iOSDisplayIndex: 12.
iSize: 0. iAdapterIndex: 13. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&DF11A96&0&00200058&04A. iBusNumber: 13. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY14. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{4D86D783-151D-46CB-B94B-A3E500BC429E}\0003. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0001. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&DF11A96&0&00200058&04. iOSDisplayIndex: 13.
iSize: 0. iAdapterIndex: 14. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00_6&DF11A96&0&00200058&05A. iBusNumber: 13. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: \\.\DISPLAY15. iPresent: 1. iExist: 1. strDriverPath: \Registry\Machine\System\CurrentControlSet\Control\Video\{4D86D783-151D-46CB-B94B-A3E500BC429E}\0004. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0001. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_0B2A1002&REV_00\6&DF11A96&0&00200058&05. iOSDisplayIndex: 14.
iSize: 0. iAdapterIndex: 15. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_1B2A1002&REV_00_6&193BA404&0&00400058A. iBusNumber: 14. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: . iPresent: 0. iExist: 1. strDriverPath: {7E3EE459-887D-4808-B99E-1AB0E309143F}. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0003. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_1B2A1002&REV_00\6&193BA404&0&00400058. iOSDisplayIndex: 0.
iSize: 0. iAdapterIndex: 16. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_1B2A1002&REV_00_6&193BA404&0&00400058&02A. iBusNumber: 14. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: . iPresent: 0. iExist: 1. strDriverPath: {7E3EE459-887D-4808-B99E-1AB0E309143F}. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0003. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_1B2A1002&REV_00\6&193BA404&0&00400058&02. iOSDisplayIndex: 0.
iSize: 0. iAdapterIndex: 17. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_1B2A1002&REV_00_6&6B422F&0&00400010A. iBusNumber: 4. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: . iPresent: 0. iExist: 1. strDriverPath: {F5B40C2D-CFD8-43C0-AD7C-06D75C9E48A7}. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0002. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_1B2A1002&REV_00\6&6B422F&0&00400010. iOSDisplayIndex: 0.
iSize: 0. iAdapterIndex: 18. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_1B2A1002&REV_00_6&6B422F&0&00400010&02A. iBusNumber: 4. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: . iPresent: 0. iExist: 1. strDriverPath: {F5B40C2D-CFD8-43C0-AD7C-06D75C9E48A7}. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0002. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_1B2A1002&REV_00\6&6B422F&0&00400010&02. iOSDisplayIndex: 0.
iSize: 0. iAdapterIndex: 19. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_1B2A1002&REV_00_6&7C9BE81&0&00400018A. iBusNumber: 8. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: . iPresent: 0. iExist: 1. strDriverPath: {4DE4225B-8C6B-45E9-A0EE-A83189C36F7C}. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0005. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_1B2A1002&REV_00\6&7C9BE81&0&00400018. iOSDisplayIndex: 0.
iSize: 0. iAdapterIndex: 20. strUDID: PCI_VEN_1002&DEV_671D&SUBSYS_1B2A1002&REV_00_6&7C9BE81&0&00400018&02A. iBusNumber: 8. iDeviceNumber: 0. iFunctionNumber: 0. iVendorID: 1002. strAdapterName: AMD Radeon HD 6990. strDisplayName: . iPresent: 0. iExist: 1. strDriverPath: {4DE4225B-8C6B-45E9-A0EE-A83189C36F7C}. strDriverPathExt: {4d36e968-e325-11ce-bfc1-08002be10318}\0005. strPNPString: PCI\VEN_1002&DEV_671D&SUBSYS_1B2A1002&REV_00\6&7C9BE81&0&00400018&02. iOSDisplayIndex: 0.

As you can see it has something to do with OpenCL but yet GUIminer detects this and im sure he uses the OpenCl API's as the vendor names match... ADL seems to detect them. I did small test with Delphi as I code in delphi to see if it detects using the OpenCl and it showed all 6 GPU's

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: lvlrdka22 on June 25, 2011, 04:17:02 PM

Can't help there. What the DLL detects is what it puts in the device list. Try a much older version where you can still put in Device Numbers manually, see if mining actually works.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: um0rion on June 25, 2011, 04:59:18 PM

Hey, great program, I switched from guiminer to this once the OSD info started showing up for me (for a while it wouldnt). One thing im wondering though, the text this shows when clients are mining looks terrible, it looks like the letters are bold, but it looks as if there is a white shadow around each letter. Black looks great on a white background, but white on a white background leaves a bluish "residue" where the text would be, red on a black background has a white shadow to all the letters, green on black has the same white shadow, as does the blue on black background. Is this just me, or?

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: lvlrdka22 on June 25, 2011, 07:26:38 PM

Fine. 1.74b. Bold removed.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: yigga on June 25, 2011, 08:39:06 PM

NICE ONE!

thanks for this awsome miner!

Title: Re: AOCLBF (was Phoenix Rising): Front End GUI to Phoenix/POCLBM
Post by: Departure on June 26, 2011, 02:21:16 AM

Quote from: lvlrdka22 on June 25, 2011, 04:17:02 PM

Can't help there. What the DLL detects is what it puts in the device list. Try a much older version where you can still put in Device Numbers manually, see if mining actually works.

Strange because the same OpenCl.dll detects 6 when using Delphi and GUIMiner also detects 6 and im he uses the OpenCL.dll for detection

But thanks anyway it is an awsome front end, I might have to try and make my own front end in delphi to support the 6 GPU's only problem is ADL kinda sucky in delphi and not much reference around for the functions and procedures in delphi ..

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: NANO on June 26, 2011, 08:10:49 AM

an option to see overall mhash/sec would be really great!

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: yigga on June 27, 2011, 11:20:24 AM

version 1.74b was working fine...
today it still works, but the hud doesnt show the MHash/s value

http://img151.imageshack.us/img151/5661/minerbug.jpg

well, i was messing with the kernel.cl from phonix, but even after putting it back to normal, the MHash value wont show correctly.

EDIT: it seems every now and then the hashrate appears for a couple of seconds (every 10 min or so)

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Jazkal on June 27, 2011, 02:23:31 PM

Bug Report:

When I run the EXE file, I get an Autoit error: "Subscript used with non-Array variable".

When I run the au3 file in scite (F5), I get the following error details:

Quote

>Running:(3.3.6.1):C:\Program Files (x86)\AutoIt3\autoit3_x64.exe "C:\aoclbf 1.74a\aoclbf\aoclbf 1.74a.au3"
C:\aoclbf 1.74a\aoclbf\aoclbf 1.74a.au3 (1870) : ==> Subscript used with non-Array variable.:
if $temp[0]=0 then
if $temp^ ERROR
->09:21:23 AutoIT3.exe ended.rc:1
>Exit code: 1 Time: 2.412

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Departure on June 27, 2011, 02:54:37 PM

I can mine with 6 GPU's with phoenix, poclbm ect.. its aoclbf just not detecting all 6, ADL detects all 6 tho which allows all 6 tabs to show..
anychance of just checking over your detecting code again, I have tested opencl.dll and it detects all 6

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: lvlrdka22 on June 27, 2011, 05:36:45 PM

Code:

#include <array.au3>
#include <memory.au3>

filedelete(@scriptdir & "\adlocl.log")

$dll=dllopen(@systemdir & "\opencl.dll")
$temp=dllcall($dll,"int","clGetPlatformIDs","uint",0,"ptr",0,"int*",0)
$platforms=dllstructcreate("uint platforms[" & $temp[3] & "]")
$temp=dllcall($dll,"int:stdcall","clGetPlatformIDs","uint",$temp[3],"ptr",dllstructgetptr($platforms),"ptr",0)
for $i=1 to dllstructgetsize($platforms)/4
	for $j=0x0900 to 0x0904
		$pbuf=dllstructcreate("char pbuf[100]")
		$temp=dllcall($dll,"int:stdcall","clGetPlatformInfo","uint",dllstructgetdata($platforms,1,$i),"uint",$j,"uint",dllstructgetsize($pbuf),"ptr",dllstructgetptr($pbuf),"ptr",0)
;~ 		consolewrite("Platform " & $i & " information: " & dllstructgetdata($pbuf,1) & @crlf)
		filewriteline(@scriptdir & "\adlocl.log","Platform " & $i & " information: " & dllstructgetdata($pbuf,1) & @crlf)
	next
	$devices=dllstructcreate("int device1;int device2;int device3;int device4;int device5;int device6;int device7;int device8;")
	$temp=dllcall($dll,"int:stdcall","clGetDeviceIDs","uint",dllstructgetdata($platforms,1,$i),"uint64",bitshift(1,-2),"uint",4,"ptr",dllstructgetptr($devices),"ptr",0)
	for $j=1 to dllstructgetsize($devices)/4
;~ 		if dllstructgetdata($devices,$j)<>0 then
;~ 			consolewrite(" Device " & $j & " number: " & dllstructgetdata($devices,$j) & @crlf)
			filewriteline(@scriptdir & "\adlocl.log"," Device " & $j & " number: " & dllstructgetdata($devices,$j) & @crlf)
			$deviceinfo=dllstructcreate("uint")
			$temp=dllcall($dll,"int:stdcall","clGetDeviceInfo","uint",dllstructgetdata($devices,$j),"uint",0x1001,"uint",dllstructgetsize($deviceinfo),"ptr",dllstructgetptr($deviceinfo),"uint*",0)
;~ 			consolewrite(" Device " & $j & " vendor ID: " & dllstructgetdata($deviceinfo,1) & @crlf)
			filewriteline(@scriptdir & "\adlocl.log"," Device " & $j & " vendor ID: " & dllstructgetdata($deviceinfo,1) & @crlf)
			for $k=0x102b to 0x1030
				$deviceinfo=dllstructcreate("char[100]")
				$temp=dllcall($dll,"int:stdcall","clGetDeviceInfo","uint",dllstructgetdata($devices,$j),"uint",$k,"uint",dllstructgetsize($deviceinfo),"ptr",dllstructgetptr($deviceinfo),"uint*",0)
;~ 				consolewrite(" Device " & $j & " information: " & dllstructgetdata($deviceinfo,1) & @crlf)
				filewriteline(@scriptdir & "\adlocl.log"," Device " & $j & " information: " & dllstructgetdata($deviceinfo,1) & @crlf)
			next
;~ 		endif
	next
next
dllclose($dll)

Copy/paste and run that. Let me know the output. It just attempts to read 8 devices without checking if device number is present.

Quote from: Jazkal on June 27, 2011, 02:23:31 PM

Bug Report:

When I run the EXE file, I get an Autoit error: "Subscript used with non-Array variable".

When I run the au3 file in scite (F5), I get the following error details:

Quote

You don't have ADL DLL registered in environment variables?

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Departure on June 27, 2011, 05:58:19 PM

~~I have never coded in Autoit so I don't have a compiler for it...~~

//edit

Code:

Platform 1 information: FULL_PROFILE
Platform 1 information: OpenCL 1.1 AMD-APP-SDK-v2.4 (650.9)
Platform 1 information: AMD Accelerated Parallel Processing
Platform 1 information: Advanced Micro Devices, Inc.
Platform 1 information: cl_khr_icd cl_amd_event_callback cl_amd_offline_devices cl_khr_d3d10_sharing
 Device 1 number: 59128160
 Device 1 vendor ID: 4098
 Device 1 information: Cayman
 Device 1 information: Advanced Micro Devices, Inc.
 Device 1 information: CAL 1.4.1417 (VM)
 Device 1 information: FULL_PROFILE
 Device 1 information: OpenCL 1.1 AMD-APP-SDK-v2.4 (650.9)
 Device 1 information: 
 Device 2 number: 77460624
 Device 2 vendor ID: 4098
 Device 2 information: Cayman
 Device 2 information: Advanced Micro Devices, Inc.
 Device 2 information: CAL 1.4.1417 (VM)
 Device 2 information: FULL_PROFILE
 Device 2 information: OpenCL 1.1 AMD-APP-SDK-v2.4 (650.9)
 Device 2 information: 
 Device 3 number: 59400176
 Device 3 vendor ID: 4098
 Device 3 information: Cayman
 Device 3 information: Advanced Micro Devices, Inc.
 Device 3 information: CAL 1.4.1417 (VM)
 Device 3 information: FULL_PROFILE
 Device 3 information: OpenCL 1.1 AMD-APP-SDK-v2.4 (650.9)
 Device 3 information: 
 Device 4 number: 59404416
 Device 4 vendor ID: 4098
 Device 4 information: Cayman
 Device 4 information: Advanced Micro Devices, Inc.
 Device 4 information: CAL 1.4.1417 (VM)
 Device 4 information: FULL_PROFILE
 Device 4 information: OpenCL 1.1 AMD-APP-SDK-v2.4 (650.9)
 Device 4 information: 
 Device 5 number: 0
 Device 5 vendor ID: 0
 Device 5 information: 
 Device 5 information: 
 Device 5 information: 
 Device 5 information: 
 Device 5 information: 
 Device 5 information: 
 Device 6 number: 0
 Device 6 vendor ID: 0
 Device 6 information: 
 Device 6 information: 
 Device 6 information: 
 Device 6 information: 
 Device 6 information: 
 Device 6 information: 
 Device 7 number: 0
 Device 7 vendor ID: 0
 Device 7 information: 
 Device 7 information: 
 Device 7 information: 
 Device 7 information: 
 Device 7 information: 
 Device 7 information: 
 Device 8 number: 0
 Device 8 vendor ID: 0
 Device 8 information: 
 Device 8 information: 
 Device 8 information: 
 Device 8 information: 
 Device 8 information: 
 Device 8 information:

:(
Thats really strange because everything else detects all 6 GPU's

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Jazkal on June 27, 2011, 06:11:13 PM

Quote from: lvlrdka22 on June 27, 2011, 05:36:45 PM

You don't have ADL DLL registered in environment variables?

I have no idea what the 'ADL DLL' is, so I couldn't tell you either way.

My PATH:

Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\WinMerge;C:\Program Files\Windows Imaging\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common\

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: lvlrdka22 on June 27, 2011, 07:03:52 PM

See if you have atiadlxx.dll in system32.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Jazkal on June 27, 2011, 07:23:20 PM

Quote from: lvlrdka22 on June 27, 2011, 07:03:52 PM

See if you have atiadlxx.dll in system32.

Not on the system I'm getting the error on.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Departure on June 28, 2011, 02:29:36 AM

snippet from GUIminer

Code:

def get_opencl_devices():
    """Return a list of available OpenCL devices.

    Raises ImportError if OpenCL is not found.
    Raises IOError if no OpenCL devices are found.
    """
    import pyopencl
    device_strings = []
    platforms = pyopencl.get_platforms() #@UndefinedVariable
    for i, platform in enumerate(platforms):
        devices = platform.get_devices()
        for j, device in enumerate(devices):
            device_strings.append('[%d-%d] %s' %
                (i, j, merge_whitespace(device.name)[:25]))
    if len(device_strings) == 0:
        raise IOError
    return device_strings

Returns all GPU's, I dont know if this helps in anyway due to a completly diffrent language and opencl headers... but anyway..

Also just to let you know aoclbf version 1.62 works when I type in Device numbers 0..5 when having 6 clients, so maybe you could update 1.62 to your latest fixes and leave the device number input to manually then it would be working for your latest fixes and support all amounts of GPU's

Once again thanks for your excellent work.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: lvlrdka22 on June 28, 2011, 07:01:07 AM

1.74. Updated to parse the newest classic POCLBM output. Added in an option to manually put in Device Number.

Quote from: Jazkal on June 27, 2011, 07:23:20 PM

Quote from: lvlrdka22 on June 27, 2011, 07:03:52 PM

See if you have atiadlxx.dll in system32.

Not on the system I'm getting the error on.

Yeah, therein lies the problem.

Quote from: Departure on June 28, 2011, 02:29:36 AM

snippet from GUIminer

Code:

def get_opencl_devices():
    """Return a list of available OpenCL devices.

    Raises ImportError if OpenCL is not found.
    Raises IOError if no OpenCL devices are found.
    """
    import pyopencl
    device_strings = []
    platforms = pyopencl.get_platforms() #@UndefinedVariable
    for i, platform in enumerate(platforms):
        devices = platform.get_devices()
        for j, device in enumerate(devices):
            device_strings.append('[%d-%d] %s' %
                (i, j, merge_whitespace(device.name)[:25]))
    if len(device_strings) == 0:
        raise IOError
    return device_strings

Added in a manual option.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Jazkal on June 28, 2011, 10:54:40 AM

Quote from: lvlrdka22 on June 28, 2011, 07:01:07 AM

Quote from: Jazkal on June 27, 2011, 07:23:20 PM

Quote from: lvlrdka22 on June 27, 2011, 07:03:52 PM

See if you have atiadlxx.dll in system32.

Not on the system I'm getting the error on.

Yeah, therein lies the problem.

Can I suggest you list ATI software as a requirement for the software, and add this code to the start of your app:

Code:

If Not FileExists(@SystemDir&"\atiadlxx.dll") Then MsgBox(0, "Error", "This application requires certain ATI DLL's to be installed on the system to function correctly (atiadlxx.dll).")

Or something like it.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: huayra.agera on June 28, 2011, 11:45:19 AM

I tried AOCLBF 1.74 with the new poclbm v06.27.2011 and the OSD shows "Stale shares unsupported" and the hashrate is in KiloHash. Maybe try to format with the original OSD display that you have in your previous versions.

Also, can you put like an "icon indicator" or added line in OSD showing if we are using either Phoenix or POCLBM. Thanks! :)

Oh, and UP for the summary/console page. :)

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Departure on June 28, 2011, 12:59:23 PM

Nice work.. I like that you input the device manually now, I even started to write my own front end based on your ideas, but now the new version supports all the GPU's I will be using this until I get motivated again to continue with my own front end (http://i52.tinypic.com/29viti.png) gets temps and phoenix output plus detects all GPU's, I love the inbuilt overclocking great work and thanks for the fast fix...

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: brunoshady on June 28, 2011, 03:29:42 PM

temp here is not showing right with 2 vga =(

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: NANO on June 28, 2011, 04:27:45 PM

Quote from: Departure on June 28, 2011, 12:59:23 PM

Im happy like Departure :)

BTW nice front end, hope you soon get motivated ;)

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Vwlopez3 on June 28, 2011, 05:37:40 PM

how are you guy using more than 4 gpu's? what os are you using?

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: 5tr1k3r on June 28, 2011, 06:29:16 PM

Please, add the option of hiding the OSD.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Departure on June 29, 2011, 01:49:01 AM

Quote from: Vwlopez3 on June 28, 2011, 05:37:40 PM

how are you guy using more than 4 gpu's? what os are you using?

Windows, 11.6 drivers and dummy plugs.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: c_k on June 29, 2011, 02:24:04 AM

Quote from: huayra.agera on June 28, 2011, 11:45:19 AM

^ this, if possible.

Also, is it just me or is the text bold again? It looks like it to me ???

Plus a link to this thread somewhere in the app, like an about button or something, would be neat :D

Great work however, keep it up! :o

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: FRanz33 on June 29, 2011, 04:21:17 AM

Any chance of Minimize on startup?

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: newunit16 on June 29, 2011, 12:04:45 PM

any chance to make "click through" reliable? id just prefer to always be able to move the damned status windows vs having to rely on random luck for them to actually be movable after clicking "click through".

p.s. you could have thought of a better name. AOCLBF is impossible to pronouonce. "AOK-LUB-EF"???

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: NANO on June 29, 2011, 05:36:13 PM

lol

yeah the name isnt very smart and easy xD

Please, try to put a OSD or something with info about overall mhash! ;)

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: lvlrdka22 on June 29, 2011, 07:58:17 PM

Quote from: newunit16 on June 29, 2011, 12:04:45 PM

p.s. you could have thought of a better name. AOCLBF is impossible to pronouonce. "AOK-LUB-EF"???

Quote from: NANO on June 29, 2011, 05:36:13 PM

lol

yeah the name isnt very smart and easy xD

QFT.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: dishwara on June 29, 2011, 09:12:52 PM

This time, core clock & mem clk saved. But fan speed not, also VDDC(not sure)
Fan speed is definitely need to be saved as slow running fan with high core clk with temp rise may kill the GPU.

I always set the fan speed to 100 or 75, depending on card & noise.

Also why the OSD stay on top?
Whatever window i open i see OSD on my right showing. Why changed from desktop only to all windows?

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: huayra.agera on June 30, 2011, 12:36:34 AM

I can add that the fan speed settings are not yet saved on the current version.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: NANO on June 30, 2011, 05:50:31 AM

All ok now with the manual entry for device ;)

Thanks!

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: jasonstx on July 01, 2011, 12:06:07 AM

Worth using just for the suspend on temperature. Good job so far.

One thing would be to change the text overlay to white with a black border, that would make it more visible.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: mattpker on July 01, 2011, 07:34:42 AM

How come my ATI Tray Tools can set unsupported clocks but this cannot? You also need to make is so it sets the fan speed on startup. Another great benefit is if it changed the clocks back to default if the application is exited. Unfortunately, I am going to have to continue to use ATI Tray Tools for my overclocking until these issues are resolved.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: huayra.agera on July 01, 2011, 09:25:19 AM

He mentioned he still couldn't get around the BIOS limit, hence the unsupported clocks or voltage adjustments.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Departure on July 01, 2011, 09:57:24 AM

this has some seriouse memory leakage, after around 30 hours of running time I decided to checking back on the system, OSD has disappeared and the memory usage for that running process was over 200mb of ram, this could be due to Phoenix also, depending how you monitor the Phoenix process.. anyway I still think its a great front end and even better that its free and we all appreciate your time and effort into making this for us to use.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: lvlrdka22 on July 01, 2011, 06:35:41 PM

Eh?
http://i56.tinypic.com/2z6ecjp.png

Side note, been working on this:
http://i54.tinypic.com/xmr1a1.png

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: dishwara on July 01, 2011, 08:49:40 PM

coooool

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: hennessy on July 01, 2011, 10:48:54 PM

GPU usage is not as maxed out as it could be compared to just running phoenix in console. Console only gives me always 99% load. With 3 workers I get 98-99% for each, 4 workers even worse, very unstable between 95-99%. Could it be cpu usage? AOCLBF uses up to 21% with 4 workers every two seconds, with 3 workers only up to 10%.

EDIT cpu usage of AOCLBF is even higher when using the temperature control in the overlay, goes up to 40% with 4 cards and reducing MHs rate from 294 to 291 :( My guess is that this is caused by the constant overlay update that is gathering data every second times 4. Can i somehow adjust the updating speed? Or how about a console view only.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: huayra.agera on July 02, 2011, 07:45:51 PM

AOCLBF 2.0 I guess? Pretty awesome! Can't wait for the release!

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: newunit16 on July 03, 2011, 01:57:14 AM

i second the console view only. or at least set time to update OSD. i found that the OSD can be moved "reliably", but you must have your pointer over the text pixels. this is tedious. perhaps a section of the OSD with "live pixels" to make it easily movable?

i use msi afterburner to "monitor" my temps. but i dig the built in functionality of miner pause on X temp. i know this could be achieved with multiple pieces of software, but i like the package this man has made.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: yigga on July 03, 2011, 10:25:50 AM

i'm using TechPowerUp GPU-Z 0.5.4 to get the data from the three sensors of each card.

As AOCLBF seems to get the correct data for my hd5850, it seems my 5770 temperature data is somehow displayed wrong by AOCLBF (man, a rename would be awsome as well ;))

any idea, why this is happening?
http://img19.imageshack.us/img19/8827/temp1a.jpg
http://img3.imageshack.us/img3/265/temp2e.jpg

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Departure on July 03, 2011, 02:29:12 PM

@lvlrdka22
I like the preview, not too interested in the trade thing personally, but OSD at the bottom looks a lot better than current one, Personally I would still prefer it in a summary tab and a total hash rate output would be great also. Also it would be nice to squeeze in an option for update time this does infact reduce MH/s when you are calling the function which gets temps ect.. so having an option to set how often it updates would come in useful. Great job keep up the excellent work.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Bloody Angel on July 04, 2011, 04:39:08 PM

First:

Thank you for the nice miner!

Second,

I have a question:

Is it possible to active logging when the miner is disonnected? If it's possible how can I activate it?

Thank you.

Bye Bloody

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: pandemic on July 05, 2011, 01:39:33 PM

What is work size?

edit: -w or --worksize controls the work group size. it defaults to the maximum value reported by the card and going above that will likely result in the miner crashing. there's no real hard and set rule for this and it varies from card to card, so find someone with your same card and ask, look at the mining hardware comparison for inspiration, or just poke in various values and look what happens to the hash rate.

:)

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: huayra.agera on July 08, 2011, 04:38:02 AM

Any updates on this awesome program? BTW, Catalyst 11.7+2.5OCL does not anymore require dummy plugs/crossfire bridges!

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: jkminkov on July 08, 2011, 06:32:35 AM

can we get a button that shifts between primary and backup pools manually

when running on backup pool, backup miner should not be stopped until some shares were accepted on primary pool, same way as poclbm handles backup pools

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: dishwara on July 08, 2011, 05:11:57 PM

I see a problem with version 1.74.
Adding new client causes all other old clients to loose HD5xxx, Fastloop, phatk, Aggression settings.
Even checking the check boxes again & save setting has no use.
Only way to solve is to edit the aoclbf.ini file manually & change 0 to 1.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: OldChap on July 09, 2011, 09:52:52 AM

Would one of you guys, that has this running properly, be kind enough to post a screenshot of the filestructure. That is to say one that shows which files should be in the same place as this .exe file.

I seem to be able to run this but it does not engage the card so maybe I am missing some file or it is in the wrong place.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: dishwara on July 09, 2011, 01:10:26 PM

Quote from: OldChap on July 09, 2011, 09:52:52 AM

Download phoenix 1.50 from phoenix page. Extract it to a folder. It will have phoenix.exe, phoenix.ini & kernel folder.
just copy the aoclbfxxx.exe, aoclbfxxx.au3, foreman.ico.
you can able to run aoclbf, then give mining details. It will create aoclbf.ini, aoclbf.log, clocks.ini...
screenshot
http://i54.tinypic.com/rt2cr6.jpg

EDIT:
Since you said its not engage the card, you may have not installed OpenCL properly.
google GPU caps viewer. It will tell clearly whether you have installed OpenCL or not.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: OldChap on July 09, 2011, 01:24:15 PM

Currently running on guiminer so I assumed that open CL would be good.??? I will double check my folder now and compare to yours.

Thanks for the help

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: huayra.agera on July 09, 2011, 06:23:47 PM

There is a new version of poclbm and they implemented a new syntax, I hope you can update aoclbf with their syntax since I've tried your foreman app with the new poclbm and it's not working. Thanks!

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: OldChap on July 10, 2011, 12:49:58 AM

Ok tried a fresh install on a different machine and even though some of the files you have (as above) are missing in mine, I now have one rig with one card up.

Somehow I expected the OSD to be bottom right...but top left works too. I will try out the extended features tomorrow.

Again dishwara, thanks for the help.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: dishwara on July 10, 2011, 07:45:13 AM

Quote from: OldChap on July 10, 2011, 12:49:58 AM

Just drag the OSD to bottom right & after u dragged click save settings.
If that fails, exit aoclbf & edit aoclbf.ini manually.
Add this line to last, after

device=1. Cypress
extraflags=
gpus=0
mintemp=
maxtemp=

Code:

[OSD1]
osdx=1426
osdy=678

x & y are pixels. Select depending on your monitor pixels. I have 1600*900 as resolution.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Rino on July 10, 2011, 09:19:28 AM

aoclbf guesses device numbers wrong on my system so ... reporting it.
i have #0 cpu and #1-3 gpus, aoclbf guesses gpus at #0-2

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: lvlrdka22 on July 10, 2011, 07:51:23 PM

Apparently one of the people who was testing my MtGox trading thing accused me of including a keylogger, so I won't be adding/releasing it.

Quote from: huayra.agera on July 09, 2011, 06:23:47 PM

There is a new version of poclbm and they implemented a new syntax, I hope you can update aoclbf with their syntax since I've tried your foreman app with the new poclbm and it's not working. Thanks!

Bleh fine.

Quote from: Rino on July 10, 2011, 09:19:28 AM

aoclbf guesses device numbers wrong on my system so ... reporting it.
i have #0 cpu and #1-3 gpus, aoclbf guesses gpus at #0-2

OpenCL has an option to read GPU list only, which is what it does.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: BrianH on July 10, 2011, 08:15:05 PM

Quote from: dishwara on July 08, 2011, 05:11:57 PM

Same problem.

All kinds of issues with mine.

-Using two 6950s, HD5xxx+, Fastloop, phatk and aggression settings are greyed out.
-Run/Stop is greyed out on the first client.
-Clicking run on the second does nothing, but causes a massive memory leak and the client is unable to close.

In short, I have never been able to get it working, so I am not sure what normal operation looks like. Is there any way to see how many Mhash/s each card is producing?

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: lvlrdka22 on July 10, 2011, 09:13:10 PM

Quote from: Departure on July 03, 2011, 02:29:12 PM

Eh, that's what it looks like when color depth is set to 16 bit (an old game I play requires that).

Quote from: yigga on July 03, 2011, 10:25:50 AM

It reads the first temperature (which is what GPU-z says is the core temperature, at least for my 5850s). Been too lazy to add the option to choose other temperature sensors.

Quote from: dishwara on July 08, 2011, 05:11:57 PM

Quote from: WiCKeD on July 10, 2011, 08:15:05 PM

Not sure what happened, but apparently these things got lost when I added POCLBM parsing, for absolutely no reason at all (that I can see).

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: pandemic on July 11, 2011, 03:26:30 PM

Well, this was working really well with CCC 11.7. I had my 5830 overclocked to 955.

I'm trying to resolve the CPU issue with CCC 11.6 so I uninstalled the drivers and loaded CCC 11.2.

For some reason now I'm having two issues.

1). In AOCLBF, when I overclock past 900mhz, I get "error setting clocks! Probably BIOS limit reached.
2). Even with the current default clocks, I press 'run' and it just idles at 0 mh/s

It appears that with 11.7, you can overclock a card higher in AOCLBF. I reinstalled 11.7 and now I can clock back at 955mhz.

still idle though, not sure what can be causing that.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: dishwara on July 11, 2011, 04:16:02 PM

Quote from: pandemic on July 11, 2011, 03:26:30 PM

give aggression 12 or something instead of "Aggression"

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: pandemic on July 11, 2011, 04:22:43 PM

Quote from: dishwara on July 11, 2011, 04:16:02 PM

Quote from: pandemic on July 11, 2011, 03:26:30 PM

give aggression 12 or something instead of "Aggression"

core: 955mhz
mem:300mhz
VDDC:1163 (stock)
Fan: 85%
Temp: 58-62c
Vectors, HD5xxx+, fastloop, phatk, agression=12, worksize=512

AOCLBF 1.75 with phoenix 1.50

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: dishwara on July 11, 2011, 05:16:29 PM

Since you installed 11.7, then 11.2 then again 11.7, some files may be corrupted, particularly OpenCL. Check out opencl is installed by using GPU caps viewer.
If it says & still you cant mine with directly using phoenix or poclbm or diablo miner, then better uninstall ati drivers fully, ONLY AFTER THAT, use driver sweeper to completely remove all the AMD by analyse & clean. You can do it in safe mode, so that it removes all drivers.
Then install again.
Also before doing that all, u can re install, AMD APP only, some times that too solves problem.

I have, in one HDD, after all the above steps still i cant mine. Only way seems for me is format.
I used 11.6 & 11.7 .

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: pandemic on July 11, 2011, 06:48:39 PM

Quote from: dishwara on July 11, 2011, 05:16:29 PM

Seems like that's exactly the issue. I just uninstalled and reinstalled 11.4. It works but the CPU is still huge and I can't overclock to 955mhz. Tried 11.2 earlier and it crashed. So it's looking like I'm going to uninstall and then go back to 11.7. Hopefully they resolve that CPU issue in the master release

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: iopq on July 12, 2011, 12:31:08 PM

This is a really annoying UI. The text fields actually get sent as parameters if you don't click on them. Really?

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: hennessy on July 12, 2011, 12:47:06 PM

Quote from: iopq on July 12, 2011, 12:31:08 PM

This is a really annoying UI. The text fields actually get sent as parameters if you don't click on them. Really?

Appreciate the work and time the developer has put into this software. Don't forget that he offers it for free. If you want to criticize, do it constructively...

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: um0rion on July 12, 2011, 09:26:49 PM

Ive got a feature request that I think would be pretty nice. Every now and then a site gets DDoS'd. If that site is your startup miner, it'll look for it, then wait the alotted time and retries, then switch the backup. A lot of times a site could be down for days. I have 1 popular pool (More likely to get DDoS'd, and a smaller pool as backup.

Would it be possible to: have a button to switch primary/backup pools on every miner, OR, have checkboxes to designate which of two pools to use as startup/backup? They're there now to say "do this on startup" and "use a backup pool" but maybe just use a simple check for the startup, and let the unchecked pool be the backup server by default? If you havent specified a backup pool and the main one goes down, you arent going to be mining anything, so if a pool goes down and searches for a null pool, the effect will be the same. Just my thoughts.

My main issue with this is that I have a windows system with 4x cards, and a pool like bitcoins.lc assigns worker names and passwords that are random. Clearing all the fields then re-entering them in the backup slot is time consuming, and if I ever want it the other way around, Ive got to spend another 10 minutes to swap them back.

OH ALSO: There seems to be a new and improved phatk kernel, can we get this implemented?
http://forum.bitcoin.org/index.php?topic=25860.0

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: iopq on July 13, 2011, 09:41:31 AM

Quote from: hennessy on July 12, 2011, 12:47:06 PM

Quote from: iopq on July 12, 2011, 12:31:08 PM

This is a really annoying UI. The text fields actually get sent as parameters if you don't click on them. Really?

Appreciate the work and time the developer has put into this software. Don't forget that he offers it for free. If you want to criticize, do it constructively...

I did do it constructively, I said the text fields get sent as parameters which is not the correct functionality, the default values should be sent, not the text

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: pandemic on July 15, 2011, 02:05:36 PM

Could you include affinity options in the next release? I'm having issues with phoenix using 50% CPU per GPU. By setting affinity to cpu1 (of 2) it'll use 100% of that core rather than 100% of both.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: smackdaddy on July 15, 2011, 05:21:53 PM

Quote from: pandemic on July 15, 2011, 02:05:36 PM

Could you include affinity options in the next release? I'm having issues with phoenix using 50% CPU per GPU. By setting affinity to cpu1 (of 2) it'll use 100% of that core rather than 100% of both.

Why would you want it to use 100% of both?

You realize the CPU usage is not a desired effect, which is why we have the affinity setting in the first place, to stack all the wasted CPU on a single core?

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: dishwara on July 15, 2011, 07:24:02 PM

Affinity is in 1.74 & 1.75 already.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: pandemic on July 16, 2011, 03:58:36 AM

Quote from: smackdaddy on July 15, 2011, 05:21:53 PM

Quote from: pandemic on July 15, 2011, 02:05:36 PM

Could you include affinity options in the next release? I'm having issues with phoenix using 50% CPU per GPU. By setting affinity to cpu1 (of 2) it'll use 100% of that core rather than 100% of both.

should probably re-read what I said.

I DO see affinity now. I don't know why I've never noticed it before. Thanks! :)

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: haploid23 on July 16, 2011, 04:25:00 AM

not sure if this has been covered before, but is there a way to disable the display output the runs on top of everything? either totally disable it, or have it run underneath every window

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: dishwara on July 16, 2011, 07:06:15 AM

Quote from: haploid23 on July 16, 2011, 04:25:00 AM

not sure if this has been covered before, but is there a way to disable the display output the runs on top of everything? either totally disable it, or have it run underneath every window

No. Also it seems developer out of home as he hasn't responded any one after the 1.75 release.
OSD running on top of every window is really annoying.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: paraipan on July 16, 2011, 03:27:36 PM

Impressive tool, will definitely recommend it to new miners :)

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: haploid23 on July 17, 2011, 07:47:10 PM

Quote from: dishwara on July 16, 2011, 07:06:15 AM

Quote from: haploid23 on July 16, 2011, 04:25:00 AM

not sure if this has been covered before, but is there a way to disable the display output the runs on top of everything? either totally disable it, or have it run underneath every window

No. Also it seems developer out of home as he hasn't responded any one after the 1.75 release.
OSD running on top of every window is really annoying.

hmm maybe it would help if we gave him a small tip to have options for this OSD? i like this pheonix rising better than the GUIminer, but it's just hard to put up with for your everyday machine. on dedicated miners, it's no problem though.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: FRanz33 on July 17, 2011, 11:24:42 PM

Actually ive discovered a way to hide the osd. Simply set the box outside the viewing area of the screen. You can set it manually in the config file or set you screen to a higher like say than usual resolution 1600x1200 then set the box in the outter most corner. When you resize the screen the OSD box will be there but beyond your view. I found it by accident moving my boxes around.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Endeavour79 on July 18, 2011, 05:11:17 AM

I've updated to Catalyst driver 11.7 (early version) and since I can't start 4 miners at the same time. The last miner is always not working..no matter which device I start last.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: hennessy on July 21, 2011, 07:23:02 AM

My two rigs were running for some days now, some minutes ago I got an error message "Error allocating memory" from AOC. Memory usage was 690MB. I had to kill and restart it. There is some kind of memory leak...

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: echo2 on July 22, 2011, 04:00:44 PM

umm can u make it support cgminer??

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: dewon on July 22, 2011, 08:12:28 PM

As someone stated earlier, its not really a big thing to move your OSD boxes outside/edges of viewing area. Once youre done watching your daily show, you can move them back in seconds.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Endeavour79 on July 23, 2011, 04:43:33 AM

Quote from: hennessy on July 21, 2011, 07:23:02 AM

I can confirm this. If you have a lot of switching between standard and backup server then AOCLBF eats up a lot of memory and crashes finally.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: haploid23 on July 24, 2011, 08:36:01 AM

Quote from: FRanz33 on July 17, 2011, 11:24:42 PM

thanks! i'll try this and report back if it works or not

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: rcocchiararo on July 28, 2011, 02:29:20 PM

Hi

im running this tool, and find it pretty good (my favourite so far, GUI or no GUI)

My only "issue" is that it does not remember fan settings, so i have to enable amd overdrive, and set fanspeeds with that.

If i set this to start on boot (putting its shortcur on the "startup" folder), it starts before AMD CCC, and sometimes hangs my pc.

If i start it from a script, wich i set to "sleep" for a few mminutes, so that everything else is loaded first, it never starts the miners. Both run and stop buttons remain greyed out. (if i manually start it from a script, with no sleep involved, it does the same thing, it wont work).

Any good ideas for starting this on boot, but only after everything else is set ?

thx

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Internet151 on July 29, 2011, 09:22:20 AM

Please for the love of god allow this app to change fan speed automatically when starting up the app.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: OldChap on July 31, 2011, 11:45:58 PM

Hi, Selecting openCL device with one card is working fine for me on rigs with 1 card

However whilst it also works fine with 1.74 and 2 cards, with 1.75 and 2 cards the issue seems to be that no matter what number I define manually the second card is not seen.

For temp monitoring there are 3 options: 0,0 and 3. Selecting 3 for the temp monitoring clearly shows the second card temps

Incidentally, selecting the 1. cypress option for the first card then the 0 option manually for the second runs both on one card.

Is there a file I can edit to cure this?

EDIT: Using 11.8 drivers, win7 64U and rolling back to 11.7 drivers and 1.74 on this machine did not help.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: dishwara on August 01, 2011, 06:09:42 AM

To those who want to control fan speed, since the developer of AOCLBF not available, you can use Clocktweak.
https://forum.bitcoin.org/index.php?topic=9982.0
It is not free, but the 20 cents you give is 100% worth.
I bought this software 2 months back & when i tried that time it didn't work, so abandoned.
But a week before again tried with the old file i downloaded & the developer gives FREE upgrades.
The tool perfectly over clocks & under clocks & also control fan speed. Besides it has power tune option, so you don't even need to install CCC(which is crap).
Check out the link above & control fan.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: huayra.agera on August 02, 2011, 04:26:03 PM

It's been a while here, seems the developer is busy with his other projects. Anyway, just to contribute to the community, for Windows users, Sapphire Trixx has version 4.0.2 up and it can control fan speeds as well. You can now also OC the cards individually for multi-gpu configs.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: RoadStress on August 04, 2011, 10:00:17 PM

How do you use this GUI with POCLBM and Phoenix in the same time? When i have the POCLBM.exe in the folder the settings for HD5xxx, Fastloop, phatk and aggresion are grayed out. If i delete the POCLBM.exe then i can use them.I want to mine with one client with POCLBM and another one phatk. How do i make the second client use phatk?(seems to run poclbm.exe even if phatk is checked but grayed out) Thank you.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: STP on August 05, 2011, 02:57:47 AM

Quote from: RoadStress on August 04, 2011, 10:00:17 PM

You can copy the source folder you run AOCLBF from to another instance and then just delete POCLBM from that directory and launch a new instance of AOCLBF from that directory. I did this when same thing happened to me. ;) Actually now I have many directories I run miners from with different patch levels for testing and such.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Kluge on August 06, 2011, 07:03:24 AM

Quote from: Endeavour79 on July 23, 2011, 04:43:33 AM

Quote from: hennessy on July 21, 2011, 07:23:02 AM

I can confirm this. If you have a lot of switching between standard and backup server then AOCLBF eats up a lot of memory and crashes finally.

I can confirm, too. Was having issues with a wireless repeater a while ago. All PCs were displaying "memory low" errors when I finally realized there was a problem.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: Endeavour79 on August 08, 2011, 06:59:25 AM

Switched to cgminer now..in combination with barely clocked. Everything runs very smooth.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: wind on August 08, 2011, 08:16:04 PM

welcome to my mod of AOCLBF https://bitcointalk.org/index.php?topic=32125.msg400922#msg400922
Some features were added such as dynamic overclocking, manual fanspeed on startup, extra info on OSD etc.
Donations are welcome ;)

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: cyberlync on August 11, 2011, 04:43:54 PM

Since the new PhatK kernels from Diapolo and Phateus are offering to use VECTORS2 and VECTORS4, how do you peeps go about using those in AOCLBF? Do I just UNtick the VECTORS box and type VECTORS2 or VECTORS4 in the "Extra Flags" box?

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: huayra.agera on August 11, 2011, 04:47:49 PM

You uncheck Vectors and under flags you type Vectors2 or vectors4. That worked for me.

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: CanaryInTheMine on August 12, 2011, 06:44:17 PM

have 2 6990s and 1 6870 card. I can OC the 6990 GPUs fine with this tool, but it's unable to change the memory setting on the 6870. any ideas why?

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: dishwara on August 13, 2011, 02:20:57 PM

http://i56.tinypic.com/332b3o7.jpg

Title: Re: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool
Post by: wind on August 16, 2011, 07:17:12 PM

Welcome to AOCLBF 1.81 by WinD (https://bitcointalk.org/index.php?topic=39697.0)! Now phoenix 1.6.x full compatible!

Bitcoin Forum

Bitcoin => Mining software (miners) => Topic started by: lvlrdka22 on May 28, 2011, 01:48:58 AM