[opensuse] Leap: kscreen problem?
Hi Folks, I have short Leap screen freezes that seem to be correlated with these messages in /var/log/messages: (syslog-ng installed) May 4 14:53:26 frog dbus-daemon[30355]: kscreen: Primary output changed from KScreen::Output(Id: 634 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 634 , Name: "DVI-I-1" ) ( "DVI-I-1" ) May 4 14:53:56 frog dbus-daemon: Last message 'kscreen: Primary out' repeated 7 times, suppressed by syslog-ng on frog It seems to happen on an irregular, but frequent basis. This is 42.1 with an Nvidia G96GL [Quadro FX 580] frame buffer. Anyone else seeing this? Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Lew Wolfgang composed on 2016-05-04 15:11 (UTC-0700):
I have short Leap screen freezes that seem to be correlated with these messages in /var/log/messages: (syslog-ng installed)
May 4 14:53:26 frog dbus-daemon[30355]: kscreen: Primary output changed from KScreen::Output(Id: 634 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 634 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 4 14:53:56 frog dbus-daemon: Last message 'kscreen: Primary out' repeated 7 times, suppressed by syslog-ng on frog
It seems to happen on an irregular, but frequent basis.
This is 42.1 with an Nvidia G96GL [Quadro FX 580] frame buffer.
Anyone else seeing this?
jdd reported this here 16 hours ago: https://lists.opensuse.org/opensuse/2016-05/msg00044.html If I've seen it using NVidia/nouveau I can't recall. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/04/2016 03:37 PM, Felix Miata wrote:
Lew Wolfgang composed on 2016-05-04 15:11 (UTC-0700):
I have short Leap screen freezes that seem to be correlated with these messages in /var/log/messages: (syslog-ng installed)
May 4 14:53:26 frog dbus-daemon[30355]: kscreen: Primary output changed from KScreen::Output(Id: 634 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 634 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 4 14:53:56 frog dbus-daemon: Last message 'kscreen: Primary out' repeated 7 times, suppressed by syslog-ng on frog
It seems to happen on an irregular, but frequent basis.
This is 42.1 with an Nvidia G96GL [Quadro FX 580] frame buffer.
Anyone else seeing this?
jdd reported this here 16 hours ago: https://lists.opensuse.org/opensuse/2016-05/msg00044.html
If I've seen it using NVidia/nouveau I can't recall.
This seems to stop the log-flooding, but the pauses are still there. From https://bugs.kde.org/show_bug.cgi?id=355928 "As mention I do not see this message in the system logs on Plasma 5.4.3 (KDE Applications 15.08.3.). Though I could get the message on the command line when running kscreen-console. I could also stop the message by creating ~/.config/QtProject/qtlogging.ini and adding:" [Rules] kscreen.debug=false "I am guessing if upgrading again to Plasma 5.5.3 (KDE’s Frameworks 5.18.0) the log messages could be turned of by adding the qtlogging.ini change above to the /etc/xdg/QtProject/ directory." Both locations worked for me, but tiny pauses/lags still there. Maybe I'll hold off a bit rolling Leap out to my users? Maybe try another frame buffer? Pauses when you're typing aren't good for confidence building and morale. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Lew Wolfgang composed on 2016-05-04 16:15 (UTC-0700):
Maybe I'll hold off a bit rolling Leap out to my users?
Are they all Nouveau users?
Maybe try another frame buffer?
Try another driver? Apparently it's little known that chip-specific Xorg video drivers have had a viable alternative for quite some time, the modeset driver built right into Xorg itself. The simplest way to test is 'zypper rm xf86-video-[ati,intel,nouveau]' and restart X. If it doesn't work, or doesn't work as well, just s/rm/in/ and rerun zypper. The only way to tell if modeset works as well or better or at all is to try and see. Not all gfxchips are supported by Xorg's modeset, but it's target audience is non-ancient chips. It's likely a waste of time to try it if the gfxchip is more than around 8-9 years old, or not as old as 42.1 is itself minus around 4-6 months. If pressed by poor performance, 42.1 can be upgraded to the more current Xorg version in BS for newer gfxchips. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/04/2016 04:41 PM, Felix Miata wrote:
Lew Wolfgang composed on 2016-05-04 16:15 (UTC-0700):
Maybe I'll hold off a bit rolling Leap out to my users?
Are they all Nouveau users?
They are mostly Nvidia equipped, maybe one or two Intel. We usually use the proprietary Nvidia drivers if for no other reason than they control the fans. I forgot to mention that I used the Nvidia repo on the subject Leap system. It loaded NVIDIA-Linux-x86_64-340.96.
Maybe try another frame buffer?
Try another driver? Apparently it's little known that chip-specific Xorg video drivers have had a viable alternative for quite some time, the modeset driver built right into Xorg itself. The simplest way to test is 'zypper rm xf86-video-[ati,intel,nouveau]' and restart X. If it doesn't work, or doesn't work as well, just s/rm/in/ and rerun zypper. The only way to tell if modeset works as well or better or at all is to try and see. Not all gfxchips are supported by Xorg's modeset, but it's target audience is non-ancient chips. It's likely a waste of time to try it if the gfxchip is more than around 8-9 years old, or not as old as 42.1 is itself minus around 4-6 months. If pressed by poor performance, 42.1 can be upgraded to the more current Xorg version in BS for newer gfxchips.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Lew Wolfgang
On 05/04/2016 04:41 PM, Felix Miata wrote:
Lew Wolfgang composed on 2016-05-04 16:15 (UTC-0700):
Maybe I'll hold off a bit rolling Leap out to my users?
Are they all Nouveau users?
They are mostly Nvidia equipped, maybe one or two Intel. We usually use the proprietary Nvidia drivers if for no other reason than they control the fans.
I forgot to mention that I used the Nvidia repo on the subject Leap system. It loaded NVIDIA-Linux-x86_64-340.96.
364.19 is available, maybe try it.... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/04/2016 05:30 PM, Patrick Shanahan wrote:
* Lew Wolfgang
[05-04-16 20:28]: Lew Wolfgang composed on 2016-05-04 16:15 (UTC-0700):
Maybe I'll hold off a bit rolling Leap out to my users? Are they all Nouveau users? They are mostly Nvidia equipped, maybe one or two Intel. We usually use the proprietary Nvidia drivers if for no other reason
On 05/04/2016 04:41 PM, Felix Miata wrote: than they control the fans.
I forgot to mention that I used the Nvidia repo on the subject Leap system. It loaded NVIDIA-Linux-x86_64-340.96. 364.19 is available, maybe try it....
Nvidia's web site didn't list that version for the Quadro FX 580. But I'll give it a try. What could possibly go wrong? :-) Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 05/05/2016 01:15, Lew Wolfgang a écrit :
On 05/04/2016 03:37 PM, Felix Miata wrote:
jdd reported this here 16 hours ago: https://lists.opensuse.org/opensuse/2016-05/msg00044.html
From https://bugs.kde.org/show_bug.cgi?id=355928
"As mention I do not see this message in the system logs on Plasma 5.4.3 (KDE Applications 15.08.3.). Though I could get the message on the command line when running kscreen-console. I could also stop the message by creating ~/.config/QtProject/qtlogging.ini and adding:"
[Rules] kscreen.debug=false
using this remove the error message, but not the crash. but may be wht looks like a crash is only a cpu full use. After making the modif, I launched the webgl page on firefox and the system crashed almost instantly, I not even had time to go to the journald -f xterm window, but I could still see some mouse cursor movement of course, nothing on the logs after reboot... jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 05/05/2016 09:12, jdd a écrit :
but may be wht looks like a crash is only a cpu full use.
the webgl page add more than 50% cpu load (top dixit) in Firefox, half this with Konqueror (low end i5) the curious is than this load is achieved without moving the mouse I recall the page url (warning: beware the dog, it's the page that makes me crash) http://dodin.org/temp/pano/pano.html notice in Firefox widows 7 - intel driver, no crash page is made with jquery-2.2.3.min.js and three.min.js (and html and css) is there a way to lower the cpu load from the code? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd composed on 2016-05-05 09:12 (UTC+0200):
Lew Wolfgang composed:
[Rules] kscreen.debug=false
using this remove the error message, but not the crash.
If using only a single display, try this addition to kded5rc: [Module-kscreen] autoload=false If using more than one display with kscreen disabled, you'll need to configure your screens with xrandr or xorg.conf*. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 05/05/2016 09:43, Felix Miata a écrit :
If using only a single display
yes , try this addition to kded5rc:
[Module-kscreen] autoload=false
If using more than one display with kscreen disabled, you'll need to configure your screens with xrandr or xorg.conf*.
I don't find any kde5rc jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd composed on 2016-05-05 09:47 (UTC+0200):
Felix Miata composed:
...try this addition to kded5rc:
[Module-kscreen] autoload=false
I don't find any kde5rc
Try ~/.config/kded5rc or maybe??? ~/.config/kdedrc If neither exists, create kded5rc. (but it should be there) -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 05/05/2016 09:57, Felix Miata a écrit :
or maybe???
~/.config/kdedrc
I have this one, with only: [$Version] update_info=kded.upd:kde3.0 I added your line thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 05/05/2016 11:09, jdd a écrit :
Le 05/05/2016 09:57, Felix Miata a écrit :
or maybe???
~/.config/kdedrc
I have this one, with only:
[$Version] update_info=kded.upd:kde3.0
I added your line
thanks jdd
and since, no more crashes, I cross my fingers :-)) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/05/2016 12:43 AM, Felix Miata wrote:
jdd composed on 2016-05-05 09:12 (UTC+0200):
Lew Wolfgang composed:
[Rules] kscreen.debug=false
using this remove the error message, but not the crash.
If using only a single display, try this addition to kded5rc:
[Module-kscreen] autoload=false
If using more than one display with kscreen disabled, you'll need to configure your screens with xrandr or xorg.conf*.
This doesn't seem to help the screen latency issue in my case. I'll try a more modern graphics adapter and report back. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/05/2016 11:08 AM, Lew Wolfgang wrote:
On 05/05/2016 12:43 AM, Felix Miata wrote:
jdd composed on 2016-05-05 09:12 (UTC+0200):
Lew Wolfgang composed:
[Rules] kscreen.debug=false
using this remove the error message, but not the crash.
If using only a single display, try this addition to kded5rc:
[Module-kscreen] autoload=false
If using more than one display with kscreen disabled, you'll need to configure your screens with xrandr or xorg.conf*.
This doesn't seem to help the screen latency issue in my case. I'll try a more modern graphics adapter and report back.
I picked up a PNY GeForce GT 730 this morning and the system is running smoother than snails through a goose now! The freezes and rendering errors are all gone. Thanks to everyone for their help and suggestions. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Felix Miata
-
jdd
-
Lew Wolfgang
-
Patrick Shanahan