Blank screen with only mouse pointer after 7.10 radeon driver update; display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-ati-hwe-16.04 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I get a blank screen with only mouse pointer upon boot, after the splash. This started after the mesa driver update on 2/15/18. The display does not appear to switch to tty7 upon lightdm start.
Xorg.0.log quickly grows and continues to grow.
I believe `lightdm` is not starting `Xorg` on the correct display, but, I don't know how to determine this from the logs.
Here is the command line `lightdm` uses to launch `Xorg`:
~$ ps -ef | grep lightdm
root 1261 1 0 18:23 ? 00:00:00 /usr/sbin/lightdm
root 1316 1261 6 18:23 tty7 00:00:03 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/
root 1350 1261 0 18:23 ? 00:00:00 lightdm --session-child 12 15
*OCCURRENCE ON 2/15/18:*
I performed a normal upgrade on 2/15/18 through the software manager in 16.04LTS.
It upgraded the following libraries (`/var/log/dpkg.log [pkg][old ver][new ver]`):
libegl1-
libwayland-
libwayland-
libegl1-
libegl1-
libgbm1:amd64 17.2.4-
libgbm1:i386 17.2.4-
libosmesa6:
libosmesa6:i386 17.2.4-
libgles2-
libgl1-
libgl1-
libglapi-
libglapi-
libgl1-
libgl1-
libxatracke
linux-
mesa-
mesa-
xserver-
xserver-
I should note, this is *not* the compiz/unity update package list. It is the mesa drivers.
Upon reboot, I started getting a blank screen with only a mouse pointer when the display manager started.
I press <kbd>CTRL<
[ 4800.851] (WW) RADEON(0): flip queue failed: Invalid argument
[ 4800.851] (WW) RADEON(0): Page flip failed: Invalid argument
These warning messages are *constantly* streaming into the log file, and it *keeps growing*. This wasn't present before the library update. I will be happy to provide a logfile upon request.
Video h/w on my laptop:
*-display
description: VGA compatible controller
product: RV516/M64-S [Mobility Radeon X2300]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:01:00.0
version: 00
width: 32 bits
clock: 33MHz
resources: irq:16 memory:
1st lines of modinfo output:
filename: /lib/modules/
license: GPL and additional rights
description: ATI Radeon
*UPDATE 2/16/18:*
I appear to be booting to the wrong VT display. All of the symptoms above are true; however, if I perform a <kbd>CTRL<
Here is the output of `w` immediately after pressing <kbd>CTRL<
09:38:01 up 44 min, 1 user, load average: 0.60, 0.67, 0.82
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
user1 tty7 :0 08:53 44:14 6:16 0.29s /sbin/upstart -
This display listing appears normal.
I should note that compiz and unity still seem to function. The desktop is fully available and already loaded when I switch to tty7.
*UPDATE 2/19/18:*
I don't believe this to be a duplicate of the compiz/unity issue. The issue I observed resulted from the mesa driver update on the morning of 2/15/18. The compiz/unity update has yet to be applied to my system. In fact, there is one other post that looks to be the same issue as I am seeing, it is: https:/
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-
ProcVersionSign
Uname: Linux 4.13.0-26-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb 19 10:22:52 2018
InstallationDate: Installed on 2017-04-05 (319 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: xserver-
UpgradeStatus: No upgrade log present (probably fresh install)
summary: |
- Blank screen with only mouse pointer after mesa driver update; display - does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows + Blank screen with only mouse pointer after 7.10 radeon driver update; + display does not switch to tty7 upon lightdm start; Xorg.0.log quickly + grows |
I think something is hosed with the radeon driver in mesa 17.2.8, but I can't find the 17.2.4 pkgs to roll back and test the theory. The 17.2.4 was pulled from updates and proposed lines. I'm hesitant to rollback to 11.2.
I can get you anything you need (logs, etc...) look at the issue. I'm a longtime, old school developer. Lived in the 'nix env for about 20 yrs, mostly Solaris. Love Ubuntu and Debian.