In message: [EMAIL PROTECTED]
Nate Lawson [EMAIL PROTECTED] writes:
: Please send me your patch for reseting USB on resume. I will test it and
: commit it.
Acutally, I have some generic resume stuff in the pipeline, so please
run it by me too. Too many drivers do too many bogus
On Sat, 5 Jul 2003, Anish Mistry wrote:
The patch is not a complete implementation but it should help identify any
hw problems in burst mode support. I won't put it into the tree without
making sure it can fall back correctly.
Also, since I forgot the URL the second time:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Outstanding issues:
- - Battery still drains uncontrollably in S3
No idea on this.
I seem to be getting this answer from everyone. Is there some specific
debugging info that I could provide the list to help with fixing this?
- - USB
Hi,
my floppy disc drive does not work. I was ignoring this fact until today,
because I need to write something to a floppy. It's probably clashing with
something ACPI is claiming:
[during boot]
fdc0: cmd 3 failed at out byte 1 of 3
fdc0: cmd 3 failed at out byte 1 of 3
fdc0: cannot reserve I/O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The patch is not a complete implementation but it should help identify any
hw problems in burst mode support. I won't put it into the tree without
making sure it can fall back correctly.
Also, since I forgot the URL the second time:
I cvsup'ed and rebuild my sources today, but I still have a problem with
suspend/resume using ACPI. Since I use the system on a laptop, I really
need to get this running properly.
The symptoms are:
- system boots and runs ok, ACPI is configured to go into suspend mode
when the lid is closed
= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 20 (acpi_thermal)
trap number = 12
panic: page fault
syncing disks, buffers remaining... ACPI
On Thu, 3 Jul 2003, John Baldwin wrote:
On 03-Jul-2003 Nate Lawson wrote:
On Thu, 3 Jul 2003, M. Warner Losh wrote:
I personally think that all tunable should be read-only (or rw if
possible) sysctls...
I'm still not sure why we have both mechanisms. Perhaps a useful approach
would
On Thu, 3 Jul 2003, Koop Mast wrote:
My machine an ASUS L3800S laptop.
Before the burst_ec patch I am using the hw.acpi.ec.event_driven sysctl.
This fixed the panic that occurred when switching to battery power.
When using the patch I get same behavior as in the pre-event_driven=1
days :)
Nate Lawson wrote:
On Thu, 3 Jul 2003, John Baldwin wrote:
On 03-Jul-2003 Nate Lawson wrote:
On Thu, 3 Jul 2003, M. Warner Losh wrote:
I personally think that all tunable should be read-only (or rw if
possible) sysctls...
I'm still not sure why we have both mechanisms. Perhaps a useful
On Thursday, July 3, 2003, at 10:28 AM, Nate Lawson wrote:
I personally think that all tunable should be read-only (or rw if
possible) sysctls...
I'm still not sure why we have both mechanisms. Perhaps a useful
approach
would be to sweep the tree for tunables and change them to sysctls with
On Thu, 3 Jul 2003, Michael Smith wrote:
[...]
No.
The two are different things, although arguably there should be more
integration.
The tunable mechanism exists to allow parameters to be set before the
kernel starts.
Things that are set with tunables tend to be things that used
On 03-Jul-2003 Florian Smeets wrote:
Nate Lawson wrote:
On Thu, 3 Jul 2003, John Baldwin wrote:
On 03-Jul-2003 Nate Lawson wrote:
On Thu, 3 Jul 2003, M. Warner Losh wrote:
I personally think that all tunable should be read-only (or rw if
possible) sysctls...
I'm still not sure why we have
On Thursday, July 3, 2003, at 10:59 AM, Julian Elischer wrote:
It makes sense to export the values set by tunables into the sysctl
MIB, but by their
very nature they're not suitable for conversion to sysctls.
= Mike
So is what you are saying...
tuneables should be converted at boot to
On Tue, Jul 01, 2003 at 10:25:36AM -0700, Nate Lawson wrote:
Would you please turn on hw.acpi.verbose=1 in loader.conf? It should
explain the cause of those errors. Also, I would like the output of
dmesg | egrep acpi_ec0\|EC\ Wait.
I tested your patch on my IBM Thinkpad 570E and didn't see
On Wed, 2 Jul 2003, Andrea Campi wrote:
On Tue, Jul 01, 2003 at 10:25:36AM -0700, Nate Lawson wrote:
Would you please turn on hw.acpi.verbose=1 in loader.conf? It should
explain the cause of those errors. Also, I would like the output of
dmesg | egrep acpi_ec0\|EC\ Wait.
I tested your
Hi Nate,
From: Nate Lawson [EMAIL PROTECTED]
Date: Tue, 1 Jul 2003 01:07:53 -0700
::Please download and try the new version. It correctly implements burst
::mode to the best of the 2.0 spec. Like the previous message, please
::report the appropriate dmesgs (acpi_ec0* and EC Waited*) and any
Please try out the patch at:
http://root.org/~nate/freebsd/ec-burst.diff
This adds support for the embedded controller to use burst mode by
default. It removes our non-working EventWaitIntr() implementation. It
has a debug print that will show:
EC Waited max 2 cycles
Please report the
On Wed, 25 Jun 2003, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Vincent Poy [EMAIL PROTECTED] writes:
: On Tue, 24 Jun 2003, M. Warner Losh wrote:
:
: In message: [EMAIL PROTECTED]
: Vincent Poy [EMAIL PROTECTED] writes:
: : Speaking about ACPI
Great. Do you also have working battery status now?
Does anyone have a 5000e? The fix for the 5000 doesn't fix my
suspend/resume problems on my 5000e. However, the battery status
works fine using standard /dev/apm from the acpi module.
Jason
On 24-Jun-2003 Mark Murray wrote:
Hi
You (?) gave me these patches at least 6 months ago, and they've
been working for my Libretto ever since then. Is it OK if I commit
them?
No, not quite yet. Those are rather hackish and I didn't develop
them, one of the other ACPI guys did.
--
John
of the other ACPI guys did.
OK. Can we work on this, then? The patches are developing a bit of
a following of folks who would _love_ to see them committed. :-)
What is needed?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http
On Mon, 23 Jun 2003, Scott Lambert wrote:
On Mon, Jun 23, 2003 at 10:38:26AM -1000, Vincent Poy wrote:
Speaking about ACPI, has anyone figured out how to close the lid
without suspending? I remember before, when the lid was closed, it would
suspend even with sysctl set to not suspend
, I find out that this is a
read-only oid. I found that I can get the value restored by disconnecting
the AC power (putting the machine in 'economy' mode) and then restoring the
AC power (putting the maching back into 'performance' mode).
I turned on verbose ACPI logging and here is what I see
, isa_driver, isa_devclass, 0, 0);
+DRIVER_MODULE(isa, acpi, acpi_isa_driver, isa_devclass, 0, 0);
#endif
MODULE_VERSION(isa, 1);
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
(putting the machine in 'economy' mode) and then restoring the
AC power (putting the maching back into 'performance' mode).
I turned on verbose ACPI logging and here is what I see in the message log:
acpi_tz0: _AC9: temperature 61.9 = setpoint -273.-2
acpi_tz0: _AC8: temperature 61.9 = setpoint
On Mon, 23 Jun 2003, David Gilbert wrote:
Nate == Nate Lawson [EMAIL PROTECTED] writes:
Nate Thanks for your patch submission. I looked into it and found a
Nate few problems. Attached is a patch based on yours that should be
Nate equivalent but fixes a few problems:
Is this working for
In message: [EMAIL PROTECTED]
Vincent Poy [EMAIL PROTECTED] writes:
: Speaking about ACPI, has anyone figured out how to close the lid
: without suspending? I remember before, when the lid was closed, it would
add the following to your /boot/loader.conf
On Tue, 24 Jun 2003, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Vincent Poy [EMAIL PROTECTED] writes:
: Speaking about ACPI, has anyone figured out how to close the lid
: without suspending? I remember before, when the lid was closed, it would
add the following
doesn't work for several models.. Including Inspiron 7500.
WHo knows enough about this to be able to look at debug info
I have?
My system gives lots of:
acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0%
ACPI-0432: *** Error: Handler for [EmbeddedControl] returned
/~stijn/freebsd/dell.php
and let me know if it works.
It seems to work for me. The ACPI warnings about zero length buffers go
away at least.
Great. Do you also have working battery status now?
I've got a Dell Inspirion 8500, A03 BIOS.
I've added this model to the confirmed working model
Hi!
I recently bought a Samsung Q10 and on both 5.1-RELEASE and -current I get these acpi
errors:
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved
Hi,
I'm seeing similiar things on my setup - both the ACPI Global Lock
messages and the wi0 issues. In fact, the wi driver seems to be
incredibly unstable - Every half hour or so I need to remove and
re-insert the card to regain network connectivity (and ofcourse killall
dhclient ; ifconfig wi0
--- Julian Elischer [EMAIL PROTECTED] wrote:
doesn't work for several models.. Including Inspiron 7500.
WHo knows enough about this to be able to look at debug info
I have?
John Baldwin has posted a patch which worked for me on my Thinkpad 600X with the same
ACPI-0340
error.
http
Hi,
doesn't work for several models.. Including Inspiron 7500.
WHo knows enough about this to be able to look at debug info
I have?
John Baldwin has posted a patch which worked for me on my Thinkpad
600X with the same ACPI-0340 error.
I tried this patch, and while it does get rid
Hi!
I applied the patch from
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=214877+0+archive/2003/freebsd-current/20030615.freebsd-current
and the AE_BAD_PARAEMTER error disappers.
Hendrik
--
Hendrik Scholz - [EMAIL PROTECTED] - http://raisdorf.net/
Forcast for tonight: Dark.
Eirik Oeverby wrote:
[...]
And with ACPI disabled, the machine refuses totally to
boot, it hangs at 'Mounting root from ...'. If I undock the machine, I
can boot with and without ACPI, with the latter option being the only
usable (stable) mode.
Just out of curiosity, have you tried setting
Ok i've been a morron... updated the wrong web site with the dmesg and
ACPI code...
The code is located at:
http://www.guldan.cistron.nl/dmesg_output.txt
http://www.guldan.cistron.nl/n610c_2.dsl
Robert
On Thu, Jun 19, 2003 at 09:42:00PM +0200, Robert Blacquière wrote:
Hi,
I've a ComPaq
On Mon, 23 Jun 2003 10:53:32 -0400
Jesse Guardiani [EMAIL PROTECTED] wrote:
And with ACPI disabled, the machine refuses totally to
boot, it hangs at 'Mounting root from ...'. If I undock the machine,
I can boot with and without ACPI, with the latter option being the
only usable (stable
that fixes this?
Try this URL:
http://sandcat.nl/~stijn/freebsd/dell.php
and let me know if it works.
It seems to work for me. The ACPI warnings about zero length buffers go
away at least.
Great. Do you also have working battery status now?
How do I figure that out
/dell.php
It seems to work for me. The ACPI warnings about zero length buffers go
away at least.
Great. Do you also have working battery status now?
How do I figure that out? Via the ACPI sysctls, or some other method?
ACPI sysctls was the method that didn't work without the patch on my
, greatest patch that fixes this?
Try this URL:
http://sandcat.nl/~stijn/freebsd/dell.php
and let me know if it works.
It seems to work for me. The ACPI warnings about zero length buffers
go away at least.
Great. Do you also have working battery status now
Eirik Oeverby wrote:
On Mon, 23 Jun 2003 10:53:32 -0400
Jesse Guardiani [EMAIL PROTECTED] wrote:
And with ACPI disabled, the machine refuses totally to
boot, it hangs at 'Mounting root from ...'. If I undock the machine,
I can boot with and without ACPI, with the latter option being
Thanks for your patch submission. I looked into it and found a few
problems. Attached is a patch based on yours that should be equivalent
but fixes a few problems:
* Don't call msleep if event has already occurred
* Don't read CSR twice if not necessary (also fixed in EcEventWait)
* Unused loop
Speaking about ACPI, has anyone figured out how to close the lid
without suspending? I remember before, when the lid was closed, it would
suspend even with sysctl set to not suspend and the screen stays on and
when you resume, you can type but the screen freezes and doesn't update
Hi again,
No workie. No difference in behaviour whatsoever.
Sorry :(
/Eirik
On Mon, 23 Jun 2003 13:43:14 -0400
Jesse Guardiani [EMAIL PROTECTED] wrote:
Eirik Oeverby wrote:
On Mon, 23 Jun 2003 10:53:32 -0400
Jesse Guardiani [EMAIL PROTECTED] wrote:
And with ACPI disabled
:
On Mon, 23 Jun 2003 10:53:32 -0400
Jesse Guardiani [EMAIL PROTECTED] wrote:
And with ACPI disabled, the machine refuses totally to
boot, it hangs at 'Mounting root from ...'. If I undock the
machine, I can boot with and without ACPI, with the latter
option being the only
Nate == Nate Lawson [EMAIL PROTECTED] writes:
Nate Thanks for your patch submission. I looked into it and found a
Nate few problems. Attached is a patch based on yours that should be
Nate equivalent but fixes a few problems:
Is this working for your laptop's S3 suspend? I'm trying to figure
On Mon, Jun 23, 2003 at 10:38:26AM -1000, Vincent Poy wrote:
Speaking about ACPI, has anyone figured out how to close the lid
without suspending? I remember before, when the lid was closed, it would
suspend even with sysctl set to not suspend and the screen stays on and
when you resume
The .asl file that I created is only for the Inspiron 5000. However, the S3
suspend itself on my machine works... however on resume I have a problem
where the keyboard driver cannot reset the keyboard: atkbd: cannot set the
command byte. I have heard that this affects some people only when
for me on my Thinkpad 600X
| with the same ACPI-0340 error.
|
| http://docs.freebsd.org/cgi/getmsg.cgi?fetch=214877+0+archive/2003/freebs
|d-current/20030615.freebsd-current
|
ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER
After patching my DSDT table, I was receiving
I have fixed the stock DSDT for my Dell Inspiron 5000 (Model: PPM). It
compiles fine using iasl from the acpicatools port, and enabling ACPI no
longer causes the LCD to blank on startup.
Additionally, I have written a patch for version 1.29 of the
sys/dev/acpica/acpi_ec.c. The patch affects
for me. The ACPI warnings about zero length buffers go
away at least.
I've got a Dell Inspirion 8500, A03 BIOS.
Ken
--
Kenneth Merry
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
On Fri, Jun 20, 2003 at 05:29:30PM -0400, Mike Sturdee wrote:
Where can I find the latest, greatest patch that fixes this?
Try this URL:
http://sandcat.nl/~stijn/freebsd/dell.php
and let me know if it works.
--Stijn
just to confirm that it works on a Dell Latitude C800
danny
In message: [EMAIL PROTECTED]
Kevin Oberman [EMAIL PROTECTED] writes:
: M S4 works on my fiva, but it seems to have a S4BIOS S4 state because
: M the bios does the save to disk...
:
: I would assume that this requires some form of DOS-like parition?
:
: Actually, it requires a
Stijn Hoop wrote:
On Thu, Jun 19, 2003 at 09:33:41AM +0200, Eirik Oeverby wrote:
- When booted with ACPI enabled (docked), the machine will at some point
simply power itself off. I have seen people complaining about similiar
machines powering themselves *on* after a power-off, but in my case
Hi,
I have a i386 machine with Gigabyte 7ZXR mainboard here (Duron, VIA
KT133 chipset, AMI BIOS).
acpiconf -s1 and -s5 are apparently working ok, -s2 is refused (OK),
-s3 is refused (might be I didn't set the jumper correctly :o) and -s4
puts the machine to some sort of sleep (power LED blinks,
Where can I find the latest, greatest patch that fixes this?
ACPI-0293: *** Warning: Buffer created with zero length in AML
-0166: *** Error: UtAllocate: Attempt to allocate zero bytes
ACPI-0293: *** Warning: Buffer created with zero length in AML
-0166: *** Error: UtAllocate: Attempt
On Fri, Jun 20, 2003 at 05:29:30PM -0400, Mike Sturdee wrote:
Where can I find the latest, greatest patch that fixes this?
Try this URL:
http://sandcat.nl/~stijn/freebsd/dell.php
and let me know if it works.
--Stijn
--
Man had always assumed that he was more intelligent than dolphins
I just found that one and was trying it as this mail came in.. It looks to
work w/o any side-effects
Thanks!
-Mike
On Sat, 21 Jun 2003, Stijn Hoop wrote:
On Fri, Jun 20, 2003 at 05:29:30PM -0400, Mike Sturdee wrote:
Where can I find the latest, greatest patch that fixes this?
Try this
On Sat, Jun 21, 2003 at 12:13:10AM +0200, Stijn Hoop wrote:
On Fri, Jun 20, 2003 at 05:29:30PM -0400, Mike Sturdee wrote:
Where can I find the latest, greatest patch that fixes this?
Try this URL:
http://sandcat.nl/~stijn/freebsd/dell.php
and let me know if it works.
I was also
On Fri, 20 Jun 2003, Mike Sturdee wrote:
I just found that one and was trying it as this mail came in.. It looks to
work w/o any side-effects
Unfortunatly it doesn't work for Inspiron 7500 and 5000 models..
Thanks!
-Mike
Try this URL:
http://sandcat.nl/~stijn/freebsd/dell.php
to* enable ACPI, otherwise it will
not boot past 'Mounting root from ufs:/dev/ad0s1a' (and the following
WARNING about / not being unmounted cleanly, if the next point happened
to be true)
- When booted with ACPI enabled (docked), the machine will at some point
simply power itself off. I have seen
On Wed, Jun 18, 2003 at 09:14:53PM -0700, Julian Elischer wrote:
My Dell is exhibiting this error message all over the place..
At USENIX I was told someone had a fix..
http://sandcat.nl/~stijn/freebsd/dell.php
As of yet still untested instructions how to patch your ASL, let me know
if they
On Thu, Jun 19, 2003 at 09:33:41AM +0200, Eirik Oeverby wrote:
- When booted with ACPI enabled (docked), the machine will at some point
simply power itself off. I have seen people complaining about similiar
machines powering themselves *on* after a power-off, but in my case it's
Stijn Hoop wrote:
On Thu, Jun 19, 2003 at 09:33:41AM +0200, Eirik Oeverby wrote:
- When booted with ACPI enabled (docked), the machine will at some point
simply power itself off. I have seen people complaining about similiar
machines powering themselves *on* after a power-off, but in my case
In message: [EMAIL PROTECTED]
David Gilbert [EMAIL PROTECTED] writes:
: Mark == Mark Santcroos [EMAIL PROTECTED] writes:
:
: Mark Ok, it would really help if you try and document all cases until
: Mark you at least exactly know the behavior. From there we can go on.
:
: What am I
I have made a doc on how to make the ACPI work on Dell
http://www.x1234.info -Doc's-i8500
On Thursday 19 June 2003 9:37 am, Stijn Hoop wrote:
On Wed, Jun 18, 2003 at 09:14:53PM -0700, Julian Elischer wrote:
My Dell is exhibiting this error message all over the place..
At USENIX I
On Thu, 19 Jun 2003, Stijn Hoop wrote:
On Wed, Jun 18, 2003 at 09:14:53PM -0700, Julian Elischer wrote:
My Dell is exhibiting this error message all over the place..
At USENIX I was told someone had a fix..
http://sandcat.nl/~stijn/freebsd/dell.php
Unfortunatly this patch does not
On Thursday 19 June 2003 9:24 pm, Sebastian Yepes [ESN] wrote:
I have made a doc on how to make the ACPI work on Dell
http://www.x1234.info -Doc's-i8500
Sorry it's http://www.x123.info -Doc's-i8500
On Thursday 19 June 2003 9:37 am, Stijn Hoop wrote:
On Wed, Jun 18, 2003 at 09:14
Hi,
I've a ComPaq n610c with FreeBSD 5.1-Current running. With the latest
bios/RomPaq i was able to install Current/5.1-Release. Previous RomPaq
was completely broken for ACPI. But now is more or less works. I have
still some problems with acpi and without acpi. With acpi i got some
warnings
M == M Warner Losh [EMAIL PROTECTED] writes:
M In message: [EMAIL PROTECTED] David
M Gilbert [EMAIL PROTECTED] writes: : Mark == Mark
M Santcroos [EMAIL PROTECTED] writes: : : Mark Ok, it would really
M help if you try and document all cases until : Mark you at least
M exactly know the
From: David Gilbert [EMAIL PROTECTED]
Date: Thu, 19 Jun 2003 16:05:51 -0400
Sender: [EMAIL PROTECTED]
M == M Warner Losh [EMAIL PROTECTED] writes:
M In message: [EMAIL PROTECTED] David
M Gilbert [EMAIL PROTECTED] writes: : Mark == Mark
M Santcroos [EMAIL PROTECTED] writes: : : Mark
With a recent -current (6/18/03) I now see the infamous ACPI-0340 error
(Could not release ACPI Global Lock, AE_BAD_PARAMETER) spewing out.
This did not happen
with a kernel from 6/5/03. I tried to apply the patch that's been
referenced here, but apparently the Inspiron 5000 DSDT is completely
Hi list!
I have recently installed FreeBSD 5.1 on my Dell C800 laptop, and I get
quite a lot (well: 48 :) of these errors on boot:
ACPI-0293: *** Warning: Buffer created with zero length in AML
-0166: *** Error: UtAllocate: Attempt to allocate zero bytes
Are those harmfull
On Tue, Jun 17, 2003 at 04:21:41PM +0100, Antony T Curtis wrote:
On a Compaq Armada V300 notebook, if I load the acpi module, boot fails after
the kernel prints about half a dozen acpi_bus_number: can't get _ADR, fails
to detect any of the hardware and panics because of failure to mount
On Wed, Jun 18, 2003 at 09:11:23AM +0200, Maikel Verheijen wrote:
I have recently installed FreeBSD 5.1 on my Dell C800 laptop, and I get
quite a lot (well: 48 :) of these errors on boot:
ACPI-0293: *** Warning: Buffer created with zero length in AML
-0166: *** Error: UtAllocate
On Tue, Jun 17, 2003 at 10:57:32PM -0400, David Gilbert wrote:
I have a Dell D800 laptop (as I've mentioned a few times here) and
I've gone so far as to upgrade the BIOS to A03 and fetch new ACPI DSDT
code from the linux site.
Please compare that one with the one posted on the list. I recall
On Tue, Jun 17, 2003 at 06:40:59AM -0600, M. Warner Losh wrote:
: I think devd(8) should be used for this, but I havn't tried.
devd does not (currently) get events for suspend/resume. Maybe it
should.
Either devd should or we do need an acpid.
Mark
--
Mark Santcroos
Mark == Mark Santcroos [EMAIL PROTECTED] writes:
Mark On Tue, Jun 17, 2003 at 10:57:32PM -0400, David Gilbert wrote:
I have a Dell D800 laptop (as I've mentioned a few times here) and
I've gone so far as to upgrade the BIOS to A03 and fetch new ACPI
DSDT code from the linux site.
Mark Please
On Wed, Jun 18, 2003 at 12:11:52PM -0400, David Gilbert wrote:
You shouldn't happen to have a reference to the one posted to the
list, would you? Sometimes the FreeBSD list search facility isn't
that useful. I'll make an effort to find it.
Date: Tue, 27 May 2003 22:28:32 +0200
Subject: Re:
Mark == Mark Santcroos [EMAIL PROTECTED] writes:
Mark Ok, it would really help if you try and document all cases until
Mark you at least exactly know the behavior. From there we can go on.
What am I looking for? S1 appears to work. S5 appears to work (that
is: shutdown -p now works). S4
Hi all..
Any one know how to turn off the screen on a notebook
i mean totally off, Not the dpms
The problem is that when i close the lid it stays on and produces to much
heat..
5-Current on dell inspiron 8500 (with AML patch)
--
/*
FingerPrint:
5BF1 58B1 DE75 CBE3 6044
7098 1246 1EF6
Satellite 1605, I can
find no way to do this through ACPI, DPMS, or any other means. On my
Pavilion N5290 running Gentoo, there's a kernel module that handles it by
twinking hardware registers.
The Inspiron 8500 is a Compal machine if I remember correctly, and there's a
very slight possibility
to be a message here that syscons and other bits need to
learn more about dpms, and that acpi needs to provide the necessary events
(and time) to the device tree to allow proper power management (and may
not currently do that). This came up a number of times at the dev summit
last week.
Robert N M Watson
Armada V300 notebook, if I load the acpi module, boot fails
after the kernel prints about half a dozen acpi_bus_number: can't get
_ADR, fails to detect any of the hardware and panics because of failure
to mount root.
With the acpi module disabled, the machine is able to boot up
My Dell is exhibiting this error message all over the place..
At USENIX I was told someone had a fix..
Julian
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL
In message: [EMAIL PROTECTED]
Simon L. Nielsen [EMAIL PROTECTED] writes:
: On 2003.06.16 07:07:36 -0400, David Gilbert wrote:
: First, I must say that it's cool that ACPI code can be examined and
: rewritten. In my laptop's case, this was key to make things fairly
: happy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On a Compaq Armada V300 notebook, if I load the acpi module, boot fails after
the kernel prints about half a dozen acpi_bus_number: can't get _ADR, fails
to detect any of the hardware and panics because of failure to mount root.
With the acpi
In the last episode (Jun 17), Scott Lambert said:
Is there some list of actions to preform and data to collect that
would assist with getting the ACPI stuff lined out?
I've read the acpiconf man page but don't know that it gives me any
way to test for any specific functionality. I've been
On Tue, Jun 17, 2003 at 01:16:49PM -0500, Dan Nelson wrote:
My resume from suspend doesn't work and I don't know how to tell where
that is going wrong. I have no serial interface so I can't use a serial
console when the LCD doesn't come on. I can live without suspend/resume
Is there some list of actions to preform and data to collect that would
assist with getting the ACPI stuff lined out?
I've read the acpiconf man page but don't know that it gives me any way
to test for any specific functionality. I've been gradually piecing
together the meaning of S1, S2, S3
Howdy list,
Is there an ACPI mailling list I can join
to help debug/test ACPI?
I'm a decent C programmer, and I'd really
like to get ACPI support working on my
IBM Thinkpad A30p.
Unfortunately, no-one has responded to my
questions about ACPI on this laptop.
Is anyone actively working on ACPI
To: [EMAIL PROTECTED]
From: Jesse Guardiani [EMAIL PROTECTED]
Date: Tue, 17 Jun 2003 16:42:22 -0400
Subject: ACPI mailling list?
Reply-To: [EMAIL PROTECTED]
[I will Cc: -current despite that request.]
Is there an ACPI mailling list I can join
to help debug/test ACPI?
See http
In message: [EMAIL PROTECTED]
Dan Nelson [EMAIL PROTECTED] writes:
: In the last episode (Jun 17), Scott Lambert said:
: Is there some list of actions to preform and data to collect that
: would assist with getting the ACPI stuff lined out?
:
: I've read the acpiconf man page
On Tue, Jun 17, 2003 at 04:29:59PM -0600, M. Warner Losh wrote:
:
: ACPI records temperature in tenths of a Kelvin, if you can believe it :)
I don't believe that. 369.2K is 96.2C, which is over 200F. That seems
to hot to me. My laptop says 2982, which is either about 30C or
15.2C. Given
the ACPI stuff lined out?
:
: I've read the acpiconf man page but don't know that it gives me any
: way to test for any specific functionality. I've been gradually
: piecing together the meaning of S1, S2, S3, S4, and S5 and figuring
: out that the *_(button|switch)_state sysctl oids
Date: Tue, 17 Jun 2003 18:40:26 -0400
From: Barney Wolff [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
On Tue, Jun 17, 2003 at 04:29:59PM -0600, M. Warner Losh wrote:
:
: ACPI records temperature in tenths of a Kelvin, if you can believe it :)
I don't believe that. 369.2K is 96.2C
On Tue, Jun 17, 2003 at 06:40:26PM -0400, Barney Wolff wrote:
On Tue, Jun 17, 2003 at 04:29:59PM -0600, M. Warner Losh wrote:
:
: ACPI records temperature in tenths of a Kelvin, if you can believe it :)
I don't believe that. 369.2K is 96.2C, which is over 200F. That seems
to hot
On Tue, Jun 17, 2003 at 03:54:34PM -0700, Kevin Oberman wrote:
I am also seeing the same thing on my T30 when I run ACPI. It's the
temperature, not any of the others. It was reading 3186 and that seems
about right for centi-degrees C. (31.86C) Kelvin simply does not
compute.
According
701 - 800 of 1744 matches
Mail list logo
