magicrat80
Newbie
Offline
Activity: 17
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
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.
|
|
|
|
lvlrdka22 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 24, 2011, 04:44:39 AM Last edit: June 24, 2011, 05:08:45 AM by lvlrdka22 |
|
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.
|
|
|
|
magicrat80
Newbie
Offline
Activity: 17
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 24, 2011, 05:24:32 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.
//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
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)
|
|
|
|
Departure
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
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...
|
|
|
|
lvlrdka22 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 24, 2011, 04:00:44 PM Last edit: June 24, 2011, 04:17:05 PM by lvlrdka22 |
|
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. 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.
|
|
|
|
Departure
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 24, 2011, 06:03:29 PM |
|
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...
|
|
|
|
zimpixa
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 98
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
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.
|
|
|
|
lvlrdka22 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
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).
|
|
|
|
zimpixa
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 98
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
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.
|
|
|
|
lvlrdka22 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
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).
|
|
|
|
Departure
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 25, 2011, 06:36:18 AM Last edit: June 25, 2011, 07:19:49 AM by Departure |
|
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 ...
|
|
|
|
lvlrdka22 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 25, 2011, 06:55:19 AM |
|
Try running this and pasting the output. http://www.mediafire.com/?p9i80it24z879d6It 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.
|
|
|
|
Departure
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 25, 2011, 07:12:26 AM Last edit: June 25, 2011, 07:23:39 AM by Departure |
|
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
|
|
|
|
lvlrdka22 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
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.
|
|
|
|
um0rion
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 91
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
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?
|
|
|
|
lvlrdka22 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 25, 2011, 07:26:38 PM |
|
Fine. 1.74b. Bold removed.
|
|
|
|
yigga
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 25, 2011, 08:39:06 PM |
|
NICE ONE!
thanks for this awsome miner!
|
|
|
|
Departure
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 26, 2011, 02:21:16 AM |
|
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 ..
|
|
|
|
NANO
Newbie
Offline
Activity: 28
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 26, 2011, 08:10:49 AM |
|
an option to see overall mhash/sec would be really great!
|
|
|
|
yigga
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2011, 11:20:24 AM Last edit: June 27, 2011, 02:00:42 PM by yigga |
|
version 1.74b was working fine... today it still works, but the hud doesnt show the MHash/s value ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fimg151.imageshack.us%2Fimg151%2F5661%2Fminerbug.jpg&t=665&c=gvEqDOBWKyOjsw) 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)
|
|
|
|
|