Your message dated Mon, 30 May 2022 15:11:40 +0200
with message-id <2113537.Mh6RI2rZIc@bagend>
and subject line Re: Bug#964181: linux-image-4.19.0-9-amd64: Unable to get
battery status
has caused the Debian Bug report #927163,
regarding linux-image-4.19.0-4-amd64: Missing modules for AXP288 power fuel
gauge driver
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
927163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927163
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:linux
Version: 4.19.28-2
Severity: wishlist
Dear Maintainer,
In #895129 axp288_fuel_gauge was included as a module for x86 platforms.
After that the battery icon was actually showing on my Cherrytrail tablet.
But since then, this has again stopped working (and I'm not sure it was
actually reporting a correct state), and also it never detected the AC power
being connected. I believe there are still some missing stuff to get this
working.
Looking at a commit for ARM I can see this:
https://salsa.debian.org/kernel-team/linux/commit/0138e6bc4eedd8c10ad637e742a4fe6c625c6def
There seems to be some additional things in there.
AXP20X_ADC, CHARGER_AXP20X, BATTERY_AXP20X, GPIO_AXP209,
AXP288_CHARGER, EXTCON_AXP288, AXP288_ADC
Also, looking at the kernel source, there seems to be a case where
the axp288_fuel_gauge module waits for axp288_adc to load (this module
is currently not built for x86):
https://github.com/torvalds/linux/blob/dc4060a5dc2557e6b5aa813bf5b73677299d62d2/drivers/power/supply/axp288_fuel_gauge.c#L774
This probing code was appearantly added late 2017 (so, possibly that code
wasn't in the kernel that was first released in Debian with the
axp288_fuel_gauge module on x86, which might possibly explain why I saw
the inaccurate reading (I recall it always reporting 100%).
Thanks,
//Marcus
-- System Information:
Debian Release: buster/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8),
LANGUAGE=sv_SE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-image-4.19.0-4-amd64 depends on:
ii initramfs-tools [linux-initramfs-tool] 0.133
ii kmod 26-1
ii linux-base 4.6
Versions of packages linux-image-4.19.0-4-amd64 recommends:
ii apparmor 2.13.2-10
ii firmware-linux-free 3.4
ii irqbalance 1.5.0-3
Versions of packages linux-image-4.19.0-4-amd64 suggests:
pn debian-kernel-handbook <none>
ii grub-pc 2.02+dfsg1-16
pn linux-doc-4.19 <none>
Versions of packages linux-image-4.19.0-4-amd64 is related to:
ii firmware-amd-graphics 20190114-1
pn firmware-atheros <none>
pn firmware-bnx2 <none>
pn firmware-bnx2x <none>
pn firmware-brcm80211 <none>
pn firmware-cavium <none>
pn firmware-intel-sound <none>
pn firmware-intelwimax <none>
pn firmware-ipw2x00 <none>
pn firmware-ivtv <none>
pn firmware-iwlwifi <none>
pn firmware-libertas <none>
ii firmware-linux-nonfree 20190114-1
ii firmware-misc-nonfree 20190114-1
pn firmware-myricom <none>
pn firmware-netxen <none>
pn firmware-qlogic <none>
pn firmware-realtek <none>
pn firmware-samsung <none>
pn firmware-siano <none>
pn firmware-ti-connectivity <none>
pn xen-hypervisor <none>
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Version: 5.10.1-1~exp1
On Monday, 18 April 2022 17:20:51 CEST Diederik de Haas wrote:
> > @@ -7234 +7234 @@ CONFIG_MMA9553=m
> > -# CONFIG_AXP288_ADC is not set
> > +CONFIG_AXP288_ADC=m
>
> I suspect that this was the crucial missing piece ...
>
> > After recompilation of the kernel the directory /sys/class/power_supply
> > was populated and I got a battery indicator on the taskbar.
>
> ... and that got added in aa87da1f902dba04f3b15680e178ad336e985f4f and is
> part of the 5.10 kernels (previously it was only enabled on arm64 and
> armhf).
>
> Tino and Markus:
> Can you verify whether the issue is fixed with a 5.10+ kernel?
Tino already confirmed it was fixed (#964181) and I'm quite sure this is the
same issue. As there hasn't been a response in >1 month, I'm closing this
issue with the same kernel version as well.
If you believe the issue is still present, feel free to reopen this issue.
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
