hello.i am a new user.
i just installed the 1.9.4 and want to config the 0miner ,but it is not listed on the /home/m1.where can i find this file?
You need to install 19-2.0 Community Release |
|
|
|
Hi, guys
I' using NVOC successfully for months but currently there is only one card left in the rig. I have removed the other cards and the miner didn't start. This card is with extender. Have tried to switch the PCIe slot but nothing.
The card is GTX1080 and is visible with nvidia-smi but the miner is silent.
Can you help me please?
Did you connect your GPU to the x16 (long PCIe slot) closest to the CPU? Also make sure the integrated GPU is disabled in the bios. |
|
|
|
Hello!
My motherboard does not see ssd with nvoc installed, while with the usb flash I can become on ssd ubuntu,
is there any bash script that would update ubuntu to nvoc fork?
Thank you!
You have to untar (unzip) the image you downloaded. Depends on the program you use, you might need to unzip it twice (From *.tar.gz to *.tar, then run it again to unzip the *.tar to get *.img). Some programs can directly unzip the tar.gz in one step, some need two steps. Once you unzipped the downloaded file and got the *.img you can use hddrawcopy to burn the img to your SSD. Once the image is burned to your SSD, plug it to your PC, remove any other HDD, SSD or USB from your PC, enter BIOS, disable UEFI, enable legacy/CSM and save and restart. It should boot into nvoc. There is no script to update/turn Ubuntu into nvoc. There's more than just few scripts... nvidia drivers, cuda, miners, removed default packages, installed extra packages, custom OS tweaks... lots of manual tweaks, not easy to do with script. |
|
|
|
[2018-03-27 04:21:10] Starting on stratum+tcp://europe.lyra2z-hub.miningpoolhub.com:20581
[2018-03-27 04:21:10] NVML GPU monitoring enabled.
[2018-03-27 04:21:10] 8 miner threads started, using 'lyra2z' algorithm.
[2018-03-27 04:21:13] Stratum difficulty set to 5 (0.01953)
[2018-03-27 04:21:20] GPU #0: Intensity set to 17, 131072 cuda threads
[2018-03-27 04:21:20] GPU #2: Intensity set to 17, 131072 cuda threads
[2018-03-27 04:21:20] GPU #1: Intensity set to 17, 131072 cuda threads
[2018-03-27 04:21:20] GPU #5: Intensity set to 17, 131072 cuda threads
[2018-03-27 04:21:20] GPU #3: Intensity set to 17, 131072 cuda threads
[2018-03-27 04:21:20] GPU #4: Intensity set to 17, 131072 cuda threads
[2018-03-27 04:21:20] GPU #7: Intensity set to 17, 131072 cuda threads
[2018-03-27 04:21:20] GPU #1: MSI GTX 1080 Ti, 79.74 kH/s
[2018-03-27 04:21:20] GPU #0: MSI GTX 1080 Ti, 79.74 kH/s
[2018-03-27 04:21:20] GPU #6: Intensity set to 17, 131072 cuda threads
[2018-03-27 04:21:20] GPU #2: MSI GTX 1080, 78.89 kH/s
[2018-03-27 04:21:20] GPU #3: MSI GTX 1080, 76.36 kH/s
[2018-03-27 04:21:20] GPU #5: MSI GTX 1080, 76.31 kH/s
[2018-03-27 04:21:21] GPU #4: MSI GTX 1080, 71.80 kH/s
[2018-03-27 04:21:21] GPU #7: MSI GTX 1080, 71.76 kH/s
[2018-03-27 04:21:21] GPU #6: MSI GTX 1080 Ti, 69.34 kH/s
[2018-03-27 04:21:25] GPU #3: MSI GTX 1080, 2183.67 kH/s
[2018-03-27 04:21:37] GPU #4: MSI GTX 1080, 2198.53 kH/s
[2018-03-27 04:21:37] accepted: 1/1 (diff 0.033), 10.70 MH/s yes!
[2018-03-27 04:21:38] GPU #2: MSI GTX 1080, 2176.62 kH/s
[2018-03-27 04:21:45] GPU #4: MSI GTX 1080, 2195.73 kH/s
[2018-03-27 04:21:45] accepted: 2/2 (diff 0.033), 11.23 MH/s yes!
[2018-03-27 04:21:46] GPU #7: MSI GTX 1080, 2174.82 kH/s
[2018-03-27 04:21:46] accepted: 3/3 (diff 0.033), 11.59 MH/s yes!
[2018-03-27 04:21:56] GPU #0: MSI GTX 1080 Ti, 2923.20 kH/s
[2018-03-27 04:21:56] GPU #0: 2019 MHz 17.20 kH/W 113W 51C FAN 30%
[2018-03-27 04:21:57] accepted: 4/4 (diff 0.033), 12.30 MH/s yes!
[2018-03-27 04:21:58] GPU #6: MSI GTX 1080 Ti, 4806.30 kH/s
[2018-03-27 04:21:58] GPU #6: unspecified launch failure
[2018-03-27 04:21:58] GPU #1: MSI GTX 1080 Ti, 4754.69 kH/s
[2018-03-27 04:21:58] GPU #1: unspecified launch failure
[2018-03-27 04:21:58] GPU #2: MSI GTX 1080, 6329.96 kH/s
[2018-03-27 04:21:58] GPU #2: unspecified launch failure
[2018-03-27 04:21:58] GPU #6: unspecified launch failure
[2018-03-27 04:21:58] GPU #4: MSI GTX 1080, 10.13 MH/s
[2018-03-27 04:21:58] GPU #4: unspecified launch failure
[2018-03-27 04:21:58] GPU #1: unspecified launch failure
[2018-03-27 04:21:58] GPU #5: MSI GTX 1080, 3618.08 kH/s
[2018-03-27 04:21:58] GPU #5: unspecified launch failure
[2018-03-27 04:21:58] GPU #7: MSI GTX 1080, 11.08 MH/s
[2018-03-27 04:21:58] GPU #7: unspecified launch failure
[2018-03-27 04:21:58] GPU #3: MSI GTX 1080, 3992.41 kH/s
[2018-03-27 04:21:58] GPU #3: unspecified launch failure
[2018-03-27 04:21:58] GPU #0: unspecified launch failure
[2018-03-27 04:21:58] GPU #2: unspecified launch failure
[2018-03-27 04:21:58] GPU #6: unspecified launch failure
when i start mining ZCOIN its starts but after gets just \\unspecified launch failure\\, what do i need to do? Try lowering OC settings, see if that helps. |
|
|
|
Hey Lee: I downloaded it for some quick and dirty testing. This miner requires cuda 9 and the Community Release is at 8: m1@Testy:~/Downloads/nevermore-linux$ ./ccminer
./ccminer: error while loading shared libraries: libcudart.so.9.0: cannot open shared object file: No such file or directory
Since I have been out of the loop for a while, I don't know where we are with upgrading cuda versions. Have you tried the top link on that page (not the source tarballs)? It might be precompiled with statically compiled cuda libraries. As for the next release I think we should go with Cuda 9. Most of the miners support Cuda 9 I believe. And those that don't, seems their devs are living in stone age and probably are not actively developed anymore and don't deserve to be included  Correct me if I'm wrong but there seems to be enough miners for all algos that will play nicely with cuda 9. Any particular (highly used) miner still stuck in stone age? |
|
|
|
XMR/Monero mining using XMR-STAKThe new version of XMR-STAK that supports Monero7 is out: https://github.com/fireice-uk/xmr-stak/releasesThe PoWs They Are a-Changin'So here is what I did to get it going on the Community Release. The first step is to DL the source and compile it: # Build XMR, from https://github.com/fireice-uk/xmr-stak/blob/master/doc/compile_Linux.md
cd /home/m1/xmr
git clone https://github.com/fireice-uk/xmr-stak.git
#mkdir xmr-stak/build
cd xmr-stak
cmake .
make install
The next thing you want to do is just execute the binary: It will do a one-time prompt for coin, pools, addr.worker, pass and create the necessary configuration files. These new configuration files are NOT compatible with previous versions so this must be done. The next step is to setup nvOC for the memory changes: # Configure Memory for hugepages
sudo vi /etc/sysctl.conf
# Add line
vm.nr_hugepages=128
# Set user limits
sudo vi /etc/security/limits.conf
# Add lines
* soft memlock 262144
* hard memlock 262144
# Reboot
sudo shutdown -r now
Note: I did all of the steps above while my rig was mining. The final thing is to modify 0miner to strip out all of the old configuration file generation stuff and get down to just the basics. One could go to the trouble of modifying all of the existing code for this in 0miner to make it compatible with the new version of XMR-STAK but I do not have the time to do it so I just went with a stripped down 0miner to just launch the miner and let the user launch it as above to do the one-time config file generation. That 0miner code is: if [ $COIN == "XMR" ]
then
HCD='/home/m1/xmr/xmr-stak/bin/xmr-stak'
cd /home/m1/xmr/xmr-stak/bin
screen -dmSL miner $HCD
fi
Hope this helps. Great work (as always) Stubo. Thanks for providing detailed guide. When you have time, could you check/review this new miner at: https://github.com/brian112358/nevermore-miner/releasesApparently is 20% faster and more stable than msft |
|
|
|
Hello guys.
I was using nvOC_v0019 for a couple of months and then I switched to nvOC v0019-2.0.
I like all the new features of nvOC v0019-2.0 but I have problems with stability.
The nvOC_v0019 lasted around 10 days without freezes but nvOC v0019-2.0 lasts only a day or two and then freezes. I went back to nvOC_v0019 and stability improved.
I use SSH to access the miner.
I have two questions:
1) Can you help me with a command that will copy 1bash from 8MB windows partition to the right place, that it will be used on startup (nvOC_v0019 has a problem that it doesn't copy 1bash on first start with HDD)
2) I suspect that the problem with nvOC v0019-2.0 is in newer drivers. Fullzero also wrote that vBASIC uses an older Nvidia Driver. Can anybody give me some instructions that will uninstall nvidia drivers in nvOC v0019-2.0 and then install older drivers?
I would use the vBASIC, but it really lacks a lot of features ...
Fullzero, can you please tell me which driver version do you use in vBASIC and which version in nvOC_v0019?
Whitch command can I use to get Nvidia driver version?
Sorry to hear that you have problems with 19-2.0. It is generally more stable but it is possible that it might perform worse on certain configurations. If you could provide more details we might be able to troubleshoot and help. 1) I don't remember the structure of v0019. I don't even remember if the small FAT partition was mounted correctly. It's quite an old version and won't be easy to guide you without installing v0019 on a rig just to see the structure. Basicly, you would need to copy 1bash from FAT partition to your /home folder then run it through dos2unix to convert it. 2) Although it is quite easy to upgrade to the latest version of the driver, it is not easy to downgrade since PPA repo keeps the latest driver only. If you can find the .deb package of an older driver you can install it manually with dpkg You can get the driver version with this: nvidia-smi -i 0 -q|grep "Driver Version"|cut -f 2 -d ":"|cut -f 2 -d " " |
|
|
|
Hi guys,
still being fairly new to Linux i encountered the following problem:
Recently i built a rig with a Ryzen 7 1700x and AMD GPU´s and then installed nvOC 19-2.0 Community.
Did not work at all, always got stuck in a login loop and the miner1 password didn´t work, the rig stayed in the login loop.
So obviously i started searching the web and found several threads with exactly the same problem, not for nvOC but Ubuntu 16.04. And there were some solutions which helped others like reassign the read write permissions, renewing .Xauthority and other solutions but none of these worked on my rig, it stayed in the login loop no matter what i did. I used a freshly imaged nvOC 19-2.0 with no changes whatsoever.
I could ctrl+alt+f1 into a tty and login but i could not get nvOC to start and run a miner.
So i figured i just try a different combination and changed the motherboard and now it gets weired. After changing the mobo the same thing happened i was stuck in the login loop so i started to change everything. I tried several motherboard´s, switched memory sticks, used Nvidia GPU´s as well as AMD GPU´s, put nvOC on an USB stick as well as on a harddisk but nothing worked for me in combination with a Ryzen processor. I also tried a Ryzen 3 and a Ryzen 5. Using a windows setup all these combinations worked just fine but not with nvOC.
The second i put a Ryzen processor into any one rig and install nvOC i always get stuck in a login loop.
So is there anybody out there successfully mining with a Ryzen processor and nvOC?
Was anybody stuck in the login loop on nvOC and successfully resolved this matter and how?
Sorry guy´s i am lost here, need some help i can´t use nvOC with a Ryzen processor.
You are using AMD GPU on nvOC? You should use rxOC for AMD and cant use mix of Nvidia and AMD on nvOC and rxOC Let me clear it up. No, i was not mixing AMD and Nvidia gpu´s in one rig, instead i built several rigs either using all AMD or all Nvidia. In fact, after figuring out that it has something to do with the Ryzen cpu i built a rig with a Ryzen 7 1700x and a single AMD gpu then installed nvOC 19-2.0 and got stuck in the login loop. I rebuilt the rig, this time using a single nvidia card alongside the Ryzen 7 1700x and again was stuck in the login loop. To further explain, the Ryzen 7 doesn´t have a builtin gpu, so in order to get anything on the screen you have to use at least a single external gpu. That is why i was asking if somebody actually is mining succesfully using nvOC in combination with a Ryzen cpu? I can´t get passed the login loop using any Ryzen cpu and nvOC. And since i don´t know enough about Linux i can´t resolve the login loop by myself. Don't bother with Ryzen CPU on the current nvoc which is based on Ubuntu 16.04 which runs on linux kernel 4.4. That kernel doesn't support Ryzen. You could upgrade kernel on ubuntu 16.04 to 4.10 which gives partial support for Ryzen but not stable operation (you will have to Google how to do it) but you would still get crashes. You would need at least kernel 4.11 for better Ryzen support but Ubuntu doesn't provide that kernel for 16.04. You could compile latest 4.15 kernel yourself but that requires more than few clicks or simple guidance on this forum thread... that is way out of scope... Your best bet is to wait for the next nvoc release which will be based on the upcoming Ubuntu 18.04 with kernel 4.15 (ETA May 2018) and use Windows with your Ryzen CPU's in the meantime. BTW, you stated that you were also trying AMD Gpu's on nvoc. That will absolutely not work with nvoc. There are no AMD drivers in nvoc and all scripts are specifically made for nvidia cards. If you want you can try rxoc that is specifically made for AMD cards but haven't been maintained for a while... I am not sure if fullzero will continue maintaining that OS or not. |
|
|
|
Hi
I am using main BioStar H81S2, how can I boot nvOC from USB Stick. I tried to using it, but it not show from boot menu.
Disable UEFI, enable CSM or Legacy boot devices. Try different USB ports. If you still having trouble join the Discord chat, it's easier to troubleshoot through live chat (I think the link is in the third post on page 1 of this thread) |
|
|
|
I have been looking at how well I could be doing using the WTM switcher system here. I did quite a long data set with 4 coins listed ETH ETC ZEC and BCG as my choices. At first there was quite a lot of switching being done. But lately with the last blood bath, ETH has stayed at the top of the list followed with ETC and then ZEC. BTG being the low dog on the block.
I was wondering how well others have been doing in the other coin arenas. I would love to hear which coins you do and why. After all my testing I have decided to just leave the rigs on ETH and see how I fare out. So far, I have done well. This is of course just my direction to go. There are so many to choose from any more it boggles the mind.
All my miners are now GTX1060 except one which is a GTX1050TI and my first one. As a side, all the GTX1060 3G cards have went south under the strain. GRINS
Onward thay
If you are experiencing problems creating DAG when mining ETH on GTX1060 3GB cards add this in the extra arguments for Claymore It might help for a while. |
|
|
|
Can anyone confirm DAG file limitations using 1060 3gb under windows 10 vs windows server?
I am unable to generate the DAG (epoch 176). I fresh installed windows 10 without any windows updates as well without a fix.
Anyone having similar problems or lack of problems running windows server 2016?
Only installing windows 7 will save you, and nothing more Try adding command line argument and see if that helps. Apparently this works on Claymore. |
|
|
|
Can anyone confirm DAG file limitations using 1060 3gb under windows 10 vs windows server?
I am unable to generate the DAG (epoch 176). I fresh installed windows 10 without any windows updates as well without a fix.
Anyone having similar problems or lack of problems running windows server 2016?
if you have a GTX 1060, you should mine other coins. you are wasting your hashpower This is not true. GTX 1060 with Samsung memory hashes a bit over 25 MH/s at 75 watts power limit? Wasting hashpower? |
|
|
|
Thanks, I was using 19-1.4 but will try version 19-2.0 now.
Is there a way to mine only certain gpu's?
There is no built-in option to select particular gpu's only yet. The default scripts select all available Gpu's. For example you could use ETH_EXTENSION_ARGUMENTS="" and supply extra arguments for Claymore miner (consult claymore how to select gpu's), but if you want to mine ethash with gpu's 0-3 and equihash with gpu's 4-7 You would need to supply appropriate arguments to both miners involved and you will need to use individual PL, Core and Mem settings because different algos require different settings. Hopefully we will implement some simpler settings for selecting particular cards, dual/triple miners and algos in future versions of nvoc |
|
|
|
Hi All,
First off all would like to thank all that are involved in creating nvOC, seems like an awesome piece of software!!
I have just started to use nvOC and after a few minutes of mining the entire system crashes and only a reboot will work.
I am using the Asus B250 mining expert with 13 1080ti's which I have been using without any issues on Ubuntu 16.0.4 for the last few months, however when I try nvOC on the same hardware setup the mining crashes after a few minutes.
I have enabled CSM in the BIOS and also plugged in the monitor to the 16pci GPU.
I have also tried disabling some of options on the 1bash file which I do not need.
So I can carry out further fault finding can someone please advise how I can select only certain GPU's to mine?
Also is there a way to stop terminal from auto-mining when it is opened so I can enter other commands and use terminal as normal?
Any other suggestions?
Thanks in advance!!!
Which version of nvoc have you installed? Are you running on latest 19-2.0 Community Release? The 19-2.0 has option in 1bash to enable or disable auto-mining: Change that to NO 19-2.0 has a lot of bug fixes from previous versions. If you are running 19-2.0 and still experience problems, open guake terminal with F12 and run And post the report here |
|
|
|
Do these settings look alright ?
EVGA SC2 1070 Power 140, MemOC 1250
EVGA 1060 Power 120, MemOC 1100
EVGA 1080 Power 150, MemOC 1260
EVGA 1080 Ti 150, MemOC 1270
Depends what you are mining, what memory chips you cards have, etc. For example, my settings for ETH: 1060 with Samsung memory: PL: 75, Core: -200, Mem: 1750-1850, hash ~25 MH/s 1070 with Micron memory: PL: 110, Core: -200, Mem: 1300-1400, hash ~ 31 MH/s I don't know if its samsung or micron, i think my 70's are micron. Any idea how to check in linux ? Unfortunately you will have to check them under Windows with GPU-Z. To my knowledge there's no linux tool yet. |
|
|
|
Do these settings look alright ?
EVGA SC2 1070 Power 140, MemOC 1250
EVGA 1060 Power 120, MemOC 1100
EVGA 1080 Power 150, MemOC 1260
EVGA 1080 Ti 150, MemOC 1270
Depends what you are mining, what memory chips you cards have, etc. For example, my settings for ETH: 1060 with Samsung memory: PL: 75, Core: -200, Mem: 1750-1850, hash ~25 MH/s 1070 with Micron memory: PL: 110, Core: -200, Mem: 1300-1400, hash ~ 31 MH/s |
|
|
|
Is it WiFi support I have D-Link dwa 132 WiFi adapter and
what the monthly fee
And what the best amd driver for my Rx 560 I use blockchain
And what the max number for GPUs
Most of the WiFi adapters are supported. If your WiFi adapter works with plain Ubuntu it will work with nvoc and rxoc. There is no monthly fee for nvoc and rxoc. It's free. This thread is for nvoc (nvidia cards only). You might want to search for rxoc thread (amd cards only). Unfortunately nvoc doesn't support amd cards at this time. At the current state nvoc supports 19 GPU's with Asus B250 Mining expert, however due to motherboard limitation you can use 13 regular GPU's and you have to use 6 GP10x-100 mining GPU's for a total of 19. |
|
|
|
|
+1 for linux version.
Please PM me if you have beta version so I can work on implementation within nvOC and do some preliminary tests before implementing it in the next version of nvOC.
Thanks!
|
|
|
|
My miner was working good last night. This morning it was crashed and at a screen wanting a password.
It appears to accept the pass: miner1 but then comes right back to the same screen.
I have rebooted it several times with the same results.
Any suggestions?
If you are on older versions it may be a broken nvidia update. Try this from an ssh session: I answered him on discord. He is using LOCAL. So here is what to do: Press CTRL-ALT-F1 together. Login with user: m1 pass: miner1 Issue these two commands: sudo dpkg --configure -a
sudo shutdown -r now |
|
|
|
It's very unusual for network card not to be recognized by nvoc. Not impossible, but unusual.
Since you have extensive Windows experience, have you tried installing Windows on that motherboard to confirm it is not a hardware failure?
If your network card works well under Windows we can rule out defective hardware and try to troubleshoot further.
What are you trying to mine? If you are planning on mining an Ethash coin; If you are having trouble with the community edition: I recommend trying vBasic as that motherboard should be supported by it. The Community Release edition was based and built upon nvoc 19-1.4 which is built on top of Ubuntu 16.04. If I understand correctly the vBASIC version is also built on top of Ubuntu 16.04. This should not be specific problem tied to the Community Release and if in fact it is related to base Ubuntu 16.04 than it will affect both, the Community Release and vBASIC release. It seems like his motherboard is defective. |
|
|
|
|
Show Posts
