Unable to extend to second display

Bug #1576864 reported by Cgiraud
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Expired
Low
Unassigned

Bug Description

Upgrading from UbuntuStudio 15.10 to 16.04, my 2nd display is a no more a 1st display extension and only a clone. xrand detects only one display.

$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x 1050
default connected 1400x1050+0+0 0mm x 0mm
   1400x1050 77.00*
$ lspci -nn | grep VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644]
$ dmesg | egrep 'drm|radeon'
[ 1.293303] [drm] Initialized drm 1.1.0 20060810
[ 1.328085] [drm] VGACON disable radeon kernel modesetting.
[ 1.328109] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
[ 12.801460] [drm] VGACON disable radeon kernel modesetting.
[ 12.801484] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
$ uname -r
4.4.0-21-lowlatency
$

Seems same than bug 1407505, but apport-bug failed, so I created a new bug.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
Uname: Linux 4.4.0-21-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Apr 29 23:19:49 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-08-21 (252 days ago)
InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-04-24 (5 days ago)
---
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CasperVersion: 1.380
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
LiveMediaBuild: Ubuntu-Studio 17.04 "Zesty Zapus" - Release amd64 (20170412)
Package: xorg 1:7.7+16ubuntu3
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 4.10.0-19.21-lowlatency 4.10.8
Tags: zesty
Uname: Linux 4.10.0-19-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
Cgiraud (cgiraud) wrote :
Revision history for this message
Cgiraud (cgiraud) wrote :

I had to roll-back to 15.10 and fglrx proprietary drivers to get back my 2 displays.

Revision history for this message
penalvch (penalvch) wrote :

Cgiraud, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information:
apport-collect -p xorg 1576864

When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
summary: - No UMS support in radeon module
+ Unable to extend to second display
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Cgiraud (cgiraud) wrote : Dependencies.txt

apport information

tags: added: apport-collected zesty
description: updated
Revision history for this message
Cgiraud (cgiraud) wrote : JournalErrors.txt

apport information

Revision history for this message
Cgiraud (cgiraud) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Cgiraud (cgiraud) wrote :

This bug still alive within Linux version 4.10.0-19-lowlatency (booting UbuntuStudio 17.04 from USB stick).

$ egrep 'drm|radeon' /media/cyril/SanDiskBlanc/dmesg170430.log
[ 7.414065] [drm] Initialized
[ 7.451216] [drm] VGACON disable radeon kernel modesetting.
[ 7.451282] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
[ 17.166670] [drm] VGACON disable radeon kernel modesetting.
[ 17.166728] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
[ 29.316284] [drm] VGACON disable radeon kernel modesetting.
[ 29.316343] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
$

(see apport information just before this post).

Quite annoying because AMD proprietary driver unavailable for new kernels.

Status moved from Expired to New.

Changed in xorg (Ubuntu):
status: Expired → New
Revision history for this message
Cgiraud (cgiraud) wrote :

Note that according to https://help.ubuntu.com/community/RadeonDriver Radeon HD 6410D should be supported.

$ lspci -nn | grep -E "VGA|Display"
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644]
$

Revision history for this message
penalvch (penalvch) wrote :

Cgiraud, when you performed the apport-collect you either didn't install xdiagnose, or you didn't click Yes for attaching additional debugging information, as requested in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576864/comments/3 .

Could you please advise?

Changed in xorg (Ubuntu):
status: New → Incomplete
Revision history for this message
Cgiraud (cgiraud) wrote :

Christopher,
My 2017-04-30 report was from standard UbuntuStudio live distro 17.04. Sorry for xdiagnose missing.
Since 2017-04-30, I bought a new graphic card Radeon HD 7450 that works fine with UbuntuStudio 17.04 and upgrade to this new version (and got new Kdenlive version that works quite well!).
I've just installed xdiagnose and I'll move out this new graphic card to apport new data as soon as possible.

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

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

Changed in xorg (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.