[opensuse-factory] Qtwebengine & nouveau - aagghhhh -
Hi To save my sanity, is there a way, in tumbleweed, to either 1. Restore kdepim to 5.2.x to get rid of reliance on qtwebengine 2. Install nvidia and lock kernel/nvidia from updates? 3. Any other solution that still uses kmail/kontact. For me, kmail stays alive for a few seconds or upto a minute or two. If i can get kmail up long enough to write/reply to an email, its doesn't crash. It all seems to be happening when clicking on a new folder or email to read and sometimes it just crashes when left alone for a while. This bug report seems to point to a threading issue - https:// bugzilla.opensuse.org/show_bug.cgi?id=997171 Regards Ian -- opensuse:tumbleweed:20160927 Qt: 5.6.1 KDE Frameworks: 5.26.0 KDE Plasma: 5.7.95 kwin5-5.7.95-155.1.x86_64 kmail5-16.08.1-1.1.x86_64 Kernel: 4.7.4-2-default Nouveau: 1.0.13_1.1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2016-09-29 13:05 GMT+02:00 ianseeks <bingmybong@btinternet.com>:
Hi
To save my sanity, is there a way, in tumbleweed, to either 1. Restore kdepim to 5.2.x to get rid of reliance on qtwebengine 2. Install nvidia and lock kernel/nvidia from updates? 3. Any other solution that still uses kmail/kontact.
For me, kmail stays alive for a few seconds or upto a minute or two. If i can get kmail up long enough to write/reply to an email, its doesn't crash. It all seems to be happening when clicking on a new folder or email to read and sometimes it just crashes when left alone for a while.
This bug report seems to point to a threading issue - https:// bugzilla.opensuse.org/show_bug.cgi?id=997171
Regards
Ian
In the changelog of TW 20160927 I noticed the update of xf86-video-nouveau to 1.0.13 and therefore removed the nvidia proprietary driver and retried nouveau (as many times before). This time, Plasma desktop runs very stable with nouveau on my hardware (HP ZBook 15 G2), in difference to the hangs and crashes several weeks and months before. For me it seems the KMail issue is currently the only critical issue. That's why I'd rather go on, reporting but not blocking so much things from being updated. I just see things are changing (something gets worse and something better). I'm aware of the fact that it is Tumbleweed and not recommended for production use :-) René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 29 September 2016 13:15:04 BST René Krell wrote:
2016-09-29 13:05 GMT+02:00 ianseeks <bingmybong@btinternet.com>:
Hi
To save my sanity, is there a way, in tumbleweed, to either 1. Restore kdepim to 5.2.x to get rid of reliance on qtwebengine 2. Install nvidia and lock kernel/nvidia from updates? 3. Any other solution that still uses kmail/kontact.
For me, kmail stays alive for a few seconds or upto a minute or two. If i can get kmail up long enough to write/reply to an email, its doesn't crash. It all seems to be happening when clicking on a new folder or email to read and sometimes it just crashes when left alone for a while.
This bug report seems to point to a threading issue - https:// bugzilla.opensuse.org/show_bug.cgi?id=997171
Regards
Ian
In the changelog of TW 20160927 I noticed the update of xf86-video-nouveau to 1.0.13 and therefore removed the nvidia proprietary driver and retried nouveau (as many times before). This time, Plasma desktop runs very stable with nouveau on my hardware (HP ZBook 15 G2), in difference to the hangs and crashes several weeks and months before. For me it seems the KMail issue is currently the only critical issue.
That's why I'd rather go on, reporting but not blocking so much things from being updated. I just see things are changing (something gets worse and something better). I'm aware of the fact that it is Tumbleweed and not recommended for production use :-)
René
Kmail has my only issue, i had no problems anywhere else apart from the odd desktop freeze where i had to physically reboot. i've got the new nouveau too and its still happening to kmail, crashes are not the only thing with kmail, it sometimes goes up to 50% CPU usage for a long time and it sometimes recovers from that. I wouldn't use tumbleweed for production either. -- opensuse:tumbleweed:20160927 Qt: 5.6.1 KDE Frameworks: 5.26.0 KDE Plasma: 5.7.95 kwin5-5.7.95-155.1.x86_64 kmail5-16.08.1-1.1.x86_64 Kernel: 4.7.4-2-default Nouveau: 1.0.13_1.1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On jeudi, 29 septembre 2016 13.15:04 h CEST René Krell wrote:
I'm aware of the fact that it is Tumbleweed and not recommended for production use :-)
This is a sentence that is not validated with facts. so it should be enclosed by sarcasm tags, or better simply avoided ;-) -- 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
* Bruno Friedmann <bruno@ioda-net.ch> [09-29-16 08:25]:
On jeudi, 29 septembre 2016 13.15:04 h CEST René Krell wrote:
I'm aware of the fact that it is Tumbleweed and not recommended for production use :-)
This is a sentence that is not validated with facts. so it should be enclosed by sarcasm tags, or better simply avoided ;-)
Definitely! -- (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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
ianseeks composed on 2016-09-29 12:05 (UTC+0100):
To save my sanity, is there a way, in tumbleweed, to either 1. Restore kdepim to 5.2.x to get rid of reliance on qtwebengine 2. Install nvidia and lock kernel/nvidia from updates?
# zypper al kernel-d* # zypper al nvidiadriverpackagenamewhateveritisthatIneveruse
3. Any other solution that still uses kmail/kontact.
For me, kmail stays alive for a few seconds or upto a minute or two. If i can get kmail up long enough to write/reply to an email, its doesn't crash. It all seems to be happening when clicking on a new folder or email to read and sometimes it just crashes when left alone for a while.
This bug report seems to point to a threading issue - https:// bugzilla.opensuse.org/show_bug.cgi?id=997171
Try driver #3. Purge both nvidia and nouveau drivers from your installation, and ensure kernel cmdline does not include anything to defeat KMS. The result is the modesetting driver integral to the X server should be used automatically unless your nvidia gfxchip is too new or too old. cf. http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-Intel-DDX -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 29 September 2016 08:08:34 BST Felix Miata wrote:
ianseeks composed on 2016-09-29 12:05 (UTC+0100):
To save my sanity, is there a way, in tumbleweed, to either 1. Restore kdepim to 5.2.x to get rid of reliance on qtwebengine 2. Install nvidia and lock kernel/nvidia from updates?
# zypper al kernel-d* # zypper al nvidiadriverpackagenamewhateveritisthatIneveruse
3. Any other solution that still uses kmail/kontact.
For me, kmail stays alive for a few seconds or upto a minute or two. If i can get kmail up long enough to write/reply to an email, its doesn't crash. It all seems to be happening when clicking on a new folder or email to read and sometimes it just crashes when left alone for a while.
This bug report seems to point to a threading issue - https:// bugzilla.opensuse.org/show_bug.cgi?id=997171
Try driver #3. Purge both nvidia and nouveau drivers from your installation, and ensure kernel cmdline does not include anything to defeat KMS. The result is the modesetting driver integral to the X server should be used automatically unless your nvidia gfxchip is too new or too old.
cf. http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-In tel-DDX
I've got a feeling its too old, GT218 (Geforce 210) Thanks for the info, i'll look into it -- opensuse:tumbleweed:20160927 Qt: 5.6.1 KDE Frameworks: 5.26.0 KDE Plasma: 5.7.95 kwin5-5.7.95-155.1.x86_64 kmail5-16.08.1-1.1.x86_64 Kernel: 4.7.4-2-default Nouveau: 1.0.13_1.1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
ianseeks composed on 2016-09-29 19:35 (UTC+0100):
Felix Miata wrote: ...
Try driver #3. Purge both nvidia and nouveau drivers from your installation, and ensure kernel cmdline does not include anything to defeat KMS. The result is the modesetting driver integral to the X server should be used automatically unless your nvidia gfxchip is too new or too old.
cf. http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-Intel-DDX
I've got a feeling its too old, GT218 (Geforce 210)
Thanks for the info, i'll look into it
modesetting worksforme on TW 20160818: # lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] (rev a2) (prog-if 00 [VGA controller]) # Xorg.0.log excerpts: X.Org X Server 1.18.4 Release Date: 2016-07-19 [ 271.414] X Protocol Version 11, Revision 0 [ 271.415] Build Operating System: openSUSE SUSE LINUX [ 271.416] Current Operating System: Linux big31 4.6.4-2-default #1 SMP PREEMPT Tue Jul 19 09:07:19 UTC 2016 (8f4696b) x86_64 ..... [ 271.451] (II) glamor: OpenGL accelerated X.org driver based. [ 271.516] (II) glamor: EGL version 1.4 (DRI2): [ 271.518] (II) modeset(0): glamor initialized [ 271.529] (II) modeset(0): Output DVI-I-1 has no monitor section [ 271.530] (II) modeset(0): Output HDMI-1 has no monitor section [ 271.557] (II) modeset(0): Output VGA-1 has no monitor section [ 271.575] (II) modeset(0): EDID for output DVI-I-1 [ 271.577] (II) modeset(0): EDID for output HDMI-1 [ 271.604] (II) modeset(0): EDID for output VGA-1 [ 271.604] (II) modeset(0): Manufacturer: LEN Model: a12 Serial#: 16843009 ... -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 29 September 2016 23:56:52 BST Felix Miata wrote:
ianseeks composed on 2016-09-29 19:35 (UTC+0100):
Felix Miata wrote: ...
Try driver #3. Purge both nvidia and nouveau drivers from your installation, and ensure kernel cmdline does not include anything to defeat KMS. The result is the modesetting driver integral to the X server should be used automatically unless your nvidia gfxchip is too new or too old.
cf. http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-> >> Intel-DDX> I've got a feeling its too old, GT218 (Geforce 210)
Thanks for the info, i'll look into it
modesetting worksforme on TW 20160818:
# lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] (rev a2) (prog-if 00 [VGA controller])
# Xorg.0.log excerpts:
X.Org X Server 1.18.4 Release Date: 2016-07-19 [ 271.414] X Protocol Version 11, Revision 0 [ 271.415] Build Operating System: openSUSE SUSE LINUX [ 271.416] Current Operating System: Linux big31 4.6.4-2-default #1 SMP PREEMPT Tue Jul 19 09:07:19 UTC 2016 (8f4696b) x86_64 ..... [ 271.451] (II) glamor: OpenGL accelerated X.org driver based. [ 271.516] (II) glamor: EGL version 1.4 (DRI2): [ 271.518] (II) modeset(0): glamor initialized [ 271.529] (II) modeset(0): Output DVI-I-1 has no monitor section [ 271.530] (II) modeset(0): Output HDMI-1 has no monitor section [ 271.557] (II) modeset(0): Output VGA-1 has no monitor section [ 271.575] (II) modeset(0): EDID for output DVI-I-1 [ 271.577] (II) modeset(0): EDID for output HDMI-1 [ 271.604] (II) modeset(0): EDID for output VGA-1 [ 271.604] (II) modeset(0): Manufacturer: LEN Model: a12 Serial#: 16843009 ... Thanks Felix
-- opensuse:tumbleweed:20160927 Qt: 5.6.1 KDE Frameworks: 5.26.0 KDE Plasma: 5.7.95 kwin5-5.7.95-155.1.x86_64 kmail5-16.08.1-1.1.x86_64 Kernel: 4.7.4-2-default Nouveau: 1.0.13_1.1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
ianseeks composed on 2016-09-30 08:30 (UTC+0100):
Felix Miata wrote:
ianseeks composed on 2016-09-29 19:35 (UTC+0100):
Felix Miata wrote: ...
Try driver #3. Purge both nvidia and nouveau drivers from your installation, and ensure kernel cmdline does not include anything to defeat KMS. The result is the modesetting driver integral to the X server should be used automatically unless your nvidia gfxchip is too new or too old.
cf. http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-> >> Intel-DDX>
I've got a feeling its too old, GT218 (Geforce 210)
Thanks for the info, i'll look into it
modesetting worksforme on TW 20160818:
# lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] (rev a2) (prog-if 00 [VGA controller]) ... Thanks Felix
Did using modesetting change anything? -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 09/29/2016 02:35 PM, ianseeks wrote:
On Thursday, 29 September 2016 08:08:34 BST Felix Miata wrote:
ianseeks composed on 2016-09-29 12:05 (UTC+0100):
To save my sanity, is there a way, in tumbleweed, to either 1. Restore kdepim to 5.2.x to get rid of reliance on qtwebengine 2. Install nvidia and lock kernel/nvidia from updates?
# zypper al kernel-d* # zypper al nvidiadriverpackagenamewhateveritisthatIneveruse
3. Any other solution that still uses kmail/kontact.
For me, kmail stays alive for a few seconds or upto a minute or two. If i can get kmail up long enough to write/reply to an email, its doesn't crash. It all seems to be happening when clicking on a new folder or email to read and sometimes it just crashes when left alone for a while.
This bug report seems to point to a threading issue - https:// bugzilla.opensuse.org/show_bug.cgi?id=997171
Try driver #3. Purge both nvidia and nouveau drivers from your installation, and ensure kernel cmdline does not include anything to defeat KMS. The result is the modesetting driver integral to the X server should be used automatically unless your nvidia gfxchip is too new or too old.
cf. http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-In tel-DDX
I've got a feeling its too old, GT218 (Geforce 210)
Thanks for the info, i'll look into it
I shop for cards on closeout, that way I can get a newer card for less then 1/4 of the original price. But then I don't play games that require high end graphics. -- Ken linux since 1994 S.u.S.E./openSUSE since 1996 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 29 September 2016 08:08:34 BST Felix Miata wrote:
ianseeks composed on 2016-09-29 12:05 (UTC+0100):
To save my sanity, is there a way, in tumbleweed, to either 1. Restore kdepim to 5.2.x to get rid of reliance on qtwebengine 2. Install nvidia and lock kernel/nvidia from updates?
# zypper al kernel-d* # zypper al nvidiadriverpackagenamewhateveritisthatIneveruse
3. Any other solution that still uses kmail/kontact.
For me, kmail stays alive for a few seconds or upto a minute or two. If i can get kmail up long enough to write/reply to an email, its doesn't crash. It all seems to be happening when clicking on a new folder or email to read and sometimes it just crashes when left alone for a while.
This bug report seems to point to a threading issue - https:// bugzilla.opensuse.org/show_bug.cgi?id=997171
Try driver #3. Purge both nvidia and nouveau drivers from your installation, and ensure kernel cmdline does not include anything to defeat KMS. The result is the modesetting driver integral to the X server should be used automatically unless your nvidia gfxchip is too new or too old.
cf. http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-In tel-DDX
I've got a feeling its too old, GT218 (Geforce 210) Thanks for the info, i'll look into it -- opensuse:tumbleweed:20160927 Qt: 5.6.1 KDE Frameworks: 5.26.0 KDE Plasma: 5.7.95 kwin5-5.7.95-155.1.x86_64 kmail5-16.08.1-1.1.x86_64 Kernel: 4.7.4-2-default Nouveau: 1.0.13_1.1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2016-09-29 14:08 GMT+02:00 Felix Miata <mrmazda@earthlink.net>:
Try driver #3. Purge both nvidia and nouveau drivers from your installation, and ensure kernel cmdline does not include anything to defeat KMS. The result is the modesetting driver integral to the X server should be used automatically unless your nvidia gfxchip is too new or too old.
cf. http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-Intel-DDX
Hi Felix, good hint, haven't even noticed this third way. Nevertheless, I can't get the X modesetting driver working on my Optimus hardware (HP ZBook 15 G2, hybrid graphics Intel/NVidea), whatever setting I choose in BIOS for Hybrid Graphics (Enabled/Disabled/Auto). Maybe this is beyond the scope of this mailing list, but it might be also important to decide how and when to replace nouveau/nv by this built-in modesetting driver. Even if I uninstall xf86-video-nouveau and xf86-video-nv and call mkinitrd the module gets into trouble: [ 13.343] (II) modesetting: Driver for Modesetting Kernel Drivers: kms ... [ 13.361] (WW) Falling back to old probe method for modesetting [ 13.361] (EE) open /dev/dri/card0: No such file or directory ... [ 13.363] (II) UnloadModule: "modesetting" I had no /etc/X11/xorg.conf and no extra kernel parameters at all, just to make sure. Did I miss something? René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2016-09-30 11:11 GMT+02:00 René Krell <renda.krell@gmail.com>:
Nevertheless, I can't get the X modesetting driver working on my Optimus hardware (HP ZBook 15 G2, hybrid graphics Intel/NVidea), whatever setting I choose in BIOS for Hybrid Graphics (Enabled/Disabled/Auto).
Just forgot to mention: I got it working just when disabling Hybrid Graphics in BIOS, but just along with the intel video driver. But I want to activate the NVidia device. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
René Krell composed on 2016-09-30 11:11 (UTC+0200):
2016-09-29 14:08 GMT+02:00 Felix Miata composed:
Try driver #3. Purge both nvidia and nouveau drivers from your installation, and ensure kernel cmdline does not include anything to defeat KMS. The result is the modesetting driver integral to the X server should be used automatically unless your nvidia gfxchip is too new or too old.
cf. http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-Intel-DDX
good hint, haven't even noticed this third way.
Nevertheless, I can't get the X modesetting driver working on my Optimus hardware (HP ZBook 15 G2, hybrid graphics Intel/NVidea), whatever setting I choose in BIOS for Hybrid Graphics (Enabled/Disabled/Auto). Maybe this is beyond the scope of this mailing list, but it might be also important to decide how and when to replace nouveau/nv by this built-in modesetting driver.
I don't think there is yet enough predictability as to which hardware works better with the built-in modesetting driver.
Even if I uninstall xf86-video-nouveau and xf86-video-nv and call mkinitrd the module gets into trouble:
[ 13.343] (II) modesetting: Driver for Modesetting Kernel Drivers: kms ... [ 13.361] (WW) Falling back to old probe method for modesetting [ 13.361] (EE) open /dev/dri/card0: No such file or directory ... [ 13.363] (II) UnloadModule: "modesetting"
I had no /etc/X11/xorg.conf and no extra kernel parameters at all, just to make sure. Did I miss something?
Maybe a key difference between OP's gfx and yours? René Krell composed on 2016-09-30 11:13 (UTC+0200):
Just forgot to mention: I got it working just when disabling Hybrid Graphics in BIOS, but just along with the intel video driver. But I want to activate the NVidia device.
I saw no evidence that the OP was using hybrid gfx. AFAIK, fully functional hybrid video demands special video drivers, Optimus, Bumblebee, Prime, or maybe something else??? -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2016-10-03 12:50 GMT+02:00 Felix Miata <mrmazda@earthlink.net>:
René Krell composed on 2016-09-30 11:11 (UTC+0200):
2016-09-29 14:08 GMT+02:00 Felix Miata composed: ... Nevertheless, I can't get the X modesetting driver working on my Optimus hardware (HP ZBook 15 G2, hybrid graphics Intel/NVidea), whatever setting I choose in BIOS for Hybrid Graphics (Enabled/Disabled/Auto). Maybe this is beyond the scope of this mailing list, but it might be also important to decide how and when to replace nouveau/nv by this built-in modesetting driver.
I don't think there is yet enough predictability as to which hardware works better with the built-in modesetting driver.
Even if I uninstall xf86-video-nouveau and xf86-video-nv and call mkinitrd the module gets into trouble:
[ 13.343] (II) modesetting: Driver for Modesetting Kernel Drivers: kms ... [ 13.361] (WW) Falling back to old probe method for modesetting [ 13.361] (EE) open /dev/dri/card0: No such file or directory ... [ 13.363] (II) UnloadModule: "modesetting"
I had no /etc/X11/xorg.conf and no extra kernel parameters at all, just to make sure. Did I miss something?
Maybe a key difference between OP's gfx and yours?
René Krell composed on 2016-09-30 11:13 (UTC+0200):
Just forgot to mention: I got it working just when disabling Hybrid Graphics in BIOS, but just along with the intel video driver. But I want to activate the NVidia device.
I saw no evidence that the OP was using hybrid gfx. AFAIK, fully functional hybrid video demands special video drivers, Optimus, Bumblebee, Prime, or maybe something else???
Interesting here (on this HP ZBook 15 G2 - Optimus hardware) is the fact that if I set the BIOS option Hybrid Graphics to Enabled, KMail 5 doesn't crash and I don't have to launch it by prepending "LIBGL_ALWAYS_SOFTWARE=1 kmail". But the second display doesn't some sometimes appear (unpredictable). On the other hand, if setting Hybrid Graphics to Auto, Kmail 5 starts to crash in the way described in https://bugs.kde.org/show_bug.cgi?id=369514, but the second display does appear reliably. Disabling Hybrid Graphics means there's just the on-board Intel graphics available, but not NVidia. The NVidia card is a NVIDIA Quadro K610M with 1 GB. In a separate discussion in the Bumblebee project they found out after several tests, that Bumblebee does work for my hardware just if booting from EFI, but not the legacy BIOS like me. See https://github.com/Bumblebee-Project/bbswitch/issues/118. I'll retry migrating to UEFI as soon as I can, maybe this will improve the situation. Otherwise doesn't probably make sense to use any Optimus switcher, because the ACPI table contents are wrong. Anyway, most reliable is still the NVidia proprietary driver (370.28), although there are rendering issues in Plasma desktop and it doesn't use Optimus technology, though. And recompiling after each second update is uncomfortable. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On jeudi, 29 septembre 2016 12.05:40 h CEST ianseeks wrote:
Hi
To save my sanity, is there a way, in tumbleweed, to either 1. Restore kdepim to 5.2.x to get rid of reliance on qtwebengine 2. Install nvidia and lock kernel/nvidia from updates? 3. Any other solution that still uses kmail/kontact.
For me, kmail stays alive for a few seconds or upto a minute or two. If i can get kmail up long enough to write/reply to an email, its doesn't crash. It all seems to be happening when clicking on a new folder or email to read and sometimes it just crashes when left alone for a while.
This bug report seems to point to a threading issue - https:// bugzilla.opensuse.org/show_bug.cgi?id=997171
Regards
Ian
TW + nvidia 367.44 work well here (even with hidpi screen). Then I get a working kmail2/5 -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot openSUSE Tumbleweed Linux 4.7.4-2-default x86_64 GNU/Linux, nvidia: 367.44 Qt: 5.6.1, KDE Frameworks: 5.26.0, Plasma: 5.7.4, kmail2 5.3.0 (QtWebEngine) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 09/29/2016 08:35 PM, ianseeks wrote:
Hi
To save my sanity, is there a way, in tumbleweed, to either 1. Restore kdepim to 5.2.x to get rid of reliance on qtwebengine 2. Install nvidia and lock kernel/nvidia from updates? 3. Any other solution that still uses kmail/kontact.
Option 4 which works reasonably well most of the time is to build the NVIDIA driver with dkms so that it gets automatically rebuilt every kernel update. This approach works well until kernel abi breaks. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adeliade Australia, UTC+9:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On Tuesday, 4 October 2016 17:16:19 BST Simon Lees wrote:
On 09/29/2016 08:35 PM, ianseeks wrote:
Hi
To save my sanity, is there a way, in tumbleweed, to either 1. Restore kdepim to 5.2.x to get rid of reliance on qtwebengine 2. Install nvidia and lock kernel/nvidia from updates? 3. Any other solution that still uses kmail/kontact.
Option 4 which works reasonably well most of the time is to build the NVIDIA driver with dkms so that it gets automatically rebuilt every kernel update. This approach works well until kernel abi breaks. I have since installed NVIDIA and now i've remembered why i installed nouveau instead. When using a browser for a while, i get a recurring intermittent beep from somewhere in the machine which does not go away until i close the browser (and sometimes have to log out) - i can only deduce it a warning from the nvidia GT218 card
-- opensuse:tumbleweed:20160928 Qt: 5.6.1 KDE Frameworks: 5.26.0 KDE Plasma: 5.7.95 kwin5-5.7.95-155.1.x86_64 kmail5-16.08.1-1.1.x86_64 Kernel: 4.7.5-1-default Nouveau: 1.0.13_1.1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
ianseeks composed on 2016-10-04 09:03 (UTC+0100):
I have since installed NVIDIA and now i've remembered why i installed nouveau instead. When using a browser for a while, i get a recurring intermittent beep from somewhere in the machine which does not go away until i close the browser (and sometimes have to log out) - i can only deduce it a warning from the nvidia GT218 card
If the GT218 is one with a fan on its heat sink, could it be that it has a beeper to tell you it's overheating from a dead or filth encrusted fan and/or heat sink and only overheats if using the proprietary driver? How old and what model is that motherboard? Could it and/or the PS have swollen or leaking electrolytic (not polymer) caps (8mm X 13mm or larger cans on motherboard, possibly smaller in the PS) anywhere? If you can take a cover off and face a fan at the GT218 and subsequently the beeping is prevented, then you'll know it's a heat related problem, especially if its heat sink has a fan that doesn't spin when the PC is on. -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, 4 October 2016 04:40:21 BST Felix Miata wrote:
ianseeks composed on 2016-10-04 09:03 (UTC+0100):
I have since installed NVIDIA and now i've remembered why i installed nouveau instead. When using a browser for a while, i get a recurring intermittent beep from somewhere in the machine which does not go away until i close the browser (and sometimes have to log out) - i can only deduce it a warning from the nvidia GT218 card
If the GT218 is one with a fan on its heat sink, could it be that it has a beeper to tell you it's overheating from a dead or filth encrusted fan and/or heat sink and only overheats if using the proprietary driver? Possibly, i've not opened the machine for a long time. I used the nvidia setting program to check the temp when it beeps and it hovers around 53/54 degrees even when its not beeping.
How old and what model is that motherboard? Could it and/or the PS have swollen or leaking electrolytic (not polymer) caps (8mm X 13mm or larger cans on motherboard, possibly smaller in the PS) anywhere? It did it from day one on the new motherboard using nvidia. Both boards a 3 -4 years old now but i never got the problem with nouveau.
If you can take a cover off and face a fan at the GT218 and subsequently the beeping is prevented, then you'll know it's a heat related problem, especially if its heat sink has a fan that doesn't spin when the PC is on.
I'll keep an eye on it. I'll just have to close the browser more often. Thanks for the info. -- opensuse:tumbleweed:20161003 Qt: 5.6.1 KDE Frameworks: 5.26.0 KDE Plasma: 5.7.95 kwin5-5.7.95-155.1.x86_64 kmail5-16.08.1-1.1.x86_64 Kernel: 4.7.5-1-default Nouveau: 1.0.13_1.1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2016-10-05 3:37 GMT-03:00 ianseeks <bingmybong@btinternet.com>:
On Tuesday, 4 October 2016 04:40:21 BST Felix Miata wrote:
ianseeks composed on 2016-10-04 09:03 (UTC+0100):
I have since installed NVIDIA and now i've remembered why i installed nouveau instead. When using a browser for a while, i get a recurring intermittent beep from somewhere in the machine which does not go away until i close the browser (and sometimes have to log out) - i can only deduce it a warning from the nvidia GT218 card
If the GT218 is one with a fan on its heat sink, could it be that it has a beeper to tell you it's overheating from a dead or filth encrusted fan and/or heat sink and only overheats if using the proprietary driver? Possibly, i've not opened the machine for a long time. I used the nvidia setting program to check the temp when it beeps and it hovers around 53/54 degrees even when its not beeping.
How old and what model is that motherboard? Could it and/or the PS have swollen or leaking electrolytic (not polymer) caps (8mm X 13mm or larger cans on motherboard, possibly smaller in the PS) anywhere? It did it from day one on the new motherboard using nvidia. Both boards a 3 -4 years old now but i never got the problem with nouveau.
If you can take a cover off and face a fan at the GT218 and subsequently the beeping is prevented, then you'll know it's a heat related problem, especially if its heat sink has a fan that doesn't spin when the PC is on.
I'll keep an eye on it. I'll just have to close the browser more often.
Thanks for the info.
-- opensuse:tumbleweed:20161003 Qt: 5.6.1 KDE Frameworks: 5.26.0 KDE Plasma: 5.7.95 kwin5-5.7.95-155.1.x86_64 kmail5-16.08.1-1.1.x86_64 Kernel: 4.7.5-1-default Nouveau: 1.0.13_1.1
The other way, is to change the video card for a recent AMD, because from the kernel 4.5.2, You has the AMDGPU open-source video driver included on it. Regards -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday, 5 October 2016 08:35:49 BST Juan Erbes wrote:
2016-10-05 3:37 GMT-03:00 ianseeks <bingmybong@btinternet.com>:
On Tuesday, 4 October 2016 04:40:21 BST Felix Miata wrote:
ianseeks composed on 2016-10-04 09:03 (UTC+0100):
I have since installed NVIDIA and now i've remembered why i installed nouveau instead. When using a browser for a while, i get a recurring intermittent beep from somewhere in the machine which does not go away until i close the browser (and sometimes have to log out) - i can only deduce it a warning from the nvidia GT218 card
If the GT218 is one with a fan on its heat sink, could it be that it has a beeper to tell you it's overheating from a dead or filth encrusted fan and/or heat sink and only overheats if using the proprietary driver?
Possibly, i've not opened the machine for a long time. I used the nvidia setting program to check the temp when it beeps and it hovers around 53/54 degrees even when its not beeping.
How old and what model is that motherboard? Could it and/or the PS have swollen or leaking electrolytic (not polymer) caps (8mm X 13mm or larger cans on motherboard, possibly smaller in the PS) anywhere?
It did it from day one on the new motherboard using nvidia. Both boards a 3 -4 years old now but i never got the problem with nouveau.
If you can take a cover off and face a fan at the GT218 and subsequently the beeping is prevented, then you'll know it's a heat related problem, especially if its heat sink has a fan that doesn't spin when the PC is on.> I'll keep an eye on it. I'll just have to close the browser more often.
Thanks for the info.
-- opensuse:tumbleweed:20161003 Qt: 5.6.1 KDE Frameworks: 5.26.0 KDE Plasma: 5.7.95 kwin5-5.7.95-155.1.x86_64 kmail5-16.08.1-1.1.x86_64 Kernel: 4.7.5-1-default Nouveau: 1.0.13_1.1
The other way, is to change the video card for a recent AMD, because from the kernel 4.5.2, You has the AMDGPU open-source video driver included on it.
I am considering that for my next card. thanks
Regards
-- opensuse:tumbleweed:20161003 Qt: 5.7.0 KDE Frameworks: 5.26.0 KDE Plasma: 5.7.4 kwin5-5.7.4-1.3.x86_64 kmail5-16.08.1-1.2.x86_64 Kernel: 4.7.5-1-default Nouveau: 1.0.13_1.1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Bruno Friedmann -
Felix Miata -
ianseeks -
Juan Erbes -
Ken Schneider -
Patrick Shanahan -
René Krell -
Simon Lees