On Sat, 21 Jun 2003, Hattie Rouge wrote:
> If your screensaver really died but you were still not back to normal,
> that implies the screensaver was not the problem. Or at least not the
> only problem.
>
> I've had screen savers hang a machine but in all cases, if it can be
> killed, everything
If your screensaver really died but you were still not back to normal,
that implies the screensaver was not the problem. Or at least not the
only problem.
I've had screen savers hang a machine but in all cases, if it can be
killed, everything clears up.
Dana Bourgeois
> -Original Messag
On Sat, 21 Jun 2003, Randy Kelsoe wrote:
> Tom Diehl wrote:
>
> >Since upgrading to the 2.4.20-18.8 kernel I am experiencing a lock up of the
> >display and keyboard when the screen saver comes on (only the one that describes
> >how to compile a kernel but looks like the intro to a star wars movi
Tom Diehl wrote:
Since upgrading to the 2.4.20-18.8 kernel I am experiencing a lock up of the
display and keyboard when the screen saver comes on (only the one that describes
how to compile a kernel but looks like the intro to a star wars movie) It has
happened every time that screen saver comes o
I finaly found something in the logs, after enableing all the gShield logs.
This what it looks like.
Jun 21 15:49:10 rodnabba kernel: gShield (reserved drop) IN=eth0 OUT=
MAC=xxx SRC=10.0.113.1 DST="My IP" LEN=328 TOS=0x00 PREC=0x00 TTL=63
ID=63273 PROTO=UDP SPT=67 DPT=68 LEN=308
gShield (reserve
