Errors from journal (also hardware/firmware)

veleno · August 15, 2024, 6:51am

Good morning, Community!
A lot of errors from journal!! Also Hardware/Firmware (drivers?)
Please how can fix it?
Thank you!!

Blockquote
– Journal begins at Sat 2024-08-03 11:22:01 CEST, ends at Thu 2024-08-15 08:20:09 CEST. –
Aug 15 07:27:22 pureos kernel: hi846 2-0020: i2c read error: -6
Aug 15 07:27:22 pureos kernel: dw9714 3-000c: I2C write fail
Aug 15 07:27:22 pureos kernel: dw9714 3-000c: dw9714_vcm_suspend I2C failure: -5
Aug 15 07:27:22 pureos kernel: s5k3l6xx: i2c_read: error during transfer (-6)
Aug 15 07:27:22 pureos kernel: debugfs: File ‘Capture’ in directory ‘dapm’ already present!
Aug 15 07:27:23 pureos kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43752-sdio for chip BCM43752/2
Aug 15 07:27:23 pureos systemd-udevd[469]: sda1: /usr/lib/udev/rules.d/85-librem5-storage.rules:7 Failed to write ATTR{/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.1/1-1.1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1/queue/rotational}, ignoring: No such file or directory
Aug 15 07:27:24 pureos sudo[648]: root : account validation failure, is your account locked? ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/swapoff /dev/zram0
Aug 15 07:27:24 pureos sudo[688]: root : account validation failure, is your account locked? ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/zramctl --reset /dev/zram0
Aug 15 07:27:24 pureos sudo[699]: root : account validation failure, is your account locked? ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/zramctl --find --size 5G
Aug 15 07:27:24 pureos sudo[704]: root : account validation failure, is your account locked? ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/mkswap /dev/zram0
Aug 15 07:27:24 pureos sudo[709]: root : account validation failure, is your account locked? ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/swapon /dev/zram0
Aug 15 07:27:24 pureos systemd[1]: Failed to start Linux zramswap setup.
Aug 15 07:27:27 pureos pipewire[881]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name ‘org.freedesktop.portal.Desktop’: no such name
Aug 15 07:27:28 pureos kernel: brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
Aug 15 07:27:28 pureos kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43752/2 wl0: Jul 13 2020 18:32:45 version 18.35.387.23.7 (b328500@shgit) (wlan=r880297) FWID 01-f50fdff0
Aug 15 07:27:29 pureos bluetoothd[1020]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Aug 15 07:27:29 pureos bluetoothd[1020]: sap-server: Operation not permitted (1)
Aug 15 07:27:29 pureos pulseaudio[882]: Found duplicated D-Bus path for adapter /org/bluez/hci0
Aug 15 07:27:30 pureos kernel: ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred
Aug 15 07:27:30 pureos kernel: ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5
Aug 15 07:27:30 pureos wpa_supplicant[668]: Failed to create interface p2p-dev-wlan0: -5 (Input/output error)
Aug 15 07:27:30 pureos wpa_supplicant[668]: nl80211: Failed to create a P2P Device interface p2p-dev-wlan0
Aug 15 07:31:45 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
Aug 15 07:33:48 pureos kernel: Bluetooth: hci0: sending frame failed (-49)
Aug 15 07:33:48 pureos kernel: Bluetooth: hci0: Opcode 0x0c03 failed: -49
Aug 15 07:37:24 pureos kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43752-sdio for chip BCM43752/2
Aug 15 07:37:24 pureos kernel: brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
Aug 15 07:37:24 pureos kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43752/2 wl0: Jul 13 2020 18:32:45 version 18.35.387.23.7 (b328500@shgit) (wlan=r880297) FWID 01-f50fdff0
Aug 15 07:37:25 pureos bluetoothd[1020]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Aug 15 07:37:25 pureos bluetoothd[1020]: sap-server: Operation not permitted (1)
Aug 15 07:37:26 pureos kernel: ieee80211 phy1: brcmf_p2p_create_p2pdev: timeout occurred
Aug 15 07:37:26 pureos kernel: ieee80211 phy1: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5
Aug 15 07:37:26 pureos wpa_supplicant[668]: Failed to create interface p2p-dev-wlan0: -5 (Input/output error)
Aug 15 07:37:26 pureos wpa_supplicant[668]: nl80211: Failed to create a P2P Device interface p2p-dev-wlan0
Aug 15 07:37:47 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
Aug 15 07:37:56 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
Aug 15 07:49:44 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
Aug 15 07:51:47 pureos kernel: Bluetooth: hci0: sending frame failed (-49)
Aug 15 07:51:47 pureos kernel: Bluetooth: hci0: Opcode 0x0c03 failed: -49
Aug 15 07:52:58 pureos kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43752-sdio for chip BCM43752/2
Aug 15 07:52:58 pureos kernel: brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
Aug 15 07:52:58 pureos kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43752/2 wl0: Jul 13 2020 18:32:45 version 18.35.387.23.7 (b328500@shgit) (wlan=r880297) FWID 01-f50fdff0
Aug 15 07:53:00 pureos bluetoothd[1020]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Aug 15 07:53:00 pureos bluetoothd[1020]: sap-server: Operation not permitted (1)
Aug 15 07:53:01 pureos kernel: ieee80211 phy2: brcmf_p2p_create_p2pdev: timeout occurred
Aug 15 07:53:01 pureos kernel: ieee80211 phy2: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5
Aug 15 07:53:01 pureos wpa_supplicant[668]: Failed to create interface p2p-dev-wlan0: -5 (Input/output error)
Aug 15 07:53:01 pureos wpa_supplicant[668]: nl80211: Failed to create a P2P Device interface p2p-dev-wlan0
Aug 15 08:09:19 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:09:29 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:09:39 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:09:49 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:09:59 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:10:09 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:10:19 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:10:39 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:10:49 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:10:59 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:11:09 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:11:19 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:11:29 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:11:39 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:11:49 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:11:59 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:12:09 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:12:19 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:12:23 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
Aug 15 08:13:29 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:15:49 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:15:59 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:16:19 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:16:29 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:16:39 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:16:49 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:16:59 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:17:01 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
Aug 15 08:17:29 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:17:39 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:17:49 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:17:59 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:18:09 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:18:19 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:18:29 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:18:39 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:18:49 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:18:59 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:19:09 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:19:12 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
Aug 15 08:19:49 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:19:59 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Aug 15 08:20:09 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
Blockquote

irvinewade · August 15, 2024, 7:19am

This may be because the root account is disabled by default. However the correct fix may not be to enable the root account. Instead, the correct fix may be to understand how these commands (all apparently relating to zram) have been introduced into the system, and address that.

General observation about Linux: yeah, that’s normal.

The journal will contain a number of incomprehensible messages. Unless you are actually experiencing a problem, or you really want to spend the time, sometimes it is better to ignore - because without the expertise, you have no way of knowing whether the message is important or just something that a developer decided to log at some point.

Sometimes it makes sense to

capture the journal output from a normal boot (if we are talking about a boot) immediately after reflash
strip the date/times
treat that as your baseline
then you can compare that with another boot later on.

irvinewade · August 15, 2024, 7:22am

A search in this forum shows that you are not the only one getting this message. I have no idea what it means.

JR-Fi · August 15, 2024, 8:04am

I cheated with AI: "The log message “kernel: bq25890-charger 3-006a: NTC state UNKNOWN” indicates that the kernel is having trouble determining the state of the NTC (Negative Temperature Coefficient) thermistor associated with the bq25890 charger. This could suggest a problem with the charger hardware, the thermistor itself, or the driver that manages the charger."

If it’s same with multiple devices, the last one is more plausible than others. Its another question, does this affect anything (or what should it effect), besides the log message?