Bug#927163: linux-image-4.19.0-4-amd64: Missing modules for AXP288 power fuel gauge driver
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 kmod26-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 ii grub-pc 2.02+dfsg1-16 pn linux-doc-4.19 Versions of packages linux-image-4.19.0-4-amd64 is related to: ii firmware-amd-graphics 20190114-1 pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas ii firmware-linux-nonfree20190114-1 ii firmware-misc-nonfree 20190114-1 pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- debconf-show failed
Bug#897060: Systems seems to boot normally now
I'm having issues since the last kernel upgrade on my Cherrytrail tablet, not sure if it's the kernel or possible mesa-related. Need to dig into it some more. Booting normally just stalls after showing a couple of console messages (about when GDM would normally show up). Booting in rescue mode and then exiting out sometimes works, sometimes not. But then screen rotation is broken and stuck in portrait mode (I guess iio-sensor-proxy was started before the driver was ready in that case). It also seems flaky and usually the GUI locks up after a while also when booting up this way. //Marcus
Bug#895129: linux: Battery not detected on Lamina 2-in-1 tablet
It seems these modules are already built for armhf: https://salsa.debian.org/kernel-team/linux/commit/0138e6bc4eedd8c10ad63 7e742a4fe6c625c6def Fixed in bug #873038 Maybe these should also be enabled for x86/amd64. //Marcus
Bug#895129: linux: Battery not detected on Lamina 2-in-1 tablet
Source: linux
Severity: normal
Dear Maintainer,
I have a Lamina T-1016B 2-in-1 tablet where the battery is not detected
(the top bar in GNOME shows only the power icon, like on the desktop machine).
Checking in /var/log/messages I could see the following (grep:ing on ACPI):
Apr 6 09:17:21 eridanus kernel: [5.663167] ACPI: AC: found native INT33F4
PMIC, not loading
Apr 6 09:17:21 eridanus kernel: [5.956763] ACPI: AC: found native INT33F4
PMIC, not loading
Apr 6 08:20:24 eridanus kernel: [5.720266] ACPI: AC: found native INT33F4
PMIC, not loading
Apr 6 08:20:24 eridanus kernel: [6.020086] ACPI: AC: found native INT33F4
PMIC, not loading
Apr 6 08:23:09 eridanus kernel: [5.656934] ACPI: AC: found native INT33F4
PMIC, not loading
Apr 6 08:23:09 eridanus kernel: [5.979635] ACPI: AC: found native INT33F4
PMIC, not loading
Apr 6 08:25:49 eridanus kernel: [5.849791] ACPI: AC: found native INT33F4
PMIC, not loading
Apr 6 08:25:49 eridanus kernel: [6.150902] ACPI: AC: found native INT33F4
PMIC, not loading
Checking in the kernel sources, I could see the following:
In https://github.com/torvalds/linux/blob/master/drivers/acpi/battery.c
There is a blacklist of ACPI HIDs at line 101:
/* Lists of PMIC ACPI HIDs with an (often better) native battery driver */
static const char * const acpi_battery_blacklist[] = {
"INT33F4", /* X-Powers AXP288 PMIC */
};
Further down there's a section for bailing out on blacklisted HIDs at 1491:
for (i = 0; i < ARRAY_SIZE(acpi_battery_blacklist); i++)
if (acpi_dev_present(acpi_battery_blacklist[i], "1", -1)) {
pr_info(PREFIX ACPI_BATTERY_DEVICE_NAME
": found native %s PMIC, not loading\n",
acpi_battery_blacklist[i]);
return;
}
In __init acpi_battery_init_async
I suppose enabling the approriate module(s) would maybe solve this.
In the make menuconfig I could see the following drivers:
AXP288_ADC, AXP288_CHARGER, and AXP288_FUEL_GAUGE
I tried building a custom kernel, but upon booting in panics,
but it seems to be because the initrams fs is not able to mount, I guess
the image wasn't properly installed in GRUB, or something like that.
By the way, the info below shows kernel 4.14, but that's because I ran
reportbug from my desktop, and haven't rebooted into the newest kernel yet
I hope this doesn't create a hassle.
Thanks!
Regards,
Marcus Lundblad
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
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
Bug#828818: Same issue on a LAMINA 2-in-1 tablet
I'm having the same issue on a LAMINA tablet. A collegue has a similar tablet with Mint on it, that one has INTEL_SOC_PMIC_CHTDC_TI built as a module (it can be seen with lsmod). It seems this module is not built in Debian. The following could maybe be relevant: # CONFIG_INTEL_SOC_PMIC_CHTWC is not set # CONFIG_INTEL_SOC_PMIC_CHTDC_TICONFIG_INTEL_SOC_PMIC_CHTDC_TICONFIG_IN TEL_SOC_PMIC_CHTDC_TI is not set I think these are for different controllers. I tried enabling CONFIG_INTEL_SOC_PMIC_CHTDC_TI as a module, but upon booting the newly installed kernel it panics (I think it can't find the boot file system, not sure how to properly do this, or if I did something wrong). Also screen brightness is non-working, in the boot log I can see something about "Failed to own the pwm chip". Also suspend/resume is very flaky, sometimes it works once, but then never wakes up (actually I think it's still running, as the battery seems to drain), maybe this is somehow related to power management or that it fails turning on the screen again. //Marcus
Bug#873164: linux-image-4.12.0-1-amd64: Enable intel_cht_int33fe
Package: src:linux Version: 4.12.6-1 Severity: normal I have a 2-in-1 tablet based on the Cherry Trail SoC, currently there is no battery level status reported. I belive this would be supplied by the intel_cht_int33fe driver, which doesn't currently seem to be built in Debian. Looking at /boot/config-4.12.0-1-amd64 I see: # CONFIG_INTEL_CHT_INT33FE is not set And this module doesn't appear under /lib/modules Thanks! -- Package-specific info: ** Version: Linux version 4.12.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 6.4.0 20170805 (Debian 6.4.0-3) ) #1 SMP Debian 4.12.6-1 (2017-08-12) ** Command line: BOOT_IMAGE=/vmlinuz-4.12.0-1-amd64 root=UUID=6ef2b100-fc78-4834-818d-b2ec7da9f38f ro quiet init=/bin/systemd
