mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Seiichi Nakashima <nakasima@kumin.ne.jp>
To: linux-kernel@vger.kernel.org
Subject: VESA VGA Graphic console has bug ?
Date: Sun, 04 Aug 2002 20:00:44 +0900	[thread overview]
Message-ID: <200208041100.AA00109@prism.kumin.ne.jp> (raw)

Hi.

I use linux-2.5.30 with VESA VGA Graphic console at slackware-8.1 based environment.
when I use emacs( 21.2 ), these situation occured. (I used to boot up with vga=771)

(1) # emacs /tmp/test
    I type a line ( /sbin/ifconfig lo 127.0.0.1 ), and save file.

(2) # emacs /tmp/test
    a line ( /sbin/ifconfig lo 127.0.0.1 ) displayed in emacs frame.

(3) I wand to insert few spaces between /sbin/ifconfig and lo.
    when I type a space, then a line change to a line ( /sbin/ifconfig  oo 127.0.0.1 ).
    I could not edit a line as I want to edit.
    this situation display only. when I save file and re-read file, results were fine.

(4) I boot up PC ( erase VGA option ), I checked this test, everything OK.

I checked a same test at linux-2.5.26,28,30 and got a same result.
I checked at linux-2.4.19, it is OK( everything work fine with vga=771 ).
I thinked VESA VGA Graphic console has bug to display in emacs frame.

Before VESA VGA Graphic console occured kernel panic at linux-2.5.14,15.
from linux-2.5.16 VESA VGA Graphic console compile and work fine,
but Pengin Image did not display at boot up time. is it OK?

--------------------------------
  Seiichi Nakashima
  Email   nakasima@kumin.ne.jp
--------------------------------

             reply	other threads:[~2002-08-04 10:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-04 11:00 Seiichi Nakashima [this message]
2002-08-31 11:12 ` linux-2.5.32 boot up but hang up Seiichi Nakashima
2002-08-31 13:46   ` Zwane Mwaikambo
2002-08-31 22:08     ` Seiichi Nakashima
2002-08-31 22:22       ` Seiichi Nakashima
2002-11-22  2:46   ` patch-2.5.48-dj1 compile error Seiichi Nakashima
2002-11-22  3:50     ` Randy.Dunlap
2003-03-04 12:29     ` linux-2.2.24-rc5 Seiichi Nakashima
2004-01-17 14:53       ` linux-2.0.40-rc7 Seiichi Nakashima
2004-01-17 16:44         ` linux-2.0.40-rc7 David Weinehall
2004-01-30 15:05         ` linux-2.0.40-rc8 Seiichi Nakashima
2004-01-30 16:50           ` linux-2.0.40-rc8 David Weinehall
2004-02-14  0:52           ` linux-2.0.40 Seiichi Nakashima
2004-02-14  7:43             ` linux-2.0.40 David Weinehall
2004-05-04  5:00             ` USB Memory Seiichi Nakashima
2003-06-23 22:36     ` linux-2.5.73 compile error Seiichi Nakashima
2003-06-24 16:35       ` Greg KH
2003-06-24 18:15         ` Bill Davidsen
2003-06-24 18:42           ` Greg KH
2003-06-25 14:04         ` Seiichi Nakashima

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=200208041100.AA00109@prism.kumin.ne.jp \
    --to=nakasima@kumin.ne.jp \
    --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

Powered by JetHome