You're welcome I needed mine up for an extended period since I'm currently travelling overseas for a few weeks: uptime
14:50:40 up 28 days, 15:58 It's what happens when the coder has the hardware himself. |
|
|
|
|
The p2pool blockchain data is massive and the power of the wrt703n in the avalon is pitiful. Presumably it's the extra workload of dealing with that that uses a lot more CPU. Also the latency of an Avalon sucks dicks on p2pool, throwing out about 3% of work when the block change is 30s (it used to be much worse at 10s). You can run the Avalon on a regular PC via a USB cable to not have CPU usage problems but that won't fix the latency issues, as it is a major Avalon design flaw. p2pool has improved to work with ASICs, but now the hardware needs to catch up.
|
|
|
|
Why is it not possible to use socks5 proxy with stratum pool since cgminer 3.1.1?
It worked fine with 3.1.0.
Check 3.1.1 changelog |
|
|
|
|
Organofcorti did an analysis and found that variance would be kept to 1% if share return rate is 20-24 per minute. You return one share per minute on average per 71.6Mhash. So you get to 24 shares at 1.7GH. Using 1% variance as an arbitrary target, that means you should increase your diff by 1 for every 6 Erupters.
|
|
|
|
|
Finishing work fully taking 1.5 seconds is the same lacklustre problem as the Avalon design. That's on average .75 seconds of work wasted per 30 seconds on p2pool which is 2.5% of work lost. That's more than many pools' fees.
|
|
|
|
Is "gpu-dyninterval" : "7" only used when using "intensity" : d  yes |
|
|
|
With the new ASIC-compatible version of p2pool, is it still recommended to turn off queuing in cgminer?
Any input on this? I'm trying p2pool with my Jalapeņo and I'm curious if this still makes a difference. Don't turn off queueing. This is misguided information. |
|
|
|
Every Avalon will be different just like every GPU will be different so they'll all have different overclock abilities. ASICs like these have hardware errors all the time by design and they're harmless. Fanspeeds at 100% are probably a bad idea because of the poorly designed fan layout in the avalon, it will make the thinner 25mm thick fan blowing to the PSU fail to work because of massive case air pressure and the air will be going backwards. Reported fanspeeds are very inaccurate on the sensors so don't bother trying to compare small differences in their RPMs. With my firmware, hardware errors are not counted as hashrate, so any rise in hashrate reported is a real rise in throughput and should be your ultimate decider in how high you go. Anything else?  |
|
|
|
I think my internal router is dead, it stops always after some hours of hashing and shows nothing for fan or temp then anymore
What do I need to use it with cgminer on windows 7, which usb driver?
I started cgminer 3.3.1 and plugged the internal USB from avalon in, but It wont be recognized..
There is no avalon code built into the cgminer binary for windows for I figured someone would have to be crazy to try that with its lousy timing capabilities. Your choices are to build a windows binary for yourself with avalon support and use zadig to associate the avalon device with the WINUSB driver, and be the first person to try that combination, or use linux. |
|
|
|
openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory-20130723.bin 23-Jul-2013 07:06 3.8M
Anyone know what the changes are in this or anyone actually using next firmware from Avalon wiki
ckolivas any details on your next release for Avalon?
I'm still in Greece and will be for 2 more weeks. I had nothing to do with that firmware. |
|
|
|
|
I remember it happening before, numerous times.
|
|
|
|
Anyone have any clue why multiple people have noticed weird hashrate increases a few nights ago while using LTC in cgminer? See the posts here: https://bitcointalk.org/index.php?topic=260642.msg2789664#msg2789664Apparently over the night a few nights ago, while tinkering with my 7970 (which was not performing as well as it should be, but it never has), it just decided to work while I was sleeping. Upped the hashrate from 522KH/s to >700KH/s (which it should be getting) for no reason. I checked it's status the next morning, and it instantly decided to go back to it's slow 522KH/s. Havn't been able to get it back up to the faster speeds since. This wasn't just CGMiner mis-reporting the hashrate, either. The WU: rate was much higher than it had been. And other people have noticed similar issues. I'm not sure if their issue was the same night as mine, as I think our dates were 1 night off. Any help would be appreciated. Thanks! Totally bizarre, and apart from "maybe it was a cold night", I have no idea. Share submission certainly does have periods of higher luck overall and vice versa, but not the hashrate as you've described. |
|
|
|
|
You do not need to install ADL SDK. That's only for building cgminer.
|
|
|
|
Q: On linux I can see the /dev/ttyUSB* devices for my Icarus FPGAs, but
cgminer can't mine on them
A: Make sure you have the required priviledges to access the /dev/ttyUSB* devices:
sudo ls -las /dev/ttyUSB*
will give output like:
0 crw-rw---- 1 root dialout 188, 0 2012-09-11 13:49 /dev/ttyUSB0
This means your account must have the group 'dialout' or root privileges
To permanently give your account the 'dialout' group:
sudo usermod -G dialout -a `whoami`
Then logout and back in again
You are providing instructions from CGMINER 3.1.1 The opening post uses the current cgminer from git WHICH DOES NOT USE ttyUSB Don't confuse instructions from different versions please. |
|
|
|
|
Hmm that definitely seems wrong. I'm quite sure single ply should be for the little singles being one board and double ply for the singles being the long board and effectively two boards.
|
|
|
|
|
Check for antivirus software interfering, quietly sneaking in and deleting or disabling things.
|
|
|
|
This must be a simple mistake but why can CGminer run BTC all day but crashes on --scrypt in 3 seconds
Im missing some part of the drivers maybe ?
Different drivers work better for different mining types. |
|
|
|
I'm plagued with these stratum interrupted disconnects. Several of my miners will print a couple more lines and then just stop. Anything I can do to keep them running??? TIA
There's a bug in there somewhere which only recently got fixed in the git master code, so no official release has the fix. If you're building your own cgminer you can try it from git. Usually trying a different pool will make them go away as a workaround - it's a temporarily blocked network connection and pools with more resources don't suffer from it. There is also a stratum disconnect issue on windows from which cgminer never recovers, no idea if this one has been fixed with the latest changes or not. |
|
|
|
They would be properly priced at $25, NOT $300. Just an expensive toy.
Maybe they would if not for the principle of supply and demand. This discussion's been done to death in numerous other threads. Let's leave it that way. |
|
|
|
|
Show Posts
