Money arrived yesterday, still a very long wait....
Post
Topic
BoardExchanges
Re: MtGox withdrawal delays [Gathering]
by
lukcoin
on 07/05/2013, 19:07:39 UTC
Still waiting for a SEPA transfer from 2013-04-09... This is ridiculous, almost always the same standard replies. Hopefully my last more angry mail will trigger some action
Post
Topic
BoardBeginners & Help
Re: raspberry pi and ztex quad ?
by
lukcoin
on 27/08/2012, 13:15:56 UTC
Seems like there is a new firmware for the pi will try this later when I find the time, switching computer is a bit of a nuisance
Post
Topic
BoardBeginners & Help
Re: Introduce yourself :)
by
lukcoin
on 21/08/2012, 11:55:19 UTC
Been lurking for some weeks, bought a ztex quad and am now mining from my basement Let see where this bitcoin path will take us
1. Get donation 2. fund future mining rig 3. world domination *evil laughter*
1LnV4QivHfQmd6z3rphEPXyPhSkBqB7M6M
Post
Topic
BoardBeginners & Help
Re: raspberry pi and ztex quad ?
by
lukcoin
on 20/08/2012, 07:38:21 UTC
Moved to an old asus eee pc for now can't have the ztex sitting idle
Post
Topic
BoardBeginners & Help
Topic OP
raspberry pi and ztex quad ?
by
lukcoin
on 19/08/2012, 08:46:35 UTC
I was wondering if anyone has gotten their ztex 1.15y quad running with a raspberry pi ? While I can find some references to BTCMiner and cgminer running on the pi all tests where done with a 1.15x instead of the quad fpga version. All get is :
With cgminer:
[2012-08-19 08:39:15] Started cgminer 2.7.0 [2012-08-19 08:39:15] Ztex check device: Failed to read ztex descriptor with err -9 [2012-08-19 08:39:15] prepare device: -9
With BTCMiner:
sudo java -cp ZtexBTCMiner-120703-ARM.jar BTCMiner -m p -f ztex_ufm1_15y.ihx -host http://xxxx -u yyyyy -p pas
old: bus=001 device=37 (`037') ID=221a:100 Manufacturer="ZTEX" Product="USB-FPGA Module 1.15y (default)" SerialNumber="04A36E10AF" productID=10.15.0.0 fwVer=0 ifVer=1 FPGA unconfigured Error: Device lost after uploading Firmware: No new device found
Both miners where run as root to avoid problems, so I assume this has something to do with the limited USB capability of the PI. But even a powered USB hub doesn't seem to help