search for: lid

...0x20 SCBPTR = 0x0 SCSISIGI[0x44]:(BSYI|IOI) ERROR[0x0] SCSIBUSL[0x0] LASTPHASE[0x40]:(IOI) SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI) SBLKCTL[0xa]:(SELWIDE|SELBUSB) SCSIRATE[0x18]:(SINGLE_EDGE) SEQCTL[0x10]:(FASTMODE) SEQ_FLAGS[0x20]:(DPHASE) SSTAT0[0x0] SSTAT1[0x2]:(PHASECHG) SSTAT2[0x50]:(EXP_ACTIVE|SHVALID) SSTAT3[0x0] SIMODE0[0x8]:(ENSWRAP) SIMODE1[0xac]:(ENSCSIPERR|ENBUSFREE|ENSCSIRST|ENSELTIMO) SXFRCTL0[0x80]:(DFON) DFCNTRL[0x28]:(HDMAEN|SCSIEN) DFSTATUS[0x80]:(PRELOAD_AVAIL) STACK: 0x8a 0x0 0x170 0x186 SCB count = 20 Kernel NEXTQSCB = 7 Card NEXTQSCB = 14 QINFIFO entries: 14 9 3 Waiting Queue ent...

Both nouveau and i915, the only 2 kernel space lid notification listeners, invoke acpi_lid_open() API to obtain _LID returning value instead of using the notified value. So this patch moves this logic from listeners to lid driver, always notify kernel space listeners using _LID returning value. This is a no-op cleanup, but facilitates administrat...

Hi, If my previous reply is not persuasive enough. Let me do that in a different way. > From: linux-acpi-owner at vger.kernel.org [mailto:linux-acpi-owner at vger.kernel.org] On Behalf Of Zheng, > Lv > Subject: RE: [PATCH v2 5/5] ACPI: button: Obselete acpi_lid_open() invocations > > Hi, > > > From: Benjamin Tissoires [mailto:benjamin.tissoires at gmail.com] > > Subject: Re: [PATCH v2 5/5] ACPI: button: Obselete acpi_lid_open() invocations > > > > On Tue, May 9, 2017 at 9:02 AM, Lv Zheng <lv.zheng at intel.com> wro...

....data.frame in an attempt to isolate the third element of the list s, but this was not helpful. Any help would be appreciated. > dim(s) [1] 342 3 > names(s) [1] "scan" "time" "a" > s scan time a.a a.a2 a.a3 202 Plastic lids Plastic lids NaN NaN NaN 195 Plastic lids Cookware lids 44 31 58 205 Plastic lids Seasoning packets 9 4 20 191 Plastic lids Baking sheets 15 7 27 209 Plastic lids Utensils 9 4 20 194 Plastic lids Cell phones...

...Hi, > > If my previous reply is not persuasive enough. > Let me do that in a different way. > >> From: linux-acpi-owner at vger.kernel.org [mailto:linux-acpi-owner at vger.kernel.org] On Behalf Of Zheng, >> Lv >> Subject: RE: [PATCH v2 5/5] ACPI: button: Obselete acpi_lid_open() invocations >> >> Hi, >> >> > From: Benjamin Tissoires [mailto:benjamin.tissoires at gmail.com] >> > Subject: Re: [PATCH v2 5/5] ACPI: button: Obselete acpi_lid_open() invocations >> > >> > On Tue, May 9, 2017 at 9:02 AM, Lv Zheng <lv....

On Tue, May 9, 2017 at 9:02 AM, Lv Zheng <lv.zheng at intel.com> wrote: > Since notification side has been changed to always notify kernel listeners > using _LID returning value. Now listeners needn't invoke acpi_lid_open(), > it should use a spec suggested control method lid device usage model: > register lid notification and use the notified value instead, which is the > only way to ensure the value is correct for "button.lid_init_state=...

What's the motivation behind commit 60821e0 (drm/nouveau: report LVDS as disconnected if lid closed)? The only noticeable effect I can see from it is that if I turn on my laptop and then close the lid, X fails to start as it can't find any screens. In fact, if I close the lid before nouveau initialises, I don't even get a framebuffer console. I know I can just use the ignorelid...

Hi, Benjamin > From: linux-acpi-owner at vger.kernel.org [mailto:linux-acpi-owner at vger.kernel.org] On Behalf Of Benjamin > Tissoires > Subject: Re: [PATCH v2 5/5] ACPI: button: Obselete acpi_lid_open() invocations > > Hi Lv, > > I am trying to reduce the number of parallel discussion we have on the > same subject, but there is something here I can't let you have. OK. So let's stop talking in PATCH 4-5. They are actually cleanups from my point of view. In fact, I...

since I got the big bolus of updates from the CR repo a few days ago my netbook (AcerAspire One D255E) will no longer go to standby when the lid is closed. This was a Gnome desktopp installation with theh MATE desktop fromm EPEL. I've verified that the correct setting still exists in power manager but it persists in continuing to run when the lid closes. it WILL go to standby if explicitly told to do so from the shutdown dialog. Has...

Hi, I'm using CentOS on a laptop that part of the time is connected to a docking station with two monitor connected to it. When the laptop lid is docked, its lid is closed, as the system is placed in a position where it's not convenient to keep it open, let alone look at the screen. Now in the past, with CentOS 5 (on a different laptop, but same physical config) and 6, the screen has automatically been switched off in this config...

Folks I have a laptop which i am using temporarily as a test server. It is permanently plugged in. It is running Centos 6, command line only. In the past, I could close the lid, thereby turning off the display, but not turning off the machine. It remained running indefinitely. A recent update (this past week) changed that behavior. Now, when I close the lid, the laptop turns itself off within an hour. A google search talks about tools like "upower" and apc...

Um texto embutido e sem conjunto de caracteres especificado associado... Nome: n?o dispon?vel Url: https://stat.ethz.ch/pipermail/r-help/attachments/20060617/d28b0fb4/attachment.pl

Since notification side has been changed to always notify kernel listeners using _LID returning value. Now listeners needn't invoke acpi_lid_open(), it should use a spec suggested control method lid device usage model: register lid notification and use the notified value instead, which is the only way to ensure the value is correct for "button.lid_init_state=ignore" mo...

...n, May 15, 2017 at 5:55 AM, Zheng, Lv <lv.zheng at intel.com> wrote: > Hi, Benjamin > >> From: linux-acpi-owner at vger.kernel.org [mailto:linux-acpi-owner at vger.kernel.org] On Behalf Of Benjamin >> Tissoires >> Subject: Re: [PATCH v2 5/5] ACPI: button: Obselete acpi_lid_open() invocations >> >> Hi Lv, >> >> I am trying to reduce the number of parallel discussion we have on the >> same subject, but there is something here I can't let you have. > > OK. So let's stop talking in PATCH 4-5. > They are actually cleanups fro...

...gt; Date: Friday, December 11, 2015 10:29:20 -0500 > > From: Fred Smith <fredex at fcshome.stoneham.ma.us> > > > > since I got the big bolus of updates from the CR repo a few days > > ago my netbook (AcerAspire One D255E) will no longer go to standby > > when the lid is closed. > > > > This was a Gnome desktopp installation with theh MATE desktop fromm > > EPEL. > > > > I've verified that the correct setting still exists in power > > manager but it persists in continuing to run when the lid closes. > > > >...

Damjan, Glad to hear that worked for you. I don't know if the gnome people can make this very much easier. Different version of different linux distros might invoke hibernate differently. How would they know which one to map to the lid button? Also, some people might want to invoke sleep rather than hibernate. If there were system commands which were persistent over all distros and versions, then maybe they could offer these two mention options (with explanations of each). Yes, that would be an improvement. Best, ken On 0...

How can I prevent the laptop from sleeping when the lid is closed. I tried messing with the settings in gnome-power-preferences but that doesn't seem to prevent it when no one is logged in. Any suggestions? Thanks, Dave

On 05/12/17 08:53, Toralf Lund wrote: > Hi, > > I'm using CentOS on a laptop that part of the time is connected to a > docking station with two monitor connected to it. When the laptop lid is > docked, its lid is closed, as the system is placed in a position where > it's not convenient to keep it open, let alone look at the screen. > > Now in the past, with CentOS 5 (on a different laptop, but same physical > config) and 6, the screen has automatically been switch...

Hello, I am using CentOS 5.1 on a toshiba tecra 8000 notebook. That works great so far. The only thing I could not realize is to shutdown the notebook if closing the lid. Therefor I need the current status (open or close) of the lid, but I don't know how. Is there any way to get this status, maybe under /proc/ or by some command? [root at beutelsend ~]# uname -a Linux beutelsend 2.6.18-53.1.14.el5 #1 SMP Wed Mar 5 11:36:49 EST 2008 i686 i686 i386 GNU/Linux [ro...

Has anyone seen the following error before? "error on enabled probe ID 2 (ID 473: sdt:unix:av_dispatch_autovect:interrupt-complete): invalid address (0x198) in action #3 at DIF offset 20" I''m trying to capture interrupt times as inlined in the below script. The script gives me some output after the errors, and I''m trying to understand if the errors are affecting my output(and the cause, of course) Thanks for...