 Show Posts
|
|
Pages: [1]
|
|
Designing a rackable 4u mining case right now that's intended to use the Delta DPS-2400AB PSU + its breakout board but i can't find any dimensions by googling around. Was wondering if someone who owns that PSU could help me out by supplying all the dimensions for the PSU and breakout board separately, along with the mounting holes if possible.
Thanks,
|
|
|
|
I'm checking this issue in Linux, so I will have some news in a few hours.
Also, even though I have the ADL v10 linked in my /usr/lib, the miner complains about no ADL installed. This is with Ubuntu 16.04. Any details regarding this would greatly be appreciated. Thanks! ADL SDK v10 contains sample code for overlocking, but it created for Windows because code loads "atiadlxx.dll" library. ADL SDK v9 also contains code for Linux that loads "libatiadlxx.so" library. So either AMD devs forgot to include code for Linux in ADL SDK v10, or Linux is not supported by ADL SDK v10. Right now miner tries to load "libatiadlxx.so", if it writes that ADL is not supported it means that you don't have "libatiadlxx.so" file. PS. Now I can duplicate issue with Linux (gpu fault detected), but it will take some more time to find the reason and fix it. Hi Claymore, I found a version of AMD drivers that now include libatiadlxx.so, it's in the SteamOS repo for AMDGPU-PRO drivers 16.40. Found it through here: https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/amd-linux/895520-amdgpu-pro-controlling-hardware-settings-for-polaris |
|
|
|
okay maybe i will look into this new API myself
It's not an API - it's the pp_table entry in the device folder of sysfs - if you can figure out the format, read it, parse it, write to it, and the AMDGPU driver will reset and load it. All I can read from it is binary :/ |
|
|
|
I fucking love this AMDGPU driver - with it, I can control everything shown here and more (NSFW): http://ottrbutt.com/tmp/custom-editor.jpgVoltages, clocks, changing DPM state settings, the state table that tells it what DPM to go to at what state... Hey, how and where to you change voltages under linux with amdgpu driver ? somewhere in /sys/class/drm/cardX ? No, you have to make your own tools - but /sys/class/drm/cardX/device/pp_table is what you want. :3 Did you bother with installing AMDGPU-PRO? Or just the kernel update to 4.8rc2 was needed to start developing your tools and mine? |
|
|
|
v6.3. This version is assumed to be stable, so it is not marked as "beta".
- added support for NVIDIA 10xx cards in Linux.
- fixed issue with gpu-pro drivers in Linux.
- minor improvements in OpenCL kernels.
- bug fixes.
Even though ADL v10 isn't currently in Linux, can I still manage voltage and clocks of my RX 480s? I know it says I can't manage the fan and temp but was just making sure. Thanks |
|
|
|
I'm checking this issue in Linux, so I will have some news in a few hours.
Also, even though I have the ADL v10 linked in my /usr/lib, the miner complains about no ADL installed. This is with Ubuntu 16.04. Any details regarding this would greatly be appreciated. Thanks! |
|
|
|
installed the latest driver and latest APP SDK. And another problem. The syslog errors are continuously [ 7669.222221] amdgpu 0000:06:00.0: GPU fault detected: 147 0x0d608401
[ 7669.222222] amdgpu 0000:06:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x081047AC
[ 7669.222223] amdgpu 0000:06:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E084001
[ 7669.222224] VM fault (0x01, vmid 7) at page 135284652, read from 'TC7' (0x54433700) (132) Linux is a problem, always. Well, it seems AMD does not support ADL v10 in Linux yet. In Windows it works fine. I will build a system with Ubuntu with latest drivers and RX480 to confirm it. "VM_CONTEXT1_PROTECTION_FAULT_ADDR" error - not sure that it is a problem of miner, it can be issue in drivers. What Linux version? What drivers version? I tried to reproduce it but it seems I'm doing something wrong. Please keep supporting Linux version  , the driver is still in beta so I'll patiently wait There is no libatiadlxx.so when using amdgpu pro driver, so I guess they release ADLv10 but not merge it with the driver yet. I myself use Ubuntu 16.04.1, driver version amdgpu-pro_16.30.3-315407.tar.xz ( this is last month version, I think before ADLv10 release ), try on both stock kernel 4.4 and 4.7 ( not the latest 4.7 kernel ), maybe 4.8 will be better Then check on /var/log/syslog or journalctl when running claymore an you'll see above error. The mining works ok anyway, but the syslog is bad "too many write" We can disable syslog to protect hdd. It looks like a driver problem, but perhaps you can find more P.S It's easier to find whether your GPU is faulty or not on Linux then Windows ( Windows just directly go to BSOD or recovery with no log ), I personally think Windows is overkill for mining I have this exact same issue, causes CPU to be tagged to 100% from all the error logging. |
|
|
|
|
On the new H97 Anniversary ASRock Boards, if you have 3+ cards it wont boot unless you plug in the molex on the board. At least that was my experience, even with USB PCI-e risers.
|
|
|
|
@jstefanop Do you mind sharing your settings? |
|
|
|
Should remove all buying of "leveling" from this coin as it is forbidden in Riot TOS
You think the developers care about a silly thing like violating the TOS? i don't see that in the OP lol... It's in the video they made in the OP |
|
|
|
|
Should remove all buying of "leveling" from this coin as it is forbidden in Riot TOS
|
|
|
|
Well, so far the best I can get out of a set of 10 is about 3.5Mh/s (850MHz)...a far cry from the 5Mh/s or so in the "secret picture" Jack has in the original post. I hope this is going to be something we can expect with a future firmware update to the controller. I tried turning the little voltage dial up on the power supplies, but it didn't appear to have any noticeable effect.
Had to cut and strip the power cables for the PSUs but it was the green/ground white/neg black/pos wiring someone else posted here, so that was easy. All of my miner cables were correctly colored. Unfortunately, the power cable for one of the USB hubs was bad out of the box...but I had another cable in my giant box of spares that works.
Setting these up is a cable management nightmare, but I've got it to where I'm happy with it. Now I'm just going to leave them overnight to do their thing and see how it goes. I had one of the controllers reset randomly on its own once, that I noticed - hopefully that isn't a frequent occurrence.
So far, I like these little guys...they look unique and the gadget factor is there. I just wish I could get the 500Kh/s performance seen in that photo...I wish Jack would tell us what was done to achieve that!
Are you having problems with the controller? Every 12-14 hours my controller randomly craps out and randomly starts working again a few hours later after unplugging+ replugging it in over and over again. Yes...it's really annoying. I have no idea what's causing it, other than it just being a piece of junk. Also, fun with screen shots time...Jack's "secret photo" in the OP is what made me decide to buy these, figuring that if they each did 500Kh/s, that would make them worth the investment. Unfortunately, I've only managed to average around 350Kh/s each. However, at one point after switching from 800MHz to 850MHz I did see this reported by the dashboard (see screenshot). Proof positive that anyone can post a "Wow look at these high hashrates" screenshot as a form of semi-false advertising on the Gridseed performance. Unless something radically changes, you won't see this kind of performance.  How do you get your controllers up and working again? They seem to randomly cycle themselves for unknown reasons but occasionally when they stop responding via the web interface it requires you to power cycle them. Really annoying, got to train my wife how to do it so we dont have downtime while I am at work. Yeah even after power cycling it isnt working... have you tried the reset button on the side of the controller? I dont want to use it if it screws up everything |
|
|
|
|
How do you guys get your controllers back online when they crap out after 12-16 hours?
|
|
|
|
Well, so far the best I can get out of a set of 10 is about 3.5Mh/s (850MHz)...a far cry from the 5Mh/s or so in the "secret picture" Jack has in the original post. I hope this is going to be something we can expect with a future firmware update to the controller. I tried turning the little voltage dial up on the power supplies, but it didn't appear to have any noticeable effect.
Had to cut and strip the power cables for the PSUs but it was the green/ground white/neg black/pos wiring someone else posted here, so that was easy. All of my miner cables were correctly colored. Unfortunately, the power cable for one of the USB hubs was bad out of the box...but I had another cable in my giant box of spares that works.
Setting these up is a cable management nightmare, but I've got it to where I'm happy with it. Now I'm just going to leave them overnight to do their thing and see how it goes. I had one of the controllers reset randomly on its own once, that I noticed - hopefully that isn't a frequent occurrence.
So far, I like these little guys...they look unique and the gadget factor is there. I just wish I could get the 500Kh/s performance seen in that photo...I wish Jack would tell us what was done to achieve that!
Are you having problems with the controller? Every 12-14 hours my controller randomly craps out and randomly starts working again a few hours later after unplugging+ replugging it in over and over again. Yes...it's really annoying. I have no idea what's causing it, other than it just being a piece of junk. Also, fun with screen shots time...Jack's "secret photo" in the OP is what made me decide to buy these, figuring that if they each did 500Kh/s, that would make them worth the investment. Unfortunately, I've only managed to average around 350Kh/s each. However, at one point after switching from 800MHz to 850MHz I did see this reported by the dashboard (see screenshot). Proof positive that anyone can post a "Wow look at these high hashrates" screenshot as a form of semi-false advertising on the Gridseed performance. Unless something radically changes, you won't see this kind of performance. How do you get your controllers up and working again? |
|
|
|
Well, so far the best I can get out of a set of 10 is about 3.5Mh/s (850MHz)...a far cry from the 5Mh/s or so in the "secret picture" Jack has in the original post. I hope this is going to be something we can expect with a future firmware update to the controller. I tried turning the little voltage dial up on the power supplies, but it didn't appear to have any noticeable effect.
Had to cut and strip the power cables for the PSUs but it was the green/ground white/neg black/pos wiring someone else posted here, so that was easy. All of my miner cables were correctly colored. Unfortunately, the power cable for one of the USB hubs was bad out of the box...but I had another cable in my giant box of spares that works.
Setting these up is a cable management nightmare, but I've got it to where I'm happy with it. Now I'm just going to leave them overnight to do their thing and see how it goes. I had one of the controllers reset randomly on its own once, that I noticed - hopefully that isn't a frequent occurrence.
So far, I like these little guys...they look unique and the gadget factor is there. I just wish I could get the 500Kh/s performance seen in that photo...I wish Jack would tell us what was done to achieve that!
Are you having problems with the controller? Every 12-14 hours my controller randomly craps out and randomly starts working again a few hours later after unplugging+ replugging it in over and over again. |
|
|
|
|
after about 12 hours of mining the controller is no longer connected to the network, what gives?
|
|
|
|
|
What's the best way to hook up these miners for power if both power and ground are black? I dont have a multimeter on hand either.
|
|
|
|
|
For all of those who are mining with locked R9 280x's and have windows + msi afterburner, try this!
[Settings]
VDDC_IR3567B_Detection = 32h
VDDC_IR3567B_Output = 0
MVDDC_IR3567B_Detection = 32h
MVDDC_IR3567B_Output = 1
That should be in your MSI AFT profile, should unlock your card, at least worked for my MSI Gaming 280x's.
|
|
|
|
|
