[ mining os ] nvoc - page 273. | Bitcointalksearch.org

philipma1957

legendary

Activity: 4354

Merit: 9201

'The right to privacy matters'

Quote from: Dhodge87 on August 09, 2017, 02:43:25 PM

Quote from: Dhodge87 on August 07, 2017, 07:58:12 AM

Quote from: Bibi187 on August 07, 2017, 03:18:08 AM

Quote from: Dhodge87 on August 06, 2017, 10:22:33 PM

Ok I was able to root and pull the current specs of my cards.
This is an 4x Gigabyte gtx 10606gb rig.
I have my MC set to 1050 in 1bash and if I'm reading this right it says I'm at a current clock of 8748 with a max of 8754.
How do I get more than a 750 MC increase?

If u want to mine SIGT u have to lower your MemTransferRate and up your nvclock

http://imgur.com/a/yZuOE

Be in root and

nvidia-settings -a /GPUGraphicsClockOffset[3]=value
nvidia-settings -a /GPUMemoryTransferRateOffset[3]=value

U can specify by GPU, like the other command

nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[3]=value
nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[3]=value

I am mining Eth
Is this what I need to do to get my cards on performance level 3?

I currently have in 1bash
CC=0
MC=950
But it doesn't appear to go past a MC of 750, in the Nvidia xserver it shows level 2 as highlighted and level 0,1,3 as greyed out and level 3 shows the clock that I have set in 1bash.

Also something else I noticed this morning
I have the powerlimit set to 75w right now in1bash.
When I start up everything runs smoothly for about 15 minutes, then one of my cards changes from a PL of 75 up to 125 and my MH/s drops from 161 down to 142.

I tested the rig with the card disconnected and it still has a 15-20 MH/s drop after about 15 minutes.

So is my question/problem to complicated?
Or am I that much of a noob you all just laugh it off and ignore me all together?

I am on an iPad mini it is hard to read your photos .

But your clocks are too aggressive .

Drop core a little
Drop ram a little
Try 80 for your watt settings
Can't tell your fan try 80.

If cards are too hot eth tends to throttle them.

If your clocks are too aggressive cards tend to reset power higher to allow the card to work.

Bibi187

full member

Activity: 420

Merit: 106

https://steemit.com/@bibi187

Quote from: Dhodge87 on August 09, 2017, 02:43:25 PM

Quote from: Dhodge87 on August 07, 2017, 07:58:12 AM

Quote from: Bibi187 on August 07, 2017, 03:18:08 AM

Quote from: Dhodge87 on August 06, 2017, 10:22:33 PM

Ok I was able to root and pull the current specs of my cards.
This is an 4x Gigabyte gtx 10606gb rig.
I have my MC set to 1050 in 1bash and if I'm reading this right it says I'm at a current clock of 8748 with a max of 8754.
How do I get more than a 750 MC increase?

https://i.imgur.com/Fh5XRQ4.png

If u want to mine SIGT u have to lower your MemTransferRate and up your nvclock

http://imgur.com/a/yZuOE

Be in root and

nvidia-settings -a /GPUGraphicsClockOffset[3]=value
nvidia-settings -a /GPUMemoryTransferRateOffset[3]=value

U can specify by GPU, like the other command

nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[3]=value
nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[3]=value

I am mining Eth
Is this what I need to do to get my cards on performance level 3?

I currently have in 1bash
CC=0
MC=950
But it doesn't appear to go past a MC of 750, in the Nvidia xserver it shows level 2 as highlighted and level 0,1,3 as greyed out and level 3 shows the clock that I have set in 1bash.

Also something else I noticed this morning
I have the powerlimit set to 75w right now in1bash.
When I start up everything runs smoothly for about 15 minutes, then one of my cards changes from a PL of 75 up to 125 and my MH/s drops from 161 down to 142.

I tested the rig with the card disconnected and it still has a 15-20 MH/s drop after about 15 minutes.

https://i.imgur.com/wJzXKVI.png

https://i.imgur.com/ra5iFQO.png

https://i.imgur.com/jy0ahPp.png

https://i.imgur.com/xZEtjTS.png

So is my question/problem to complicated?
Or am I that much of a noob you all just laugh it off and ignore me all together?

http://cryptomining-blog.com/7341-how-to-squeeze-some-extra-performance-mining-ethereum-on-nvidia/

dbolivar

member

Activity: 119

Merit: 10

Quote from: tomlev5 on August 09, 2017, 05:07:25 PM

dbolivar, how do I run the "top" utility?

I will post the irqbalance tomorow when I have time to test.

I also discovered something else: When I changed the POWERLIMIT from 150 to 200 (I have 1080 Ti cards) the CPU usage went from 100% to 80%. It is very strange. When GPUs have lower power limit the CPU becomes bottlenecked

Just type "top" at the terminal shell (e.g. the Guake terminal you access with F12). To quit top, type "q".

Regarding the powerlimit... That's very interesting! Looking forward for the "top" output I asked... I'm wondering if there's some sort of I/O queuing going on with the lower power limit (it will show as a high % of I/O wait or perhaps system usage). I suppose your hash rate also goes up a good amount by increasing the power limit, right?

tomlev5

newbie

Activity: 35

Merit: 0

Quote from: dbolivar on August 08, 2017, 07:23:19 PM

Quote from: tomlev5 on August 08, 2017, 05:02:55 PM

When I start the miner in single process:

1) breakdown of the CPU usage after about 20 minutes of uptime:
   1x process miner used 3:51
   14x process kworker (they used from 0:40 to 1:20)
   9x irq nvidia (they used from 0:40 to 1:03)

2) in the top twenty processes are miner, kworker, irq nvidia (nothing else)

3) if I type "ps aux | grep irqbalance" in Guake terminal i get two processes: one is root the other is m1.
What parameters can I check?

Thanks for helping dbolivar. I am stuck, because I have no experience with linux.

It's OK to have a high CPU usage time* for kworker and irq/nvidia, these account for internal kernel worker threads and interrupts for GPU I/O (expected on a multi-GPU rig mining). What I'm really looking for is how much CPU usage is for user processes, system processes, and I/O wait, that's why I asked these values. Try this: run the "top" utility, it will be constantly updating -- type "1", it will expand the third line (CPU usage summary) to show each CPU. Then paste the values here, like that:

%Cpu0 : 0.3 us, 1.0 sy, 0.0 ni, 98.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu1 : 0.3 us, 1.3 sy, 0.0 ni, 98.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
...
%CpuN : ....

Regarding irqbalance, running the command I suggested, you should get one line like this:

root 874 0.0 0.0 19536 2232 ? Ss Aug06 0:12 /usr/sbin/irqbalance --pid=/var/run/irqbalance.pid

* EDIT: high CPU usage TIME (which accumulates until the next reboot), not a constant high CPU usage percentual.

dbolivar, how do I run the "top" utility?

I will post the irqbalance tomorow when I have time to test.

I also discovered something else: When I changed the POWERLIMIT from 150 to 200 (I have 1080 Ti cards) the CPU usage went from 100% to 80%. It is very strange. When GPUs have lower power limit the CPU becomes bottlenecked

tomlev5

newbie

Activity: 35

Merit: 0

Quote from: ?? on ??

Quote from: tomlev5 on August 08, 2017, 04:13:16 PM

Quote from: tomlev5 on August 08, 2017, 01:29:06 AM

Quote from: car1999 on August 06, 2017, 01:32:36 AM

Quote from: gs777 on August 06, 2017, 12:20:06 AM

Hi!
I'm about to build a rig with Pentium G4400.
But after reading about Skylake issues with hyper threading don't know
should I use it or better to return and exchange it with i3?

i have a rig runs 8 cards with G3900, no problem.

I have a rig with G3900 and 10 cards, but it seems that the G3900 is bottlenecking the system. First core uses 100%, the other around 20%.

Is there a way to split the workload on both cores (If I could run EWBF miner in two terminals or is there some other way)?

Can somebody please help me, i'm a noob in linux.

nvOC is a great system. Thanks for all the work.

I tried opening two miners in two screens with some change in 1bash:

screen -dmS minerX1 $HCD --eexit 3 --fee $EWBF_PERCENT --cuda_devices 0 1 2 3 4 --pec --server $ZEC_POOL --user $ZECADDR --pass z --port $ZEC_PORT;
screen -dmS minerX2 $HCD --eexit 3 --fee $EWBF_PERCENT --cuda_devices 5 6 7 8 9 --pec --server $ZEC_POOL --user $ZECADDR --pass z --port $ZEC_PORT;

After the change there are two processes in System monitor, but CPU usage is still the same (100% one core, 20% second core).

Is it possible that System monitor doesn't show the correct CPU utilization?
Will it help if I change the CPU from G3900 to i3 or perhaps i5?

Fullzero, I see You have 13 GPUs on Asrock H110 PRO BTC (I am using the same motherboard). What kind of CPU do you have so that everything is working smoothly?

Using a kabylake i5;

I'm making another 13x rig soon with a g4560; I'll let you know if it works well as well.

Thanks for the info. I will buy an i5. It looks like the G3900 is not strong enough.
Regarding g4560: Is the Intel HyperThreading Bug fixed for ASrock H110 PRO BTC by default?

And thanks for all the work on nvOC and great support by you and all the other forum members.

Dhodge87

newbie

Activity: 57

Merit: 0

Quote from: Dhodge87 on August 07, 2017, 07:58:12 AM

Quote from: Bibi187 on August 07, 2017, 03:18:08 AM

Quote from: Dhodge87 on August 06, 2017, 10:22:33 PM

Ok I was able to root and pull the current specs of my cards.
This is an 4x Gigabyte gtx 10606gb rig.
I have my MC set to 1050 in 1bash and if I'm reading this right it says I'm at a current clock of 8748 with a max of 8754.
How do I get more than a 750 MC increase?

https://i.imgur.com/Fh5XRQ4.png

If u want to mine SIGT u have to lower your MemTransferRate and up your nvclock

http://imgur.com/a/yZuOE

Be in root and

nvidia-settings -a /GPUGraphicsClockOffset[3]=value
nvidia-settings -a /GPUMemoryTransferRateOffset[3]=value

U can specify by GPU, like the other command

nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[3]=value
nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[3]=value

I am mining Eth
Is this what I need to do to get my cards on performance level 3?

I currently have in 1bash
CC=0
MC=950
But it doesn't appear to go past a MC of 750, in the Nvidia xserver it shows level 2 as highlighted and level 0,1,3 as greyed out and level 3 shows the clock that I have set in 1bash.

Also something else I noticed this morning
I have the powerlimit set to 75w right now in1bash.
When I start up everything runs smoothly for about 15 minutes, then one of my cards changes from a PL of 75 up to 125 and my MH/s drops from 161 down to 142.

I tested the rig with the card disconnected and it still has a 15-20 MH/s drop after about 15 minutes.

https://i.imgur.com/wJzXKVI.png

https://i.imgur.com/ra5iFQO.png

https://i.imgur.com/jy0ahPp.png

https://i.imgur.com/xZEtjTS.png

So is my question/problem to complicated?
Or am I that much of a noob you all just laugh it off and ignore me all together?

JayneL

member

Activity: 104

Merit: 10

hmmmm i think it stay on that power limit, like now i try dual_eth_sc, i set power to 55, but in nvdia-smi i get 55w now seems oK Cheesy

are u lagging on dual_sia after a couple of hours then ang error of temperature cant read?

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

Quote from: JayneL on August 09, 2017, 10:35:13 AM

so much thanks to all of peeps here, all things work like a charm now Grin

very little problem now i'm using updated ethminer and trying to set powerlimit to 50 on my 1050ti but still when i check to nvidia-smi the card uses 64w

any idea why?

Sometimes they go over the limit for a certain times and then drop back too (occurred to me), its not that big deal if it is happening with one card at certain times?

JayneL

member

Activity: 104

Merit: 10

so much thanks to all of peeps here, all things work like a charm now Grin

very little problem now i'm using updated ethminer and trying to set powerlimit to 50 on my 1050ti but still when i check to nvidia-smi the card uses 64w

any idea why?

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

I agree with you, he might definitely add it in v19 hopefully

Quote from: WarwickNZ on August 09, 2017, 09:02:12 AM

Thanks appreciate the reply, think i'll wait for Fullzero to compile a trusted version direct from the Git if he doesn't mind. Windows version running faster than Palgin so far though.

Quote from: damNmad on August 09, 2017, 08:41:48 AM

Quote from: WarwickNZ on August 09, 2017, 08:19:16 AM

Hi, any chance you would be able to compile the new open source miner for Skunk? I am running into the same issue with the SSL error as ccminer2.2.

Cryptoblog announced it a couple of days ago. The Git for it is here: https://github.com/krnlx/ccminer-skunk-krnlx

Many thanks as always!

Hello,

Please see this

https://bitcointalksearch.org/topic/m.20713903

Hope it helps...

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

Quote from: ?? on ??

Quote from: damNmad on August 09, 2017, 04:02:16 AM

Quote from: ?? on ??

Hi guys, if posted prior my apologies as I tried to search this thread and the global threads.

My question is in regards to 'Maximus007_Auto_Temperature_control'

When I have it on it doesnt matter what I set the 'target_temp' for each card at it seems to like running the cards at 70 to 80 degrees and will up and down scale the fans to keep them there. Fans are at 30 - 35%.

I prefer a temp of 55 to 60.

Then I thought I would turn it off but even if I set manual fan to yes and the auto temp to 'no' my fan speed of 65% is not reflected so I think the script runs regardless of what you put in 1bash.

Anyone had this issue and either (a) found a way to make it respect the selected temperature or (b) disable it and allow for manual fans?

Many thanks!

change:

Code:

TARGET_TEMP_0=60

TARGET_TEMP_1=60

TARGET_TEMP_2=60

TARGET_TEMP_3=60

TARGET_TEMP_4=60

TARGET_TEMP_5=60

TARGET_TEMP_6=60

TARGET_TEMP_7=60

TARGET_TEMP_8=60

TARGET_TEMP_9=60

TARGET_TEMP_10=60

TARGET_TEMP_11=60

TARGET_TEMP_12=60

TARGET_TEMP_13=60

for b see:

https://bitcointalksearch.org/topic/mining-os-nvoc-1854250

Hi Fullzero,

With a fresh install of NvOC , changing target temps doesnt do anything on my rig. The fans do move up and down but they dont maintain target temp.

For example I set target temp as per your note to 60 and the cards run at 80. The fans go up and down on each card to maintain 80. The expected result is that they go faster to say 55% so the card runs at 60.

If I follow the steps in (b) this doesnt do anything different.

I am using v17 , was this an issue in 17? Or could it be my cards causing the issue
I am in Australia and we have celcius as our default temperature and you guys use farenheit could that be an issue somewhere?

In version v15 if I set manual fans to 70% they ran at 70% - for me in this version they seem to do their own thing Sad

I think living in Australia doesn't have anything to do with 'Maximus007_Auto_Temperature_control' script Cheesy

I would suggest try V18 and try the above suggested options, there were issues in v17 (I had similar one) so better try v18.

If the issue still persists in V18 share your 1bash with me, i will compare it to mine and see if there is any issue.

EDIT :

Lets give fullzero max time on development getting done for next releases by solving the minor issues ourselves

No worries ill download v18 and give that a shot. Is there a forum for minor issues such as this one as I agree with your suggestion.

So far V18 is working like charm by default, if there are any issues we are here to answer most of them

You are welcome

WarwickNZ

newbie

Activity: 21

Merit: 0

Thanks appreciate the reply, think i'll wait for Fullzero to compile a trusted version direct from the Git if he doesn't mind. Windows version running faster than Palgin so far though.

Quote from: damNmad on August 09, 2017, 08:41:48 AM

Quote from: WarwickNZ on August 09, 2017, 08:19:16 AM

Hi, any chance you would be able to compile the new open source miner for Skunk? I am running into the same issue with the SSL error as ccminer2.2.

Cryptoblog announced it a couple of days ago. The Git for it is here: https://github.com/krnlx/ccminer-skunk-krnlx

Many thanks as always!

Hello,

Please see this

https://bitcointalksearch.org/topic/m.20713903

Hope it helps...

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

Quote from: WarwickNZ on August 09, 2017, 08:19:16 AM

Hi, any chance you would be able to compile the new open source miner for Skunk? I am running into the same issue with the SSL error as ccminer2.2.

Cryptoblog announced it a couple of days ago. The Git for it is here: https://github.com/krnlx/ccminer-skunk-krnlx

Many thanks as always!

Hello,

Please see this

https://bitcointalksearch.org/topic/m.20713903

Hope it helps...

WarwickNZ

newbie

Activity: 21

Merit: 0

Hi, ~~any chance you would be able to compile the new open source miner for Skunk? I am running into the same issue with the SSL error as ccminer2.2.~~

Cryptoblog announced it a couple of days ago. The Git for it is here: https://github.com/krnlx/ccminer-skunk-krnlx

Sorted it, replaced the openssl "bn.h" file with a new version, build working correctly after that

Many thanks as always!

lards

newbie

Activity: 50

Merit: 0

Quote from: ?? on ??

Quote from: lards on August 03, 2017, 02:06:07 PM

Hey Guys,

Have a problem with loading the OS as it tells me "xorg PROBLEM DETECTED" and then reboots and shows:
error: unknown filesystem
grab rescue>

What can it be and how can I solve this? Used flashing tools as described and tried it at least twice. I am using ASrock h110 and at the moment just one Manli P106-100 card just so I can test if I can install the OS before installing all 13 cards.

I need one or two of the:

P106-100

to test and ensure nvOC will properly support these GPUs. A number of members have had problems using these GPUs. If someone is willing to sell me 1 or preferably 2 Please pm me.

I have solved this issue by editing the line "XORG FAIL" to XORG "OK" which worked and the system started, now I have the different problem :

When I run more then 6-7 cards on the board no matter in what miner I either get error 15 " cannot get current temperature " or the system just freezes after in about half an hour or a bit longer and the only thing that helps is to turn off/on the power socket... I have updated the drivers and now trying to wait for it to freeze on 6 cards since it works the longest out of all the set ups I tried. As soon as I try 10 or more GPUs I either get error 15 or just frozen system. I don't think it's one of the cards since I mixed them a couple of times and what I noticed is that it crashes faster as I add more GPUs.

Do you have any idea where the problem can be? I have also 2 PSUs connected together one 600W Zalmann powering motherboard and 2400W HP server PSU which was remade for GPU mining and powers risers and GPUs, both of those seem to be working fine , so I have no idea where to look for solution.

If anyone had this problem please let me know , would be greatly appreciated... Even willing to donate to somebody who's advice will help.

PS. The cards are in stock mode, so it's not OC.

UPD Been pretty stable on 6 cards , have been running for 8 hours now , probably will try and add a couple after a 16-20 hour mark...

ivoldemar

newbie

Activity: 23

Merit: 0

Quote from: ?? on ??

Quote from: car1999 on August 08, 2017, 06:54:03 AM

Quote from: damNmad on August 08, 2017, 12:57:05 AM

Quote from: Malbo on August 07, 2017, 05:37:12 PM

Quote from: Bibi187 on August 07, 2017, 03:35:33 PM

Quote from: Malbo on August 07, 2017, 03:31:13 PM

Hey, ty for adding teamviewer to nvOC!

But i got a problem: teamviewer never start on boot, i always need to enter this on guake terminal :

sudo teamviewer --daemon enable

My rigs are not at home, and if i need to reboot this, i can't control after the reboot :-(, please help me.

On your 1bash be sure to set

TEAMVIEWER="YES"

Oh thanks, there is a way to edit the 1bash in ubuntu ? if yes it need a restart ? thanks!

Yes, you can. It is in the home directory. Please search in home folder (where you see all miners)

EDIT:

For restart, to apply the 1bash changes you don't need to restart whole rig, you can kill the mining process using 'CTRL + c' and it should restart the process with new changes, if it doesn't just close the terminal after 'CTRL+c' and close the terminal and restart the terminal (not the rig)

press CTRL+c, it restarts 1bash, do you know how to disable this feature?
I'd like to exit the terminal when I press CTRL+c, thanks.

The way everything is setup; is to expect this to occur. You can change this but; it will break a lot of other things.

When gnome terminal is open go to the top left of the screen and click terminal, then preferences, then profiles. select mining and click edit. Click the command tab. Change when command exits: to Exit the terminal.

Friend, look, please. It's in your interests. I need to collect 30 farms for 12 Mining Edition cards and I want to do this on NVOC and I need to collect it before the end of the week, but without overclocking there is no sense at all.
I sent you access to private messages.

Very much I ask you, to solve a situation.

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

Quote from: ?? on ??

Hi guys, if posted prior my apologies as I tried to search this thread and the global threads.

My question is in regards to 'Maximus007_Auto_Temperature_control'

When I have it on it doesnt matter what I set the 'target_temp' for each card at it seems to like running the cards at 70 to 80 degrees and will up and down scale the fans to keep them there. Fans are at 30 - 35%.

I prefer a temp of 55 to 60.

Then I thought I would turn it off but even if I set manual fan to yes and the auto temp to 'no' my fan speed of 65% is not reflected so I think the script runs regardless of what you put in 1bash.

Anyone had this issue and either (a) found a way to make it respect the selected temperature or (b) disable it and allow for manual fans?

Many thanks!

change:

Code:

TARGET_TEMP_0=60

TARGET_TEMP_1=60

TARGET_TEMP_2=60

TARGET_TEMP_3=60

TARGET_TEMP_4=60

TARGET_TEMP_5=60

TARGET_TEMP_6=60

TARGET_TEMP_7=60

TARGET_TEMP_8=60

TARGET_TEMP_9=60

TARGET_TEMP_10=60

TARGET_TEMP_11=60

TARGET_TEMP_12=60

TARGET_TEMP_13=60

for b see:

https://bitcointalksearch.org/topic/mining-os-nvoc-1854250

Hi Fullzero,

With a fresh install of NvOC , changing target temps doesnt do anything on my rig. The fans do move up and down but they dont maintain target temp.

For example I set target temp as per your note to 60 and the cards run at 80. The fans go up and down on each card to maintain 80. The expected result is that they go faster to say 55% so the card runs at 60.

If I follow the steps in (b) this doesnt do anything different.

I am using v17 , was this an issue in 17? Or could it be my cards causing the issue
I am in Australia and we have celcius as our default temperature and you guys use farenheit could that be an issue somewhere?

In version v15 if I set manual fans to 70% they ran at 70% - for me in this version they seem to do their own thing Sad

I think living in Australia doesn't have anything to do with 'Maximus007_Auto_Temperature_control' script Cheesy

I would suggest try V18 and try the above suggested options, there were issues in v17 (I had similar one) so better try v18.

If the issue still persists in V18 share your 1bash with me, i will compare it to mine and see if there is any issue.

EDIT :

Lets give fullzero max time on development getting done for next releases by solving the minor issues ourselves

dbolivar

member

Activity: 119

Merit: 10

@fullzero

Have you considered moving the configuration, or at least the key configuration parameters like pools and coin to mine, to a separate file? I sometimes change pools and coins, for instance, and currently I have several "1bash_xxx" files for each configuration, controlling the active one with a symlink to "1bash". One idea would be a config file like this (for instance in INI format, but just to illustrate):

::: 1bash.conf :::
[defaults]
# Every configuration option

# Below just what's different from default. Users define their config keys,
# specifying the active one in 1bash
[zec-nanopool]
COIN="ZEC"
ZEC_POOL="zec-us-east1.nanopool.org"

[eth-dwarfpool]
COIN="ETH"
ETH_POOL="eth-us.dwarfpool.com"

::: 1bash :::
# 1) Read default options
# 2) Read user options
USER_CONF="zec-nanopool"
...

Just an idea. I may be able to help you with that, if you want and find it a good idea. I know Bash doesn't have a built-in parser for INI (or whatever) config files, but there's some code around to do that.

philipma1957

legendary

Activity: 4354

Merit: 9201

'The right to privacy matters'

Quote from: ?? on ??

Quote from: fk1 on July 28, 2017, 06:15:39 PM

Hi,

I got a gainward 1060 today and it is the first card that ignores the power-limit out of 8 cards (gigabyte, asus) wether I set it by bash or nvidia-smi. ie. sucks 100w/80w. card damaged?

still using v0017

btw: any planned date for v0019? I much appretiate this OS!

best regards

I am not familiar with gainward. The GPU may not be properly recognized by X; in turn causing OC and PL to not work on it. I usually test GPUs that have a problem in a rig; by moving them to a mobo 16x slot direct (only GPU on the mobo) and testing if the same problems manifest.

There are a lot of changes for v0019; I want to test them before releasing.

skunk on zpool please thanks phil

BigSmurf

newbie

Activity: 15

Merit: 0

hi,
i have Asrock H110 btc+ pro, and 13xMining/P106-100 (1060 6gb) GPU-z everything works fine and stable with other OS-es, but with your OS it keeps restarting and restarting because of not being able to see/find xorg file.

We managed to start the OS via GTX 1060 card and then added the Mining P106-100 (1060 6gb) cards, but no go with only the Mining P106-100 (1060 6gb) cards. can you look in to this ? i would like to use your OS but dont want to have a normal gaming card, don't need it when using all Mining cards.

Can you also make a explination on overckloking as we tried via the file but failed. we only managed to individually overclock via the Nvidia x server.

thank you.
BigSmurf

Topic: [ mining os ] nvoc - page 273. (Read 418549 times)