Bitcoin Forum
May 01, 2024, 01:58:39 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: WTF? New R9 290's not recognized  (Read 1547 times)
grippy54 (OP)
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
March 04, 2014, 11:54:50 PM
Last edit: March 05, 2014, 01:40:32 AM by grippy54
 #1

I’m adding cards to my rig and am having some difficulty. I’d be very appreciative for any help. I have been running 1 R9 290 at 880khs for a couple weeks. I’m trying to add 2 additional R9 290’s, but they are not recognized by my system. The first card is still recognized and mines fine at 880khs, same as before. I can switch the cards and they each work, one at a time, but not together.

I had it recognizing 3 cards previously, but then went down to 1, now going back to 3. The cards are all Gigabyte Radeon R9 290 GV-R929OC-4GD. It shows only 1 GPU in sgminer, MSI Afterburner and only 1 display adapter in the Device Manager. I even booted to BAMT and it only sees 1 GPU.

I reinstalled sgminer and AMD drivers (after using Display Driver Uninstaller to remove the old ones). I’ve tried different risers. I've tried plugging each of the new cards one at a time. I’ve tried plugging the cards into the second 16x slot on the MB. All without success.

Thanks in advance.


I’m running:

MSI 970A-G43
8GB RAM
Win 7 x64
1 Gigabyte Radeon R9 290 GV-R929OC-4GD directly on MB
2 Gigabyte Radeon R9 290 GV-R929OC-4GD on powered 1x to 16x risers
SGminer 4.1
13.12 beta drivers

I am executing setx GPU_MAX_ALLOC_PERCENT 100 and setx GPU_USE_SYNC_OBJECTS 1 before launching SGminer.

My config:

   "failover-only": true,
   "xintensity": "500",
   "vectors": "1",
   "worksize": "256",
   "lookup-gap": "2",
   "thread-concurrency": "30719",
   "gpu-engine": "1002",
   "gpu-memclock": "1500",
   "gpu-powertune": "20",
   "gpu-threads": "1",
   "auto-fan": true,
   "temp-cutoff": "90",
   "temp-overheat": "85",
   "temp-target": "80",
   "queue": "0",
   "scan-time": "1",
   "expiry": "120",
   "api-port": "4028",
   "log": "5",
   "temp-hysteresis": "3",
   "kernel-path": "/usr/local/bin"
1714571919
Hero Member
*
Offline Offline

Posts: 1714571919

View Profile Personal Message (Offline)

Ignore
1714571919
Reply with quote  #2

1714571919
Report to moderator
1714571919
Hero Member
*
Offline Offline

Posts: 1714571919

View Profile Personal Message (Offline)

Ignore
1714571919
Reply with quote  #2

1714571919
Report to moderator
The network tries to produce one block per 10 minutes. It does this by automatically adjusting how difficult it is to produce blocks.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714571919
Hero Member
*
Offline Offline

Posts: 1714571919

View Profile Personal Message (Offline)

Ignore
1714571919
Reply with quote  #2

1714571919
Report to moderator
1714571919
Hero Member
*
Offline Offline

Posts: 1714571919

View Profile Personal Message (Offline)

Ignore
1714571919
Reply with quote  #2

1714571919
Report to moderator
everything_zen
Member
**
Offline Offline

Activity: 109
Merit: 11


View Profile
March 05, 2014, 12:44:49 AM
 #2

You had it running 3 before? What did you change?

grippy54 (OP)
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
March 05, 2014, 01:08:46 AM
 #3

I had the same cards but had to RMA them. I fried them by hot plugging the DVI cable while it was mining. I always thought that was cool to do, but I guess not. After that, I may have reinstalled win. But regardless, I'm thinking this is not software, since BAMT doesn't recognize them either.
everything_zen
Member
**
Offline Offline

Activity: 109
Merit: 11


View Profile
March 05, 2014, 01:49:40 AM
 #4

may have fried your pcie ports too - try different ones.

grippy54 (OP)
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
March 05, 2014, 03:09:53 AM
Last edit: March 05, 2014, 05:04:47 PM by grippy54
 #5

OK, so here's what did to get it working. I reset the MB bios to stock settings and reinstalled the chipset drivers. That seemed to do the trick.

Now I have them all screamin' at full bore. Thanks for the suggestions zen.  Smiley
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!