From: Nathan Thompson <nate@thebog.net>
To: "Rodney M. Jokerst" <rmjokers@gnwy29.wuh.wustl.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem: Blank screen in X after heavy disk access (2.4 only)
Date: Tue, 16 Jan 2001 16:43:29 -0500 [thread overview]
Message-ID: <20010116164329.A1247@eliot.thebog.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0101161503310.24100-100000@gnwy29.wuh.wustl.edu>
In-Reply-To: <Pine.LNX.4.21.0101161503310.24100-100000@gnwy29.wuh.wustl.edu>; from rmjokers@gnwy29.wuh.wustl.edu on Tue, Jan 16, 2001 at 03:11:01PM -0600
On Tue, Jan 16, 2001 at 03:11:01PM -0600, Rodney M. Jokerst wrote:
> This action causes my screen to go blank in X and remain blank
> unless I move the mouse or type on the keyboard. The second I stop doing
> one of these activities, it goes blank again. While it is blank, it seems
> to be flashing every second, as if it is recieving blank screen commands
> repeatedly. This behavior continues until I restart the machine. If I
> switch to a console, everything is fine. If I restart the X server, the
> behavior continues.
Is this a VIA chipset based motherboard?
If so someone (Vojtech Pavlik ?) has a patch that helps this...
It is a hardware error.
For what it's worth I have seen this exact same behavior on my machine
in 2.2.x.
I have an abit ka7 motherboard, via kx133 chipset.
Nate
> thanks,
>
> Rodney M. Jokerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-16 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 21:11 Rodney M. Jokerst
2001-01-16 21:43 ` Nathan Thompson [this message]
2001-01-16 22:01 ` Rodney M. Jokerst
2001-01-17 3:27 ` Shane Shrybman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010116164329.A1247@eliot.thebog.net \
--to=nate@thebog.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmjokers@gnwy29.wuh.wustl.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®