I've done some tests with the 2.4.18 kernel, and I have the same
problem. I've noticed that when removing a full-charged battery
(either the first one or the second one), a light at the middle
of the rear of the machine fluctuates for a few seconds, then
switches off; I assume this is because there
On Wed, Apr 14, 2004 at 11:52:04AM +1000, Benjamin Herrenschmidt wrote:
> Do enough tests to have some statistic, it may not fail all the time,
> could be only occasional. It's also possible that the problem is indeed
> the low-charge sleep kicking too late, but it could be the kernel
> not always
>
> This is indicative of a reset of the power manager chip, which will
> produce this symptom 100% of the time. This can be artifically induced,
> but I believe to do this you have to hold shift-ctl-alt-power when the
> machine is off then release them (on recent models). This should *not*
> hap
Vincent Lefevre wrote:
ps. you meant 1984-01-01 not 1904-01-01 right?
No, it was 1904.
This is indicative of a reset of the power manager chip, which will
produce this symptom 100% of the time. This can be artifically induced,
but I believe to do this you have to hold shift-ctl-al
On Wed, 2004-04-14 at 09:04, Vincent Lefevre wrote:
> BTW, I've just noticed another difference: I had kernel 2.4.25 at
> this time (for the #1 -> #2 change). But as the default kernel is
> 2.4.18 on my machine and I had to power the machine on, it booted
> with this kernel 2.4.18, and the test wi
Hi,
On 2004-04-13 18:40:35 +0200, Julien BLACHE wrote:
> Vincent, are you running a 2.4 or 2.6 kernel ?
The problem occurred with 2.4.25. When I had the same problem in
January, I'm quite sure I had 2.4.22.
> I noticed the same kind of problem with 2.4 kernels after 2.4.20. It's
> impossible to
On 2004-04-13 10:29:34 -0600, Sam George wrote:
> So I believe you are saying that you have two batteries, and that when
Yes I have two batteries (initially both charged, and after I got
the problem when swapping #1 to #2, I did the test with #2 only,
just to be sure that swapping battries could
Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
Hi,
> Or maybe you just wasn't fast enough flipping the battery... I suspect
> we don't power things down as efficiently than MacOS when going to sleep
> (we just don't have the HW infos for some stuffs like the thermostat/fan
> controllers and ma
On 2004 Apr 13 , at 09:32, Vincent Lefevre wrote:
On 2004-04-13 08:37:51 -0600, Sam George wrote:
Another possibility you perchance did not consider is that your bridge
battery may be dead. The bridge battery sustains main memory while
you
switch out the main battery.
Unlikely, as it did
On 2004-04-13 08:37:51 -0600, Sam George wrote:
> Another possibility you perchance did not consider is that your bridge
> battery may be dead. The bridge battery sustains main memory while you
> switch out the main battery.
Unlikely, as it did work when I removed the second battery and put it
On 2004 Apr 13 , at 03:36, Vincent Lefevre wrote:
On 2004-04-13 13:31:23 +1000, Benjamin Herrenschmidt wrote:
Or maybe you just wasn't fast enough flipping the battery...
This took just a few seconds. I had prepared the second battery to do
the change as fast as possible.
I did the same with
On 2004-04-13 13:31:23 +1000, Benjamin Herrenschmidt wrote:
> Or maybe you just wasn't fast enough flipping the battery...
This took just a few seconds. I had prepared the second battery to do
the change as fast as possible.
I did the same with the second battery only (removing it, waiting for
a
On Tue, 2004-04-13 at 11:25, Vincent Lefevre wrote:
> Same problem as before... :( But this time I was using the
> pbbuttonsd 0.5.10-1 package.
>
> To summarize, the battery of my PowerBook G4 got too low and the machine
> was put into sleep. I closed the lid, changed the battery, but when
> I reo
Same problem as before... :( But this time I was using the
pbbuttonsd 0.5.10-1 package.
To summarize, the battery of my PowerBook G4 got too low and the machine
was put into sleep. I closed the lid, changed the battery, but when
I reopened the lid, I noticed that the PowerBook was in fact off. And
> > I wasn't going to dig into smartbatt programming, thanks.
>
> :-) Do we expose all battery-related info PMU gives us via /proc/pmu?
That's not much. No min/max voltage, at any rate.
> > Did your voltage continuously drop even when charge left was zero?
>
> Mostly yes, but voltage also depends
On 27 Jan, this message from Michael Schmitz echoed through cyberspace:
>> > The point about voltage is well taken, though. We just need a way
>> > to detect what kind of battery is installed to use it.
>>
>> That will be non-trivial. Unless we find access to the I2C bus on
>> which we can talk to
> > The point about voltage is well taken, though. We just need a way to
> > detect what kind of battery is installed to use it.
>
> That will be non-trivial. Unless we find access to the I2C bus on which
> we can talk to the battery controller, to maybe get access to more info
> than provided by p
On 26 Jan, this message from Michael Schmitz echoed through cyberspace:
> The point about voltage is well taken, though. We just need a way to
> detect what kind of battery is installed to use it.
That will be non-trivial. Unless we find access to the I2C bus on which
we can talk to the battery c
> > It would be interesting for pmud to be able to work on battery voltage
> > instead of the time left as indicated by the obviously mislead battery
> > controller...
>
> Do you mean that pmud currently works on the time left? I noticed that
> it is really meaningless, probably because it depends
On 2004-01-25 21:10:23 +0100, Mich Lanners wrote:
> It would be interesting for pmud to be able to work on battery voltage
> instead of the time left as indicated by the obviously mislead battery
> controller...
Do you mean that pmud currently works on the time left? I noticed that
it is really me
On 23 Jan, this message from Michael Schmitz echoed through cyberspace:
> 1) battery capacity tends to decrease over time. To see how much
> capacity is left, run without pmud (or similar service), remount
> everything ro and wait for it to power off.
Here is some anectdotical information about m
On Fri, Jan 23, 2004 at 12:35:18PM +0100, Guido Guenther wrote:
> Just for the record, I didn't look into this further:
> I had the clock reset to 1904 after hitting Magic-Sysrq+M (showMem)
> where the machine simply powered off and when hitting Magic-Syrrq+B
> (reboot).
Also for the record: the c
> > I've had the same happen on occasion, and won't of course blame pmud for
> > it :-) Seriously, what seems to happen is the battery is lying about how
> > much charge is left, and runs out during sleep.
>
> This may be the cause, as I got the message after less than 2 hours,
> though the battery
> Well, this is different.
>
> The kernel continuously talks to the PMU. It happens asynchronously
> at interrupt time. If for some reason, that communication is stopped
> in the middle of a message transmission, the PMU times out and shuts
> the machine down, losing the time (I suspect it resets i
On Fri, 2004-01-23 at 23:48, Michael Schmitz wrote:
> > Well, this is different.
> >
> > The kernel continuously talks to the PMU. It happens asynchronously
> > at interrupt time. If for some reason, that communication is stopped
> > in the middle of a message transmission, the PMU times out and sh
On Fri, 2004-01-23 at 22:35, Guido Guenther wrote:
> On Fri, Jan 23, 2004 at 11:32:46AM +0100, Michael Schmitz wrote:
> > I've had the same happen on occasion, and won't of course blame pmud for
> > it :-) Seriously, what seems to happen is the battery is lying about how
> > much charge is left, an
On Fri, Jan 23, 2004 at 11:32:46AM +0100, Michael Schmitz wrote:
> I've had the same happen on occasion, and won't of course blame pmud for
> it :-) Seriously, what seems to happen is the battery is lying about how
> much charge is left, and runs out during sleep.
Just for the record, I didn't look
On 2004-01-23 11:32:46 +0100, Michael Schmitz wrote:
> I've had the same happen on occasion, and won't of course blame pmud for
> it :-) Seriously, what seems to happen is the battery is lying about how
> much charge is left, and runs out during sleep.
This may be the cause, as I got the message a
> > The battery of my PowerBook G4 got too low and the machine was put into
> > sleep. I closed the lid, changed the battery, but when I reopened the
> > lid, I noticed that the PowerBook was in fact off. And when I switched
> > it on (around 21:00), the clock was set back to 1904-01-01. Here's a
>
On Thu, 2004-01-22 at 22:38, Vincent Lefevre wrote:
> The battery of my PowerBook G4 got too low and the machine was put into
> sleep. I closed the lid, changed the battery, but when I reopened the
> lid, I noticed that the PowerBook was in fact off. And when I switched
> it on (around 21:00), the
Hi !
> The battery of my PowerBook G4 got too low and the machine was put into
> sleep. I closed the lid, changed the battery, but when I reopened the
> lid, I noticed that the PowerBook was in fact off. And when I switched
> it on (around 21:00), the clock was set back to 1904-01-01. Here's a
> /
On 2004-01-22 19:30:35 -0500, Michael D. Crawford wrote:
> Most Macs have a small battery on the motherboard for this purpose.
> I don't know for sure, but possibly your Powerbook and my iBook
> don't have one.
My PowerBook seems to have one (as I've said, this is the first time
the problem occurs
That happens to me on my iBook, but under Mac OS X.
I think the Mac hardware must be depending on the battery to keep its hardware
clock running while it's turned off.
Most Macs have a small battery on the motherboard for this purpose. I don't
know for sure, but possibly your Powerbook and m
The battery of my PowerBook G4 got too low and the machine was put into
sleep. I closed the lid, changed the battery, but when I reopened the
lid, I noticed that the PowerBook was in fact off. And when I switched
it on (around 21:00), the clock was set back to 1904-01-01. Here's a
/var/log/syslog e
34 matches
Mail list logo
