Initial test on RaspiBlitz v1.10.0.
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Influx disabled.
Noticed no hashing registering at pool and this error message:
2024-03-19 17:11:43,054 - INFO - temperature: [38.25, 0]
2024-03-19 17:11:43,560 - DEBUG - new extranonce2 6e789b83
2024-03-19 17:11:43,561 - DEBUG - new work 28
Exception in thread Thread-2:
Traceback (most recent call last):
File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
self.run()
File "/usr/lib/python3.9/threading.py", line 892, in run
self._target(*self._args, **self._kwargs)
File "/home/admin/piaxe-miner/piaxe/miner.py", line 683, in _receive_thread
byte = self._serial_rx_func(11, 100)
File "/home/admin/piaxe-miner/piaxe/miner.py", line 592, in _serial_rx_func
data = self.serial_port.read(size)
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 577, in read
raise SerialException(
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2024-03-19 17:11:44,556 - INFO - temperature: [38.3125, 0]
2024-03-19 17:11:45,062 - DEBUG - new extranonce2 7882b585
Searched and found:
https://raspberrypi.stackexchange.com/questions/90013/uart-rx-stops-reading-data-after-working-correctly
Ran in SSH:
sudo systemctl stop serial-getty@ttyS0.service
sudo systemctl disable serial-getty@ttyS0.service
Restarted miner and hashing started registering at the pool.
Not sure if i missed anything in the preparing configurations, but maybe this can help others and if required to disable serial-getty@ttyS0.service, maybe worth mentioning in the readme?
Initial test on RaspiBlitz v1.10.0.
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Influx disabled.
Noticed no hashing registering at pool and this error message:
Searched and found:
https://raspberrypi.stackexchange.com/questions/90013/uart-rx-stops-reading-data-after-working-correctly
Ran in SSH:
Restarted miner and hashing started registering at the pool.
Not sure if i missed anything in the preparing configurations, but maybe this can help others and if required to disable serial-getty@ttyS0.service, maybe worth mentioning in the readme?