Bitcoin Forum
June 29, 2024, 02:12:26 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Hardware / Re: GekkoScience NewPac / Terminus R606 (BM1387) Official Support Thread on: December 19, 2019, 07:25:25 PM
try poolin.com.

I have, and they certainly work well. I've tried Slushpool a few more times since my original post and have basically confirmed that something is messed up between Slushpool and my Newpacs for some reason. I've consistently used Bitcoin.com's auto-profit-switching mining pool for bitcoin and bitcoin-cash and can consistently see 7 of 8 of my Newpacs hitting a stable 650MHz and reaching a stable combined hashrate of 1.1THs. This is usually for the first few hours of mining, then one of the 'good' 7 newpacs will back off to about 644MHz or less, and the one sub-par newpac only hitting 500MHz or less.

I'm planning on expanding my setup to a total of 12 Newpacs, ideally all, or most, runnning at 650MHz (or even an even 700MHz), possibly getting me a total of 1.5THs or even 2THs. All of the Newpacs I have so far that can reach a stable 650MHz have shown a hashrate of around 140GHs. I'd like to use the Newpacs to mine Bitcoin-cash, and my Antminer to mine on ProHashing.com, where they can auto-switch between many different SHA256 crypto-currencies.  
2  Bitcoin / Hardware / Re: GekkoScience NewPac / Terminus R606 (BM1387) Official Support Thread on: December 13, 2019, 03:25:07 AM
I have an interesting problem. Up until this past Sunday, I was getting almost 1.1TH/s with eight Newpacs on a Sipolar 20-port, 200W, 40Amp, USB 3.0 hub. I know all of my Newpacs are getting the power they need. I even have 4 fans blowing on them at all times when operating. Specifically, I have three 140mm fans and one desktop USB speed-adjustable fan. Two of the 140's are blowing down from above and the third is 'exhausting' warm air to the side. The desktop USB fan is pointed directly at the front of my setup at max speed.

As of now, as shown by the pic below, even setting it at 100MHz still results in "missing nonces from chip[0]" errors and automatic ASIC Plateau adjustments to well below what I set the frequency at. Oddly enough, I seem to only encounter this behavior with my Newpacs on Slushpool stratums and no where else. I've switched to a few different Slushpool stratums and nothing helps. This is especially wierd since I have a used Antminer S9 hashing away with no issues on the US-East Slushpool stratum, even with the "Hashrate+2.0THs" option enabled. Temps hover between 69C on the hottest board and 67C on the coolest one.

https://imgur.com/a/FI85oC8

https://imgur.com/a/zqiWO4M

And below is the current operational behavior on that Bitcoin.com pool (normal behavior for my Newpacs, might bump them back up to 600 or even 650 later):

https://imgur.com/a/FVOTeUZ

I'd ultimately like to go back to Slushpool, but if its going to treat my precious babies like crap, then no more Slushpool for me! Any recommendations for auto-profit switching SHA256 pools would also be appreciated.
3  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] Dogethereum | Fork 10 000:1 of DOGE on: November 03, 2019, 02:17:22 PM
Just started mining DogX and so far like the hashrates I'm getting. But I'm having a "weird" problem with the Dogethereum wallet client that I'm using. I understand that the client has to download the blockchain in order to ensure that the transactions to and from your account are valid, but I would like to point the client to a different folder when downloading all that data. My primary drive (C drive) is an SSD and it is at roughly 70% capacity at the moment. I have a second, similarly sized SSD (D drive) purely for data storage that is mostly empty currently. I want to install the wallet into and have the blockchain download to the D drive. I've tried to uninstall and reinstall the wallet several times and tried to point the wallet to the drive with more space but have had no luck in changing the download location of the blockchain data. Any advice would be appreciated>
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!