Date: Mon, 7 Apr 2008 21:36:41 +0200 From: "Spil Oss" <spil.oss@googlemail.com> To: freebsd-acpi@freebsd.org Subject: Re: Problem with lid on Dell D400 Message-ID: <5fbf03c20804071236i6db67a2ascd95f94eb1ba7abc@mail.gmail.com> In-Reply-To: <5fbf03c20804070149j15a3e3b1s54ced2f0bfc81efd@mail.gmail.com> References: <5fbf03c20804040812t5fdf8065ubf46d6420358595@mail.gmail.com> <5fbf03c20804040844q22875ac8nbbc3fae121d3eac8@mail.gmail.com> <731432799.20080406100414@masm.elcom.ru> <5fbf03c20804070149j15a3e3b1s54ced2f0bfc81efd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 06/04/2008, Victor M. Blood <root@masm.elcom.ru> wrote:
> > On 04.04.2008, Spil Oss wrote:
> > > On a Dell D400 notebook (Pentium-M 1.4GHz, Intel 855GM, ICH4M) running
> > > FreeBSD 7.0 #0
> >
> > > Closing the lid switches off the display, opening the lid does not
> > > switch the display back on. Very annoying. The machine is fully
> > > functional otherwise (accessed via ssh).
> >
> > > Noticed this first on a vanilla FreeBSD-7.0 #0 install, the optimized
> > > kernel seems to behave the same.
> >
> > > In sysctl I noticed after closing and opening the lid
> > > hw.acpi.lid_switch_state: NONE
> > > but I have not checked the status of this sysctl before I closed the lid.
> >
> > > dmesg output is not of boot -v, but of regular boot
> >
> > > I wouldn't care if the lid doesn't have acpi features (e.g. suspend on
> > > lid close), but I'd like the screen to switch off for additional
> > > battery-life.
> >
> > > Hope someone can help me!
> >
> > on Dell 1300B I use module acpi_video
> > add to loader.conf acpi_video_load="yes"
> >
> > and configure devd.conf to run script on lid change status: exist in
> > it's examples.
> >
> > notify 10 {
> > match "system" "ACPI";
> > match "subsystem" "Lid";
> > action "/sbin/lidctl $notify";
> > };
> >
> >
> > # cat /sbin/lidctl
> > #!/bin/sh
> > hive=hw.acpi.video.lcd0.active
> > sysctl=/sbin/sysctl
> >
> > case "$1" in
> > "1" | "0x01")
> > ${sysctl} ${hive}=1 >/dev/null
> > ;;
> > "0" | "0x00")
> > ${sysctl} ${hive}=0 >/dev/null
> > ;;
> > esac
> >
> > --
> > With all regards, Victor M. Blood. mailto: freebsd@masm.elcom.ru
> > FTN: 2:5024/1.95@Fidonet.org, ICQ#3567656
> >
>
> Thanks Victor,
>
> Installed acpi_video and will try this later, currently I can't get to
> the console to check. Will report back after checking!
>
> New sysctls after kldload acpi_video:
> hw.acpi.video.tv0.active: 0
> hw.acpi.video.crt0.active: 0
> hw.acpi.video.lcd0.active: 0
> hw.acpi.video.ext0.active: 0
>
> Kind regards,
>
> Spil
>
Thanks Victor,
When I load acpi_video, I get following messages:
acpi_video0: <ACPI video extension> on vgapci0
acpi_video1: <ACPI video extension> on vgapci1
evaluation of \\_SB_.PCI0.VID2._DOD makes no sense
At least I could get the display back on by issueing
sysctl hw.acpi.video.lcd0.active=1
But as I set the execute bit on /sbin/lidctl it was flying!
Thanks a bundle!
Kind regards,
Spil.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5fbf03c20804071236i6db67a2ascd95f94eb1ba7abc>