 Show Posts
|
|
Pages: [1]
|
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. Hey Stubo, Compile it from source, it works a charm with cuda8. autogen.sh configure build.sh Compiled it with cuda9 as well, there is no difference whatsoever on some hundred of 1070, 1070Ti and 1080Ti YMMV |
|
|
|
|
Great to see a new OSS project and a brave dev making it open source.
In order to get more traction it would be useful to handle worker names transparently, that is presenting to the upstream pool each and every worker name behind the proxy. Sometimes, when you have 20 workers, you'd need to somehow check their hash stats with the pool.
|
|
|
|
Putting all my responses in RED and in one reply (working from nvOC in LOCAL mode so not able to copy-and-paste results, so I'm slow...) In order to be able to help you a bit, try to run the following command:
sudo lshw -C network
When I run that command, it flashes "PCI (sysfs)" real quickly & disappears and then flashes "USB" real quickly & disappears and then returns to the command prompt of m1@m1-sesktop:~$sudo lshw -C network | grep logical
When I run that command same outcome as command above: it flashes "PCI (sysfs)" real quickly & disappears and then flashes "USB" real quickly & disappears and then returns to the command prompt of m1@m1-sesktop:~$For some even more debug options, the result of the following commands will give us a hint on the potential driver/modules issues:
sudo lspci -nnk | grep -iA2 eth
This does nothing other than return to the command prompt.sudo cat /etc/network/interfaces
Returns these three lines:
# interfaces(5) file used by ifup( and ifdown(
auto lo
iface lo inet loopback
You can always try to re-initialize the network-manager using this command:
sudo dpkg-reconfigure network-manager
I get the following message: insserv: warning: script 'gpu' missing LSB tags and overrides
Then I used: sudo service network-manager restart
That showed a graphical message that said I was now disconnected and off-line (which is interesting since I wasn't on-line to begin withTry this and get back with the output: lspci -nnk | grep 0200 -A3 There seems to be a issue with the hardware if the lspci and lshw are returning naught... Being a Gigabyte mobo, known for their hairy implementations of the Realtek to ICH bridging, it might help also to update your BIOS: https://www.gigabyte.com/MicroSite/462/images/BIOS-Z270P-D3.zipNOTE: Please check the HW revision of your mobo before trying to update. This is a "mining" optimised BIOS I've seen something similar a while back with a rev. 1 board, similar to yours, that was running out of lanes for peripherals and the loading of the PHY drivers for ethernet and usb were loaded erratically at times. |
|
|
|
In order to be able to help you a bit, try to run the following command:
sudo lshw -C network
and paste here the result.
When I run that command, it flashes "PCI (sysfs)" real quickly & disappears and then flashes "USB" real quickly & disappears and then returns to the command prompt of m1@m1-sesktop:~$ R u running the command using the guake terminal ? Come over to discord and lets work it out over there. |
|
|
|
Am a newbie to mining and setting up my first rig. Have an extensive Windows background. Have zero Linux background (except for the immersion course I'm in the middle of trying to get nvOC v2.0 set up and running  ). I got nvOC up and running but my issue is, somewhere along the way, the LAN controller ceased being recognized. My setup:- Attempting a 6-card build with all 1080ti's, largely following Vosk's "How to Build a 6x 1080 TI Mining Rig with ATX & Server PSU's" (https://www.youtube.com/watch?v=2MxNVySpbcw)
- Motherboard = Gigabyte Z270P-D3
- PSU (to power risers) = EVGA Supernova 650 P2
- PSU (to power cards) = Bitmain APW3++
- Harddrive = Lexar 32G USB 3.0 memory stick
I'm initially working to get one card set up and running. It is plugged into a riser that is connected to the primary PCI slot on the mobo, both of which (riser and card) are powered by the EVGA PSU (once I get one card running I'll work up to all six cards and then power the risers solely with the EVGA and the cards with the Bitmain). I have the most current BIOS for the mobo installed, 1bash is configured to mine SMART and I can boot & have the miner software functioning. But my current issue is that the LAN controller is not visible to the OS. I've had fits and starts thru this process, re-imaging the USB probably 4 or 5 times, for various things I hadn't done correctly (e.g., hadn't updated the BIOS before booting, had plugged my monitor into the mobo HDMI instead of the cards's HDMI and dealt with Xorg issues, etc.). I know that at one point, the LAN controller was working (green light flashing on controller, which BTW, is a Realtek® GbE LAN chip (10/100/1000 Mbit))-- I'm just not sure when it quit working to be able to exactly determine what I might have changed that caused the issue. Diagnostics & Steps I've Taken To Address- Re-imaged nvOC
- Reset CMOS (including pulling mobo battery for about 30 minutes)
- ifconfig -a only shows a "lo" entry, no WLAN
- sudo lshw -c network flashes "PCI (sysfs)" real quickly and then flashes "USB" real quickly and then returns to the command prompt
- And yes, I have tried plugging in an ethernet cable that was live and working in another computer sitting right next to my rig
I guess the issue could be a fried controller, but this is a brand new mobo. The only other thing I did differently at one point was change the mouse I was using from a USB mouse to an older wireless mouse where the wireless receiver plugs into the light green mouse port on the back of the mobo instead of being a USB mouse. But I've re-imaged, reset CMOS, etc. since then and even went without using a mouse on a couple of attempts to see if that had caused some issue. Anyway, I would greatly appreciate any assistance and guidance the Community might have to offer. Thank you! In order to be able to help you a bit, try to run the following command: sudo lshw -C network then sudo lshw -C network | grep logical and paste here the result of both commands. For some even more debug options, the result of the following commands will give us a hint on the potential driver/modules issues: sudo lspci -nnk | grep -iA2 eth sudo cat /etc/network/interfaces You can always try to re-initialize the network-manager using this command: sudo dpkg-reconfigure network-manager |
|
|
|
Try this: for i in s u b; do echo $i | sudo tee /proc/sysrq-trigger; sleep 5; done # reboot no matter the state for i in s u o; do echo $i | sudo tee /proc/sysrq-trigger; sleep 5; done # shutdown the system even when it is in a hanged state Is there a script for a “rig offline” telegram notification that I’m missing? The telegram messages are awesome, but would be good to know if it powers down and stay down.
If system is going to be rebooted you will get notified from script that send the reboot command (watchdog or temp control), but if your rig freeze there is nothing to do. You can set up an external watchdog like an RPi to check your rigs ping and ssh port and send you message if they were unreachable. Hi About this, does nvOC use the linux kernel watchdog ? Unfortunately no. Actually a card in one of my rigs making it hard freeze lately and I was reading and playing with sysctl to do a reboot on kernel panic with no success. I changed in both watchdog and temp control to sudo systemctl reboot --force Didnt helped a bit. Also added to /etc/sysctl.conf And no help too, The system freezes after 3-4 days of running clean with no logs, just a hard freeze. Any one has good ideas to implement linux hardware kernel watchdog would be amazing to add ... |
|
|
|
Seeding with a gigabit seedbox and a 500 MB 2nd seedbox for the next 7 days. Enjoy ! |
|
|
|
Guys what is SRR option?
also when i set minimum temp=25 or lower, it wont go lower than 30
(using v0019 with updating)
SRR = Simple Rig Resetter it's a little board that connects to your power/reset pins on the motherboard, it then listens for heartbeats from specific rigs, when the heartbeat stops, it means the rig froze, it hard re-sets the specific rig. https://simplemining.net/download/SRR/PDF/SRR-manual-2017-02-10.pdfI've been using one for a few months, saved me lots of time at the beginning. Does Linux ever hard freeze? Been using ubuntu since 2006, Got lucky and have never experienced it. I'm running my own 176 cards and hosting another 388 for friends and family and turning this into a hosting business. After trying basically all the setups possible (with 6,7,8,9, 13 cards) i've settled on 3 cards per rig. Never looking back. If you're using second hand HP Compaq DC7800 or DC7900 (you get it for 40 usd in my country with 4 G RAM, 3 pciex slots) and a dual core duo CPU you get the vPro awesomeness of full remote power on and off and Intel AMT out of band remote management included. Nobody can't beat that. Upgrade the firmware on the motherboards and BAM! you have a remote KVM built in. You can see your screen and do whatever you want from anywhere in the world. If i am running 1080 cards and above, i buy a 750 W server PSU for another 50 USD and i can have a full rig up and running with the total cost of 90 USD per rig. If i am running 1060 cards, i simply upgrade for 10 usd the PSU in the SFF desktop to a 500 W one... All the rigs are beautiful, no cabling nightmare, whenever a rig crashes i scripted a full power cycle using a raspberry pi as a watchdog. SRR's are expensive when you have a lot of rigs. |
|
|
|
There are NO such limitations; nvOC is designed to max of 13 cards without any modification of 1bash & 3main (can add more by modifying these two files). Try to verify the risers (swap them around with the working ones).
Hash rates dropped with your 8 cards??
OK, I think same - no limitations... I've rate ~6400 Sol/s with 8 cards. After connection next 3 cards, rate dropped to ~5100 Sol/s only. nvOS didn't detect more than 8 cards, as you can saw on nvidia-smi. Well, risers maybe problem - I'm novice in mining, so I ordered more types. I using version v006C and v008S. On cards plugged on v006C blinking LEDs below power connectors on card. I've ordered 13 pcs of v008S (these: www.aliexpress.com/item/TISHRIC-2018-Hot-VER008S-Molex-4PIN-15PIN-SATA-6PIN-3-in-1-PCIE-PCI-Express-Riser/32830747032.html). I hope that will works well. Many thanks :-) What is your CPU ? I had the exact same issue with AsRock and 12 Ti's and it all went smooth when i switched the CPU's from the rig with my own. For me it worked putting a i5 7400 on the motherboard. Maybe it works with a less expensive CPU but it was the only one i had around. |
|
|
|
Hi guys, can someone give some hints or explain what is wrong with my rigs since only the gpu0 can have can receive/execute the fan speed as being set ? Below is the error i see all the time when any other than gpu0 fan gets set:
ERROR: Error assigning value 50 to attribute
'GPUTargetFanSpeed' (m1-desktop:0[fan:1])
as specified in assignment
'[fan:1]/GPUTargetFanSpeed=50' (Unknown
Error).
I am currently using rigs with 3 x 1080 Ti and 3 x 1070's and having the first release of v019 installed on SSD.
Tried manually to do:
nvidia-xconfig --enable-all-gpus
nvidia-xconfig --cool-bits=4
nvidia-settings -a [gpu:1]/GPUFanControlState=1
nvidia-settings -a [fan:1]/GPUTargetFanSpeed=50
but the error is the same.
Other than being unable to set the fan speeds, the rigs are chugging along, however, the speed of the fans for the cards other than gpu0 is the factory default as neither the minimum fan speed set in 1bash gets applied, with or without the automated fan control feature.
Edit: in the nvidia x server settings i can see the Enable fan control feature for the gpu0 but it is missing for the other gpu's.
Does the error happens if you set speed to higher values like 60-65 too ? I think I had the same problem on low values Thank you for your answer ! Yes, the problem persists even if i set higher fan values or 100%... In the Thermal Settings in the nvidia x settings utility only gpu0 has fan control option enabled, the other gpu's are missing this feature. Then may be some things wrong with the image/OS Some times starting from scratch is easier than trying to solve the problem. P.S. is GPU Power Mizer Mode set in 1bash? GPUPowerMizerMode_Adjust="YES"
The PowerMizer setting makes no difference. However, i think there is something odd here. When i run manually m1@m1-desktop:~$ lspci |grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1) 20:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1) 30:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1) Then in the xorg.conf generated in an attempt to debug the issue i have: Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce GTX 1070" BusID "PCI:1:0:0" EndSection Section "Device" Identifier "Device1" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce GTX 1070" BusID "PCI:32:0:0" EndSection Section "Device" Identifier "Device2" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce GTX 1070" BusID "PCI:48:0:0" EndSection Shouldn't there be some sort of relation between what the lspci command lists and the Xorg.conf device id ? I think its better not to waste your time on finding the solution to the problem, as it should be none start from scratch. Set your bios, connect one gpu, boot,copy your 1bash (there is a bug that wont copy it from temp partition), reboot, check if every thing is ok. shutdown, connect rest of the gpu, restart, while first one is still connected, it may reboot with xorg error. After restart all should be ok. Well... i can build a complete rig for less than usd50 using older hp compaq business pc's like dc7800 or dc7900, everything works ok with dc7900, this issue seems to be related to the dc7800. The dc7800 has 3 pciex slots as its biger sibling dc7900, the only difference being the chipset: dc7900 has a q45 chipset while dc7800 has a q35 chipset. I'll try tomorrow with a dc7900 using the same gpu cards to see if it works. These older motherboards might have glitches with the latest ubuntu... EDIT: SOLUTION: In the /etc/X11/xorg.conf in the Devices section there should be a Screen 0 added right before the EndSection. That fixes it. Apparently if the busId of the VGA is >16 nvOc doesn't attach the screen to the cards and hence there is no power nor fan control enabled for the cards. Tested the fix with old motherboards using Q35 and Q45 chipsets. |
|
|
|
Hi guys, can someone give some hints or explain what is wrong with my rigs since only the gpu0 can have can receive/execute the fan speed as being set ? Below is the error i see all the time when any other than gpu0 fan gets set:
ERROR: Error assigning value 50 to attribute
'GPUTargetFanSpeed' (m1-desktop:0[fan:1])
as specified in assignment
'[fan:1]/GPUTargetFanSpeed=50' (Unknown
Error).
I am currently using rigs with 3 x 1080 Ti and 3 x 1070's and having the first release of v019 installed on SSD.
Tried manually to do:
nvidia-xconfig --enable-all-gpus
nvidia-xconfig --cool-bits=4
nvidia-settings -a [gpu:1]/GPUFanControlState=1
nvidia-settings -a [fan:1]/GPUTargetFanSpeed=50
but the error is the same.
Other than being unable to set the fan speeds, the rigs are chugging along, however, the speed of the fans for the cards other than gpu0 is the factory default as neither the minimum fan speed set in 1bash gets applied, with or without the automated fan control feature.
Edit: in the nvidia x server settings i can see the Enable fan control feature for the gpu0 but it is missing for the other gpu's.
Does the error happens if you set speed to higher values like 60-65 too ? I think I had the same problem on low values Thank you for your answer ! Yes, the problem persists even if i set higher fan values or 100%... In the Thermal Settings in the nvidia x settings utility only gpu0 has fan control option enabled, the other gpu's are missing this feature. Then may be some things wrong with the image/OS Some times starting from scratch is easier than trying to solve the problem. P.S. is GPU Power Mizer Mode set in 1bash? GPUPowerMizerMode_Adjust="YES"
The PowerMizer setting makes no difference. However, i think there is something odd here. When i run manually m1@m1-desktop:~$ lspci |grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1) 20:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1) 30:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1) Then in the xorg.conf generated in an attempt to debug the issue i have: Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce GTX 1070" BusID "PCI:1:0:0" EndSection Section "Device" Identifier "Device1" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce GTX 1070" BusID "PCI:32:0:0" EndSection Section "Device" Identifier "Device2" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce GTX 1070" BusID "PCI:48:0:0" EndSection Shouldn't there be some sort of relation between what the lspci command lists and the Xorg.conf device id ? |
|
|
|
Hi guys, can someone give some hints or explain what is wrong with my rigs since only the gpu0 can have can receive/execute the fan speed as being set ? Below is the error i see all the time when any other than gpu0 fan gets set:
ERROR: Error assigning value 50 to attribute
'GPUTargetFanSpeed' (m1-desktop:0[fan:1])
as specified in assignment
'[fan:1]/GPUTargetFanSpeed=50' (Unknown
Error).
I am currently using rigs with 3 x 1080 Ti and 3 x 1070's and having the first release of v019 installed on SSD.
Tried manually to do:
nvidia-xconfig --enable-all-gpus
nvidia-xconfig --cool-bits=4
nvidia-settings -a [gpu:1]/GPUFanControlState=1
nvidia-settings -a [fan:1]/GPUTargetFanSpeed=50
but the error is the same.
Other than being unable to set the fan speeds, the rigs are chugging along, however, the speed of the fans for the cards other than gpu0 is the factory default as neither the minimum fan speed set in 1bash gets applied, with or without the automated fan control feature.
Edit: in the nvidia x server settings i can see the Enable fan control feature for the gpu0 but it is missing for the other gpu's.
Does the error happens if you set speed to higher values like 60-65 too ? I think I had the same problem on low values Thank you for your answer ! Yes, the problem persists even if i set higher fan values or 100%... In the Thermal Settings in the nvidia x settings utility only gpu0 has fan control option enabled, the other gpu's are missing this feature. |
|
|
|
|
Hi guys, can someone give some hints or explain what is wrong with my rigs since only the gpu0 can have can receive/execute the fan speed as being set ? Below is the error i see all the time when any other than gpu0 fan gets set:
ERROR: Error assigning value 50 to attribute
'GPUTargetFanSpeed' (m1-desktop:0[fan:1])
as specified in assignment
'[fan:1]/GPUTargetFanSpeed=50' (Unknown
Error).
I am currently using rigs with 3 x 1080 Ti and 3 x 1070's and having the first release of v019 installed on SSD.
Tried manually to do:
nvidia-xconfig --enable-all-gpus
nvidia-xconfig --cool-bits=4
nvidia-settings -a [gpu:1]/GPUFanControlState=1
nvidia-settings -a [fan:1]/GPUTargetFanSpeed=50
but the error is the same.
Other than being unable to set the fan speeds, the rigs are chugging along, however, the speed of the fans for the cards other than gpu0 is the factory default as neither the minimum fan speed set in 1bash gets applied, with or without the automated fan control feature.
Edit: in the nvidia x server settings i can see the Enable fan control feature for the gpu0 but it is missing for the other gpu's.
|
|
|
|
Hi there nvoc-ers !
I may be stupid or definitely not paying enough attention to something as i can't for sake of me to be able to make AsRock H110 to recognize 13 x 1060 6GB GPU's. Tried with nvoc17, then 18, then 19..does not see the gpu on the last pciex slot.
It mines beautifully with 12 GPU's but there is no way i can make it see all the 13 GPU's.
The rig is built using a G4560, i tried using an i3... same result.
2 x Corsair 1000 W PSU's powering 6 gpu + mobo + risers and the 2nd powering 7 gpu's
Any hints ?
I struggled with this for a very long time. For me, it came down to a bad riser. I could have sworn I had tested and replaced them all, but this past weekend I started with one, and kept adding 1, one boot at a time, until I got to 13 working. I swear I did this a few times, but i find the pic-e risers LOVED to come loose as well, and may have had bad luck swapping a bad riser for a bad riser. Aside from that, if you haven't, I would make sure the the 2 molex connectors on the motherboard are each connected to the separate power supplies. Also, I noticed you have all risers on one PSU. I believe I have read that you should not have more than 2 per connector - I am unsure how many connectors are on those corsairs, but it might be worth trying splitting them up if you haven't. Let me know if you get anywhere with this. I put 3 risers per 1 connector - works fine Hello guys and thank you for your answers ! Regarding the risers there are lots of urban legends, they draw up to 25 - 30 W each, measured for 24h continously, on 3 different rigs, one with 1060, one 1070 and one 1080ti's. Surprisingly the 1080Ti's draw a steady 25 W, no fluctuations as 1070's or 1060's. As long as the rail supports it and the sum of the draw of the risers do not exceed the rated wire, you can add as many as you want. Apparently the motherboard has a issue with the last pciex slot, as i replaced the mobo and it worked from the first boot. Switched it back to the old mobo and the same problem with the 13th card not being recognised was identified. I changed the risers with new ones, tested with the 2nd board in parallel, the same card and same riser, its final: the mobo might have a defective pciex port. I suspect a mechanical issue since the riser doesn't get powered by the mobo. Thank you again for your support ! |
|
|
|
|
Hi there nvoc-ers !
I may be stupid or definitely not paying enough attention to something as i can't for sake of me to be able to make AsRock H110 to recognize 13 x 1060 6GB GPU's. Tried with nvoc17, then 18, then 19..does not see the gpu on the last pciex slot.
It mines beautifully with 12 GPU's but there is no way i can make it see all the 13 GPU's.
The rig is built using a G4560, i tried using an i3... same result.
2 x Corsair 1000 W PSU's powering 6 gpu + mobo + risers and the 2nd powering 7 gpu's
Any hints ?
|
|
|
|
|
Hi there guys !
Long time lurker and actual user of nvOC, i need help converting my 21 1080Ti's into rigs with 3 cards using HP DC7900 Small Form Factor pc's as the base for the rigs.
My issue is that although i can boot basically any live distro using a USB stick, i can't boot no matter what nvOC from a usb stick.
Does nvOC needs a UEFI compatible BIOS in order to be booted by older machines ?
Can i convert the image to be non-GPT and hence bootable on older machines ?
Thanks a lot for your support !
|
|
|
|
|
