Video Crash

A. Racine aracine at
Sat May 27 01:46:46 PDT 2000

Try piping the attachment through less. You'll need to have
enable-unix-pipe-cmd set in your config, though. There are FAT errors,
floppy CRC errors, and more. In a quick pass, I didn't see anything that
indicated that the monitor crapped out.


On Sat, 27 May 2000, R. David Whitlock wrote:

# Hrmmm, all I get when I look at the attachment is a message "Can't display
# missing text segment" from pine, so I'm not really sure what you see. Can
# you describe it in greater detail?
# Here's a theory: could it be because you have power management turned on
# and so the apm daemon kicked in and tried to set your monitor in sleep
# mode? (and failed?) It's about the only reason I can imagine a monitor
# acting on it's own without someone touching it... I mean, killing the
# XServer should be fairly conclusive, and since that didn't work, I suspect
# a lower-level cause like hardware. (you did try to kill the xserver first
# by pressing ctrl-alt-backspace, right?)
# Of course, it's just a shot in the dark. More details?
# Later,
# David
# On Fri, 26 May 2000, Benjamin Honsinger wrote:
# > This is weird. I used my computer a couple of hours ago, and came back to use
# > it again a few minutes later. The monitor simple wouldn't work, acting like it
# > was receiving _no_ info from the computer. This must have been the case,
# > because the Self Test message was on the screen, saying the monitor was fine,
# > please check your cable blah blah. I don't know what caused the crash, all I
# > have is a rather long e-mail e-mailed to me by the system. I think it holds the
# > clues to what happened, but I can't figure it out. Could someone please look at
# > the attached e-mail and tell me what happened and why my video card simply
# > stopped working until I rebooted? (Now everything seems fine).
# > Any help would be much appreciated, thanks!
# >
# > - Benjamin Honsinger

More information about the Linux mailing list