Bitcoin Forum
May 12, 2024, 06:28:03 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: x1 in x16 slot - lock ups [SOLVED]  (Read 899 times)
BkkCoins (OP)
Hero Member
*****
Offline Offline

Activity: 784
Merit: 1009


firstbits:1MinerQ


View Profile WWW
September 06, 2011, 09:30:55 AM
Last edit: September 06, 2011, 10:04:11 AM by BkkCoins
 #1

My system has been stable for a few weeks now. 2x 5830, Ubuntu, SDK 2.4, Driver 11.6
Gigabyte GA970A-D3 board. Sempron 145.

I decided to do a few tests to see if I could move a 5830 working fine in a x1 slot to the x16 slot next to it. This was in prep for two more cards coming soon.

So now the card is on an x1 ext. in an x16 slot (whereas it was on the x1 ext in a x1 slot).

After running aticonfig to reset the X config, and rebooting, it seems both cards are detected again fine and even have the same X id 0.0 and 0.1.

But usually pretty quickly, maybe 30 seconds to 1 minute the machine locks up. I'm not even sure it's due to mining as one time I think I didn't start the miners yet.

Is this a typical indicator for the x16 slot needing presence pins shorted? Or does it ring any bells for something else maybe I missed when changing cards/slots?

I've set it back to the x1 slot it's been in for weeks now and it's running fine.
Next week I'm going to have to move things around for real.

EDIT - PROBLEM SOLVED!

Silly me for not noticing.
When I move that card it actually changes the ordering of the device numbers.
So now device 1 that used to be fine at 1000 clock is now device 0 that locks above 970 clock.
Changed my script parms around and all works fine again with x1 in x16 slot.

Funny the device numbers changed as they are still in same physical order on board. I deduce that the device numbers don't follow the physical slot order. My guess, the x16 slot has priority over the x1 slot and gets numbered first.

Once again a Happy Miner.

1715495283
Hero Member
*
Offline Offline

Posts: 1715495283

View Profile Personal Message (Offline)

Ignore
1715495283
Reply with quote  #2

1715495283
Report to moderator
1715495283
Hero Member
*
Offline Offline

Posts: 1715495283

View Profile Personal Message (Offline)

Ignore
1715495283
Reply with quote  #2

1715495283
Report to moderator
Each block is stacked on top of the previous one. Adding another block to the top makes all lower blocks more difficult to remove: there is more "weight" above each block. A transaction in a block 6 blocks deep (6 confirmations) will be very difficult to remove.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715495283
Hero Member
*
Offline Offline

Posts: 1715495283

View Profile Personal Message (Offline)

Ignore
1715495283
Reply with quote  #2

1715495283
Report to moderator
pixilated8
Newbie
*
Offline Offline

Activity: 47
Merit: 0


View Profile
September 06, 2011, 02:16:28 PM
 #2

Funny the device numbers changed as they are still in same physical order on board. I deduce that the device numbers don't follow the physical slot order. My guess, the x16 slot has priority over the x1 slot and gets numbered first.

I found the same on my Biostar A870U3.  From right-to-left, the 16x are first, then the 1x.
Code:
   1  3  0  2
   [] [] [] []
   []    []
   []    []
   []    []
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!