>Okay, the power consumption during sleep has improved.
>Without the latest changes, sleeping for 12 hours used up about 42% of
>the battery. With your latest kernel, it used up about 25%. (I
>haven't measured it on MacOS yet.) Is that about what you would
>expect?
What would be interes
> On Mon, 16 Jul 2001 09:40:06 +0200, Benjamin Herrenschmidt <[EMAIL
> PROTECTED]> said:
[ TiPB screen artifacts when sleeping with 2.4.6 kernel ]
b> It's a side effect of my tentative to save more power by shutting
b> down the DAC and LVDS transmittr. I'm trying to trace the MacOS
b> dr
>Sorry for the non-technical description, but has anyone else
>noticed this?
It's a side effect of my tentative to save more power by shutting
down the DAC and LVDS transmittr. I'm trying to trace the MacOS
driver to figure out what it actually does.
Did you notice a loss in battery life
> On Wed, 11 Jul 2001 11:52:46 -0400, Colin Walters <[EMAIL PROTECTED]>
> said:
[ TiPB sleep on 2.4.6 kernel ]
c> Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
>> Could one of you quickly test if the problem still happen with my
>> current rsync ? I merged some fixes from recent bk
Hello Benjamin!
Same for me, rsynced, recompiled and did a quick test. sleep works
within X and console!
Thanks for your work,
Christoph
Colin Walters schrieb:
>
> Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
>
> > Could one of you quickly test if the problem still happen with my
Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
> Could one of you quickly test if the problem still happen with my
> current rsync ? I merged some fixes from recent bk _2_4_devel that
> may or may not help.
Yep, rsync as of about 20 minutes ago, with Altivec support enabled,
sleeps just fine
>> Disabling altivec seemed to fix the problem sleeping. It went to
>> sleep and woke up 7 or 8 times with no problems aside from
>> temporarily scrambling the console a bit.
>
>Yep, disabling altivec worked for me too.
Could one of you quickly test if the problem still happen with
my current rsyn
>failing again (as it does even with older kernels). X11 sleep still
>works. It seems like the problem is in aty128_sleep_notifier because
>this debug code you suggested:
>
>> - edit drivers/video/aty128fb.c, comment out the call to
>> pmu_register_sleep_notifier() line 1907, and add
>> a "re
>
>giveup_altivec:
> mfpvr r24 /* check if we are on a G4 */
> srwir24,r24,16
> cmpwi r24,[EMAIL PROTECTED]
> beq 3f /* continue */
> mflrr24
> bl msr_vec_debug /* debug thingy in process.c *
> On Tue, 10 Jul 2001 23:30:48 -0700, [EMAIL PROTECTED] (Gregorio Gervasio
> Jr.) said:
[ TiPB sleep problems with 2.4.6 ]
g> I get the same trace. As Olaf Hering suggested, it's failing
g> when "giveup_altivec" is called. It looks like a processor version
g> check was recently
> On Tue, 10 Jul 2001 18:37:41 -0500, Adam Lazur <[EMAIL PROTECTED]> said:
[ TiPB sleep problem with 2.4.6 ]
a> cpu 0: vector: 300 at pc = c0007894, lr = c0007894, msr = b032, sp =
c76d9d90 [c76d9ce0]
a> dar = 358, dsisr = 4000
a> current = c76d8000, pid = 283, comm = pmud
a> 0:mon>
(c0
Adam Lazur <[EMAIL PROTECTED]> writes:
> Disabling altivec seemed to fix the problem sleeping. It went to
> sleep and woke up 7 or 8 times with no problems aside from
> temporarily scrambling the console a bit.
Yep, disabling altivec worked for me too.
Olaf Hering ([EMAIL PROTECTED]) said:
> can you try to disable altivec in your kernel?
>
> c0007820 T dump_altivec
> c0007870 T msr_vec_debug
> c00078e0 T enable_kernel_altivec
Disabling altivec seemed to fix the problem sleeping. It went to sleep
and woke up 7 or 8 times with no problems aside f
On Tue, Jul 10, Adam Lazur wrote:
> return notifier c0280d8c
> cpu 0: vector: 300 at pc = c0007894, lr = c0007894, msr = b032, sp = c76d9d90
> [c76d9ce0]
> dar = 358, dsisr = 4000
> current = c76d8000, pid = 283, comm = pmud
> 0:mon>
can you try to disable altivec in your kernel?
c0007820 T
Benjamin Herrenschmidt ([EMAIL PROTECTED]) said:
> Did you try without the USB mouse ? And also without compiling the
> USB OHCI driver in the kernel at all ?
Hmm, I have usb-ohci in my kernel... I have the same symptoms on my TiPB
as the others reported, so I figured I'd help debug.
> One thing
>
>I have my Microsoft USB optical mouse plugged in, and I do have the
>Airport card installed now, but I don't have the Airport driver module
>running.
Did you try without the USB mouse ? And also without compiling the
USB OHCI driver in the kernel at all ?
If I understand you properly, it hangs
On Tue, Jul 10, 2001 at 12:11:59AM -0400, Colin Walters wrote:
> I have my Microsoft USB optical mouse plugged in, and I do have the
well no wonder, you attach something made by Microsoft and you expect
stability?
--
Ethan Benson
http://www.alaska.net/~erbenson/
pgpa7KSPuZbgq.pgp
Description
Michel Dänzer <[EMAIL PROTECTED]> writes:
> AFAIK this is related to thermal management. Apparently you should
> leave it off for now. It doesn't harm my Pismo though.
I don't have thermal management enabled. FWIW, here's the .config:
#
# Automatically generated make config: don't edit
#
# CONF
Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
> Could you resync again ? Sleep is supposed to work with my current
> kernels on the TiBook, if it's still locking up your box, some
> investigations will be needed.
rsync as of about 33 minutes ago doesn't work for me.
> Note that if you are u
> >AFAIK the airport unload hack is no longer required with 2.4 kernels
> >(what's with 2.2.19?). If Ben says 2.4 sleep support on Core99 is stable,
> >I'll just have to check the kernel version number and either shutdown or
> >sleep. If someone backports the Core99 sleep code to 2.2, the better.
>
>
>AFAIK the airport unload hack is no longer required with 2.4 kernels
>(what's with 2.2.19?). If Ben says 2.4 sleep support on Core99 is stable,
>I'll just have to check the kernel version number and either shutdown or
>sleep. If someone backports the Core99 sleep code to 2.2, the better.
2.2.19
> > Also, does sleep work with older kernels ? (you have the proper hacks
> > to pmud scripts for sleep to work properly on core99) ?
>
> Apropos... are we including the latest/best/brightest of these scripts
> in Debian?
If someone tells me which version of the pmud pwrctl scripts is the
best/bri
Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
> Also, does sleep work with older kernels ? (you have the proper hacks
> to pmud scripts for sleep to work properly on core99) ?
Apropos... are we including the latest/best/brightest of these scripts
in Debian?
--
David N. Welton
Free Software
Benjamin Herrenschmidt wrote:
> Note that if you are using DRI in X, you should also make sure
> you enable APM emulation (a new option in my kernels), and that
> you create /dev/apm_bios
>
> mknod /dev/apm_bios c 10 134
This is Debian, so just cd /dev; MAKEDEV apm :)
--
Earthling Michel Dä
Colin Walters wrote:
>
> Is anyone else out there using a recentish benh 2.4.6 kernel with a
> TiBook? 2.4.4 from a while ago worked fine for me for pretty much
> everything, but 2.4.6 kills the machine when I close the lid.
AFAIK this is related to thermal management. Apparentl
>Is anyone else out there using a recentish benh 2.4.6 kernel with a
>TiBook? 2.4.4 from a while ago worked fine for me for pretty much
>everything, but 2.4.6 kills the machine when I close the lid.
>
>I would just stick with 2.4.4, except that it locks the machine when I
>try t
Is anyone else out there using a recentish benh 2.4.6 kernel with a
TiBook? 2.4.4 from a while ago worked fine for me for pretty much
everything, but 2.4.6 kills the machine when I close the lid.
I would just stick with 2.4.4, except that it locks the machine when I
try to build the Debian boot
27 matches
Mail list logo
