Quote from: leenoox on March 05, 2018, 03:02:41 AM

Quote from: mudball on March 04, 2018, 11:02:43 PM

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!

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.

I have not tried installing Windows. But even if I interrupt the boot sequence and look at the System Information, the MAC address for the LAN controller (which is onboard to the motherboard) is blank. It's like the motherboard doesn't see it. And if I try to plug a USB WiFi adapter in after boot-up, it's dead too. No activity at all. Yet if I plug a USB data stick in to the same USB port, it opens up and lets me browse the stick. Regardless of the OS, wouldn't the fact that the BIOS interrupt and review of system info not showing an active LAN controller indicate it is an issue prior to the OS?