battery gauge broken on Pinebook Pro with Slarm64
by wowbaggerHU from LinuxQuestions.org on (#5MENT)
Hello Everyone,
After running into similar problems in the past (1, 2) I am kind of hesitant to open this thread, but here I am...
My problem is that the XFCE 4 battery meter doesn't show any useful information for the battery of my Pinebook Pro.
I just noticed this behavior today, while yesterday I have upgraded the Slarm64 -current OS running on it.
I checked Code:slackpkg install-new too, and did not see anything worth installing, but eventually ended up installing most of the (non-KDE) packages listed there.
Still, the battery meter shows no battery information, but the battery still works, charges, I just have no reading on its state.
I also stumbled into this article, and I do have the same output in dmesg:
Code:root@janos-pbp:~# dmesg | fgrep -i bat
[ 7.437466] power_supply cw2015-battery: Not all required supplies found, defer probe
[ 7.450290] power_supply cw2015-battery: Not all required supplies found, defer probe
[ 7.475889] power_supply cw2015-battery: cw2015-battery: Found supply : dc-charger
[ 7.475913] power_supply cw2015-battery: cw2015-battery: Found supply : tcpm-source-psy-4-0022
root@janos-pbp:~#I have a "older" (5.12) kernel, that wasn't updated yesterday, and that was known to work (at least the battery meter worked OK). Plus while googling for the above error message, I found one of my own threads from a year ago, when I had the same output in dmesg, but the xfce battery meter was working just fine.
Plus I have the kernel code, mentioned in the article above compiled into the kernel as a module (CONFIG_TYPEC_FUSB302 and Co.):
Code:root@janos-pbp:~# lsmod | fgrep fusb
fusb302 28672 0
tcpm 65536 1 fusb302
root@janos-pbp:~# zcat /proc/config.gz | fgrep TYPEC
CONFIG_TYPEC=m
CONFIG_TYPEC_TCPM=m
CONFIG_TYPEC_TCPCI=m
CONFIG_TYPEC_RT1711H=m
CONFIG_TYPEC_TCPCI_MAXIM=m
CONFIG_TYPEC_FUSB302=m
CONFIG_TYPEC_UCSI=m
CONFIG_TYPEC_HD3SS3220=m
CONFIG_TYPEC_TPS6598X=m
CONFIG_TYPEC_STUSB160X=m
CONFIG_TYPEC_MUX_PI3USB30532=m
CONFIG_TYPEC_DP_ALTMODE=m
# CONFIG_TYPEC_NVIDIA_ALTMODE is not set
CONFIG_CROS_EC_TYPEC=m
CONFIG_PHY_ROCKCHIP_TYPEC=ySo this suggests a different cause.
Also, there are no missing libs/dependencies for the xfce4-power-manager (otherwise it wouldn't start up...)
As mentioned I also installed any packages shown in Code:slackpkg install-new, that had a remote chance of influencing this for the better.
I installed:
- editorconfig-core-c-0.12.5-aarch64-1
- haveged-1.9.14-aarch64-3
- icecream-1.3.1-aarch64-3
- libmypaint-1.6.1-aarch64-4
- mlt-6.26.1-aarch64-1
- openal-soft-1.21.1-aarch64-2-
- opencv-4.5.3-aarch64-1
- rubygem-asciidoctor-2.0.15-aarch64-1
- sc-im-20200904_bdd936a-aarch64-3:
- spirv-llvm-translator-12.0.0-aarch64-1
But neither of those actually helped, and the situation is unchanged.
The last time when I had a similar issue with KDE, it was the mozjs* package's upgrade that broke the KDE power meter.
This time, I'm not seeing anything suspicious in the output of Code:slackpkg clean-system.
Any ideas how I should get to the end of this?
Thanks!
Best Regards,
Janos
After running into similar problems in the past (1, 2) I am kind of hesitant to open this thread, but here I am...
My problem is that the XFCE 4 battery meter doesn't show any useful information for the battery of my Pinebook Pro.
I just noticed this behavior today, while yesterday I have upgraded the Slarm64 -current OS running on it.
I checked Code:slackpkg install-new too, and did not see anything worth installing, but eventually ended up installing most of the (non-KDE) packages listed there.
Still, the battery meter shows no battery information, but the battery still works, charges, I just have no reading on its state.
I also stumbled into this article, and I do have the same output in dmesg:
Code:root@janos-pbp:~# dmesg | fgrep -i bat
[ 7.437466] power_supply cw2015-battery: Not all required supplies found, defer probe
[ 7.450290] power_supply cw2015-battery: Not all required supplies found, defer probe
[ 7.475889] power_supply cw2015-battery: cw2015-battery: Found supply : dc-charger
[ 7.475913] power_supply cw2015-battery: cw2015-battery: Found supply : tcpm-source-psy-4-0022
root@janos-pbp:~#I have a "older" (5.12) kernel, that wasn't updated yesterday, and that was known to work (at least the battery meter worked OK). Plus while googling for the above error message, I found one of my own threads from a year ago, when I had the same output in dmesg, but the xfce battery meter was working just fine.
Plus I have the kernel code, mentioned in the article above compiled into the kernel as a module (CONFIG_TYPEC_FUSB302 and Co.):
Code:root@janos-pbp:~# lsmod | fgrep fusb
fusb302 28672 0
tcpm 65536 1 fusb302
root@janos-pbp:~# zcat /proc/config.gz | fgrep TYPEC
CONFIG_TYPEC=m
CONFIG_TYPEC_TCPM=m
CONFIG_TYPEC_TCPCI=m
CONFIG_TYPEC_RT1711H=m
CONFIG_TYPEC_TCPCI_MAXIM=m
CONFIG_TYPEC_FUSB302=m
CONFIG_TYPEC_UCSI=m
CONFIG_TYPEC_HD3SS3220=m
CONFIG_TYPEC_TPS6598X=m
CONFIG_TYPEC_STUSB160X=m
CONFIG_TYPEC_MUX_PI3USB30532=m
CONFIG_TYPEC_DP_ALTMODE=m
# CONFIG_TYPEC_NVIDIA_ALTMODE is not set
CONFIG_CROS_EC_TYPEC=m
CONFIG_PHY_ROCKCHIP_TYPEC=ySo this suggests a different cause.
Also, there are no missing libs/dependencies for the xfce4-power-manager (otherwise it wouldn't start up...)
As mentioned I also installed any packages shown in Code:slackpkg install-new, that had a remote chance of influencing this for the better.
I installed:
- editorconfig-core-c-0.12.5-aarch64-1
- haveged-1.9.14-aarch64-3
- icecream-1.3.1-aarch64-3
- libmypaint-1.6.1-aarch64-4
- mlt-6.26.1-aarch64-1
- openal-soft-1.21.1-aarch64-2-
- opencv-4.5.3-aarch64-1
- rubygem-asciidoctor-2.0.15-aarch64-1
- sc-im-20200904_bdd936a-aarch64-3:
- spirv-llvm-translator-12.0.0-aarch64-1
But neither of those actually helped, and the situation is unchanged.
The last time when I had a similar issue with KDE, it was the mozjs* package's upgrade that broke the KDE power meter.
This time, I'm not seeing anything suspicious in the output of Code:slackpkg clean-system.
Any ideas how I should get to the end of this?
Thanks!
Best Regards,
Janos