** Changed in: feisty-backports
Status: Confirmed = Won't Fix
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
https://bugs.launchpad.net/bugs/127773
You received this bug notification because you are a member of Ubuntu
Scott,
Fix released where, Gutsy or Hardy?
If Hardy, can we backport into Gutsy?
On 12/11/07, Scott Kitterman [EMAIL PROTECTED] wrote:
Tested again with the new linux-image-2.6.24-1-generic and the battery
is now recognized as well as the CPU temp and A/C state. Marking fix
released.
**
Fixed in the 2.6.24 kernel in Hardy. I wouldn't recommend trying to run Gutsy
with the Hardy kernel.
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
https://bugs.launchpad.net/bugs/127773
You received this bug notification
Tested again with the new linux-image-2.6.24-1-generic and the battery
is now recognized as well as the CPU temp and A/C state. Marking fix
released.
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Released
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team
Works with the Gutsy HAL and the Hardy Kernel, so given that a HAL
backport broke Feisty, it looks like some kind of incompatibility.
Works now, so marking fix released.
** Changed in: hal (Ubuntu)
Status: Confirmed = Fix Released
--
A/C Status, CPU Temp, and Battery no longer recognized
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
The problem is that the proc filesystem (linux kernel) reports no
battery present. What does cat /proc/acpi/battery/BAT1 from a command
line spit out? It should say present:yes and then a bunch of
other info, assuming you have a battery.
On Thu, 2007-12-06 at 03:36 +, Scott Kitterman
Why remove hardy-kernel-candidate? I thought this was being worked on for
Hardy?
On 12/5/07, Leann Ogasawara [EMAIL PROTECTED] wrote:
** Tags removed: hardy-kernel-candidate
--
A/C Status, CPU Temp, and Battery no longer recognized as present after
upgrade to Gutsy in Dell Latitude L400
The 'hardy-kernel-candidate' tag has been removed because the report has
appropriately been targeted at the Hardy kernel. As you can see, the
bug report has been updated and tasked against the 'linux' package. The
'linux' package is the current Hardy kernel source. The kernel team
switched from
Hi All,
The Hardy Heron kernel was recently uploaded for testing. We'd really
appreciate it if you could try testing with this newer kernel and verify
if this issue still exists. Unfortunately, the Hardy Heron Alpha1
LiveCD was released with the older 2.6.22 kernel. You'll have to
manually
It appears to still be a problem. I reinstalled kde-guidance-
powermanager and booted into the kernel. I never saw a battery status
from it. Let me know when there are new kernels and I'll be glad to
continue to test.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
A/C
The good news is that the CPU fan problem described in Bug #127772
appears fixed, so I marked that one taken care of.
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
https://bugs.launchpad.net/bugs/127773
You received this bug
** Tags removed: hardy-kernel-candidate
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
https://bugs.launchpad.net/bugs/127773
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
This will be retargeted towards the Hardy kernel once it is released.
I've tagged this as hardy-kernel-candidate so that we make sure to
retarget this report once the new release is out. However against the
linux-source-2.6.22 package this is being marked as Won't Fix as it
does not meet the
On 12/2/07, Henrik Nilsen Omma [EMAIL PROTECTED] wrote:
This will be retargeted towards the Hardy kernel once it is released.
I've tagged this as hardy-kernel-candidate so that we make sure to
retarget this report once the new release is out. However against the
linux-source-2.6.22 package
Silly me. It does affect Feisty because of the HAL backport.
Nevermind. Ugh.
** Changed in: feisty-backports
Status: Invalid = Confirmed
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
A/C Status, CPU Temp, and Battery no longer recognized as present
This bug does not affect Feisty. If you are having Feisty problems, you
are having a different bug.
** Changed in: feisty-backports
Status: Confirmed = Invalid
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
On Sun, 25 Nov 2007, DJ Saltarelli wrote:
i wouldn't really fault the software here too much b/c there's no doubt
in my mind that there are bugs in the acpi bios on this machine. they
just weren't evident under feisty. if i upgraded to the lastest bios
under feisty, i would see acpi suspend
i wouldn't really fault the software here too much b/c there's no doubt
in my mind that there are bugs in the acpi bios on this machine. they
just weren't evident under feisty. if i upgraded to the lastest bios
under feisty, i would see acpi suspend button events every 30 secs.
reverting to the
Well it worked fine in Feisty and non-HAL using software can find it if ACPI
is disabled, so I don't think that's the issue.
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
https://bugs.launchpad.net/bugs/127773
You received
Perhaps the problem for Dell L400 anyway is that the kernel acpi is
misidentifying the battery slots? Under /proc/acpi/battery/ I have
BAT1, and no BAT0. Restart of hald shows:
Nov 23 10:26:21 itybity NetworkManager: debug [1195842381.209004]
nm_hal_device_added(): New device added (hal udi is
I found the order of /etc/rc2.d script was incorrect. It was S12hal S20acpid.
May be it was changed when I upgrade feisty to gutsy.
So, I changed S20acpid to S10acpid, and now, gnome-power-manager shows correct
AC BATTERY information.
But, fn+brightness does not yet shows brightness applet.
Not the problem I had.
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
https://bugs.launchpad.net/bugs/127773
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
After upgrade from feisty to gutsy, I have the same problem on a thinkpad t40.
gnome-power-manager shows always using only AC adapter.
HAL can't detect my battery, but acpi detect battery.
It apears :
(1) [EMAIL PROTECTED]:~$ lshal | grep battery
(1) [EMAIL PROTECTED]:~$ acpi -V
Battery 1:
I am also having this problem on a Thinkpad Z60t. It worked fine until I
restarted a service, and now doesn't recognize the battery at all.
I appears however:
[EMAIL PROTECTED]:~$ cat /proc/acpi/battery/BAT0/state
present: yes
capacity state: ok
charging state:
Im having the same problem on my Acer Aspire 5050
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
https://bugs.launchpad.net/bugs/127773
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Tags added: dell
** Tags removed: gutsy hal
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
https://bugs.launchpad.net/bugs/127773
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Tags removed: acpi
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
https://bugs.launchpad.net/bugs/127773
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I'm experiencing this problem as well on a Compaq Presario C571NR.
However, I didn't experience the problem until I manually restarted the
dbus service. It ran fine before I did this. Restarting the hal
service fixes the problem, so that's an annoying work around for the
time being.
--
A/C
I understand gkrellm could work as a workaround, but that's not what I'm
after. I want the original icon in the panel, from acpi, with the
accurate, interesting diagnostics.
Is there any way I can find what aspect of the kernel is at fault here
and report back? Or copy something across from the
** Changed in: acpi (Ubuntu)
Status: New = Invalid
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
https://bugs.launchpad.net/bugs/127773
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: acpi = linux-source-2.6.22
Importance: Undecided = Medium
Status: Invalid = Confirmed
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
Disabling acpi did nothing. Still always on AC, according to this.
Gutsy release out, no fix, not impressed.
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
https://bugs.launchpad.net/bugs/127773
You received this bug
On Thursday 18 October 2007 14:54, Matt Hoy wrote:
Disabling acpi did nothing. Still always on AC, according to this.
Install gkrellm and see if it can status the battery (it can for me with
acpi=off). While it's not as integrated as kde-guidance-powermanager, it's a
lot less of a resource
Booting with acpi=off solved (worked around) that fan problem I was
having in Bug #127772. With acpi=off I get the battery icon on my tray
(so the presence of the battery is now recognized), but no indication
that the system knows when it switches to/from battery or what the
battery charge level
Although ancient, the gkrellm is still present in Gutsy. With acpi off,
it can get battery status correctly (I expect it doens't use HAL). So
that's a work around.
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
Interesting. What are the downsides of using that?
And I suppose I just edit the grub entry to have acpi=off at the end?
On 10/17/07, Scott Kitterman [EMAIL PROTECTED] wrote:
Although ancient, the gkrellm is still present in Gutsy. With acpi off,
it can get battery status correctly (I expect
Interesting. What are the downsides of using that?
And I suppose I just edit the grub entry to have acpi=off at the end?
I'll try it in a bit and report back.
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
Scott Kitterman wrote on 2007-10-11: Re: [Bug 127773] Re: A/C Status, CPU
Temp, and Battery no longer recognized as present after upgrade to Gutsy
in Dell Latitude L400
Right but installing the feisty-backports version (from Gutsy) in Feisty
causes the same problem. Problem is HAL and
Final kernel has been rolled, so this isn't going to be fixed. With any luck
maybe someone will figure out the problem and it can be added to a kernel
update.
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
** Summary changed:
- A/C Status, CPU Temp, and Battery no longer recognized as present after
upgrade to Gutsy in Dell Latitdue L400
+ A/C Status, CPU Temp, and Battery no longer recognized as present after
upgrade to Gutsy in Dell Latitude L400
** Tags added: acpi battery gutsy hal
--
A/C
Should be in:
https://launchpad.net/ubuntu/gutsy/+package/hal
?
Installing hal and/or hal-info from the Feisty repository (using dpkg -i
--force-all), and rebooting, fixes nothing.
If anyone on gutsy HAS managed to fix this, somehow, please let us know
in a reply/comment to this.
--
A/C
Booting 2.6.20-16-generic gives me a regular, working battery.
2.6.22-14-generic is the problem.
--
A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade
to Gutsy in Dell Latitude L400
https://bugs.launchpad.net/bugs/127773
You received this bug notification because
On Thu, 11 Oct 2007 17:18:26 - Matt Hoy [EMAIL PROTECTED] wrote:
Should be in:
https://launchpad.net/ubuntu/gutsy/+package/hal
?
Installing hal and/or hal-info from the Feisty repository (using dpkg -i
--force-all), and rebooting, fixes nothing.
Right but installing the feisty-backports
44 matches
Mail list logo
