Description of problem: Battery is not detected in my Toshiba L655-S5117 Laptop. It is an Intel Core i3 with integrated video. I unplug the current cable, the computer still thinks it is on AC current. I tried Mandriva 2010.2, mandriva 2011 beta and Mageia and the same happens in all of them. ACPI shows: $ acpi -bV Adapter 0: on-line Cooling 0: Processor 0 of 10 Cooling 1: Processor 0 of 10 Cooling 2: Processor 0 of 10 Cooling 3: Processor 0 of 10 Cooling 4: LCD 0 of 7 This is the output of lspci: 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) 00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 05) 00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 05) 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05) 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05) 02:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 03:00.0 Ethernet controller: Atheros Communications AR8152 v1.1 Fast Ethernet (rev c1) ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02) ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02) ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02) ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02) ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02) ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02) Version-Release number of selected component (if applicable): kernel-desktop-2.6.38.7-1.mga-1-1.mga1 How reproducible: Run Mageia in a Toshiba L655-S5117 Laptop, live or installed, and see no info for the battery or "battery no present" message in ACPI info Steps to Reproduce: 1. Install Mageia, or use the live CD 2. Look for any battery information
Funny, at the same time I was reporting this bug, someone found the way to solve it at kernel level here: http://techinterplay.com/fix-toshiba-battery-issue-linux.html I hope that can help to fix this in Mageia. Right now I don't feel like compiling the kernel as I would have done a few years ago :p. Cu!
$ zgrep DSDT /proc/config.gz CONFIG_ACPI_CUSTOM_DSDT_FILE="" # CONFIG_ACPI_CUSTOM_DSDT is not set CONFIG_ACPI_CUSTOM_DSDT_INITRD=y While the option to load a custom DSDT from /etc/initramfs-tools/DSDT.aml by the kernel is not set, the option to have the initrd load one is. grep DSDT ./mkinitrd-mkinitrd DEFAULT_DSDT_FILES="/boot/dsdt.aml /boot/DSDT.aml" dsdt_files=$DEFAULT_DSDT_FILES cp -aL $dsdt_file $MNTIMAGE/DSDT.aml I'd go ahead and try putting the altered DSDT in /boot, and then try running mkinitrd --dsdt=/boot/dsdt.aml ... Might not work, but I think it's worth a try. Make a backup of the original initrd file, and ensure you have an alternate method to boot, if it doesn't work.
CC: (none) => davidwhodgins
Assignee: bugsquad => tmb
It didn't work. I made an initrd image with the modified DSDT file, made a backup of the original and used the new one instead so the initrd.img link pointed to the new version. It booted OK but it still doesn't see the battery. Should I wait for a next kernel release for Mageia? Do you need any other information?
not being able to fix the dsdt by adding a fixed version to the initrd is bug 2831
CC: (none) => lohmaier+mageia
We have kernel 2.6.38.8-8 now, did that change anything?
CC: (none) => marja11
Baterry is still undetected. As soon as I have time I will try the dsdt thing again.
It didn't work I generated the initrd image with the last kernel, 2.6.38.8-desktop-10, and still no battery. I guess the option is to recompile the kernel, but I'm not willing to do that with every new kernel release so I'll stay with no battery info in Mageia. Any other idea of something I could try?
I installed Mageia 2 beta 2 last night and it doesn't see the battery.
Back to Mageia 1 and I finally had time to compile the kernel following the instructions of the link of the second post and I see the battery! :'( Now I can wait for Mageia 2 knowing that I have a way to make it see and use my laptop's battery. I hope the fix can be added to the kernel someday tough. Regards!
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Version: 1 => 2
Updating the "Version" field. Bug is still present in Mageia 2.
Tried Mageia 3 Beta 2 and the problem still exists. I tried the KDE live DVD version.
Version: 2 => Cauldron
Tried Mageia 4 Beta 2 and the problem has been fixed! :D :D :D I don't know if it is the new kernel or what, but thanks a lot, now I can see my battery right away and I don't need to compile the kernel anymore. PS: I don't know if I should mark this as solved or if someone in the QA team should do it.
as you are the reporter, you can Close if....
Status: NEW => RESOLVEDResolution: (none) => FIXED