And another. Poor Kano who's at his brother's funeral will at least get some joy when he returns home  |
|
|
|
Forum Moderators: please lock this thread. I also suggest that unless BAN are prepared to actually communicate with their ripped-off miners, they should be banned from opening yet another useless thread in the future.
We wouldn't lock the thread for that reason alone as the ability to discuss the pool needs to go somewhere so that users can make up their own minds based on the most recent discussion, but we wouldn't allow multiple duplicate threads. |
|
|
|
What would you call the current hashrate?
Seems to be fluctuating between 1.2 & 2.8 lately tbh - could do with double that though.......  I'd say 1.5 ph/s. 1.5 sounds like a good description then. |
|
|
|
This is getting very rough indeed.  Having the hash rate at 1/2 of what it was not that long ago doesn't help. M For sure. Guess the thread title needs to be edited to reflect that. What would you call the current hashrate? |
|
|
|
Cgminer primarily targets Linux not Windows. Ckolivas doesn't even test on windows at all(his windows builds are cross compiles).
Nonsense. I test every release on a windows laptop. Whether I still have access to certain mining hardware or not is another story. Meant more along the lines of the testing during driver development. Sure linux is my primary platform for development so it's always going to work better, but saying I don't even test on windows is a bit rich. |
|
|
|
Are (some of) these problems peculiar to Windows ?
Would people be better off purchasing the new Raspberry Pi 2 (quadcore Arm 7 + 1GB memory)
Yes and no. Windows drivers can always be annoying but generally once its working it should just continue to work. The same could be said on another platform. These have also been tested significantly more on Windows so we tend to know what will go wrong. Cgminer primarily targets Linux not Windows. Ckolivas doesn't even test on windows at all(his windows builds are cross compiles). Nonsense. I test every release on a windows laptop. Whether I still have access to certain mining hardware or not is another story. |
|
|
|
|
Even if you could get an ipad to mine you would earn maybe one cent in the course of a year in a denomination no pool would ever allow you to withdraw so it is a futile exercise pursuing this.
I think this thread has existed long enough and I'm locking it to prevent it being bumped repeatedly with nothing useful to add.
|
|
|
|
|
What pool and what are you mining?
|
|
|
|
The other thing I want to point out is the -expiry option. A lot of people have said the setting doesn't matter anymore, but I can't see why. I've never looked at the code, but the cgminer readme has the info below. I always change my miners to 1 (all currently Antminer). When I left it as the default of 120, I got more stales. I did not run an extensive test though. --expiry|-E <arg> Upper bound on how many seconds after getting work we consider a share from it stale (default: 120) You've never looked at the code but can't see why it doesn't matter... I wrote the code and I'm telling you it doesn't matter. |
|
|
|
Thank you for mtr! I installed it and this is a report: root@officerasp:/home/xxxxxxxx# mtr --report -w solo.ckpool.org HOST: officerasp Loss% Snt Last Avg Best Wrst StDev
1.|-- FRITZBOX 0.0% 10 1.3 1.7 1.3 4.2 0.9
2.|-- rdsl-krlh-de80.nw.mediaways.net 0.0% 10 45.5 42.5 41.0 45.5 1.2
3.|-- xmws-krlh-de02-chan-20.nw.mediaways.net 0.0% 10 40.7 40.9 39.7 43.0 0.9
4.|-- xe-1-0-0-0.0002.dbrx.01.kae.de.net.telefonica.de 0.0% 10 40.2 51.8 39.1 143.3 32.2
5.|-- rmwc-zuri-ch01-so-2-1-0-0.nw.mediaways.net 0.0% 10 56.2 55.2 52.0 57.1 1.6
6.|-- 10gigabitethernet1-2.core1.zrh1.he.net 0.0% 10 65.0 59.1 53.9 65.7 4.7
7.|-- 10ge10-1.core1.par2.he.net 0.0% 10 74.6 74.4 71.2 80.2 3.3
8.|-- 10ge15-1.core1.ash1.he.net 0.0% 10 155.2 153.1 139.8 200.2 17.4
9.|-- 100ge15-1.core1.lax1.he.net 0.0% 10 197.4 202.0 197.4 209.7 4.0
10.|-- 100ge15-1.core1.sjc2.he.net 0.0% 10 207.3 210.0 207.0 218.7 3.6
11.|-- 10ge3-2.core3.fmt2.he.net 0.0% 10 225.2 213.7 206.7 225.2 5.6
12.|-- router3-fmt.linode.com 10.0% 10 211.0 209.0 205.5 212.1 2.1
13.|-- li773-180.members.linode.com 10.0% 10 208.6 208.5 206.5 211.5 1.4
looks ok for me? what do you think? Yep looks perfectly fine right now. Check it if/when you next see connectivity problems. |
|
|
|
I see the interuption live, i have two cgminer running.
One is on a Raspi with Debian and your cgminer with a Jalapeno and on my work pc
running xp i got a Antminer 2 with cgminer. Both reported the same.
I am in germany, so maybe the link to your server was simply interupted.
The internet connection was ok.
Never mind, it was a time of 2 min. and i just want to let you know, no complain.
I had this before, but i never see it live, as i am working and not constantly monitoring the miner.
In that case i saw it and i wrote the message. 2 min. later it was reastablished and i edit my Posting.
Usually this is packet loss somewhere in the routing between you and the server, so it's not your fault or the pool's fault. If you're on linux/*nix you can check the quality of your routing at any time with mtr. If a hop has packet loss of up to 10% that's ok but anything 20% or more is likely a problem. This is the command: mtr --report -w solo.ckpool.org
|
|
|
|
|
It has been many years since computers were last able to mine bitcoin on their own sorry. Normal computer hardware that you buy in a regular computer store cannot meaningfully mine bitcoin in any capacity whatsoever, they can only be used to run software the runs dedicated mining hardware (ASICs) that do the actual bitcoin mining. No you cannot earn money running even 10s of thousands of computers attempting to mine bitcoin without dedicated mining hardware.
|
|
|
|
Good luck! Damn shame that 50TH isn't even that much these days. Server and pool still seems fine. I've opened a ticket for the upstream provider.
Provider has already responded and they have had zero issues. The fact that 2 different users had issues means that perhaps the internet routing in their part of the world was where the problem was. Anyway everything's fine at the pool, server and datacentre. |
|
|
|
|
Server and pool still seems fine. I've opened a ticket for the upstream provider.
|
|
|
|
 Pool 0 stratum+tcp://solo.ckpool.org:3333 not responding Ohhh EDit: resuming, that was quick! There was no interruption at the pool end so you probably had a problem somewhere downstream from the pool. Mine failed over too. Don't know for how long though. Nothing wrong at the pool end, but probably immediately upstream maybe at the data centre? I didn't get any notification of any issues but that doesn't mean it didn't happen. |
|
|
|
Pool 0 stratum+tcp://solo.ckpool.org:3333 not responding Ohhh EDit: resuming, that was quick! There was no interruption at the pool end so you probably had a problem somewhere downstream from the pool. |
|
|
|
i tried running " sudo apt-get install build-essential
./configure --without-ckdb
make
" but got a whole wackload of errors. really need an ELI5 on this it seems They're separate lines which are not wrapped on the repository summary. Read the readme directly. ./configure --without-ckdb "-bash: ./configure: No such file or directory" I guess I have to spell it out. You are building from git, there are extra instructions. |
|
|
|
i tried running " sudo apt-get install build-essential
./configure --without-ckdb
make
" but got a whole wackload of errors. really need an ELI5 on this it seems They're separate lines which are not wrapped on the repository summary. Read the readme directly. |
|
|
|
|
Show Posts
