mir multi-monitor boots to black screen with radeon

[jerrylamos]

Followed https://wiki.ubuntu.com/Mir/MultiMonitorTesting on saucy 3.11.0-4 including system-compositor install.
Booted to black screens both built in 1366x768 and external 1600x900
In recovery mode boots but slow jerky screen updating.
system settings thinks this is the built-in monitor, it's not, it's the external monitor. The real built-in is black. Acer Aspire 5253 wide screen notebook.
Resolution running is 1152x864, no clue where that came from. xrandr doesn't recognize the monitor and only shows one.
"top" does not show system compositor running.
Boot message about an internal error which it would not report complaining about third party package - mir of course.
Will try to boot with external monitor disconnected.

[jerrylamos (jerrylamos)]

Tried booting with external monitor disconnected. Came up in degraded graphics mode .
Rebooted in recovery mode, screen is at 1024x768 and monitor settings does not show 1366x768.
Display is patchy anjd jerky.

"topp" shows Xorg running but no system compositor entry.

What do I do, apt-get remove system compositor? Re-install saucy?

Thanks.

Now rebooting 13.04.

[jerrylamos (jerrylamos)]

Here's the Xorg.0.log
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310]
Sometimes boots black, sometimes in degraded graphics mode because it can't detect the graphics.

[jerrylamos (jerrylamos)]

There's an Xorg.1.log also

[jerrylamos (jerrylamos)]

There's an Xorg.1.log also

[jerrylamos (jerrylamos)]

Also an Xorg failsafe log

[jerrylamos (jerrylamos)]

.xsession-errors.old

Can't open display :0
Can't open display :0
Can't open display :0
xrdb: Connection refused
xrdb: Can't open display ':0'
xhost: unable to open display ":0"
xhost: unable to open display ":0"
Script for cjkv started at run_im.
Script for default started at run_im.
init: unity-panel-service main process (2685) terminated with status 1
init: unity-panel-service main process ended, respawning
init: gnome-settings-daemon main process (2675) terminated with status 1
init: gnome-settings-daemon main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: unity-panel-service main process (2697) terminated with status 1
init: unity-panel-service main process ended, respawning
init: gnome-settings-daemon main process (2699) terminated with status 1
init: gnome-settings-daemon main process ended, respawning
init: unity-panel-service main process (2704) terminated with status 1
init: unity-panel-service main process ended, respawning
init: gnome-session main process (2682) terminated with status 1
init: gnome-settings-daemon main process (2706) terminated with status 1
init: gnome-settings-daemon main process ended, respawning

[jerrylamos (jerrylamos)]

.xsession-errors

Maybe this is from the boot in recovery mode?

xrandr: Failed to get size of gamma for output default
xrandr: Failed to get size of gamma for output default
xrandr: cannot find output "VGA-0"
xrandr: Failed to get size of gamma for output default
warning: output VGA-0 not found; ignoring
Script for cjkv started at run_im.
Script for default started at run_im.

[Daniel van Vugt (vanvugt)]

Apparently radeon support was much improved this past day or so. Can you please purge all PPAs, update and retest?

[jerrylamos (jerrylamos)]

Re-installed 13.10 (running nicely for U+1, thanks), no problems with X or graphics at all.

Put in mir ppa and got the same bug, black screen, Ctrl-Alt-F1 wouldn't even work.

Booted in recovery mode which is how it is running now, usable but crippled:

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 800 x 600, current 1152 x 864, maximum 1152 x 864
default connected primary 1152x864+0+0 0mm x 0mm
   1152x864 0.0*
   1024x768 0.0
   800x600 61.0

Actual notebook screen 1366x768
external vga monitor 1600x900

.

[jerrylamos (jerrylamos)]

.xsession-errors after booting in recovery mode:
Script for cjkv started at run_im.
Script for default started at run_im.
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd respawning too fast, stopped

VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310]

[jerrylamos (jerrylamos)]

nomodeset boots same as recovery, settings only sees a "built in display" actually this external monitor, actual built in monitor black. xrandr as above.

[Kai Mast (kai-mast)]

Is my issue maybe a duplicate of this bug?
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1219081

[Daniel van Vugt (vanvugt)]

Could you please:

1. Reproduce the bug.
2. Switch to VT 1: Ctrl+Alt+F1
3. cp /var/log/lightdm/unity-system-compositor.log /tmp/
4. Attach unity-system-compositor.log to this bug?

I suspect this might actually be bug 1206633.

[Till Kamppeter (till-kamppeter)]

I do not know whether it is the same problem, as I have Intel graphics (Lenovo Thinkpad Twist, Intel Core i7) but I also get a black screen when booting with an external monitor connected. During boot I have to disconnect the monitor to get a login screen. After logging in I can connect the monitor and use it as extended desktop.

[jerrylamos (jerrylamos)]

Daniel, can't quite get what you want. Ctrl-Alt-F1 gets nothing. Dead.
Now if I delete quiet splash it comes up in "low graphics mode" and I can get Ctrl-Alt-F1, attached is unity-system-compositor.log

If I then do
sudo service lightdm start
screen goes black,
do Ctrl-Alt-F1 message is job failed to start.

I also have unity...logs from recovery mode and nomodeset and after lightdm start attempt

All the while the built in screen is totally black. Let me try disconnecting the external monitor which is the only one working but in some intermediate resolution. Should be 1600x900.

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 800 x 600, current 1152 x 864, maximum 1152 x 864
default connected primary 1152x864+0+0 0mm x 0mm
   1152x864 0.0*
   1024x768 0.0
   800x600 61.0

[jerrylamos (jerrylamos)]

Acer Aspire 5253 wide screen notebook,
Aspire-5253:~$ sudo lshw -C display
  *-display UNCLAIMED
       description: VGA compatible controller
       product: Wrestler [Radeon HD 6310]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 1
       bus info: pci@0000:00:01.0
       version: 00
       width: 32 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:80000000-8fffffff ioport:4000(size=256) memory:90400000-9043ffff

tried booting with no external monitor.
black. Nothing. Dead, no Ctrl-Alt-F1.
Boot with quiet splash removed comes up in "low graphics mode", compositor.log attached.
Try xrandr and get:
Can't open display.

[Daniel van Vugt (vanvugt)]

Jerry,

compositor.log seems to suggest that lightdm isn't even trying to start unity-system-compositor.

While the screen is black, can you please get the list of processes either from a VT or SSH login?...
    ps auxw

Also, please provide /var/log/lightdm/lightdm.log*

[jerrylamos (jerrylamos)]

Daniel, I would if I could, with the screen totally black not even a blinking cursor,
Ctrl+Alt+F1
nothing happens.

I haven't run SSH for years. Let me see if I remember how.

I haven't run VT ever. Any pointers as to how?

Comment #16, booting with quiet splash removed, it comes up in low graphics mode and Ctrl-Alt-F1 does work.
sudo service lightdm start
Job failed to start.

[Daniel van Vugt (vanvugt)]

Sorry, when I say "VT" I mean Ctrl+Alt+F1.

OK, if you can recover at all, then it should be sufficient to copy the *.log.old files from the previous failed boot.

[Kai Mast (kai-mast)]

I couldn't switch TTYs either the last time I tried. Also when using only one screen.

My duplicate also has all the log.old files :)

[jerrylamos (jerrylamos)]

Interesting.
Booted first into black screen. Waited then power off, the only thing that works.
Then booted into recovery mode, unity+mir ppa can't detect the built in notebook screen, and is running the external monitor in reduced resolution.

Looks to me like the black screen logs dated 13:57 are all 0 bytes. Ubuntu must not have started the logs.
There is content in the 13:58 logs.

jerry@Aspire-5253:~/black.old.logs$ ls -l /var/log/lightdm
total 32
-rw------- 1 root root 3143 Sep 5 13:58 lightdm.log
-rw------- 1 root root 0 Sep 5 13:57 lightdm.log.old
-rw------- 1 root root 456 Sep 5 13:58 unity-system-compositor.log
-rw------- 1 root root 0 Sep 5 13:57 unity-system-compositor.log.old
-rw------- 1 root root 2471 Sep 5 13:58 x-0.log
-rw------- 1 root root 0 Sep 5 13:57 x-0.log.old

will attach what there is.

[Daniel van Vugt (vanvugt)]

Thanks Jerry. The unity-system-compositor.log seems to show bug 1206633 so let this be a duplicate of that.

Although this X message might also be related:
(II) [KMS] drm report modesetting isn't supported.