Comment 9 for bug 1872863

For both tests I used the kmod package from my test ppa, since it is still
in the unapproved upload queue.

Firstly, I installed 4.15.0-99-generic from -updates, and booted my EFI based
KVM machine with VGA=std. The screen was garbled, as the framebuffer used was
efifb.

I then installed 4.15.0-100-generic from -proposed, and rebooted, keeping the
same settings. The screen was perfect and readable. The issue was fixed. I looked
at lsmod, and bochs-drm was loaded.

$ lsmod | grep bochs_drm
bochs_drm 20480 1
ttm 106496 1 bochs_drm
drm_kms_helper 172032 1 bochs_drm
drm 401408 4 drm_kms_helper,bochs_drm,ttm

Dmesg shows:

[ 1.082068] checking generic (c0000000 12c000) vs hw (c0000000 1000000)
[ 1.082069] fb: switching to bochsdrmfb from EFI VGA
[ 1.082468] Console: switching to colour dummy device 80x25
[ 1.083148] [drm] Found bochs VGA, ID 0xb0c5.
[ 1.083151] [drm] Framebuffer size 16384 kB @ 0xc0000000, mmio @ 0xc1c8c000.
[ 1.083386] [TTM] Zone kernel: Available graphics memory: 4026194 kiB
[ 1.083389] [TTM] Zone dma32: Available graphics memory: 2097152 kiB
[ 1.083390] [TTM] Initializing pool allocator
[ 1.083394] [TTM] Initializing DMA pool allocator
[ 1.085265] fbcon: bochsdrmfb (fb0) is primary device
[ 1.087421] Console: switching to colour frame buffer device 128x48
[ 1.091589] bochs-drm 0000:00:01.0: fb0: bochsdrmfb frame buffer device
[ 1.108664] [drm] Initialized bochs-drm 1.0.0 20130925 for 0000:00:01.0 on minor 0

Attached is a screenshot showing a good screen. I am happy to mark this as
verified for the linux package.