phlogin problems

I have a machine with two Pentium III processors. There are two images, one
is for SMP and the other is for the non-smp configuration. The vesa
graphics drivers are being used.

If I boot with the SMP image, I run into a wierd problem. If I leave the
machine at the phlogin screen long enough for it to enter the “screen-saver”
state, the computer stops recognizing the keyboard and mouse actions. So it
stays in the screen-saver state for another 5-10 mins before totally
freezing.

Using both procnto-smp and procnto-smp -h give show the same response.

If I login and leave the computer on, it does not freeze, and everything
works fine (screensaver or not). If we prevent the phlogin screensaver
mode, there is no problem with login etc.

If I use the non-SMP image this problem does not occur.

all suggestions as to why this might happen are much appreciated. Also is
there a way to disable the screen-saver mode at the login screen.

Thanks
Dennis

Dennis <dmoses@z-kat.com> wrote:

If I boot with the SMP image, I run into a wierd problem. If I leave the
machine at the phlogin screen long enough for it to enter the “screen-saver”
state, the computer stops recognizing the keyboard and mouse actions. So it

Even Ctrl-Shift-Alt-BackSpace doesn’t work, right?

stays in the screen-saver state for another 5-10 mins before totally
freezing.

all suggestions as to why this might happen are much appreciated. Also is

Is it possible for you to telnet into this machine before its keyboard
stops working, and try to collect some info using pidin and phin after?

there a way to disable the screen-saver mode at the login screen.

phlogin recognizes a -T option that takes the number of seconds before
the screen saver mode kicks in; I think zero disables it altogether.
One minor difficulty is that since phlogin must be started by Photon,
you have to give phlogin’s arguments to Photon’s -l option; another
difficulty is that the command that starts Photon is buried somewhere in
the startup scripts.

But you can fool Photon into running something else instead of phlogin,
as long as it’s also called “phlogin” and is found on the default $PATH
before the real phlogin. The following shell script worked for me when
I put it in /bin/phlogin:

#! /bin/ksh
exec /usr/photon/bin/phlogin “$@” -T0

\

Wojtek Lerch QNX Software Systems Ltd.

Wojtek Lerch <wojtek_l@yahoo.ca> wrote in article <a7a8v3$3id$1@nntp.qnx.com>…

Dennis <> dmoses@z-kat.com> > wrote:

If I boot with the SMP image, I run into a wierd problem. If I leave the
machine at the phlogin screen long enough for it to enter the “screen-saver”
state, the computer stops recognizing the keyboard and mouse actions. So it

Even Ctrl-Shift-Alt-BackSpace doesn’t work, right?

stays in the screen-saver state for another 5-10 mins before totally
freezing.

all suggestions as to why this might happen are much appreciated. Also is

Is it possible for you to telnet into this machine before its keyboard
stops working, and try to collect some info using pidin and phin after?

there a way to disable the screen-saver mode at the login screen.

phlogin recognizes a -T option that takes the number of seconds before
the screen saver mode kicks in; I think zero disables it altogether.
One minor difficulty is that since phlogin must be started by Photon,
you have to give phlogin’s arguments to Photon’s -l option; another
difficulty is that the command that starts Photon is buried somewhere in
the startup scripts.

I believe ‘tinit -P’ starts phlogin and I guess it does some extra work. So, your suggestion is
quite good, IMO.


Eduard.
ed1k at yahoo dot com

But you can fool Photon into running something else instead of phlogin,
as long as it’s also called “phlogin” and is found on the default $PATH
before the real phlogin. The following shell script worked for me when
I put it in /bin/phlogin:

#! /bin/ksh
exec /usr/photon/bin/phlogin “$@” -T0

\

Wojtek Lerch QNX Software Systems Ltd.

ed1k <ed1k@spamerstrap.com> wrote:

I believe ‘tinit -P’ starts phlogin and I guess it does some extra work. So, your suggestion is

tinit runs the ph script.
The ph script starts Photon and does some extra work.
Photon starts phlogin.

quite good, IMO.

Thank you. :slight_smile:


Wojtek Lerch QNX Software Systems Ltd.

Thanks for your help.

Here is what happened.

Even Ctrl-Shift-Alt-BackSpace doesn’t work, right?

Bingo! Nothing on the keyboard (or mouse) would be recoganized. not
Numlock or anything.
I am able to telnet into the machine. but that is only for a couple of mins
before it freezes.

phlogin recognizes a -T option that takes the number of seconds before
… difficulty is that the command that starts Photon is buried
somewhere in
the startup scripts.

I wasnt aware of the -T0 option (my fault… that should have been obvious
thing to try). basically I found the startup in /usr/bin/ph and set it to
kick into the screensaver after around a month !! its been over 24hrs and
the machine is doing great. (But the -T0 sounds like the cleaner way to do
it)

The script idea is pretty neat…simple and neat !!

Thanks again
Dennis

Dennis <dmoses@z-kat.com> wrote:

Thanks for your help.

Here is what happened.

Even Ctrl-Shift-Alt-BackSpace doesn’t work, right?

Bingo! Nothing on the keyboard (or mouse) would be recoganized. not
Numlock or anything.

I am able to telnet into the machine. but that is only for a couple of mins
before it freezes.

A couple of minutes should be enough to run “pidin” and “phin ch”; could
you try that and post the output her if it’s not too much trouble? Even
though you have a workaround, it would be good to know what the problem
was…

phlogin recognizes a -T option that takes the number of seconds before
… difficulty is that the command that starts Photon is buried
somewhere in
the startup scripts.

I wasnt aware of the -T0 option (my fault… that should have been obvious
thing to try). basically I found the startup in /usr/bin/ph and set it to
kick into the screensaver after around a month !! its been over 24hrs and
the machine is doing great. (But the -T0 sounds like the cleaner way to do
it)

The script idea is pretty neat…simple and neat !!

Well, I tend to think of it as more of a hack really, but I agree that
it’s neither complicated nor messy. :wink:


Wojtek Lerch QNX Software Systems Ltd.

Sorry about the late response.
the pidin looks pretty much the same as always.

Below are the Pidin and the phin outputs

Thanks
Dennis

=================================
Pidin

1 1 procnto 0f READY

1 2 procnto 0f RUNNING

1 3 procnto 63r RECEIVE 1

1 4 procnto 15r RECEIVE 1

1 5 procnto 63r RECEIVE 1

1 6 procnto 15r RECEIVE 1

1 7 procnto 10r RUNNING

1 8 procnto 10r RECEIVE 1

1 9 procnto 15r RECEIVE 1

1 10 procnto 6r NANOSLEEP

1 11 procnto 10r RECEIVE 1

1 12 procnto 10r RECEIVE 1

2 1 sbin/tinit 10o REPLY 266262

3 1 proc/boot/slogger 15o RECEIVE 1

12292 1 sbin/mqueue 10o RECEIVE 1

5 1 proc/boot/pci-bios 12o RECEIVE 1

6 1 roc/boot/devb-eide 10o SIGWAITINFO

6 2 roc/boot/devb-eide 21r RECEIVE 1

6 3 roc/boot/devb-eide 21r RECEIVE 4

6 4 roc/boot/devb-eide 10o RECEIVE 10

6 5 roc/boot/devb-eide 10r CONDVAR b037866c

6 7 roc/boot/devb-eide 10o RECEIVE 7

6 8 roc/boot/devb-eide 10o RECEIVE 7

6 10 roc/boot/devb-eide 15o RECEIVE 7

7 1 /x86/sbin/devc-con 12o RECEIVE 1

8 1 hA/x86/sbin/fs-pkg 10o RECEIVE 1

8 2 hA/x86/sbin/fs-pkg 10o SIGWAITINFO

8 3 hA/x86/sbin/fs-pkg 10o RECEIVE 1

8 4 hA/x86/sbin/fs-pkg 10o RECEIVE 1

8 5 hA/x86/sbin/fs-pkg 10o RECEIVE 1

8 6 hA/x86/sbin/fs-pkg 10o RECEIVE 1

4105 1 sbin/pipe 10o RECEIVE 1

4105 2 sbin/pipe 10o RECEIVE 1

4105 3 sbin/pipe 10o RECEIVE 1

4105 4 sbin/pipe 10o RECEIVE 1

155658 1 usr/sbin/random 10o SIGWAITINFO

155658 2 usr/sbin/random 10o RECEIVE 1

155658 3 usr/sbin/random 10o NANOSLEEP

45067 1 sbin/devc-pty 10o RECEIVE 1

77836 1 sbin/io-net 10o SIGWAITINFO

77836 2 sbin/io-net 9o RECEIVE 1

77836 5 sbin/io-net 9o RECEIVE 1

77836 6 sbin/io-net 10o RECEIVE 6

77836 7 sbin/io-net 10o RECEIVE 22

77836 8 sbin/io-net 21o RECEIVE 17

77836 9 sbin/io-net 21o RECEIVE 30

77836 10 sbin/io-net 9o RECEIVE 1

77836 11 sbin/io-net 18o RECEIVE 1

77836 12 sbin/io-net 10o CONDVAR 80e1384

77836 13 sbin/io-net 10o CONDVAR 80c3174

143373 1 sbin/devb-fdc 10o SIGWAITINFO

143373 2 sbin/devb-fdc 21r RECEIVE 1

143373 3 sbin/devb-fdc 10o RECEIVE 7

143373 4 sbin/devb-fdc 10o CONDVAR b037866c

143373 5 sbin/devb-fdc 10o RECEIVE 4

143373 6 sbin/devb-fdc 10o RECEIVE 4

167950 1 usr/sbin/dumper 10o RECEIVE 1

110607 1 sbin/devc-ser8250 24o RECEIVE 1

188432 1 usr/sbin/inetd 10o SIGWAITINFO

110609 1 sbin/io-audio 10o SIGWAITINFO

110609 2 sbin/io-audio 10o RECEIVE 1

110609 3 sbin/io-audio 15o RECEIVE 1

110609 4 sbin/io-audio 10o RECEIVE 1

110609 5 sbin/io-audio 15r INTR

200722 1 usr/sbin/fs-cifs 10o RECEIVE 1

200722 2 usr/sbin/fs-cifs 10o RECEIVE 1

200722 3 usr/sbin/fs-cifs 10o RECEIVE 1

204819 1 usr/sbin/fs-cifs 10o RECEIVE 1

204819 2 usr/sbin/fs-cifs 10o RECEIVE 1

204819 3 usr/sbin/fs-cifs 10o RECEIVE 1

630804 1 photon/bin/phlogin 10r REPLY 266262

634901 1 usr/sbin/telnetd 10o SIGWAITINFO

266262 1 /photon/bin/Photon 12r RECEIVE 1

311319 1 ton/bin/fontsleuth 6o RECEIVE 1

311319 2 ton/bin/fontsleuth 6o RECEIVE 1

311319 3 ton/bin/fontsleuth 10o RECEIVE 1

634904 1 bin/sh 10o SIGSUSPEND

303129 1 hoton/bin/phfontFA 15r RECEIVE 1

344090 1 on/bin/io-graphics 12r REPLY 266262

696347 1 bin/pidin 10o REPLY 1

360476 1 ton/bin/devi-hirun 15o RECEIVE 1

360476 2 ton/bin/devi-hirun 10o REPLY 7

360476 3 ton/bin/devi-hirun 12o SIGWAITINFO

==========================
Phin ch

NID PID RID PRNT PS FLAG CH FLAG BLOCK CH PR NUMQ MAXQ BLEN PROGRAM

266262 0 V----- ----- 0 Photon

630804 30 0 -----D --P-D 0 10 1064 phlogin

630804 31 30 -----D --P-D 0 10 1064 phlogin

630804 23 31 -----D --P-D 0 10 1064 phlogin

630804 22 23 -----D --P-D 0 10 1064 phlogin

630804 53 22 -----D --P-D 0 10 1064 phlogin

630804 52 22 -----D --P-D 0 10 1064 phlogin

630804 51 0 -----D --P-D 0 10 1064 phlogin

266262 1 0 V----- ----- 0 Photon

266262 3 1 V----- ----- 0 Photon

360476 6 3 -A—D —H- 0 1 2040 devi-hirun

344090 2 3 ------ --PHD 0 4 8188 io-graphics








“Wojtek Lerch” <wojtek_l@yahoo.ca> wrote in message
news:a7aogt$etf$1@nntp.qnx.com

Dennis <> dmoses@z-kat.com> > wrote:
Thanks for your help.

Here is what happened.

Even Ctrl-Shift-Alt-BackSpace doesn’t work, right?

Bingo! Nothing on the keyboard (or mouse) would be recoganized. not
Numlock or anything.

I am able to telnet into the machine. but that is only for a couple of
mins
before it freezes.

A couple of minutes should be enough to run “pidin” and “phin ch”; could
you try that and post the output her if it’s not too much trouble? Even
though you have a workaround, it would be good to know what the problem
was…

phlogin recognizes a -T option that takes the number of seconds before
… difficulty is that the command that starts Photon is buried
somewhere in
the startup scripts.

I wasnt aware of the -T0 option (my fault… that should have been
obvious
thing to try). basically I found the startup in /usr/bin/ph and set it
to
kick into the screensaver after around a month !! its been over 24hrs
and
the machine is doing great. (But the -T0 sounds like the cleaner way to
do
it)

The script idea is pretty neat…simple and neat !!

Well, I tend to think of it as more of a hack really, but I agree that
it’s neither complicated nor messy. > :wink:


Wojtek Lerch QNX Software Systems Ltd.

Dennis <dmoses@z-kat.com> wrote:

Sorry about the late response.
the pidin looks pretty much the same as always.

Below are the Pidin and the phin outputs

I don’t see anything obviously unusual there, either.

Running “slay -shup Photon” as root from the telnet should bring you
back to text mode. Does is also give you the keyboard back?

\

Wojtek Lerch QNX Software Systems Ltd.

Yup I got the keyboard and mouse back. No problems there either.

I think for now I will stick with the no screensaver work around.

Thanks
Dennis




“Wojtek Lerch” <wojtek_l@yahoo.ca> wrote in message
news:a7sn8p$69$1@nntp.qnx.com

Dennis <> dmoses@z-kat.com> > wrote:
Sorry about the late response.
the pidin looks pretty much the same as always.

Below are the Pidin and the phin outputs

I don’t see anything obviously unusual there, either.

Running “slay -shup Photon” as root from the telnet should bring you
back to text mode. Does is also give you the keyboard back?

\

Wojtek Lerch QNX Software Systems Ltd.