Search content
Sort by
Showing 20 of 50 results by lards
Hi guys,
Met a new problem lately with 1bash being unable to read or open with the error saying :
" Error reading lock file ./.1bash.swp: Not enough data read"
Has anybody seen this before and how to solve this? I don't want to reinstall the whole OS just because of 1bash isn't opening. The miner works fine and been on for over 10 days but I can't change any settings or anything due to this problem.
Met a new problem lately with 1bash being unable to read or open with the error saying :
" Error reading lock file ./.1bash.swp: Not enough data read"
Has anybody seen this before and how to solve this? I don't want to reinstall the whole OS just because of 1bash isn't opening. The miner works fine and been on for over 10 days but I can't change any settings or anything due to this problem.
Its usually a swp file created when editing with nano and stoped nano with ctrl-z instead of exiting
Remove the file with:
Code:
rm .1bash.swp
Thanks for your quick response but the command you gave doesn't do anything , I've tried the same with sudo and my file name but with no success.
Are there any alternative ways to solve this?
Please as user m1 do:
Code:
ls -al *bash
and paste output here.
Thx
m1@m1-desktop:~$ ls -al *bash
-rw-r--r-- 1 m1 m1 79986 Nov 13 17:03 1bash
This is what I get when using your command
Hi guys,
Met a new problem lately with 1bash being unable to read or open with the error saying :
" Error reading lock file ./.1bash.swp: Not enough data read"
Has anybody seen this before and how to solve this? I don't want to reinstall the whole OS just because of 1bash isn't opening. The miner works fine and been on for over 10 days but I can't change any settings or anything due to this problem.
Met a new problem lately with 1bash being unable to read or open with the error saying :
" Error reading lock file ./.1bash.swp: Not enough data read"
Has anybody seen this before and how to solve this? I don't want to reinstall the whole OS just because of 1bash isn't opening. The miner works fine and been on for over 10 days but I can't change any settings or anything due to this problem.
Its usually a swp file created when editing with nano and stoped nano with ctrl-z instead of exiting
Remove the file with:
Code:
rm .1bash.swp
Thanks for your quick response but the command you gave doesn't do anything , I've tried the same with sudo and my file name but with no success.
Are there any alternative ways to solve this?
Hi guys,
Met a new problem lately with 1bash being unable to read or open with the error saying :
" Error reading lock file ./.1bash.swp: Not enough data read"
Has anybody seen this before and how to solve this? I don't want to reinstall the whole OS just because of 1bash isn't opening. The miner works fine and been on for over 10 days but I can't change any settings or anything due to this problem.
Met a new problem lately with 1bash being unable to read or open with the error saying :
" Error reading lock file ./.1bash.swp: Not enough data read"
Has anybody seen this before and how to solve this? I don't want to reinstall the whole OS just because of 1bash isn't opening. The miner works fine and been on for over 10 days but I can't change any settings or anything due to this problem.
Hi everyone,
I still got this weird problem on both of my rigs : After around 24/48 hours the hashrate on one of the rigs drops about half of what it is supposed to be and then keeps working normally on the lower hashrate without restarting etc. I have tried applying higher PL or reducing OC settings but I still see this problem coming up all the time and have to reset the rig manually. I am using 12 and 13 P106-100 Cards on Asrock h110 pro btc one with 2 PSUs and one with just server PSU and on both rigs I get the same problem. I have tried turning on the WD but It sometimes doesn't reboot the system, does anyone know why the hashrate drops in half ?
Hope somebody can help me to find out the source of the problem since I have tried altering all the settings in the 1bash and still get the same results
I still got this weird problem on both of my rigs : After around 24/48 hours the hashrate on one of the rigs drops about half of what it is supposed to be and then keeps working normally on the lower hashrate without restarting etc. I have tried applying higher PL or reducing OC settings but I still see this problem coming up all the time and have to reset the rig manually. I am using 12 and 13 P106-100 Cards on Asrock h110 pro btc one with 2 PSUs and one with just server PSU and on both rigs I get the same problem. I have tried turning on the WD but It sometimes doesn't reboot the system, does anyone know why the hashrate drops in half ?
Hope somebody can help me to find out the source of the problem since I have tried altering all the settings in the 1bash and still get the same results
Hi everyone,
I still got this weird problem on both of my rigs : After around 24/48 hours the hashrate on one of the rigs drops about half of what it is supposed to be and then keeps working normally on the lower hashrate without restarting etc. I have tried applying higher PL or reducing OC settings but I still see this problem coming up all the time and have to reset the rig manually. I am using 12 and 13 P106-100 Cards on Asrock h110 pro btc one with 2 PSUs and one with just server PSU and on both rigs I get the same problem. Since I am in headless mode I cannot turn on the WD to restart the system,so has anybody experienced this kind of errors and how did you guys get rid of it?
Hope somebody can help me to find out the source of the problem since I have tried altering all the settings in the 1bash and still get the same results.
I still got this weird problem on both of my rigs : After around 24/48 hours the hashrate on one of the rigs drops about half of what it is supposed to be and then keeps working normally on the lower hashrate without restarting etc. I have tried applying higher PL or reducing OC settings but I still see this problem coming up all the time and have to reset the rig manually. I am using 12 and 13 P106-100 Cards on Asrock h110 pro btc one with 2 PSUs and one with just server PSU and on both rigs I get the same problem. Since I am in headless mode I cannot turn on the WD to restart the system,so has anybody experienced this kind of errors and how did you guys get rid of it?
Hope somebody can help me to find out the source of the problem since I have tried altering all the settings in the 1bash and still get the same results.
Finally updated to v0019 and went headless because v0012 crashed and somehow corrupted the USB.
I am running 12 ASUS P106 mining cards remotely since they have no video out. This free's up my MSI1060 so I can put it back in my gaming pc (yeay I can game again).
All cards set at 150/900 115w and temps set at 70. I tried higher over clocks even small ones and the miner was crashing.
Currently just running Ethminer
Miner has run flawlessly for 48 hours so far. Averaging 283MH/s on ETH
Mining nanopool asia1 and almost no stale solutions
I am pretty happy, tomorrow I will set up Telegram and set up Dual Mining and see what I get. I look forward to getting telegram working.
Big thanks to FullZero
I am running 12 ASUS P106 mining cards remotely since they have no video out. This free's up my MSI1060 so I can put it back in my gaming pc (yeay I can game again).
All cards set at 150/900 115w and temps set at 70. I tried higher over clocks even small ones and the miner was crashing.
Currently just running Ethminer
Miner has run flawlessly for 48 hours so far. Averaging 283MH/s on ETH
Mining nanopool asia1 and almost no stale solutions
I am pretty happy, tomorrow I will set up Telegram and set up Dual Mining and see what I get. I look forward to getting telegram working.
Big thanks to FullZero
Why you have such high PL? Try to negative clock the core and a bit more memory clock. I am running p106-100 cards on 90-95PL with -200cc and 1400MC , seems pretty stable to me. On 12 cards the same as yours I have around 300 Mh/s with those settings.
This is my first rig and I just went off what was suggested by someone way earlier in the forums for a gtx1060.
Also, I tried going with lower power with current OC settings and and my hash rate dropped to around 250.
I just updated 1bash with your recommendations and we will see what happens!
Thank you kindly
I just updated 1bash with your recommendations and ran into some issues.
First it crashed immediately after rebooting with the new 1bash. After it restarted it's self again it started mining and the cards do seem to be mining at about 299MH/s.
Issue: About every 3 to 4 rounds of work that comes in, the cards are only registering at about 48MH/s. I am wondering how that is going to effect my over all average hash rates. I am also confused as to why the rates would fluctuate so much.
I will let it go for 6 to 12 hours and see what happens but if someone has insight on that, it would be appreciated.
What do you mean by rounds? If you are talking about shown hashrate in the miner itself I had a weird issue when my hashrate dropped to about half of what I had. I increased the PL and changed the claymore version to 9.7 and I haven't seen such thing happen again.
Hope it helps!
Finally updated to v0019 and went headless because v0012 crashed and somehow corrupted the USB.
I am running 12 ASUS P106 mining cards remotely since they have no video out. This free's up my MSI1060 so I can put it back in my gaming pc (yeay I can game again).
All cards set at 150/900 115w and temps set at 70. I tried higher over clocks even small ones and the miner was crashing.
Currently just running Ethminer
Miner has run flawlessly for 48 hours so far. Averaging 283MH/s on ETH
Mining nanopool asia1 and almost no stale solutions
I am pretty happy, tomorrow I will set up Telegram and set up Dual Mining and see what I get. I look forward to getting telegram working.
Big thanks to FullZero
I am running 12 ASUS P106 mining cards remotely since they have no video out. This free's up my MSI1060 so I can put it back in my gaming pc (yeay I can game again).
All cards set at 150/900 115w and temps set at 70. I tried higher over clocks even small ones and the miner was crashing.
Currently just running Ethminer
Miner has run flawlessly for 48 hours so far. Averaging 283MH/s on ETH
Mining nanopool asia1 and almost no stale solutions
I am pretty happy, tomorrow I will set up Telegram and set up Dual Mining and see what I get. I look forward to getting telegram working.
Big thanks to FullZero
Why you have such high PL? Try to negative clock the core and a bit more memory clock. I am running p106-100 cards on 90-95PL with -200cc and 1400MC , seems pretty stable to me. On 12 cards the same as yours I have around 300 Mh/s with those settings.
Also, a second question.
How many risers is it safe to run off 1 strip of Sata plugs out of the psu? Ive seen youtube build videos where people say no more than 2... others say no more than 4?
How many risers is it safe to run off 1 strip of Sata plugs out of the psu? Ive seen youtube build videos where people say no more than 2... others say no more than 4?
I would say this depends on the risers and actual PSU used as well as the card plugged in the riser. What you can do is connect the sata to 6pin and run the rig for a couple of hours to see how hot the cable got over this time and then see for yourself how many can you put in. In my opinion those connectors just physically can't burn if they don't get warm over some time.
On the other side I would also recommend using a server PSU and not using 6pin to sata cables at all , this way you will get rid of another failure point.
I have recently built a new rig with 13 P106-100 ASUS cards on nv0019 running -200cc 1550mc and PL90. I have a weird problem that after some time the hashrate on all cards drop by 50% or more and doesn't go back up, the miner doesn't restart and it just keeps running with lower hashrate. This time it did this after 7 hours , with 7 cards running it was up for over 12hours and no problems. Has anyone experienced this before and maybe you know where the problem is?
How is the temperature of your cards? Have you configured nvOC to use auto temp control? If you have, it may be the case that you set the temp too low for what can be reached with 100% fan speed. In this case, auto temp control will smartly reduce the power limit to cool the cards, but of course this reduces the hash rate. Just a guess...
The highest temp I have on these cards is 61 degrees and fans are running no more than 67% so I doubt that these causes the problem. Unfortunately in P106-100 headless mode neither watchdog nor tempcontrol works so I do not use those.
Hi guys,
I have recently built a new rig with 13 P106-100 ASUS cards on nv0019 running -200cc 1550mc and PL90. I have a weird problem that after some time the hashrate on all cards drop by 50% or more and doesn't go back up, the miner doesn't restart and it just keeps running with lower hashrate. This time it did this after 7 hours , with 7 cards running it was up for over 12hours and no problems. Has anyone experienced this before and maybe you know where the problem is?
I am obviously running headless and using SSH to monitor the rig and adjust the settings.
PS. The miner or the OS doesn't restart the miner or reboot the system, just the hashrate drops pretty badly from 328 to 140 MH/s.
Thanks in advance to everyone who can help and also thanks to fullzero for the new version!
I have recently built a new rig with 13 P106-100 ASUS cards on nv0019 running -200cc 1550mc and PL90. I have a weird problem that after some time the hashrate on all cards drop by 50% or more and doesn't go back up, the miner doesn't restart and it just keeps running with lower hashrate. This time it did this after 7 hours , with 7 cards running it was up for over 12hours and no problems. Has anyone experienced this before and maybe you know where the problem is?
I am obviously running headless and using SSH to monitor the rig and adjust the settings.
PS. The miner or the OS doesn't restart the miner or reboot the system, just the hashrate drops pretty badly from 328 to 140 MH/s.
Thanks in advance to everyone who can help and also thanks to fullzero for the new version!
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
Hello everyone,
Has anybody had their hashrate go down on couple or all cards and then back up to normal? This happens to me pretty much with every second line which states hashrate. Reported hashrate on the pool itself changes also but around 3-7Mh/s . Can somebody advice on what the problem is? I am running 7 asus p106-100 cards atm on asrock h110 with claymore v10 mining etc. Using -200cc 1550mc and 90PL.
Thanks to everyone.
Has anybody had their hashrate go down on couple or all cards and then back up to normal? This happens to me pretty much with every second line which states hashrate. Reported hashrate on the pool itself changes also but around 3-7Mh/s . Can somebody advice on what the problem is? I am running 7 asus p106-100 cards atm on asrock h110 with claymore v10 mining etc. Using -200cc 1550mc and 90PL.
Thanks to everyone.
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
Hello everyone, is possible to setup the SMOS to dual mining ETH + DCR? I look at the Dashboard and don't see anything related to DCR.
Please see examples on specific miner page here:https://bitcointalk.org/index.php?topic=1433925.0
Tytanick can you please confirm if the new version works on P106-100 rig with applied OC and PL ? As some forum users said it works but others say it doesn't. Just to make it clear for everyone including myself.
Thanks in advance.
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
Hey guys,
I was wondering if anyone who uses SMOS on more than 10 P106-100 mining edition cards still experiences problems with OC and PL or did tytanick solved this issues? Also, do I still need to edit the system file to get the cards running from 2MH/s to their standard hashrate ( deleting the -allow-empty-configuration command) ?
Wanted to use the SMOS but since OC wasn't available there's not much point really.
Thanks in advance to everyone who can answer my question!
I currently running 3 P106 rig: 2x13gpu and 1x14gpu. I haven't experience any problem with OC so far, there is a new patch that fix the problem already you don't have to edit any system file.I was wondering if anyone who uses SMOS on more than 10 P106-100 mining edition cards still experiences problems with OC and PL or did tytanick solved this issues? Also, do I still need to edit the system file to get the cards running from 2MH/s to their standard hashrate ( deleting the -allow-empty-configuration command) ?
Wanted to use the SMOS but since OC wasn't available there's not much point really.
Thanks in advance to everyone who can answer my question!
Thanks for your answer I will try for myself soon when I get new hardware.
Btw what manufacturer do you have and what hashrate did you reach? Also, I guess the negative core overclock still doesn't apply in SMOS?
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
Hey guys,
I was wondering if anyone who uses SMOS on more than 10 P106-100 mining edition cards still experiences problems with OC and PL or did tytanick solved this issues? Also, do I still need to edit the system file to get the cards running from 2MH/s to their standard hashrate ( deleting the -allow-empty-configuration command) ?
Wanted to use the SMOS but since OC wasn't available there's not much point really.
Thanks in advance to everyone who can answer my question!
I was wondering if anyone who uses SMOS on more than 10 P106-100 mining edition cards still experiences problems with OC and PL or did tytanick solved this issues? Also, do I still need to edit the system file to get the cards running from 2MH/s to their standard hashrate ( deleting the -allow-empty-configuration command) ?
Wanted to use the SMOS but since OC wasn't available there's not much point really.
Thanks in advance to everyone who can answer my question!
Hi guys,
Did anyone had any problems with autoreboot when running headless rig? It seems like sometimes after autoreboot my rig doesn't want to start the miner and I have to manually reboot the rig for the miner to start and sometimes after autoreboot it starts the mining as expected.
Has anyone seen this before? If somebody knows the solution to this I would be verythankul.
Also fullzero you said that celeron isn't the best for 13x rig , what processor should be used for better stability and could it be the processor that causes this ?
Did anyone had any problems with autoreboot when running headless rig? It seems like sometimes after autoreboot my rig doesn't want to start the miner and I have to manually reboot the rig for the miner to start and sometimes after autoreboot it starts the mining as expected.
Has anyone seen this before? If somebody knows the solution to this I would be verythankul.
Also fullzero you said that celeron isn't the best for 13x rig , what processor should be used for better stability and could it be the processor that causes this ?
I recommend using a g4560 or better CPU; if you are using a celeron the CPU might be the problem.
So you think this problem with autoreboot might be due to the CPU? It's strange that sometimes it can reboot itself with no problem even 3 times in a row and sometimes it reboots but the miner doesn't start. I will get a new processor for my new rigs , but I don't really understand how this depends on the CPU since it happens in different times. Shouldn't this be happening everytime if the CPU isn't powerful enough ?
Can somebody with a full P106-100 rig confirm that v0019 works on your rig and OC values apply? I am away from my rig atm so can't test this myself .
Hi everyone again, can somebody confirm if nvOC v0019 works for all p106-100 rig without having 1 normal 1000x card? Does it still have to be headless or can we attach the monitor now? Since fullzero deleted the updated 1bash for this case I assume that it should be working with new version but in case I have to flash a new USB I just want to make sure that it's actually stable and OC is possible.
Thanks again for your work!
Thanks again for your work!
Hi guys,
Did anyone had any problems with autoreboot when running headless rig? It seems like sometimes after autoreboot my rig doesn't want to start the miner and I have to manually reboot the rig for the miner to start and sometimes after autoreboot it starts the mining as expected.
Has anyone seen this before? If somebody knows the solution to this I would be verythankul.
Also fullzero you said that celeron isn't the best for 13x rig , what processor should be used for better stability and could it be the processor that causes this ?
Did anyone had any problems with autoreboot when running headless rig? It seems like sometimes after autoreboot my rig doesn't want to start the miner and I have to manually reboot the rig for the miner to start and sometimes after autoreboot it starts the mining as expected.
Has anyone seen this before? If somebody knows the solution to this I would be verythankul.
Also fullzero you said that celeron isn't the best for 13x rig , what processor should be used for better stability and could it be the processor that causes this ?
I'll try the to use new 1bash if I get unstable results in the future since now I had the rig up for over 28 hours. Also does the autoreboot in the SSH only mode works as it supposed to?
Hey everyone.
As fullzero has already posted the instruction on OC of P106-100 rigs, I can confirm that this works and i am now using cc -200 and mc 1300(was stable for over 10 hours ) , I think it can go to 1400-1500 but I am in the process of testing the 12th card since it caused me issues everytime i connected before.
Also I have another question to ask fullzero : When I start the rig it sometimes doesn't swap the xorg files and giving me errors which lead to the OC being off(Sometimes even after autoreboot it doesn't autostart 1bash). This solves after a couple of reboots but I can't figure out how to reboot it so the OC will work and the miner also would start automatically since sometimes when I turn it on the miner doesn't autostart and this leads to further errors and no OC available. So far I haven't found any other problems so thank you again for solving OC issue.
Can you advise on what should I do in that case?
As fullzero has already posted the instruction on OC of P106-100 rigs, I can confirm that this works and i am now using cc -200 and mc 1300(was stable for over 10 hours ) , I think it can go to 1400-1500 but I am in the process of testing the 12th card since it caused me issues everytime i connected before.
Also I have another question to ask fullzero : When I start the rig it sometimes doesn't swap the xorg files and giving me errors which lead to the OC being off(Sometimes even after autoreboot it doesn't autostart 1bash). This solves after a couple of reboots but I can't figure out how to reboot it so the OC will work and the miner also would start automatically since sometimes when I turn it on the miner doesn't autostart and this leads to further errors and no OC available. So far I haven't found any other problems so thank you again for solving OC issue.
Can you advise on what should I do in that case?
When remoting in; it is important to realize that you can SSH in before all system init has occurred. Think of when you are watching nvOC load on a monitor. When Ubuntu is loading; there is a period where you cannot use the keyboard or mouse / guake has not started / 2unix (via gnome-terminal) hasn't launched. You can SSH in before this interval in system init. If you do, this act alone may change the init sequence, or it might only be launching bash earlier which may do this.
It could also be something else entirely; such as x intermittently launching or not launching which is causing the problem. This is the type of thing It will be much easier to isolate with my own p106-100 test rig.
For now I would try waiting longer after reboot before SSHing into the rig and seeing if that resolves the problem. Let me know how it goes.
I was trying to reboot away from the rig by turning on/off the power plug so I wasn't even connecting via SSH at all. Waited for over 15 minutes, no reported rate on pool made me think that it hasn't started so to turn it on I had to come to the home network of the rig but after another reboot it started fine with no errors after starting 1bash.
When 1bash is started automatically no errors appear at all and OC works fine but mostly it doesn't autostart and I have to use console to start it , it reports problems with replacing xorg + some other errors and OC doesn't work.
Maybe that info would help you to work out why does it do such thing.
Thanks for your reply.
In that case, it is probably x intermittently launching or not launching most likely do to modification of the xorg.conf. It is probably best to only conditionally change the xorg; but making / testing a configuration that works more smoothly will be much easier with my own p106-100 rig. I set the current p106-100 1bash to always modify the xorg.conf to avoid potential infinite boot loop problems vs only having a single boot that doesn't OC.
So what would you suggest to get rid of this problem? To reboot until the xorg and the miner start correctly or can I modify the 1bash somehow to make sure I don't have to reboot 5 times in a row to get it up and running?
Hey everyone.
As fullzero has already posted the instruction on OC of P106-100 rigs, I can confirm that this works and i am now using cc -200 and mc 1300(was stable for over 10 hours ) , I think it can go to 1400-1500 but I am in the process of testing the 12th card since it caused me issues everytime i connected before.
Also I have another question to ask fullzero : When I start the rig it sometimes doesn't swap the xorg files and giving me errors which lead to the OC being off(Sometimes even after autoreboot it doesn't autostart 1bash). This solves after a couple of reboots but I can't figure out how to reboot it so the OC will work and the miner also would start automatically since sometimes when I turn it on the miner doesn't autostart and this leads to further errors and no OC available. So far I haven't found any other problems so thank you again for solving OC issue.
Can you advise on what should I do in that case?
As fullzero has already posted the instruction on OC of P106-100 rigs, I can confirm that this works and i am now using cc -200 and mc 1300(was stable for over 10 hours ) , I think it can go to 1400-1500 but I am in the process of testing the 12th card since it caused me issues everytime i connected before.
Also I have another question to ask fullzero : When I start the rig it sometimes doesn't swap the xorg files and giving me errors which lead to the OC being off(Sometimes even after autoreboot it doesn't autostart 1bash). This solves after a couple of reboots but I can't figure out how to reboot it so the OC will work and the miner also would start automatically since sometimes when I turn it on the miner doesn't autostart and this leads to further errors and no OC available. So far I haven't found any other problems so thank you again for solving OC issue.
Can you advise on what should I do in that case?
When remoting in; it is important to realize that you can SSH in before all system init has occurred. Think of when you are watching nvOC load on a monitor. When Ubuntu is loading; there is a period where you cannot use the keyboard or mouse / guake has not started / 2unix (via gnome-terminal) hasn't launched. You can SSH in before this interval in system init. If you do, this act alone may change the init sequence, or it might only be launching bash earlier which may do this.
It could also be something else entirely; such as x intermittently launching or not launching which is causing the problem. This is the type of thing It will be much easier to isolate with my own p106-100 test rig.
For now I would try waiting longer after reboot before SSHing into the rig and seeing if that resolves the problem. Let me know how it goes.
I was trying to reboot away from the rig by turning on/off the power plug so I wasn't even connecting via SSH at all. Waited for over 15 minutes, no reported rate on pool made me think that it hasn't started so to turn it on I had to come to the home network of the rig but after another reboot it started fine with no errors after starting 1bash.
When 1bash is started automatically no errors appear at all and OC works fine but mostly it doesn't autostart and I have to use console to start it , it reports problems with replacing xorg + some other errors and OC doesn't work.
Maybe that info would help you to work out why does it do such thing.
Thanks for your reply.