All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: John Hunter <zhjwpku@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/bochs: convert bochs driver to atomic mode-setting
Date: Wed, 10 Jun 2015 14:20:53 +0200	[thread overview]
Message-ID: <1433938853.16508.54.camel@redhat.com> (raw)
In-Reply-To: <CAEG8a3J4A1CwtVWosO8L9yeE_pSnC-O6hjjDLvOJrpQo428tAg@mail.gmail.com>

On Mi, 2015-06-10 at 19:39 +0800, John Hunter wrote:
> Hi Gerd,
> I have tried what you told me.
> 1. Turn off fbdev support:
>     static bool enable_fbdev = false;

Good.

> 2. configure a serial console:
>     - add something like "console=ttyS0, 9600n8" to the grub menuentry

Good.

You can use 115200 as line speed to speedup the console a bit.

>     - add a start parameter to qemu when start the virtual machine
> "-serial pty"

'-serial stdio' might be more convenient.

> saned disabled; edit /etc/default/saned
> [ ok ] Starting network connection manager: NetworkManager.
> [ ok ] Starting Common Unix Printing System: cupsd.
> 
> 
> The serial console messages also stop here, no other output.

Which guest is this?  On modern linux distros (anything systemd-based)
you should automatically get a login prompt on the serial line in case
it is configured as console.  Older systems need manual configuration
for that.  Could also be the system simply hangs here.

Try adding "ignore_loglevel" and "drm.debug=0x07" to the kernel command
line.

HTH,
  Gerd



_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-06-10 12:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10  7:21 [PATCH] drm/bochs: convert bochs driver to atomic mode-setting John Hunter
2015-06-10  8:04 ` Gerd Hoffmann
2015-06-10  8:15   ` John Hunter
2015-06-10 11:39     ` John Hunter
2015-06-10 12:20       ` Gerd Hoffmann [this message]
2015-06-11  3:18         ` John Hunter
2015-06-11  6:29           ` Gerd Hoffmann
2015-06-11  6:40             ` John Hunter

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=1433938853.16508.54.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=zhjwpku@gmail.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.