public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luca Falavigna <dktrkranz@gmail.com>
To: ebiederm@xmission.com, rddunlap@osdl.org
Cc: fastboot@osdl.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: kexec and frame buffer
Date: Thu, 04 Aug 2005 13:35:47 +0000	[thread overview]
Message-ID: <42F219B3.6090502@gmail.com> (raw)

I made three experiments regarding kexec with frame buffer support (vesafb). For
each of them I gathered dmesg messages from original and relocated kernel, in
order to easily compare them later on. These tests were run on a virtual machine
in order to provide the same environment for each experiment.

Here are my tests and related results:



	1) Frame buffer not enabled

Original kernel command line: root=/dev/hda1 ro
Relocated kernel command line: root=/dev/hda1 ro

Everything went well, as supposed to be. I was able to read boot messages and to
see login prompts.


	2) Frame buffer enabled in the relocated kernel

Original kernel command line: root=/dev/hda1 ro
Relocated kernel command line: root=/dev/hda1 ro vga=791

This time I was able to read boot messages and so on, but I couldn't be able to
load vesafb in the relocated kernel. dmesg showed nothing about vesafb.


	3) Frame buffer enabled in the original kernel

Original kernel command line: root=/dev/hda1 ro vga=791
Relocated kernel command line: root=/dev/hda1 ro {vga=791,}

This time I wasn't able to read boot messages in the relocated kernel, whether
vga parameter was set or not. I looked at dmesg in order to get some useful
informations:

Linux version 2.6.13-rc5 (dktrkranz@gandalf) (gcc version 3.3.4 (Debian
1:3.3.4-13)) #3 Wed Aug 3 13:39:11 UTC 2005
[...]
-Console: colour dummy device 80x25
+Console: colour VGA+ 80x25
[...]
-vesafb: framebuffer at 0xf0000000, mapped to 0xc2880000, using 3072k, total
16384k
-vesafb: mode is 1024x768x16, linelength=2048, pages=0
-vesafb: protected mode interface info at 00ff:44f0
-vesafb: scrolling: redraw
-vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
-mtrr: your processor doesn't support write-combining
-Console: switching to colour frame buffer device 128x48
-fb0: VESA VGA frame buffer device
[...]

It seems relocated kernel doesn't (or can't) load vesafb. Is frame buffer
supported in kexec or there is some work-in-progress?



Regards,
--
					Luca



             reply	other threads:[~2005-08-04 16:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 13:35 Luca Falavigna [this message]
2005-08-04 18:43 ` kexec and frame buffer Eric W. Biederman
2005-08-06 14:19   ` Luca Falavigna
2005-08-06 16:50     ` Eric W. Biederman
2005-08-07 15:19       ` Luca Falavigna
2005-08-12 18:53         ` Luca Falavigna
2005-08-12 17:10           ` Eric W. Biederman

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=42F219B3.6090502@gmail.com \
    --to=dktrkranz@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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