Long time no talk, the old, now defunct, PlanetCrypto here (forgot password & lost email account when we shut it down 5+ years ago). Since BM no longer releases the data sheets Sidehack had to manually debug the signals/commands and timing for the 1397 and then supplied that info to Kano to work into the driver. Looking at older chips data sheets it is obvious that Bitmain plays around with different timing specs for the internal circuits - none of them are the same. Or are the comms too different?I highly doubt a simple 'drop-in' replacement is possible. If one replaced the 1397 w/ a 1398 on the Compac F would your driver for CGminer work? I run all of them at 400Mhz averaging around 250Ghs, but 1 always come down to around 115 MHz / 120GHsīeen looking for the Gekkoscience hubs on ebay as well, but havnt seen the German " Go F yourself" guy. I thought it was the inconsistentcy of power distribution when all 4 sticks are plugged in to each of the hubs. I got 8 of them, runnin on the bitcoinmerch hub. ![]() I have the same issue with 1 of my stick too, but I couldnt find out which stick it was. I offered him $500, and he told me to go F myself ¯\_ (ツ)_/¯ hopefully there in stock again soon. There is a guy in Germany selling 2 hubs on Ebay for like 1500 Euros ($1700) +$160 shipping. If only I could find more gekko hubs, Id buy some more. so i turned back up a bit, but not as much as I had before. Which is still amazing.Īnd I did dial back the volt screw. 3 were getting about 360ghs, and 1 was at 340. Since i got the Gekko hub I ramped them up (incrementally) to 550mhz. 0: GSF 0 - CompacF Bitcoin Miner (10050211) 0: GSF 0 - plateau adjust: target frequency 85.00MHz Stratum from pool 0 requested work restart 0: GSF 0 - set ticket to 0xe0/8 work 8/8.0 ![]() 0: GSF 0 - setting bauddiv : 00 61 (ftdi/2)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |