From: Greg MATTHEWS <G.Matthews@cs.ucl.ac.uk>
To: Guido Guenther <agx@sigxcpu.org>
Cc: linux-mips@oss.sgi.com, debian-mips@lists.debian.org
Subject: Re: Console corruption with newport & XFree86
Date: Tue, 18 Dec 2001 10:34:19 +0000 [thread overview]
Message-ID: <4498.1008671659@cs.ucl.ac.uk> (raw)
In-Reply-To: Your message of "Tue, 18 Dec 2001 00:15:47 +0100." <20011218001546.B11359@galadriel.physik.uni-konstanz.de>
under what circumstances does corruption take place on the relevant newport?
> Hi,
> to get a better idea with which versions of the newport the console
> corruption happens I'd like to ask everybody with a newport to send me:
> - The version numbers of the different chips on the newport(as printed
> by the kernel - dmesg)
> - if it is the 8bpp or 24bpp version
> - the version number of XFree86 with which console corruption[1] happens(if
> any)
> - the version number of XFree86 with which *no* console corruption happens(if
> any)
> So even if everything is fine for you, please drop me a short notice.
> Please do this in private mail, since I don't want to pollute this ml
> with(for other people) uninteresting stuff.
> Thanks,
> -- Guido
>
> [1] completely black console with only a blinking cursor
>
>
> --
> To UNSUBSCRIBE, email to debian-mips-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
next prev parent reply other threads:[~2001-12-18 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 23:15 Console corruption with newport & XFree86 Guido Guenther
2001-12-18 10:34 ` Greg MATTHEWS [this message]
2001-12-18 10:44 ` Ladislav Michl
2001-12-18 11:27 ` Guido Guenther
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=4498.1008671659@cs.ucl.ac.uk \
--to=g.matthews@cs.ucl.ac.uk \
--cc=agx@sigxcpu.org \
--cc=debian-mips@lists.debian.org \
--cc=linux-mips@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.