 Show Posts
|
|
Pages: [1] 2 3 4 »
|
That is much better now. You could save even more space by removing the whole hashrate bar :  And put it at the right of the buttons :  |
|
|
|
I like the new graph, I don't really care about it's placement as much as I'd like not having to scroll on the detailed view...  |
|
|
|
|
Hi there, great OS I just started using it a month ago, I must say WOW!
After all that I had tried and heard that linux consummes more power, I was shocked to find that it is not true!
Yay!
Now I have also tried HiveOS and meh, don't like it... don't like the layout, slow to make changes...
Can we requests features here? Is this the right spot?
Cause I would love to be able to trigger to have GPU numbers according to the miner in use, i.e. Claymore 0-9 vs Phoenix 1-10
I am using Phoenix and keep having to make sure I use the proper cards when troubleshooting... it would greatly help!
|
|
|
|
|
I have rigs in two locations.
Shellinabox works obviously only on the local rig.
Problem is on one rig it works and the second it doesn't.
I see it filling the user and pass fields (it shows in the URL anyway) but the login/password is always incorrect...
How can that be? Is this a known issue?
I am new to SimpleMining, however I think it's extremely cool!
Btw, would it be possible to request a "dark" theme for the UI?
Thanks!
|
|
|
|
|
Coinwarz still has not updated Curecoin showing up as SHA256 which it is not for the couple of weeks or months...
|
|
|
|
I think there was still an algo with only CPU mining support, something that sounds Japanese-like... I can't remember the name but it had very low liquidity and profitability so I didn't bother.
Do you mean Yenten? I mined this sucker for almost a year! So yeah, any update soon JoBlo? There is this new VECO coin cpu only that JUST changed algo today for yespower and it seems the only miners available are some forks...
cpuminer-opt-rplant
cpuminer-opt-bf
cpuminer-opt-cryplyI don't know if I'm allowed to post the links but I imagine it would be disrespectful towards JoBlo, unless maybe he knows some of 'em? There's not much going on here, not even 10 posts in the past months... Oh well! Happy new Year!  |
|
|
|
Wallet enabled on Bittrex , hooray we just hit 100+ masternodes over day.
Finafuckinglly!  That was long... Now let's hope it's worth the wait! |
|
|
|
How can there be 23 nodes already  |
|
|
|
Ok, it is clear you are trying to help but please let this one go.
That source you posted is obviously outdated and clearly rookie targeted.
Mining is not the typical usage senario for desktop PC so please skip any article, guide whatever that is not specifically made for Cryptomining.
Anything below 20GB virtual memory will propably crash the miner. Even the OP states that VM should be 16GB or more.
I recommend he sets it to 25GB and try again.
Actually, when I decreased my RAM from 8 GB to 3 GB, I was facing some sort of application crash during mining (somewhat similar to @damba_'s), but decreasing the virtual RAM to 15000 MB worked out for me that time (it was way over this number before I decreased it). It's still running good at 15000 MB (just re-checked this number) with 3 GB RAM. From what I can conclude, if you've over 4 GB RAM, you can set insanely huge values of virtual RAM like 40 GB or 50 GB (probably as big as your available secondary memory size), but if you've around 2-3 GB RAM, you've to set it lower and can't be that crazy. Well that does not mean that it's because you decreased the pagefile that it ran better, rather decreasing the pagefile deletes it and recreates it. I am certain that if you went right back after to 15gb it would still work, proving my point. The amount of virtual memory has nothing to do with system stability, especially for mining where with ETH you need about 2.5gb of memory for each card. Now on a 10 cards rig that's close to 25gb and you want to set a bit more for increase over time. I run mine with 60gb pagefile and don't have stability issues. What you mention is what I believe you had instability issues in that pagefile and recreating it fixed your problem, the issue was not fixed by lowering it. See the difference? |
|
|
|
Can this miner run on 2GB of system memory?
I had 3 gb ddr2, but one ram stick stopped working so I'm left with only 2 gb of system memory.
I tried to start miner and I get message: ethdcrminer64.exe has stopped working
I didn't have any problems so far with 3 gb of RAM.
Miner should run just fine on 2 GB of RAM. "Virtual memory" could be the issue here. It should be no less than 1.5x and no more than 3x the amount of system memory (RAM). Just what the heck are you talking about? Virtual memory (pagefile) can be anything you want, there are no min or max, in fact the more cards you have the more Virtual ram you need, I have plenty or rigs running 50GB pagefiles. You are confusing what Windows automatically sets with your 1.5x... Please don't spread misinformation. |
|
|
|
here ya go  i think it's the latest  i'm running v2.0.0.1, so search for a link in this thread somewhere after the post quoted  if you go to http://www.hempcoin.org/ and click the download wallet button you get a file called hcwin32.exe, it is version 2.1.1.0-gcc, it's a 32 bit wallet, but it works fine on win64 systems. There is also the qt project file on https://github.com/hempcoin-project/THC which I use on my linux mint system. Actually the one on hempcoin.org (hcwin32.exe) is version 2.0.0.1 which has the staking regression bug that was fixed in 2.1.1.0, which is available here https://github.com/hempcoin-project/THC/releases in both 32 or 64 bit! I have no clue why the version on the website is still not the latest, I know this because about 3 months ago I used 2.0.0.1 after the previous version couldnt stake properly, only to find that even 2.0.0.1 had the same bug, so about 50 days ago I found version 2.1.1.0 that actually works. It would be nice if the dev would actually update the wallet version from their website... I would advise anyone that is about to stake (the 45 days wait) or even if you are already in it, don't start any other version wallet than 2.1.1.0 otherwise you might lose your staking as it only works once then resets the dates as of that day and then you have to wait another 45 days. Also, could dev or anyone with proper rights fix the links in OP? I hope this is not too confusing, it was for me... |
|
|
|
|
Can't seem to be able to mine with 3.1
I get bad shares
|
|
|
|
I messed up some miners and put my sending address instead of my receiving one.. Shocked
Can I get some help please? I see no contact information...
That happened to me when I started YTN, nothing can be done tho sorry. If you do find help let us know but I doubt. |
|
|
|
No it's still dual channel, running @ 1.35V like it should, I'll take a look at this paper thanks!
Make sure your Ryzen has the latest BIOS, there have been issues with higher speed memory. Yes of course it is up to date... But still this is B-Die ram 2x8GB, even on older bios it works fine. The question is, why or how is CPU hashing less on YescryptR16 / R32 ? |
|
|
|
Joblo I got a question. (or anyone that could)
I just changed my ram from 3200 (Only able to run 2666Mhz, it is dual rank ram) 16-18-18 to 3200 14-14-14 Samsung B-Die to be able to run full speed of 3200 on Ryzen...
I mine YescryptR32 or R16. On R32 I get speeds of 585H/s with the 2666 CL16 vs 450H/s with the 3200 CL14...
I read it could be that this algo has memory requirements... but can't get any more info than this...
Do you know?
If I understand correctly, you went from dual channel memory to single. Math would say that the throughput is now (3200 / 2666 / 2) ~= 60% of the original, so the more memory dependent the algo, the more speed you loose You can also take a look at the CPU load/temps/power consumption, if it is lower that it was before, this means that you dont have enough memory bandwidth to feed cpu with enough work Yescrypt algo is bandwidth hard, since it performs memory lookups If interested, see more in the whitepaper https://password-hashing.net/submissions/specs/yescrypt-v2.pdfNo it's still dual channel, running @ 1.35V like it should, I'll take a look at this paper thanks! |
|
|
|
|
Joblo I got a question. (or anyone that could)
I just changed my ram from 3200 (Only able to run 2666Mhz, it is dual rank ram) 16-18-18 to 3200 14-14-14 Samsung B-Die to be able to run full speed of 3200 on Ryzen...
I mine YescryptR32 or R16. On R32 I get speeds of 585H/s with the 2666 CL16 vs 450H/s with the 3200 CL14...
I read it could be that this algo has memory requirements... but can't get any more info than this...
Do you know?
|
|
|
|
digger 2 Ryzen - 1600 - 558 h/s the second digs less, the equipment is the same №2 Ryzen - 1600 - 504 h/s  I dig on video cards 1060 - 420 h/s That sound about right! So weird my issue it drives me nuts! I did memtest to be sure, seems ok. I understand you. I remember how I started to mining on video cards, constantly changing MHz trying to find the optimal ratio of temperature and speed of mining, spent a lot of time on it. What was my surprise when on another algorithm these settings were not optimal and I had to start all over again. I want to help you, but I do not know how. I still think you need to dig in the direction of the settings of the RAM, it is possible to swap the bars or something else. Yeah I'll play around with this tomorrow, right now I'm just pissed.  Need sleep! |
|
|
|
digger 2 Ryzen - 1600 - 558 h/s the second digs less, the equipment is the same №2 Ryzen - 1600 - 504 h/s I dig on video cards 1060 - 420 h/s That sound about right! So weird my issue it drives me nuts! I did memtest to be sure, seems ok. |
|
|
|
I have an issue with WAVI Mining.
I mine Wavi with a i5-8600K (6 physical cores) and cpuminer-opt from JayDDee/Joblo (last version).
My issue is that I have the same hashrate with 2, 3, 4, 5 or 6 cores and I can't have better than 200 hash/s... this is near that I have with my Celeron G3900.
This computer is with Windows 10 but I have the same issue with Ubuntu (last kernel).
Any idea ?
maybe slow memory? One memory channel? Yes, I have only one DDR4 DIMM, but you think that can be the issue ? A 8600k should make at least 400 h/s, the double that I have ? I heard that in this algorithm the memory characteristics are important. Probably slow memory and one channel does not allow to fully open the CPU potential in this algorithm. I wonder what the developer will say in this regard @WNC12k Where have you read this? I have been mining fine with my Ryzen 1700 at ~600H/s for well over a month, but I had 2x8GB of Corsair Vengeance 3200Mhz and could only run them at 2666Mhz, reading that B-Die ram is the only one worthy on the Ryzen platform I finally bought some. Got the TEAM Dark Pro which are 3200Mhz and advertized as beeing B-Die. It seems to be the case, runs fine... But now I can only mine at ~395H/s! I search for the info but it seems it hard to find really... I'd like to understand what it is that I should be doing next... return it or try to tweak it? Worst part is I sold them rightaway ( the corsairs ) so ... I need to deal with this now, any help would be appreciated guys! This I know from the experience of using the algorithm YescryptR16, especially since it is exactly twice as fast. Check the speed on Yenten, there should be an increase of 2 times. If the speed has increased no more than twice from the current one, then this may be a problem in the memory settings, the dual-channel mode may not be enabled I was mining Yenten also before and will get back to it soon... I am running dual channel, I just spent 20 minutes in the bios to check all the options available, though besides the sticks being faster @ 3200Mhz 14-14-14-31 vs 2666Mhz 16-16-18-36, nothing else is different... that I can see. If anything it should be faster no? Now what is the speed on the YescryptR16? Now is 900H/s (up to 450H/s now with YescryptR32) but before with the other ram I was doing ~1.1K/s So it's exactly in the hardware settings. Try to play around with the RAM settings, can the energy-saving mode be enabled? No nonsense settings are applied, I am the type of geek that disables whatever is not needed like com ports, even the S3 mode is disabled... I can't imagine that an actual faster ram slows down this algo? If I swap right now to my old one, I get the better results of 585H/s, but if not it's at 450H/s |
|
|
|
|
