Hi Zero:
Decided to give your S/W a go since the last two failed. I have been looking for a Linux solution for a long time now.
First right off the bat, you seem to be the only one who supports your system. That is a great plus to have an avenue
to the producer. I am at the current release version atm.
System as follows:
ASUS H270 PRO current bios
EVGA 850 Gld
Intel I5
16 G ram
250G laptop drive
3X Gtx 1060 3G
Had a rough time figuring your 1bash out but after that, system is rock solid now except for the soft crash caused by
me clocking the mem at +900. Just will not go there. Pleased to say I have found the winner. Watchdog and auto fan
regulation does a wonderful job.
So far, I have had to suffer with Win7 as I will never have W10 in my house. I was a short time beta tester for it and
like Vista, I deleted it after about a month and give them "my" views. Wasn't received well and told I didn't qualify
for my free copy. Oh my.
One thing I would like to ask is if you will add the option to resize the partition out to the full drive size. I really don't
want to go playing around in a system that is rock solid just yet. I need it to be mining coins, not trying to mop up
the mess I created.
Keep on mate, you rockin in the free world. Is the ETH addy in the original 1Bash yours, if so will send you a donation.
thay
Topic: [ mining os ] nvoc - page 196. (Read 418546 times)
Unfortunately I must write, that nvOS is really unstable with 11 GPUs in my case. I'm sad... :-( In this case, each miner crash a few minutes after mining for memory segmentation fault, in 70% of startups watchdog kill mining process for maybe 20x times. In general there are many epochs without mining - when nvOS set up GPUs, or restating whole mining process. After GPUs re-allocation there are great improvement in stability. So, someone who has in one rig more that 8 cards and succesfully OCed?
I'm solving miners crashing, OC all day. My conclusion is nvOS v0019 is unstable and I can't trust it - with 11x GPUs.
It's little strange that if rig has only 8 cards, so it's stable. So, I've two rigs now, with 8 gpus, and 3 gpus. Both use nvOS and works :-) I don't understand why both rigs can have different OC settings.
On rig with 8 gpus is this:
On rig with 3 gpus is this:
both rigs use CPU mining too
Hash rates are for ZCash:
I'm solving miners crashing, OC all day. My conclusion is nvOS v0019 is unstable and I can't trust it - with 11x GPUs.
It's little strange that if rig has only 8 cards, so it's stable. So, I've two rigs now, with 8 gpus, and 3 gpus. Both use nvOS and works :-) I don't understand why both rigs can have different OC settings.
On rig with 8 gpus is this:
- power limit: 208W
- core: +85
- mem: +480
- Mobo: ASRock BTC Pro+
- PSU 1200W, 1700W
- 7x Gigabite AORUS 1080Ti Extreme Water
- 1x Zotac Extreme 1080Ti AMP
- i5-7600K
- used these risers, powered via SATA https://www.aliexpress.com/item/10pcs-TISHRIC-2018-VER008S-Molex-4PIN-15PIN-SATA-6PIN-3-in-1-PCIE-PCI-Express-Riser/32828808283.html?spm=a2g0s.9042311.0.0.szfVUP
On rig with 3 gpus is this:
- power limit: 225W
- core: +120
- mem: +900
- Mobo: ASUS Maximus Ranger IV
- PSU 1700W
- 3x Gigabite AORUS 1080Ti Extreme Water
- i7-4790K
both rigs use CPU mining too
Hash rates are for ZCash:
- with 8 gpus - about 5550 Sol/s
- with 3 gpus - about 2150 Sol/s
"
Bits Be Trippin'
4 days ago
@asus @ASUSUSA Just got off Asus Support and they confirmed 13x is MAX on B250 Mining Expert until BIOS update in 4Q. Case ID#
N171017058"
Bits Be Trippin'
4 days ago
@asus @ASUSUSA Just got off Asus Support and they confirmed 13x is MAX on B250 Mining Expert until BIOS update in 4Q. Case ID#
N171017058"
Of course I already tried plugging up all three motherboard inputs. :p
Which still leaves the question of CPU; how many cores/threads is the one you're using?
Of course I already tried plugging up all three motherboard inputs. :p
B250 Expert won't boot with 14 1080ti GPUs. 13 is the limit. So there must be some hardware or bios or some limitation. Some speculate that a future update from Asus may fix it. Of course, I would have preferred to use 19 1080tis.
2 thoughts:CPU thread limitations.
Board power (in the video you only had/have 1 PSU, of 3 possible, plugged into the board).
B250 Expert won't boot with 14 1080ti GPUs. 13 is the limit. So there must be some hardware or bios or some limitation. Some speculate that a future update from Asus may fix it. Of course, I would have preferred to use 19 1080tis.
Hello,
One of my rigs that prevoiusly ran 2x 1070 with +145/+1300 OC was upgraded to 6x of these GPU's.
It is not stable anymore tho, the miner crashes 2 times an hour, where to begin looking?
When I check /var/logs/kernel.log & xorg.0.log they are both empty, but created with the same timestamp of the crash.
What do?
G3900 Cpu
H110-D3A mobo
Also, at the time of the crash, watchdog shows 0 GPU tjreshold on all devices.
Mining Zcash with zm on v0019 1.2
One of my rigs that prevoiusly ran 2x 1070 with +145/+1300 OC was upgraded to 6x of these GPU's.
It is not stable anymore tho, the miner crashes 2 times an hour, where to begin looking?
When I check /var/logs/kernel.log & xorg.0.log they are both empty, but created with the same timestamp of the crash.
What do?
G3900 Cpu
H110-D3A mobo
Also, at the time of the crash, watchdog shows 0 GPU tjreshold on all devices.
Mining Zcash with zm on v0019 1.2
I dont know your cards manufacturer, I have 2 rigs of 6x1070 Asus and 7x1070 Gygabite
and none of those can handle your oc
My stable oc for ZEC with 440-450 Sol/s
Asus:
Power 120
Core Clock 120
Mem Clock 600
Gygabite:
Power 125
Core Clock 115
Mem Clock 600
You can also enable telegram to get warning notification from watcdog
Wow... I have tweaked my settings now and my rig finally runs 3 hrs without crash.
The manufactor is Gigabyte, model G1 and these are my settings:
+130 core clock
+1200 mem clock
-135W
Each card generate ~475-480 sol/s.
I got it working. Since I had no GPUs in the rig yet (was just using the on-board graphics while getting the rig configured, nvOC went into a loop on the xorg check. I threw a 1050Ti in there and it came up fine once the xorg file had been restored. So both PRIME Z270-A and PRIME Z270-AR works just fine.
Never boot nvOC with onboard gpu. Period.Disable onboard GPU as soon as you edit bios / before starting nvOC for 1st run.
I got it working. Since I had no GPUs in the rig yet (was just using the on-board graphics while getting the rig configured, nvOC went into a loop on the xorg check. I threw a 1050Ti in there and it came up fine once the xorg file had been restored. So both PRIME Z270-A and PRIME Z270-AR works just fine.
Hello,
One of my rigs that prevoiusly ran 2x 1070 with +145/+1300 OC was upgraded to 6x of these GPU's.
It is not stable anymore tho, the miner crashes 2 times an hour, where to begin looking?
When I check /var/logs/kernel.log & xorg.0.log they are both empty, but created with the same timestamp of the crash.
What do?
G3900 Cpu
H110-D3A mobo
Also, at the time of the crash, watchdog shows 0 GPU tjreshold on all devices.
Mining Zcash with zm on v0019 1.2
One of my rigs that prevoiusly ran 2x 1070 with +145/+1300 OC was upgraded to 6x of these GPU's.
It is not stable anymore tho, the miner crashes 2 times an hour, where to begin looking?
When I check /var/logs/kernel.log & xorg.0.log they are both empty, but created with the same timestamp of the crash.
What do?
G3900 Cpu
H110-D3A mobo
Also, at the time of the crash, watchdog shows 0 GPU tjreshold on all devices.
Mining Zcash with zm on v0019 1.2
I dont know your cards manufacturer, I have 2 rigs of 6x1070 Asus and 7x1070 Gygabite
and none of those can handle your oc
My stable oc for ZEC with 440-450 Sol/s
Asus:
Power 120
Core Clock 120
Mem Clock 600
Gygabite:
Power 125
Core Clock 115
Mem Clock 600
You can also enable telegram to get warning notification from watcdog
Ran into an issue I've never encountered before. When doing a boot from a freshly imaged 32G USB (same make, model and size I use in all my other rigs), after the initial boot where the 1bash file is converted from dos to unix, I get stuck here on the 2nd boot:
I tried re-imaging the USB drive twice, but get stuck at the same place every time. I even imaged 0019 to a 64GB SSD and still got stuck in the exact same place, see below:
The mobo I'm using is an Asus PRIME Z270-AR. My other Asus rig is using a PRIME Z270-A. The only different between these 2 mobos, is that the AR version only has a HDMI output where the A version also has DVI.
Another difference is that I already installed 2 M.2 to PCI adapters in this new mobo (plan to run 9 GPUs), but I have no GPU's connected yet. Both rigs run Celeron G3930 CPUs (I have posted another question about using Celerons with 8+ GPUs, but I don't see how that could be related to this).
I did install the latest BIOS before I got started, and I configured the BIOS exactly the same as my other PRIME Z270-A, which has the following settings:
Advanced/Platform Misc Configuration - Everything Disabled
Advanced/System Agent (SA) Configuration / Graphics Configuration / Leave alone
Advanced/System Agent (SA) Configuration / Graphics Configuration / DMI/OPI Configuration / DMI Max Link Speed = Gen2
Advanced/System Agent (SA) Configuration / Graphics Configuration / PEG Port Configuration / Gen2, Gen2, Auto
Advanced/PCH Configuration / PCI Express Configuration / Gen2
Advanced/PCH-FW Configuration/PTT Configuration/PTP aware OS = Not PTP Aware
Advanced/Onboard Devices Configuration / HD Audio Controller = Disabled
Advanced/Onboard Devices Configuration / M.2_1 Configuration = Auto
Advanced/Onboard Devices Configuration / M.2_2 Bandwidth Configuration = X2
Advanced/Onboard Devices Configuration / RGB LED Lighting / In Sleep, hibernate and soft off states = Off
Advanced/APM Configuration / Restore AC Power Loss = Power On
Boot / Above 4G Decoding = Enabled
Boot/Secure Boot/Key Management/Clear Secure Boot Keys = YES
I went ahead and installed windows onto that 64G SSD just to make sure everything worked fine with the rest of the system, and it did.
Any ideas why nvOC doesn't appear to like the PRIME Z270-AR mobo?
One last note, I never did edit 1bash in Windows, I just "ejected" both USB partitions under windows, and then booted the 0019 image on the Asus.
I tried re-imaging the USB drive twice, but get stuck at the same place every time. I even imaged 0019 to a 64GB SSD and still got stuck in the exact same place, see below:
The mobo I'm using is an Asus PRIME Z270-AR. My other Asus rig is using a PRIME Z270-A. The only different between these 2 mobos, is that the AR version only has a HDMI output where the A version also has DVI.
Another difference is that I already installed 2 M.2 to PCI adapters in this new mobo (plan to run 9 GPUs), but I have no GPU's connected yet. Both rigs run Celeron G3930 CPUs (I have posted another question about using Celerons with 8+ GPUs, but I don't see how that could be related to this).
I did install the latest BIOS before I got started, and I configured the BIOS exactly the same as my other PRIME Z270-A, which has the following settings:
Advanced/Platform Misc Configuration - Everything Disabled
Advanced/System Agent (SA) Configuration / Graphics Configuration / Leave alone
Advanced/System Agent (SA) Configuration / Graphics Configuration / DMI/OPI Configuration / DMI Max Link Speed = Gen2
Advanced/System Agent (SA) Configuration / Graphics Configuration / PEG Port Configuration / Gen2, Gen2, Auto
Advanced/PCH Configuration / PCI Express Configuration / Gen2
Advanced/PCH-FW Configuration/PTT Configuration/PTP aware OS = Not PTP Aware
Advanced/Onboard Devices Configuration / HD Audio Controller = Disabled
Advanced/Onboard Devices Configuration / M.2_1 Configuration = Auto
Advanced/Onboard Devices Configuration / M.2_2 Bandwidth Configuration = X2
Advanced/Onboard Devices Configuration / RGB LED Lighting / In Sleep, hibernate and soft off states = Off
Advanced/APM Configuration / Restore AC Power Loss = Power On
Boot / Above 4G Decoding = Enabled
Boot/Secure Boot/Key Management/Clear Secure Boot Keys = YES
I went ahead and installed windows onto that 64G SSD just to make sure everything worked fine with the rest of the system, and it did.
Any ideas why nvOC doesn't appear to like the PRIME Z270-AR mobo?
One last note, I never did edit 1bash in Windows, I just "ejected" both USB partitions under windows, and then booted the 0019 image on the Asus.
Im pretty sure I tested nvOC with one of my Asus Prime(Z270-A) a few weeks and it was fine. Im getting another one this week, Ill test it again if I have the time.
btw, you should just stick with Windows 10 if you have 8 or less cards. nvOC has a lot of problems sadly and the support is very limited, even worse if you are not a Linux expert. Im running 0019 1.2 and since I upgraded the only thing I can mine is zcash. (true, I did not tried many coins)
I did managed to mine Vertcoin with 0019 but for some reason, the temp limit stopped working my 1080Ti but was fine with my 1070s. So I upgraded to 1.2 but now zencash and Vertcoin crash after a few seconds...
I suspect a cuda problem with Vertcoin but I have no idea why ewbf wont work anymore. I had no issue with 0019.
Ill probably start from scratch as soon as the new version is available. But if I had less cards on that rig (currently 12), I would stick with Windows 10.
Ran into an issue I've never encountered before. When doing a boot from a freshly imaged 32G USB (same make, model and size I use in all my other rigs), after the initial boot where the 1bash file is converted from dos to unix, I get stuck here on the 2nd boot:
I tried re-imaging the USB drive twice, but get stuck at the same place every time. I even imaged 0019 to a 64GB SSD and still got stuck in the exact same place, see below:
The mobo I'm using is an Asus PRIME Z270-AR. My other Asus rig is using a PRIME Z270-A. The only different between these 2 mobos, is that the AR version only has a HDMI output where the A version also has DVI.
Another difference is that I already installed 2 M.2 to PCI adapters in this new mobo (plan to run 9 GPUs), but I have no GPU's connected yet. Both rigs run Celeron G3930 CPUs (I have posted another question about using Celerons with 8+ GPUs, but I don't see how that could be related to this).
I did install the latest BIOS before I got started, and I configured the BIOS exactly the same as my other PRIME Z270-A, which has the following settings:
Advanced/Platform Misc Configuration - Everything Disabled
Advanced/System Agent (SA) Configuration / Graphics Configuration / Leave alone
Advanced/System Agent (SA) Configuration / Graphics Configuration / DMI/OPI Configuration / DMI Max Link Speed = Gen2
Advanced/System Agent (SA) Configuration / Graphics Configuration / PEG Port Configuration / Gen2, Gen2, Auto
Advanced/PCH Configuration / PCI Express Configuration / Gen2
Advanced/PCH-FW Configuration/PTT Configuration/PTP aware OS = Not PTP Aware
Advanced/Onboard Devices Configuration / HD Audio Controller = Disabled
Advanced/Onboard Devices Configuration / M.2_1 Configuration = Auto
Advanced/Onboard Devices Configuration / M.2_2 Bandwidth Configuration = X2
Advanced/Onboard Devices Configuration / RGB LED Lighting / In Sleep, hibernate and soft off states = Off
Advanced/APM Configuration / Restore AC Power Loss = Power On
Boot / Above 4G Decoding = Enabled
Boot/Secure Boot/Key Management/Clear Secure Boot Keys = YES
I went ahead and installed windows onto that 64G SSD just to make sure everything worked fine with the rest of the system, and it did.
Any ideas why nvOC doesn't appear to like the PRIME Z270-AR mobo?
One last note, I never did edit 1bash in Windows, I just "ejected" both USB partitions under windows, and then booted the 0019 image on the Asus.
I tried re-imaging the USB drive twice, but get stuck at the same place every time. I even imaged 0019 to a 64GB SSD and still got stuck in the exact same place, see below:
The mobo I'm using is an Asus PRIME Z270-AR. My other Asus rig is using a PRIME Z270-A. The only different between these 2 mobos, is that the AR version only has a HDMI output where the A version also has DVI.
Another difference is that I already installed 2 M.2 to PCI adapters in this new mobo (plan to run 9 GPUs), but I have no GPU's connected yet. Both rigs run Celeron G3930 CPUs (I have posted another question about using Celerons with 8+ GPUs, but I don't see how that could be related to this).
I did install the latest BIOS before I got started, and I configured the BIOS exactly the same as my other PRIME Z270-A, which has the following settings:
Advanced/Platform Misc Configuration - Everything Disabled
Advanced/System Agent (SA) Configuration / Graphics Configuration / Leave alone
Advanced/System Agent (SA) Configuration / Graphics Configuration / DMI/OPI Configuration / DMI Max Link Speed = Gen2
Advanced/System Agent (SA) Configuration / Graphics Configuration / PEG Port Configuration / Gen2, Gen2, Auto
Advanced/PCH Configuration / PCI Express Configuration / Gen2
Advanced/PCH-FW Configuration/PTT Configuration/PTP aware OS = Not PTP Aware
Advanced/Onboard Devices Configuration / HD Audio Controller = Disabled
Advanced/Onboard Devices Configuration / M.2_1 Configuration = Auto
Advanced/Onboard Devices Configuration / M.2_2 Bandwidth Configuration = X2
Advanced/Onboard Devices Configuration / RGB LED Lighting / In Sleep, hibernate and soft off states = Off
Advanced/APM Configuration / Restore AC Power Loss = Power On
Boot / Above 4G Decoding = Enabled
Boot/Secure Boot/Key Management/Clear Secure Boot Keys = YES
I went ahead and installed windows onto that 64G SSD just to make sure everything worked fine with the rest of the system, and it did.
Any ideas why nvOC doesn't appear to like the PRIME Z270-AR mobo?
One last note, I never did edit 1bash in Windows, I just "ejected" both USB partitions under windows, and then booted the 0019 image on the Asus.
/dev/sdax: clean, xxxxxx/xxxxxxx files, xxxxx/xxx blocks is output from a fsck check.
Thats not an error
Let it check the drive and it will boot for sure
Ran into an issue I've never encountered before. When doing a boot from a freshly imaged 32G USB (same make, model and size I use in all my other rigs), after the initial boot where the 1bash file is converted from dos to unix, I get stuck here on the 2nd boot:
I tried re-imaging the USB drive twice, but get stuck at the same place every time. I even imaged 0019 to a 64GB SSD and still got stuck in the exact same place, see below:
The mobo I'm using is an Asus PRIME Z270-AR. My other Asus rig is using a PRIME Z270-A. The only different between these 2 mobos, is that the AR version only has a HDMI output where the A version also has DVI.
Another difference is that I already installed 2 M.2 to PCI adapters in this new mobo (plan to run 9 GPUs), but I have no GPU's connected yet. Both rigs run Celeron G3930 CPUs (I have posted another question about using Celerons with 8+ GPUs, but I don't see how that could be related to this).
I did install the latest BIOS before I got started, and I configured the BIOS exactly the same as my other PRIME Z270-A, which has the following settings:
Advanced/Platform Misc Configuration - Everything Disabled
Advanced/System Agent (SA) Configuration / Graphics Configuration / Leave alone
Advanced/System Agent (SA) Configuration / Graphics Configuration / DMI/OPI Configuration / DMI Max Link Speed = Gen2
Advanced/System Agent (SA) Configuration / Graphics Configuration / PEG Port Configuration / Gen2, Gen2, Auto
Advanced/PCH Configuration / PCI Express Configuration / Gen2
Advanced/PCH-FW Configuration/PTT Configuration/PTP aware OS = Not PTP Aware
Advanced/Onboard Devices Configuration / HD Audio Controller = Disabled
Advanced/Onboard Devices Configuration / M.2_1 Configuration = Auto
Advanced/Onboard Devices Configuration / M.2_2 Bandwidth Configuration = X2
Advanced/Onboard Devices Configuration / RGB LED Lighting / In Sleep, hibernate and soft off states = Off
Advanced/APM Configuration / Restore AC Power Loss = Power On
Boot / Above 4G Decoding = Enabled
Boot/Secure Boot/Key Management/Clear Secure Boot Keys = YES
I went ahead and installed windows onto that 64G SSD just to make sure everything worked fine with the rest of the system, and it did.
Any ideas why nvOC doesn't appear to like the PRIME Z270-AR mobo?
One last note, I never did edit 1bash in Windows, I just "ejected" both USB partitions under windows, and then booted the 0019 image on the Asus.
I tried re-imaging the USB drive twice, but get stuck at the same place every time. I even imaged 0019 to a 64GB SSD and still got stuck in the exact same place, see below:
The mobo I'm using is an Asus PRIME Z270-AR. My other Asus rig is using a PRIME Z270-A. The only different between these 2 mobos, is that the AR version only has a HDMI output where the A version also has DVI.
Another difference is that I already installed 2 M.2 to PCI adapters in this new mobo (plan to run 9 GPUs), but I have no GPU's connected yet. Both rigs run Celeron G3930 CPUs (I have posted another question about using Celerons with 8+ GPUs, but I don't see how that could be related to this).
I did install the latest BIOS before I got started, and I configured the BIOS exactly the same as my other PRIME Z270-A, which has the following settings:
Advanced/Platform Misc Configuration - Everything Disabled
Advanced/System Agent (SA) Configuration / Graphics Configuration / Leave alone
Advanced/System Agent (SA) Configuration / Graphics Configuration / DMI/OPI Configuration / DMI Max Link Speed = Gen2
Advanced/System Agent (SA) Configuration / Graphics Configuration / PEG Port Configuration / Gen2, Gen2, Auto
Advanced/PCH Configuration / PCI Express Configuration / Gen2
Advanced/PCH-FW Configuration/PTT Configuration/PTP aware OS = Not PTP Aware
Advanced/Onboard Devices Configuration / HD Audio Controller = Disabled
Advanced/Onboard Devices Configuration / M.2_1 Configuration = Auto
Advanced/Onboard Devices Configuration / M.2_2 Bandwidth Configuration = X2
Advanced/Onboard Devices Configuration / RGB LED Lighting / In Sleep, hibernate and soft off states = Off
Advanced/APM Configuration / Restore AC Power Loss = Power On
Boot / Above 4G Decoding = Enabled
Boot/Secure Boot/Key Management/Clear Secure Boot Keys = YES
I went ahead and installed windows onto that 64G SSD just to make sure everything worked fine with the rest of the system, and it did.
Any ideas why nvOC doesn't appear to like the PRIME Z270-AR mobo?
One last note, I never did edit 1bash in Windows, I just "ejected" both USB partitions under windows, and then booted the 0019 image on the Asus.
Im pretty sure I tested nvOC with one of my Asus Prime(Z270-A) a few weeks and it was fine. Im getting another one this week, Ill test it again if I have the time.
Hello,
One of my rigs that prevoiusly ran 2x 1070 with +145/+1300 OC was upgraded to 6x of these GPU's.
It is not stable anymore tho, the miner crashes 2 times an hour, where to begin looking?
When I check /var/logs/kernel.log & xorg.0.log they are both empty, but created with the same timestamp of the crash.
What do?
G3900 Cpu
H110-D3A mobo
Also, at the time of the crash, watchdog shows 0 GPU tjreshold on all devices.
Mining Zcash with zm on v0019 1.2
One of my rigs that prevoiusly ran 2x 1070 with +145/+1300 OC was upgraded to 6x of these GPU's.
It is not stable anymore tho, the miner crashes 2 times an hour, where to begin looking?
When I check /var/logs/kernel.log & xorg.0.log they are both empty, but created with the same timestamp of the crash.
What do?
G3900 Cpu
H110-D3A mobo
Also, at the time of the crash, watchdog shows 0 GPU tjreshold on all devices.
Mining Zcash with zm on v0019 1.2
Ran into an issue I've never encountered before. When doing a boot from a freshly imaged 32G USB (same make, model and size I use in all my other rigs), after the initial boot where the 1bash file is converted from dos to unix, I get stuck here on the 2nd boot:
I tried re-imaging the USB drive twice, but get stuck at the same place every time. I even imaged 0019 to a 64GB SSD and still got stuck in the exact same place, see below:
The mobo I'm using is an Asus PRIME Z270-AR. My other Asus rig is using a PRIME Z270-A. The only different between these 2 mobos, is that the AR version only has a HDMI output where the A version also has DVI.
Another difference is that I already installed 2 M.2 to PCI adapters in this new mobo (plan to run 9 GPUs), but I have no GPU's connected yet. Both rigs run Celeron G3930 CPUs (I have posted another question about using Celerons with 8+ GPUs, but I don't see how that could be related to this).
I did install the latest BIOS before I got started, and I configured the BIOS exactly the same as my other PRIME Z270-A, which has the following settings:
Advanced/Platform Misc Configuration - Everything Disabled
Advanced/System Agent (SA) Configuration / Graphics Configuration / Leave alone
Advanced/System Agent (SA) Configuration / Graphics Configuration / DMI/OPI Configuration / DMI Max Link Speed = Gen2
Advanced/System Agent (SA) Configuration / Graphics Configuration / PEG Port Configuration / Gen2, Gen2, Auto
Advanced/PCH Configuration / PCI Express Configuration / Gen2
Advanced/PCH-FW Configuration/PTT Configuration/PTP aware OS = Not PTP Aware
Advanced/Onboard Devices Configuration / HD Audio Controller = Disabled
Advanced/Onboard Devices Configuration / M.2_1 Configuration = Auto
Advanced/Onboard Devices Configuration / M.2_2 Bandwidth Configuration = X2
Advanced/Onboard Devices Configuration / RGB LED Lighting / In Sleep, hibernate and soft off states = Off
Advanced/APM Configuration / Restore AC Power Loss = Power On
Boot / Above 4G Decoding = Enabled
Boot/Secure Boot/Key Management/Clear Secure Boot Keys = YES
I went ahead and installed windows onto that 64G SSD just to make sure everything worked fine with the rest of the system, and it did.
Any ideas why nvOC doesn't appear to like the PRIME Z270-AR mobo?
One last note, I never did edit 1bash in Windows, I just "ejected" both USB partitions under windows, and then booted the 0019 image on the Asus.
I tried re-imaging the USB drive twice, but get stuck at the same place every time. I even imaged 0019 to a 64GB SSD and still got stuck in the exact same place, see below:
The mobo I'm using is an Asus PRIME Z270-AR. My other Asus rig is using a PRIME Z270-A. The only different between these 2 mobos, is that the AR version only has a HDMI output where the A version also has DVI.
Another difference is that I already installed 2 M.2 to PCI adapters in this new mobo (plan to run 9 GPUs), but I have no GPU's connected yet. Both rigs run Celeron G3930 CPUs (I have posted another question about using Celerons with 8+ GPUs, but I don't see how that could be related to this).
I did install the latest BIOS before I got started, and I configured the BIOS exactly the same as my other PRIME Z270-A, which has the following settings:
Advanced/Platform Misc Configuration - Everything Disabled
Advanced/System Agent (SA) Configuration / Graphics Configuration / Leave alone
Advanced/System Agent (SA) Configuration / Graphics Configuration / DMI/OPI Configuration / DMI Max Link Speed = Gen2
Advanced/System Agent (SA) Configuration / Graphics Configuration / PEG Port Configuration / Gen2, Gen2, Auto
Advanced/PCH Configuration / PCI Express Configuration / Gen2
Advanced/PCH-FW Configuration/PTT Configuration/PTP aware OS = Not PTP Aware
Advanced/Onboard Devices Configuration / HD Audio Controller = Disabled
Advanced/Onboard Devices Configuration / M.2_1 Configuration = Auto
Advanced/Onboard Devices Configuration / M.2_2 Bandwidth Configuration = X2
Advanced/Onboard Devices Configuration / RGB LED Lighting / In Sleep, hibernate and soft off states = Off
Advanced/APM Configuration / Restore AC Power Loss = Power On
Boot / Above 4G Decoding = Enabled
Boot/Secure Boot/Key Management/Clear Secure Boot Keys = YES
I went ahead and installed windows onto that 64G SSD just to make sure everything worked fine with the rest of the system, and it did.
Any ideas why nvOC doesn't appear to like the PRIME Z270-AR mobo?
One last note, I never did edit 1bash in Windows, I just "ejected" both USB partitions under windows, and then booted the 0019 image on the Asus.
Hi guys,
I've problems with detecting all installed GPUs. I bought 13x risers V008S with 100cm USB 3 cables. Installed 11x 1080Ti, but system detect only 10.
There are 3 PSU (2x 1700W, 1x 1200W). Each GPU is connected on same PSU as riser. I don't know why I don't see all cards. There is some way, how detect which cars wasn't recognise?
Mobo: ASRock PRO (for 13 gpus)
Unfortunatelly this is not one problem which I have... :-(
Miner is running and sometimes is killed immediately after execution for 5 or more cycles, so it's mean that I don't mine for 20 minutes - if mining MONA.
Safter sometimes has same problem... :-(
I've problems with detecting all installed GPUs. I bought 13x risers V008S with 100cm USB 3 cables. Installed 11x 1080Ti, but system detect only 10.
There are 3 PSU (2x 1700W, 1x 1200W). Each GPU is connected on same PSU as riser. I don't know why I don't see all cards. There is some way, how detect which cars wasn't recognise?
Mobo: ASRock PRO (for 13 gpus)
Unfortunatelly this is not one problem which I have... :-(
Miner is running and sometimes is killed immediately after execution for 5 or more cycles, so it's mean that I don't mine for 20 minutes - if mining MONA.
Safter sometimes has same problem... :-(
Run the miner for a bit then feel each GPU; the one that is cold is the undetected one.
My guess is that MONA often uses less than 90% to reduce this to a MONA friendly level open:
IAmNotAJeep_and_Maxximus007_WATCHDOG
and edit:
Code:
THRESHOLD=90
to:
Code:
THRESHOLD=65
I tried clean installation nvOS v0019. Same problem...
Crash log:
Code:
[2017-10-08 04:41:49] GPU #3: the launch timed out and was terminated
[2017-10-08 04:41:49] GPU #0: Gigabyte GTX 1080 Ti, 8358.70 MH/s
[2017-10-08 04:41:49] GPU #0: the launch timed out and was terminated
[2017-10-08 04:41:49] GPU #5: Gigabyte GTX 1080 Ti, 7946.02 MH/s
[2017-10-08 04:41:49] GPU #5: the launch timed out and was terminated
[2017-10-08 04:41:49] GPU #4: Gigabyte GTX 1080 Ti, 8785.84 MH/s
[2017-10-08 04:41:49] GPU #4: the launch timed out and was terminated
[2017-10-08 04:41:49] GPU #8: Gigabyte GTX 1080 Ti, 8819.18 MH/s
[2017-10-08 04:41:49] GPU #8: the launch timed out and was terminated
[2017-10-08 04:41:49] GPU #6: Gigabyte GTX 1080 Ti, 8189.00 MH/s
[2017-10-08 04:41:49] GPU #6: the launch timed out and was terminated
[2017-10-08 04:41:49] GPU #7: Gigabyte GTX 1080 Ti, 12.07 GH/s
[2017-10-08 04:41:49] GPU #7: the launch timed out and was terminated
[2017-10-08 04:41:49] GPU #10: Gigabyte GTX 1080 Ti, 7792.20 MH/s
[2017-10-08 04:41:49] GPU #10: the launch timed out and was terminated
^C[2017-10-08 04:41:49] SIGINT received, exiting
*** Error in `/home/m1/SPccminer/ccminer': double free or corruption (out): 0x00007f7e994bda60 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f7f13f977e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7f7f13fa037a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f7f13fa453c]
/home/m1/SPccminer/ccminer[0x42a23a]
/home/m1/SPccminer/ccminer[0x405715]
/home/m1/SPccminer/ccminer[0x40f33a]
/lib/x86_64-linux-gnu/libc.so.6(+0x354b0)[0x7f7f13f554b0]
/lib/x86_64-linux-gnu/libpthread.so.0(pthread_join+0xbb)[0x7f7f1566398b]
/home/m1/SPccminer/ccminer[0x406870]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f7f13f40830]
/home/m1/SPccminer/ccminer[0x40d3c9]
======= Memory map: ========
00400000-00fe3000 r-xp 00000000 08:02 393655 /home/m1/SPccminer/ccminer
011e2000-011e3000 r--p 00be2000 08:02 393655 /home/m1/SPccminer/ccminer
011e3000-011e7000 rw-p 00be3000 08:02 393655 /home/m1/SPccminer/ccminer
011e7000-04248000 rw-p 00000000 00:00 0
046a9000-0474a000 rw-p 00000000 00:00 0 [heap]
200000000-200200000 ---p 00000000 00:00 0
200200000-200400000 rw-s 241dfa000 00:06 460 /dev/nvidiactl
200400000-200600000 rw-s 70115000 00:06 460 /dev/nvidiactl
200600000-200800000 rw-s 6f126000 00:06 460 /dev/nvidiactl
200800000-200a00000 rw-s 1f2669000 00:06 460 /dev/nvidiactl
200a00000-200c00000 rw-s 247648000 00:06 460 /dev/nvidiactl
200c00000-200e00000 rw-s 1f9b94000 00:06 460 /dev/nvidiactl
200e00000-201000000 rw-s 1fba1f000 00:06 460 /dev/nvidiactl
201000000-201200000 rw-s 203250000 00:06 460 /dev/nvidiactl
201200000-201400000 rw-s 1e94be000 00:06 460
OK guys
Here is My WhatToMine Auto Switch forked from damNmad smartminer
It will check the coins you want to mine then based on your cards and your own url mine the top coin if difficulty low and profit is high
These are the files:
WTM_AUTO_SWITCH
WTM_AUTO_SWITCH.py
Put both in /home/m1/
Edit /home/m1/1bash and add :
#WTM_AUTO_SWITCH_diff="TO BE ADDED IN NEXT VERSIONS" # PERCENTAGE TO CHANGE IF TOP COIN IS HIGHER THAN CURRENT COIN
Edit /home/m1/3main and add these lines somewhere after Maxximus007_AUTO_TEMPERATURE_CONTROL ( easier to find "SALFTER_NICEHASH_PROFIT_SWITCHING" and add before it:
Install requests python module with :
Go to whattomine select your cards, hash rate, power.
You can also select to mine base on current, 24 hour, 3 day or a week profit and difficulty.
Dont forget to choose same for both profit and difficulty or it will give wrong results.
Click calculate, then add .json to coins at the begining of the address after you click calculate!!!
From:
To:
Copy the whole address and paste it to WTM_AUTO_SWITCH.py replace the default address:
Set the coins you want to be switched in WTM_AUTO_SWITCH.py in the included tags :
Now you can start wtm auto switch with
P.S
Need help to improve the WTM_AUTO_SWITCH.py script, if any one willing to help please let me know.
Here is My WhatToMine Auto Switch forked from damNmad smartminer
It will check the coins you want to mine then based on your cards and your own url mine the top coin if difficulty low and profit is high
These are the files:
WTM_AUTO_SWITCH
WTM_AUTO_SWITCH.py
Put both in /home/m1/
Edit /home/m1/1bash and add :
Code:
# WTM AUTO SWITCH SETTINGS# remember to disable Parallax MODE (_Parallax_MODE="NO")
WTM_AUTO_SWITCH="YES"
WTM_AUTO_SWITCH_SYNC_INTERVAL="3" # Time to sync with WTM for best coin
#WTM_AUTO_SWITCH_URL="FOR NOW EDIT IT IN WTM_AUTO_SWITCH.py
#WTM_AUTO_SWITCH_COINS=" FOR NOW EDIT IT IN WTM_AUTO_SWITCH.py > includeTags = [ 'ZEC', 'ZEN', 'ZCL', 'SIB' , 'LBC' ]
Edit /home/m1/3main and add these lines somewhere after Maxximus007_AUTO_TEMPERATURE_CONTROL ( easier to find "SALFTER_NICEHASH_PROFIT_SWITCHING" and add before it:
Code:
if [ $WTM_AUTO_SWITCH == "YES" ]
then
HCD='/home/m1/WTM_AUTO_SWITCH'
running=$(ps -ef | awk '$NF~"WTM_AUTO_SWITCH" {print $2}')
if [ "$running" == "" ]
then
guake -n $HCD -r WTM_AUTO_SWITCH -e "bash /home/m1/WTM_AUTO_SWITCH"
running=""
fi
fi
Install requests python module with :
Code:
sudo apt install python-requests
Go to whattomine select your cards, hash rate, power.
You can also select to mine base on current, 24 hour, 3 day or a week profit and difficulty.
Dont forget to choose same for both profit and difficulty or it will give wrong results.
Click calculate, then add .json to coins at the begining of the address after you click calculate!!!
From:
Code:
https://whattomine.com/coins?utf8=✓&adapt_q_280x=0....
Code:
https://whattomine.com/coins.json?utf8=✓&adapt_q_280x=0&adapt_q_380=0&adapt_q_fury=0&adapt_q
Copy the whole address and paste it to WTM_AUTO_SWITCH.py replace the default address:
Code:
data = requests.get("https://whattomine.com/coins.json");
Code:
includeTags = [ 'ZEC', 'ZEN', 'ZCL', 'SIB' , 'LBC' ]
Now you can start wtm auto switch with
Code:
bash WTM_AUTO_SWITCH &
P.S
Need help to improve the WTM_AUTO_SWITCH.py script, if any one willing to help please let me know.
I'm excited for this!
When I run it, I'm getting an error: ValueError: No JSON object could be decoded
cat: /home/m1/top_coin: No such file or directory
screen killed (pid 15856)
screen killed (pid 15857)
It looks like it's trying to find a file that doesn't exist: TOP_COIN=$(cat /home/m1/top_coin). There is no "top_coin" file in home/m1. Is it supposed to create one?
Are you sure you put both in /home/m1/ ?
WTM_AUTO_SWITCH
WTM_AUTO_SWITCH.py
Also did you change the link and add .json to link ?
First run may gives error, let it go for 2nd cycle and it should be ok,
I did not add .json. Now it's working! Looks good! It is opening a new terminal for the auto temperature control each time it switches. So there are many temp control terminals open that say they were terminated. Other than that. It looks good!
Thats because your setting is local and WTM_AUTO_SWITCH kills 3main to restart miner
Already talked with fullzero to make changes so it can only restart miner instead of restarting 3main,
OK guys
Here is My WhatToMine Auto Switch forked from damNmad smartminer
It will check the coins you want to mine then based on your cards and your own url mine the top coin if difficulty low and profit is high
These are the files:
WTM_AUTO_SWITCH
WTM_AUTO_SWITCH.py
Put both in /home/m1/
Edit /home/m1/1bash and add :
#WTM_AUTO_SWITCH_diff="TO BE ADDED IN NEXT VERSIONS" # PERCENTAGE TO CHANGE IF TOP COIN IS HIGHER THAN CURRENT COIN
Edit /home/m1/3main and add these lines somewhere after Maxximus007_AUTO_TEMPERATURE_CONTROL ( easier to find "SALFTER_NICEHASH_PROFIT_SWITCHING" and add before it:
Install requests python module with :
Go to whattomine select your cards, hash rate, power.
You can also select to mine base on current, 24 hour, 3 day or a week profit and difficulty.
Dont forget to choose same for both profit and difficulty or it will give wrong results.
Click calculate, then add .json to coins at the begining of the address after you click calculate!!!
From:
To:
Copy the whole address and paste it to WTM_AUTO_SWITCH.py replace the default address:
Set the coins you want to be switched in WTM_AUTO_SWITCH.py in the included tags :
Now you can start wtm auto switch with
P.S
Need help to improve the WTM_AUTO_SWITCH.py script, if any one willing to help please let me know.
Here is My WhatToMine Auto Switch forked from damNmad smartminer
It will check the coins you want to mine then based on your cards and your own url mine the top coin if difficulty low and profit is high
These are the files:
WTM_AUTO_SWITCH
WTM_AUTO_SWITCH.py
Put both in /home/m1/
Edit /home/m1/1bash and add :
Code:
# WTM AUTO SWITCH SETTINGS# remember to disable Parallax MODE (_Parallax_MODE="NO")
WTM_AUTO_SWITCH="YES"
WTM_AUTO_SWITCH_SYNC_INTERVAL="3" # Time to sync with WTM for best coin
#WTM_AUTO_SWITCH_URL="FOR NOW EDIT IT IN WTM_AUTO_SWITCH.py
#WTM_AUTO_SWITCH_COINS=" FOR NOW EDIT IT IN WTM_AUTO_SWITCH.py > includeTags = [ 'ZEC', 'ZEN', 'ZCL', 'SIB' , 'LBC' ]
Edit /home/m1/3main and add these lines somewhere after Maxximus007_AUTO_TEMPERATURE_CONTROL ( easier to find "SALFTER_NICEHASH_PROFIT_SWITCHING" and add before it:
Code:
if [ $WTM_AUTO_SWITCH == "YES" ]
then
HCD='/home/m1/WTM_AUTO_SWITCH'
running=$(ps -ef | awk '$NF~"WTM_AUTO_SWITCH" {print $2}')
if [ "$running" == "" ]
then
guake -n $HCD -r WTM_AUTO_SWITCH -e "bash /home/m1/WTM_AUTO_SWITCH"
running=""
fi
fi
Install requests python module with :
Code:
sudo apt install python-requests
Go to whattomine select your cards, hash rate, power.
You can also select to mine base on current, 24 hour, 3 day or a week profit and difficulty.
Dont forget to choose same for both profit and difficulty or it will give wrong results.
Click calculate, then add .json to coins at the begining of the address after you click calculate!!!
From:
Code:
https://whattomine.com/coins?utf8=✓&adapt_q_280x=0....
Code:
https://whattomine.com/coins.json?utf8=✓&adapt_q_280x=0&adapt_q_380=0&adapt_q_fury=0&adapt_q
Copy the whole address and paste it to WTM_AUTO_SWITCH.py replace the default address:
Code:
data = requests.get("https://whattomine.com/coins.json");
Code:
includeTags = [ 'ZEC', 'ZEN', 'ZCL', 'SIB' , 'LBC' ]
Now you can start wtm auto switch with
Code:
bash WTM_AUTO_SWITCH &
P.S
Need help to improve the WTM_AUTO_SWITCH.py script, if any one willing to help please let me know.
I'm excited for this!
When I run it, I'm getting an error: ValueError: No JSON object could be decoded
cat: /home/m1/top_coin: No such file or directory
screen killed (pid 15856)
screen killed (pid 15857)
It looks like it's trying to find a file that doesn't exist: TOP_COIN=$(cat /home/m1/top_coin). There is no "top_coin" file in home/m1. Is it supposed to create one?
Are you sure you put both in /home/m1/ ?
WTM_AUTO_SWITCH
WTM_AUTO_SWITCH.py
Also did you change the link and add .json to link ?
First run may gives error, let it go for 2nd cycle and it should be ok,
I did not add .json. Now it's working! Looks good! It is opening a new terminal for the auto temperature control each time it switches. So there are many temp control terminals open that say they were terminated. Other than that. It looks good!
Hi guys,
I've problems with detecting all installed GPUs. I bought 13x risers V008S with 100cm USB 3 cables. Installed 11x 1080Ti, but system detect only 10.
There are 3 PSU (2x 1700W, 1x 1200W). Each GPU is connected on same PSU as riser. I don't know why I don't see all cards. There is some way, how detect which cars wasn't recognise?
Mobo: ASRock PRO (for 13 gpus)
Unfortunatelly this is not one problem which I have... :-(
Miner is running and sometimes is killed immediately after execution for 5 or more cycles, so it's mean that I don't mine for 20 minutes - if mining MONA.
Safter sometimes has same problem... :-(
I've problems with detecting all installed GPUs. I bought 13x risers V008S with 100cm USB 3 cables. Installed 11x 1080Ti, but system detect only 10.
There are 3 PSU (2x 1700W, 1x 1200W). Each GPU is connected on same PSU as riser. I don't know why I don't see all cards. There is some way, how detect which cars wasn't recognise?
Mobo: ASRock PRO (for 13 gpus)
Unfortunatelly this is not one problem which I have... :-(
Miner is running and sometimes is killed immediately after execution for 5 or more cycles, so it's mean that I don't mine for 20 minutes - if mining MONA.
Safter sometimes has same problem... :-(
Run the miner for a bit then feel each GPU; the one that is cold is the undetected one.
My guess is that MONA often uses less than 90% to reduce this to a MONA friendly level open:
IAmNotAJeep_and_Maxximus007_WATCHDOG
and edit:
Code:
THRESHOLD=90
to:
Code:
THRESHOLD=65
Jump to: