Title: any ideas to reach 300+Mhash/sec on a 6870 using Phoenix? Post by: fxgmblr on June 30, 2011, 09:10:22 PM running stock voltages and clock speeds I'm only getting 265Mhash/sec
any way to get that up to 300 w/o overclocking? (don't want to shorten the life of the card) if not, then what should i overclock/underclock to hit 300Mhash/sec? rig specs: Ubuntu 11.04 64-bit 2x HIS Digital ATI Radeon HD6870 Video Card (Engine Clock: 900 MHz; Video Memory: 1GB DDR5; Memory Clock: 4.2 GHz; RAMDAC: 400 MHz) AMD Sempron 140, Socket AM3, 2.7 GHz, 1 MB Cache, 45 Watts ASRock AM3 processors AMD 770-140W 4DDR3/ATI CrossFireX motherboard Seagate Barracuda 7200.12 500 GB 7200RPM SATA 6Gb/s with NCQ 16MB Cache Kingston ValueRAM 2 GB 1333MHz PC3-10600 DDR3 DIMM Desktop Memory Thermaltake V3 Black Edition SECC / Plastic ATX Mid Tower Computer Case Antec EA-650 Green ATX Energy Star Certified Power Supply running: python phoenix.py -u http://user:pass@server:8832 -k phatk VECTORS BFI_INT AGGRESSION=12 DEVICE=0 thanks in advanced! edit: using phoenix 1.50 Title: Re: any ideas to reach 300+Mhash/sec on a 6870 using Phoenix? Post by: deslok on June 30, 2011, 09:31:04 PM there was a post on how to get a ~3% increase
http://forum.bitcoin.org/index.php?topic=23067.0 however you need more than 3% to get from where you are to where you want to be. unfortunatly i don't see any reports of 300mhash/sec at stock clocks you're going to be doing some overclocking check here https://en.bitcoin.it/wiki/Mining_hardware_comparison and look at settings people ahve used on their 6870. Title: Re: any ideas to reach 300+Mhash/sec on a 6870 using Phoenix? Post by: Acidka on June 30, 2011, 09:47:49 PM look at http://forum.bitcoin.org/index.php?topic=23823.0 (http://forum.bitcoin.org/index.php?topic=23823.0)
Title: Re: any ideas to reach 300+Mhash/sec on a 6870 using Phoenix? Post by: fxgmblr on June 30, 2011, 10:01:29 PM look at http://forum.bitcoin.org/index.php?topic=23823.0 (http://forum.bitcoin.org/index.php?topic=23823.0) what program did you use to change voltage and also OC? Title: Re: any ideas to reach 300+Mhash/sec on a 6870 using Phoenix? Post by: humble on June 30, 2011, 10:06:42 PM AMDOverdriveCTRL will let you mess with the clock and memory speeds. I run my 6870 at 1000 mhz and the memory at 350 which gives me about 310mh/s using poclbm.
Title: Re: any ideas to reach 300+Mhash/sec on a 6870 using Phoenix? Post by: Acidka on June 30, 2011, 10:14:36 PM look at http://forum.bitcoin.org/index.php?topic=23823.0 (http://forum.bitcoin.org/index.php?topic=23823.0) what program did you use to change voltage and also OC? AMDOverdriveCTRL under LinuxCoin Title: Re: any ideas to reach 300+Mhash/sec on a 6870 using Phoenix? Post by: fxgmblr on June 30, 2011, 10:23:30 PM AMDOverdriveCTRL will let you mess with the clock and memory speeds. I run my 6870 at 1000 mhz and the memory at 350 which gives me about 310mh/s using poclbm. what temp do you get on that? Title: Re: any ideas to reach 300+Mhash/sec on a 6870 using Phoenix? Post by: shotgun on July 02, 2011, 04:38:14 AM Here's a simple script to help you set your stuff up.. just set your user/pass/pool-url info and execute.
Code: #!/bin/sh Title: Re: any ideas to reach 300+Mhash/sec on a 6870 using Phoenix? Post by: CyberPhunk on July 02, 2011, 06:14:33 PM an easy thing to try is to just add the WORKSIZE=128 flag
BTW, it's not necessary to jack up the core too high to hit 300Mh/s, I'm running a 6950 with a 6970 bios at 900/1250 with the voltage at max 1200 and I get 385Mh/s using phoenix and around 397Mh/s with guiminer. Both within Win7 Edit: Phoenix ver 1.5 running phatk Device=0 VECTORS WORKSIZE=128 BFI_INT FASTLOOP AGGRESSION=11 Guiminer is July 1 version Edit 2: 6950 flashed to 6970, doh! Title: Re: any ideas to reach 300+Mhash/sec on a 6870 using Phoenix? Post by: sethmo on July 02, 2011, 09:56:04 PM Don't you mean 6950 running 6970 bios? Those numbers you posted can't be from a 6850 ...
Title: Re: any ideas to reach 300+Mhash/sec on a 6870 using Phoenix? Post by: CyberPhunk on July 02, 2011, 10:22:05 PM My bad, edited the post. heh
|