All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kinsella, Ray" <ray.kinsella-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: "linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"jason.taylor-RrviKlmTjidOSnsfY10OVw@public.gmane.org"
	<jason.taylor-RrviKlmTjidOSnsfY10OVw@public.gmane.org>
Subject: Re: efi_printk
Date: Fri, 15 Apr 2016 16:32:50 +0000	[thread overview]
Message-ID: <1460737968.3575.63.camel@intel.com> (raw)
In-Reply-To: <666a26ae-8a78-a2d0-77c3-e2724be7d1d5-RrviKlmTjidOSnsfY10OVw@public.gmane.org>


Should work then, once you set earlyprintk=efi. 

As I remember from reading the efi printk code, their is an assumption
that UEFI supports framebuffer. In my case my board was headless, so
earlyprintk=efi did not work for me.  

Given your virtualized environment, it is not outside possibility that
their is no framebuffer support in the VM's UEFI? 

Thanks,

Ray K 

On Fri, 2016-04-15 at 10:24 -0400, Jason Taylor wrote:
> On 4/15/2016 6:08 AM, Kinsella, Ray wrote:
> > 
> > Have you set CONFIG_EARLY_PRINTK_EFI ?
> 
> Yes, I enabled that build option.
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-efi"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2016-04-15 16:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 19:25 efi_printk Jason Taylor
     [not found] ` <005f85571fda40a483f7a5b7438a738d-KbE+qi2yd2TmmfPIhZPphU4JlKGuRTdvVpNB7YpNyf8@public.gmane.org>
2016-04-15 10:08   ` efi_printk Kinsella, Ray
     [not found]     ` <1460714923.3575.2.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-04-15 14:24       ` efi_printk Jason Taylor
     [not found]         ` <666a26ae-8a78-a2d0-77c3-e2724be7d1d5-RrviKlmTjidOSnsfY10OVw@public.gmane.org>
2016-04-15 16:32           ` Kinsella, Ray [this message]

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=1460737968.3575.63.camel@intel.com \
    --to=ray.kinsella-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=jason.taylor-RrviKlmTjidOSnsfY10OVw@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.