The last log where bz worked correctly doesn’t state why. Think bz doesn’t show why it terminated. However, it could have been autoswitch changing currency. Did took a bit over a minute between runs. Also there could had been a network issue. The next run seems to had network problems, but that shouldn’t had caused it to grab all the gpus
last lines of the good run
<Debug> GPU 8:0: Starting kaspa work on job 3a
<Debug> Received new kaspa job
would love to try another lol, but not an option. I’m already using all the other possible miners Maybe a custom one
Usually I noticed it grabs all the cards when it restarts. I need to shutdown and do a cold boot. I have noticed something strange during the boot process when it will fail. Haven’t had a chance to grab it, maybe next time syslog doesn’t seem rotate
as I said, I am already using all the other options (gminer, lolminer, trm). Currently lolminer is mining something else, so I can’t use it or any other miner bz seems to be the only option.
also noticed something strange. bz seems to be mining to a weird address. Been mining to this using my pool, and it isn’t getting authorized. Could 34TJQUdMYzyV5GNLVFRpRRdFAbgLmVwJ3v be the wallet for the miner’s fee? Though it isn’t a kaspa address
It only happens with bz and no other miner. So not sure it is malware
<Warn> Kaspa wallet is: 34TJQUdMYzyV5GNLVFRpRRdFAbgLmVwJ3v.2842067
<Warn> Kaspa wallets should start with 'kaspa:'
<Warn> GPU 9:0: disabled. Set start_mining to true to enable.
Connecting to stratum+tcp://us.acc-pool.pw:16061 as rig with wallet:
34TJQUdMYzyV5GNLVFRpRRdFAbgLmVwJ3v.2842067
<Debug> GPU kaspa 8:0: Work thread starting
GPU 8:0: OC has been set for kaspa
GPU 8:0: kaspa OC set to [ Mem Offset: 0mhz Locked Mem: 810mhz]
<Debug> Error on stratum+tcp://us.acc-pool.pw:16061: Connection reset by peer
Connected to stratum+tcp://us.acc-pool.pw:16061 using stratum as rig
kaspa dev fee: 1.0%
Reconnecting to stratum+tcp://us.acc-pool.pw:16061 in 3 seconds...
<Debug> Error shutting down pool connection: shutdown: Transport endpoint is not connected [system:107]
<Debug> GPU 8:0: stop work requested
<Debug> GPU 8:0: Work thread closing
<Debug> Destroying pool connection to stratum+tcp://us.acc-pool.pw:16061
<Debug> GPU kaspa 8:0: Work thread starting
<Debug> Received HTTP GetHiveStatus
Finally grabbed some screenshots of when it crashes. Strangely enough except for an obscure error, everything works! Finds the wireless card, connects flawlessly to the wifi network, and should have worked (and still waits for 2m). However, it is when this happens that bz misbehaves
Maybe you know how to fix an msr error? The linux kernel is disabling userspace writes to MSR in version 5.9
@keaton_hiveon why would I do that? miniz is hashing to nicehash using the nicehash address wallet. All the others are mining using the correct wallet for each coin. Should I have mixed them up, it wouldn’t mine!
Even mentioned that the address for bz changed to an incorrect wallet. None of my wallets has 34TJQUdMYzyV5GNLVFRpRRdFAbgLmVwJ3v as a value. Not sure if this is the miner’s wallet or could be malware
You are missing the point, this is a problem happens only sometimes when the rig boots. Not sure that I have seen this at other times. Something goes wrong and bz tries to mine on all the cards. This causes some cards to double mine using bz and the other miners. After a couple of minutes, the rig crashes.
If this misstep doesn’t happen, then the rig mines correctly and bz uses only the assigned card. It is this that makes me think there might be a problem with hive that leads to this. bz might not be as stable as the other miners, but seems it is when hive launches bz.