... Basically i've told the Mrs to ask me before she does anything with electric........ like cook, make a cup of tea, shower.... anything has to be checked with me first 
What is plan B?
Topic: Avalon ASIC users thread - page 163. (Read 438516 times)
What is plan B?
Oh really? Wasn't this a necessity in the olden days?
To get my avalons stable I had to change the clock values to 36:xxx in /etc/init.d/cgminer. With the standard values from stromborn's firmware, the avalons restarted every 5-10minutes.
greets,
ebereon
are you still running stock psu on 365?
Sweet.
And now for a stupidly simple question: is there a way to initially configure the Miner for first use (connect to WiFi) without connecting a laptop directly? I don't have a comp-to-comp lan cable around.
Just use a standard network cable. All network cards doing this automaticaly. No need of a "comp-to-comp" cable. And now for a stupidly simple question: is there a way to initially configure the Miner for first use (connect to WiFi) without connecting a laptop directly? I don't have a comp-to-comp lan cable around.
Sweet.
And now for a stupidly simple question: is there a way to initially configure the Miner for first use (connect to WiFi) without connecting a laptop directly? I don't have a comp-to-comp lan cable around.
And now for a stupidly simple question: is there a way to initially configure the Miner for first use (connect to WiFi) without connecting a laptop directly? I don't have a comp-to-comp lan cable around.
The default network setup is:
LAN: fixed IP (192.168.0.100)
WWAN (wifi): DHCP
Not sure if it roams onto any wifi network available, but if you hook it up, and it gets a DHCP address, you can either figure out that IP address from your network router that issues DHCP or just guess it (or use nmap -sP) and surf to the Avalon
If the yellow light goes out, then it's hashing using the default cgminer config so you'll know if it gets online (takes about 30 seconds)
Sweet.
And now for a stupidly simple question: is there a way to initially configure the Miner for first use (connect to WiFi) without connecting a laptop directly? I don't have a comp-to-comp lan cable around.
And now for a stupidly simple question: is there a way to initially configure the Miner for first use (connect to WiFi) without connecting a laptop directly? I don't have a comp-to-comp lan cable around.
Can Avalons mine on P2Pool yet? I searched the thread and spotted only problems so far.
Has anyone managed to destroy a module yet by overclocking or are there really enough safeguards to disallow this?
I tried some settings with p2pool but nothing. If I use the avalon branch and the start cgminer with --fix-protocol i get messages from p2pool like "Couldn't link returned work's merkle root with its handler. This should only happen if this process was recently restarted!"... So no success here :-(Has anyone managed to destroy a module yet by overclocking or are there really enough safeguards to disallow this?
You can destroy chips with high temperature. So if you want to overclock, make sure your temps are low like:
Here is my setup. The Avalons blow outsite the room in to a "roof room" ~1 meter hight, ~1.5 meter width, ~20 meter long:
To get my avalons stable I had to change the clock values to 36:xxx in /etc/init.d/cgminer. With the standard values from stromborn's firmware, the avalons restarted every 5-10minutes.
greets,
ebereon
Apparently I am not aloud to pull more than 5kwh
This is not normal. Typical Dutch homes have 1-3 main fuses of 25 Amps.
You can upgrade these to 3 x 35 Amps but then you have to pay 70 euro a month extra.
One 25A fuse allows usage of ~6000 W/h.
Dc-Dc TPS40193 max 20A
Chip max current is 2A
10x2A max =20A max
it should be safe enough
Chip max current is 2A
10x2A max =20A max
it should be safe enough
Can Avalons mine on P2Pool yet? I searched the thread and spotted only problems so far.
Has anyone managed to destroy a module yet by overclocking or are there really enough safeguards to disallow this?
Has anyone managed to destroy a module yet by overclocking or are there really enough safeguards to disallow this?
Apparently I am not aloud to pull more than 5kwh
Could it be that the service is inadequate to meet your present needs? Or is it some kind of condo association rule?
4 avalons 50usb erypters, oven tv, laptop 450w of electrics. ..... the kettle pushed it over the edge
heh kettle is always the last drop 
Blew my main fuse........ engineer on way, fun times ahead explaining why I pull so much power.....
How much power?
Whats the easiest way to switch my avalon to using an ethernet cord versus wifi. I tried following the instructions on the wiki last time and it had locked me out. Took me almost 4 hours to try and figure out how to get access to the avalon.
Anyone know what the settings would be for an overlock to 345mhz? I was running these with the Strombom firmware and appeared to get lesser hw errors
I haven't included support for 345Ok, so I guess strombom had some custom additional modifications in his firmware? In his firmware the 345mhz seems to be the sweet spot for me.
I am currently getting around a 2.3% HW error rate using the (hw/diff1shares+hw formula). Accepted shares 7555, HW 12034. Does this seem to high?
Thanks
Thanks Noted.
However I have reverted to the strombom modified firmware because the 345mhz seems to yield the lowest amount of hw errors (0.39%) and about the same hash rate as 350mhz. The only caveat are the fans running at full speed that sound like a mini jet, but I would rather have the fans failed than the slight potential of shortening the life of the chips with an increase HW error rate.
Is there any modification that could be made to lower the speed of the fans (via ssh) or is a full recompile the only way?
running perfect so far with an uptime of around 2hrs on 345.... cheers for the tip!
I had some problems from the start with it
It stopped hashing and I`m trying to fix it.
A solution is near (maybe is better as I did not change the power supply hashing at about 58k up from 47k )
It stopped hashing and I`m trying to fix it.
A solution is near
(maybe is better as I did not change the power supply hashing at about 58k up from 47k ) the stromborn version has this values
case "$_cf" in
256)
CF="50:256"
;;
270)
CF="47:270"
;;
282)
CF="45:282"
;;
300)
CF="40:300"
;;
305)
CF="39:305"
;;
310)
CF="38:310"
;;
315)
CF="38:315"
;;
320)
CF="37:320"
;;
325)
CF="36:325"
;;
330)
CF="36:330"
;;
335)
CF="35:335"
;;
340)
CF="35:340"
;;
345)
CF="34:345"
;;
350)
CF="34:350"
;;
355)
CF="33:355"
;;
360)
CF="33:360"
;;
365)
CF="32:365"
;;
370)
CF="32:370"
;;
375)
CF="32:375"
;;
380)
CF="31:380"
;;
385)
CF="31:385"
;;
390)
CF="30:390"
;;
395)
CF="30:395"
;;
esac
my sweet spot is 355 but I have only 2 modules Avalon V1
I think that the hw rate is dependent on the controller + temp
I had 0,4% increase in hw with 370 but I have already a broken module so 355 is better
case "$_cf" in
256)
CF="50:256"
;;
270)
CF="47:270"
;;
282)
CF="45:282"
;;
300)
CF="40:300"
;;
305)
CF="39:305"
;;
310)
CF="38:310"
;;
315)
CF="38:315"
;;
320)
CF="37:320"
;;
325)
CF="36:325"
;;
330)
CF="36:330"
;;
335)
CF="35:335"
;;
340)
CF="35:340"
;;
345)
CF="34:345"
;;
350)
CF="34:350"
;;
355)
CF="33:355"
;;
360)
CF="33:360"
;;
365)
CF="32:365"
;;
370)
CF="32:370"
;;
375)
CF="32:375"
;;
380)
CF="31:380"
;;
385)
CF="31:385"
;;
390)
CF="30:390"
;;
395)
CF="30:395"
;;
esac
my sweet spot is 355 but I have only 2 modules Avalon V1
I think that the hw rate is dependent on the controller + temp
I had 0,4% increase in hw with 370 but I have already a broken module so 355 is better
They will not work with the default official firmware if you just insert them inside. Tried and was unable to get some configs, I am assuming the firmware has to support certain speeds like 345, 355, etc
Btw, how did you break a module ?
the stromborn version has this values
case "$_cf" in
256)
CF="50:256"
;;
270)
CF="47:270"
;;
282)
CF="45:282"
;;
300)
CF="40:300"
;;
305)
CF="39:305"
;;
310)
CF="38:310"
;;
315)
CF="38:315"
;;
320)
CF="37:320"
;;
325)
CF="36:325"
;;
330)
CF="36:330"
;;
335)
CF="35:335"
;;
340)
CF="35:340"
;;
345)
CF="34:345"
;;
350)
CF="34:350"
;;
355)
CF="33:355"
;;
360)
CF="33:360"
;;
365)
CF="32:365"
;;
370)
CF="32:370"
;;
375)
CF="32:375"
;;
380)
CF="31:380"
;;
385)
CF="31:385"
;;
390)
CF="30:390"
;;
395)
CF="30:395"
;;
esac
my sweet spot is 355 but I have only 2 modules Avalon V1
I think that the hw rate is dependent on the controller + temp
I had 0,4% increase in hw with 370 but I have already a broken module so 355 is better
case "$_cf" in
256)
CF="50:256"
;;
270)
CF="47:270"
;;
282)
CF="45:282"
;;
300)
CF="40:300"
;;
305)
CF="39:305"
;;
310)
CF="38:310"
;;
315)
CF="38:315"
;;
320)
CF="37:320"
;;
325)
CF="36:325"
;;
330)
CF="36:330"
;;
335)
CF="35:335"
;;
340)
CF="35:340"
;;
345)
CF="34:345"
;;
350)
CF="34:350"
;;
355)
CF="33:355"
;;
360)
CF="33:360"
;;
365)
CF="32:365"
;;
370)
CF="32:370"
;;
375)
CF="32:375"
;;
380)
CF="31:380"
;;
385)
CF="31:385"
;;
390)
CF="30:390"
;;
395)
CF="30:395"
;;
esac
my sweet spot is 355 but I have only 2 modules Avalon V1
I think that the hw rate is dependent on the controller + temp
I had 0,4% increase in hw with 370 but I have already a broken module so 355 is better
They will not work with the default official firmware if you just insert them inside. Tried and was unable, I am assuming the firmware has to support certain speeds like 345, etc
Of course they will not work. you need to run patched cgminer. strombom could you please post the patch? It will be of great use for some of us
the stromborn version has this values
case "$_cf" in
256)
CF="50:256"
;;
270)
CF="47:270"
;;
282)
CF="45:282"
;;
300)
CF="40:300"
;;
305)
CF="39:305"
;;
310)
CF="38:310"
;;
315)
CF="38:315"
;;
320)
CF="37:320"
;;
325)
CF="36:325"
;;
330)
CF="36:330"
;;
335)
CF="35:335"
;;
340)
CF="35:340"
;;
345)
CF="34:345"
;;
350)
CF="34:350"
;;
355)
CF="33:355"
;;
360)
CF="33:360"
;;
365)
CF="32:365"
;;
370)
CF="32:370"
;;
375)
CF="32:375"
;;
380)
CF="31:380"
;;
385)
CF="31:385"
;;
390)
CF="30:390"
;;
395)
CF="30:395"
;;
esac
my sweet spot is 355 but I have only 2 modules Avalon V1
I think that the hw rate is dependent on the controller + temp
I had 0,4% increase in hw with 370 but I have already a broken module so 355 is better
case "$_cf" in
256)
CF="50:256"
;;
270)
CF="47:270"
;;
282)
CF="45:282"
;;
300)
CF="40:300"
;;
305)
CF="39:305"
;;
310)
CF="38:310"
;;
315)
CF="38:315"
;;
320)
CF="37:320"
;;
325)
CF="36:325"
;;
330)
CF="36:330"
;;
335)
CF="35:335"
;;
340)
CF="35:340"
;;
345)
CF="34:345"
;;
350)
CF="34:350"
;;
355)
CF="33:355"
;;
360)
CF="33:360"
;;
365)
CF="32:365"
;;
370)
CF="32:370"
;;
375)
CF="32:375"
;;
380)
CF="31:380"
;;
385)
CF="31:385"
;;
390)
CF="30:390"
;;
395)
CF="30:395"
;;
esac
my sweet spot is 355 but I have only 2 modules Avalon V1
I think that the hw rate is dependent on the controller + temp
I had 0,4% increase in hw with 370 but I have already a broken module so 355 is better
They will not work with the default official firmware if you just insert them inside. Tried and was unable to get some configs, I am assuming the firmware has to support certain speeds like 345, 355, etc
Btw, how did you break a module ?
Compile. There's no command outside of what the driver does internally to change fanspeed. It's very hard to make some kind of meaningful interface to control that when most users rely on the web UI and changes to that lag far behind any command lines I add. Maybe I can add some command line parameters and you could add them to the "more options" section.
Jump to: