New Slack 9.1.

I can't get the power management thing to work in Slack. My Samsung LCD
monitor supports it.

I uncommented out the modprobe apm parm in the rc.modules file. I added
Option "DPMS" to the X86FConfig file. Did a restart. Nothing. The lsmod
command says that apm is loaded and I have the settings in KDE set
correctly. The BIOS has ACPI set to "S1 State". Have I not covered all the
bases here?

Maybe bare.i does not have this feature? Or maybe I don't know what the heck
I'm doin'!!!

Thanks,
Al

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Sun, 12 Oct 2003 07:20:02 GMT, Adams-Blake Co. <atakeoutcanton@adams-blaketakeout.com> wrote:
> I can't get the power management thing to work in Slack. My Samsung LCD
> monitor supports it.

Power management, as you use it there, implies ACPI or APM type power
management - all you need is DPMS. You don't need to worry about APM or
ACPI.

> I uncommented out the modprobe apm parm in the rc.modules file. I added
> Option "DPMS" to the X86FConfig file. Did a restart. Nothing. The lsmod
> command says that apm is loaded and I have the settings in KDE set
> correctly. The BIOS has ACPI set to "S1 State". Have I not covered all the
> bases here?

ACPI and APM are two seperate things, to begin with. Pick one and use
that. APM is tried and true, but very old and not supported on a lot of
new hardware. ACPI is the new big thing, but isn't supported yet on a
lot of hardware. I only have partial ACPI support on my laptop here,
but zero APM support.

Either way, APM or ACPI have *nothing* to do with DPMS - turning off
your monitor.

To see if it's working, open up an xterm (or konsole) and run
"xset dpms 3 4 5" and don't touch your mouse or keyboard. After five
seconds, your screen should be off, if everything is enabled properly in
your XF86Config file.

If it does turn off, then you just need to fix a setting somewhere in
KDE's settings area. If it does not turn off, we need to investigate to
find out why. If it does *not* work, tell us what kind of video card
you have, exactly, and show us the "Monitor" section of your XFree86
config file.

> Maybe bare.i does not have this feature? Or maybe I don't know what the heck
> I'm doin'!!!

Naw, bare.i definitely has support for DPMS, if that's even a kernel
option - if it is, I haven't seen it.

DPMS is all you need to worry about for screen blanking...

--
Rob | If not safe,
Email and Jabber: | one can never be free.
athlonrob at axpr dot net |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/iQivhm6KEoOOAe0RAjQRAKD4eRX+ynEAe1i3zbFgpWeHRZuiyQ CeM/27
5yJ3RwOt6Tke0wWegZ3eExY=
=jWnQ
-----END PGP SIGNATURE-----

On Sun, 12 Oct 2003 07:20:02 +0000, Adams-Blake Co. wrote:

> New Slack 9.1.
>
> I can't get the power management thing to work in Slack. My Samsung LCD
> monitor supports it.
>
> I uncommented out the modprobe apm parm in the rc.modules file. I added
> Option "DPMS" to the X86FConfig file. Did a restart. Nothing. The lsmod
> command says that apm is loaded and I have the settings in KDE set
> correctly. The BIOS has ACPI set to "S1 State".

Well isn't there a setting for APM as well, or anly ACPI?
(It should work anyways - but still.)

> Have I not covered all the
> bases here?

Nope, you need to have `apmd' running. Try:
ps -ef |grep apmd
In case it's not started have a look in `/etc/rc.d/rc.M'.
If it _is_ running you might have to configure it (i didn't BTW.)
man apmd

Otherwise you might need `acpid'.
(That has more features but might not work correct, yet.)
However do /not/ run them bouth at the same time (they conflict).

> Maybe bare.i does not have this feature?

Not sure (but i think APM is there).
If you need ACPI try `acpibare.i'.

> Or maybe I don't know what the heck I'm doin'!!!

Possible.
It don't matter though, as long as you learn from trying.

> Thanks,

HTH.

--
-Menno.

The bareacpi.i kernel works on my toshiba no probslems

Adams-Blake Co. wrote:
> New Slack 9.1.
>
> I can't get the power management thing to work in Slack. My Samsung LCD
> monitor supports it.
>
> I uncommented out the modprobe apm parm in the rc.modules file. I added
> Option "DPMS" to the X86FConfig file. Did a restart. Nothing. The lsmod
> command says that apm is loaded and I have the settings in KDE set
> correctly. The BIOS has ACPI set to "S1 State". Have I not covered all the
> bases here?
>
> Maybe bare.i does not have this feature? Or maybe I don't know what the heck
> I'm doin'!!!
>
> Thanks,
> Al
>

AthlonRob wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> NotDashEscaped: You need GnuPG to verify this message
>
> On Sun, 12 Oct 2003 07:20:02 GMT, Adams-Blake Co.
> <atakeoutcanton@adams-blaketakeout.com> wrote:
>> I can't get the power management thing to work in Slack. My Samsung LCD
>> monitor supports it.
>
> Power management, as you use it there, implies ACPI or APM type power
> management - all you need is DPMS. You don't need to worry about APM or
> ACPI.
>
>> I uncommented out the modprobe apm parm in the rc.modules file. I added
>> Option "DPMS" to the X86FConfig file. Did a restart. Nothing. The lsmod
>> command says that apm is loaded and I have the settings in KDE set
>> correctly. The BIOS has ACPI set to "S1 State". Have I not covered all
>> the bases here?
>
> ACPI and APM are two seperate things, to begin with. Pick one and use
> that. APM is tried and true, but very old and not supported on a lot of
> new hardware. ACPI is the new big thing, but isn't supported yet on a
> lot of hardware. I only have partial ACPI support on my laptop here,
> but zero APM support.
>
> Either way, APM or ACPI have *nothing* to do with DPMS - turning off
> your monitor.
>
> To see if it's working, open up an xterm (or konsole) and run
> "xset dpms 3 4 5" and don't touch your mouse or keyboard. After five
> seconds, your screen should be off, if everything is enabled properly in
> your XF86Config file.
>
> If it does turn off, then you just need to fix a setting somewhere in
> KDE's settings area. If it does not turn off, we need to investigate to
> find out why. If it does *not* work, tell us what kind of video card
> you have, exactly, and show us the "Monitor" section of your XFree86
> config file.
>
>> Maybe bare.al@darkstar:~$ ps -ef | grep apmd
root 38 1 0 Oct11 ? 00:00:00 [kapmd]
root 1501 1 0 Oct11 ? 00:00:00 /usr/sbin/apmd
i does not have this feature? Or maybe I don't know what the
>> heck I'm doin'!!!
>
> Naw, bare.i definitely has support for DPMS, if that's even a kernel
> option - if it is, I haven't seen it.
>
> DPMS is all you need to worry about for screen blanking...
>


It does NOT turn off.

apmd is running:

al@darkstar:~$ ps -ef | grep apmd
root 38 1 0 Oct11 ? 00:00:00 [kapmd]
root 1501 1 0 Oct11 ? 00:00:00 /usr/sbin/apmd

I don't have a video card as I have on-board video from the Intel
motherboard. They call it "Extreme Graphics" or something like that. During
install I did NOT do the XF86Config thing as the installer said it would
use something called VERSA framebuffer to make everything work.

Now this is interesting. I see that I have 3 XF86Config files:
XF86Config
XF86Config-versa
XF86Config-fbdev

I must be using the first one because that is the one I made the change to
for the mouse scroll wheel and it worked.

When looking at the XF86Config I found this:

# Set the basic blanking screen saver timeout.

# Option "blank time" "10" # 10 minutes

# Set the DPMS timeouts. These are set here because they are global
# rather than screen-specific. These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

# Option "standby time" "20"
# Option "suspend time" "30"
# Option "off time" "60"

Do these need to be uncommented?



Here is the monitor section:


Thanks for your help,

Al



# ************************************************** ********************
# Monitor section
# ************************************************** ********************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 31.5 - 50.0

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 40-90
Option "DPMS"

EndSection



# ************************************************** ********************
# Graphics device section
# ************************************************** ********************

# Any number of graphics device sections may be present

Section "Device"
Identifier "VESA Framebuffer"
Driver "vesa"
#VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection

# ************************************************** ********************
# Screen sections
# ************************************************** ********************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "VESA Framebuffer"
Monitor "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 24
# DefaultDepth 32

# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubsection

EndSection

On Sun, 12 Oct 2003 14:57:58 +0000, Adams-Blake Co. wrote:

> I don't have a video card as I have on-board video from the Intel
> motherboard. They call it "Extreme Graphics" or something like that. During
> install I did NOT do the XF86Config thing as the installer said it would
> use something called VERSA framebuffer to make everything work.

"VESA" its called.

> # Option "standby time" "20"
> # Option "suspend time" "30"
> # Option "off time" "60"

> Do these need to be uncommented?

Yes.

I would once again suggest that you use www.google.com/linux to find out
more about your graphics chipset.

I used "Extreme Graphics" as a search phrase, returns a wealth of info.
One in particular.

http://www.google.nl/linux?hl=nl&ie=...gle+zoeken&lr=

Note i use google.nl, if you use google.com you will get redirected to
your local mirror site.

Try it it works wonders.

Have you had your google today..

--
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

Richard Adams wrote:

>
> I would once again suggest that you use www.google.com/linux to find out
> more about your graphics chipset.
>

This is good advice. I honestly didn't know that you could do something like
this. Thanks for the info. I bookmarked it. (And BTW the new Konqueror that
comes with Slakc 9.1 is terrific.... huge improvement over the 2.2 ver. )

I don't use the web too often for research as so much of it is out of date.
I much prefer Usenet because Google gives you an "advanced" search ability
to narrow your request for postings within a date range.

Now on to figuring out how to write to a CD and then I'll tackle the
Win4Lin kernel patch and I'll be all done. Good thing tomorrow is a (US)
holiday and my office is closed.

I've learned more Linux in the past 48 hours than in my prev. year with
Mandrake. Thanks, guys. Give me another month or two and I'll be able to
contribute something to this KB... maybe!


Al

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Sun, 12 Oct 2003 14:57:58 GMT, Adams-Blake Co. <atakeoutcanton@adams-blaketakeout.com> wrote:
>>> Maybe bare.al@darkstar:~$ ps -ef | grep apmd
> root 38 1 0 Oct11 ? 00:00:00 [kapmd]
> root 1501 1 0 Oct11 ? 00:00:00 /usr/sbin/apmd
> i does not have this feature? Or maybe I don't know what the
>>> heck I'm doin'!!!

Let me try again -

APM and ACPI are power managemen schemes that have *NOTHING* to do with
screen blanking. They have to do with idling the CPU, CPU fan speeds,
CPU temperatures, suspending the system to RAM or disk, shutting down
the system, and stuff like that. They have *NOTHING* to do with
blanking your screen (turning off the monitor after being idle for a
while).

DPMS is what blanks your screen. DPMS doesn't really do anything except
turn off your monitor when you forget to.

> It does NOT turn off.
>
> apmd is running:
>
> al@darkstar:~$ ps -ef | grep apmd
> root 38 1 0 Oct11 ? 00:00:00 [kapmd]
> root 1501 1 0 Oct11 ? 00:00:00 /usr/sbin/apmd

Again - APM has *NOTHING* to do with blanking your screen.

> I don't have a video card as I have on-board video from the Intel
> motherboard. They call it "Extreme Graphics" or something like that. During
> install I did NOT do the XF86Config thing as the installer said it would
> use something called VERSA framebuffer to make everything work.

Ok - the VESA driver may not be able to make DPMS work with your
graphics chip. I'm surprised you're running that system with an onboard
graphics chip, really. That'll suck down your memory bandwidth - and if
you're running a P4, it's already memory starved, quite likely.

Google on how to set up X for *your* graphics chip, and not the VESA
generic driver.

> Now this is interesting. I see that I have 3 XF86Config files:
> XF86Config
> XF86Config-versa
> XF86Config-fbdev
>
> I must be using the first one because that is the one I made the change to
> for the mouse scroll wheel and it worked.

Yep, the XF86Config-vesa and XF86Config-fbdev are just example files.
If you're running on a framebuffer, you could try switching to the fbdev
one and see how things work and act differently.

> When looking at the XF86Config I found this:
>
> # Set the basic blanking screen saver timeout.
>
> # Option "blank time" "10" # 10 minutes
>
> # Set the DPMS timeouts. These are set here because they are global
> # rather than screen-specific. These settings alone don't enable DPMS.
> # It is enabled per-screen (or per-monitor), and even then only when
> # the driver supports it.
>
> # Option "standby time" "20"
> # Option "suspend time" "30"
> # Option "off time" "60"
>
> Do these need to be uncommented?

You can manually set it with xset or adjust/uncomment those. The xset
line we had you run above manually set them to three seconds, four
seconds, and five seconds. If that didn't work, then editing the config
file won't change things.

> Here is the monitor section:

For future reference, to save bandwidth, run things through
| grep -v "^#" | grep -v "^$" before posting any config files to clean
it up a bit for us. We don't need the comments in there...

> Option "DPMS"

That's the line I was interested in. It's trying to enable DPMS. Now I
wonder if something would appear in the log file about DPMS? Hmmmm....

Ahhh... yes.....

/var/log/XFree86.0.log contains, for me:

(II) Loading extension DPMS

and

(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled

Do you have anything similar? The (**) lines are the ones to look for
right now, as you should have the (II) lines from your config file.

--
Rob | If not safe,
Email and Jabber: | one can never be free.
athlonrob at axpr dot net |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/iZsQhm6KEoOOAe0RAqQfAKCmYZNhUByPYwD4/kOmEPYKqlJz2QCg7mvI
IuGTHlS2m3VnN7cFHJe96PU=
=/jAu
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Sun, 12 Oct 2003 16:31:38 GMT, Adams-Blake Co. <atakeoutcanton@adams-blaketakeout.com> wrote:
> Now on to figuring out how to write to a CD and then I'll tackle the
> Win4Lin kernel patch and I'll be all done. Good thing tomorrow is a (US)
> holiday and my office is closed.

A holiday tomorrow? What holiday is that?

> I've learned more Linux in the past 48 hours than in my prev. year with
> Mandrake. Thanks, guys. Give me another month or two and I'll be able to
> contribute something to this KB... maybe!

Yeah... I went a while with Mandrake and didn't even know how to edit
files from the command line. Hell, I could barely move files at the
command line. I couldn't untar files.

A few hours with Slackware had me going like gangbusters.

--
Rob | If not safe,
Email and Jabber: | one can never be free.
athlonrob at axpr dot net |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/iZuXhm6KEoOOAe0RAjtiAKCxBCrECanP5Y3Dtnvy1TPfqStxFg CfTI9w
2STjBUU9SIamwvpi14l/oks=
=78kc
-----END PGP SIGNATURE-----

AthlonRob wrote:

> A holiday tomorrow? What holiday is that?

My, (British), Diary says it's 'Veterans Day'.
--
Two Ravens
"...hit the squirrel!"