From: Ryan Cumming <bodnar42@phalynx.dhs.org>
To: Dan Merillat <harik@chaos.ao.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: radeonfb bug: text ends up scrolling in the middle of tux.
Date: Mon, 19 Nov 2001 17:59:46 -0800 [thread overview]
Message-ID: <E1660CQ-0001CY-00@localhost> (raw)
In-Reply-To: <200111200133.fAK1XT2J000773@vulpine.ao.net>
In-Reply-To: <200111200133.fAK1XT2J000773@vulpine.ao.net>
On November 19, 2001 17:33, Dan Merillat wrote:
> Ok, I've poked around but I can't find a penguin or tux bitmap to
> figure out why scrolling is so broken. I've got to login blind and type
> reset to get the console back. Needless to say, no kernel messages
> are readable after the mode-switch (they all overwrite themselves on
> a single line)
Type 'dmesg' as root to get all your lost kernel messages back. Hopefully
they'll shed some light on the problem.
-Ryan
next prev parent reply other threads:[~2001-11-20 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 1:33 radeonfb bug: text ends up scrolling in the middle of tux Dan Merillat
2001-11-20 1:59 ` Ryan Cumming [this message]
2001-11-20 12:24 ` Ingo Saitz
-- strict thread matches above, loose matches on Subject: below --
2001-11-20 4:38 Dan Merillat
2001-11-21 3:13 Louis Garcia
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=E1660CQ-0001CY-00@localhost \
--to=bodnar42@phalynx.dhs.org \
--cc=harik@chaos.ao.net \
--cc=linux-kernel@vger.kernel.org \
/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