Search content
Sort by
Showing 20 of 778 results by tuaris
These days it's the firmware that concerns me the most. People/vendors are getting into nasty habits. Things like forcing you to use an app in order to configure it, integrating with the "cloud", and lack of control over the hardware you own. When I buy a piece of hardware, I expect it to function offline without an app, with a built-in web server.
It's not impossible, is it? Don't AC's heat up a gas that then goes through condensation? My understanding is that the state change from gas to liquid absorbs ambient heat. The purpose of the compressor in current AC's is just to heat up the gas, or am I wrong in my theory?
I never sell anything. My USB ASICminer Block Erupter's are now an art piece sitting on a shelf in my office. It makes for great conversation.
My Bitmain USB miners are actually still in use as lottery miners.
I also have the a few USB scrypt miners (circular gridseed miners) that I need to dust off. If I'm not mistaken, I may also have a stick USB scrypt miner.
My Bitmain USB miners are actually still in use as lottery miners.
I also have the a few USB scrypt miners (circular gridseed miners) that I need to dust off. If I'm not mistaken, I may also have a stick USB scrypt miner.
It's surprisingly difficult to figure out what fan is what and there is a serious lack of information about it.
According to Bitmain
J12 = fan_id = 3
J13 = fan_id = 2
J15 = fan_id = 0
J14 = fan_id = 1
But I have J11, J12, J13, J14, and according to the labels on the control board
J11 = Fan 3
J12 = Fan 1
J13 = Fan 2
J14 = Fan 4
So do I assume Fan 2 = fan_id = 1 = J13 = Rear0 = bottom back?
According to Bitmain
J12 = fan_id = 3
J13 = fan_id = 2
J15 = fan_id = 0
J14 = fan_id = 1
But I have J11, J12, J13, J14, and according to the labels on the control board
J11 = Fan 3
J12 = Fan 1
J13 = Fan 2
J14 = Fan 4
So do I assume Fan 2 = fan_id = 1 = J13 = Rear0 = bottom back?
you lost a fan it happens. buy a fan and replace it.
https://altairtech.io/product/antminer-120mm-replacement-fan-for-s19-s17-s11-s15-and-s9-series/
make sure you get a square pin if the bad fan has a square pin
make sure you get a rectangle pin if the bad fan has a rectangular pin.
https://altairtech.io/product/antminer-120mm-replacement-fan-for-s19-s17-s11-s15-and-s9-series/
make sure you get a square pin if the bad fan has a square pin
make sure you get a rectangle pin if the bad fan has a rectangular pin.
Hmm, maybe just getting the fan is less trouble than trying to work with the vendor I purchased from.
I wonder... I have a ton of spare fans from L3's and S9's. Will they work here?
Applied a firmware update (Antminer-S19k-Pro-merge-release-20240409060820.bmu), now I get:
So I got a unit with a bad fan? Is the ASIC fine?
Code:
2025-01-08 18:42:54 pulse_mode = 1, ccdly_sel = 0, pwth_sel = 4
2025-01-08 18:42:54 start do_core_reset
2025-01-08 18:43:06 end do_core_reset
2025-01-08 18:43:06 noraml inc freq voltage
2025-01-08 18:43:06 set_voltage_by_steps to 1500.
2025-01-08 18:43:10 Version num 65536
2025-01-08 18:43:10 Mask num 0x1fffe000
2025-01-08 18:43:10 opt_multi_version = 65536, interval timeout = 2620657
2025-01-08 18:43:10 freq = 590, percent = 90, hcn = 4442, timeout = 2620657
2025-01-08 18:43:10 (null)
2025-01-08 18:43:21 freq 200 waiting board temp to 35,curr temp 24
2025-01-08 18:43:23 Error, fan lost, only find 3 (< 4)
2025-01-08 18:43:23 fan_id = 0, fan_speed = 1990
2025-01-08 18:43:23 fan_id = 1, fan_speed = 0
2025-01-08 18:43:23 fan_id = 2, fan_speed = 2400
2025-01-08 18:43:23 fan_id = 3, fan_speed = 2400
2025-01-08 18:43:23 Sweep error string = F:1.
2025-01-08 18:43:23 ERROR_FAN_LOST: fan lost
2025-01-08 18:43:23 stop_mining: fan lost
2025-01-08 18:43:23 uninit_temp_info
2025-01-08 18:43:23 do not read temp anymore...
2025-01-08 18:43:23 cancel thread
2025-01-08 18:43:23 cancel thread
2025-01-08 18:43:23 ****power off hashboard****
2025-01-08 18:43:23 power off
2025-01-08 18:43:25 temp monitor thread exit
2025-01-08 18:43:31 freq 200 waiting board temp to 35,curr temp 24
2025-01-08 18:43:42 Sweep error string = P:2.
2025-01-08 18:43:42 ERROR_TEMP_TOO_LOW: protect machine!
2025-01-08 18:43:42 stop_mining: protect machine!
2025-01-08 18:43:42 ****power off hashboard****
2025-01-08 18:43:42 power off
2025-01-08 18:42:54 start do_core_reset
2025-01-08 18:43:06 end do_core_reset
2025-01-08 18:43:06 noraml inc freq voltage
2025-01-08 18:43:06 set_voltage_by_steps to 1500.
2025-01-08 18:43:10 Version num 65536
2025-01-08 18:43:10 Mask num 0x1fffe000
2025-01-08 18:43:10 opt_multi_version = 65536, interval timeout = 2620657
2025-01-08 18:43:10 freq = 590, percent = 90, hcn = 4442, timeout = 2620657
2025-01-08 18:43:10 (null)
2025-01-08 18:43:21 freq 200 waiting board temp to 35,curr temp 24
2025-01-08 18:43:23 Error, fan lost, only find 3 (< 4)
2025-01-08 18:43:23 fan_id = 0, fan_speed = 1990
2025-01-08 18:43:23 fan_id = 1, fan_speed = 0
2025-01-08 18:43:23 fan_id = 2, fan_speed = 2400
2025-01-08 18:43:23 fan_id = 3, fan_speed = 2400
2025-01-08 18:43:23 Sweep error string = F:1.
2025-01-08 18:43:23 ERROR_FAN_LOST: fan lost
2025-01-08 18:43:23 stop_mining: fan lost
2025-01-08 18:43:23 uninit_temp_info
2025-01-08 18:43:23 do not read temp anymore...
2025-01-08 18:43:23 cancel thread
2025-01-08 18:43:23 cancel thread
2025-01-08 18:43:23 ****power off hashboard****
2025-01-08 18:43:23 power off
2025-01-08 18:43:25 temp monitor thread exit
2025-01-08 18:43:31 freq 200 waiting board temp to 35,curr temp 24
2025-01-08 18:43:42 Sweep error string = P:2.
2025-01-08 18:43:42 ERROR_TEMP_TOO_LOW: protect machine!
2025-01-08 18:43:42 stop_mining: protect machine!
2025-01-08 18:43:42 ****power off hashboard****
2025-01-08 18:43:42 power off
So I got a unit with a bad fan? Is the ASIC fine?
It was working fine for about 4 days. Put it on sleep mode about a day ago, and turned it back on. Now, it's giving this:
Also noticed this in the historical log
What happened? The room temperature never exceeds 75F, and the current room temp is 61F. Other S19k's still humming along nicely.
Did I receive a bad unit?
Code:
2025-01-08 17:51:00 no board pluged in socket 432
...
2025-01-08 17:51:51 Error, fan lost, only find 3 (< 4)
2025-01-08 17:51:51 fan_id = 0, fan_speed = 7000
2025-01-08 17:51:51 fan_id = 1, fan_speed = 3440
2025-01-08 17:51:51 fan_id = 2, fan_speed = 5168
2025-01-08 17:51:51 fan_id = 3, fan_speed = 6020
2025-01-08 17:51:51 Sweep error string = F:1.
2025-01-08 17:51:51 ERROR_FAN_LOST: fan lost
2025-01-08 17:51:51 stop_mining: fan lost
2025-01-08 17:51:51 cancel thread
2025-01-08 17:51:51 ****power off hashboard****
2025-01-08 17:51:51 power off
2025-01-08 17:51:52 ERROR_SOC_INIT: soc init failed!
2025-01-08 17:51:52 stop_mining: soc init failed!
2025-01-08 17:51:52 ****power off hashboard****
2025-01-08 17:51:52 power off
...
2025-01-08 17:51:51 Error, fan lost, only find 3 (< 4)
2025-01-08 17:51:51 fan_id = 0, fan_speed = 7000
2025-01-08 17:51:51 fan_id = 1, fan_speed = 3440
2025-01-08 17:51:51 fan_id = 2, fan_speed = 5168
2025-01-08 17:51:51 fan_id = 3, fan_speed = 6020
2025-01-08 17:51:51 Sweep error string = F:1.
2025-01-08 17:51:51 ERROR_FAN_LOST: fan lost
2025-01-08 17:51:51 stop_mining: fan lost
2025-01-08 17:51:51 cancel thread
2025-01-08 17:51:51 ****power off hashboard****
2025-01-08 17:51:51 power off
2025-01-08 17:51:52 ERROR_SOC_INIT: soc init failed!
2025-01-08 17:51:52 stop_mining: soc init failed!
2025-01-08 17:51:52 ****power off hashboard****
2025-01-08 17:51:52 power off
Also noticed this in the historical log
Code:
2025-01-05 19:04:20 chain[2] asic[5] [215] [0]
2025-01-05 19:04:20 chain[2] bad asic num: 6 6 0
2025-01-05 19:04:20 chain[2] asic[5] [215] 28651771-28651556 [0] 62-62
2025-01-05 19:04:20 chain[2] bad asic num: 6 6 0
2025-01-05 19:04:20 chain[2] asic[5] [215] 28651771-28651556 [0] 62-62
What happened? The room temperature never exceeds 75F, and the current room temp is 61F. Other S19k's still humming along nicely.
Did I receive a bad unit?
If scrypt was published a few months earlier, would Bitcoin have used it instead
Scrypt was published 3 months after Satoshi mined the Genesis block. If scrypt had been published before or if Satoshi started working on Bitcoin after March 2009, would he have used scrypt as the proof of work function instead of SHA256D?
Quote
Don’t hate because you didn’t get in below $0.50 like those of us who believed in it
Exactly, tell me you want to buy into it without telling me. Constantly bashing and claiming something will dump/fall/fail is pretty much saying you feel stupid for not buying into it earlier and want pick it up at a discount.
If you actually didn't care and see no purpose or future in it, you'd stay silent and ignore it.
I pity the fool who spends more than a few hundred dollars on ASICS for these altcoins that come out of nowhere. It took years before anyone considered making an ASIC for Litecoin. Now all of a sudden we have ASIC's for things like KDA, KAS, and ALPH in less than a few months. Something fishy indeed. My hunch is that it's a single large shady company behind the scenes who has the most to gain with over priced chips.
⭐ Merited by ABCbits (1)
No doubt I believe HD wallets are better. They solve a few quirks that have bugged me. However I have gotten pretty comfortable with the "legacy wallets". Backup and restoration was just making sure you had your private key physically and safely stashed away somewhere offline. Bitcoin will always be accessible regardless of future file formats and bitrot, or data loss.
How do I achieve the same sense of 'security' with an HD wallet. It doesn't seem it's that simple any more. Sure, I can backup the data itself, but I want the assurance of a text based backup. Data formats change. Imagine 30 years from now if I had kept only the Berkeley DB 4.8 binary wallet file? It would be pretty near impossible to find a working system that could read that, let alone a Bitcoin wallet that would work with it.
Is the `listdescriptors true` command what I want here?
How do I achieve the same sense of 'security' with an HD wallet. It doesn't seem it's that simple any more. Sure, I can backup the data itself, but I want the assurance of a text based backup. Data formats change. Imagine 30 years from now if I had kept only the Berkeley DB 4.8 binary wallet file? It would be pretty near impossible to find a working system that could read that, let alone a Bitcoin wallet that would work with it.
Is the `listdescriptors true` command what I want here?
I'm considering one (or two). It usually gets down to -20F where I am and I need a way to heat a garage. At 140W and as low as $130 USD, seems like a good idea. Except that I am concerned about it's 'openness'. Looks like I'm getting a very locked down device. A literal "black box" in this case.
Is this the experience from most people? Does it lack a web UI, is it app controlled only? Does it phone home?
Is this the experience from most people? Does it lack a web UI, is it app controlled only? Does it phone home?
Yeah, this change is super upsetting. What concerns me most is my unpaid balance that is below the payment threshold, will that be paid? It's quite significant considering the rising value of Bitcoin. I'm guessing it a no. They are going to add a "Service fee" which basically means they are going to steal my balance. No other way to put it, but these people are scumbags.
Seems like there will be demand for a replacement. I really need to get my pools up and running again.
Seems like there will be demand for a replacement. I really need to get my pools up and running again.
Re: NiceHash is paying 6% more than mining Bitcoin traditionally
Since Nicehash has ended anonymous mining as of November 12, 2024 I can no longer recommended using it. The requirement of registration KYC violates privacy principals. I myself will stop using it. This was my go to for years.
There is this matter of an unpaid balance that is below the payment threshold, will that be paid? It's quite significant considering the rising value of Bitcoin.
There is this matter of an unpaid balance that is below the payment threshold, will that be paid? It's quite significant considering the rising value of Bitcoin.
Re: [∞ YH] solo.ckpool.org 2% fee solo mining 294 blocks solved!
I've made a fork of your code base to work exclusively on FreeBSD. More specifically, going through and replacing the Linux specific system calls and some logic with FreeBSD counterparts. The most significant change being of course the epoll to kqueue conversion. I'm currently in the process of fixing the logging. The current implementation seems to be creating a memory leak on FreeBSD. Not sure why.
Porting is complete and the software is semi-functioning (memory leak issue) and successfully mining blocks on testnet and on a lower difficulty SHA256 fork of bitcoin that I use for personal test/dev.
I would like to ask if you are open to allowing a dual licensing model where for the FreeBSD fork it uses a more permissive license. I would prefer to publish my current and future contributions under a downstream project with a new name and using the BSD2 license. Obviously I will be providing proper attribution and making it clear this is a derivative work.
Porting is complete and the software is semi-functioning (memory leak issue) and successfully mining blocks on testnet and on a lower difficulty SHA256 fork of bitcoin that I use for personal test/dev.
I would like to ask if you are open to allowing a dual licensing model where for the FreeBSD fork it uses a more permissive license. I would prefer to publish my current and future contributions under a downstream project with a new name and using the BSD2 license. Obviously I will be providing proper attribution and making it clear this is a derivative work.