Re: Killing the console screen saver ?

1999-11-23 Thread James S. Kaplan KG7FU

You can probably leave the powersave out. Unless you have a laptop or kernel
level support
for power management (which is very poor for non-battery power).

jk

-
James S. Kaplan KG7FU
Eugene Oregon USA
[EMAIL PROTECTED]
http://www.rio.com/~kg7fu
ICQ # 1227639
Have YOU tried Linux today?
-


- Original Message -
From: Steve Mc Donough <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 22, 1999 5:24 PM
Subject: Re: Killing the console screen saver ?


> Hi James,
> I run RH6.0 with Jnos and was wondering myself how
> to get rid of the screen blanking and found the string on
> the Red Hat site to disable it.
>
> setterm -powersave off -blank 0
>
> It worked on this end.  By the way my Jnos has been up now
> for 83 days without a reboot and that reboot was due to
> a power failure.  I run a 486dx2 with 32 megs with RH6.
> Hope this helps.  73  Steve
>
> At 07:55 PM 11/21/99 -0800, you wrote:
> >tried 'setterm -blank 0' ??
> >
> >jk
> >
> >-
> >James S. Kaplan KG7FU
> >Eugene Oregon USA
> >[EMAIL PROTECTED]
> >http://www.rio.com/~kg7fu
> >ICQ # 1227639
> >Have YOU tried Linux today?
> >-
> >
> >
> >- Original Message -
> >From: aa6qn <[EMAIL PROTECTED]>
> >To: Linux-Hams <[EMAIL PROTECTED]>; NOS-BBS
> ><[EMAIL PROTECTED]>
> >Sent: Sunday, November 21, 1999 2:11 PM
> >Subject: Killing the console screen saver ?
> >
> >
> >> Need to ask the Linux Guru's on how to kill the Linux console screen
> >> black out. Or, at least change the timing on it.  I have a feeling that
> >> it may be part of my lockup problems.  Was looking in the
/etc/sysconfig
> >> but did not see anything regarding the console settings.
> >>
> >> For Richard, I am running RH6.0  with the linux kernel 2.2.13 on a
> >> Pentium 133 with 64meg ram.  I tried several kernels and they all lock
> >> up after a bit. Hmmm, wonder if it is Jnos ? At one time I had it up
for
> >> days without a problem. I am also posting this to the nos-bbs folks, in
> >> case they have some ideas as well.  One thing of note is that while I
am
> >> working on the console , or when someone is using the Squid cache, it
> >> seems not to lockup very often.
> >>
> >> Thank you to all those who responded to my kissattach query.
> >>
> >> 73, John
> >
> >



Re: Killing the console screen saver ?

1999-11-22 Thread Steve Mc Donough

Hi James,
I run RH6.0 with Jnos and was wondering myself how
to get rid of the screen blanking and found the string on 
the Red Hat site to disable it.

setterm -powersave off -blank 0

It worked on this end.  By the way my Jnos has been up now
for 83 days without a reboot and that reboot was due to
a power failure.  I run a 486dx2 with 32 megs with RH6.
Hope this helps.  73  Steve

At 07:55 PM 11/21/99 -0800, you wrote:
>tried 'setterm -blank 0' ??
>
>jk
>
>-
>James S. Kaplan KG7FU
>Eugene Oregon USA
>[EMAIL PROTECTED]
>http://www.rio.com/~kg7fu
>ICQ # 1227639
>Have YOU tried Linux today?
>-
>
>
>- Original Message -
>From: aa6qn <[EMAIL PROTECTED]>
>To: Linux-Hams <[EMAIL PROTECTED]>; NOS-BBS
><[EMAIL PROTECTED]>
>Sent: Sunday, November 21, 1999 2:11 PM
>Subject: Killing the console screen saver ?
>
>
>> Need to ask the Linux Guru's on how to kill the Linux console screen
>> black out. Or, at least change the timing on it.  I have a feeling that
>> it may be part of my lockup problems.  Was looking in the /etc/sysconfig
>> but did not see anything regarding the console settings.
>>
>> For Richard, I am running RH6.0  with the linux kernel 2.2.13 on a
>> Pentium 133 with 64meg ram.  I tried several kernels and they all lock
>> up after a bit. Hmmm, wonder if it is Jnos ? At one time I had it up for
>> days without a problem. I am also posting this to the nos-bbs folks, in
>> case they have some ideas as well.  One thing of note is that while I am
>> working on the console , or when someone is using the Squid cache, it
>> seems not to lockup very often.
>>
>> Thank you to all those who responded to my kissattach query.
>>
>> 73, John
>
>



Re: Killing the console screen saver ?

1999-11-21 Thread Richard Adams

On Sun, 21 Nov 1999, aa6qn wrote:
>Need to ask the Linux Guru's on how to kill the Linux console screen
>black out. Or, at least change the timing on it.  I have a feeling that
>it may be part of my lockup problems.  Was looking in the /etc/sysconfig
>but did not see anything regarding the console settings.
>
>For Richard, I am running RH6.0  with the linux kernel 2.2.13 on a
>Pentium 133 with 64meg ram.  I tried several kernels and they all lock
>up after a bit. Hmmm, wonder if it is Jnos ? At one time I had it up for
>days without a problem. I am also posting this to the nos-bbs folks, in
>case they have some ideas as well.  One thing of note is that while I am
>working on the console , or when someone is using the Squid cache, it
>seems not to lockup very often.

Hello John.

This is interesting as i think i may have had the same problem with
the system just locking, i had this when i compiled my first 2.2.x
kernel, what i did not do was read the flipping manual, i just
defined what i thougt best and away i went, only to find that the
first time i started up X and then switched back to a console
everything just died, no messages in the logs and no screen dump.

The mistake i made was defining Framebuffers wrongly that was i
belive with kernel 2.2.10 or 11 i cant remember but i dont think
thats the issue here, i have run 2.2.13 without problems.

Unfortunaly i get connection refused thesedays when trying to telnet
to you, so i cant look to confirm my susspishtions.

You might want to try and define the framebuffers with make config 
use the following as an example, please note i have a matrox video
card, if you dont have a matrox dont define one.

CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
# CONFIG_FB_PM2 is not set
# CONFIG_FB_VESA is not set
# CONFIG_FB_VGA16 is not set
CONFIG_VIDEO_SELECT=y
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_MILLENIUM=y
# CONFIG_FB_MATROX_MYSTIQUE is not set
# CONFIG_FB_MATROX_G100 is not set
# CONFIG_FB_MATROX_MULTIHEAD is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FBCON_ADVANCED is not set
CONFIG_FBCON_CFB8=y
CONFIG_FBCON_CFB16=y
CONFIG_FBCON_CFB24=y
CONFIG_FBCON_CFB32=y
# CONFIG_FBCON_FONTWIDTH8_ONLY is not set
CONFIG_FBCON_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_FONT_SUN8x16=y
# CONFIG_FONT_SUN12x22 is not set
CONFIG_FONT_6x11=y
CONFIG_FONT_PEARL_8x8=y
CONFIG_FONT_ACORN_8x8=y
 
The above is not perfect and some options are not nessacary, however
it does work here ok.

You might want to take a look at;

/usr/src/linux/Documentation/fb/*

yourself.

>Thank you to all those who responded to my kissattach query.

Keep in touch.

>
>73, John

--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/



Re: Killing the console screen saver ?

1999-11-21 Thread James S. Kaplan KG7FU

tried 'setterm -blank 0' ??

jk

-
James S. Kaplan KG7FU
Eugene Oregon USA
[EMAIL PROTECTED]
http://www.rio.com/~kg7fu
ICQ # 1227639
Have YOU tried Linux today?
-


- Original Message -
From: aa6qn <[EMAIL PROTECTED]>
To: Linux-Hams <[EMAIL PROTECTED]>; NOS-BBS
<[EMAIL PROTECTED]>
Sent: Sunday, November 21, 1999 2:11 PM
Subject: Killing the console screen saver ?


> Need to ask the Linux Guru's on how to kill the Linux console screen
> black out. Or, at least change the timing on it.  I have a feeling that
> it may be part of my lockup problems.  Was looking in the /etc/sysconfig
> but did not see anything regarding the console settings.
>
> For Richard, I am running RH6.0  with the linux kernel 2.2.13 on a
> Pentium 133 with 64meg ram.  I tried several kernels and they all lock
> up after a bit. Hmmm, wonder if it is Jnos ? At one time I had it up for
> days without a problem. I am also posting this to the nos-bbs folks, in
> case they have some ideas as well.  One thing of note is that while I am
> working on the console , or when someone is using the Squid cache, it
> seems not to lockup very often.
>
> Thank you to all those who responded to my kissattach query.
>
> 73, John



Re: Killing the console screen saver ?

1999-11-21 Thread Bob Nielsen

On Sun, Nov 21, 1999 at 06:12:46PM -0500, aa6qn wrote:
> Need to ask the Linux Guru's on how to kill the Linux console screen
> black out. Or, at least change the timing on it.  I have a feeling that
> it may be part of my lockup problems.  Was looking in the /etc/sysconfig
> but did not see anything regarding the console settings.


'setterm -blank [n]'  0 <= n <= 60  n = time until blank (in minutes) 0
disables blanking.

 
> 
> For Richard, I am running RH6.0  with the linux kernel 2.2.13 on a
> Pentium 133 with 64meg ram.  I tried several kernels and they all lock
> up after a bit. Hmmm, wonder if it is Jnos ? At one time I had it up for
> days without a problem. I am also posting this to the nos-bbs folks, in
> case they have some ideas as well.  One thing of note is that while I am
> working on the console , or when someone is using the Squid cache, it
> seems not to lockup very often.

I usually run JNOS for weeks without any problems (and if I do reboot,
it isn't because JNOS misbehaved or the kernel locked up).  Debian
potato, kernel 2.0.38, 40 MB ram, P-100.

Bob, w6swe

-- 
Bob Nielsen Internet: [EMAIL PROTECTED]
Tucson, AZ  AMPRnet:  [EMAIL PROTECTED]
DM42nh  http://www.primenet.com/~nielsen



Killing the console screen saver ?

1999-11-21 Thread aa6qn

Need to ask the Linux Guru's on how to kill the Linux console screen
black out. Or, at least change the timing on it.  I have a feeling that
it may be part of my lockup problems.  Was looking in the /etc/sysconfig
but did not see anything regarding the console settings.

For Richard, I am running RH6.0  with the linux kernel 2.2.13 on a
Pentium 133 with 64meg ram.  I tried several kernels and they all lock
up after a bit. Hmmm, wonder if it is Jnos ? At one time I had it up for
days without a problem. I am also posting this to the nos-bbs folks, in
case they have some ideas as well.  One thing of note is that while I am
working on the console , or when someone is using the Squid cache, it
seems not to lockup very often.

Thank you to all those who responded to my kissattach query.

73, John