Wrong resolution during boot

Bug #1820685 reported by Bart van Pelt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

When booting the startup screen is in low resolution while before it was in high resolution.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 18 18:04:57 2019
DistUpgraded: 2018-09-26 21:31:06,974 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 530] [1043:839b]
InstallationDate: Installed on 2018-01-04 (437 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: ASUSTeK COMPUTER INC. CM6870
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=UUID=4aa7afed-ca87-4f94-9a08-c806fccfbd1d ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-09-26 (172 days ago)
dmi.bios.date: 12/25/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0708
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: CM6870
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0708:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: Desktop
dmi.product.name: CM6870
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Sep 26 20:09:04 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: nouveau

Revision history for this message
Bart van Pelt (pinguin03) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Low resolution during boot is something usually caused by the Nvidia proprietary driver. So I wonder if you might still have some remnants of that installed?

tags: added: nouveau nvidia
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Actually it looks like just vesafb starting in low resolution:

[ 0.532845] vesafb: mode is 1280x1024x32, linelength=5120, pages=0
[ 0.532846] vesafb: scrolling: redraw
[ 0.532847] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.532854] vesafb: framebuffer at 0xf1000000, mapped to 0x (ptrval), using 5120k, total 5120k

which is then later corrected by nouveaufb:

[ 15.346865] fb: switching to nouveaufb from VESA VGA
...
[ 16.853149] nouveau 0000:01:00.0: DRM: allocated 1920x1080 fb: 0x60000, bo 000000004d979e0c

so it sounds like the main issue is that vesafb is used at all during boot.

affects: xorg (Ubuntu) → linux (Ubuntu)
tags: removed: nvidia
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Can you please try some slightly older kernels and tell us if using those avoids the bug?

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Bart van Pelt (pinguin03) wrote :

After some reading on internet I decided yesterday to install the nvidia diverse in package nvidia-driver-390. This resulted in a non-working graphic display. So I had to restore my installed packages and remove the nvidia-driver-390 package.

When rebooting the initial screen showed the expected graphic resolution instead of a terminal like screen.

I still don't quite understand what happened.
nvidia-settings? or graphic card which has gotten wrong commands from previous installed driver?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.