[OS] UbuMiner -Free Nvidia Linux Mining Build v0.81 : Simple / Clean / 14GB - page 3.

CryptoWatcher420

sr. member

Activity: 462

Merit: 258

Small Time Miner, Rig Builder, Crypto Trader

so in this OS's current state what does it offer that others do not? ethos does both AMD and NVidia, so why make one yourself that only plays to a smaller part of the crypto mining community? you are in fact losing out on a lot by doing so

minerja

sr. member

Activity: 1249

Merit: 297

oh, and sceen is real laggy...scrolling down this box takes seconds, in stages....never had that before with ubuntu....weird

minerja

sr. member

Activity: 1249

Merit: 297

Update.

Re-booted and re ran "run on 1st boot" , selected "Y" to install drivers, blah blah, installed, no errors, re-bboted....repeat 3 times

On 4th time, same actions, diff result...driver install took considerably longer, and now i have a 1080p destop...yippee

ran "mine@ and got this
==================================================================
miner@miner:~/Mining$ mine

UbuMiner v0.72

Mining ZEN Coins with zm_0.3.2 starting in 20 seconds...

TEST Mode: The miner will not exit from SCREEN automatically when it terminates.
It will wait for you to type [exit] to terminate the screen.

This is done so you can see errors with your miner if it crashes!

Press ENTER to start Mining now or CTRL-C to stop

Persistence mode is already Enabled for GPU 00000000:01:00.0.
All done.

Provided power limit 75.00 W is not a valid power limit which should be between 30.00 W and 38.50 W for GPU 00000000:01:00.0
Terminating early due to previous errors.
Persistence mode is already Enabled for GPU 00000000:07:00.0.
All done.

Provided power limit 75.00 W is not a valid power limit which should be between 30.00 W and 38.50 W for GPU 00000000:07:00.0
Terminating early due to previous errors.
No devices were found

ERROR: Error resolving target specification 'gpu:2' (No targets match target
specification), specified in assignment
'[gpu:2]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:2' (No targets match target
specification), specified in assignment
'[gpu:2]/GPUMemoryTransferRateOffset[3]=000'.

No devices were found
No devices were found

ERROR: Error resolving target specification 'gpu:3' (No targets match target
specification), specified in assignment
'[gpu:3]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:3' (No targets match target
specification), specified in assignment
'[gpu:3]/GPUMemoryTransferRateOffset[3]=000'.

No devices were found
No devices were found

ERROR: Error resolving target specification 'gpu:4' (No targets match target
specification), specified in assignment
'[gpu:4]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:4' (No targets match target
specification), specified in assignment
'[gpu:4]/GPUMemoryTransferRateOffset[3]=000'.

No devices were found
No devices were found

ERROR: Error resolving target specification 'gpu:5' (No targets match target
specification), specified in assignment
'[gpu:5]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:5' (No targets match target
specification), specified in assignment
'[gpu:5]/GPUMemoryTransferRateOffset[3]=000'.

No devices were found
No devices were found

ERROR: Error resolving target specification 'gpu:6' (No targets match target
specification), specified in assignment
'[gpu:6]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:6' (No targets match target
specification), specified in assignment
'[gpu:6]/GPUMemoryTransferRateOffset[3]=000'.

No devices were found

Executing:
./zm --server us.zenmine.pro --port 9009 --user znhasBQy3fZUVTpQUd7JkYdgRHUskCcwyiC.miner

Type: screen -r miner to check on Mining Progress.

TEST Mode: The miner will not exit from SCREEN automatically when it terminates.
It will wait for you to type [exit] to terminate the screen.

This is done so you can see errors with your miner if it crashes!
================================================

when i run "gpus" i get this

=================================
miner@miner:~/Mining$ gpus
   Bus Address: 0000:00:01.0
   Bus Address: 0000:00:1c.3
   Bus Address: 0000:08:1c.4
   Bus Address: 0000:00:1c.5
   Bus Address: 0000:00:1c.6
   Bus Address: 0000:00:1c.7
Fri Sep 29 04:01:44 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.90 Driver Version: 384.90 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 750 Ti On | 00000000:01:00.0 On | N/A |
| 51% 61C P0 25W / 38W | 1534MiB / 1999MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 750 Ti On | 00000000:07:00.0 Off | N/A |
| 46% 57C P0 26W / 38W | 1352MiB / 2000MiB | 100% Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 985 G /usr/lib/xorg/Xorg 140MiB |
| 0 1554 G compiz 41MiB |
| 0 2171 C ./zm 446MiB |
| 0 2286 C ./zm 446MiB |
| 0 2653 C ./zm 446MiB |
| 1 2171 C ./zm 446MiB |
| 1 2286 C ./zm 446MiB |
| 1 2653 C ./zm 446MiB |
+-----------------------------------------------------------------------------+

So, erm, what now, how and where do i go to alter power settings?

making progress...baby steps, but progress
J

minerja

sr. member

Activity: 1249

Merit: 297

hatch789

member

Activity: 66

Merit: 10

Sorry I have been crazy busy lately guys. Has anyone tried v0.72 on their rigs? I am hoping some people will have favorable results without needing to use Recovery Mode to get past their first boot. I will be doing some more testing this weekend and making adjustments as necessary.

hatch789

member

Activity: 66

Merit: 10

Hello Everyone,

I've added a new version 0.72 that has some (hopeful) fixes for the issues experienced on boot-up ...seems as though the nouveau driver is being a bugger. If you can't boot cleanly the first boot, then use GRUB to boot into Recovery Mode. That will let you boot up and install the nvidia drivers.

Once they are installed you should be fine.

Here are the highlights of the v0.72 changes:

-After doing some research on a boot issue experienced by a user, I have now installed the "nomodeset" option in the GRUB boot loader.
   -Hopefully this will help with any black screen "lockups" on first boot that people were experiencing
   -We will need to all do some testing to determine if it helps with the nouveau lockups
   -Alternatively boot into Recovery Mode the first time to get the nvidia drivers first loaded then reboot normally after that
-Added the journalctl system to the setup. This will help us diagnose any odd boot issues people experience
   -journalctl -b0 will show the current session's boot records
   -journalctl -b-1 will show the last session's boot records
   -journalctl -b-2 will show the 2nd to last session's boot records and so on
   -Added a crontab option on each reboot to remove or clear the journal records above the last 10. Helps keep the journal size small
-Added the pci=nomsi kernel option to the /etc/default/grub file so that the PCI errors that are sometimes generated with newer motherboards are eliminated
-Did some work to clean up the crontab file and add comments
-Performed some system updates through aptitude to keep the build up to date and fresh for everyone

hatch789

member

Activity: 66

Merit: 10

Quote from: chtat12 on September 14, 2017, 12:34:06 AM

For the first boot, I had to unplug all my GPUs except the one connecting to display. Boot up, then I installed a driver (via the provided 1st script). Shutdown & plug everything in. Reboot. (Now it works for me.) Run 2nd script. And then edit the .coin file.

chtat12, you're a trooper. I applaud you for your patience in working with my build to get it mining on your system. I am sorry you had to go through all that. You shouldn't have to! -I want this to be super simple for you guys. But I am fighting with a kernel or driver issue here and need some Linux Guru's to help me figure out what's going on.

I don't want people to have to pull GPU's out of a working system to run my build. I have also had success by booting up the first time in SAFE Mode or whatever that 3rd option is called. I don't want people to have to do any of this crap! Sad

It's all so very frustrating.

So I will continue to chip away at the problem. I'll continue to try to overcome the problem but if anyone has some help they can offer or some good information for me; that would be most appreciated.

Maybe I can force a NON-graphical First Boot that would then NOT load the nouveau drivers. This first boot could then be used to properly install the nvidia drivers on your system. Next boot could go to the GUI and continue as normal.

Ideas and suggestions welcome!

hatch789

member

Activity: 66

Merit: 10

Quote from: car1999 on September 13, 2017, 11:53:20 PM

0.71 cannot boot on my 4 cards rig, on which nvOC works well.
I got black screen at the first boot, restarted by hand after 10 minutes. after the second boot, it showed a ton of errors, I took a video and would like to send it to your email.

Yeah this sucks. I have worked probably a total of 280 hours on this build now over the past 2 months and it's SOOO nice. But if we can't figure out the boot instability then it's worthless to the rest off you. I don't want you guys to have to fight to get the first boot to work. That's insane!

So I am working hard to overcome this issue. Maybe fullzero is doing some magic with his kernel, maybe he is building his image off of a real machine where I am building my image from a VM? But the odd thing is the image I build v0.70 that had the nvidia drivers pre-installed; worked perfectly fine on two older motherboards and those rigs are operating and rebooting flawlessly every time.

My new Z270-A motherboards, I can't boot to that image without serious PCI errors all over the place! -So frustrating.

That's why I thought OK I'll let you guys do the nvidia driver install on your end during the First Boot script. It only takes 3 minutes so no big deal. But even this causes problems because then the darn nouveau drivers are causing people to hang on a purple or black screen. And again ...my Z270-A motherboards do this as well.

So I can see and reproduce the issue. I just need some suggestions of how to overcome it. What are nvOC and SimpleMining and that other one (forget the name) doing in their builds to allow people to boot with the drivers already installed? -I'm missing something critical here and once that's fixed you guys will have a really nice build to work with that we can all build upon together.

chtat12

newbie

Activity: 7

Merit: 0

Quote from: car1999 on September 13, 2017, 11:53:20 PM

0.71 cannot boot on my 4 cards rig, on which nvOC works well.
I got black screen at the first boot, restarted by hand after 10 minutes. after the second boot, it showed a ton of errors, I took a video and would like to send it to your email.

For the first boot, I had to unplug all my GPUs except the one connecting to display. Boot up, then I installed a driver (via the provided 1st script). Shutdown & plug everything in. Reboot. (Now it works for me.) Run 2nd script. And then edit the .coin file.

car1999

full member

Activity: 350

Merit: 100

0.71 cannot boot on my 4 cards rig, on which nvOC works well.
I got black screen at the first boot, restarted by hand after 10 minutes. after the second boot, it showed a ton of errors, I took a video and would like to send it to your email.

hatch789

member

Activity: 66

Merit: 10

Quote from: trinaldao on September 13, 2017, 11:16:10 PM

btw have screenshot for this OS ?
i want try but i never used linux for mining soo i didnt know how to setting rigs for mine

Setting the rigs for mining is a simple matter of editing the .coin files for the various coins you want to mine. I built example .coin files already into the image so you can use those for starting you off. It seems the numbers are about 2x higher in OC settings than in windows. So if you have 100 core in windows you'd use 200 core here. Obviously I suggest starting a bit lower since the Linux drivers can be a bit unforgiving if you push the OC too far.

But in the end this is a very clean and simple way to manage the individual coins you're mining and the overclocking needs of those coins.

I'm trying very hard to get past this img issue and figure that out. That's why I have not put a new update out for 2 days. Still working on figuring out why people get stuck on boot with nvidia drivers pre-installed and also get stuck on nouveau drivers if I do NOT have the nvidia drivers pre-installed. -I have tried it both ways in search of a solution.

trinaldao

copper member

Activity: 1218

Merit: 1007

Post your ann & bounty just contact me

btw have screenshot for this OS ?
i want try but i never used linux for mining soo i didnt know how to setting rigs for mine

NameTaken

hero member

Activity: 630

Merit: 502

Quote from: hatch789 on September 13, 2017, 08:53:20 PM

Quote from: NameTaken on September 13, 2017, 08:35:14 PM

The image file itself includes the bootloader and multiple partitions.

Yes it is a complete image with bootloader and all. I'm not really sure how I could or would be able to separate out just a single partition and have it be useful to anyone; other than the odd case of wanting that partition for a dual boot (or more) setup.

So NameTaken, it sounds like you've looked at my build. I am running into a technical challenge that perhaps you could offer some advice. In trying to export my image for use I've tried:
A. Not having the nvidia drivers pre-installed; but then people run into errors with the goofy nouveau drivers in the bootup.
B. Pre-installing the nvidia drivers (v0.70) but then it gives a ton of PCI errors on certain newer motherboards.

I'm really wondering how others get around this and build an image if not by these 2 methods. I feel like I'm missing something easy to give you guys a clean bootup the first time; preferably with the nvidia drivers pre-installed.

I actually haven't used or downloaded this but was an educated assumption. I come from more of a sysadmin background that doesn't deal with graphics, audio, mouse, etc so not sure how much help I can provide. My rigs are running vanilla Ubuntu that are managed using ansible playbook. Raspberry Pi distros also come in image files so I wrote a shell function to mount just the root partition

Code:

imount(){
    if [ -n "$(findmnt /mnt)" ]; then
        sudo umount -vR /mnt
    fi
    sudo mount -vo offset=$[512*$(fdisk -l $1 | awk '/83/ && /Linux/ {print $2}')] $1 /mnt
}

then I can use qemu-arm-static and systemd-nspawn to boot it on my PC as a container.

hatch789

member

Activity: 66

Merit: 10

Quote from: NameTaken on September 13, 2017, 08:35:14 PM

The image file itself includes the bootloader and multiple partitions.

Yes it is a complete image with bootloader and all. I'm not really sure how I could or would be able to separate out just a single partition and have it be useful to anyone; other than the odd case of wanting that partition for a dual boot (or more) setup.

So NameTaken, it sounds like you've looked at my build. I am running into a technical challenge that perhaps you could offer some advice. In trying to export my image for use I've tried:
A. Not having the nvidia drivers pre-installed; but then people run into errors with the goofy nouveau drivers in the bootup.
B. Pre-installing the nvidia drivers (v0.70) but then it gives a ton of PCI errors on certain newer motherboards.

I'm really wondering how others get around this and build an image if not by these 2 methods. I feel like I'm missing something easy to give you guys a clean bootup the first time; preferably with the nvidia drivers pre-installed.

NameTaken

hero member

Activity: 630

Merit: 502

Quote from: chtat12 on September 13, 2017, 08:23:33 PM

Is it possible to flash .img file onto an empty partition? Right now my SSD has 2 partitions (dual boot): 1 for Windows and 1 for Ubuntu. I want to replace the Ubuntu with your OS instead. However HDDRawCopy won't let me choose just a partition as a target.

The image file itself includes the bootloader and multiple partitions.

chtat12

newbie

Activity: 7

Merit: 0

Is it possible to flash .img file onto an empty partition? Right now my SSD has 2 partitions (dual boot): 1 for Windows and 1 for Ubuntu. I want to replace the Ubuntu with your OS instead. However HDDRawCopy won't let me choose just a partition as a target.

hatch789

member

Activity: 66

Merit: 10

I did a bit more digging today and found that the default Ubuntu 16.04 install still utilizes the nouveau drivers.

So in some cases even though I did a clean build; it may fail booting up on various motherboards. To that end I have added a setting

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"

This will hopefully be enough to eliminate issues that users may experience while booting up with my new build. I will test this later today on several of my new motherboards to see if it makes any difference.

I have also enabled journalctl so that we can more easily view where things get stuck if there are boot issues.

journalctl -b0 will show the current session's boot records
journalctl -b-1 will show the last session's boot records
journalctl -b-2 will show the 2nd to last session's boot records and so on

hatch789

member

Activity: 66

Merit: 10

Quote from: Porticus on September 11, 2017, 09:36:39 AM

Ok perfect, I got out of work and I'm getting nowhere with it, it's going down SO, we'll see how it works ^^^

Hi Porticus, Not sure I'm following you? What's going down?

I pulled v0.70 because the pre-installed video drivers were messing things up. I have put v0.71 out there now (as of this morning) so please try that new v0.71 build and let me know how you make out with it.

Porticus

full member

Activity: 180

Merit: 100

Quote from: hatch789 on September 10, 2017, 02:30:25 PM

Quote from: Porticus on September 10, 2017, 02:19:26 PM

I use an Asrock pro BTC 2.0, the GPUs are 1050TI, it's a test rig, I try to test new things, performance and more, tomorrow if I can prove what you just told me, thank you and continue with the project!

Well I just loaded up v0.70 early AM this morning. So use that build. It already has the nvidia-384 drivers installed for you. Cheesy

If you make sure the Secure Boot Keys are cleared in the BIOS (if it even has Secure Boot Keys) then you should be fine. I was in the midst of testing on my Z270-A motherboard when we got company so I will get to testing that motherboard with this build in another hour or so. It has worked flawlessly on the 2 boards I tested it on so far. I think you'll like this v0.70 build, so I'll be anxious for your feedback Porticus. Thank you for trying my build and thank you for the feedback so far.

Ok perfect, I got out of work and I'm getting nowhere with it, it's going down SO, we'll see how it works ^^^

hatch789

member

Activity: 66

Merit: 10

Quote from: car1999 on September 11, 2017, 05:15:07 AM

it is 6:13 AM Eastern Time, cannot see 0.71 in the download page.

Crap, I'm sorry!

I inserted a new routine in last night to update the website html pages and version history. The problem line was UpdateWebsite.bat but I should have used call UpdateWebsite.bat instead.

The new little html update routine ran but never returned to the parent batch file. So the files were sitting here and never got uploaded to the site.

I've fixed the routine now. Actually, even went a step further and put that little CALL after the UbuMiner build ZIP is copied out to the server, so if I ever mess up that (UpdateWebsite.bat) again it won't hurt the main routine!

Sorry about that!

Topic: [OS] UbuMiner -Free Nvidia Linux Mining Build v0.81 : Simple / Clean / 14GB - page 3. (Read 5197 times)