Bug 1402652
Summary: | Battery not working since Fedora 24 on Dell Inspiron 7537 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dominik Gronkiewicz <gronki> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 25 | CC: | cz172638, gansalmon, ichavero, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-12-08 16:27:39 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dominik Gronkiewicz
2016-12-08 04:06:05 UTC
Our position hasn't changed. CONFIG_ACPI_REV_OVERRIDE_POSSIBLE has the potential to cause more problems than it solves. Overriding the REV changes how all tables are interpreted, not the one for the battery. We don't plan on turning it on. What problems can it cause? The flag only allows user to override the ACPI _REV, does not set it by default. I can see no harm it will cause for an user who doesn't turn it on. It is extremely unfair that first someone "fixed" the kernel by changing the _REV value, breaking a perfectly working system, and now you don't provide any way to fix this. Enabling this flag WILL NOT BREAK ANY SINGLE MACHINE. Disabling it breaks all Dell Inspiron 7xxx machines, which come shipped with Linux, therefore are a popular choice among Linux users. If you don't plan to enable this flag, please provide an another solution to make my laptop work. (Compiling my kernel every two weeks is ridiculous and is obviously not an acceptable solution.) To be honest, I feel extremely sorry and dissapointed with Fedora community right now. Dominik. To anyone affected by this problem, here is how to deal with this issue in Fedora 25: To exclude kernel from the repositories, edit the .repo files gedit admin:///etc/yum.repos.d/fedora{,-updates}.repo Append following at the end of each of three sections in both files: exclude=kernel* perf python-perf Note that the above change will crash PackageKit while trying to fetch updates in Fedora 24. After moving to 25, everything works for me. Now you can either trust me and add the kernel repository I am using for my laptop (Dell 7537) https://copr.fedorainfracloud.org/coprs/gronki/kernel-dell7537/ or build the kernel using this easy tutorial: https://fedoramagazine.org/building-fedora-kernel/ The only edit you need to do for battery slot to work is to append this line: CONFIG_ACPI_REV_OVERRIDE_POSSIBLE=y to config-local file. You can also follow the "standard" way using rpmdev tools only, but using fedpkg is way easier. Also, when using rpmbuild alone, you have to add your flags everytime you want to build a new version (the old source gets wiped out), while using fedpkg makes it as easy as merging changes from the upstream git branch (origin/f25) into your local branch. Building kernel takes a lot of time and requires plenty of resources so you might want to do it overnight or do it on some other machine that won't burn your knees. (Copr is super convenient for this purpose.) After installing the custom kernel, you need to add following kernel boot parameters to /etc/default/grub: acpi_osi=Linux acpi_rev_override Hope this gets indexed by google so that others can find this solution. I got very frustrated using rpmbuild, but using fedpkg and copr is so convenient I can live with the custom kernel. :) |