NikoDE
Newbie
 Offline
Activity: 3
Merit: 0
|
 |
June 12, 2018, 07:13:01 PM |
|
Sorry, updated to latest commit but still: "invalid option -- 'i' "
And still ktccminer?
|
|
|
|
|
|
|
|
According to NIST and ECRYPT II, the cryptographic algorithms used in
Bitcoin are expected to be strong until at least 2030. (After that, it
will not be too difficult to transition to different algorithms.)
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
CryptAtomeTrader44
Full Member
Offline
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
|
|
June 12, 2018, 11:24:41 PM |
|
I'm actually using 19.2.1 beta testing version and i give my returns :90 1/ I think first step before launching is to update miners, all miners. But you can specifically update those you prefer/need to use. Yourt miner's update script is good and easy to use but it has some errors due to incomplete code in papampi's github repository. I opened your script and donwload manually each miners i need to launch and i saw they had only two files (version and ccminer) for some of them in his repository. @papampi : Why do you not use repositories of each miner's developpers on github ? Is there some problems to dowload them from nvOC ? Why not git command from their repositories directly to NVoc ?? I think you should force recompile all of the miners softwares for the first step. It's the best way to make some adaptated miners for each hardware configuration. Your miners update script is good and easy to use, but must be improved. it will be decisive for 19.2.1. It was the first problem i had with the testing version. 2/ You should define default intensity to 17, maximal intensity for Neoscrypt in using Klaust ccminer (KTccminer) I mine MONA and i saw immediatly the -i option empty made an invalid command to launch TPccminer for Lyra2REV2. I changed for NAccminer. But i had same problem. So i had to re-read you 1bash and 3main, and 0miner files to understand your unifications and modifications you made. I had some headacke after two month not reading code. But i succeded to undertsand after several re-readings ah ah  3/ I don't understand how you put power under 90w. Nvidia commands refuses to apply them under 90W for my 1060 and 1070. I think for the first launch, you should enter 90w for all power parameters in 1 bash, even ALGO SPECIFIC. Or, if you use a spécific command to launch theses less power instructions, it must be executed BEFORE, and we should not see theses warnings messages. 4/ Your WTM switcher is more complicated to set. I saw you launch it in a screen command to prevent your minning time errors that was problematic before. Good job ! Too bad that at the moment it is not too useful because of the bear market. I think i had to tame how to use it and set it correctly. 5/ I saw 2 new miners that i don't know if they have some best perrfomances : a) Bminer ? Which ALGO this miner is better to use ? b) ZENEMY ? Same Questions ? I noticed we can now using xmr-stak almost like all others miner's softwares. 6/ I 've not mined X16R ALGO yet, but if i look at WTM website, i'm not sure i will mine it. Furthermore, i'm suspicious about cryptobridge DEX "decentralazed exchange" that look me centralized on their website and servers and with a bitch of shitcoins. I use BarterDEX for now since 3 month, it's Ok, not perfect but i succeded 5 or 6 atomics swaps with HUSH/KMD...So, i think i will not use cryptopia stealers again. Furthermore, they recently published a better interface than barterDEX, called hyperDEX (not tested yet). 7/ I think, we could add all the coins permitted to mine with xmr-stak. I mined 2 XMR with 5x1060 + 5x1070 in less than two month on a small pool with less than 3 MH/s at the beginningg (april 14) and less than 2Mh/s after 15 days. Perhaps i will make some addintions propositions about that in nest weeks. Resume : 1/ Improve your miner's update script, and propose to launch it a the first boot to force reompiling all of them for each RIG. 2/ Add intensity to 17 by default for all miners (leave a comment beside as you did for overclocking settings) 3) How do you put power under 90 W ? 4/ WTM_SWITCHER is a good impovment that necessitate more gray matter from the miner to set it ! Ouchhhhh ! 5/ Bmine ? ZENEMYminer ? 6/ Is X16R is really profitable ? I doubt a lot... 7/ Adding some Cryptonight and cryptonight V7 added in xmr-stak miner ./xmr-stak_miner --help
Usage: xmr-stak_miner [OPTION]...
-h, --help show this help
-v, --version show version number
-V, --version-long show long version number
-c, --config FILE common miner configuration file
-C, --poolconf FILE pool configuration file
--benchmark BLOCKVERSION ONLY do a 60-second benchmark and exit
--noCPU disable the CPU miner backend
--cpu FILE CPU backend miner config file
--noAMD disable the AMD miner backend
--noAMDCache disable the AMD(OpenCL) cache for precompiled binar ies
--openCLVendor VENDOR use OpenCL driver of VENDOR and devices [AMD,NVIDIA ]
default: AMD
--amd FILE AMD backend miner config file
--noNVIDIA disable the NVIDIA miner backend
--nvidia FILE NVIDIA backend miner config file
-i --httpd HTTP_PORT HTTP interface port
The following options can be used for automatic start without a guided config,
If config exists then this pool will be top priority.
-o, --url URL pool url and port, e.g. pool.usxmrpool.com:3333
-O, --tls-url URL TLS pool url and port, e.g. pool.usxmrpool.com:1044 3
-u, --user USERNAME pool user name or wallet address
-r, --rigid RIGID rig identifier for pool-side statistics (needs pool support)
-p, --pass PASSWD pool password, in the most cases x or empty ""
--use-nicehash the pool should run in nicehash mode
--currency NAME currency to mine
Supported coin opitons:
- aeon7
- bbscoin
- croat
- cryptonight
- cryptonight_heavy
- cryptonight_lite
- cryptonight_lite_v7
- cryptonight_v7
- edollar
- electroneum
- graft
- haven
- intense
- karbo
- monero7
- stellite
- sumokoin
Version: xmr-stak 2.4.3 26a5d65f
Brought to by fireice_uk and psychocrypt under GPLv3.
Conclusion, i'm ready to test again when you will have revised theses 2 or three first point i post above. and you will able to make a new image after new testings. footnote : I don't used google translate, so sorry if my message is not esasy to read. And I do not have time to re-read Good job papampi. happy minning. Waiting for the next testing version. |
|
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
June 13, 2018, 08:18:19 AM |
|
Sorry, updated to latest commit but still: "invalid option -- 'i' "
And still ktccminer?
ETN was in CRYPTONIGHT algos, fixed and moved to CRYPTONIGHTV7 Please update and test again |
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
June 13, 2018, 08:37:48 AM |
|
1/ Improve your miner's update script, and propose to launch it a the first boot to force reompiling all of them for each RIG.
2/ Add intensity to 17 by default for all miners (leave a comment beside as you did for overclocking settings)
3) How do you put power under 90 W ?
4/ WTM_SWITCHER is a good impovment that necessitate more gray matter from the miner to set it ! Ouchhhhh !
5/ Bmine ? ZENEMYminer ?
6/ Is X16R is really profitable ? I doubt a lot...
7/ Adding some Cryptonight and cryptonight V7 added in xmr-stak miner
Thanks for the detailed review 1. Not a good idea to force re-compile all miners as it take long time, its best to let users decide. we made some changes though to just stop the running miner if it needed so there is much less time wasted when updating miners Miners source are already added and they get downloaded from source code if you go for recompile. 2. There is already a comment for intensity in 1bash, Will make a change for the error so it uses default values. # Test intensity on your rig and edit it or miner will set default values 3. I already set some cards to 75, no idea why you get into trouble setting that. Please post the warning messages you get. 4. Dont catch what you asked here 5. Bminer is new miner for ethahs and equihash, z-enemy is best for x16r 6. You know better 7. Fixed ETN and moved to V7 |
|
|
|
WaveFront
Member
Offline
Activity: 126
Merit: 10
|
|
June 13, 2018, 09:18:57 AM |
|
Hey :-)
What do you think is the ideal RAM size for a motherboard running nvOC?
Here is a look at how much it uses one one of my rigs with 7 1070's: m1@Miner1:~$ free
total used free shared buff/cache available
Mem: 8107204 1632364 5565128 42012 909712 6055112
As you can see, I have 8 Gb but it uses less than 2 in REMOTE (no local display). I tend to buy HW that I can re-purpose in the event that mining goes south, so I recommend running a single 8 Gb stick per mining host. I typically purchase them as a 16 Gb "kit" with 2 8 GB DIMMs. Clearly, you could go as low as 4 with no issues but I have no use for DIMMs that small outside of mining. Hi Stubo, Thanks for your answer. It's a good idea. the 16Gb kits can be cost competitive and easier to repurpose. Cheers Luca |
|
|
|
|
NikoDE
Newbie
Offline
Activity: 3
Merit: 0
|
|
June 13, 2018, 04:47:00 PM |
|
Sorry, updated to latest commit but still: "invalid option -- 'i' "
And still ktccminer?
ETN was in CRYPTONIGHT algos, fixed and moved to CRYPTONIGHTV7 Please update and test again OK one step further ☺, Now it starts xmr-stak, unfortunately it doesn't come far... : no config.txt found in home/m1 Also it seems like there is much less content inside the xmr-stak folder of 19.2.1 than it was in xmr of 19.2.0. Looks like there is a lot work to do- don't stress👍 |
|
|
|
|
CryptAtomeTrader44
Full Member
Offline
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
|
|
June 13, 2018, 10:44:37 PM |
|
1/ Improve your miner's update script, and propose to launch it a the first boot to force reompiling all of them for each RIG.
2/ Add intensity to 17 by default for all miners (leave a comment beside as you did for overclocking settings)
3) How do you put power under 90 W ?
4/ WTM_SWITCHER is a good impovment that necessitate more gray matter from the miner to set it ! Ouchhhhh !
5/ Bmine ? ZENEMYminer ?
6/ Is X16R is really profitable ? I doubt a lot...
7/ Adding some Cryptonight and cryptonight V7 added in xmr-stak miner
Thanks for the detailed review 1.
Not a good idea to force re-compile all miners as it take long time, its best to let users decide.
we made some changes though to just stop the running miner if it needed so there is much less time wasted when updating miners
Miners source are already added and they get downloaded from source code if you go for recompile.
- Perhaps not all miners need to be re-compiled, but i can affirm you that when i launch you miner script update thaht i used from your Wiki page, i was having 3 miners of 4 don't started anything. - I opened your script and i saw thaht you donwload some miners from YOUR github. YOUR repository don't contain all sources files, only 2 files. I manually download miners thaht cause me loops in 3main. I have no reasons to tell you a different reality that i had when i follow your Wiki page on github. 2.
There is already a comment for intensity in 1bash, Will make a change for the error so it uses default values.
# Test intensity on your rig and edit it or miner will set default values
- Ok, i had'nt saw this comment line. But i can affirm you that TPccminer don't apply default value and it don't start at my first boot. perhaps because it needs to be re-compiled ! All started correctly after re-compliling some miners. It was effectively very long time to re-compile all. I also updated xmr-stak with their last github code. 3.
I already set some cards to 75, no idea why you get into trouble setting that.
Please post the warning messages you get.
Ok, i will post this message when i was having more time. 4.
Dont catch what you asked here
Is it possible to make graphcet diagram to be more understanding for a newbie user ? Your explantation comments helps so much but i think it's not an easy to use profit switcher for a beginner. Perhaps a simple minimalist diagram could helps. That's just i wanted to tell at this point. 5.
Bminer is new miner for ethahs and equihash, z-enemy is best for x16r
Is Bminer better than Claymore and DSTM ? More stable ? More efficency ? Less fees ? 6.
You know better
I'm not sure what you mean. NO, i don't know anything about this algo. I read a little on discord but it was more than 2 month ... 7.
Fixed ETN and moved to V7
In fact, i was thinking about a profit Switcher on all Cryptonight algo and coins proposed by this miner I discovered a new bug : In 1bash, at the end of file : Replace NICE- to NICE_
## IDENTIFY MINING ALGORITHM START
if [[ $COIN == FTC || $COIN == ORB || $COIN == PXC || $COIN == VIVO || $COIN == TZC || $COIN == NICE-NEOSCRYPT || $COIN == DSR || $COIN == CRC || $COIN == GBX || $COIN == MPH_NEOSCRYPT || $COIN == ZPOOL_NEOSCRYPT ]]
then
ALGO=NEOSCRYPT
elif [[ $COIN == ETH || $COIN == ETC || $COIN == EXP || $COIN == UBQ || $COIN == CLO || $COIN == MUSIC || $COIN == SOIL || $COIN == MPH_ETHASH || $COIN == PIRL || $COIN == NICE-ETHASH || $COIN == ETP ]]
then
ALGO=ETHASH
elif [[ $COIN == BTG || $COIN == ZEC || $COIN == ZEN || $COIN == HUSH || $COIN == ZCL || $COIN == BTCP || $COIN == KMD || $COIN == ZPOOL_EQUIHASH || $COIN == MPH_EQUIHASH || $COIN == NICE-EQUIHASH || $COIN == VOTE || $COIN == BTCP || $COIN == BCI ]]
then
ALGO=EQUIHASH
elif [[ $COIN == SIGT || $COIN == ZPOOL_SKUNK || $COIN == ALTCOM || $COIN == NICE-SKUNKHASH ]]
then
ALGO=SKUNK
elif [[ $COIN == MONA || $COIN == VTC || $COIN == NICE-LYRA2REV2 || $COIN == XVG || $COIN == MPH_LYRA2V2 || $COIN == ZPOOL_LYRA2V2 ]]
then
ALGO=LYRA2V2
elif [[ $COIN == KRB || $COIN == ETN || $COIN == NICE-CRYPTONIGHT ]]
then
ALGO=CRYPTONIGHT
elif [[ $COIN == ZCOIN || $COIN == MPH_LYRA2Z ]]
then
ALGO=LYRA2Z
elif [[ $COIN == BSD ]]
then
ALGO=XEVAN
elif [[ $COIN == RVN ]]
then
ALGO=X16R
elif [[ $COIN == BTX ]]
then
ALGO=BITCORE
elif [[ $COIN == SIB || $COIN == NICE-X11GHOST ]]
then
ALGO=SIB
elif [[ $COIN == MONERO || $COIN == MPH_CRYPTONIGHTV7 ]]
then
ALGO=CRYPTONIGHTV7
elif [[ $COIN == XMR || $COIN == LUX || $COIN == FLM ]]
then
ALGO=PHI
elif [[ $COIN == PASC || $COIN == PASL ]]
then
ALGO=PASCAL
elif [[ $COIN == LBC || $COIN == ZPOOL_LBRY ]]
then
ALGO=LBRY
elif [[ $COIN == DMD ]]
then
ALGO=DMD-GR
elif [[ $COIN == GRS || $COIN == MPH_GRS ]]
then
ALGO=GRS
elif [[ $COIN == XMY ]]
then
ALGO=MYR-GR
elif [[ $COIN == DCR || $COIN == MPH_MYR-GR ]]
then
ALGO=DECRED
elif [[ $COIN == SIA ]]
then
ALGO=SIA
elif [[ $COIN == ONION ]]
then
ALGO=X13
elif [[ $COIN == ZPOOL_SKEIN || $COIN == MPH_SKEIN ]]
then
ALGO=SKEIN
else
ALGO=UNDEFINED
fi
export ALGO
## IDENTIFY ALGORITHM END
Today i tried to use NICE_ETHASH, NICE_NEOSCRYPT and NICE_EQUIHASH in WTM_SWITCHER and it seems thaht NICE_ETHASH is not functionnal. i saw Error blobxxx with claymore. I don't tried Bminer yet for ETHASH ALGO...No PB with 2 others nicehash algo switch When do you plan to provide a new ISO file ? How much time testing ? |
|
|
|
|
CryptAtomeTrader44
Full Member
Offline
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
|
|
June 13, 2018, 10:55:45 PM |
|
I have some erros With Bminer: INFO] [2018-06-14T00:51:39+02:00] Bminer: When Crypto-mining Made Fast (v8.0.0-32928c5)
[INFO] [2018-06-14T00:51:39+02:00] Checking updates
[INFO] [2018-06-14T00:51:40+02:00] Watchdog has started.
[INFO] [2018-06-14T00:51:40+02:00] Starting miner on devices [0 1 2 3 4 5 6 7 8]
[INFO] [2018-06-14T00:51:40+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:51:40+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:51:41+02:00] Starting miner on device 0...
[INFO] [2018-06-14T00:51:41+02:00] Started miner on device 0
[INFO] [2018-06-14T00:51:41+02:00] Starting miner on device 1...
[INFO] [2018-06-14T00:51:42+02:00] Started miner on device 1
[INFO] [2018-06-14T00:51:42+02:00] Starting miner on device 2...
[INFO] [2018-06-14T00:51:42+02:00] Started miner on device 2
[INFO] [2018-06-14T00:51:43+02:00] Starting miner on device 3...
[INFO] [2018-06-14T00:51:43+02:00] Started miner on device 3
[INFO] [2018-06-14T00:51:44+02:00] Starting miner on device 4...
[INFO] [2018-06-14T00:51:44+02:00] Started miner on device 4
[INFO] [2018-06-14T00:51:44+02:00] Starting miner on device 5...
[INFO] [2018-06-14T00:51:45+02:00] Started miner on device 5
[INFO] [2018-06-14T00:51:45+02:00] Starting miner on device 6...
[INFO] [2018-06-14T00:51:45+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:51:45+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:51:45+02:00] Started miner on device 6
[INFO] [2018-06-14T00:51:46+02:00] Starting miner on device 7...
[INFO] [2018-06-14T00:51:46+02:00] Started miner on device 7
[INFO] [2018-06-14T00:51:47+02:00] Starting miner on device 8...
[INFO] [2018-06-14T00:51:47+02:00] Started miner on device 8
[INFO] [2018-06-14T00:51:50+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:51:50+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:51:55+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:51:55+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:01+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:01+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:06+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:06+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:11+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:11+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:11+02:00] [GPU 0] Speed: 443.81 Sol/s 241.78 Nonce/s Temp: 46C Fan: 55% Power: 110W 4.03 Sol/J
[INFO] [2018-06-14T00:52:12+02:00] [GPU 1] Speed: 352.93 Sol/s 185.47 Nonce/s Temp: 58C Fan: 55% Power: 109W 3.24 Sol/J
[INFO] [2018-06-14T00:52:12+02:00] [GPU 2] Speed: 358.73 Sol/s 188.78 Nonce/s Temp: 49C Fan: 55% Power: 110W 3.26 Sol/J
[INFO] [2018-06-14T00:52:13+02:00] [GPU 3] Speed: 429.11 Sol/s 235.15 Nonce/s Temp: 55C Fan: 55% Power: 103W 4.17 Sol/J
[INFO] [2018-06-14T00:52:14+02:00] [GPU 4] Speed: 434.70 Sol/s 225.22 Nonce/s Temp: 45C Fan: 55% Power: 101W 4.30 Sol/J
[INFO] [2018-06-14T00:52:15+02:00] [GPU 5] Speed: 443.81 Sol/s 241.78 Nonce/s Temp: 46C Fan: 55% Power: 110W 4.03 Sol/J
[INFO] [2018-06-14T00:52:15+02:00] [GPU 6] Speed: 348.59 Sol/s 185.47 Nonce/s Temp: 50C Fan: 55% Power: 42W 8.30 Sol/J
[INFO] [2018-06-14T00:52:16+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:16+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:16+02:00] [GPU 7] Speed: 344.86 Sol/s 188.78 Nonce/s Temp: 57C Fan: 55% Power: 108W 3.19 Sol/J
[INFO] [2018-06-14T00:52:17+02:00] [GPU 8] Speed: 411.52 Sol/s 221.90 Nonce/s Temp: 46C Fan: 55% Power: 99W 4.16 Sol/J
[INFO] [2018-06-14T00:52:21+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:21+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:26+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:26+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:31+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:31+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:36+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:36+02:00] Get error: End of file, resetting in 5 seconds
I just changed ETHASH_MINER="CLAYMORE" to ETHASH_MINER="BMINER" What's the problem ? It looks OK for Bminer minning EQUIHASH. Even, the first start on ZCL had the same problem than above with ETHASH |
|
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
June 14, 2018, 05:22:27 AM
Last edit: June 14, 2018, 09:52:57 AM by papampi |
|
Sorry, updated to latest commit but still: "invalid option -- 'i' "
And still ktccminer?
ETN was in CRYPTONIGHT algos, fixed and moved to CRYPTONIGHTV7 Please update and test again OK one step further ☺, Now it starts xmr-stak, unfortunately it doesn't come far... : no config.txt found in home/m1 Also it seems like there is much less content inside the xmr-stak folder of 19.2.1 than it was in xmr of 19.2.0. Looks like there is a lot work to do- don't stress👍 config.txt should be created in first run by xmr-stak miner, ignore that error on first run. |
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
June 14, 2018, 05:28:56 AM
Last edit: June 14, 2018, 09:27:27 PM by papampi |
|
I have some erros With Bminer: INFO] [2018-06-14T00:51:39+02:00] Bminer: When Crypto-mining Made Fast (v8.0.0-32928c5)
[INFO] [2018-06-14T00:51:39+02:00] Checking updates
[INFO] [2018-06-14T00:51:40+02:00] Watchdog has started.
[INFO] [2018-06-14T00:51:40+02:00] Starting miner on devices [0 1 2 3 4 5 6 7 8]
[INFO] [2018-06-14T00:51:40+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:51:40+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:51:41+02:00] Starting miner on device 0...
[INFO] [2018-06-14T00:51:41+02:00] Started miner on device 0
[INFO] [2018-06-14T00:51:41+02:00] Starting miner on device 1...
[INFO] [2018-06-14T00:51:42+02:00] Started miner on device 1
[INFO] [2018-06-14T00:51:42+02:00] Starting miner on device 2...
[INFO] [2018-06-14T00:51:42+02:00] Started miner on device 2
[INFO] [2018-06-14T00:51:43+02:00] Starting miner on device 3...
[INFO] [2018-06-14T00:51:43+02:00] Started miner on device 3
[INFO] [2018-06-14T00:51:44+02:00] Starting miner on device 4...
[INFO] [2018-06-14T00:51:44+02:00] Started miner on device 4
[INFO] [2018-06-14T00:51:44+02:00] Starting miner on device 5...
[INFO] [2018-06-14T00:51:45+02:00] Started miner on device 5
[INFO] [2018-06-14T00:51:45+02:00] Starting miner on device 6...
[INFO] [2018-06-14T00:51:45+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:51:45+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:51:45+02:00] Started miner on device 6
[INFO] [2018-06-14T00:51:46+02:00] Starting miner on device 7...
[INFO] [2018-06-14T00:51:46+02:00] Started miner on device 7
[INFO] [2018-06-14T00:51:47+02:00] Starting miner on device 8...
[INFO] [2018-06-14T00:51:47+02:00] Started miner on device 8
[INFO] [2018-06-14T00:51:50+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:51:50+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:51:55+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:51:55+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:01+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:01+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:06+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:06+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:11+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:11+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:11+02:00] [GPU 0] Speed: 443.81 Sol/s 241.78 Nonce/s Temp: 46C Fan: 55% Power: 110W 4.03 Sol/J
[INFO] [2018-06-14T00:52:12+02:00] [GPU 1] Speed: 352.93 Sol/s 185.47 Nonce/s Temp: 58C Fan: 55% Power: 109W 3.24 Sol/J
[INFO] [2018-06-14T00:52:12+02:00] [GPU 2] Speed: 358.73 Sol/s 188.78 Nonce/s Temp: 49C Fan: 55% Power: 110W 3.26 Sol/J
[INFO] [2018-06-14T00:52:13+02:00] [GPU 3] Speed: 429.11 Sol/s 235.15 Nonce/s Temp: 55C Fan: 55% Power: 103W 4.17 Sol/J
[INFO] [2018-06-14T00:52:14+02:00] [GPU 4] Speed: 434.70 Sol/s 225.22 Nonce/s Temp: 45C Fan: 55% Power: 101W 4.30 Sol/J
[INFO] [2018-06-14T00:52:15+02:00] [GPU 5] Speed: 443.81 Sol/s 241.78 Nonce/s Temp: 46C Fan: 55% Power: 110W 4.03 Sol/J
[INFO] [2018-06-14T00:52:15+02:00] [GPU 6] Speed: 348.59 Sol/s 185.47 Nonce/s Temp: 50C Fan: 55% Power: 42W 8.30 Sol/J
[INFO] [2018-06-14T00:52:16+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:16+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:16+02:00] [GPU 7] Speed: 344.86 Sol/s 188.78 Nonce/s Temp: 57C Fan: 55% Power: 108W 3.19 Sol/J
[INFO] [2018-06-14T00:52:17+02:00] [GPU 8] Speed: 411.52 Sol/s 221.90 Nonce/s Temp: 46C Fan: 55% Power: 99W 4.16 Sol/J
[INFO] [2018-06-14T00:52:21+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:21+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:26+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:26+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:31+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:31+02:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-06-14T00:52:36+02:00] Connected to europe.ethash-hub.miningpoolhub.com:20535
[WARN] [2018-06-14T00:52:36+02:00] Get error: End of file, resetting in 5 seconds
I just changed ETHASH_MINER="CLAYMORE" to ETHASH_MINER="BMINER" What's the problem ? It looks OK for Bminer minning EQUIHASH. Even, the first start on ZCL had the same problem than above with ETHASH No idea, ask in bminer thread. But something strange, why it shows eth hashrate as sols/s? We talked and tested NICE_ in GitHub issue 88Please post problems with nice in GitHub so we can follow and fix (if there are any) Edit: Did you set correct bminer protocol for ethereum in 1bash? |
|
|
|
LuKePicci
Jr. Member
Offline
Activity: 128
Merit: 1
|
|
June 15, 2018, 10:31:17 AM |
|
When do you plan to provide a new ISO file ? How much time testing ?
Thank you for all your feedbacks, please test again the miners update procedure, we did some chenges recently, in case of any issue with the testing version please report on github, to avoid confusing people here. As you see lot of things changed, and the testing stage is just at the beginning. The more people test the new beta version, the more we feel confident in declaring it as ready. Please remember to always attach a report anytime you report issues because the report contains version info needed to understand which test version you are running at that time. |
|
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
June 20, 2018, 06:39:24 AM
Last edit: June 20, 2018, 08:08:18 AM by papampi |
|
nvOC 19-2.1 beta image, Ubuntu 16.04, Nvidia 390, Date 180619 Thanks to all contributors. This is a beta image and not fully tested yet. Please post bugs, errors,questions and any problems here in forum or GitHub issues. nvOC_V19-2.1beta_U16.04_N390_D180619.img sha256: cb607c8e028d3bc0a0e274c34b4e0def0c71330053f0c8328120a717e0029938 nvOC_V19-2.1beta_U16.04_N390_D180619.img.zip sha256: 7700dfdfc1cabab8a1dd9816a6322d6653c89943cb63afa59e79f88cfe14a6a9 Zip download size 3.6 Gb, Image size 9 Gb Auto expand to fill all the volume at first boot. Download link
Write the image with your favourite image writer of choice Browse to the small fat partition you can see on the drive, edit 1bash. Auto start miner is set to no, change it when you are sure all settings are correct. Attach the SSD/USB/HDD to rig and boot up. USB install not recommended for mining, only use it for testing. Good luck. Keep calm and carry on mining. |
|
|
|
CryptAtomeTrader44
Full Member
Offline
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
|
|
June 22, 2018, 11:47:53 PM |
|
I just changed ETHASH_MINER="CLAYMORE" to ETHASH_MINER="BMINER"
What's the problem ?
It looks OK for Bminer minning EQUIHASH. Even, the first start on ZCL had the same problem than above with ETHASH
No idea, ask in bminer thread. But something strange, why it shows eth hashrate as sols/s? We talked and tested NICE_ in GitHub issue 88Please post problems with nice in GitHub so we can follow and fix (if there are any) Edit: Did you set correct bminer protocol for ethereum in 1bash? You were right for the definition of the BMINER protocol. I defined ethstratum and everything is back in order, including for ETC which has made a nice comeback in the WTM rankings and the markets in recent days. On the other hand, I did not understand how to make Claymore fight the minning switching between ETH (on MPH) and NICE_ETHASH (On Nicehash). I systematically have this blob3 error. and I think it comes from these prameters prese, born on their support web page "EthDcrMiner64.exe -epool stratum + tcp: //daggerhashimoto.eu.nicehash.com: 3353 -ewal YOUR_BTC_ADDRESS -epsw x-esm 3 -allpools 1" To min out ETh on MPH, the -esm option is 2 and not 3. I note that Bminer does not seem to be affected by this option but that the software is only planting every 3-5 minutes on nice_ethash. I have not yet understood if I can and / or should use the specificity of BMINER and the pill enlargment. But after a few days of minning, if what is displayed by Bminer is accurate in terms of hashing speed, then it is as fast as claymore and slightly more stable. EDIT : minerinfo is dead and i don't understand whey or how to relaunch it. minerinfo seems to be dysfunctional and I can not consult anything locally :-( translated by google translate Report generator v0019-2.0.002 by leenoox
Software info:
Report ver : v0019-2.0.002
nvOC (1bash) : nvOC v0019-2.1 - Community Release
nvOC (3main) : nvOC v0019-2.1 - Community Release
1bash ver : v0019-2.1.0026
3main ver : v0019-2.1.0021
5watchdog ver : v0019-2.0.018
6tempcontrol v: v0019-2.1.0006
wtm switch ver: v0019-2.0.0021
Kernel : 4.4.0-97-generic
OS : Ubuntu 16.04.3 LTS
System : (gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
nvidia driver : 387.34
Hardware info:
Motherboard : BIOSTAR Group TB250-BTC PRO
BIOS ver. : 5.12 06/07/2017
CPU Model : Celeron(R) CPU G3900 @ 2.80GHz
CPU Cores : 2 (Cores + Threads)
Mem Total : 4011968 kB
Mem Free : 759176 kB
Swap Total : 4194300 kB
Swap Free : 4194300 kB
Ethernet : Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
HDD and Partion info:
NAME SIZE FSTYPE TYPE ROTA HOTPLUG TRAN VENDOR MODEL REV MOUNTPOINT
sda 186.3G disk 1 1 usb ATA Hitachi H C54P
├─sda1 9M vfat part 1 1 /media/m1/12D
├─sda2 20G ext4 part 1 1 /
└─sda3 4G swap part 1 1 [SWAP]
VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0b:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
1bash settings:
1bash version .............: v0019-2.1.0026
LOCAL or REMOTE ...........: LOCAL
TEAMVIEWER started ........: NO
SSH daemon started ........: YES
SLOW_USB_KEY_MODE .........: NO
SRR .......................: NO
Watchdog ..................: YES
SYSRQ Reboot ..............: YES
Watchdog Cycle ............: 15
GPU Utilization Threshold .: 70
Alternate Pool ............: NO
Temp Control ..............: YES
MANUAL_FAN ................: NO
TARGET_TEMP ...............: 70
__FAN_ADJUST ..............: 3
POWER_ADJUST ..............: 3
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 85
MINIMAL_FAN_SPEED .........: 55
MAXIMAL_FAN_SPEED .........: 100
CLEAR_LOGS_ON_BOOT ........: NO
AUTO_UPDATE ...............: STABLE
AUTO_REBOOT ...............: NO
_Parallax_MODE (upPaste)...: NO
TELEGRAM_MESSAGES .: YES
TELEGRAM_ALERTS ...: YES
TELEGRAM_TYPE .............: papampi
TELEGRAM_TIMEOUT_IN_MINUTES: 60
TELEGRAM_CHATID ...........: CHATID_NOT_SHOWN
TELEGRAM_APIKEY ...........: APIKEY_NOT_SHOWN
HEADLESS MODE:.............: NO
GPUPowerMizerMode_Adjust...: NO
ETH Pill ..................: NO
POWERLIMIT MODE ...........: GPU_SPECIFIC
GPU0 Power Limit ..........: 112
GPU1 Power Limit ..........: 114
GPU2 Power Limit ..........: 114
GPU3 Power Limit ..........: 114
GPU4 Power Limit ..........: 114
GPU5 Power Limit ..........: 114
GPU6 Power Limit ..........: 100
GPU7 Power Limit ..........: 114
GPU8 Power Limit ..........: 114
GPU9 Power Limit ..........: 114
OVERCLOCK MODE ............: GPU_SPECIFIC
GPU0 Core Overclock ........: 106
GPU0 Memory Overclock ......: 1200
GPU1 Core Overclock ........: 106
GPU1 Memory Overclock ......: 1100
GPU2 Core Overclock ........: 106
GPU2 Memory Overclock ......: 1100
GPU3 Core Overclock ........: 106
GPU3 Memory Overclock ......: 1100
GPU4 Core Overclock ........: 106
GPU4 Memory Overclock ......: 1100
GPU5 Core Overclock ........: 106
GPU5 Memory Overclock ......: 1100
GPU6 Core Overclock ........: 106
GPU6 Memory Overclock ......: 1100
GPU7 Core Overclock ........: 106
GPU7 Memory Overclock ......: 1200
GPU8 Core Overclock ........: 106
GPU8 Memory Overclock ......: 1200
GPU9 Core Overclock ........: 106
GPU9 Memory Overclock ......: 1300
GLOBAL WORKERNAME .........: YES
AUTO WORKERNAME ...........: CUSTOM
WORKERNAME ................: MINER44
plusCPU ...................: NO
COIN ......................: NICE_ETHASH
ALGO ......................: ETHASH
MINER .....................: BMINER
NICE_ETHASH WORKER ................: MINER44
NICE_ETHASH ADDRESS ...............: ...
NICE_ETHASH POOL ..................: daggerhashimoto.usa.nicehash.com
NICE_ETHASH PORT ..................: 3353
ETHASH INTENSITY ..........:
|
|
|
|
|
CryptAtomeTrader44
Full Member
Offline
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
|
|
June 23, 2018, 12:00:46 AM |
|
I'm trying desperately to connect my vnc to my local minor but nothing to do, ulraVNC told me that the protocol is not supported and other software tell me that the connection is refused!
I stopped teamviwer because he asked me to buy a professional license. Note that their site shows that they determine themselves whether it is a pro or personal use ... So, they only decide whether the user cheats or not. Here's a method to sneak up on it, a little more money when shareholders claim additional turnover (and the dividends that come with it). Not really reasonable all that.
I will try on the new version tomorrow.
translated by google translate
|
|
|
|
|
CryptAtomeTrader44
Full Member
Offline
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
|
|
June 23, 2018, 12:28:21 AM |
|
When do you plan to provide a new ISO file ? How much time testing ?
Thank you for all your feedbacks, please test again the miners update procedure, we did some chenges recently, in case of any issue with the testing version please report on github, to avoid confusing people here. As you see lot of things changed, and the testing stage is just at the beginning. The more people test the new beta version, the more we feel confident in declaring it as ready. Please remember to always attach a report anytime you report issues because the report contains version info needed to understand which test version you are running at that time. A few pages ago, we had discussed updating to a newer version of ubuntu that was to be released last spring. What about these projects? As I wrote, I think Xubuntu could do the trick and be a little lighter. I know that leenoox also wanted to propose many other systems even more minimalist but I do not know if he finally gave up his idea to lighten the image of nvOC. You can see my miner report in a recent message above. translated by google translate |
|
|
|
|
CryptAtomeTrader44
Full Member
Offline
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
|
|
June 23, 2018, 12:35:53 AM |
|
nvOC 19-2.1 beta image, Ubuntu 16.04, Nvidia 390, Date 180619 Thanks to all contributors. This is a beta image and not fully tested yet. Please post bugs, errors,questions and any problems here in forum or GitHub issues. nvOC_V19-2.1beta_U16.04_N390_D180619.img sha256: cb607c8e028d3bc0a0e274c34b4e0def0c71330053f0c8328120a717e0029938 nvOC_V19-2.1beta_U16.04_N390_D180619.img.zip sha256: 7700dfdfc1cabab8a1dd9816a6322d6653c89943cb63afa59e79f88cfe14a6a9 Zip download size 3.6 Gb, Image size 9 Gb Auto expand to fill all the volume at first boot. Download link
Write the image with your favourite image writer of choice Browse to the small fat partition you can see on the drive, edit 1bash. Auto start miner is set to no, change it when you are sure all settings are correct. Attach the SSD/USB/HDD to rig and boot up. USB install not recommended for mining, only use it for testing. Good luck. Keep calm and carry on mining. I'm downloading it now. I will install tomorrow in place of 19.2.0 with another terminal profile that i'm actually using. Well, but if not, when will donald.T stop tweeting his bullshit and make big falls in the crytpo market  grrrrrrrrr Quickly, quickly, find a clever little who "hack" his twitter account and make him say anything! Arf, no, on the contrary make him say something intelligent, otherwise no one will notice ah ah ah pfffffff It pisses us all well translated by google translate |
|
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
June 23, 2018, 06:29:15 AM |
|
I just changed ETHASH_MINER="CLAYMORE" to ETHASH_MINER="BMINER"
What's the problem ?
It looks OK for Bminer minning EQUIHASH. Even, the first start on ZCL had the same problem than above with ETHASH
No idea, ask in bminer thread. But something strange, why it shows eth hashrate as sols/s? We talked and tested NICE_ in GitHub issue 88Please post problems with nice in GitHub so we can follow and fix (if there are any) Edit: Did you set correct bminer protocol for ethereum in 1bash? You were right for the definition of the BMINER protocol. I defined ethstratum and everything is back in order, including for ETC which has made a nice comeback in the WTM rankings and the markets in recent days. On the other hand, I did not understand how to make Claymore fight the minning switching between ETH (on MPH) and NICE_ETHASH (On Nicehash). I systematically have this blob3 error. and I think it comes from these prameters prese, born on their support web page "EthDcrMiner64.exe -epool stratum + tcp: //daggerhashimoto.eu.nicehash.com: 3353 -ewal YOUR_BTC_ADDRESS -epsw x-esm 3 -allpools 1" To min out ETh on MPH, the -esm option is 2 and not 3. I note that Bminer does not seem to be affected by this option but that the software is only planting every 3-5 minutes on nice_ethash. I have not yet understood if I can and / or should use the specificity of BMINER and the pill enlargment. But after a few days of minning, if what is displayed by Bminer is accurate in terms of hashing speed, then it is as fast as claymore and slightly more stable. EDIT : minerinfo is dead and i don't understand whey or how to relaunch it. minerinfo seems to be dysfunctional and I can not consult anything locally :-( translated by google translate Report generator v0019-2.0.002 by leenoox
Software info:
Report ver : v0019-2.0.002
nvOC (1bash) : nvOC v0019-2.1 - Community Release
nvOC (3main) : nvOC v0019-2.1 - Community Release
1bash ver : v0019-2.1.0026
3main ver : v0019-2.1.0021
5watchdog ver : v0019-2.0.018
6tempcontrol v: v0019-2.1.0006
wtm switch ver: v0019-2.0.0021
Kernel : 4.4.0-97-generic
OS : Ubuntu 16.04.3 LTS
System : (gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
nvidia driver : 387.34
Hardware info:
Motherboard : BIOSTAR Group TB250-BTC PRO
BIOS ver. : 5.12 06/07/2017
CPU Model : Celeron(R) CPU G3900 @ 2.80GHz
CPU Cores : 2 (Cores + Threads)
Mem Total : 4011968 kB
Mem Free : 759176 kB
Swap Total : 4194300 kB
Swap Free : 4194300 kB
Ethernet : Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
HDD and Partion info:
NAME SIZE FSTYPE TYPE ROTA HOTPLUG TRAN VENDOR MODEL REV MOUNTPOINT
sda 186.3G disk 1 1 usb ATA Hitachi H C54P
├─sda1 9M vfat part 1 1 /media/m1/12D
├─sda2 20G ext4 part 1 1 /
└─sda3 4G swap part 1 1 [SWAP]
VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0b:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
1bash settings:
1bash version .............: v0019-2.1.0026
LOCAL or REMOTE ...........: LOCAL
TEAMVIEWER started ........: NO
SSH daemon started ........: YES
SLOW_USB_KEY_MODE .........: NO
SRR .......................: NO
Watchdog ..................: YES
SYSRQ Reboot ..............: YES
Watchdog Cycle ............: 15
GPU Utilization Threshold .: 70
Alternate Pool ............: NO
Temp Control ..............: YES
MANUAL_FAN ................: NO
TARGET_TEMP ...............: 70
__FAN_ADJUST ..............: 3
POWER_ADJUST ..............: 3
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 85
MINIMAL_FAN_SPEED .........: 55
MAXIMAL_FAN_SPEED .........: 100
CLEAR_LOGS_ON_BOOT ........: NO
AUTO_UPDATE ...............: STABLE
AUTO_REBOOT ...............: NO
_Parallax_MODE (upPaste)...: NO
TELEGRAM_MESSAGES .: YES
TELEGRAM_ALERTS ...: YES
TELEGRAM_TYPE .............: papampi
TELEGRAM_TIMEOUT_IN_MINUTES: 60
TELEGRAM_CHATID ...........: CHATID_NOT_SHOWN
TELEGRAM_APIKEY ...........: APIKEY_NOT_SHOWN
HEADLESS MODE:.............: NO
GPUPowerMizerMode_Adjust...: NO
ETH Pill ..................: NO
POWERLIMIT MODE ...........: GPU_SPECIFIC
GPU0 Power Limit ..........: 112
GPU1 Power Limit ..........: 114
GPU2 Power Limit ..........: 114
GPU3 Power Limit ..........: 114
GPU4 Power Limit ..........: 114
GPU5 Power Limit ..........: 114
GPU6 Power Limit ..........: 100
GPU7 Power Limit ..........: 114
GPU8 Power Limit ..........: 114
GPU9 Power Limit ..........: 114
OVERCLOCK MODE ............: GPU_SPECIFIC
GPU0 Core Overclock ........: 106
GPU0 Memory Overclock ......: 1200
GPU1 Core Overclock ........: 106
GPU1 Memory Overclock ......: 1100
GPU2 Core Overclock ........: 106
GPU2 Memory Overclock ......: 1100
GPU3 Core Overclock ........: 106
GPU3 Memory Overclock ......: 1100
GPU4 Core Overclock ........: 106
GPU4 Memory Overclock ......: 1100
GPU5 Core Overclock ........: 106
GPU5 Memory Overclock ......: 1100
GPU6 Core Overclock ........: 106
GPU6 Memory Overclock ......: 1100
GPU7 Core Overclock ........: 106
GPU7 Memory Overclock ......: 1200
GPU8 Core Overclock ........: 106
GPU8 Memory Overclock ......: 1200
GPU9 Core Overclock ........: 106
GPU9 Memory Overclock ......: 1300
GLOBAL WORKERNAME .........: YES
AUTO WORKERNAME ...........: CUSTOM
WORKERNAME ................: MINER44
plusCPU ...................: NO
COIN ......................: NICE_ETHASH
ALGO ......................: ETHASH
MINER .....................: BMINER
NICE_ETHASH WORKER ................: MINER44
NICE_ETHASH ADDRESS ...............: ...
NICE_ETHASH POOL ..................: daggerhashimoto.usa.nicehash.com
NICE_ETHASH PORT ..................: 3353
ETHASH INTENSITY ..........:
Nice hash: Just added a new option in latest 1bash (v19-2.1.0029) for all NICE_ALGO_EXTENSION_ARGUMENTS add required arguments and should solve claymore problem. miner info: If you run 19-2.1 side by side with an older version, remove or rename /home/m1//www/cgi-bin/minerinfo and reboot, should solve 19-2.1 minerinfo problem. |
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
June 23, 2018, 06:30:22 AM |
|
When do you plan to provide a new ISO file ? How much time testing ?
Thank you for all your feedbacks, please test again the miners update procedure, we did some chenges recently, in case of any issue with the testing version please report on github, to avoid confusing people here. As you see lot of things changed, and the testing stage is just at the beginning. The more people test the new beta version, the more we feel confident in declaring it as ready. Please remember to always attach a report anytime you report issues because the report contains version info needed to understand which test version you are running at that time. A few pages ago, we had discussed updating to a newer version of ubuntu that was to be released last spring. What about these projects? As I wrote, I think Xubuntu could do the trick and be a little lighter. I know that leenoox also wanted to propose many other systems even more minimalist but I do not know if he finally gave up his idea to lighten the image of nvOC. You can see my miner report in a recent message above. translated by google translate Waiting for ubuntu 18.04.1 then will release an nvOC with it. |
|
|
|
fk2
Jr. Member
Offline
Activity: 67
Merit: 2
|
|
June 23, 2018, 12:05:47 PM |
|
Hi, its fk1, someone hacked my bct account. I already complained about my rig not auto rebooting anymore since update.
Now I have a new rig, freshly installed nvOC 0019v2.0 image, it doesnt start anything anymore. wether auto reboot, or bash 2unix bash 3main, nothing.
I also tried 2.1 clone and 1.4 image to 2.0. absolutely clueless what the problem is
|
|
|
|
|
CryptAtomeTrader44
Full Member
Offline
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
|
|
June 23, 2018, 03:22:47 PM |
|
On Windows 7, write the image via HDDrawcopy on another disk then connect to my RIG, then copy my 1bash currently used on the 19.2.0 via another profile in the terminal 1st test: 1 / My 1bash was not copied to the system at first boot 2 / The autoexpand was not done at the first boot 3 / The second boot did not start the system 4 / The 3rd boot shows me unrecoverable file system error nvOC v0019-2.1 - Community Release
nvOC v0019-2.1 - Community Release
Cannot make directory '/var/run/screen': Permission denied
rig IP: 192.168.1.144
rig MAC: b8:97:5a:f7:33:9e
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0b:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
Sat Jun 23 05:41:31 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.67 Driver Version: 390.67 |
|-------------------------------+----------------------+----------------------+
| 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 1070 Off | 00000000:01:00.0 On | N/A |
| 0% 51C P8 9W / 151W | 125MiB / 8119MiB | 4% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 106... Off | 00000000:02:00.0 Off | N/A |
| 37% 51C P8 8W / 180W | 9MiB / 6078MiB | 4% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 106... Off | 00000000:03:00.0 Off | N/A |
| 25% 45C P8 10W / 180W | 9MiB / 6078MiB | 4% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 1070 Off | 00000000:05:00.0 Off | N/A |
| 0% 47C P8 6W / 151W | 9MiB / 8119MiB | 2% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 106... Off | 00000000:06:00.0 Off | N/A |
| 38% 53C P8 7W / 180W | 9MiB / 6078MiB | 4% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 1070 Off | 00000000:07:00.0 Off | N/A |
| 0% 44C P8 5W / 151W | 9MiB / 8119MiB | 1% Default |
+-------------------------------+----------------------+----------------------+
| 6 GeForce GTX 1070 Off | 00000000:08:00.0 Off | N/A |
| 0% 50C P8 7W / 151W | 9MiB / 8119MiB | 2% Default |
+-------------------------------+----------------------+----------------------+
| 7 GeForce GTX 106... Off | 00000000:09:00.0 Off | N/A |
| 27% 46C P8 6W / 180W | 9MiB / 6078MiB | 4% Default |
+-------------------------------+----------------------+----------------------+
| 8 GeForce GTX 106... Off | 00000000:0A:00.0 Off | N/A |
| 33% 50C P8 6W / 180W | 9MiB / 6078MiB | 3% Default |
+-------------------------------+----------------------+----------------------+
| 9 GeForce GTX 1070 Off | 00000000:0B:00.0 Off | N/A |
| 0% 47C P8 6W / 151W | 9MiB / 8119MiB | 2% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1276 G /usr/lib/xorg/Xorg 94MiB |
| 0 2072 G compiz 28MiB |
| 1 1276 G /usr/lib/xorg/Xorg 6MiB |
| 2 1276 G /usr/lib/xorg/Xorg 6MiB |
| 3 1276 G /usr/lib/xorg/Xorg 6MiB |
| 4 1276 G /usr/lib/xorg/Xorg 6MiB |
| 5 1276 G /usr/lib/xorg/Xorg 6MiB |
| 6 1276 G /usr/lib/xorg/Xorg 6MiB |
| 7 1276 G /usr/lib/xorg/Xorg 6MiB |
| 8 1276 G /usr/lib/xorg/Xorg 6MiB |
| 9 1276 G /usr/lib/xorg/Xorg 6MiB |
+-----------------------------------------------------------------------------+
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:0]) assigned value 100.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:1]) assigned value 100.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:2]) assigned value 100.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:3]) assigned value 100.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:4]) assigned value 100.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:5]) assigned value 100.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:6]) assigned value 100.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:7]) assigned value 100.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:8]) assigned value 100.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:9]) assigned value 100.
Power limit for GPU 00000000:01:00.0 was set to 75.00 W from 151.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.
Provided power limit 75.00 W is not a valid power limit which should be between 90.00 W and 200.00 W for GPU 00000000:02:00.0
Terminating early due to previous errors.
LAUNCHING: MINER TEMPCONTROL
Cannot make directory '/var/run/screen': Permission denied
process in screen temp, guake terminal Tab (f12), 'nvOC temp-log'
Auto Start Miner is set to NO
Miner is not starting
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:1]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:1]) assigned value 100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:2]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:2]) assigned value 100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:3]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:3]) assigned value 100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:4]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:4]) assigned value 100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:5]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:5]) assigned value 100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:6]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:6]) assigned value 100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:7]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:7]) assigned value 100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:8]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:8]) assigned value 100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:9]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:9]) assigned value 100.
2nd test: On Windows 7, write the image via HDDrawcopy on another disk then connect to my RIG, then copy my 1bash currently used on the 19.2.0 via another profile in the terminal: 1 / the system booted correctly and executed the first boot script successfully. The autoexpand ran correctly and my 1 bash was copied, then the system rebooted 2 / the script 3main read some variables of my 1 bash but does not seem able to determine which coin / algorithm it should use 3 / The 3main script prevented the watchdog script from starting and he refused to start the minning. the system remained started, the tabs in guakes are started but nothing happens. nvOC v0019-2.1 - Community Release
nvOC v0019-2.1 - Community Release
No Sockets found in /var/run/screen/S-m1.
rig IP: 192.168.1.144
rig MAC: b8:97:5a:f7:33:9e
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0b:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
Sat Jun 23 06:08:35 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.67 Driver Version: 390.67 |
|-------------------------------+----------------------+----------------------+
| 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 1070 Off | 00000000:01:00.0 On | N/A |
| 0% 48C P8 8W / 151W | 124MiB / 8119MiB | 4% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 106... Off | 00000000:02:00.0 Off | N/A |
| 0% 36C P8 6W / 180W | 9MiB / 6078MiB | 4% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 106... Off | 00000000:03:00.0 Off | N/A |
| 0% 37C P8 10W / 180W | 9MiB / 6078MiB | 4% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 1070 Off | 00000000:05:00.0 Off | N/A |
| 0% 34C P8 5W / 151W | 9MiB / 8119MiB | 2% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 106... Off | 00000000:06:00.0 Off | N/A |
| 0% 37C P8 7W / 180W | 9MiB / 6078MiB | 1% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 1070 Off | 00000000:07:00.0 Off | N/A |
| 0% 37C P8 5W / 151W | 9MiB / 8119MiB | 1% Default |
+-------------------------------+----------------------+----------------------+
| 6 GeForce GTX 1070 Off | 00000000:08:00.0 Off | N/A |
| 0% 40C P8 6W / 151W | 9MiB / 8119MiB | 1% Default |
+-------------------------------+----------------------+----------------------+
| 7 GeForce GTX 106... Off | 00000000:09:00.0 Off | N/A |
| 0% 34C P8 6W / 180W | 9MiB / 6078MiB | 2% Default |
+-------------------------------+----------------------+----------------------+
| 8 GeForce GTX 106... Off | 00000000:0A:00.0 Off | N/A |
| 0% 35C P8 6W / 180W | 9MiB / 6078MiB | 1% Default |
+-------------------------------+----------------------+----------------------+
| 9 GeForce GTX 1070 Off | 00000000:0B:00.0 Off | N/A |
| 0% 37C P8 5W / 151W | 9MiB / 8119MiB | 1% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1406 G /usr/lib/xorg/Xorg 93MiB |
| 0 2147 G compiz 28MiB |
| 1 1406 G /usr/lib/xorg/Xorg 6MiB |
| 2 1406 G /usr/lib/xorg/Xorg 6MiB |
| 3 1406 G /usr/lib/xorg/Xorg 6MiB |
| 4 1406 G /usr/lib/xorg/Xorg 6MiB |
| 5 1406 G /usr/lib/xorg/Xorg 6MiB |
| 6 1406 G /usr/lib/xorg/Xorg 6MiB |
| 7 1406 G /usr/lib/xorg/Xorg 6MiB |
| 8 1406 G /usr/lib/xorg/Xorg 6MiB |
| 9 1406 G /usr/lib/xorg/Xorg 6MiB |
+-----------------------------------------------------------------------------+
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:0]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:1]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:2]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:3]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:4]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:5]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:6]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:7]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:8]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:9]) assigned value 0.
Power limit for GPU 00000000:01:00.0 was set to 114.00 W from 151.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.
Power limit for GPU 00000000:02:00.0 was set to 114.00 W from 180.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.
Power limit for GPU 00000000:03:00.0 was set to 114.00 W from 180.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.
Power limit for GPU 00000000:05:00.0 was set to 114.00 W from 151.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.
Power limit for GPU 00000000:06:00.0 was set to 114.00 W from 180.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.
Power limit for GPU 00000000:07:00.0 was set to 114.00 W from 151.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.
Power limit for GPU 00000000:08:00.0 was set to 100.00 W from 151.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.
Power limit for GPU 00000000:09:00.0 was set to 114.00 W from 180.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.
Power limit for GPU 00000000:0A:00.0 was set to 114.00 W from 180.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.
Power limit for GPU 00000000:0B:00.0 was set to 114.00 W from 151.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.
LAUNCHING: MINER TEMPCONTROL
process in screen temp, guake terminal Tab (f12), 'nvOC temp-log'
LAUNCHING: WTM AUTO SWITCH
process in screen wtm, guake terminal Tab (f12)
Auto Start Miner Set to YES
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 105.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 1200.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:1]) assigned value 105.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:1]) assigned value 1100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:2]) assigned value 105.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:2]) assigned value 1100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:3]) assigned value 105.
LAUNCHING: MINER WATCHDOG (LOCAL)
process in screen wdog, guake terminal Tab (f12), 'nvOC wdog-log'
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:3]) assigned value 1200.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:4]) assigned value 105.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:4]) assigned value 1100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:5]) assigned value 105.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:5]) assigned value 1150.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:6]) assigned value 105.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:6]) assigned value 1100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:7]) assigned value 105.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:7]) assigned value 1100.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:8]) assigned value 105.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:8]) assigned value 1100.
[WARNING] - Attempting to launch miner for an undefined algo
LAUNCHING: MINER
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:9]) assigned value 105.
COIN/ALGO not found, Check your settings
Miner not started, Stopping watchdog
Miner output: ./nvOC miner-log
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:9]) assigned value 1250.
3rd test On Windows 7, write the image via HDDrawcopy on another disk then connect to my RIG, then change the 1bash testing 19-2.1beta1 to match it provided with the image: 1 / The first automated steps mentioned above take place properly, even if the machian restarts 2 / After restarting, 3main starts the mining on FTC, then turns in loop, then I replace FTC by KMD by hand in the 1bash, and 3main launches well DSTM on KMD 3 / WTM_SWITCHING tells me that the corner to mine is ETH! so there is a pb with WTM_SWITCHING 4 / Minerinfo works (but I will change the colors at my convenience later) 4th test 1 / Minning in FTC Manual: Does not work 2 / I kill all the screens (pkill -f screen) and I run the command in ssh via putty: I get: /home/m1/NVOC/mining/miners/KTccminer/ccminer -a neoscrypt -o stratum+tcp://hub.miningpoolhub.com:20510 -u cryptatometrader44.ATOMICMINER44 -p x -i 17
ccminer 8.20-KlausT (64bit) for nVidia GPUs
Compiled with GCC 5.4 using Nvidia CUDA Toolkit 8.0
Based on pooler cpuminer 2.3.2 and the tpruvot@github fork
CUDA support by Christian Buchner, Christian H. and DJM34
Includes optimizations implemented by sp-hash, klaust, tpruvot and tsiv.
Illegal instruction I guess the software is to recompile, so I restart the KTccminer compilation via the papampi script: ./NVOC/mining/miners/nvOC_miner_update.sh Alas, the compilation script in the new image does not work! bn.h openssl fixed for compiling miners
Select miners to compile (multiple comma separated values: 1,6,7)
1 - ASccminer
2 - KTccminer
3 - KTccminer-cryptonight
4 - KXccminer
5 - NAccminer
6 - SPccminer
7 - TPccminer
8 - vertminer
9 - ANXccminer
R - MSFTccminer (RVN)
X - xmr-stak
Do your Choice: [A]LL [1] [2] [3] [4] [5] [6] [7] [8] [9] [R] [X] [E]xit: 2
2
Compiling KlausT ccminer
This could take a while ...
fatal: Not a git repository (or any of the parent directories): .git
./NVOC/mining/miners/nvOC_miner_update.sh: line 404: cd: /home/m1/KTccminer/src: No such file or directory
bash: /home/m1/KTccminer/src/autogen.sh: No such file or directory
bash: /home/m1/KTccminer/src/configure: No such file or directory
bash: /home/m1/KTccminer/src/build.sh: No such file or directory
cp: cannot stat '/home/m1/KTccminer/src/ccminer': No such file or directory
Finished compiling KlausT ccminer
Restart miner I manually start the compilation in the KTccminer software folders: m1@m1-desktop:~/NVOC/mining/miners$ ls KTccminer
ccminer KTccminer.tar.xz src version
m1@m1-desktop:~/NVOC/mining/miners$ ls
ANXccminer ethminer NAccminer TPccminer
ASccminer KTccminer nvOC_miner_update.sh vertminer
bminer KTccminer-cryptonight README.md xmr-stak
claymore KXccminer SILENTminer ZENEMYminer
dstm MSFTccminer SPccminer
m1@m1-desktop:~/NVOC/mining/miners$ cd KTccminer
m1@m1-desktop:~/NVOC/mining/miners/KTccminer$ ls
ccminer KTccminer.tar.xz src version
m1@m1-desktop:~/NVOC/mining/miners/KTccminer$ cd src/
m1@m1-desktop:~/NVOC/mining/miners/KTccminer/src$ ls
m1@m1-desktop:~/NVOC/mining/miners/KTccminer/src$ Alas, again, as I had already reported in one of my previous posts, the sources are not available on the RIG! Yet at the launch of the software update script minning, he did check between the repository and those present on the RIG. Which in my opinion means that the sources of the software provided in the update script are corrupt, missing or missing. I therefore insist once again that the recompilation of some minning software is systematic or mandatory. Especially that of KLAUST for neoscrypt I had to make a in /home/m1/NVOC/minning to mail you this report. And I see that the tool has expanded other functions that I did not know before this beta2.
Software info:
Report ver : v0019-2.0.002
nvOC (1bash) : nvOC v0019-2.1 - Community Release
nvOC (3main) : nvOC v0019-2.1 - Community Release
1bash ver : v0019-2.1.0026
3main ver : v0019-2.1.0022
5watchdog ver : v0019-2.0.018
6tempcontrol v: v0019-2.1.0006
wtm switch ver: v0019-2.0.0021
Kernel : 4.4.0-128-generic
OS : Ubuntu 16.04.4 LTS
System : (gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
nvidia driver : 390.67
Hardware info:
Motherboard : BIOSTAR Group TB250-BTC PRO
BIOS ver. : 5.12 06/07/2017
CPU Model : Celeron(R) CPU G3900 @ 2.80GHz
CPU Cores : 2 (Cores + Threads)
Mem Total : 4011868 kB
Mem Free : 2351776 kB
Swap Total : 0 kB
Swap Free : 0 kB
Ethernet : Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
HDD and Partion info:
NAME SIZE FSTYPE TYPE ROTA HOTPLUG TRAN VENDOR MODEL REV MOUNTPOINT
sda 465.8G disk 1 1 usb ATA WDC WD500 1A01
├─sda1 9M vfat part 1 1 /media/m1/12D
└─sda2 465.8G ext4 part 1 1 /
VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0b:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
1bash settings:
1bash version .............: v0019-2.1.0026
LOCAL or REMOTE ...........: LOCAL
TEAMVIEWER started ........: NO
SSH daemon started ........: YES
SLOW_USB_KEY_MODE .........: NO
SRR .......................: NO
Watchdog ..................: YES
SYSRQ Reboot ..............: YES
Watchdog Cycle ............: 15
GPU Utilization Threshold .: 70
Alternate Pool ............: NO
Temp Control ..............: YES
MANUAL_FAN ................: NO
TARGET_TEMP ...............: 70
__FAN_ADJUST ..............: 3
POWER_ADJUST ..............: 3
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 85
MINIMAL_FAN_SPEED .........: 55
MAXIMAL_FAN_SPEED .........: 100
CLEAR_LOGS_ON_BOOT ........: NO
AUTO_UPDATE ...............: STABLE
AUTO_REBOOT ...............: NO
_Parallax_MODE (upPaste)...: NO
TELEGRAM_MESSAGES .: YES
TELEGRAM_ALERTS ...: YES
TELEGRAM_TYPE .............: papampi
TELEGRAM_TIMEOUT_IN_MINUTES: 60
TELEGRAM_CHATID ...........: CHATID_NOT_SHOWN
TELEGRAM_APIKEY ...........: APIKEY_NOT_SHOWN
HEADLESS MODE:.............: NO
GPUPowerMizerMode_Adjust...: NO
ETH Pill ..................: NO
POWERLIMIT MODE ...........: GPU_SPECIFIC
GPU0 Power Limit ..........: 114
GPU1 Power Limit ..........: 114
GPU2 Power Limit ..........: 114
GPU3 Power Limit ..........: 114
GPU4 Power Limit ..........: 114
GPU5 Power Limit ..........: 114
GPU6 Power Limit ..........: 100
GPU7 Power Limit ..........: 114
GPU8 Power Limit ..........: 114
GPU9 Power Limit ..........: 114
OVERCLOCK MODE ............: GPU_SPECIFIC
GPU0 Core Overclock ........: 105
GPU0 Memory Overclock ......: 1200
GPU1 Core Overclock ........: 105
GPU1 Memory Overclock ......: 1100
GPU2 Core Overclock ........: 105
GPU2 Memory Overclock ......: 1100
GPU3 Core Overclock ........: 105
GPU3 Memory Overclock ......: 1200
GPU4 Core Overclock ........: 105
GPU4 Memory Overclock ......: 1100
GPU5 Core Overclock ........: 105
GPU5 Memory Overclock ......: 1150
GPU6 Core Overclock ........: 105
GPU6 Memory Overclock ......: 1100
GPU7 Core Overclock ........: 105
GPU7 Memory Overclock ......: 1100
GPU8 Core Overclock ........: 105
GPU8 Memory Overclock ......: 1100
GPU9 Core Overclock ........: 105
GPU9 Memory Overclock ......: 1250
GLOBAL WORKERNAME .........: YES
AUTO WORKERNAME ...........: CUSTOM
WORKERNAME ................: ATOMICMINER44
plusCPU ...................: NO
COIN ......................: FTC
ALGO ......................: NEOSCRYPT
MINER .....................: KTccminer
FTC WORKER ................: ATOMICMINER44
FTC ADDRESS ...............: cryptato...
FTC POOL ..................: hub.miningpoolhub.com
FTC PORT ..................: 20510
NEOSCRYPT INTENSITY ..........: 17
|
|
|
|
|
|
