<div dir="ltr">Hi Gerd,<div>Here is what I got:<div><br></div><div><div>[ 813.137939] [drm:drm_pci_init] </div><div>[ 813.142780] [drm:drm_get_pci_dev] </div><div>[ 813.156986] [drm:drm_minor_register] </div><div>[ 813.212679] [drm:drm_minor_register] new minor registered 64</div><div>[ 813.213341] [drm:drm_minor_register] </div><div>[ 813.215081] [drm:drm_minor_register] </div><div>[ 813.235736] [drm:drm_minor_register] new minor registered 0</div><div>[ 813.252701] [drm] Found bochs VGA, ID 0xb0c0.</div><div>[ 813.254993] [drm] Framebuffer size 8192 kB @ 0xfe000000, ioports @ 0x1ce.</div><div>[ 813.271384] [TTM] Zone kernel: Available graphics memory: 513150 kiB</div><div>[ 813.272036] [TTM] Initializing pool allocator</div><div>[ 813.279538] [TTM] Initializing DMA pool allocator</div><div>[ 813.299800] [drm:drm_sysfs_connector_add] adding "Virtual-1" to sysfs</div><div>[ 813.303164] [drm:drm_sysfs_hotplug_event] generating hotplug event</div><div>[ 813.313079] [drm] Initialized bochs-drm 1.0.0 20130925 for 0000:00:02.0 on minor 0</div></div><div><br></div><div>If I remove the bochs-drm.ko from its place, then boot the virtual machine, after it runs,</div><div>copy the bochs-drm.ko to its original place, depmod the module, and modprobe </div><div>bochs-drm, it give the messages above. Seems like the bochs driver works, but</div><div>if I reboot with the bochs-drm.ko, it goes to dark, and the messages related to bochs</div><div>is same as above.</div><div><br></div><div>I guess the problem is because that I take no care of bochs_hw_setbase after remove</div></div><div>the bochs_crtc_mode_set_base, but I am not sure. </div><div><br></div><div>I will be appreciate if you can review the patch a bit and tell me where the problem</div><div>might be, and I will dig more into that.</div><div><br></div><div>I really can't get any clue.</div><div><br></div><div>If my question is stupid, forgive me, I will try to catch up :)</div><div><br></div><div>Best Regards,</div><div>Zhao</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 10, 2015 at 8:20 PM, Gerd Hoffmann <span dir="ltr"><<a href="mailto:kraxel@redhat.com" target="_blank">kraxel@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mi, 2015-06-10 at 19:39 +0800, John Hunter wrote:<br>
> Hi Gerd,<br>
> I have tried what you told me.<br>
> 1. Turn off fbdev support:<br>
> static bool enable_fbdev = false;<br>
<br>
</span>Good.<br>
<span class=""><br>
> 2. configure a serial console:<br>
> - add something like "console=ttyS0, 9600n8" to the grub menuentry<br>
<br>
</span>Good.<br>
<br>
You can use 115200 as line speed to speedup the console a bit.<br>
<span class=""><br>
> - add a start parameter to qemu when start the virtual machine<br>
> "-serial pty"<br>
<br>
</span>'-serial stdio' might be more convenient.<br>
<span class=""><br>
> saned disabled; edit /etc/default/saned<br>
> [ ok ] Starting network connection manager: NetworkManager.<br>
> [ ok ] Starting Common Unix Printing System: cupsd.<br>
><br>
><br>
> The serial console messages also stop here, no other output.<br>
<br>
</span>Which guest is this? On modern linux distros (anything systemd-based)<br>
you should automatically get a login prompt on the serial line in case<br>
it is configured as console. Older systems need manual configuration<br>
for that. Could also be the system simply hangs here.<br>
<br>
Try adding "ignore_loglevel" and "drm.debug=0x07" to the kernel command<br>
line.<br>
<br>
HTH,<br>
Gerd<br>
<br>
<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>Best regards<br></div><div>Junwang Zhao</div><div>Microprocessor Research and Develop Center</div><div>Department of Computer Science &Technology</div><div>Peking University</div><div>Beijing, 100871, PRC</div></div></div>
</div>