I have a couple of what will probably be simple questions. My Avalon6 is currently in transit, so I thought I would get the RPi environment all worked out before it arrives.
I started with the image that was provided by Notlist3d. This a bit shy of 4G and was rigged for DHCP. I got that flashed onto a card, and Model B Pi that I have seemed boot just fine. I was able to get in via the web interface using just "admin" for the Id (no password). Obviously a bunch of stuff is blank/empty since there is nothing connected to the USB port. All looking good.
What I have found so far is a NO way to "Shutdown" the Pi from the web GUI. Maybe its buried somewhere and I am just not seeing it. I am really reluctant to just yank the power on a Ri for fear of corrupting the SD card. I found a Reboot button that works great, but no "Shutdown". Any comments/thoughts?
I then thought I would do the "Set a password and enable SSH" thing. I am really not understanding how to correctly operate that page. I can enter a password and confirm it just fine, but it seems to have zero effect. I am also confused by the Id that I am setting the password for. Is it "root" or "admin". Any comments on the userid/password structure that is in place would be greatly appreciated.
I also looked at the ehash website and found a variety of firmware versions, all from different dates. I also see multiple files for each date. It would be really good to know exactly which one I need to flash, and what it's expectations are in terms of network environment (DHCP, Static, etc). I am also surprised by the fact that the largest one is but a mere 76Mbyte in size, way smaller than the 3.9 Gbyte image I started with. I can obviously try some of these things to see what happens, but thought I would see what the collective wisdom is one some of the more mundane "System Admin" tasks for the Rpi in this environment. I have a comfortable grasp of Raspbian on the Pi, but OpenWrt is way new for me.
On firmware I wanted to distribute a untouched copy of BlockC's kit at time of release. So I left it without being in a zip/rar file. I do have a .rar that is around 600 MB if anyone needs it. I might be taking it for granted on my internet speed, I just liked that I felt it was almost from kit to users on here without me zipping it up.
Biggest thing I changed on it myself after is static IP. The DHCP is a great option for install as is not configured for a different IP range then some users. But I hate it jumping around as I do like to monitor gear. So I suggest going to static after you get it up on network.
I have a way of operating if it works don't mess with it, unless big issue fixed. I have had Avalon 6's since first hit market and never updated the firmware. You could do a MM update on gear, but I have been happy with it. The fixes are all listed here:
https://en.bitcoin.it/wiki/Avalon6#AUC2_Firmware So it really is personal preference I don't think there is a wrong choice.
I don't think there are any mundane tasks you need to do, beside checking and making sure you are hashing. Which as a miner I have always enjoyed monitoring. In my opinion Avalon did a great job with the miner. Below you will see about a month of running without doing any tasks:
So really very stable any not something I have had any tasks that needed repeated to keep it going.