Bitcoin Forum>Bitcoin>Mining>Mining support
Author

Topic: Hashboard not showing Temp readings (Read 136 times)

spangyy
newbie
Activity: 16
Merit: 0
Hashboard not showing Temp readings
June 02, 2021, 08:43:02 AM
#15
Quote from: mikeywith on June 01, 2021, 07:35:12 PM
Quote from: spangyy on June 01, 2021, 11:23:35 AM
yea just cant believe price for antminer s9 that expensive these days and its pretty old , i guess crypto market doesn't work like the real world 

I think the S9 price has been the same for years when you take the ROI in days excluding the power bill, it now goes for $400 and makes about $90 a month, It was about $800 when it made about $150 and when it made only a dollar or less day last year it was going for about $100, so really the average is 4-5 months ROI if you have free power, of course, sudden BTC price increase create some temporary "unrealistic" demand which would extend the average but that only lasts for a while and then we eventually fall back into the 4-5 ROI based price.

I also believe this is true for all other gears, this is why I ALWAYS tell people here not to buy overpriced gears that can't (at least on paper) ROI in 6-8 months, those who paid 15-16k for S19 pro are now in deep shit, their gear now worths 20-30% less and makes 20-30% less profit, the only price that makes sense for an S19 pro now is around 6k, anything above that and you will probably never ROI, the math is rather simple, but most folks just don't seem to care.

you are correct , given how unpredictable these machines can be I wouldn't recommend overspending , for example this morning one of my boards had its last breath , results showing in dashboard of Braiins os " chips cant be detected " this board was running for like 3 months . just goes to show you might not even get a ROI if hardware fails
mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: Hashboard not showing Temp readings
June 01, 2021, 07:35:12 PM
#14
Quote from: spangyy on June 01, 2021, 11:23:35 AM
yea just cant believe price for antminer s9 that expensive these days and its pretty old , i guess crypto market doesn't work like the real world  

I think the S9 price has been the same for years when you take the ROI in days excluding the power bill, it now goes for $400 and makes about $90 a month, It was about $800 when it made about $150 and when it made only a dollar or less per day last year it was going for about $100, so really the average is 4-5 months ROI if you have free power, of course, sudden BTC price increase create some temporary "unrealistic" demand which would extend the average but that only lasts for a while and then we eventually fall back into the 4-5 ROI based price.

I also believe this is true for all other gears, this is why I ALWAYS tell people here not to buy overpriced gears that can't (at least on paper) ROI in 6-8 months, those who paid 15-16k for S19 pro are now in deep shit, their gear now worths 20-30% less and makes 20-30% less profit, the only price that makes sense for an S19 pro now is around 6k, anything above that and you will probably never ROI, the math is rather simple, but most folks just don't seem to care.
spangyy
newbie
Activity: 16
Merit: 0
Re: Hashboard not showing Temp readings
June 01, 2021, 11:23:35 AM
#13
Quote from: mikeywith on June 01, 2021, 09:49:23 AM
Quote from: spangyy on May 31, 2021, 06:23:44 PM
im using a antminer s9 , but how do i post the full code ? each time i try doing that , it keeps saying i have surpassed maximum length.

You can split the kernel log into 2 posts to get around the forum limits.

Quote
i eventually ended up replacing board with another board had laying around . seems to often that these things chips just fail so frequent. doesnt even make sense to repair better just buy a new one especially if dont know how to solder

Actually, it takes a lot more than soldering knowledge to fix these boards, you will need some tools and skills, so unless you are planning to do this large scale it really isn't worth investing your time and money just to fix one or two hash boards.

yea just cant believe price for antminer s9 that expensive these days and its pretty old , i guess crypto market doesn't work like the real world 
mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: Hashboard not showing Temp readings
June 01, 2021, 09:49:23 AM
#12
Quote from: spangyy on May 31, 2021, 06:23:44 PM
im using a antminer s9 , but how do i post the full code ? each time i try doing that , it keeps saying i have surpassed maximum length.

You can split the kernel log into 2 posts to get around the forum limits.

Quote
i eventually ended up replacing board with another board had laying around . seems to often that these things chips just fail so frequent. doesnt even make sense to repair better just buy a new one especially if dont know how to solder

Actually, it takes a lot more than soldering knowledge to fix these boards, you will need some tools and skills, so unless you are planning to do this large scale it really isn't worth investing your time and money just to fix one or two hash boards.
spangyy
newbie
Activity: 16
Merit: 0
Re: Hashboard not showing Temp readings
May 31, 2021, 06:23:44 PM
#11
Quote from: mikeywith on May 31, 2021, 05:48:42 PM
Quote from: spangyy on May 31, 2021, 03:01:41 PM
Undecided ahh man

I know right? anyway, what miner is this? seems like one of the 17 series from Bitmain, judging from the single line of the kernel log you posted (which is called the system log on BO+) it seems like you have a faulty chip which is very, very, very common with all of these gears, and the issue is usually a hardware related, i.e the chip is dead and needs replacement

With that being said, please post more info regarding the miner as well as the complete "system logs".

im using a antminer s9 , but how do i post the full code ? each time i try doing that , it keeps saying i have surpassed maximum length. i eventually ended up replacing board with another board had laying around . seems to often that these things chips just fail so frequent. doesnt even make sense to repair better just buy a new one especially if dont know how to solder
mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: Hashboard not showing Temp readings
May 31, 2021, 05:48:42 PM
#10
Quote from: spangyy on May 31, 2021, 03:01:41 PM
Undecided ahh man

I know right? anyway, what miner is this? seems like one of the 17 series from Bitmain, judging from the single line of the kernel log you posted (which is called the system log on BO+) it seems like you have a faulty chip which is very, very, very common with all of these gears, and the issue is usually a hardware related, i.e the chip is dead and needs replacement

With that being said, please post more info regarding the miner as well as the complete "system logs".
spangyy
newbie
Activity: 16
Merit: 0
Re: Hashboard not showing Temp readings
May 31, 2021, 03:01:41 PM
#9
Quote from: mikeywith on May 31, 2021, 02:46:31 PM
Quote from: BitMaxz on May 31, 2021, 01:26:14 PM
Is that the complete kernel logs? I can't seem to find any issue on the kernel logs.
 

That isn't even the kernel log you are expecting, funny enough most firmware except for Bitmain call the kernel logs "the one we call Kernel logs" other names, like miner log, syslog, system log and etc.

 Undecided ahh man
mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: Hashboard not showing Temp readings
May 31, 2021, 02:46:31 PM
#8
Quote from: BitMaxz on May 31, 2021, 01:26:14 PM
Is that the complete kernel logs? I can't seem to find any issue on the kernel logs.
 

That isn't even the kernel log you are expecting, funny enough most firmware except for Bitmain call the kernel logs "the one we call Kernel logs" other names, like miner log, syslog, system log and etc.
spangyy
newbie
Activity: 16
Merit: 0
Re: Hashboard not showing Temp readings
May 31, 2021, 01:55:25 PM
#7
did some checks through system logs and kept seeing instance of this error

Code:
Mon May 31 17:01:28 2021 daemon.err bosminer[1538]: May 31 17:01:28.500 ERRO Sensor hb6: read failed: I2C error: general error Hashchip: no response for GetStatusCmd(reg=0x20) from chip One(61)

does 61 mean the chip number?
spangyy
newbie
Activity: 16
Merit: 0
Re: Hashboard not showing Temp readings
May 31, 2021, 01:41:22 PM
#6
Quote from: BitMaxz on May 31, 2021, 01:26:14 PM
Quote from: spangyy on May 31, 2021, 12:40:26 PM

not sure if thats what you looking for

Is that the complete kernel logs? I can't seem to find any issue on the kernel logs.

How about the system logs?


If we can't find any issues on the logs try to reduce the power and enable auto-tuning.

Use Braiins OS+ Manager the easily configure your miner.

https://www.youtube.com/watch?v=vVB41klUiFw&t=310s

Let see if reducing the power will keep up the temp readings but if it still down to zero try to increase a bit the temp limit from the configuration settings and increase the fan speed.

that was the kernel log , see the last part of system log at given time since can submit all the system code here

Code:
Mon May 31 18:36:37 2021 daemon.err bosminer[1538]: May 31 18:36:37.238 WARN extra garbage command response: [
Mon May 31 18:36:37 2021 daemon.err bosminer[1538]:     0x63,
Mon May 31 18:36:37 2021 daemon.err bosminer[1538]:     0x98,
Mon May 31 18:36:37 2021 daemon.err bosminer[1538]:     0x6d,
Mon May 31 18:36:37 2021 daemon.err bosminer[1538]:     0x61,
Mon May 31 18:36:37 2021 daemon.err bosminer[1538]:     0x4d,
Mon May 31 18:36:37 2021 daemon.err bosminer[1538]:     0xf6,
Mon May 31 18:36:37 2021 daemon.err bosminer[1538]: ]
Mon May 31 18:36:37 2021 daemon.err bosminer[1538]: May 31 18:36:37.344 ERRO Sensor hb6: read failed: I2C error: general error Hashchip: no response for GetStatusCmd(reg=0x20) from chip One(61)
Mon May 31 18:36:38 2021 daemon.err bosminer[1538]: May 31 18:36:38.485 INFO Stratum: accepted solution #10622 with nonce=768916c7
Mon May 31 18:36:38 2021 daemon.err bosminer[1538]: May 31 18:36:38.886 INFO Monitor: User defined fan 55% | On(ReadFailed) On(56°C,NotPresent) On(64°C,77°C) | 3.8K 3.9K 0 0 fan_55%
Mon May 31 18:36:42 2021 daemon.err bosminer[1538]: May 31 18:36:42.446 ERRO Sensor hb6: read failed: I2C error: general error Hashchip: no response for GetStatusCmd(reg=0x20) from chip One(61)
Mon May 31 18:36:43 2021 daemon.err bosminer[1538]: May 31 18:36:43.887 INFO Monitor: User defined fan 55% | On(ReadFailed) On(56°C,NotPresent) On(64°C,77°C) | 3.8K 3.8K 0 0 fan_55%
Mon May 31 18:36:47 2021 daemon.err bosminer[1538]: May 31 18:36:47.548 ERRO Sensor hb6: read failed: I2C error: general error Hashchip: no response for GetStatusCmd(reg=0x20) from chip One(61)
Mon May 31 18:36:48 2021 daemon.err bosminer[1538]: May 31 18:36:48.888 INFO Monitor: User defined fan 55% | On(ReadFailed) On(57°C,NotPresent) On(64°C,77°C) | 3.8K 3.9K 0 0 fan_55%
Mon May 31 18:36:52 2021 daemon.err bosminer[1538]: May 31 18:36:52.650 ERRO Sensor hb6: read failed: I2C error: general error Hashchip: no response for GetStatusCmd(reg=0x20) from chip One(61)
Mon May 31 18:36:53 2021 daemon.err bosminer[1538]: May 31 18:36:53.889 INFO Monitor: User defined fan 55% | On(ReadFailed) On(57°C,NotPresent) On(64°C,77°C) | 3.8K 3.8K 0 0 fan_55%
Mon May 31 18:36:54 2021 daemon.err bosminer[1538]: May 31 18:36:54.348 INFO Stratum: accepted solution #10623 with nonce=acb09ae2
Mon May 31 18:36:57 2021 daemon.err bosminer[1538]: May 31 18:36:57.752 ERRO Sensor hb6: read failed: I2C error: general error Hashchip: no response for GetStatusCmd(reg=0x20) from chip One(61)
Mon May 31 18:36:58 2021 daemon.err bosminer[1538]: May 31 18:36:58.890 INFO Monitor: User defined fan 55% | On(ReadFailed) On(57°C,NotPresent) On(64°C,77°C) | 3.8K 3.9K 0 0 fan_55%
Mon May 31 18:37:00 2021 cron.info crond[1391]: USER root pid 15154 cmd /usr/sbin/logrotate /etc/logrotate.conf 2>&1 | logger -t logrotate
Mon May 31 18:37:02 2021 daemon.err bosminer[1538]: May 31 18:37:02.854 ERRO Sensor hb6: read failed: I2C error: general error Hashchip: no response for GetStatusCmd(reg=0x20) from chip One(61)
Mon May 31 18:37:03 2021 daemon.err bosminer[1538]: May 31 18:37:03.892 INFO Monitor: User defined fan 55% | On(ReadFailed) On(57°C,NotPresent) On(64°C,77°C) | 3.8K 3.8K 0 0 fan_55%
Mon May 31 18:37:06 2021 daemon.err bosminer[1538]: May 31 18:37:06.956 INFO Stratum: accepted solution #4888 with nonce=5e32f450
Mon May 31 18:37:07 2021 daemon.err bosminer[1538]: May 31 18:37:07.299 INFO Stratum: accepted solution #4889 with nonce=51afac4a
Mon May 31 18:37:07 2021 daemon.err bosminer[1538]: May 31 18:37:07.414 INFO Stratum: accepted solution #4890 with nonce=cd879afa
Mon May 31 18:37:07 2021 daemon.err bosminer[1538]: May 31 18:37:07.569 INFO Stratum: accepted solution #4891 with nonce=0aab08f6
Mon May 31 18:37:07 2021 daemon.err bosminer[1538]: May 31 18:37:07.956 ERRO Sensor hb6: read failed: I2C error: general error Hashchip: no response for GetStatusCmd(reg=0x20) from chip One(61)
Mon May 31 18:37:08 2021 daemon.err bosminer[1538]: May 31 18:37:08.893 INFO Monitor: User defined fan 55% | On(ReadFailed) On(58°C,NotPresent) On(64°C,77°C) | 3.8K 3.9K 0 0 fan_55%
Mon May 31 18:37:12 2021 daemon.err bosminer[1538]: May 31 18:37:12.998 INFO Stratum: accepted solution #10624 with nonce=c3cacf39
Mon May 31 18:37:13 2021 daemon.err bosminer[1538]: May 31 18:37:13.058 ERRO Sensor hb6: read failed: I2C error: general error Hashchip: no response for GetStatusCmd(reg=0x20) from chip One(61)
Mon May 31 18:37:13 2021 daemon.err bosminer[1538]: May 31 18:37:13.894 INFO Monitor: User defined fan 55% | On(ReadFailed) On(56°C,NotPresent) On(64°C,77°C) | 3.8K 3.8K 0 0 fan_55%
Mon May 31 18:37:14 2021 daemon.err bosminer[1538]: May 31 18:37:14.394 INFO Stratum: accepted solution #10625 with nonce=8f0f2716
Mon May 31 18:37:15 2021 daemon.err bosminer[1538]: May 31 18:37:15.937 INFO Stratum: accepted solution #10626 with nonce=a377f872
Mon May 31 18:37:18 2021 daemon.err bosminer[1538]: May 31 18:37:18.160 ERRO Sensor hb6: read failed: I2C error: general error Hashchip: no response for GetStatusCmd(reg=0x20) from chip One(61)
Mon May 31 18:37:18 2021 daemon.err bosminer[1538]: May 31 18:37:18.895 INFO Monitor: User defined fan 55% | On(ReadFailed) On(56°C,NotPresent) On(64°C,77°C) | 3.8K 3.9K 0 0 fan_55%
Mon May 31 18:37:22 2021 daemon.err bosminer[1538]: May 31 18:37:22.632 INFO Stratum: accepted solution #10627 with nonce=56213b1b
Mon May 31 18:37:23 2021 daemon.err bosminer[1538]: May 31 18:37:23.262 ERRO Sensor hb6: read failed: I2C error: general error Hashchip: no response for GetStatusCmd(reg=0x20) from chip One(61)
Mon May 31 18:37:23 2021 daemon.err bosminer[1538]: May 31 18:37:23.896 INFO Monitor: User defined fan 55% | On(ReadFailed) On(56°C,NotPresent) On(64°C,77°C) | 3.8K 3.9K 0 0 fan_55%
Mon May 31 18:37:27 2021 daemon.err bosminer[1538]: May 31 18:37:27.319 INFO Stratum: accepted solution #10628 with nonce=5fdfa938
Mon May 31 18:37:28 2021 daemon.err bosminer[1538]: May 31 18:37:28.364 ERRO Sensor hb6: read failed: I2C error: general error Hashchip: no response for GetStatusCmd(reg=0x20) from chip One(61)
Mon May 31 18:37:28 2021 daemon.err bosminer[1538]: May 31 18:37:28.364 ERRO Sensor hb6: Too many sensor errors, disabling sensor
Mon May 31 18:37:28 2021 daemon.err bosminer[1538]: May 31 18:37:28.897 INFO Monitor: User defined fan 55% | On(ReadFailed) On(56°C,NotPresent) On(64°C,77°C) | 3.8K 3.8K 0 0 fan_55%
Mon May 31 18:37:33 2021 daemon.err bosminer[1538]: May 31 18:37:33.899 INFO Monitor: User defined fan 55% | On(Broken) On(57°C,NotPresent) On(64°C,77°C) | 3.8K 3.8K 0 0 fan_55%
Mon May 31 18:37:38 2021 daemon.err bosminer[1538]: May 31 18:37:38.900 INFO Monitor: User defined fan 55% | On(Broken) On(57°C,NotPresent) On(64°C,77°C) | 3.8K 3.9K 0 0 fan_55%
Mon May 31 18:37:43 2021 daemon.err bosminer[1538]: May 31 18:37:43.901 INFO Monitor: User defined fan 55% | On(Broken) On(57°C,NotPresent) On(64°C,77°C) | 3.8K 3.8K 0 0 fan_55%
Mon May 31 18:37:46 2021 daemon.err bosminer[1538]: May 31 18:37:46.967 INFO Stratum: accepted solution #10629 with nonce=c45a7ca9
Mon May 31 18:37:48 2021 daemon.err bosminer[1538]: May 31 18:37:48.902 INFO Monitor: User defined fan 55% | On(Broken) On(56°C,NotPresent) On(64°C,77°C) | 3.8K 3.9K 0 0 fan_55%
Mon May 31 18:37:53 2021 daemon.err bosminer[1538]: May 31 18:37:53.551 INFO Stratum: accepted solution #10630 with nonce=50db0ed7
Mon May 31 18:37:53 2021 daemon.err bosminer[1538]: May 31 18:37:53.903 INFO Monitor: User defined fan 55% | On(Broken) On(56°C,NotPresent) On(64°C,77°C) | 3.8K 3.9K 0 0 fan_55%
Mon May 31 18:37:57 2021 daemon.err bosminer[1538]: May 31 18:37:57.236 INFO Stratum: accepted solution #4892 with nonce=e088cc56
Mon May 31 18:37:57 2021 daemon.err bosminer[1538]: May 31 18:37:57.392 INFO Stratum: accepted solution #4893 with nonce=b59d4b99
Mon May 31 18:37:57 2021 daemon.err bosminer[1538]: May 31 18:37:57.393 INFO Stratum: accepted solution #4894 with nonce=d3be9d25
Mon May 31 18:37:57 2021 daemon.err bosminer[1538]: May 31 18:37:57.393 INFO Stratum: accepted solution #4895 with nonce=71e12bf5
Mon May 31 18:37:58 2021 daemon.err bosminer[1538]: May 31 18:37:58.904 INFO Monitor: User defined fan 55% | On(Broken) On(56°C,NotPresent) On(64°C,77°C) | 3.8K 3.8K 0 0 fan_55%
Mon May 31 18:38:00 2021 cron.info crond[1391]: USER root pid 15161 cmd /usr/sbin/logrotate /etc/logrotate.conf 2>&1 | logger -t logrotate
Mon May 31 18:38:01 2021 daemon.err bosminer[1538]: May 31 18:38:01.960 INFO Stratum: accepted solution #10631 with nonce=71a3736a
Mon May 31 18:38:02 2021 daemon.err bosminer[1538]: May 31 18:38:02.885 INFO Stratum: accepted solution #10632 with nonce=efb8ca59
Mon May 31 18:38:03 2021 daemon.err bosminer[1538]: May 31 18:38:03.905 INFO Monitor: User defined fan 55% | On(Broken) On(57°C,NotPresent) On(64°C,76°C) | 3.8K 3.8K 0 0 fan_55%
Mon May 31 18:38:07 2021 daemon.err bosminer[1538]: May 31 18:38:07.231 INFO Stratum: accepted solution #10633 with nonce=f6617719
Mon May 31 18:38:07 2021 daemon.err bosminer[1538]: May 31 18:38:07.333 INFO Stratum: accepted solution #10634 with nonce=774104b7

BitMaxz
legendary
Activity: 3472
Merit: 3217
Playbet.io - Crypto Casino and Sportsbook
Re: Hashboard not showing Temp readings
May 31, 2021, 01:26:14 PM
#5
Quote from: spangyy on May 31, 2021, 12:40:26 PM

not sure if thats what you looking for

Is that the complete kernel logs? I can't seem to find any issue on the kernel logs.

How about the system logs?


If we can't find any issues on the logs try to reduce the power and enable auto-tuning.

Use Braiins OS+ Manager the easily configure your miner.

https://www.youtube.com/watch?v=vVB41klUiFw&t=310s

Let see if reducing the power will keep up the temp readings but if it still down to zero try to increase a bit the temp limit from the configuration settings and increase the fan speed.
spangyy
newbie
Activity: 16
Merit: 0
Re: Hashboard not showing Temp readings
May 31, 2021, 12:40:26 PM
#4
Quote from: BitMaxz on May 31, 2021, 11:26:50 AM
Do you mind share your whole kernel logs?
We might see the issue from your kernel logs if you can share it here.

My guess maybe because of over-temp protection that is why the hash rate drops. If I'm right you can disable the sensor scanning but the problem is it might fry your hashboard.

not sure if thats what you looking for
spangyy
newbie
Activity: 16
Merit: 0
Re: Hashboard not showing Temp readings
May 31, 2021, 12:27:44 PM
#3
Code:
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.4.0-xilinx-g518c00cd977f-dirty (build@runner-pegegjka-project-312-concurrent-0) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3560-79f57e422d) ) #0 SMP PREEMPT Fri Nov 27 22:34:11 2020
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: AntMiner S9 Miner Control Board
[    0.000000] cma: Reserved 16 MiB at 0x1f000000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 131072
[    0.000000] free_area_init_node: node 0, pgdat c07ba300, node_mem_map debf0000
[    0.000000]   Normal zone: 1024 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 131072 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 12 pages/cpu @debcc000 s18944 r8192 d22016 u49152
[    0.000000] pcpu-alloc: s18944 r8192 d22016 u49152 alloc=12*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
[    0.000000] Kernel command line: console=ttyPS0,115200 noinitrd ubi.mtd=8 ubi.block=0,1 root=/dev/ubiblock0_1 r rootfstype=squashfs rootwait mtdparts=pl35x-nand:512k(boot),2560k(uboot),2m(fpga1),2m(fpga2),512k(uboot_env),512k(miner_cfg),22m(recovery),95m(firmware1),95m(firmware2),36m(factory) earlyprintk
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 495060K/524288K available (5568K kernel code, 204K rwdata, 1844K rodata, 264K init, 221K bss, 12844K reserved, 16384K cma-reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xe0800000 - 0xff800000   ( 496 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc07454fc   (7414 kB)
[    0.000000]       .init : 0xc0746000 - 0xc0788000   ( 264 kB)
[    0.000000]       .data : 0xc0788000 - 0xc07bb260   ( 205 kB)
[    0.000000]        .bss : 0xc07bb260 - 0xc07f2984   ( 222 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] slcr mapped to e0800000
[    0.000000] L2C: platform modifies aux control register: 0x02060000 -> 0x32460000
[    0.000000] L2C: DT/platform modifies aux control register: 0x02060000 -> 0x32460000
[    0.000000] L2C-310 erratum 769419 enabled
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[    0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x46460001
[    0.000000] zynq_clock_init: clkc starts at e0800100
[    0.000000] Zynq clock init
[    0.000011] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
[    0.000034] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
[    0.000135] clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
[    0.000164] timer #0 at e0808000, irq=17
[    0.000427] Console: colour dummy device 80x30
[    0.000449] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.090309] pid_max: default: 32768 minimum: 301
[    0.090415] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090429] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090926] CPU: Testing write buffer coherency: ok
[    0.091131] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.091222] Setting up static identity map for 0x8280 - 0x82d8
[    0.260296] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.260368] Brought up 2 CPUs
[    0.260386] SMP: Total of 2 processors activated (2664.03 BogoMIPS).
[    0.260394] CPU: All CPU(s) started in SVC mode.
[    0.264142] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.264543] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.265441] pinctrl core: initialized pinctrl subsystem
[    0.266719] NET: Registered protocol family 16
[    0.268776] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.290287] cpuidle: using governor ladder
[    0.320274] cpuidle: using governor menu
[    0.330485] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0xe0880000
[    0.330897] zynq-pinctrl 700.pinctrl: zynq pinctrl initialized
[    0.381368] GPIO IRQ not connected
[    0.381388] XGpio: /amba_pl/gpio@41200000: registered, base is 897
[    0.381577] GPIO IRQ not connected
[    0.381589] XGpio: /amba_pl/gpio@41210000: registered, base is 884
[    0.382451] vgaarb: loaded
[    0.382904] SCSI subsystem initialized
[    0.383399] usbcore: registered new interface driver usbfs
[    0.383491] usbcore: registered new interface driver hub
[    0.383595] usbcore: registered new device driver usb
[    0.383985] media: Linux media interface: v0.10
[    0.384065] Linux video capture interface: v2.00
[    0.384157] pps_core: LinuxPPS API ver. 1 registered
[    0.384169] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
[    0.384217] PTP clock support registered
[    0.384319] EDAC MC: Ver: 3.0.0
[    0.385087] Advanced Linux Sound Architecture Driver Initialized.
[    0.386309] clocksource: Switched to clocksource arm_global_timer
[    0.395658] NET: Registered protocol family 2
[    0.396406] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.396469] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.396555] TCP: Hash tables configured (established 4096 bind 4096)
[    0.396609] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.396640] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.396846] NET: Registered protocol family 1
[    0.397303] RPC: Registered named UNIX socket transport module.
[    0.397317] RPC: Registered udp transport module.
[    0.397326] RPC: Registered tcp transport module.
[    0.397334] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.397364] PCI: CLS 0 bytes, default 64
[    0.398884] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.409616] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.421980] io scheduler noop registered
[    0.422002] io scheduler deadline registered
[    0.422054] io scheduler cfq registered (default)
[    0.423899] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[    0.423920] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.424689] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.425955] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 143, base_baud = 6249999) is a xuartps
[    1.055318] console [ttyPS0] enabled
[    1.059471] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to e081c000
[    1.066146] [drm] Initialized drm 1.1.0 20060810
[    1.081479] brd: module loaded
[    1.090653] loop: module loaded
[    1.096657] CAN device driver interface
[    1.102118] libphy: MACB_mii_bus: probed
[    1.186471] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 145 (2a:9c:7b:3b:73:04)
[    1.196354] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:01, irq=-1)
[    1.207532] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    1.213279] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.223696] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.230181] ehci-pci: EHCI PCI platform driver
[    1.234745] usbcore: registered new interface driver usb-storage
[    1.242079] mousedev: PS/2 mouse device common for all mice
[    1.258017] i2c /dev entries driver
[    1.264608] EDAC MC: ECC not enabled
[    1.268402] Xilinx Zynq CpuIdle Driver started
[    1.273073] sdhci: Secure Digital Host Controller Interface driver
[    1.279210] sdhci: Copyright(c) Pierre Ossman
[    1.283521] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.290535] sdhci-arasan e0100000.sdhci: No vmmc regulator found
[    1.296484] sdhci-arasan e0100000.sdhci: No vqmmc regulator found
[    1.336335] mmc0: SDHCI controller on e0100000.sdhci [e0100000.sdhci] using ADMA
[    1.344564] ledtrig-cpu: registered to indicate activity on CPUs
[    1.350935] usbcore: registered new interface driver usbhid
[    1.356450] usbhid: USB HID core driver
[    1.361173] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.367474] nand: Micron MT29F2G08ABAEAWP
[    1.371433] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.379022] nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[    1.390455] Bad block table found at page 131008, version 0x01
[    1.396634] Bad block table found at page 130944, version 0x01
[    1.402673] 10 cmdlinepart partitions found on MTD device pl35x-nand
[    1.408969] Creating 10 MTD partitions on "pl35x-nand":
[    1.414149] 0x000000000000-0x000000080000 : "boot"
[    1.419992] 0x000000080000-0x000000300000 : "uboot"
[    1.435810] 0x000000300000-0x000000500000 : "fpga1"
[    1.441631] 0x000000500000-0x000000700000 : "fpga2"
[    1.457487] 0x000000700000-0x000000780000 : "uboot_env"
[    1.473629] 0x000000780000-0x000000800000 : "miner_cfg"
[    1.489722] 0x000000800000-0x000001e00000 : "recovery"
[    1.505843] 0x000001e00000-0x000007d00000 : "firmware1"
[    1.522548] 0x000007d00000-0x00000dc00000 : "firmware2"
[    1.539272] 0x00000dc00000-0x000010000000 : "factory"
[    1.558049] nf_conntrack version 0.5.0 (7991 buckets, 31964 max)
[    1.565924] NET: Registered protocol family 10
[    1.571561] sit: IPv6 over IPv4 tunneling driver
[    1.576907] NET: Registered protocol family 17
[    1.581327] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    1.593893] can: controller area network core (rev 20120528 abi 9)
[    1.600097] NET: Registered protocol family 29
[    1.604467] can: raw protocol (rev 20120528)
[    1.608739] can: broadcast manager protocol (rev 20120528 t)
[    1.614364] can: netlink gateway (rev 20130117) max_hops=1
[    1.620035] 8021q: 802.1Q VLAN Support v1.8
[    1.624519] Registering SWP/SWPB emulation handler
[    1.630763] ubi0: attaching mtd8
[    1.944832] ubi0: scanning is finished
[    1.955668] ubi0: attached mtd8 (name "firmware2", size 95 MiB)
[    1.961534] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.968386] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.975134] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.982092] ubi0: good PEBs: 760, bad PEBs: 0, corrupted PEBs: 0
[    1.988086] ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
[    1.995274] ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 895408428
[    2.004314] ubi0: available PEBs: 0, total reserved PEBs: 760, PEBs reserved for bad PEB handling: 40
[    2.013534] ubi0: background thread "ubi_bgt0d" started, PID 823
[    2.024444] block ubiblock0_1: created from ubi0:1(rootfs)
[    2.029895] hctosys: unable to open rtc device (rtc0)
[    2.039420] ALSA device list:
[    2.042306]   No soundcards found.
[    2.047971] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    2.055380] Freeing unused kernel memory: 264K (c0746000 - c0788000)
[    2.523473] init: Console is alive
[    2.527027] init: - watchdog -
[    2.926501] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    3.020603] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    3.034724] init: - preinit -
[    3.611197] random: jshn urandom read with 0 bits of entropy available
[    3.811904] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    5.186740] macb e000b000.ethernet eth0: link up (100/Full)
[    5.192249] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    6.986377] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 896
[    7.002676] UBIFS (ubi0:2): recovery needed
[    7.061122] UBIFS (ubi0:2): recovery completed
[    7.065568] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data"
[    7.073366] UBIFS (ubi0:2): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    7.083230] UBIFS (ubi0:2): FS size: 76820480 bytes (73 MiB, 605 LEBs), journal size 3809280 bytes (3 MiB, 30 LEBs)
[    7.093690] UBIFS (ubi0:2): reserved for root: 3628421 bytes (3543 KiB)
[    7.100249] UBIFS (ubi0:2): media format: w4/r0 (latest is w4/r0), UUID 7A89DF36-1AA4-4847-888E-D3633E0807F3, small LPT model
[    7.113342] mount_root: switching to ubifs overlay
[    7.125697] urandom-seed: Seeding with /etc/urandom.seed
[    7.248421] procd: - early -
[    7.251279] procd: - watchdog -
[    7.899523] procd: - watchdog -
[    7.902800] procd: - ubus -
[    8.060105] procd: - init -
[    8.186357] macb e000b000.ethernet eth0: link down
[    8.441624] kmodloader: loading kernel modules from /etc/modules.d/*
[    8.450615] tun: Universal TUN/TAP device driver, 1.6
[    8.455588] tun: (C) 1999-2004 Max Krasnyansky
[    8.464684] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    8.477193] ip_tables: (C) 2000-2006 Netfilter Core Team
[    8.617702] xt_time: kernel timezone is -0000
[    8.628089] kmodloader: done loading kernel modules from /etc/modules.d/*
[   11.590942] Start post-upgrade process...
[   11.611176] device eth0 entered promiscuous mode
[   11.622889] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   12.186588] macb e000b000.ethernet eth0: link up (100/Full)
[   12.192168] br-lan: port 1(eth0) entered forwarding state
[   12.197545] br-lan: port 1(eth0) entered forwarding state
[   12.211878] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   12.500329] random: nonblocking pool is initialized
[   14.196337] br-lan: port 1(eth0) entered forwarding state
BitMaxz
legendary
Activity: 3472
Merit: 3217
Playbet.io - Crypto Casino and Sportsbook
Re: Hashboard not showing Temp readings
May 31, 2021, 11:26:50 AM
#2
Do you mind share your whole kernel logs?
We might see the issue from your kernel logs if you can share it here.

My guess maybe because of over-temp protection that is why the hash rate drops. If I'm right you can disable the sensor scanning but the problem is it might fry your hashboard.
spangyy
newbie
Activity: 16
Merit: 0
Re: Hashboard not showing Temp readings
May 31, 2021, 10:33:32 AM
#1
been using the Braiins OS+ firmware on a couple miners and found that i get more stable hashrate while using less power based on my setup , however yesterday i decided to test out some old boards i had laying around that would never show up in the bitmain firmware. I first dusted and cleaned the boards then placed them in miner to get readings , to my surprise most of the boards show up however im having issue where a few boards start out mining then gradually start loosing hashrate then temp readings go zero . any assistance would be appreciated

thanks
Bitcoin Forum>Bitcoin>Mining>Mining support
Jump to: