[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067495
** Tags removed: performing-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067495
Title:
Only one battery visible after upgrade to Quantal
To manage notifications about this bug go to:
Scott Kitterman, as per
http://www.dell.com/support/troubleshooting/us/en/19/Product/latitude-e6320
an update is available for your BIOS (A18). If you update to this, does
it change anything?
If not, could you please both specify what happened, and provide the output of
the following terminal
Can you next test v3.5.3 ?
v3.5.3 : http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.3-quantal/
If v3.5.3 is good, please test v3.5.4:
v3.5.4 : http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.4-quantal/
If v3.5.4 is good, then we know the bug was introduced in v3.5.5.
--
You received
With v3.3 final, it shows a BAT2 in upower --dump, but still not in KDE,
but I'll assume that's a different issue.
$ upower --dump
Device: /org/freedesktop/UPower/devices/line_power_AC
native-path:
/sys/devices/LNXSYSTM:00/device:00/ACPI0003:00/power_supply/AC
power supply:
I still have my last precise kernel installed and it was BAT2 on that
one too, so that's consistent.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067495
Title:
Only one battery visible after
BAT0/2 both show in 3.4.0-030400-generic #201205221131 too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067495
Title:
Only one battery visible after upgrade to Quantal
To manage notifications
BAT0/2 both present in v3.5-rc4-quantal too, but when I booted back to
the current quantal kernel, it's back to just BAT0, so that should
narrow it down considerably.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That's good news. Can you also test v3.5-rc6 and v3.5 final:
v3.5-rc7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc6-quantal/
v3.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-quantal/
Thanks again for testing!
--
You received this bug notification because you are a
BAT0/BAT2 with both of those too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067495
Title:
Only one battery visible after upgrade to Quantal
To manage notifications about this bug go to:
That's interesting. Thanks for testing. That means the regression was
introduced in one of the stable updates. Can you test the following:
v3.5.2 : http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.2-quantal/
Based on the results of that kernel, we can then try 3.5.1 or 3.5.3.
--
You
BAT0/BAT2 present on that one too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067495
Title:
Only one battery visible after upgrade to Quantal
To manage notifications about this bug go to:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.7 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
Once you've tested the
In case this helps:
$ ls /sys/devices/LNXSYSTM\:00/device\:00/PNP0C0A\:00/power_supply/
BAT0
No BAT1/2 there.
** Tags removed: needs-upstream-testing
** Tags added: kernel-unable-to-test-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug
I'd like to perform a bisect to figure out what commit caused this
regression. It would be very helpful to know the earliest kernel where
the issue started happening as well as the latest kernel that did not
have this issue.
Can you test the following kernels and report back? We are looking for
15 matches
Mail list logo
