From: Markus Gutschke <markus-nyufa/AnP+9Wk0Htik3J/w@public.gmane.org>
To: Michael Hardy <mike-YPUHpfzIkGtIf6P1QZMOBw@public.gmane.org>
Cc: Malcolm Caldwell
<malcolm.caldwell-HU4z9rI8l8AQrrorzV6ljw@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: lid switch on dell latitude d800 freezes system
Date: Thu, 15 May 2003 22:02:20 -0700 [thread overview]
Message-ID: <3EC470DC.7080609@gutschke.com> (raw)
In-Reply-To: <3EC46882.50102-YPUHpfzIkGtIf6P1QZMOBw@public.gmane.org>
As mentioned before, I do not see any of these problems. Screen blanking
works just fine when I close the lid. I get the ACPI event and then call
xset to (un)blank the screen from a script.
I'd be happy to make my kernel (somewhat patched version of Linux
2.4.21-rc1-ac3 with ACPI patches) and X binaries (Debian unstable, XFree
4.2.1.1) available to anybody who wants to investigate this problem
further.
Markus
Michael Hardy wrote:
>
> Seems to me like there are two separate paths to follow, one of which
> may only
> be here because I haven't tested everything correctly -
>
> 1) work with nvidia and/or Dell - if loading the nvidia driver causes an
> ACPI
> interaction that locks the machine, it seems that it must be a vendor
> thing.
> I'd go with nvidia first just because they at least *try*, and might know
> something, then maybe followup with Dell
>
> 2) work with the open source nv authors to see if they can work out DPMS
> for
> the D800. This is where I might be ignorant, but I'm under the impression
> screen blanking doesn't work with the nv driver and getting it to work
> would
> get a very effective power-save state on lid close combined with ACPI S1.
> Obviously doesn't get you 3D, but I'd be quite happy if this worked
>
> Mainly, I'm just glad I'm not crazy and someone else sees what I do :-).
> I've
> posted this on my D800 site, and I'll be happy to test and chronicle
> anything
> anyone finds out.
>
> Thanks for putting in the effort to try and isolate this-
> -Mike
>
> Malcolm Caldwell wrote:
>
>> Ok,
>>
>> I have more or less confirmed that the problem is, as Michael suggested,
>> the nvidia driver. If I never start X the lid button does nothing
>> except log stuff into the log file. With X started once, even if it is
>> no longer running running the system freezes.
>>
>> So - what now? Report this to nvidia? Try to work this out in some
>> other way? Any hints where to look?
>>
>> On Fri, 2003-05-16 at 03:02, Malcolm Caldwell wrote:
>>
>>
>>> Hello,
>>>
>>> I am running 2.4.21-rc1 with acpi patches. I have also patched to run a
>>> custom dstc which I got from someone on the net. (The interface at
>>> acpi.sourceforge.net fails to find the dstc that it says are there -
>>> however the author's email address is there and he sent it to me
>>> directly)
>>>
>>> The only problem is that the lid switch freezes the machine. As far as
>>> I know the freeze only happens if something is reading from
>>> /proc/acpi/events (although I would have to do some more testing to
>>> verify this).
>>>
>>> Can anyone give any hints on how to go about fixing this?
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
>>> The only event dedicated to issues related to Linux enterprise solutions
>>> www.enterpriselinuxforum.com
>>>
>>> _______________________________________________
>>> Acpi-devel mailing list
>>> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>>> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>>>
>>>
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
next prev parent reply other threads:[~2003-05-16 5:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 17:32 lid switch on dell latitude d800 freezes system Malcolm Caldwell
[not found] ` <1053019947.4310.20.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-05-16 1:40 ` Malcolm Caldwell
[not found] ` <1053049258.4929.4.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-05-16 4:26 ` Michael Hardy
[not found] ` <3EC46882.50102-YPUHpfzIkGtIf6P1QZMOBw@public.gmane.org>
2003-05-16 5:02 ` Markus Gutschke [this message]
[not found] ` <3EC470DC.7080609-nyufa/AnP+9Wk0Htik3J/w@public.gmane.org>
2003-05-16 6:40 ` Michael Frank
[not found] ` <200305161440.59376.mflt1-DTdK3Ks6N5kHTnRCetW4+N0b+6lKrnBL@public.gmane.org>
2003-05-16 15:45 ` Michael Hardy
[not found] ` <3EC5079B.5030009-YPUHpfzIkGtIf6P1QZMOBw@public.gmane.org>
2003-05-16 15:51 ` Markus Gutschke
[not found] ` <3EC508FA.1070500-nyufa/AnP+9Wk0Htik3J/w@public.gmane.org>
2003-05-16 17:57 ` Malcolm Caldwell
[not found] ` <1053107846.5147.3.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-05-16 18:15 ` Michael Frank
2003-05-16 19:01 ` Malcolm Caldwell
2003-05-16 15:44 ` Michael Hardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EC470DC.7080609@gutschke.com \
--to=markus-nyufa/anp+9wk0htik3j/w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=malcolm.caldwell-HU4z9rI8l8AQrrorzV6ljw@public.gmane.org \
--cc=mike-YPUHpfzIkGtIf6P1QZMOBw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox