public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* 2.4.x kernels cause random launch of xscreensaver?
@ 2002-07-15 22:26 Richard Sembera
  2002-07-16  9:42 ` Bernd Schubert
  0 siblings, 1 reply; 3+ messages in thread
From: Richard Sembera @ 2002-07-15 22:26 UTC (permalink / raw)
  To: linux-kernel

Hi all,

I asked around in the Slackware NG about this problem last week and got 
redirected here. I hope someone can help. I'm not subscribed to the mailing 
list so please cc me copies of your replies.

On Slackware 8.0, when I try to install the 2.4.5 kernel, I get a problem 
with X, namely, xscreensaver starts up at random intervals. Sometimes the 
problem shows up immedately, sometimes it takes longer (the longest period so 
far has been 2 days). While I'm working, xscreensaver will suddenly go off, 
complain about not being able to grab the mose pointer, and launch a random 
screen saver. After typing in my password to unlock the screen, xscreensaver 
launches again after an interval of about 2-10 seconds.

If I disable xscreensaver in my .xinitrc file (or try fvwm2 instead of my 
standard xfce), then instead of xscreensaver I just get a blank screen, as if 
there were no video signal. Moving the mouse gets me a normal display, but at 
2-5 second intervals the screen will simply black out as described.

I've tried installing the 2.4.18 kernel but got the same problem. The 2.2.19 
kernel works just fine, however. I've also experienced the same problem with 
SuSE 7.1 and a 2.4.0 kernel.

It was suggested in the Slackware NG that it might be a clock problem. I do 
have the "clock timer configuration lost--probably a VIA686" message coming 
up intermittently at boot time and during shutdown, although I don't have a 
VIA chipset (in fact, this is why I switched to Slack, which by default 
doesn't log or display kernel messages).

I hope someone can offer suggestions or advice. I'm including as much 
trechnical information as seems relevant, though I'm just a hobbyist, so 
please ask if something's not quite clear.

Thanks in advance,

Richard Sembera.

Technical Info:

Monitor: old 14" el cheapo non-PnP

Graphics Card: (SuperProbe output):
	First video: Super-VGA
        Chipset: S3 ViRGE/DX (PCI Probed)
        Memory:  4096 Kbytes
        RAMDAC:  Generic 8-bit pseudo-color DAC
                 (with 6-bit wide lookup tables (or in 6-bit mode))

Mouse: standard serial mouse on ttyS0

CPU: Intel Pentium MMX 166 MHz

Motherboard: AOpenAP57
Chipset: SiS 5571 PCIset
(I recall that there is an issue with these boards, they were supposed to be 
USB-enabled, but the company goofed something up and they were sold as 
non-USB boards. See below:)

lspci -v output:

00:00.0 Host bridge: Silicon Integrated Systems [SiS] 5571
	Flags: bus master, medium devsel, latency 255

00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 01)
	Flags: bus master, medium devsel, latency 0

00:01.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev c0) 
(prog-if 8a [Master SecP PriP])
	Subsystem: Unknown device 0058:0000
	Flags: bus master, fast devsel, latency 64, IRQ 14
	I/O ports at 01f0
	I/O ports at 03f4
	I/O ports at 0170
	I/O ports at 0374
	I/O ports at 4000

00:01.2 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev b0) 
(prog-if 10 [OHCI])
	Flags: bus master, medium devsel, latency 64, IRQ 10
	Memory at e4000000 (32-bit, non-prefetchable)
	I/O ports at 6000

00:0c.0 VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 01) (prog-if 
00 [VGA])
	Subsystem: S3 Inc. ViRGE/DX
	Flags: bus master, medium devsel, latency 64, IRQ 11
	Memory at e0000000 (32-bit, non-prefetchable)

-- 
Richard Sembera, Ph.D.
es034@ncf.carleton.ca
http://ncf.carleton.ca/~es034

^ permalink raw reply	[flat|nested] 3+ messages in thread
* 2.4.x kernels cause random launch of xscreensaver?
@ 2002-07-16  3:16 Richard, Sembera
  0 siblings, 0 replies; 3+ messages in thread
From: Richard, Sembera @ 2002-07-16  3:16 UTC (permalink / raw)
  To: linux-kernel

Hi all,

I asked around in the Slackware NG about this problem last
week and got 
redirected here. I hope someone can help. I'm not
subscribed to the mailing 
list so please cc me copies of your replies.

On Slackware 8.0, when I try to install the 2.4.5 kernel, I
get a problem 
with X, namely, xscreensaver starts up at random intervals.
Sometimes the 
problem shows up immedately, sometimes it takes longer (the
longest period so 
far has been 2 days). While I'm working, xscreensaver will
suddenly go off, 
complain about not being able to grab the mose pointer, and
launch a random 
screen saver. After typing in my password to unlock the
screen, xscreensaver 
launches again after an interval of about 2-10 seconds.

If I disable xscreensaver in my .xinitrc file (or try fvwm2
instead of my 
standard xfce), then instead of xscreensaver I just get a
blank screen, as if 
there were no video signal. Moving the mouse gets me a
normal display, but at 
2-5 second intervals the screen will simply black out as
described.

I've tried installing the 2.4.18 kernel but got the same
problem. The 2.2.19 
kernel works just fine, however. I've also experienced the
same problem with 
SuSE 7.1 and a 2.4.0 kernel.

It was suggested in the Slackware NG that it might be a
clock problem. I do 
have the "clock timer configuration lost--probably a
VIA686" message coming 
up intermittently at boot time and during shutdown,
although I don't have a 
VIA chipset (in fact, this is why I switched to Slack,
which by default 
doesn't log or display kernel messages).

I hope someone can offer suggestions or advice. I'm
including as much 
trechnical information as seems relevant, though I'm just a
hobbyist, so 
please ask if something's not quite clear.

Thanks in advance,

Richard Sembera.

Technical Info:

Monitor: old 14" el cheapo non-PnP

Graphics Card: (SuperProbe output):
        First video: Super-VGA
        Chipset: S3 ViRGE/DX (PCI Probed)
        Memory:  4096 Kbytes
        RAMDAC:  Generic 8-bit pseudo-color DAC
                 (with 6-bit wide lookup tables (or in
6-bit mode))

Mouse: standard serial mouse on ttyS0

CPU: Intel Pentium MMX 166 MHz

Motherboard: AOpenAP57
Chipset: SiS 5571 PCIset
(I recall that there is an issue with these boards, they
were supposed to be 
USB-enabled, but the company goofed something up and they
were sold as 
non-USB boards. See below:)

lspci -v output:

00:00.0 Host bridge: Silicon Integrated Systems [SiS] 5571
        Flags: bus master, medium devsel, latency 255

00:01.0 ISA bridge: Silicon Integrated Systems [SiS]
85C503/5513 (rev 01)
        Flags: bus master, medium devsel, latency 0

00:01.1 IDE interface: Silicon Integrated Systems [SiS]
5513 [IDE] (rev c0) 
(prog-if 8a [Master SecP PriP])
        Subsystem: Unknown device 0058:0000
        Flags: bus master, fast devsel, latency 64, IRQ 14
        I/O ports at 01f0
        I/O ports at 03f4
        I/O ports at 0170
        I/O ports at 0374
        I/O ports at 4000

00:01.2 USB Controller: Silicon Integrated Systems [SiS]
7001 (rev b0) 
(prog-if 10 [OHCI])
        Flags: bus master, medium devsel, latency 64, IRQ
10
        Memory at e4000000 (32-bit, non-prefetchable)
        I/O ports at 6000

00:0c.0 VGA compatible controller: S3 Inc. ViRGE/DX or /GX
(rev 01) (prog-if 
00 [VGA])
        Subsystem: S3 Inc. ViRGE/DX
        Flags: bus master, medium devsel, latency 64, IRQ
11
        Memory at e0000000 (32-bit, non-prefetchable)

-- 
Richard Sembera
es034@ncf.carleton.ca
http://ncf.carleton.ca/~es034


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-07-16  9:39 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-07-15 22:26 2.4.x kernels cause random launch of xscreensaver? Richard Sembera
2002-07-16  9:42 ` Bernd Schubert
  -- strict thread matches above, loose matches on Subject: below --
2002-07-16  3:16 Richard, Sembera

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox