So why nobody is putting their old machines to support this network.  Actually it is not the coin that sucks, it is the community that does not support it.    There are no asics on the AGA network, still the coin looks pretty much as dead as the Amiga itself.

This did it for me.  I saved the settings once after a hard reset and then the wheel of death dissapeared

By the way this small FAQ comes from the author's Gogle + page.  

It was hard find this information, therefore I compiled it in one page and re-posted here for easer access:

#FAQ 001

my rig stuck on boot, its says "Looking for SLAX data in /slax"

mostly its caused by
* your usb flash drive are corrupted
* slax can't find your usb flash drive
* your usb controller aren't working or we dont have driver your your usb controller

solution
* clean up and check your flash drive, make sure its FAT32 formatted, delete [FLASHDRIVE:]\slax\changes content to make it back to factory settings
* put your flash disk to USB 2.0 port, if SLAX can't use your USB 3.0 controller
* most AMD based motherboard need IOMMU to be enabled in your motherboard BIOS in order your usb controller to be recognize by SLAX
* you can try put iommu=soft at boot option list


#FAQ  002

what is root password ? how do i change it?
its "toor" by default, you can change it by issuing command "passwd root"

#FAQ  003

how do i activate module (.sb file)

* you can activate modules on www.slax.org by issuing "slax active [module name]" while it running
* you can activate custom cryptoslax module (on official website) by downloading it first (you can use "wget [url to module]") then issuing "slax activate /path/to/downloaded/module"
* or you can simply put that .sb file into your flash drive at [FLASHDRIVE :]\slax\modules then boot it

#FAQ 004

how do i access and edit my files on CryptoSLAX system?

* you can use SMB service, on windows using your windows explorer type \\[YOUR RIG IP] , on OSX using your Finder, go to Connect menu and put "smb://[Your RIG IP]
* you can use SSH service, for example you can use WinSCP and connect with your Rig IP, on OSX you can use CyberDuck software

#FAQ  005

how do i auto-start miner on boot?

* SLAX will execute all executable files on /etc/rc.d/rc.xxxx on boot (runlevel 3) which is before X started, so any program that need to access GPU wont detect gpu at this time, therefore u need to autostart after X started (see below)
* CryptoSLAX also will execute all executable files on /root/.kde/Autostart/start.h and run it in background (no visible terminal)
* CryptoSLAX will execute all executable files on /root/.kde/Autostart/start.d and run it on KDE terminal inside screen session
* for miner program, i create it more easy by creating symbolic link to miner autostart-session.sh script inside /root/.kde/Autostart/start.d , so if you want to autostart miner, simply make autostart-session.sh executable by issuing "chmod +x /path/to/autostart-session.sh" and to disable it to being autostarted simply make it non-executable by issuing "chmod -x /path/to/autostart-session.sh"

you need the module coreutil.sb that you can grab from slax site or that you can directly activate in the console:

 or perhaps that is:
 I dont know I didn't try, but I did try this

then you navigate under the directory /opt/miners There are all the miners you want to modify or to add new ones.

to add the optimized X11mod :


then modify mining.conf with your user data

and you are good to go with ./start.sh under that directory

If you want to preciously keep the install you made as a module, once you are done playing with it, just try:


That should save your install under modules directory. Not sure how this works however, because those changes are already saved.  The module conversion is useful only to be reused in another live Cryptslax USB distro without having to go through all the above. Or if you want to erase the changes directory because you've messed things up and need to reset them in the original state.  

Repeat the same process for any other mining software you wish to install.

If you have questions, dont ask me, I have no idea! I just found this stuff by tinkering around with cryptoslax..

I explained to the store that these cards were all burning even though held at optimum conditions. They apparently tested them and they sent me today 3 replacements but with Sapphire R9 280 instead of HD 7950.  (Not the 280X version!).  i think it is essentially the same card but just a different series.

I still have another 3 burned 7950 cards to send back, but they said that it would be ok to replace those too with R9 280.

The fact is that the HD 7950s fire up at a whopping 300 W against 220 W for the R9 280, while having a slightly higher hashrate.  So I'm happy to exchange them.

I had bought 7 actually from this famous 11196-19-20G serie, SN A13510xxxxxxxx

Thay ran fine 24/7 for a few days... then one after the other 6 out of 7 were out.  Three of them in the spectacular purple smoke fashion described above. 

In the begining I was suspecting power variations and I ran out and bought a power stabiliser.  But that did not prevent another 7950 to burn right before my eyes.

Power supplies (by the way two of them do not work any longer following the purple somke episodes) were 80 plus gold or platinum. I did not overclock my cards while mining and tried to keep them as cool as possible with latteral fans blowing on both sides.  Temperatures stayed always below 68° C.

I checked out in the internet and apparently there are several similar stories with these cards. 

I had also several 270x from Sapphire in the same rigs that the faulty 7950 and they seem to run fine despite the sparks and smoke that burnt the 7950.

I also have other cards and not a single one of my other cards have had a glitch. I am not an expert but clearly the 7950 (or at least the 11196-19-20G serie) are unreliable compared to other models.