Topic: Avalon ASIC users thread - page 57. (Read 438582 times)

for 4 modules 600$ and for 4 mini their write 60$

I was told to leave it at 24 but when I set it to 16 I found that my unit produced less overall hardware errors. Also I have my clocked to 400 mhz with a temperature intake at around 18c but when I do not cool the room the unit can get super hot and even puts off a nice smell so I am not so sure you want to run them OC without cooling or at least I wouldn't do it...

On the other hand anything over 400mhz produced way more hardware errors than I was tolerate of.

i just flashed my mini to CK 0821 firmware - overclocking the chips at 400 Mhz, question: for the miner count(default 24) in the cgminer configuration tab do i need to change the miner count to 16? cause i remember each module has 8 miner count and minis have only 2 module. would an erroneous miner count cause any problems?

any insight as to how i should proceed is greatly appreciated!

avalon mini overcloked  400mhz on btcguild 67.15 GH/s  HW 1.5%

just overcloked 2 unit at 401mhz

now it s better to buy 2 avalon mini instead a 4 modules

avalon mini is more stable

i just flashed my mini to CK 0821 firmware - overclocking the chips at 400 Mhz, question: for the miner count(default 24) in the cgminer configuration tab do i need to change the miner count to 16? cause i remember each module has 8 miner count and minis have only 2 module. would an erroneous miner count cause any problems?

any insight as to how i should proceed is greatly appreciated!

avalon mini overcloked  400mhz on btcguild 67.15 GH/s  HW 1.5%

just overcloked 2 unit at 401mhz

now it s better to buy 2 avalon mini instead a 4 modules

avalon mini is more stable

for 4 modules 600$ and for 4 mini their write 60$

I would recommend you install CK's latest firmware, I think that's still 0821. I have seen a couple of people complain they have had nothing but problems with the latest Avalon firmware installed on their machines.

Flash the machine with the CK firmware, do not restore the settings. And add your mining servers back manually and confirm if it's working.

I am not sure if you have are doing this, but my Avalon's are set to failover and I have two pools added to them, I found when I only added one Pool the hashing sometimes would not start at all, it's only when I added the second pool (as a failover) I didn't have any issues at all and at restart the hash kicks on pretty quickly.

Keep in mind when you update the firmware (pushing it back to CK's 0821) the default settings will be applied to the Avalon, so you will need to connect to it on 192.168.0.100.

When you connect a computer do your network does your computer get an IP address? If so there is a DHCP server (application if you want to call it) running likely on your internet modem or router. Avalon's by default enable DHCP server so you need to make sure this is disabled as two DHCP servers on the same subnet (192.168.0.xxx) will fight with one another as you are technically only supposed to have ONE DHCP server in your network environment.

So disable DHCP on your Avalon, assign the Avalon a static IP within the range that your DHCP doesn't operate in; example again DHCP servers may say the first IP is 192.168.0.100 with a pool of 50 so .150 is the last IP it will hand out. You have IP's 192.168.0.1 to .99 and .151 to .254 which you can statically assign out to your equipment. If you assign a DHCP server address statically when a second device grabs that IP from the DHCP server which doesn't know what machines have that IP assigned statically you will have an IP conflict problem between the two devices.

The last thing I forgot to ask or mention is plug your computer into your network and confirm you can get out on the internet. Then go to command prompt (if you are running windows) and type "ipconfig /all" without the quote, then look for the network adapter that has 192.168.0.x for the IP, copy down the numbers, IP, Subnet, Gateway, DNS.

On your Avalon you it should have it's own IP, subnet, the gateway must match what your computer says, and DNS I set mine to 8.8.8.8 which is Google's openDNS server.

I don't believe the --avalon-auto feature works with the mini, but like my mini which came with a 850W Gold Evermax PSU your's may have the same PSU (you'll have to check), my runs comfortably at 400Mhz doing 63 ~ 65GH/s.

First off, thank you ckolivas for all of your hard work, I will be sending another tip soon!

I just upgraded my mini's to your latest firmware and had a question about the --avalon-auto mode. On my Batch #2 Avalons this setting slowly tweaks the clockrate from my default 350 to find the sweet spot between hardware errors and hashrate and ends up at around 356-357. On my Mini's the clockrate stays at the default 375 so I was wondering if there was an upper limit in the --avalon-auto setting that prevents it from tweaking it since I've been able to run the mini at 400 but with a 3% error rate. Just curious!

Keep up the good work!