Welcome to the PiMP OS and Miner.farm forum.
Trouble with install AFTER putting my Validation key in.
there is a lot more info than just a couple lines. One of the issues with doing BIOS modification is that you must sign the BIOS properly. The driver checks the hash of the BIOS against a value saved in the BIOS, if they do not match, it will have issues. As well, the community here shares a lot of information on BIOS mods, and then its validated against lots of miners, rigs, etc. Perhaps a good place to start is using the BIOS mods vetted by the community. Regardless, please post the whole output from atitool. Read the manual page for Putty to get the information you need to support cut and paste. Thanks!
Right.... i've gotten the miner to work fine through SSH so all is well there. Got the Eth only miner up with 6 cards but its only pulling 90 MH which is half of what i would be expecting (30x6=180ish).
Not modified anything yet but that is low . Are compute drivers enabled? Are they latest drivers (17)? Getting the hang of this system you've got here :)
If you are using 2.4.1 version of pimp, you will have access to both the AMDGPU-DC and AMDGPU-PRO 17.40 drivers. You can pick and choose the bits you want in your driver stack. The OS is based on 4.15 rc2 and has the current AMDGPU-DC drivers built in. I would start by putting the stock BIOS back though, just to see what the hashing rates are.
Got it, In linux, not sure why i was using putty. Ha
Firmware signature: 0x4d4f5441
Max GPU freq (Mhz): 2000
Max memory freq (Mhz): 2250
Power control limit (%%): 50
TDP (W): 145
TDC (A): 132
Max Power Limit (W): 135
Max Temp. (C): 90
Shutdown Temp. (C): 94
Hotspot Temp. (C): 105
Temp. Hysteresis: 3
Min Temp. (C): 40
Med Temp. (C): 65
High Temp. (C): 85
Max Temp. (C): 109
Legacy or Fuzzy Fan Mode: 1
Min PWM (%): 20
Med PWM (%): 40
High PWM (%): 60
Max PWM (%): 1
Max RPM: 3000
Acoustic Limit (MHz): 918
300 Mhz: 750 mV
600 Mhz: 65282 mV
918 Mhz: 65283 mV
1167 Mhz: 65284 mV
1239 Mhz: 65285 mV
1282 Mhz: 65286 mV
1326 Mhz: 65287 mV
1366 Mhz: 65288 mV
Part num: K4G80325FB
Size (MB): 8192
Density: 4M x 32
Part num: H5GC8H24MJ
Size (MB): 8192
Density: 4M x 32
Wow, it's all falling into place now using linux's ssh.
My bad leaving the XMR miner running, Getting 160mh and have not even configured cards yet.
Seems im all good but this error is stoppin the monitor loading on the rig? Not sure but im happier in ssh anyways.
Drivers are working fantastic, will go through all the forum threads and tips and tricks i briefly saw scanning through when i have some spare time.
Thanks for everything :)
Awesome possum. Thats what we like to hear! We what our users to have the most reliable rigs, remote managed, and the fastest consistent hashing rates period. Would love it if you had the time to write up a review about your experience with hashing speeds. Thanks!
I will do for sure. With so many different setups/levels of experience i would just say it's not ALWAYS the easiest thing to get up and running but i do like the layout.
1 thing before i get my settings dialed in, are these commands correct for sgminer?
There under whats possible but a safe starting point. Also, Is there a command for changing the memory voltage? i could only see core voltage.
Thanks again :)
It was the comma missing from end of line :)
The thing is, its showing in miner farm its changed the clocks but its still only doing 150mh (25 per card) instead of 180 (30 per card) that i got from windows (woefully unstable) and 170 from standard xubuntu using ethminer with no clocking (couldnt get to work) which showed my Modded bios works fine.
Plus, the settings are doing nothing to the hashrate, not sure why....
Unstable is bad M'Kay! So why try to reach unstable places? Keep the cards in a safe work zone, better for the cards, better for the rig, and in the end... better for the hashing :)
md last edited by md
Hi, I'm having the same problem with 2.4.1, however I'm unable to SSH the machine. The mobo is Gigabyte AX370 Gaming 5 and I'm testing it with a single card only. Same results for R9 390 and RX570. The screen goes blank on boot. Please note that with 2.3 everything worked, however I'm hoping for better hashrates with the new AMD GPU driver in 2.4.1 and hence the switch. Basically 2.4.1 booted up, I've managed to enter the key, then the system rebooted and after a short while all I could see was Loading initial ramdisk and a blank screen after that. Please advise. Yes, I've read everything, I believe. Recommended mobo settings, proper image creation in Windows, etc. And the cards have a stock BIOS.
We promise to keep your email safe and never spam you.
Copyright (c) 2012-2018 PiMP LLC. All rights Reserved.