 Show Posts
|
|
Pages: « 1 [2] 3 »
|
|
So I tried SMOS for my 8x1080ti rig (running with 2 psu), I understand that the OC function is not available for this alpha version, but for the Power consumption, the accepted value is only from 70-150, can you make it from 70 to 300 so I can manage it better? In addition, when I set the Power to 0, or to 250, which mean I want it to run at factory setting, the system just does not recognize my 3 GPU which run via a 2nd PSU, but if I set the power value to 150, the system will recognize all 8 cards.
So for easier to understand:
1- If I set power to 150w, everything is fine, although the hashrate is as now as 580 sols, but the 8 cards running fine.
2- If I do not set power or set to 0 or 250, the system initially recognize all 8 gpu, then it display the error code
"The pci:0:0:2 has fallen of the bus"
"The pci:0:0:3 has fallen of the bus"
"The pci:0:0:4 has fallen of the bus"
These 3 gpu is powered by the 2nd psu, the 5 remaining gpus which powered by my main PSU running well at 250w and 720sols.
Do you have any ideas how can I solve this issue?
|
|
|
|
Thank you for your information, do you mean that I can just download the new version and paste it to EWBF directory? Can you please let me know where does the EWBF file locate in nvOC? I tried to search but I can not find it. Hi fullhero, I see that EWBF update to version 0.3.4b, do I need to reimage with the new nvOC version or I can update it directly in the OS? In addition I see that all MOBO now can use the same nvOC image v0015, right?
Thank you so much for your awesome work.
Yes just copy it and it works nicely (+0-2% faster). You might want to add --api 0.0.0.0:42000 to the miner string in oneBash, EWBF has a nice monitoring page now. |
|
|
|
Awsome rig, dude, do you use 2 psu 1600w for this rig? And can you share what kind of MOBO you use please? Thanks to EWBF for the 0.3.4b update, here are my updated benchmarks (not yet optimised):
11 x 1080 Ti FE
Ubuntu 16.04.2 LTS
NVIDIA Driver Version 381.22
EWBF's Zcash CUDA miner. 0.3.4b
+-------------------------------------------------+
| EWBF's Zcash CUDA miner. 0.3.4b |
+-------------------------------------------------+
INFO: Current pool: <redacted>
INFO: Selected pools: 1
INFO: Solver: Auto.
INFO: Devices: All.
INFO: Temperature limit: 90
INFO: Api: Disabled
---------------------------------------------------
---
CUDA: Device: 0 GeForce GTX 1080 Ti, 11172 MB i:64
CUDA: Device: 1 GeForce GTX 1080 Ti, 11172 MB i:64
CUDA: Device: 2 GeForce GTX 1080 Ti, 11172 MB i:64
CUDA: Device: 3 GeForce GTX 1080 Ti, 11172 MB i:64
CUDA: Device: 4 GeForce GTX 1080 Ti, 11172 MB i:64
CUDA: Device: 5 GeForce GTX 1080 Ti, 11172 MB i:64
CUDA: Device: 6 GeForce GTX 1080 Ti, 11172 MB i:64
CUDA: Device: 7 GeForce GTX 1080 Ti, 11172 MB i:64
CUDA: Device: 8 GeForce GTX 1080 Ti, 11172 MB i:64
CUDA: Device: 9 GeForce GTX 1080 Ti, 11172 MB i:64
CUDA: Device: 10 GeForce GTX 1080 Ti, 11172 MB i:64
CUDA: Device: 0 Selected solver: 2
CUDA: Device: 2 Selected solver: 2
CUDA: Device: 4 Selected solver: 2
CUDA: Device: 1 Selected solver: 2
CUDA: Device: 3 Selected solver: 0
CUDA: Device: 5 Selected solver: 0
CUDA: Device: 9 Selected solver: 2
CUDA: Device: 6 Selected solver: 2
CUDA: Device: 7 Selected solver: 2
CUDA: Device: 8 Selected solver: 2
CUDA: Device: 10 Selected solver: 0
---
Temp: GPU0: 42C GPU1: 43C GPU2: 39C GPU3: 42C GPU4: 48C GPU5: 45C GPU6: 41C GPU7: 49C GPU8: 44C GPU9: 41C GPU10: 46C
GPU0: 751 Sol/s GPU1: 731 Sol/s GPU2: 749 Sol/s GPU3: 758 Sol/s GPU4: 737 Sol/s GPU5: 762 Sol/s GPU6: 748 Sol/s GPU7: 760 Sol/s GPU8: 738 Sol/s GPU9: 755 Sol/s GPU10: 742 Sol/s
Total speed: 8231 Sol/s
+-----+-------------+--------------+
| GPU | Power usage | Efficiency |
+-----+-------------+--------------+
| 0 | 280W | 2.68 Sol/W |
| 1 | 271W | 2.70 Sol/W |
| 2 | 273W | 2.74 Sol/W |
| 3 | 275W | 2.76 Sol/W |
| 4 | 271W | 2.72 Sol/W |
| 5 | 273W | 2.79 Sol/W |
| 6 | 278W | 2.69 Sol/W |
| 7 | 286W | 2.66 Sol/W |
| 8 | 272W | 2.71 Sol/W |
| 9 | 271W | 2.79 Sol/W |
| 10 | 271W | 2.74 Sol/W |
+-----+-------------+--------------+
---
|
|
|
|
|
Hi fullhero, I see that EWBF update to version 0.3.4b, do I need to reimage with the new nvOC version or I can update it directly in the OS? In addition I see that all MOBO now can use the same nvOC image v0015, right?
Thank you so much for your awesome work.
|
|
|
|
Hey folks,
So I am new to mining. Only cards I could get a couple of weeks ago was GTX1070 (as most of you know, AMD is nowhere to be found).
I have had a my first rig set up for about 10 days. Windows 10, MSI Z270-A Plus mobo, 5x MSI GTX 1070 Gaming X 8G. I mine ETH only, using Claymore. I am averaging about 30.6 M/H per card with decent stability. Rig power draw 830 watts for 5 cards. Temp 59-61 degrees. Fan speed 60%
Currently using nvidia 382.05 driver.
So I am awaiting my last component today for a second rig same mobo, same cards (but a 6 card rig).
If I try Fullzero's nvOC what can I expect? I have zero experience with Linux, but I am comfortable with command line interfaces.
A few questions:
Do you always boot from USB? Or can you install on an ssd? My rig that has windows 10, if I change the boot order in BIOS to USB and boot with nvOC is this a "dual partition"?
Will I be able to get better stability and increase M/H?
Thanks
nvOC is the best solution for nvidia card if you have no idea about Linux, it is like plug and play usb, you just need to change the modify onebash file, which is pretty easy task for anyone who can set up a mining rig. My 6 1080Ti card run smoothly for 5 days. |
|
|
|
|
I think miners just point their L3+ to more profitable Scrypt coin like DGB or GAME, I myseft also do that, earn about 20% more comparing with mining LTC.
|
|
|
|
sure you can remove a hashing board, I always did it by adding an "air-dummy" not 2 influence the air-flow in the unit. I even did some redesigns to 1U or 2U 19" Units.  Thank you for your help dude, but can you please let me know which is the "air-dummy", do you mean it is just a blank plastic plate? |
|
|
|
|
Did you try to switch to Linux? If not you may want to try simplemining, really nice os.
|
|
|
|
Mining is like a high risk investment, and there are so many uncertain things which you can not simply put the number in and calculate it. So let predict the future: Situation 1: ETH price going up in the next 3 months, as well as the difficulty, so you still can ROI within 3 months, thanks to ETH price. Situation 2: ETH price stay in the range of $200-$250 in the next 3 months, but the difficulty still increase, so your calculation is not accurate anymore, the ROI should be 6-8 months in this case, and after ROI, your rig may take additional 12-16 months to get another $2500 if the price of ETH does not go up. Situation 3, the worst one: BTC, ETH price going down, difficulty still going up (cause people already invested in the equipment so they have to use it anyway), at this case you may expect around 15 months ROI, or maybe never ROI, but good thing is your cards have resale value, so you can still sell it. So the decision is yours, mining is fun, I must say that  , people tell others to not to invest to mining equipment but invest in the coin itself, that is also a good advice. Let s talk about my situation, I bought 8 L3+ to mine Litecoin for their 2nd batch on 5 May, it costs me total 11 BTC = $13,200, including PSU and shipping charge, the BTC price is $1200 that time. Now my 8 L3+ almost ROI, iti s about 80% ROI now But the opportunity cost is pretty high, since 11 BTC = $30,250, BTC price is $2750 at the moment. So do you think how long will my 8 L3+ earn me more $20,000 difference, considering more and more L3+ batch will come from Bitmain in the future? It is hard to say, but in term of investment, the decision to keep BTC instead of buying L3+ is a better decision. |
|
|
|
|
If you run in Window, you can use MSI Afterburner to adjust the Watt value, if you use Linux, you can open the Terminal and use the command : sudo nvidia-smi -pl 125
125 here is the watt number you want for all cards, you can pick the number which is suitable with your card type.
|
|
|
|
so no one overclocked L3+s?
Here you have a victim, dont do it, I oc 8 L3+ to 419 and 1 get trouble with the hashboard, now it only run with 3 hashboard and automatically restart each 2-3 minutes. It does not worth the risk. So I plan to remove the defective hashboard and let the L3+ run with only 3 hashboard only, maybe it will be more stable that way. Anyone try it with the S9 beofre? |
|
|
|
|
Guys, I know the S9 is famous for dead hash board, anyone managed to run it with only 2 boards instead of 3?
|
|
|
|
|
So I tried to run DGB since it is the new hot trend at the moment, overclock the card as core+200 and mem -300 as some people told in some topics. However the result is quite poor, it only does 650mh per card with that setting. I heard that 1080ti only do good on skein with cc miner 1.0, not sure if it is true or not, but I backed to mine Zcash since the rig run more stable with Zcash setting at the moment. Anyone get a better result with Skein on NVOC?
|
|
|
|
Hello guys, so one of my L3+ suddenly stop working as normal, it automatically reset after 2-3 minutes. I check the miner status and it seems the hash-board number 2 is defective, it just does not show up, only the board 1-3-4 are there. I understand that I can remove the defective board and send it to bitmain to ask for them to fix it, but in the meantime, can I assemble to L3+ again and run it with only 3 boards? It seems the design is similar to the S9, so anyone run S9 with only 2 or 1 hash-board before? Here is the screenshot of my miner status, do not know why it does not show up with the post, I insert the link between the IMG tag.  |
|
|
|
|
Thank you for the reply guys, I also believe 99% it was fried by my mistake, I will try to RMA tomorrow and hopefully they will accept it. At first I thought the usb 3.0 only handle the data transfer, whereas the power riser cable will handle the electricity, but I was so wrong.
|
|
|
|
Guys, I have a question regarding the VGA, yesterday I moved my rig to the new location and assemble it again, but stupid me I somehow put the usb riser for the 7th card like this  The small port of usb riser was connected to the wrong port on MOBO, when the wide port of riser connect to nothing. And then I boot the rig with nvOC, of course it only recognize 6 cards, I checked and saw what I did and I immediately shut down the rig and put the usb riser in the correct port. However from that time my rig can not recognize that specific GPU. I tried to: - Unplug all others GPU and use only that GPU but the window or linux can not recognize it - Install driver but it does not help too. - I plug the HDMI cable from the monitor to the gpu, but it does not help. - Plug the gpu to another working rig, but it does not help. The GPU fan and led is still running as normal, there is no smell. But I wonder if I accidentally shorted my card? Sadly it seems the warranty will be voided if the card is fried or shorted. I know it is not related to nvOc, but I see people here very responsive to any questions, so I really appreciate your help. The card is Galax 1080ti 11GB Sucks when things like this happen. Your card may still be able to be RMAed. Thanks for warning others to ensure pcie connectors are correct before powering on: you are not the first person to do this. On the plus side it looks like you are using a custom frame. Ya, that is the wooden shoes shelf I bought from the super market, take about some hours to customize it to use as a rig, but it is pretty good and time killing job. I will bring the card to the retailer tomorrow to see if it can be RMA, I hope they are ok with it. At first I thought the usb 3.0 only transfer the data, the power riser cable will handle the electricity, but I was so wrong, lol. |
|
|
|
Guys, I have a question regarding the GPU, yesterday I moved my rig with 7 cards to the new location and assemble it again, but stupid me I somehow put the usb riser for the 7th card like this https://i.imgur.com/xaRw3nll.jpgThe small port of usb riser was connected to the wrong port on MOBO, when the wide port of riser connect to nothing. And then I boot the rig with nvOC, of course it only recognize 6 cards, I checked and saw what I did and I immediately shut down the rig and put the usb riser in the correct port. However from that time my rig can not recognize that specific GPU. I tried to: - Unplug all others GPU and use only that GPU but the window or linux can not recognize it - Install driver but it does not help too. - I plug the HDMI cable from the monitor to the gpu, but it does not help. - Plug the gpu to another working rig, but it does not help. The GPU fan and led is still running as normal, there is no smell. But I wonder if I accidentally shorted my card? Sadly it seems the warranty will be voided if the card is fried or shorted. I really appreciate your help. The card is Galax 1080ti 11GB |
|
|
|
Guys, I have a question regarding the VGA, yesterday I moved my rig to the new location and assemble it again, but stupid me I somehow put the usb riser for the 7th card like this The small port of usb riser was connected to the wrong port on MOBO, when the wide port of riser connect to nothing. And then I boot the rig with nvOC, of course it only recognize 6 cards, I checked and saw what I did and I immediately shut down the rig and put the usb riser in the correct port. However from that time my rig can not recognize that specific GPU. I tried to: - Unplug all others GPU and use only that GPU but the window or linux can not recognize it - Install driver but it does not help too. - I plug the HDMI cable from the monitor to the gpu, but it does not help. - Plug the gpu to another working rig, but it does not help. The GPU fan and led is still running as normal, there is no smell. But I wonder if I accidentally shorted my card? Sadly it seems the warranty will be voided if the card is fried or shorted. I know it is not related to nvOc, but I see people here very responsive to any questions, so I really appreciate your help. The card is Galax 1080ti 11GB |
|
|
|
|
So here is my lspci
m1@m1-desktop:~$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
and here is my xorg.conf, as I see the busid is matched. I tried to change to value, for example, from 01:00:0 to 01:00.0, but it did not work.
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 381.09 (buildd@lgw01-19) Sat Apr 8 10:34:02 UTC 2017
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 378.13 (buildmeister@swio-display-x86-rhel47-05) Tue Feb 7 19:37:00 PST 2017
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" 1920 0
Screen 2 "Screen2" 3840 0
Screen 3 "Screen3" 5760 0
Screen 4 "Screen4" 7680 0
Screen 5 "Screen5" 9600 0
Screen 6 "Screen6" 11520 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "HannStar Display Corp HE225DPB"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "CLB fit Headless"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 76.0
EndSection
Section "Monitor"
Identifier "Monitor2"
VendorName "Unknown"
ModelName "CLB fit Headless"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 76.0
EndSection
Section "Monitor"
Identifier "Monitor3"
VendorName "Unknown"
ModelName "CLB fit Headless"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 76.0
EndSection
Section "Monitor"
Identifier "Monitor4"
VendorName "Unknown"
ModelName "CLB fit Headless"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 76.0
EndSection
Section "Monitor"
Identifier "Monitor5"
VendorName "Unknown"
ModelName "CLB fit Headless"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 76.0
EndSection
Section "Monitor"
Identifier "Monitor6"
VendorName "Unknown"
ModelName "CLB fit Headless"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 76.0
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 1050 Ti"
BusID "PCI:01:00:0"
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 1050 Ti"
BusID "PCI:02:00:0"
EndSection
Section "Device"
Identifier "Device2"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 1050 Ti"
BusID "PCI:04:00:0"
EndSection
Section "Device"
Identifier "Device3"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 1050 Ti"
BusID "PCI:05:00:0"
EndSection
Section "Device"
Identifier "Device4"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 1050 Ti"
BusID "PCI:06:00:0"
EndSection
Section "Device"
Identifier "Device5"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 1050 Ti"
BusID "PCI:08:00:0"
EndSection
Section "Device"
Identifier "Device6"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 1050 Ti"
BusID "PCI:09:00:0"
EndSection
Section "Screen"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-3"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-2"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-3"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-1"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-3"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-1"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-3"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "AllowEmptyInitialConfiguration" "True"
Option "Coolbits" "28"
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-1"
Option "metamodes" "nvidia-auto-select +0+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "AllowEmptyInitialConfiguration" "True"
Option "Coolbits" "28"
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-1"
Option "metamodes" "nvidia-auto-select +0+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-1"
Identifier "Screen2"
Device "Device2"
Monitor "Monitor2"
DefaultDepth 24
Option "AllowEmptyInitialConfiguration" "True"
Option "Coolbits" "28"
Option "nvidiaXineramaInfoOrder" "DFP-3"
Option "Stereo" "0"
Option "metamodes" "nvidia-auto-select +0+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-1"
Identifier "Screen3"
Device "Device3"
Monitor "Monitor3"
DefaultDepth 24
Option "AllowEmptyInitialConfiguration" "True"
Option "Coolbits" "28"
Option "nvidiaXineramaInfoOrder" "DFP-3"
Option "Stereo" "0"
Option "metamodes" "nvidia-auto-select +0+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen4"
Device "Device4"
Monitor "Monitor4"
DefaultDepth 24
Option "AllowEmptyInitialConfiguration" "True"
Option "Coolbits" "28"
Option "nvidiaXineramaInfoOrder" "DFP-3"
Option "Stereo" "0"
Option "metamodes" "nvidia-auto-select +0+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen5"
Device "Device5"
Monitor "Monitor5"
DefaultDepth 24
Option "AllowEmptyInitialConfiguration" "True"
Option "Coolbits" "28"
Option "nvidiaXineramaInfoOrder" "DFP-3"
Option "Stereo" "0"
Option "metamodes" "nvidia-auto-select +0+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen6"
Device "Device6"
Monitor "Monitor6"
DefaultDepth 24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-1"
Option "metamodes" "nvidia-auto-select +0+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection
|
|
|
|
Thank you so much for your help, here is the LSPCI
m1@m1-desktop:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Device 5902 (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
And here is the xorg.conf
This xorg.conf is missing large amounts of needed settings. I think I know what the problem is / happened. The image I made needs to NOT be using integrated graphics. You have integrated graphics enabled in the bios or have attached a monitor to the video output on the mobo and forced an auto configuration on the mobo to start the integrated graphics. This caused the system to create a new xorg.conf file which lacks almost all the needed changes. Technically the one needed should be stored as the backup, but fixing this image will probably take longer than the following: How is your monitor connected to your rig? If it is not attached to the second GPU please attach it there. Then shutdown your rig. Unplug the usb key. Power on the rig, bios should post. Restore defaults to the bios, it should need to restart to do this. When it has rebooted with default configurations, make these three bios changes here and no others: ensure 'Above 4G Decoding' is enabled in the bios.ensure PTP aware OS: is set to 'Not PTP Aware' in the bios.ensure you 'Clear Secure Boot Keys' in the biossave and reboot Now reimage your USB key with the ASUS PRIME Z270-A image. when it is done, attach to rig and press ctrl + alt + delete to reboot When ubuntu starts up watch the gnome terminal and see if OC occurs correctly. I think it will if you follow the previous steps. If it doesn't: open the guake terminal and enter: lspci | grep VGA and post what it says. If it does work also let me know. Edit: note when 7 cards are connected the monitor will display all black while booting; but will display normally once ubuntu starts. So I followed your instruction and it is working well now, just 1 problem, although the busid match 100% with other cards, onebash only recognize Gpu 0 (the one with hdmi cable plug to monitor), and only oc that card, for the remain 5 card i need to do it manually with nvidia x server app. For the oc value. I am using galax 1080ti, each time i try to oc it with cc200 mc >600, the system is almost crashed, sometimes the card not respone. I am using powerlimit 200, should I pl 125 as you do and oc 200-900? I may try it tomorrow since I am testing the stable of the system with the current oc value 150/450 before I go to sleep. And one more thing, the usb os is kind of quite slow, do you plan to make the os for ssd in the future? I see th e system quite laggy at the start, not sure if it can handle the 7 cards running in the long run, like 1 months continuesly. I really thank you for your os and your support for my problem, you are the real hero, man. |
|
|
|
|
