Bitcoin Forum
February 20, 2019, 02:58:56 PM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 [289] 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 ... 418 »
  Print  
Author Topic: [OS] nvOC easy-to-use Linux Nvidia Mining  (Read 397936 times)
Stubo
Member
**
Offline Offline

Activity: 222
Merit: 13


View Profile
November 24, 2017, 09:53:28 PM
 #5761

One of my rigs just failed.  Sad
I suspect it was one of the cables that got stuck into the CPU fan.
Motherboard and processor seem completely dead.

I checked the PSU with the paper clip method and it looks like it is working.

If it was really a cable that blocked the CPU fan, is the CPU unrecoverable? (I was convinced that most processors had a protection mechanism of some sort)


I have never seen a hot CPU die. Typically, it just crashes and restarts. What you did is not much different that trying to OC a CPU beyond its thermal  limits and I never killed one that way. If you haven't already, start with the basics - mobo with only power and front panel connectors - no cards in slots or other cables and troubleshoot from there.

Hope this helps.
Hi Stubo,
You were right. It's the motherboard that gave up. The CPU is perfectly fine. :-)

Good to know. I have never seen a mobo fail from CPU heat but I have fried my fair share of them doing other stupid things. <- Don't Ask.
1550674736
Hero Member
*
Offline Offline

Posts: 1550674736

View Profile Personal Message (Offline)

Ignore
1550674736
Reply with quote  #2

1550674736
Report to moderator
1550674736
Hero Member
*
Offline Offline

Posts: 1550674736

View Profile Personal Message (Offline)

Ignore
1550674736
Reply with quote  #2

1550674736
Report to moderator
1550674736
Hero Member
*
Offline Offline

Posts: 1550674736

View Profile Personal Message (Offline)

Ignore
1550674736
Reply with quote  #2

1550674736
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1550674736
Hero Member
*
Offline Offline

Posts: 1550674736

View Profile Personal Message (Offline)

Ignore
1550674736
Reply with quote  #2

1550674736
Report to moderator
WaveFront
Member
**
Offline Offline

Activity: 117
Merit: 10


View Profile
November 24, 2017, 10:58:45 PM
 #5762

One of my rigs just failed.  Sad
I suspect it was one of the cables that got stuck into the CPU fan.
Motherboard and processor seem completely dead.

I checked the PSU with the paper clip method and it looks like it is working.

If it was really a cable that blocked the CPU fan, is the CPU unrecoverable? (I was convinced that most processors had a protection mechanism of some sort)


I have never seen a hot CPU die. Typically, it just crashes and restarts. What you did is not much different that trying to OC a CPU beyond its thermal  limits and I never killed one that way. If you haven't already, start with the basics - mobo with only power and front panel connectors - no cards in slots or other cables and troubleshoot from there.

Hope this helps.
Hi Stubo,
You were right. It's the motherboard that gave up. The CPU is perfectly fine. :-)

Good to know. I have never seen a mobo fail from CPU heat but I have fried my fair share of them doing other stupid things. <- Don't Ask.
I won't ask :-D
bdog1234
Full Member
***
Offline Offline

Activity: 133
Merit: 100


View Profile
November 25, 2017, 08:39:47 AM
 #5763

Would it be a bad idea or difficult to enable ftp server on these nvOC machines?

As I get more and more running it seems it would be nice to be able to blast a 1bash file with all my settings to them. None of my machines have monitors or keyboards.

I guess it could be done with scp but that is kind of slow and clunky.

sikke1
Jr. Member
*
Offline Offline

Activity: 34
Merit: 18


View Profile
November 25, 2017, 09:04:56 AM
 #5764

Would it be a bad idea or difficult to enable ftp server on these nvOC machines?

As I get more and more running it seems it would be nice to be able to blast a 1bash file with all my settings to them. None of my machines have monitors or keyboards.

I guess it could be done with scp but that is kind of slow and clunky.

The pastebin.com script is already doing this. I have setup unique url for each miner and then edit in browser. Miner updates itself automatic. Or you can force reboot with ssh.
ha5hi5h
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
November 25, 2017, 09:06:40 AM
 #5765

fullzero and the gang - thanks for making this an easy distribution for mining. I have been using v19 for the past few months and have now attempted to move to 19-1.4.

Motherboard is an Asrock H110 BTC.

I've recently flashed v19-1.4 to my sandisk ultra fit usb 3.0 drive and even after numerous attempts I am unable to get it to work. v19 was running fine off it.

On the first boot it ends up with the screen:

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built in commands.

(initramfs)

---

After which when I reboot, it goes straight to bios.

Tried this on a couple of different usb drives and the results are the same. Is there a specific setting that I'm missing here?

Thanks and advance
papampi
Full Member
***
Offline Offline

Activity: 420
Merit: 119


Linux FOREVER! Resistance is futile!!!


View Profile
November 25, 2017, 10:01:59 AM
 #5766

fullzero and the gang - thanks for making this an easy distribution for mining. I have been using v19 for the past few months and have now attempted to move to 19-1.4.

Motherboard is an Asrock H110 BTC.

I've recently flashed v19-1.4 to my sandisk ultra fit usb 3.0 drive and even after numerous attempts I am unable to get it to work. v19 was running fine off it.

On the first boot it ends up with the screen:

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built in commands.

(initramfs)

---

After which when I reboot, it goes straight to bios.

Tried this on a couple of different usb drives and the results are the same. Is there a specific setting that I'm missing here?

Thanks and advance

have you tried other usb or ssd ?
I think your usb has reached end of its life, get a 30$ SSD and save yourself.

papampi
Full Member
***
Offline Offline

Activity: 420
Merit: 119


Linux FOREVER! Resistance is futile!!!


View Profile
November 25, 2017, 10:02:47 AM
 #5767

Would it be a bad idea or difficult to enable ftp server on these nvOC machines?

As I get more and more running it seems it would be nice to be able to blast a 1bash file with all my settings to them. None of my machines have monitors or keyboards.

I guess it could be done with scp but that is kind of slow and clunky.

The pastebin.com script is already doing this. I have setup unique url for each miner and then edit in browser. Miner updates itself automatic. Or you can force reboot with ssh.

If you set ssh=yes
you can use sftp.

ha5hi5h
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
November 25, 2017, 01:49:20 PM
 #5768

fullzero and the gang - thanks for making this an easy distribution for mining. I have been using v19 for the past few months and have now attempted to move to 19-1.4.

Motherboard is an Asrock H110 BTC.

I've recently flashed v19-1.4 to my sandisk ultra fit usb 3.0 drive and even after numerous attempts I am unable to get it to work. v19 was running fine off it.

On the first boot it ends up with the screen:

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built in commands.

(initramfs)

---

After which when I reboot, it goes straight to bios.

Tried this on a couple of different usb drives and the results are the same. Is there a specific setting that I'm missing here?

Thanks and advance

have you tried other usb or ssd ?
I think your usb has reached end of its life, get a 30$ SSD and save yourself.

I have. Not USB issue. Tried 3 different ones including two fresh new ones. All 3 works with v19 without issues. Wondering if anyone else is having the same issue.

papampi
Full Member
***
Offline Offline

Activity: 420
Merit: 119


Linux FOREVER! Resistance is futile!!!


View Profile
November 25, 2017, 01:56:53 PM
 #5769

fullzero and the gang - thanks for making this an easy distribution for mining. I have been using v19 for the past few months and have now attempted to move to 19-1.4.

Motherboard is an Asrock H110 BTC.

I've recently flashed v19-1.4 to my sandisk ultra fit usb 3.0 drive and even after numerous attempts I am unable to get it to work. v19 was running fine off it.

On the first boot it ends up with the screen:

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built in commands.

(initramfs)

---

After which when I reboot, it goes straight to bios.

Tried this on a couple of different usb drives and the results are the same. Is there a specific setting that I'm missing here?

Thanks and advance

have you tried other usb or ssd ?
I think your usb has reached end of its life, get a 30$ SSD and save yourself.

I have. Not USB issue. Tried 3 different ones including two fresh new ones. All 3 works with v19 without issues. Wondering if anyone else is having the same issue.



May be the downloaded image has problem, download and flash again.

FFI2013
Hero Member
*****
Offline Offline

Activity: 892
Merit: 507



View Profile
November 25, 2017, 02:20:00 PM
 #5770

First let me say I think NVOC is awesome I've been running amd rx cards and win 10 pro on my rigs but after setting up this nvidia trial rig I'm hooked I just got two 1070's and a 1060 to see what cards I want to go with both my 1060 and 1070 are msi gaming cards and my other 1070 is a pny what would be the best over clocking setting for these I was thinking of using algo specific oc settings but would there be a problem with running the same clocks for 1060 and 1070 also in 1bash there's two different sets of algo specific oc's what is the difference one is halfway down and the other is at the bottom

My motherboard is asus M5A97 R2.0 with amd sempron 145 cpu don't know if you want to add it to supported hardware

Quote
  ,█████████████████████████████
  ]█████████████████████████████
  ]█████████████████████████████
  ]█████████████████████████████oooooo.
  ]████████                   ]████████
  ]████████                   ]████████
  ]████████                   ]████████
  ]████████ooooooo     ,ooooood█PPPPPPP
  ]███████████████     ]████████
  ]███████████████     ]████████
  ]███████████████_____J████████_______
  ]████████'''''7████████'''''7████████
  ]████████     ]████████     ]████████
  ]████████     ]████████     ]████████
  `PPPPPPY█oooood█PPPPPY█oooood█PPPPPPP
         ]████████     ]████████
         ]████████     ]████████
         ]████████     ]████████
          """"""Y████████""""""'
                ]████████
                ]████████
                `████████
BitValve
P2P crypto
exchange





THE MOST ADVANCED
P2P CRYPTO EXCHANGE
PLATFORM
      FOLLOW  US
.
.
















.TWITTER...............
.
.FACEBOOK..
O U R   S O L U T I O N
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
    We are building a platform for the
                Crypto Trading Industry
:   :   :   :   :   :   :   :   :   :   :
..JOIN ICO....WHITEPAPER..

UP TO 50% LESS FEES
MULTI CRYPTO. SUPPORT
CRYPTO TO CRYPTO TRADING
OFFICIAL MOBILE APPS
meligo
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
November 25, 2017, 02:41:54 PM
 #5771

fullzero and the gang - thanks for making this an easy distribution for mining. I have been using v19 for the past few months and have now attempted to move to 19-1.4.

Motherboard is an Asrock H110 BTC.

I've recently flashed v19-1.4 to my sandisk ultra fit usb 3.0 drive and even after numerous attempts I am unable to get it to work. v19 was running fine off it.

On the first boot it ends up with the screen:

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built in commands.

(initramfs)

---

After which when I reboot, it goes straight to bios.

Tried this on a couple of different usb drives and the results are the same. Is there a specific setting that I'm missing here?

Thanks and advance

hey , I have an Asrock H110 as well and with me it's working perfectly, have you tried with one 1 gpu in the slot closest to the CPU?
snhelix
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
November 25, 2017, 05:32:22 PM
 #5772


Hello everyone, and thank the authors of this mining os.
I'm new to using the system, but I've started everything right.Everything works nicely for 1-2 hours and then terminates the miners' work and I get this down report.

Please if anyone has a suggestion for repair.After restart all repeats in the circuit.

srry for my bad english Wink


nvOC_v0019-1.4
sudo: unable to resolve host 19_1_4


rig IP: 192.168.5.13


rig MAC: bc:5f:f4:0a:22:90 


01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)


Sat Nov 25 17:58:01 2017       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 387.12                 Driver Version: 387.12                    |
|-------------------------------+----------------------+----------------------+
| 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 106...  Off  | 00000000:01:00.0  On |                  N/A |
| 24%   34C    P0    28W / 120W |    175MiB /  6071MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 106...  Off  | 00000000:05:00.0 Off |                  N/A |
| 24%   28C    P8     5W / 120W |      9MiB /  6072MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 106...  Off  | 00000000:07:00.0 Off |                  N/A |
| 24%   29C    P8     5W / 120W |      9MiB /  6072MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 106...  Off  | 00000000:08:00.0 Off |                  N/A |
| 38%   30C    P8     5W / 120W |      9MiB /  6072MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      1065      G   /usr/lib/xorg/Xorg                           133MiB |
|    0      1823      G   compiz                                        39MiB |
|    1      1065      G   /usr/lib/xorg/Xorg                             6MiB |
|    2      1065      G   /usr/lib/xorg/Xorg                             6MiB |
|    3      1065      G   /usr/lib/xorg/Xorg                             6MiB |
+-----------------------------------------------------------------------------+

sudo: unable to resolve host 19_1_4
Power limit for GPU 00000000:01:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:05:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:07:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:08:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

All done.
sudo: unable to resolve host 19_1_4

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.
INFO:guake.guake_app:Logging configuration complete
/usr/lib/python2.7/dist-packages/guake/guake_app.py:1785: GtkWarning: gtk_box_pack: assertion 'child->parent == NULL' failed
  self.mainframe.pack_start(self.notebook, expand=True, fill=True, padding=0)

** (guake:2099): WARNING **: Binding 'F12' failed!
-h
--help

Stubo
Member
**
Offline Offline

Activity: 222
Merit: 13


View Profile
November 25, 2017, 05:47:10 PM
 #5773


Hello everyone, and thank the authors of this mining os.
I'm new to using the system, but I've started everything right.Everything works nicely for 1-2 hours and then terminates the miners' work and I get this down report.

Please if anyone has a suggestion for repair.After restart all repeats in the circuit.

srry for my bad english Wink


nvOC_v0019-1.4
sudo: unable to resolve host 19_1_4


rig IP: 192.168.5.13


rig MAC: bc:5f:f4:0a:22:90 


01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)


Sat Nov 25 17:58:01 2017       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 387.12                 Driver Version: 387.12                    |
|-------------------------------+----------------------+----------------------+
| 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 106...  Off  | 00000000:01:00.0  On |                  N/A |
| 24%   34C    P0    28W / 120W |    175MiB /  6071MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 106...  Off  | 00000000:05:00.0 Off |                  N/A |
| 24%   28C    P8     5W / 120W |      9MiB /  6072MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 106...  Off  | 00000000:07:00.0 Off |                  N/A |
| 24%   29C    P8     5W / 120W |      9MiB /  6072MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 106...  Off  | 00000000:08:00.0 Off |                  N/A |
| 38%   30C    P8     5W / 120W |      9MiB /  6072MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      1065      G   /usr/lib/xorg/Xorg                           133MiB |
|    0      1823      G   compiz                                        39MiB |
|    1      1065      G   /usr/lib/xorg/Xorg                             6MiB |
|    2      1065      G   /usr/lib/xorg/Xorg                             6MiB |
|    3      1065      G   /usr/lib/xorg/Xorg                             6MiB |
+-----------------------------------------------------------------------------+

sudo: unable to resolve host 19_1_4
Power limit for GPU 00000000:01:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:05:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:07:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:08:00.0 was set to 75.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

All done.
sudo: unable to resolve host 19_1_4

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(guake:2099): libglade-WARNING **: unknown attribute `swapped' for <signal>.
INFO:guake.guake_app:Logging configuration complete
/usr/lib/python2.7/dist-packages/guake/guake_app.py:1785: GtkWarning: gtk_box_pack: assertion 'child->parent == NULL' failed
  self.mainframe.pack_start(self.notebook, expand=True, fill=True, padding=0)

** (guake:2099): WARNING **: Binding 'F12' failed!
-h
--help



You can clean up the "unable to resolve host 19_1_4" errors by editing /etc/hostname and changing "19_1_4" to "m1-desktop", then reboot. I am not familiar with error "libglade-WARNING **: unknown attribute `swapped' for <signal>.". Please look in file /home/m1/screenlog.0 for miner errors at about the time it failed for additional clues on what is happening.

Hope this helps.
snhelix
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
November 25, 2017, 05:59:18 PM
 #5774

Okay, thank you for the answer, I'll try and inform.... Wink
papampi
Full Member
***
Offline Offline

Activity: 420
Merit: 119


Linux FOREVER! Resistance is futile!!!


View Profile
November 25, 2017, 06:34:31 PM
 #5775

Okay, thank you for the answer, I'll try and inform.... Wink

libglade-warning is guake error and has been solved with latest updates, weird its shows again
Does the error appear when guake terminal is open (f12) or it appears with it close too ?

May be try to do a package update upgrade
In an ssh session or terminal with ctrl+alt+f1 run :

Code:
pkill -f gnome-terminal
pkill -f DOG
pkill -f TEMP
pkill -e screen
sudo apt update && sudo apt upgrade

Then reboot the rig and see how it goes.
Be careful, nvidia just posted a new update, make sure miner and wdog are not running before start update/upgrade

6x1070ethsia
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
November 25, 2017, 06:45:53 PM
 #5776

Hi all.

 Totally new here,

I am currently running nvOC 0019 with 6x1070s mining eth / sia on an gigabyte H110-D3A

Everything works fine except my over clock settings appear to have no affect on hash rates, and I am pretty sure they are not even being applied.

Any ideas?
papampi
Full Member
***
Offline Offline

Activity: 420
Merit: 119


Linux FOREVER! Resistance is futile!!!


View Profile
November 25, 2017, 06:51:37 PM
 #5777

Hi all.

 Totally new here,

I am currently running nvOC 0019 with 6x1070s mining eth / sia on an gigabyte H110-D3A

Everything works fine except my over clock settings appear to have no affect on hash rates, and I am pretty sure they are not even being applied.

Any ideas?
I remember there was a bug in earlier versions
set the clocks and the power you want in the individual clock and power settings at the bottom of 1bash, I think it reads from the first one "gpu0"

6x1070ethsia
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
November 25, 2017, 06:57:38 PM
 #5778


[/quote]
I remember there was a bug in earlier versions
set the clocks and the power you want in the individual clock and power settings at the bottom of 1bash, I think it reads from the first one "gpu0"
[/quote]

I would enable "YES" for individual clock settings right?
jsenden
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
November 25, 2017, 07:46:15 PM
 #5779

Does this OS only work with these motherboards?

partially supported motherboard links:
ASUS B250 MINING EXPERT (13x gpu) Link

fully supported motherboard links:
ASRock H110 PRO BTC+ (13x gpu) Link
BIOSTAR TB250-BTC PRO (12x gpu) Link
ASRock H81 PRO BTC (6x gpu) Link
BIOSTAR TB85 (6x gpu) Link
MSI Z270-A PRO (6x gpu: 7x if you use 1x m2 adapter) Link
GIGABYTE GA-B250M-Gaming 3 (4x gpu) Link
BIOSTAR TB250-BTC (6x gpu) Link
ASUS Z270-F GAMING (7x gpu: 9x if you use 2x m2 adapters)  Link
MSI Z170A GAMING M5 (7x gpu) Link
ASUS PRIME Z270-A (7x gpu: 9x if you use 2x m2 adapters) Link
GIGABYTE GA-Z270P-D3 (6x gpu) Link
ASUS PRIME H270-PLUS (6x gpu: 8x if you use 2x m2 adapters) Link

Or will it also work for my mainboard (Gigabyte h110-d3a) ??

Stubo
Member
**
Offline Offline

Activity: 222
Merit: 13


View Profile
November 25, 2017, 08:07:05 PM
 #5780

Does this OS only work with these motherboards?

partially supported motherboard links:
ASUS B250 MINING EXPERT (13x gpu) Link

fully supported motherboard links:
ASRock H110 PRO BTC+ (13x gpu) Link
BIOSTAR TB250-BTC PRO (12x gpu) Link
ASRock H81 PRO BTC (6x gpu) Link
BIOSTAR TB85 (6x gpu) Link
MSI Z270-A PRO (6x gpu: 7x if you use 1x m2 adapter) Link
GIGABYTE GA-B250M-Gaming 3 (4x gpu) Link
BIOSTAR TB250-BTC (6x gpu) Link
ASUS Z270-F GAMING (7x gpu: 9x if you use 2x m2 adapters)  Link
MSI Z170A GAMING M5 (7x gpu) Link
ASUS PRIME Z270-A (7x gpu: 9x if you use 2x m2 adapters) Link
GIGABYTE GA-Z270P-D3 (6x gpu) Link
ASUS PRIME H270-PLUS (6x gpu: 8x if you use 2x m2 adapters) Link

Or will it also work for my mainboard (Gigabyte h110-d3a) ??

I believe those are just ones that folks have confirmed that it works on. I am reasonably certain that nvOC will work as long as the underlying Ubuntu installation works on your hardware. For example, I have 2 rigs that run an X99 based board that is not even on that list at all. Give it a go and if you have issues, post them here and we will try to resolve them with you.

Pages: « 1 ... 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 [289] 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 ... 418 »
  Print  
 
Jump to:  

Bitcointalk.org is not available or authorized for sale. Do not believe any fake listings.
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!