This looks to me as if Ubuntu (the kernel, Wayland, and/or the X server,
depending on when the problem occurs) is delivering a video mode that
the display device can't handle. (With VGA, the display should deliver
its capabilities to the computer via EDID, but this doesn't always work
correctly.) Thus, the first question is what that "display device" is.
The screen shots look like a remote KVM of some sort. Is that the BMC's
built-in screen-sharing tool, a network-accessible KVM hardware device
(like a Raritan or Avocent), or something else? If possible, I recommend
testing in person with a plain monitor plugged directly into the
computer, at least as a diagnostic procedure. If that works, then it's
likely that the issue is either a matter of a restrictive set of video
modes in the remote-access tool, miscommunication between the remote-
access tool and the kernel/Wayland/X, or both. Also, if a physical
monitor is plugged into the server while it's being accessed remotely,
it's conceivable that the kernel/Wayland/X is taking its cues about
video mode from the physical monitor rather than from the remote-access
tool, thus creating a mismatch. If the problem is caused by the remote
access tool, or by an interaction between that and the kernel/Wayland/X,
then updating the remote access tool's firmware may fix the problem.
Note that the video mode used can vary depending on the kernel version,
X vs. Wayland, EFI vs. BIOS boot mode, and other factors. Such variables
likely explain why earlier kernels worked but newer ones don't.
As a workaround, it might be possibly to forcibly reconfigure the system
to use a video mode that will work with the display device.
Unfortunately, there are a lot of different ways to do this, depending
on the subsystem involved. For instance:
* Kernel parameters can set the kernel's video mode. Unfortunately, there are
a lot of possibilities even here, including, but not limited to:
* nomodeset
* video=vga16fb:off
* vga16fb.modeset=0
* video=efifb:width:640,height:480
* Try Googling "kernel video mode setting" or something similar for
additional possibilities.
* X configuration
* If you can get X working, even temporarily, you can use the GUI
setup tools to change the resolution.
* The xrandr tool can be used to probe and set video options; see
https://www.x.org/wiki/Projects/XRandR/
* I've not kept up with text-mode (manual) X configuration, but
you may be able to find some documentation on how to get it
to change video mode. Start here:
https://help.ubuntu.com/community/VideoDriverHowto#Xorg.conf.d
* Wayland configuration
* I'm even less of an expert on this, so I suggest you try
Googling "wayland set resolution" or something similar.
Finally, note that Ubuntu server certification doesn't cover display
devices, so this is NOT a certification blocker.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1762940
Title:
Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI
boot mode
Status in linux package in Ubuntu:
Triaged
Status in install-package source package in Bionic:
New
Status in linux source package in Bionic:
Triaged
Bug description:
For all(as I know) Huawei servers, the vga adapter are embed in the
iBMC chips. Those server can install from ISO manually for 16.04.4 and
screen display normally. But for 18.04 ( tested both for daily and
final beta)version, the install screen is blur. One of tested server
is Huawei 2855 v5, the certification link for 16.04 are
https://certification.ubuntu.com/hardware/201707-25596/.
Below are key difference of dmesg. It seems might related with DRM.
18.04 install screen is blur
dmesg
...
[ 2.039009] fb0: EFI VGA frame buffer device
...
[ 4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 4.191435] [drm] No driver support for vblank timestamp query.
[ 4.209338] checking generic (90000000 300000) vs hw (0 0)
[ 4.209384] fbcon: hibmcdrmfb (fb1) is primary device
[ 4.209385] fbcon: Remapping primary device, fb1, to tty 1-63
...
[ 5.357024] hibmc-drm 0000:07:00.0: fb1: hibmcdrmfb frame buffer device
[ 5.380085] [drm] Initialized hibmc 1.0.0 20160828 for 0000:07:00.0 on
minor 0
...
[ 5.636624] vga16fb: initializing
[ 5.636627] vga16fb: mapped to 0x0000000048a7a1d2
[ 5.636630] checking generic (90000000 300000) vs hw (a0000 10000)
[ 5.636676] fb2: VGA16 VGA frame buffer device
...
16.04.4 install screen is fine (no screen blur)
dmesg
...
[ 2.000419] fb0: EFI VGA frame buffer device
....
[ 8.795065] vga16fb: initializing
[ 8.795068] vga16fb: mapped to 0xffff8800000a0000
[ 8.795071] checking generic (98000000 300000) vs hw (a0000 10000)
[ 8.795121] fb1: VGA16 VGA frame buffer device
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
