|
247G best share - come on little ASIC chips, you can do 100x that and get us a block.
|
|
|
|
|
38sT5ANJa5bkbZ4HgWwF8RWHGRfpeFzdon for my payout when we hit a few blocks!
|
|
|
|
since a single newer ASIC is going to eat around 3 kwh per day. Not correct. Kwh is total power over time. The newer ASIC's constantly consume over 3kw at any given point in time and that works out to over 72kwh per 24-hour day. Oops, you're right, I'll fix it. Thanks! |
|
|
|
I recommend something like this:
...
That way you never stop mining even after software miner crash, it just restarts automatically.
Thanks, wrapped the start shell script in that. |
|
|
|
|
I'll join again if there is room. Hopefully with a much lower diff!
|
|
|
|
That is interesting indeed. What I don't understand is that if S17 will do approx 42 TH and all the 4x 3080s will do a combined 360 MH, shouldn't the S17 be mining a lot more coins? The value of $9.20 usd / day for S17 seems too low or this is how things work? I thought, the more the hashrate, the more the coins mined.
You're comparing two different hash rates. The S17 will only mine SHA-256 coins. Because of all the ASIC miners tuned to this algorithm, the difficulty on those coins is higher, so it's harder to hit a block. The GPUs can mine a whole range of coins that ASICs either don't exist for or aren't widely used. That means they could take advantage of any market imbalances between those altcoins they mine, their difficulty, and their sale price. Ultimately, if you want to mine Bitcoin (and this is the Bitcoin mining forum), you need modern SHA-256 ASICs. Your limits are going to be your power costs and space availability, since a single newer ASIC is going to eat around 72 kwh (thanks to Fuzzy for the correction) kwh per day. |
|
|
|
Still getting the apollo miner crashing at least once daily. Any updates on increased ability to debug where the segmentation fault is coming from?
Is this on the standalone software or on your full unit? Standalone unit running on Ubuntu. |
|
|
|
|
Still getting the apollo miner crashing at least once daily. Any updates on increased ability to debug where the segmentation fault is coming from?
|
|
|
|
|
Here's one for me: 34uN73AXqiYfcY8FS9nGo2KpQtPqXnT3V2
|
|
|
|
count me in Phil if you get it going
Okay. What do we want to spend. 0.01 = 358-360 usd ten guys total of 0.10 btc? the diff is dropping like a mofo. 12% if we do it next jump it would be easier to hit it. I'm in too if you want more gamblers. |
|
|
|
I have 3 GekkoScience NewPac USB Miners. Is it possible to mine Ethereum with these devices. I would like to know also what would be the pool to use for these devices. Another question would be how would I be able to access the balance from this device has generated. Thank You
No, these can only mine SHA-256 coins like Bitcoin. You can use any pool you like, as long as they'll accept the low hashrates of these devices. When you connect to a pool, they'll have instructions on how to redeem any balance you might have. |
|
|
|
Is this on the standalone software? What system are you using?
This is the standalone software (linux-x86_64) from the git link in the first page. I'm running Ubuntu 20.04.2 LTS. |
|
|
|
Is there a way to turn on/export more detailed logs? After running for a day just fine (standard unit hooked up to Ubuntu i5 computer), I see this: ./start_apollo.sh: line 63: 211343 Segmentation fault (core dumped)
Line 63 in my start file just loads the miner: ./apollo-miner -h <real pool here> -port 3333 -user <real user> -pswd x -comport /dev/ttyACM0 -brd_ocp 48 -osc 30 -ao_mode 1
Seems like the miner is crashing on something, but I dont where to check logs for more detail. In case it matters, my miner-details shows: 2021-06-18 06:16:07 ::: MINER_ALIVE ::: Enjoy your mining!
2021-06-18 06:17:05 ::: POOL_CLEAN_JOB ::: jobIdCounter = 1075, JOB: jobName: 605ebf7d0003b423, prevHash: 9e04d278ad805d9a6d26ee24176b41a5ff7561de0000e4af0000000000000000, nTime: 0x60cc9cce, cleanJobs: 1
2021-06-18 07:43:28 ::: MINER_START ::: Enjoy your mining!
(It crashed sometime after 06:17:00, then I did a restart of the program at 07:43:28 ) |
|
|
|
Send an email if you see above version mismatch error if your trying to run your standard unit with our pc/linux software.
This is caused by an older version of the firmware that was installed at the factory and should have been updated before shipment, but a few units slipped through with the older firmware. We have a simple one click firmware updater that will fix this.
Thanks, the new firmware fixed it and i'm hashing away! |
|
|
|
Hi
I got a problem to make it work my Apollo BTC on raspberry PI 3 (it work on my PC)
- I extracted the archive : Apollo-Miner_aarch64.tar.gz
- The device : /dev/ttyACM0 is correct into the directory
- When i try to launch the script file the console it quit directly => I tryed manually to launch the script in a
console and i get (translated from french)
"./start_apollo.sh: line 63 ./apollo-miner : impossible to launch the binary file : Format error for exec()"
Question two : It is compatible with linux minera ?
Just me or?
Are you running at 64 bit OS on your Pi? What does it say when you run "uname -a"? If it's not a 64 bit OS, the binaries won't work. |
|
|
|
Hello, I wonder if anyone can help get my standard unit hooked up to my Ubuntu machine working. I keep getting a "packet ignored" message: I tried with a different cable on Ubuntu machine, and now I can see the USB device. However, when I start the miner, I get the same symptom as the windows box: 6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
I also tried on Windows, where I see it show up as COM3, but just get this same warning and no hashing: MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
|
|
|
|
|
Alright! Been a while since a proper block sunday!
|
|
|
|
everyone is counting on your 8 P rental  No way - I want my 500GH of sidehack-created miners to hit the block! |
|
|
|
...
[2018-10-06 11:41:05] Stratum from pool 0 detected new block
This word i can see it many many time in the day what is the meaning
Stratum from pool 0 detected new block
It means somewhere on the network, a new block was found, and the pool is sending your client new work to work on that new previous block ID. (It does not mean your worker found a block, sadly.) |
|
|
|
|
Are the cooler master 50x50x20 fans what people are upgrading the "stock" fans with?
|
|
|
|
|
Show Posts
