XBC will prevail and all the bagholders will rejoice in their wealth, people who sold will search for someone to blame, but will only find themselves.
|
|
|
Why oh why does so much drama surround this beautiful coin
|
|
|
Sent my address to you via PM!
|
|
|
I love XBC to death but cmon guys, the wallet was promised "in 24 hours" over a week ago. That doesn't help add any credibility to the coin or dev team. Since then there has been many "in 24 hours" announcements that didn't follow through, that doesn't help either. I understand you need to make the wallet work and be bug free, but at this point, just don't say any kind of timeframe to get people's hopes up, just to crush them, it is not helping the coins image.
you still don't "get it" let me explain >> I "get" you must have nothing better to do on a Saturday or Saturday night than watch the XBC thread and troll on people's posts.
|
|
|
I love XBC to death but cmon guys, the wallet was promised "in 24 hours" over a week ago. That doesn't help add any credibility to the coin or dev team. Since then there has been many "in 24 hours" announcements that didn't follow through, that doesn't help either. I understand you need to make the wallet work and be bug free, but at this point, just don't say any kind of timeframe to get people's hopes up, just to crush them, it is not helping the coins image.
|
|
|
Sandor, how do I pull an old version from github? I need to revert to an older version. Ever since about 0.9c I get super high rejects, but cpuminer actually only reports a small portion of them, my pool reports a much higher amount. I never had this problem with the original gridseed cpuminer and not with your early versioning. I believe ever since you updated the stratum code to fix a bug, those versions and on give problems.
I get the "debug: job not found" error all the time.
Also what is your advice on compiling for the Pi. Should I.use the cfflags ="03" option or the "March=armv6....." options that Mr Jinx suggested?
|
|
|
I've only been running it for a little while but 0.9e seems to be giving the same problems as 0.9d, for me (Windows version). i.e. too many rejects with message "DEBUG: reject reason: unknown-work". Who here on Windows is or is not having the same issue? I've gone back to using 0.9c, again - its working fantastic. Sandor do you think this issue is likely to be specific to my setup? You are the magic jesus of mining and I look forward to your reply. In 0.9d, new work is sent when there is a new job and after a nonce is found, in 0.9c it would stop hashing immediately and send the new work. The latter is actually inefficient and slows down the mining. Could you post a log with --debug and --protocol option enabled? Personally I'm still getting 0.2% rejects whatever the pool I go with. Same issue here still.too on Raspberrypi. I get a LOT of rejects, sometimes my pool shows.only 75% efficiency. I've tried different pools.with the same result. Tried with auto tune on and off, same result. Using version 0.9e. C worked the best so far. 5 chip miners, 21 per RasPi.
|
|
|
Looks like I spoke too soon. After about 15 minutes of hashing I start getting massive rejects. Pool shows 15% rejected right now.
These are the rejects I get:
DEBUG: reject reason: Job 'c907' not found
|
|
|
I'm getting a lot of rejects with cpuminer 0.9d. Didn't have this problem with 0.9c, I'm certain. Just me?
e.g. with 0.9c I was pleasantly surprised to see the poolside reject rate fall to a new all-time low of 0.38%. After switching to 0.9d, its gone up to 5.27% and climbing, and I can see reports of rejects locally a few times every minute. So I've gone back to 0.9c for now. Rejects such as:
"DEBUG: reject reason: unknown-work" "DEBUG: reject reason: high hash"
Rowan, I had the same issue, except mine was about 25% rejected. I was running on a Raspberry Pi. I updated to the latest firmware and made sure everything else was up to date, recompiled newest cpuminer with the config commands Mr Jinx suggested, and now it seems to be back to normal.
|
|
|
Just got my Pi in the mail this morning. I managed to install RASPBIAN and am able to work in it and SSH to it, so I am part way there. Can anyone point me in the direction for instructions on loading the latest CPUminer onto the Pi and getting it to run.
If you want to compile it yourself on a Pi use this: apt-get install -y build-essential libtool libcurl4-openssl-dev libncurses5-dev libudev-dev autoconf automake screen git clone https://github.com/siklon/cpuminer-gc3355 cd cpuminer-gc3355 sh ./autogen.sh ./configure CFLAGS="-march=armv6 -mfpu=vfp -mfloat-abi=hard" make Thanks Mr. Jinx! Can you explain these config commands? Where did you see that this is correct for the Pi. Sandor, can you chime in on this??
|
|
|
2 XBC sent to the wallet dev team. Thank you guys! That 2 XBC should be worth quite a bit soon.
|
|
|
WATER deposits and withdraw disabled on Bittrex. Anyone know why?
|
|
|
The list is growing. Please let me know so I can add your name to the
list. I lost tons of money in AC and would like this to be fixed. The
list so far:
AsiaCoin holders who wants to see a fix:
CryptoSteam Nicolaas.R silencesilence bluebit25 WildChaser777 istop08 GröBkAz Maxikosw (Maxikose on freenode irc) hrt cjp007 kache minuchi.str amit2007gunjan noobthegreat EEKman (Lost 3K USD. I feel you. I lost tons myself) Maestro1 Xuorc probrian artem6662 Shkembe Wolden probrian bittcoinn voisina jarserk dirtypolecat masterboy nin7672 syrota AC2 (1.35 million AsiaCoin) Alpinist (200K AC) Gambiman Deathtoallptots (130K AC) goldmann bitsta (Lost 25 BTC) ra1nb0wdash (Lost 3 BTC) ApoloTwo (lost 10BTC or 20 BTC on it ( i am not sure). ) georgeblair (680K AC) minuchi.str (Lost 17 BTC) BitcoinStacker crypto_bull (700K AC) Maestro1 (1 Million AC) Final nekokenny (49660 AC) CycleSurfer360 tarzanbigcity gaazje milan74 (5K AC) teringlijer (All his money in it) kalenen (Lost 440k of AC) LisboaKuya (lost 80k AC) richwang (The post growing fast, I am holding 100 000AC) bloodyboy (just when i was away for a while and have buy offer for about 900 satoshi this shit happend ;/ now i'm bagholder too...)
surgexvb (lost 9620.63971700 AC)
|
|
|
The freezing problem seems to have something to do.with the autotune feature. When enabled, it freezes every 2 hours or so everytime. When I disable it, now it has been running fine for 12 hours.
That's because the the autotune features prints a line immediately after another, so it's more likely to deadlock (tui_lock). Do you still experience freezing even with v0.9a? It should be a thing of the past now. Looks like "--freq=950" overrides the "--gc3355-freq=\\.\COM42:700" How could i set one device lower/higher than all the rest without typing each individually?
Edit: OK. I got it. I needed to write individual freq before the overall.
I'm pretty sure it's not the case. The most specific frequency is always applied. Thanks for your reply Sandor. One thing I have always wondered about is when I have multiple gridseeds, or any other ASIC for that matter, do the ASICS actually work together to solve the work that the pool gives, or is each ASIC on its own trying to solve the work. The reason I ask is I used to run individual cpuminer instances per ASIC, with each ASIC connected with its own worker name to the pool. With that method, each worker had a low difficulty appropriate for its hashrate. My hashrate was pretty consistent around 14,500 KH. Never went much below or.above that. Now, using your cpuminer, I have 21 gridseeds under one worker name, and since the hashrate is high, the pool gives them high difficulty. This results in my hashrate fluctuating anywhere from 9,500 KH to 17,000 KH. If each gridseed is indeed operating on its own, I would think the difficulty would be too high for a 340kh device and would be discarding work because it cannot solve it in time before the work becomes stale. Any insight into this would be much appreciated.
|
|
|
The freezing problem seems to have something to do.with the autotune feature. When enabled, it freezes every 2 hours or so everytime. When I disable it, now it has been running fine for 12 hours.
|
|
|
The previous update was working great, but the most recent after the TUI recode and stratum fix crashes after about 2 hours. The previous version was running solid for 15 hours until I stopped to update. I can still view the screen but all text has stopped updating on the worker is not online anymore. Very similar looking crash to the update from 2 revisions ago, before the "TUI stuck" issue was addressed. I'm sorry if this is no help. RBPi with 3.10.30+ kernel All updates done 21 5 chip miners
|
|
|
i keep getting failed to open /dev/ttyACM0
I am running on Raspberry pi: ./minerd --gc3355=/dev/ttyACM0,/dev/ttyACM1,/dev/ttyACM2,/dev/ttyACM3,/dev/ttyACM4,/dev/ttyACM5,/dev/ttyACM6,/dev/ttyACM7 --freq=1000 --gc3355-autotune --url=stratum+tcp://usa-1.liteguardian.com:3335 --userpass=cxxx:x --retries=5
I have the same problem ... I'm using Kernel ... 3.10.37+ I don't have any ttyACM0 in my dev folder ... got 9 Blades connected thru 2 x 10 port usb hubs ... working well with cgminer ... Having exactly the same issue, am I forgetting something or is there a workaround? I had the same problem trying to use cpuminer after having just used cgminer. Could not get a listing of any ttyACM devices. Quick fix was to reboot and start cpuminer without first using cgminer. Running it as root should clear up that problem. Thanks for the great work Sandor! Sent .04 btc your way!
|
|
|
Pool Hashrate: 491.33 MH/s Pool Workers: 119 Net Hashrate: 5,006.34 MH/s guess its working It's working And they just found their first post 200 block 86.26% efficiency though, eek.
|
|
|
paradice for asic owners anyone who pays for electricity should buy asics, period. I used to pay $350 a month for power to run 3 GPU rigs and get about 7MH, plus the issue of dealing with the heat. Now I pay about $15 a month for power and get 14MH, almost no heat. You do the math. Where did you get an ASIC miner with 14MH this early...? Three 5 MH ASICs? And where do you get 5MH ASICs? I got 40 Gridseed 330KH units for a killer deal.
|
|
|
|