Guys,
description on V0013 says:
" dummy plug is no longer required "
Yet when I connect to my rig via team viewer I get a very tiny window (if no screen is connected to the GPU). Is there a workaround to this problem?
Topic: [ mining os ] nvoc - page 293. (Read 418549 times)
Just tried nvOC v0017 on an ASROCK X370 Gaming K4 motherboard and it does not recognize the hardware.
I don't have a x370 mobo and haven't added support for the chipset.
You can do this by:
Click Ubuntu button on top left and type:
u
Click on software updater
Install updates
If you can't get ubuntu to boot:
If the bios posts; you can access the grub loader menu by pressing
esc
continuously while booting (note holding it down doesn't usually work), then select boot in recovery mode.
in recovery mode:
Enable networking
then install updates from the cmd prompt:
Code:
sudo apt-get update && sudo apt-get dist-upgrade --yes
and reboot
this should ensure your build has all known system files for your system.
After booting in recovery mode (not even sure it is booting completely) get (initramfs) which I am not sure is the command prompt. Type help and and nothing there to enable networking. Try the sudo apt-get command line and says sudo: not found. Have not messed with since 1989 and do not remember any of it so will need a bit more help. Appreciate it
What USB key are you using?
I flashed 0017 again today and unmounting was possible again so you definetly might reconsider using the previous filesystem.
I've flashed image on USB stick but my rig wont boot to it, is says bootable drive not found. Same rig with same USB drive flashed with SMOS worked, any ideas why this wont?
Fullzero, IAmNotAJeep or Maxximus007,
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
I have noticed a problem when using both PROFIT_SWITCHING and or WATCHDOG together; I will make changes to the next 1bash to fix it.
It is also possible that the timeouts between checks in the WATCHDOG should be relaxed when mining Ethash COINs. Or relaxed in general.
If the timing is right; PROFIT_SWITCHING will switch close to the WATCHDOG check and a low utilization will be detected.
I will make a flag for both IN-SWITCHING and DAG-BUILDING to prevent this in the next 1bash.
What COIN selection are you using or are you using SALFTER_NICEHASH_PROFIT_SWITCHING?
I am not currently using SALFTER_NICEHASH_PROFIT_SWITCHING since Ethash is so close with the profit switching right now.
Not sure what it is but I am rolling back to VER17 on this rig, as it just restarted again and then hard locked up after initial start-up showing a black screen then the flash drive was corrupted and refused to boot.
Just found out it may have been the flash drive the last 48 hours as it just died. LOL write errors all over it. I am testing now with a new flash drive.
Hi i added DeepOnion Mining in v17 without a Problem, but i cant get it working in v18
This is from v17:
ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="localhost:3633"
if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"
until $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION
do
echo "FAILURE; reinit in 5" >&2
sleep 5
done
fi
and this here v18 are not working
ONION_WORKER="nv$IP_AS_WORKER"
ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="stratum+tcp://kawaiipool.party:3633"
if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"
screen -dmS miner $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION
if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi
also how could i Solo mining this coin by changing here the Parameters?
Just set localhost as Pool, but wehere to add the conf. for ccminer?
ccminer config for Onion?!
testnet=0
listen=1
maxconnections=30
server=1
rpcuser=username
rpcpassword=pass
rpcport=18580
rpcconnect=127.0.0.1
cheers
This is from v17:
ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="localhost:3633"
if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"
until $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION
do
echo "FAILURE; reinit in 5" >&2
sleep 5
done
fi
and this here v18 are not working
ONION_WORKER="nv$IP_AS_WORKER"
ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="stratum+tcp://kawaiipool.party:3633"
if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"
screen -dmS miner $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION
if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi
also how could i Solo mining this coin by changing here the Parameters?
Just set localhost as Pool, but wehere to add the conf. for ccminer?
ccminer config for Onion?!
testnet=0
listen=1
maxconnections=30
server=1
rpcuser=username
rpcpassword=pass
rpcport=18580
rpcconnect=127.0.0.1
cheers
try:
Code:
ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="stratum+tcp://kawaiipool.party:3633"
ONION_POOL="stratum+tcp://kawaiipool.party:3633"
Code:
if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"
screen -dmS miner $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION
if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi
BITCOIN="theGROUND"
while [ $BITCOIN == "theGROUND" ]
do
sleep 60
done
fi
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"
screen -dmS miner $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION
if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi
BITCOIN="theGROUND"
while [ $BITCOIN == "theGROUND" ]
do
sleep 60
done
fi
and let me know if it works
conf should be in the
'/home/m1/TPccminer'
directory
Working. How to set up solo mining for this coin over bath?
Thank you cheers
just a quick one
does not work with 9 GPUs even though it has 2x m2 slots
unless someone knows some magical trick?
Quote
ASUS PRIME Z270-A (7x gpu: 9x if you use 2x m2 adapters) Link
does not work with 9 GPUs even though it has 2x m2 slots
unless someone knows some magical trick?
Did you change the bios settings as directed by the OP?
If you are using an ASUS PRIME Z270-A;
ensure 'Above 4G Decoding' is enabled in the bios.
Also ensure PTP aware OS: is set to 'Not PTP Aware' in the bios.
Finally, ensure you 'Clear Secure Boot Keys' in the bios.
I am running 5 of these boards and do not have any issues. This board appears to have the most PCI lane management features I have ever seen on a motherboard. Be sure your M.2 slots are configured for PCI and not SATA. Also, if you are using a SSD/HDD for nvOC, be sure you are not using a SATA slot that might be conflicting with the M.2 slot. There is a chart for this in the mobo manual. My 2 cents.
Fullzero, IAmNotAJeep or Maxximus007,
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
I have noticed a problem when using both PROFIT_SWITCHING and or WATCHDOG together; I will make changes to the next 1bash to fix it.
It is also possible that the timeouts between checks in the WATCHDOG should be relaxed when mining Ethash COINs. Or relaxed in general.
If the timing is right; PROFIT_SWITCHING will switch close to the WATCHDOG check and a low utilization will be detected.
I will make a flag for both IN-SWITCHING and DAG-BUILDING to prevent this in the next 1bash.
What COIN selection are you using or are you using SALFTER_NICEHASH_PROFIT_SWITCHING?
I am not currently using SALFTER_NICEHASH_PROFIT_SWITCHING since Ethash is so close with the profit switching right now.
saflter your newest version of switch was causing problems when run with a monitor connected (LOCAL); I would recommend relying on the:
IAmNotAJeep_and_Maxximus007_WATCHDOG
to handle miner crashes / 0 hashrates.
I spent a couple hours testing this, and it is very effective; it is worth noting that it currently only works when the mining process is launched in a screen ( I will make it work for all the clients even when run locally soon: so don't spend a lot of time upgrading rigs with this)
IAmNotAJeep_and_Maxximus007_WATCHDOG
to handle miner crashes / 0 hashrates.
I spent a couple hours testing this, and it is very effective; it is worth noting that it currently only works when the mining process is launched in a screen ( I will make it work for all the clients even when run locally soon: so don't spend a lot of time upgrading rigs with this)
I've been laying low the past few days, doing stability checks. Unloading/reloading the driver while switching hasn't completely eliminated crashes, so I'm thinking that a watchdog process would work better.
My latest commit comments out the GPU-resetting code, and also logs whenever it switches coins to algo-log. I definitely need to look into the existing watchdog code, as it seems that avoiding crashes is nearly impossible. I'm not even overclocking my cards, except for one algo (daggerhashimoto) where the GPU is underclocked and the memory is overclocked. It seems that if a GPU is going to hang, it nearly always does so right after an algo switch. If it doesn't hang then, it'll most likely run indefinitely.
I tried with hddrawcopy and things are speedy again. I am using a 32gb usb 3.0 stick. you need the exact vendor/model/FW?
edit: terminated terminal process and restarted 1bash manually. this thing stops after setting up GPU Clocks. like freeze.
e: MEGA download limit and hassle aint cool
edit: terminated terminal process and restarted 1bash manually. this thing stops after setting up GPU Clocks. like freeze.
e: MEGA download limit and hassle aint cool
Quote
Do you mean you used HDDRawCopy and it didn't have this problem? If so then there may be an issue with etcher.
I never used HDDRawCopy. seems like etcher is the problem although I am doin nothing else since flashing 0017 wich flashed flawlessly
I changed the format of the windows partition for v0018 which possibly is causing problems with etcher. I will try to replicate this problem with etcher; for now with windows I would try HDDRawCopy and see if it works as intended.
I also am not sure if there is a problem with the resulting image; regardless of if etcher cannot properly eject the image afterwards.
I tested it again with flashing with etcher but without the ejecting tic. No luck with unmounting so shutdown windows. I've found the 1bash file but it takes like forever to navigate or nano into it. Cant mine musicoin right now but that is new to me so I will try to mine eth to see if this works as usual. never had musicoin config running so this might be my fault. but as said partition seems to be incredibly slow since 0018 you should check and maybe fix that.
HHDRawCopy seems to be linux only so I can't use that atm, the only linux I have is on the rig
e: executing bash also sloooow. please provide 0017 temporary
e2: oh i mistaken hddrawcopy is for win will try gimme a min...
Quote
Do you mean you used HDDRawCopy and it didn't have this problem? If so then there may be an issue with etcher.
I never used HDDRawCopy. seems like etcher is the problem although I am doin nothing else since flashing 0017 wich flashed flawlessly
Hi i added DeepOnion Mining in v17 without a Problem, but i cant get it working in v18
This is from v17:
ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="localhost:3633"
if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"
until $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION
do
echo "FAILURE; reinit in 5" >&2
sleep 5
done
fi
and this here v18 are not working
ONION_WORKER="nv$IP_AS_WORKER"
ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="stratum+tcp://kawaiipool.party:3633"
if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"
screen -dmS miner $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION
if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi
also how could i Solo mining this coin by changing here the Parameters?
Just set localhost as Pool, but wehere to add the conf. for ccminer?
ccminer config for Onion?!
testnet=0
listen=1
maxconnections=30
server=1
rpcuser=username
rpcpassword=pass
rpcport=18580
rpcconnect=127.0.0.1
cheers
This is from v17:
ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="localhost:3633"
if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"
until $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION
do
echo "FAILURE; reinit in 5" >&2
sleep 5
done
fi
and this here v18 are not working
ONION_WORKER="nv$IP_AS_WORKER"
ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="stratum+tcp://kawaiipool.party:3633"
if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"
screen -dmS miner $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION
if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi
also how could i Solo mining this coin by changing here the Parameters?
Just set localhost as Pool, but wehere to add the conf. for ccminer?
ccminer config for Onion?!
testnet=0
listen=1
maxconnections=30
server=1
rpcuser=username
rpcpassword=pass
rpcport=18580
rpcconnect=127.0.0.1
cheers
I tried v0018 today but with no success: whenever I finished flashing my usb stick with etcher I can't unmount the device from windows anymore. When I plug it out without unmounting, it boots up but after a while my ssh session disconnects and it seems to hang.
v0017 worked fine, where can I redownload it?
v0017 worked fine, where can I redownload it?
Were you imaging an SSD or HDD with etcher when it didn't let you eject? If so that is expected.
Anytime you cannot properly eject an imaged drive; shutdown the build pc and remove it after shutdown is complete.
SALFTER_NICEHASH_PROFIT_SWITCHING
and
IAmNotAJeep_and_Maxximus007_WATCHDOG
will intermittently kill your screen in their normal operation.
If you set both to "NO" and:
Code:
LOCALorREMOTE="REMOTE"
you should be able to have an uninterrupted SSH screen connection similar to v0017
When using PROFIT_SWITCHING and or WATCHDOG if your screen was killed you can connect to the regenerated one with the cmd:
Code:
screen -r miner
Also I have noticed a problem when using both PROFIT_SWITCHING and or WATCHDOG together; I will make changes to the next 1bash to fix it.
serious issues over here since 0018. I did reflash my stick, edited the 1bash and shut down computer. I SSHed into my rig like forever and when I take a look at nvidia-smi no cards are working (0%). nanoing the bash file over ssh doesn't work, nothing happens...
took a look: /media/m1 empty. I did not understand what you meant with
Quote
Were you imaging an SSD or HDD with etcher when it didn't let you eject? If so that is expected.
I just downloaded the zip file you provided to my win system on ssd (checked the zip file successfully btw) unzipped the image and load it in etcher, choose my usb stick and flash+verify it. same procedure as 0017 but without the unmounting problem.
e: google says its etcher problem lets see... i also get info i have to format stick after flashing from win so i try to untick auto eject in etcher
All,
Was working great in 16 but having issues dual mining ETC and SC with Claymore in 18. Got ETC working and working WELL (yay higher hashrate for my 1060) but whenever I try to connect to siamining.com I'm getting an error:
SC: Stratum - connecting to 'us-east.siamining.com' <45.79.159.167> port 7777
SC: Stratum - Connected (us-east.siamining.com:7777)
SC: Authorization failed
: {"id":2,"error":null,"result":false}
Stratum - reading socket failed, disconnect
SC: Job timeout, disconnect, retry in 20 sec...
GPU0 t=65C fan=60%
Here's my 1bash config:
I'm using port 7777 to reach siamining.com on a dual mining claymore config on Windows 10 with no problem. It's not clear to me what I should be setting the SC_GW_POOL value to. Any insight there?
Thanks!
Was working great in 16 but having issues dual mining ETC and SC with Claymore in 18. Got ETC working and working WELL (yay higher hashrate for my 1060) but whenever I try to connect to siamining.com I'm getting an error:
Code:
SC: Stratum - connecting to 'us-east.siamining.com' <45.79.159.167> port 7777
SC: Stratum - Connected (us-east.siamining.com:7777)
SC: Authorization failed
: {"id":2,"error":null,"result":false}
Stratum - reading socket failed, disconnect
SC: Job timeout, disconnect, retry in 20 sec...
GPU0 t=65C fan=60%
Here's my 1bash config:
Code:
SC_WORKER="nv$IP_AS_WORKER"
SC_ADDRESS="c4fa3fa4acf1a317752204d730888c755367d8e81092a944f6727d06251f1fd1a752576afac6"
SC_POOL="us-east.siamining.com:7777"
SC_GW_POOL="us-east.siamining.com:9980"
SC_ADDRESS="c4fa3fa4acf1a317752204d730888c755367d8e81092a944f6727d06251f1fd1a752576afac6"
SC_POOL="us-east.siamining.com:7777"
SC_GW_POOL="us-east.siamining.com:9980"
I'm using port 7777 to reach siamining.com on a dual mining claymore config on Windows 10 with no problem. It's not clear to me what I should be setting the SC_GW_POOL value to. Any insight there?
Thanks!
this pool uses the syntax:
-dpool stratum+tcp://us-east.siamining.com:7777 -dwal YourSiacoinAddress.YourWorkerName -dcoin sc
on or near line 2764:
Code:
SCADDR="$SC_ADDRESS/$SC_WORKER"
need to be changed to
Code:
SCADDR="$SC_ADDRESS.$SC_WORKER"
for this pool.
for the next 1bash; I will make a YES/NO switch to make this easier to change in the future.
Let me know if this solves the problem.
That did the job. A switch would be awesome but even just a comment somewhere relevant in the config would be a good pointer.
Fullzero, IAmNotAJeep or Maxximus007,
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
60 x 12 = 720 mns
the description is wrong in the 1bash file
I did catch that and changed it to 3600 minutes or 2.5 days
Thank you though!
Fullzero, IAmNotAJeep or Maxximus007,
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
60 x 12 = 720 mns
the description is wrong in the 1bash file
Fullzero, IAmNotAJeep or Maxximus007,
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
I tried v0018 today but with no success: whenever I finished flashing my usb stick with etcher I can't unmount the device from windows anymore. When I plug it out without unmounting, it boots up but after a while my ssh session disconnects and it seems to hang.
v0017 worked fine, where can I redownload it?
v0017 worked fine, where can I redownload it?
How exactly do I utilize
The new watchdog function?
Auto reboot?
And can I remote in?
The new watchdog function?
Auto reboot?
And can I remote in?
Jump to: