2017-01-16 12:13 GMT+01:00 Bruno Friedmann:

On lundi, 16 janvier 2017 11.39:57 h CET René Krell wrote:

...

Additionally to the reported issues with this snapshot I have these two on a HP ZBook 15 G2 notebook, running kernel 4.9.0_2 from the TW update repository:

... Did anyone notice something similar? Any analyze or solution out there?

I've a quatro M2000M working greatly with 375.26 nvidia drivers with 4.9.0 and xserver 1.19.

Is this a system with Hybrid Graphics (Intel/NVidia)? If yes, have you activated this feature? After a look to the kernel changes logs after 4.9.0 I saw there has been also alot of i915 driver fixes, which is always loaded here beside the according driver for the NVidia chipset. I tried to set Hybrid Graphics to Auto and Enabled (I have always needed one of these two settings to activate a secondary. external DVI display. But I cannot see any bigger issue in /var/log/messages so far with the current kernel. René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

I have a similar issue. Although I'm not experiencing any delays, I lost my 3 monitor setup. 2 monitors are connected on on Radeon GPU and another one on a second Radeon GPU. The second GPU is not activated at all (although during boot it is initialized). 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 250/350] 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] xrandr -q Screen 0: minimum 320 x 200, current 3200 x 1080, maximum 16384 x 16384 HDMI-0 connected 1280x1024+1920+0 (normal left inverted right x axis y axis) 341mm x 274mm 1280x1024 60.02 + 75.02* 1280x960 60.00 1152x864 75.00 1024x768 75.03 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 640x480 75.00 72.81 66.67 59.94 720x400 70.08 DVI-0 disconnected (normal left inverted right x axis y axis) VGA-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm 1920x1080 60.00*+ 1680x1050 59.95 1400x1050 59.98 1600x900 60.00 1280x1024 75.02 60.02 1440x900 59.89 1280x800 59.81 1152x864 75.00 1280x720 60.00 1024x768 75.03 60.00 800x600 75.00 60.32 640x480 75.00 59.94 720x400 70.08 No third screen is displayed Complete xorg.log here: https://paste.opensuse.org/86455566 I cannot find something there but maybe someone more experienced can. On Mon, Jan 16, 2017 at 2:12 PM, Bruno Friedmann wrote:

On lundi, 16 janvier 2017 12.38:32 h CET René Krell wrote:

...

2017-01-16 12:13 GMT+01:00 Bruno Friedmann:

...

On lundi, 16 janvier 2017 11.39:57 h CET René Krell wrote:

...

Additionally to the reported issues with this snapshot I have these two on a HP ZBook 15 G2 notebook, running kernel 4.9.0_2 from the TW update repository:

... Did anyone notice something similar? Any analyze or solution out there?

I've a quatro M2000M working greatly with 375.26 nvidia drivers with 4.9.0 and xserver 1.19.

Is this a system with Hybrid Graphics (Intel/NVidia)? If yes, have you activated this feature? Nope due to the too much limitation of intel gpu (number and treatment of external display). I admit I a fan of nvidia. I choose carefully my hardware to be able to only run nvidia chipset. After a look to the kernel changes logs after 4.9.0 I saw there has been also alot of i915 driver fixes, which is always loaded here beside the according driver for the NVidia chipset. I tried to set Hybrid Graphics to Auto and Enabled (I have always needed one of these two settings to activate a secondary. external DVI display. But I cannot see any bigger issue in /var/log/messages so far with the current kernel. var/log/messages ? you mean journalctl René

--

Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 16/01/17 02:55 PM, Felix Miata wrote:

Preferred FOSS Xorg drivers have been transitioning[1] from discrete gfxchip-specific to the generic modesetting driver that was moved from a separate package directly into Xorg back in server 1.17. You might try uninstalling the AMD/ATI/Radeon driver (xf86-video-ati)

[1] https://lists.opensuse.org/opensuse-factory/2017-01/msg00163.html

While the modesetting driver should work (and most certainly does for me), do note the recently expressed opinion on what the "preferred" DDX for AMD GPUs is: https://lwn.net/Articles/704883/

see if automatic use of the third display is restored

It won't be. Stratos is mistaken -- it is still the case that, with 2 GPUs, you manually (or some configuration utility) must bridge the two together via "xrandr --setprovideroutputsource displays renders" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Monday, 16 January 2017 12:18:43 GMT stakanov wrote:

In data lunedì 16 gennaio 2017 11:39:57, René Krell ha scritto:

...

Additionally to the reported issues with this snapshot I have these two on a HP ZBook 15 G2 notebook, running kernel 4.9.0_2 from the TW update repository:

1. Plasma desktop does sometimes hang during startup, I see the message "Yakuake started" at the beginning, but no widget, just the empty background. In this situation, when trying to reboot, the shutdown hangs on a task I haven't still identified for about one and a half minute, systemd shuts it down probably forcibly after this time.

To exclude a driver problem I tried this in these variants: - nouveau (with Mesa-dri-nouveau installed) - nouveau (no Mesa-dri-nouveau installed) - nvidia native 375.20 (nouveau blacklisted) The effect is always the same, there seems not to be a problem with a graphics driver.

2. A second display connected to the docking station stopped working, it doesn't even wake up neither during booting nor after Plasma has been started. The second display isn't even recognized according to the Plasma desktop settings, there is just the laptop display present. This has been still working with the update state of last friday (20170110).

Did anyone notice something similar? Any analyze or solution out there?

René

I do not know if this is related. I am on a Nouveau Nividia System. Also with me plasma freezes from time to time (it seems related with sound and / or video but I am by no means sure). Kaffeine tends to freeze/lockup when using pause during dvb-t. Amarok locks up when using a lot pause/start on any mp3 audiofile. When booting the flashpopup when starting kde hangs and has to be killed by hand. This is true even if changing type of animation. It seems the system has also a problem to wake up when it goes into a lower state of consumption. Mouse will still react but the rest of plasma shows no reaction. alt+ctl+del is usually possible with end of session. When logging in again everything seems to work. I get the same thing on login. I have to ctrl backspace backspace to kill the login and then i can login okay. Definitely something wrong in this release

-- opensuse:tumbleweed:20170112 Qt: 5.7.1 KDE Frameworks: 5.30.0 KDE Plasma: 5.8.95 kwin5-5.8.95-174.1.x86_64 Kernel: 4.9.0-2-default Nouveau: 1.0.13_2.2 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

2017-01-16 12:45 GMT+01:00 Vojtěch Zeisek:

Dne pondělí 16. ledna 2017 11:39:57 CET, René Krell napsal(a):

...

1. Plasma desktop does sometimes hang during startup, I see the message "Yakuake started" at the beginning, but no widget, just the

For me, Plasma sometimes takes relatively long time to start, Yakuake is already running, other background services also, but I don't see desktop. After ~15 seconds of waiting (Isn't it bit long for SSD?) everything runs normally.

...

empty background. In this situation, when trying to reboot, the shutdown hangs on a task I haven't still identified for about one and a half minute, systemd shuts it down probably forcibly after this time.

Reboot/shutdown takes extraordinary long time. If I press Esc to see the log messages. It seems the most of the time is consumed by unmounting of /var/log which finally fails (if I see correctly), then it scrolls quickly with bunch of unspecific errors. Apart this, everything seems to be working fine.

These two comments sound very similar to the issues I've noticed. Haven't just analyzed them more deeply.

...

To exclude a driver problem I tried this in these variants: - nouveau (with Mesa-dri-nouveau installed) - nouveau (no Mesa-dri-nouveau installed) - nvidia native 375.20 (nouveau blacklisted) The effect is always the same, there seems not to be a problem with a graphics driver.

I'm on Intel graphic card.

...

2. A second display connected to the docking station stopped working, it doesn't even wake up neither during booting nor after Plasma has been started. The second display isn't even recognized according to the Plasma desktop settings, there is just the laptop display present. This has been still working with the update state of last friday (20170110).

It works well for me, using HDMI as well as VGA. Two full HD monitors. No problem.

This won't be probably a Hybrid Graphics system (Intel/NVidia) with Optimus support. I've always loaded two graphical drivers in parallel, i915 and nouveau (or nvidia instead of nouveau). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Montag, 16. Januar 2017 12:45:56 CET Vojtěch Zeisek wrote:

Dne pondělí 16. ledna 2017 11:39:57 CET, René Krell napsal(a):

...

1. Plasma desktop does sometimes hang during startup, I see the message "Yakuake started" at the beginning, but no widget, just the

For me, Plasma sometimes takes relatively long time to start, Yakuake is already running, other background services also, but I don't see desktop. After ~15 seconds of waiting (Isn't it bit long for SSD?) everything runs normally.

The same is here already for some time. During start-up the system take some seconds (perhaps 5-8) to finally show the KDE desktop. In the meantime the openSUSE bulb is shown and the yakuake-popup is shown shortly. Cheers, Robby. --

I managed to fix my issue as follows: 1. I disabled kscreen so I can manage the monitor setup manually with xrandr. 2. I enabled the second GPU with xrandr --setprovideroutputsource 1 0 3. Fixed my layout with xrandr --output VGA-0 --primary --mode 1920x1080 --pos 1280x0 --rotate normal --output DVI-1-1 --off --output HDMI-1-1 --off --output VGA-1-1 --mode 1280x1024 --pos 0x0 --rotate normal --output HDMI-0 --mode 1280x1024 --pos 3200x0 --rotate normal --output DVI-0 --off 4. Added a script on pre KDE startup to perform the above both commands. Although it works, the secondary GPU should be enabled (if it has a monitor connected) by default and not need to be forced. I have updated also the upstream bug because it is not the expected behavior. Stratos. On Mon, Jan 16, 2017 at 4:26 PM, Stratos Zolotas wrote:

Did a little more research...

My secondary GPU is detected (as it seems from Xorg.0.log) and the output of

xrandr --listproviders Providers: number : 2 Provider 0: id: 0x9a cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 3 associated providers: 0 name:OLAND @ pci:0000:01:00.0 Provider 1: id: 0x54 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 3 associated providers: 0 name:OLAND @ pci:0000:02:00.0

but I cannot enable it. It is not listed (even disabled) on kscreen or arandr. I tried to remove everything from /etc/X11/xorg.conf.d/ to force autodetection without any luck.

I opened a bug here: https://bugs.freedesktop.org/show_bug.cgi?id=99427 in case it is an upstream issue but any advice would be helpful in case this is has to do with any configuration, although before the upgrade to X 1.19 all 3 monitors were working as expected. The third monitor is waking up during boot but stops working as soon as X comes up and doesn't work after login also.

On Mon, Jan 16, 2017 at 3:07 PM, Robert Kaiser wrote:

...

René Krell schrieb:

...

1. Plasma desktop does sometimes hang during startup, I see the message "Yakuake started" at the beginning, but no widget, just the empty background. In this situation, when trying to reboot, the shutdown hangs on a task I haven't still identified for about one and a half minute, systemd shuts it down probably forcibly after this time.

For me, on my main desktop computer (Intel SandyBridge graphics), which has a secondary display, plasma doesn't come up fully at all, the startup screen (on the primary display) frezees and never goes away, while on the secondary screen, things seems kinda usable but I don't have any widgets or anything there. As I still use KDM there, I could select a "Plasma Workspace (failsafe session)" at login, which seems to turn off some gfx freatures ("hardware accelaration" or anything else?) and that seems to work fine for now. So I suspect the X update or something regarding Mesa is involved in this issue.

On my laptop (IvyBridge), the plasma workspace comes up fine but the plasmashell (task bar, desktop, etc.) freezes sometimes and gets unusable but as I use SDDM already there I don't have failsafe mode available as a selection unfortunately, so I can't try if that helps there as well.

KaiRo

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Robert Kaiser schrieb:

For me, on my main desktop computer (Intel SandyBridge graphics), which has a secondary display, plasma doesn't come up fully at all, the startup screen (on the primary display) frezees and never goes away, while on the secondary screen, things seems kinda usable but I don't have any widgets or anything there. As I still use KDM there, I could select a "Plasma Workspace (failsafe session)" at login, which seems to turn off some gfx freatures ("hardware accelaration" or anything else?) and that seems to work fine for now.

FWIW, this is all back to working normally with the standard Plasma Workspace session with effects enabled, now that I have X.org server 1.19.1 installed. Thanks for delivering that pretty fast! Cheers, KaiRo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org