 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
|
Have you tried any clock rates higher than this? What was the highest stable?
What is the wall voltage you are using?
Presumably PSU efficiency will be higher for higher incoming voltages.
Either way, very nice and thanks for the post!
|
|
|
|
|
I recently tried to flash my 2nd Gen 3-card Avalon with the latest CGMiner firmware, but after restarting the box it doesn't seem to start hashing. I finally just reverted back to the August firmware and restarted the box. Everything started hashing immediately again.
Did something change in the latest version that requires the configuration parameters to change or something? Perhaps is the November firmware not intended for the 2nd gen avalon?
Any pointers greatly appreciated!
|
|
|
|
|
I have been mining for 21 hours @ 15MH/s with auto trade enabled and my account shows less than .06 BTC. Is this normal or are payouts lagged somehow? I can count numerous transactions estimating far more than this amount. Something seems very wrong here.
|
|
|
|
ck.kolivas.org is down :/ mirror needed  Again, to repeat. Opening post, mirror of files. That mirror doesn't contain the compiled avalon firmwares though does it? |
|
|
|
I just had an avalon that was running fine for weeks suddenly stop working  Red/yellow lights are on. The miner starts but it never does any work (hashrate is 0) Where should I start looking for the problem? I had one do something similar. It turned out to be a bad USB cable connection inside of the case. The cable that runs from the built-in router to the front of the case makes poor contact with the hub where all of the power and data cables connect. Try pushing the cable to the right or left of the socket. My theory is the vibration of the fans eventually wiggled the cable enough to get it to disconnect. Good luck! |
|
|
|
|
Hi All,
So I am seeing this appear over and over in the System Log, but my other Avalon boxes have no such problem:
Sun Aug 18 11:48:49 2013 auth.info kernel: [ 558.900000] usb 1-1: USB disconnect, device number 36
Sun Aug 18 11:48:49 2013 auth.info kernel: [ 558.910000] usb 1-1.1: USB disconnect, device number 37
Sun Aug 18 11:48:50 2013 auth.info kernel: [ 559.210000] usb 1-1: new high-speed USB device number 38 using ehci-platform
Sun Aug 18 11:48:50 2013 auth.info kernel: [ 559.380000] hub 1-1:1.0: USB hub found
Sun Aug 18 11:48:50 2013 auth.info kernel: [ 559.380000] hub 1-1:1.0: 2 ports detected
Sun Aug 18 11:48:50 2013 auth.info kernel: [ 559.660000] usb 1-1.1: new full-speed USB device number 39 using ehci-platform
Sun Aug 18 11:48:50 2013 auth.info kernel: [ 559.810000] ftdi_sio 1-1.1:1.0: FTDI USB Serial Device converter detected
Sun Aug 18 11:48:50 2013 auth.info kernel: [ 559.820000] usb 1-1.1: Detected FT232RL
Sun Aug 18 11:48:50 2013 auth.info kernel: [ 559.820000] usb 1-1.1: Number of endpoints 2
Sun Aug 18 11:48:50 2013 auth.info kernel: [ 559.820000] usb 1-1.1: Endpoint 1 MaxPacketSize 16384
Sun Aug 18 11:48:50 2013 auth.info kernel: [ 559.830000] usb 1-1.1: Endpoint 2 MaxPacketSize 16384
Sun Aug 18 11:48:50 2013 auth.info kernel: [ 559.830000] usb 1-1.1: Setting MaxPacketSize 64
Sun Aug 18 11:48:50 2013 auth.info kernel: [ 559.840000] usb 1-1.1: FTDI USB Serial Device converter now attached to ttyUSB0
Sun Aug 18 11:48:51 2013 auth.info kernel: [ 560.970000] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Sun Aug 18 11:48:51 2013 auth.info kernel: [ 560.990000] ftdi_sio 1-1.1:1.0: device disconnected
Sun Aug 18 11:49:12 2013 auth.info kernel: [ 581.570000] usb 1-1: USB disconnect, device number 38
Sun Aug 18 11:49:12 2013 auth.info kernel: [ 581.570000] usb 1-1.1: USB disconnect, device number 39
Sun Aug 18 11:49:12 2013 auth.info kernel: [ 581.880000] usb 1-1: new high-speed USB device number 40 using ehci-platform
Sun Aug 18 11:49:12 2013 auth.info kernel: [ 582.050000] hub 1-1:1.0: USB hub found
Sun Aug 18 11:49:12 2013 auth.info kernel: [ 582.050000] hub 1-1:1.0: 2 ports detected
I noticed that my box's hash rate started resetting to 0 MH/s and then climbing back up to 70 or so. It did this once before right when I first got my Avalon and I couldn't figure out why. I moved the box around a bit and the issue went away ever since.
Fast forward a month: I had to re-arrange some hardware recently and my Avalon ran fine for a day, then stopped hashing last night. I restarted it and then it ran fine for several hours. When I log in, I see the above in the logs, the 5 second average hash rate climbs up to the 70 or so GH/s then resets to 0 and repeats.
It seems to me that maybe I have a bad hub connection judging by the logs. Currently I have it set to run at 300 MHz, but it has no problems hitting 345 MHz and ran for a month just fine before I moved it around. WiFi is disabled, etc.
Anyone else experienced problems like this? How did you resolve it?
|
|
|
|
|
I would love for this new card to be real, but I have a hard time believing this is achievable. I hope someone can prove me wrong. Let's look at this from a competition perspective:
Avalon: 110nm, 67 GH/s, 600+ watts
BFL: 65nm, 60 GH/s, 300+ watts
KNC Miner: 28nm, 400+ GH/s, ~1,000 watts (Yet to be seen)
BFL Monarch: 28nm, 600 GH/s, 350 watts
So the die size cutting nearly in half from the Avalon's 110nm to the BFL's 65nm cut the power in half for roughly the same performance (60-67 GH/s). Avalon is 600+ watts, BFL single is 300+ watts. Makes sense.
One would assume that cutting the die size in half again to 28nm from 65nm would allow the power to be cut in half again for the same 60 GH/s performance. Let's assume it consumes 150 watts as a result (half that of a Single). Seems reasonable.
But now let's assume instead of 60GH/s, the performance is going to be 600 GH/s. If we are going to increase the hash rate by 10x, then the power requirement will also likely increase by 10x. That means the power should be roughly 1,500 watts (about the maximum you can safely draw from a single residential power circuit in the US).
If memory serves me correctly, KNC miner estimated 1,000 watts for their rig. If the BFL Monarch is going to perform 50% greater and the same die size, then power draw naturally would also seem to be 50% greater. So, that seems consistent with my 1,500 watt figure above.
It would be great to get some clarification from BFL on this before placing orders.
Thoughts anyone?
|
|
|
|
What does CDF mean and how is it calculated?
http://en.m.wikipedia.org/wiki/Cumulative_distribution_functionBasically, it shows the odds of a block being found now. Around 60% is when you reach the current difficulty in shares. It will never reach 100% because you can't know for sure when you'll find a block, obviously. Thanks for the explanation. Looks like we're on another long round again. CDF is currently over 71%. |
|
|
|
Why isn't doublec on the scammer list yet? He stole hundreds of NMC from www.exchange.bitparking.com just from me. A few months ago he told me don't worry you are on the queue... and now he refuses to answer his bitmessages. I have a hard time believing this. A long time ago, I inadvertently sent some bitcoins (like $150 worth at the time) to a wrong address. It turned out to be an old mining pool address DoubleC was running. I contacted him, explained what happened, and he actually dug out the old files to his pool, retrieved the coins and sent them back to me. I knew from then on that he's an honest man. He could have easily just ignored my message. |
|
|
|
|
Did you happen to have other items listed for sale on eBay at the same time as your Avalon? It could be that the thief bought one of your other items to get your address.
|
|
|
|
|
I just came to say Bitparking is the best pool! You rock DoubleC!
|
|
|
|
|
Still having problems on one of my Avalon boxes. I've updated the firmware, disabled Wi-Fi, fuse is not present, ran at minimum 256 MHz, checked cables, and it still stops after mining for just a couple of minutes. Hash rate goes all over the place too. It eventually drops to zero and the LED stays yellow.
Any suggestions?
|
|
|
|
|
I received my Avalon boxes today, but one of them has severe problems:
All of them hash just fine at 300 MHz, but one of them only works if I set it to 256 (but still problems).
When it starts hashing, it will climb to about 66 GH, but then resets every 1-5 minutes, sometimes resets even quicker.
This box had an older firmware on it than my other ones. It had 3.1.1 instead of 3.2.1 (I think).
The temperatures seem to be pretty normal. But it just resets a lot. Sometimes it will not start again even if I stop and start the service, and I have to power off and on again.
What are some things I can do to troubleshoot the issues with this box?
|
|
|
|
Seems my 13XX order is closing.  please elaborate what you mean. Do you mean it has shipped? I am pretty sure he means "closing in" which means "getting closer." I had placed an order on the 18th as well, first thing when they went online, and I have yet to receive any shipping updates. |
|
|
|
I switched all of my machines over to d=2, and initially as I was halfway through switching them I was still seeing rejects. At some point along the way, all started working without rejects. Not sure if it was the complete change-over, or DoubleC made some fixes but either way bitparking is working great again!  And, as always, thanks again to DoubleC for a fine pool and excellent support! |
|
|
|
The other thing I don't do is manually set my difficulty. I noticed others here are doing that, but is it necessary? My rigs range from about 800 MH/s to 1.8 GH/s.
You are the third one in a row, if you read the last 3 pages. This problem is caused by the fact that BitParking sets the default difficulty to 16, which is too high for GPU/FPGA mining. You should use "d=1" or "d=2" as your password to set the difficulty lower. This will avoid inactivity timeouts and stratum disconnections. Even though my rigs are 800 MH/s to 1.8 GH/s, my total farm is 23 GH/s. Is it still advised that I change them all to d=2, or does it make a difference if my entire farm is 23 GH/s? Still seeing the problem, but haven't changed any difficulty settings yet. Also, running cgminer 3.1.1 |
|
|
|
No issues here... Do you by any chance have also LTC config and you have just switch back to BTC? I know that someone did scrypt mining on this pool some time back...
No, nothing like that. I configure everything from a batch file. I am seeing a lot of "Stratum connection to pool 0 interrupted" errors, and then all shares are rejected after that until the pool connects again. The other thing I don't do is manually set my difficulty. I noticed others here are doing that, but is it necessary? My rigs range from about 800 MH/s to 1.8 GH/s. |
|
|
|
|
Im getting a crazy amount of rejects from many of my miners. Anyone else having this issue?
|
|
|
|
|
