[opensuse] Help! 15.1 System unusable due to KDE freezes
Hi I write from my laptop because my desktop computer has become unusable all of a sudden. It is OS 15.1 with latest updated KDE, with an Nvidia-Card. I had similar problems before, but then I thought I found the solution changing compositor version - but the fun only was for 7 days (in which I didn't reboot). This morning, after entering the password in the creen that comes after a while of inactivity, the desktop froze. I logged out and the password page showed completely scrambled. After logging in it froze again. I rebooted several times, always the same result. I let the computer down for half an hour, booted, and happily enjoyed it - for some time. Now, it's frozen again... Mouse doesn't move, keyboard is dead, but I can SSH to it from the laptop. Immediately after logging in as root via SSH I typed "dmesg" and copied the result. I didn't shorten it, because I don't know from when those messages are and which are important. I also copied /var/log/messages since the last boot: https://www.daniel-bauer.com/div/dmesg.txt https://www.daniel-bauer.com/div/mesages.txt Right now the computer - my only working place - is unusable and I hope somebody can give me a hint on what happened and what I can do. Thanks a lot! Daniel -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
sorry typo... the correct messages link is https://www.daniel-bauer.com/div/messages.txt On 05.09.19 13:55, Daniel Bauer wrote:
Hi
I write from my laptop because my desktop computer has become unusable all of a sudden.
It is OS 15.1 with latest updated KDE, with an Nvidia-Card.
I had similar problems before, but then I thought I found the solution changing compositor version - but the fun only was for 7 days (in which I didn't reboot). This morning, after entering the password in the creen that comes after a while of inactivity, the desktop froze.
I logged out and the password page showed completely scrambled. After logging in it froze again. I rebooted several times, always the same result.
I let the computer down for half an hour, booted, and happily enjoyed it - for some time. Now, it's frozen again...
Mouse doesn't move, keyboard is dead, but I can SSH to it from the laptop.
Immediately after logging in as root via SSH I typed "dmesg" and copied the result. I didn't shorten it, because I don't know from when those messages are and which are important. I also copied /var/log/messages since the last boot:
https://www.daniel-bauer.com/div/dmesg.txt
https://www.daniel-bauer.com/div/mesages.txt
Right now the computer - my only working place - is unusable and I hope somebody can give me a hint on what happened and what I can do.
Thanks a lot!
Daniel
-- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/09/2019 13.58, Daniel Bauer wrote:
sorry typo... the correct messages link is https://www.daniel-bauer.com/div/messages.txt
Leafpad shows blank file? I don't understand, filesystem says it is 279 KB. Ok, the start is filled with many ascii-zero, so the editor thinks end of file. Repairing. Huh, mozilla set it read only, changing first. Now looking. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-09-05 07:55 AM, Daniel Bauer wrote:
Mouse doesn't move, keyboard is dead, but I can SSH to it from the laptop.
When mine locked up and left me with a blank screen, I was able to log in with ssh, from another computer. The system was definetely alive, but with no destkop. On other occasions, I could ping but not ssh. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/09/2019 13.55, Daniel Bauer wrote: ...
https://www.daniel-bauer.com/div/dmesg.txt
https://www.daniel-bauer.com/div/mesages.txt
Right now the computer - my only working place - is unusable and I hope somebody can give me a hint on what happened and what I can do.
Thanks a lot!
Looking at dmesg: [ 0.016058] DMAR-IR: This system BIOS has enabled interrupt remapping on a chipset that contains an erratum making that feature unstable. To maintain system stability interrupt remapping is being disabled. Please contact your BIOS vendor for an update Maybe you should check for a bios update. [ 0.310520] pci 0000:03:00.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff] [ 0.310526] pci 0000:03:00.1: Linked as a consumer to 0000:03:00.0 [ 0.310534] pci 0000:05:00.0: async suspend disabled to avoid multi-function power-on ordering issue [ 0.310538] pci 0000:05:00.1: async suspend disabled to avoid multi-function power-on ordering issue [ 0.310541] pci 0000:06:00.0: async suspend disabled to avoid multi-function power-on ordering issue [ 0.310544] pci 0000:06:00.1: async suspend disabled to avoid multi-function power-on ordering issue [ 0.310571] PCI: CLS 64 bytes, default 64 ? [ 16.263816] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [ 16.269885] ACPI: Power Button [PWRB] [ 16.269968] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [ 16.270083] ACPI: Power Button [PWRF] [ 16.289091] EDAC MC0: Giving out device to module i7core_edac.c controller i7 core #0: DEV 0000:3f:03.0 (INTERRUPT) [ 16.289134] EDAC PCI0: Giving out device to module i7core_edac controller EDAC PCI controller: DEV 0000:3f:03.0 (POLLED) [ 16.289149] EDAC i7core: Driver loaded, 1 memory controller(s) found. [ 16.297716] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x000000000000042C-0x000000000000042D (\GP2C) (20170303/utaddress-213) [ 16.297722] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 16.297750] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 36.952308] resource sanity check: requesting [mem 0x000e0000-0x000fffff], which spans more than pnp 00:05 [mem 0x000e0000-0x000effff] [ 36.952595] caller _nv027774rm+0x58/0x90 [nvidia] mapping multiple BARs [ 37.067950] r8169 0000:07:00.0 eth0: link up [ 37.067961] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 37.089226] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] [ 37.089367] caller _nv001015rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs Looking at messages, from bottom to up. I see several KDE messages which I can not interpret. I see you did some updates (12:55). packagekit did it. Many more KDE related messages. [...] I don't see any thing obvious. I would try another desktop, Gnome or XFCE. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Am 05.09.19 um 15:02 schrieb Carlos E. R.:
On 05/09/2019 13.55, Daniel Bauer wrote:
...
https://www.daniel-bauer.com/div/dmesg.txt
https://www.daniel-bauer.com/div/mesages.txt
Right now the computer - my only working place - is unusable and I hope somebody can give me a hint on what happened and what I can do.
Thanks a lot!
Looking at dmesg:
[ 0.016058] DMAR-IR: This system BIOS has enabled interrupt remapping on a chipset that contains an erratum making that feature unstable. To maintain system stability interrupt remapping is being disabled. Please contact your BIOS vendor for an update
Maybe you should check for a bios update.
If I read that message, the unstable part comes from the chipset, whci I cannot change that easily. And the feature is simply disabled, so it shouldn't interfere. Or do I see that wrong? ...
Looking at messages, from bottom to up.
I see several KDE messages which I can not interpret.
I see you did some updates (12:55). packagekit did it.
Yes, it was running for an hour this time, and I used the moments without freeze to update...
Many more KDE related messages.
[...]
I don't see any thing obvious.
I would try another desktop, Gnome or XFCE.
Most of my apps are KDE apps. So, I'd have KDE's things working anyway, but without the comfort, I guess... I fear it is simply that linux cannot handle Nvidia cards correctly, or Nvidia cannot handle KDE correctly. All comments I find on the topic "KDE freeze" in google refer to Nvidia, since years. On the desktop I could change the graphics card, in the laptop I can't (the laptop, because currently unused, still runs 42.3)... I don't know if I should look for another graphics card. If it would solve the problems, I'd buy one. But what if the problems persist? -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Daniel Bauer
Most of my apps are KDE apps. So, I'd have KDE's things working anyway, but without the comfort, I guess...
I fear it is simply that linux cannot handle Nvidia cards correctly, or Nvidia cannot handle KDE correctly. All comments I find on the topic "KDE freeze" in google refer to Nvidia, since years.
On the desktop I could change the graphics card, in the laptop I can't (the laptop, because currently unused, still runs 42.3)...
I don't know if I should look for another graphics card. If it would solve the problems, I'd buy one. But what if the problems persist?
instead of spending monies w/o knowing that is actually the problem, why not try using the nouveau drivers first, just as a test? https://forums.opensuse.org/showthread.php/528745-Nouveau-How-to-reverse-fro... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 05.09.19 um 16:41 schrieb Patrick Shanahan:
* Daniel Bauer
[09-05-19 10:33]: [...]
Most of my apps are KDE apps. So, I'd have KDE's things working anyway, but without the comfort, I guess...
I fear it is simply that linux cannot handle Nvidia cards correctly, or Nvidia cannot handle KDE correctly. All comments I find on the topic "KDE freeze" in google refer to Nvidia, since years.
On the desktop I could change the graphics card, in the laptop I can't (the laptop, because currently unused, still runs 42.3)...
I don't know if I should look for another graphics card. If it would solve the problems, I'd buy one. But what if the problems persist?
instead of spending monies w/o knowing that is actually the problem, why not try using the nouveau drivers first, just as a test?
https://forums.opensuse.org/showthread.php/528745-Nouveau-How-to-reverse-fro...
I followed that, but then my 1920 x 1200 px screen was in a low resolution with huge and distrorted, unsharp characters... So now I went through "Nvidia the hard way" and installed x85_64-390.129 The login screen was scrambled... let's see if the desktop freezes or if it works... -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 05.09.19 um 17:44 schrieb Daniel Bauer:
Am 05.09.19 um 16:41 schrieb Patrick Shanahan:
* Daniel Bauer
[09-05-19 10:33]: [...]
Most of my apps are KDE apps. So, I'd have KDE's things working anyway, but without the comfort, I guess...
I fear it is simply that linux cannot handle Nvidia cards correctly, or Nvidia cannot handle KDE correctly. All comments I find on the topic "KDE freeze" in google refer to Nvidia, since years.
On the desktop I could change the graphics card, in the laptop I can't (the laptop, because currently unused, still runs 42.3)...
I don't know if I should look for another graphics card. If it would solve the problems, I'd buy one. But what if the problems persist?
instead of spending monies w/o knowing that is actually the problem, why not try using the nouveau drivers first, just as a test?
https://forums.opensuse.org/showthread.php/528745-Nouveau-How-to-reverse-fro...
I followed that, but then my 1920 x 1200 px screen was in a low resolution with huge and distrorted, unsharp characters...
So now I went through "Nvidia the hard way" and installed x85_64-390.129
The login screen was scrambled... let's see if the desktop freezes or if it works...
So, no difference... After some minutes a short freeze and a KDE restart with desktop effects disabled. I guess the complete freeze will show in some moment, too :-( -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 05.09.19 um 16:41 schrieb Patrick Shanahan:
* Daniel Bauer
[09-05-19 10:33]: [...]
Most of my apps are KDE apps. So, I'd have KDE's things working anyway, but without the comfort, I guess...
I fear it is simply that linux cannot handle Nvidia cards correctly, or Nvidia cannot handle KDE correctly. All comments I find on the topic "KDE freeze" in google refer to Nvidia, since years.
On the desktop I could change the graphics card, in the laptop I can't (the laptop, because currently unused, still runs 42.3)...
I don't know if I should look for another graphics card. If it would solve the problems, I'd buy one. But what if the problems persist?
instead of spending monies w/o knowing that is actually the problem, why not try using the nouveau drivers first, just as a test?
https://forums.opensuse.org/showthread.php/528745-Nouveau-How-to-reverse-fro...
Ok, I got it running with nouveau now in my resolution. There are some things: fonts are displayed different (the bold text in my email list is significantly larger now). I also have the feeling that colors are not as vivid as with the nvidia driver, but I am not 100% sure. I installed/deinstalled nvidia drivers to look at the same images, but as there are a lot of screens in between, my eyes are tired now, I cannot tell it with certainty - still it feels as if... Anyway, I will leave it at nouveau for a while to see if no more freezes arise and to be sure that the bad guy is the nvidia driver. One thing changed for the good: with the nvidia driver (both, the one from suse's rpm's and from nvidia.run) I could not use the two rightmost icon rows ion the desktop: after every log-in they were moved to other places on the screen, and other icons were moved, too. I could only have the icons-positions survive a logout/in when leaving empty the two rows at the left. Now I can use those two rows again. For the moment... -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data giovedì 5 settembre 2019 16:20:18 CEST, Daniel Bauer ha scritto:
Am 05.09.19 um 15:02 schrieb Carlos E. R.:
On 05/09/2019 13.55, Daniel Bauer wrote:
...
https://www.daniel-bauer.com/div/dmesg.txt
https://www.daniel-bauer.com/div/mesages.txt
Right now the computer - my only working place - is unusable and I hope somebody can give me a hint on what happened and what I can do.
Thanks a lot!
Looking at dmesg:
[ 0.016058] DMAR-IR: This system BIOS has enabled interrupt remapping
on a chipset that contains an erratum making that feature unstable. To maintain system stability interrupt remapping is being disabled. Please contact your BIOS vendor for an update
Maybe you should check for a bios update.
If I read that message, the unstable part comes from the chipset, whci I cannot change that easily. And the feature is simply disabled, so it shouldn't interfere. Or do I see that wrong?
...
Looking at messages, from bottom to up.
I see several KDE messages which I can not interpret.
I see you did some updates (12:55). packagekit did it.
Yes, it was running for an hour this time, and I used the moments without freeze to update...
Many more KDE related messages.
[...]
I don't see any thing obvious.
I would try another desktop, Gnome or XFCE.
Most of my apps are KDE apps. So, I'd have KDE's things working anyway, but without the comfort, I guess...
I fear it is simply that linux cannot handle Nvidia cards correctly, or Nvidia cannot handle KDE correctly. All comments I find on the topic "KDE freeze" in google refer to Nvidia, since years.
On the desktop I could change the graphics card, in the laptop I can't (the laptop, because currently unused, still runs 42.3)...
I don't know if I should look for another graphics card. If it would solve the problems, I'd buy one. But what if the problems persist? Well I had the problem of freezing when changing user (Fn+ctrl+alt) With AMD I solved that issue. I do not know your chipset. Opensuse since 15.1 does not support the G02 driver anymore, so if your card relies on it forget it or change distribution. These cards do not handle opengl any more so the use of it is a PITA.
My advice would be a good AMD graphics card. If you did run the system a lot of time and use Kontact check your memory. The bug Bug 1136132 will make your system unresponsive if it runs long time without logout. If you are hit by it control swap. If swap is close to 100 % of memory you will have to kill akonadi and all kontakt related files, then swapoff -a and wait for a long time. Sometimes then it comes back. (This is BTW with an Intel graphics). I do not think the BIOS is the culprit. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 05.09.19 um 16:47 schrieb stakanov:
In data giovedì 5 settembre 2019 16:20:18 CEST, Daniel Bauer ha scritto:
Am 05.09.19 um 15:02 schrieb Carlos E. R.:
On 05/09/2019 13.55, Daniel Bauer wrote:
...
https://www.daniel-bauer.com/div/dmesg.txt
https://www.daniel-bauer.com/div/mesages.txt
Right now the computer - my only working place - is unusable and I hope somebody can give me a hint on what happened and what I can do.
Thanks a lot!
Looking at dmesg:
[ 0.016058] DMAR-IR: This system BIOS has enabled interrupt remapping
on a chipset that contains an erratum making that feature unstable. To maintain system stability interrupt remapping is being disabled. Please contact your BIOS vendor for an update
Maybe you should check for a bios update.
If I read that message, the unstable part comes from the chipset, whci I cannot change that easily. And the feature is simply disabled, so it shouldn't interfere. Or do I see that wrong?
...
Looking at messages, from bottom to up.
I see several KDE messages which I can not interpret.
I see you did some updates (12:55). packagekit did it.
Yes, it was running for an hour this time, and I used the moments without freeze to update...
Many more KDE related messages.
[...]
I don't see any thing obvious.
I would try another desktop, Gnome or XFCE.
Most of my apps are KDE apps. So, I'd have KDE's things working anyway, but without the comfort, I guess...
I fear it is simply that linux cannot handle Nvidia cards correctly, or Nvidia cannot handle KDE correctly. All comments I find on the topic "KDE freeze" in google refer to Nvidia, since years.
On the desktop I could change the graphics card, in the laptop I can't (the laptop, because currently unused, still runs 42.3)...
I don't know if I should look for another graphics card. If it would solve the problems, I'd buy one. But what if the problems persist? Well I had the problem of freezing when changing user (Fn+ctrl+alt) With AMD I solved that issue. I do not know your chipset. Opensuse since 15.1 does not support the G02 driver anymore, so if your card relies on it forget it or change distribution. These cards do not handle opengl any more so the use of it is a PITA.
The Nvidia website says the card supports OpenGL 4.1
My advice would be a good AMD graphics card.
Yes. I just read that the AMD drivers are far behind the nvidia drivers in regard of 3D. I am totally unsure what to do.
If you did run the system a lot of time and use Kontact check your memory.
I don't use kontakt.
The bug Bug 1136132 will make your system unresponsive if it runs long time without logout. If you are hit by it control swap. If swap is close to 100 % of memory you will have to kill akonadi and all kontakt related files, then swapoff -a and wait for a long time. Sometimes then it comes back. (This is BTW with an Intel graphics).
I believe there's no akonadi running. I wonder though that I see things like "Started Daily Cleanup of Snapper Snapshots" in /var/log/messages although I have nothing with btrfs and no snapshots... I have 24GB of new memory chips. Swap shouldn't be used at any time... I downloaded the memory test and will let it run for a while to be sure...
I do not think the BIOS is the culprit.
-- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/09/2019 18.15, Daniel Bauer wrote:
Am 05.09.19 um 16:47 schrieb stakanov:
...
I believe there's no akonadi running. I wonder though that I see things like "Started Daily Cleanup of Snapper Snapshots" in /var/log/messages although I have nothing with btrfs and no snapshots...
Everybody does. Just ignore it. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 09/05/2019 11:27 AM, Carlos E. R. wrote:
On 05/09/2019 18.15, Daniel Bauer wrote:
Am 05.09.19 um 16:47 schrieb stakanov:
...
I believe there's no akonadi running. I wonder though that I see things like "Started Daily Cleanup of Snapper Snapshots" in /var/log/messages although I have nothing with btrfs and no snapshots...
Everybody does. Just ignore it.
If you have *NO BTRFS* # zypper rm btrfsmaintenance btrfsprogs btrfsprogs-udev-rules libbtrfs0 -- David C. Rankin, J.D.,P.E.
On 07/09/2019 05.04, David C. Rankin wrote:
On 09/05/2019 11:27 AM, Carlos E. R. wrote:
On 05/09/2019 18.15, Daniel Bauer wrote:
Am 05.09.19 um 16:47 schrieb stakanov:
...
I believe there's no akonadi running. I wonder though that I see things like "Started Daily Cleanup of Snapper Snapshots" in /var/log/messages although I have nothing with btrfs and no snapshots...
Everybody does. Just ignore it.
If you have *NO BTRFS*
If you have NO BTRFS *ever*
# zypper rm btrfsmaintenance btrfsprogs btrfsprogs-udev-rules libbtrfs0
-- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 05/09/2019 16.20, Daniel Bauer wrote:
Am 05.09.19 um 15:02 schrieb Carlos E. R.:
On 05/09/2019 13.55, Daniel Bauer wrote:
...
https://www.daniel-bauer.com/div/dmesg.txt
https://www.daniel-bauer.com/div/mesages.txt
Right now the computer - my only working place - is unusable and I hope somebody can give me a hint on what happened and what I can do.
Thanks a lot!
Looking at dmesg:
[ 0.016058] DMAR-IR: This system BIOS has enabled interrupt remapping on a chipset that contains an erratum making that feature unstable. To maintain system stability interrupt remapping is being disabled. Please contact your BIOS vendor for an update
Maybe you should check for a bios update.
If I read that message, the unstable part comes from the chipset, whci I cannot change that easily. And the feature is simply disabled, so it shouldn't interfere. Or do I see that wrong?
Yes, but if there is a BIOS update available, I'd do it. Although there is always some risk, but not being a new computer, it should not contain dangerous bugs by now. Be sure to be connected to an UPS (SAI), though.
...
Looking at messages, from bottom to up.
I see several KDE messages which I can not interpret.
I see you did some updates (12:55). packagekit did it.
Yes, it was running for an hour this time, and I used the moments without freeze to update...
Many more KDE related messages.
[...]
I don't see any thing obvious.
I would try another desktop, Gnome or XFCE.
Most of my apps are KDE apps. So, I'd have KDE's things working anyway, but without the comfort, I guess...
I too use KDE applications when I want/need them, but without the desktop. Of course, it is more memory load. In this case, if it works, well, it works: now the machine doesn't. It would tell you more: is the machine bad or not?
I fear it is simply that linux cannot handle Nvidia cards correctly, or Nvidia cannot handle KDE correctly. All comments I find on the topic "KDE freeze" in google refer to Nvidia, since years.
I don't know. Only that people complain.
On the desktop I could change the graphics card, in the laptop I can't (the laptop, because currently unused, still runs 42.3)...
I don't know if I should look for another graphics card. If it would solve the problems, I'd buy one. But what if the problems persist?
There is no assurance :-( -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 5/9/19 9:55 pm, Daniel Bauer wrote:
Hi
I write from my laptop because my desktop computer has become unusable all of a sudden.
It is OS 15.1 with latest updated KDE, with an Nvidia-Card.
I had similar problems before, but then I thought I found the solution changing compositor version - but the fun only was for 7 days (in which I didn't reboot). This morning, after entering the password in the creen that comes after a while of inactivity, the desktop froze.
I logged out and the password page showed completely scrambled. After logging in it froze again. I rebooted several times, always the same result.
I let the computer down for half an hour, booted, and happily enjoyed it - for some time. Now, it's frozen again...
Mouse doesn't move, keyboard is dead, but I can SSH to it from the laptop.
Immediately after logging in as root via SSH I typed "dmesg" and copied the result. I didn't shorten it, because I don't know from when those messages are and which are important. I also copied /var/log/messages since the last boot:
https://www.daniel-bauer.com/div/dmesg.txt
https://www.daniel-bauer.com/div/mesages.txt
Right now the computer - my only working place - is unusable and I hope somebody can give me a hint on what happened and what I can do.
Thanks a lot!
Daniel
Daniel, I have looked over all the msgs relating to your problem with your desktop -- and I am ONLY talking about your desktop -- and would like to put forward some random questions/comments. You mention in one of your posts (dated 17/8/19) that you added a new SSD, a new HDD, and added additional RAM. Firstly, how 'big' is your power supply (psu)? Does it have enough power to handle the additional h/ware? Just wondering (as well as wondering if one of the power supply channels is playing up because of the extra h/ware). Secondly, according to the dmesg.txt/messages.txt you "posted" your motherboard is a Gigabyte X58A-UD3R which has 6 slots for RAM. When you added the new RAM-- (a) was it matched to the old RAM you had installed?; (b) did you install the new RAM in the correct combination of slots as per the manual for the m/board?; (c) did you test the RAM to ensure that it is OK (I installed new RAM only to find that the desktop played up when a program needed to use memory on a bum chip :-(); (d) is it possible that, with the m/board of the 2010 vintage, that the slots where the new RAM went in were 'dirty' and that one of the new RAM chips is not fully functioning? Finally, the *.txt file/s shows (1) that the kernel finds that there is an erratum in the BIOS and that the BIOS needs updating; (2) that sda2 (formatted in FAT) has not been properly unmounted and that fsck should be rung. BC -- A three-year-old boy was examining his testicles while taking a bath. "Mum" he asked, "are these my brains?" "Not yet," she replied. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 08.09.19 um 10:34 schrieb Basil Chupin:
On 5/9/19 9:55 pm, Daniel Bauer wrote:
Hi
I write from my laptop because my desktop computer has become unusable all of a sudden.
It is OS 15.1 with latest updated KDE, with an Nvidia-Card.
I had similar problems before, but then I thought I found the solution changing compositor version - but the fun only was for 7 days (in which I didn't reboot). This morning, after entering the password in the creen that comes after a while of inactivity, the desktop froze.
I logged out and the password page showed completely scrambled. After logging in it froze again. I rebooted several times, always the same result.
I let the computer down for half an hour, booted, and happily enjoyed it - for some time. Now, it's frozen again...
Mouse doesn't move, keyboard is dead, but I can SSH to it from the laptop.
Immediately after logging in as root via SSH I typed "dmesg" and copied the result. I didn't shorten it, because I don't know from when those messages are and which are important. I also copied /var/log/messages since the last boot:
https://www.daniel-bauer.com/div/dmesg.txt
https://www.daniel-bauer.com/div/mesages.txt
Right now the computer - my only working place - is unusable and I hope somebody can give me a hint on what happened and what I can do.
Thanks a lot!
Daniel
Daniel, I have looked over all the msgs relating to your problem with your desktop -- and I am ONLY talking about your desktop -- and would like to put forward some random questions/comments.
You mention in one of your posts (dated 17/8/19) that you added a new SSD, a new HDD, and added additional RAM. Firstly, how 'big' is your power supply (psu)? Does it have enough power to handle the additional h/ware? Just wondering (as well as wondering if one of the power supply channels is playing up because of the extra h/ware).
750W - should be enough
Secondly, according to the dmesg.txt/messages.txt you "posted" your motherboard is a Gigabyte X58A-UD3R which has 6 slots for RAM. When you added the new RAM-- (a) was it matched to the old RAM you had installed?;
The old Ram have been 2 slots of 8, now its 3 slots of 8
(b) did you install the new RAM in the correct combination of slots as per the manual for the m/board?;
I think so. They are placed in every second slot.
(c) did you test the RAM to ensure that it is OK (I installed new RAM only to find that the desktop played up when a program needed to use memory on a bum chip :-(); (d) is it possible that, with the m/board of the 2010 vintage, that the slots where the new RAM went in were 'dirty' and that one of the new RAM chips is not fully functioning?
I download memtest and run it for several hours, although it cost me nerves because it shows the processor temperature wrong (I guess) - it went up to 98°C - and I killed the test, and checked the temperature in Bios which was much lower. So I let memtest run again. No errors.
Finally, the *.txt file/s shows (1) that the kernel finds that there is an erratum in the BIOS and that the BIOS needs updating;
Yes, but I don't think that this matter too much. And honestly I am afraid of changing that...
(2) that sda2 (formatted in FAT) has not been properly unmounted and that fsck should be rung.
Yes, this is an old problem I already asked the list a year or more ago. When shutting down it tells me that the disk is active and cannot be unmounted. It's part of an encrypted LVM. I was told that I don't have to care about that. It was and is like that "since always" also on 42.3 where the nvidia card still worked.... Now, I guess a hardware defect can be excluded. I have removed the nvidia drivers and run it with nouveau now and all those problems are gone (there are some other, minor ones, though, like fonts looking different). Just this morning I installed the nvidia drivers again to provide an output I was asked at the bug report. With nvidia the problems are here immediately. After the test I removed nvidia drivers and the problems are gone, again. So, it's definitively an nvidia driver problem, that occurs the same with the opensuse repository rpms as with the nvidia*.run directly from nvidia, which I have tested also and that produce the same problems. -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/08/2019 03:52 AM, Daniel Bauer wrote:
Secondly, according to the dmesg.txt/messages.txt you "posted" your motherboard is a Gigabyte X58A-UD3R which has 6 slots for RAM. When you added the new RAM-- (a) was it matched to the old RAM you had installed?;
The old Ram have been 2 slots of 8, now its 3 slots of 8
Yikes, Double-triple check this in your manual. Generally in the 2010 vintage motherboards, you would install RAM in pairs to provide Dual-Channel capability enabling the RAM to use double the single-chip memory width. So if you have 2-sticks attempting to run in dual-channel mode and 1 new stick that has no way to run in dual-channel mode -- I can see that causing issues. The mobo should be smart enough to disable dual-channel all the way around, enabling your setup to run, but you need to check. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 08.09.19 um 11:47 schrieb David C. Rankin:
On 09/08/2019 03:52 AM, Daniel Bauer wrote:
Secondly, according to the dmesg.txt/messages.txt you "posted" your motherboard is a Gigabyte X58A-UD3R which has 6 slots for RAM. When you added the new RAM-- (a) was it matched to the old RAM you had installed?;
The old Ram have been 2 slots of 8, now its 3 slots of 8
Yikes,
Double-triple check this in your manual. Generally in the 2010 vintage motherboards, you would install RAM in pairs to provide Dual-Channel capability enabling the RAM to use double the single-chip memory width.
So if you have 2-sticks attempting to run in dual-channel mode and 1 new stick that has no way to run in dual-channel mode -- I can see that causing issues.
The mobo should be smart enough to disable dual-channel all the way around, enabling your setup to run, but you need to check.
I believe all is ok with the memory. It passed memtest for hours without error. Now that I removed the nvidia drivers and run nouveau those problems are gone. Right now I'm doing quite memory intensive jobs: having digikam plus several 30Mpx images open in kuickshow or up to 8 of them in Gimp, or working with Win10 in Virtualbox with 30Mpx raw files, batch processing them while writing this mail... I am quite sure that the nvidia drivers simply do not work (anymore?) for my card. So far it works with nouveau but I am not sure if nouveau renders the colors in a bit a different way. It's hard to say because I cannot have both at the same time to really compare. I just have the impression that colors are a bit less vivid now - colors are important for my work, of course. What I can say for sure is that nouveau renders differently at least the font I use in email, it's obvious. -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/09/2019 15.12, Daniel Bauer wrote:
Am 08.09.19 um 11:47 schrieb David C. Rankin:
On 09/08/2019 03:52 AM, Daniel Bauer wrote:
Secondly, according to the dmesg.txt/messages.txt you "posted" your motherboard is a Gigabyte X58A-UD3R which has 6 slots for RAM. When you added the new RAM-- (a) was it matched to the old RAM you had installed?;
The old Ram have been 2 slots of 8, now its 3 slots of 8
Yikes,
Double-triple check this in your manual. Generally in the 2010 vintage motherboards, you would install RAM in pairs to provide Dual-Channel capability enabling the RAM to use double the single-chip memory width.
So if you have 2-sticks attempting to run in dual-channel mode and 1 new stick that has no way to run in dual-channel mode -- I can see that causing issues.
The mobo should be smart enough to disable dual-channel all the way around, enabling your setup to run, but you need to check.
I believe all is ok with the memory. It passed memtest for hours without error.
The issue is not really "working", but the speed. A machine that uses dual channel runs faster. Or rather performs better. In order to have it, you have to follow some rules from your mobo manual. For example, mine says: Dual-Channel mode Population Rule In Dual-Channel mode, the memory modules can transmit and receive data with two data bus lines simultaneously. Enabling Dual-Channel mode can enhance the system performance. Please refer to the following illustrations for population rules under Dual-Channel mode. Having 3 ram modules is suspicious.
Now that I removed the nvidia drivers and run nouveau those problems are gone.
Nouveau does not support 3D, has to be done by the CPU instead, thus slower. That's the main impact. And KDE uses 3D, I believe.
Right now I'm doing quite memory intensive jobs: having digikam plus several 30Mpx images open in kuickshow or up to 8 of them in Gimp, or working with Win10 in Virtualbox with 30Mpx raw files, batch processing them while writing this mail...
I am quite sure that the nvidia drivers simply do not work (anymore?) for my card.
So far it works with nouveau but I am not sure if nouveau renders the colors in a bit a different way. It's hard to say because I cannot have both at the same time to really compare. I just have the impression that colors are a bit less vivid now - colors are important for my work, of course.
You could perhaps take photos of the screen to compare, manual mode to avoid camera corrections. However, it is possible that the difference is in the contrast/brightness adjustments.
What I can say for sure is that nouveau renders differently at least the font I use in email, it's obvious.
I don't know why that would be, if the display mode is the same. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Le 08/09/2019 à 15:30, Carlos E. R. a écrit :
Now that I removed the nvidia drivers and run nouveau those problems are gone.
Nouveau does not support 3D, has to be done by the CPU instead, thus slower. That's the main impact. And KDE uses 3D, I believe.
As far as I understand, 15.1 nouveau is much better than 15.0 one, specially since I moved to 15.1, my computer is *much* faster, and bumblebee works. Installing bumblebee (optimus computer) removed nvidia to install nouveau (when I expected the other way round)
So far it works with nouveau but I am not sure if nouveau renders the colors in a bit a different way. It's hard to say because I cannot have both at the same time to really compare.
two things... You can use the color picker to see what is the color of the picture - sure it's not easy (could need two installs on the same computer), then may be the color in the frame buffer is the same, but not rendered the same on screen? for this you may have to calibrate your screen, but you may know this better than I do. I use to share photos with friends on forum, and I have the same impression in front of them than the other people, this makes me think my screen is OK (I have a calibrating device, but never could make a real use of it) jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/09/2019 16.37, jdd@dodin.org wrote:
Le 08/09/2019 à 15:30, Carlos E. R. a écrit :
Now that I removed the nvidia drivers and run nouveau those problems are gone.
Nouveau does not support 3D, has to be done by the CPU instead, thus slower. That's the main impact. And KDE uses 3D, I believe.
As far as I understand, 15.1 nouveau is much better than 15.0 one, specially since I moved to 15.1, my computer is *much* faster, and bumblebee works. Installing bumblebee (optimus computer) removed nvidia to install nouveau (when I expected the other way round)
That's good :-)
So far it works with nouveau but I am not sure if nouveau renders the colors in a bit a different way. It's hard to say because I cannot have both at the same time to really compare.
two things... You can use the color picker to see what is the color of the picture - sure it's not easy (could need two installs on the same computer), then may be the color in the frame buffer is the same, but not rendered the same on screen? for this you may have to calibrate your screen, but you may know this better than I do.
That's what I think. The photos obviously have the same digital value, but the adjustments of the voltages applied to each pixel may be different for each driver. There may be different colours depending on what cable (ie, what interface) is used.
I use to share photos with friends on forum, and I have the same impression in front of them than the other people, this makes me think my screen is OK (I have a calibrating device, but never could make a real use of it)
I don't even try to calibrate these days... -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Am 08.09.19 um 21:50 schrieb Carlos E. R.:
So far it works with nouveau but I am not sure if nouveau renders the colors in a bit a different way. It's hard to say because I cannot have both at the same time to really compare.
two things... You can use the color picker to see what is the color of the picture - sure it's not easy (could need two installs on the same computer), then may be the color in the frame buffer is the same, but not rendered the same on screen? for this you may have to calibrate your screen, but you may know this better than I do.
That's what I think. The photos obviously have the same digital value, but the adjustments of the voltages applied to each pixel may be different for each driver.
There may be different colours depending on what cable (ie, what interface) is used.
Yes, I think they'd have the same value anyway. I'd need a densitometer or something to see how the digital value is "translated" into display colors. Still it would be difficult as I usually don't have larger areas of the same color - it's mostly skin, which is exactly very delicate. My impression - and I say it is an impression only - is that the very fine differences in the shades of a sun tanned skin are smaller with nouveau, thus the 2-dimensional skin has less shape. But it's hard to say, because when de-installing nvidia, running mkinitrd, shut down, boot... there are many bright and dark screens displayed, black, green, blue... so my eye could cheat me, although I tried to concentrate.
I use to share photos with friends on forum, and I have the same impression in front of them than the other people, this makes me think my screen is OK (I have a calibrating device, but never could make a real use of it)
I don't even try to calibrate these days...
For internet use one can forget colors. Each screen shows them different. With the stupid fashion of instagram filters that produce terribly oversaturated photos people get used to heavily blue sky and sea, and when they go out, they think that what they see is not real, pale. So they lower their eyes and check Instagram where the world is much more beautiful :-) I have a calibrated screen, Eizo ColorEdge. It displays /exactly/ as I print on my large Epson or what I get from a professional printer. Fantastic. I'll have to spend some ink and paper to compare. On the other hand, it seems that I must live with nouveau anyway now, so it wouldn't help if I could confirm that it shows colors less vivid... -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/09/2019 22.36, Daniel Bauer wrote:
Am 08.09.19 um 21:50 schrieb Carlos E. R.:
So far it works with nouveau but I am not sure if nouveau renders the colors in a bit a different way. It's hard to say because I cannot have both at the same time to really compare.
two things... You can use the color picker to see what is the color of the picture - sure it's not easy (could need two installs on the same computer), then may be the color in the frame buffer is the same, but not rendered the same on screen? for this you may have to calibrate your screen, but you may know this better than I do.
That's what I think. The photos obviously have the same digital value, but the adjustments of the voltages applied to each pixel may be different for each driver.
There may be different colours depending on what cable (ie, what interface) is used.
Yes, I think they'd have the same value anyway. I'd need a densitometer or something to see how the digital value is "translated" into display colors. Still it would be difficult as I usually don't have larger areas of the same color - it's mostly skin, which is exactly very delicate.
My impression - and I say it is an impression only - is that the very fine differences in the shades of a sun tanned skin are smaller with nouveau, thus the 2-dimensional skin has less shape.
But it's hard to say, because when de-installing nvidia, running mkinitrd, shut down, boot... there are many bright and dark screens displayed, black, green, blue... so my eye could cheat me, although I tried to concentrate.
I think you need to display a calibration photo, one with known colours. Or several. I don't know, I've never done it. Another thing to consider is if the screen modes used are exactly the same. Specially the number of bits per colour. Years ago I handled a "camera" that would calibrate a colour, for a project. Read a wall or lamp and display a luminance and colour values. A million pesetas and a half, back on 1995. 9000€. But you can do by photographing the display in both cases (camera on tripod, 'M' position), and then reading the resulting colours in the photo. If the sample displayed is a grid with black lines separating the colours, you can judge the differences. I hope that the difference is only a question of adjusting the brightness/contrast values of the display.
I use to share photos with friends on forum, and I have the same impression in front of them than the other people, this makes me think my screen is OK (I have a calibrating device, but never could make a real use of it)
I don't even try to calibrate these days...
For internet use one can forget colors. Each screen shows them different. With the stupid fashion of instagram filters that produce terribly oversaturated photos people get used to heavily blue sky and sea, and when they go out, they think that what they see is not real, pale. So they lower their eyes and check Instagram where the world is much more beautiful :-)
:-D
I have a calibrated screen, Eizo ColorEdge. It displays /exactly/ as I print on my large Epson or what I get from a professional printer. Fantastic.
:-o
I'll have to spend some ink and paper to compare. On the other hand, it seems that I must live with nouveau anyway now, so it wouldn't help if I could confirm that it shows colors less vivid...
It should be adjustable to look the same. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 9/9/19 6:36 am, Daniel Bauer wrote:
Am 08.09.19 um 21:50 schrieb Carlos E. R.:
So far it works with nouveau but I am not sure if nouveau renders the colors in a bit a different way. It's hard to say because I cannot have both at the same time to really compare.
two things... You can use the color picker to see what is the color of the picture - sure it's not easy (could need two installs on the same computer), then may be the color in the frame buffer is the same, but not rendered the same on screen? for this you may have to calibrate your screen, but you may know this better than I do.
That's what I think. The photos obviously have the same digital value, but the adjustments of the voltages applied to each pixel may be different for each driver.
There may be different colours depending on what cable (ie, what interface) is used.
Yes, I think they'd have the same value anyway. I'd need a densitometer or something to see how the digital value is "translated" into display colors. Still it would be difficult as I usually don't have larger areas of the same color - it's mostly skin, which is exactly very delicate.
My impression - and I say it is an impression only - is that the very fine differences in the shades of a sun tanned skin are smaller with nouveau, thus the 2-dimensional skin has less shape.
But it's hard to say, because when de-installing nvidia, running mkinitrd, shut down, boot... there are many bright and dark screens displayed, black, green, blue... so my eye could cheat me, although I tried to concentrate.
I use to share photos with friends on forum, and I have the same impression in front of them than the other people, this makes me think my screen is OK (I have a calibrating device, but never could make a real use of it)
I don't even try to calibrate these days...
For internet use one can forget colors. Each screen shows them different. With the stupid fashion of instagram filters that produce terribly oversaturated photos people get used to heavily blue sky and sea, and when they go out, they think that what they see is not real, pale. So they lower their eyes and check Instagram where the world is much more beautiful :-)
I have a calibrated screen, Eizo ColorEdge. It displays /exactly/ as I print on my large Epson or what I get from a professional printer. Fantastic.
*** I take it that the Eizo ColorEdge is a monitor in which case which model is it? (I think that in one of the posts you mention that your resolution is 1920x1200 -- am I right?) More random thoughts on the Saga of Daniel's Nvidia Graphics :-D. Now, reviewing all the tos/fros re your problem I think it is safe to say that it has all to do with graphics -- be it either the monitor or the nvidia card or the driver(s). According to you, all seemed well until you upgraded from 42.3 to 15.1 (a clean, new install you say, with the 42.3 root (/) partition formatted before 15.1 was written to it, right?). At the same time as you upgraded to 15.1 you installed extra RAM (into the correct, clean, slot(s) as per the manual), also installed a 500GB SSD and a new (?size) HDD. This is when the sky fell in, right? :-) I really cannot understand why even self-compiled Nvidia driver causes hassles but a nouveau driver (appears) to 'work' OK. Something not quite right... OK, your gpu is GTX 460 which is now 9 years old. Perhaps it's time has come? One small component on it has now aged and is playing up? Maybe not, maybe yes -- but something is not quite right. I looked up the specs for your Gigabyte m/board, X58A-UD3R, and noticed what is states in the Notes -- see the attachment. Which did the SSD go in relation to the PCIe slot for the GTX460? BC -- A three-year-old boy was examining his testicles while taking a bath. "Mum" he asked, "are these my brains?" "Not yet," she replied.
On 09/09/2019 12:18 AM, Basil Chupin wrote:
OK, your gpu is GTX 460 which is now 9 years old. Perhaps it's time has come? One small component on it has now aged and is playing up? Maybe not, maybe yes -- but something is not quite right.
I have a slew of those cards and so far, I haven't seen any problems from a degradation standpoint -- fantastic cards. I run them in my kids machines (on windows with the Nvidia driver) and they continually pound on them with every game with full-graphics settings and they keep on humming along.... But, that's not to say that you could have a bad component somewhere. My thought in all this is that the WRONG Nvidia drivers were installed on you latest install. There are several different versions. You will need to check, but you should use the GO3 or GO4 drivers, and then should work just fine with the card once you get the right one installed. There is a opensuse page that has the card-model/driver to use cross-reference somewhere, but I don't have the link handy. Double confirm you have the right one. I strongly suspect the installer chose the wrong one to begin with. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 09.09.19 um 09:32 schrieb David C. Rankin:
On 09/09/2019 12:18 AM, Basil Chupin wrote:
OK, your gpu is GTX 460 which is now 9 years old. Perhaps it's time has come? One small component on it has now aged and is playing up? Maybe not, maybe yes -- but something is not quite right.
I have a slew of those cards and so far, I haven't seen any problems from a degradation standpoint -- fantastic cards. I run them in my kids machines (on windows with the Nvidia driver) and they continually pound on them with every game with full-graphics settings and they keep on humming along.... But, that's not to say that you could have a bad component somewhere.
My thought in all this is that the WRONG Nvidia drivers were installed on you latest install. There are several different versions. You will need to check, but you should use the GO3 or GO4 drivers, and then should work just fine with the card once you get the right one installed. There is a opensuse page that has the card-model/driver to use cross-reference somewhere, but I don't have the link handy.
Double confirm you have the right one. I strongly suspect the installer chose the wrong one to begin with.
According to the answer I received in the opensuse bug http://bugzilla.opensuse.org/show_bug.cgi?id=1142971 "Unfortunately your gfxcard is no longer supported by the current driver" ... Well, I was looking at the nvidia driver page and it recommended NVIDIA-Linux-x86_64-390.129.run for this card. But exactly the same problems happened as with the g04 driver from opensuse rpm's. I also tried the G03 driver, but that produced only a black screen with a movable cursor pointer. -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/09/2019 09.55, Daniel Bauer wrote:
According to the answer I received in the opensuse bug http://bugzilla.opensuse.org/show_bug.cgi?id=1142971 "Unfortunately your gfxcard is no longer supported by the current driver" ...
Well, I was looking at the nvidia driver page and it recommended NVIDIA-Linux-x86_64-390.129.run for this card. But exactly the same problems happened as with the g04 driver from opensuse rpm's.
which means that the driver might not support features that KDE uses. Educated wild guess. I got the same reply about my nvidia card, and it results, for instance, that I can no longer install the fgfs game. Card too old. So my next computer will have AMD cpu (because of the intel bugs) and AMD graphics. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 09/09/2019 02:55 AM, Daniel Bauer wrote:
According to the answer I received in the opensuse bug http://bugzilla.opensuse.org/show_bug.cgi?id=1142971 "Unfortunately your gfxcard is no longer supported by the current driver" ...
Well, I was looking at the nvidia driver page and it recommended NVIDIA-Linux-x86_64-390.129.run for this card. But exactly the same problems happened as with the g04 driver from opensuse rpm's.
I also tried the G03 driver, but that produced only a black screen with a movable cursor pointer.
I don't get it. Is the openSUSE wiki page just wrong? https://en.opensuse.org/SDB:NVIDIA_drivers x11-video-nvidiaG04 | NVIDIA graphics driver for GeForce 400 series and newer That would include your GeForce 460 I mean I still have nvidia cards that are 15 years old and I've never had a problem finding a driver for them. ATI gave everyone the shaft in Sept. 07 and cut of driver support for older cards, but as far as I know I can still get drivers for all nvidia cards?? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2019 01.24, David C. Rankin wrote:
On 09/09/2019 02:55 AM, Daniel Bauer wrote:
According to the answer I received in the opensuse bug http://bugzilla.opensuse.org/show_bug.cgi?id=1142971 "Unfortunately your gfxcard is no longer supported by the current driver" ...
Well, I was looking at the nvidia driver page and it recommended NVIDIA-Linux-x86_64-390.129.run for this card. But exactly the same problems happened as with the g04 driver from opensuse rpm's.
I also tried the G03 driver, but that produced only a black screen with a movable cursor pointer.
I don't get it. Is the openSUSE wiki page just wrong?
https://en.opensuse.org/SDB:NVIDIA_drivers
x11-video-nvidiaG04 | NVIDIA graphics driver for GeForce 400 series and newer
That would include your GeForce 460
I mean I still have nvidia cards that are 15 years old and I've never had a problem finding a driver for them. ATI gave everyone the shaft in Sept. 07 and cut of driver support for older cards, but as far as I know I can still get drivers for all nvidia cards??
In my case (GeForce 9500 GT, ie, GeForce 9 Series): [Bug 1132952] New: FlightGear - Flight Simulator is not installable, it conflicts with Nvidia RPMs. http://bugzilla.opensuse.org/show_bug.cgi?id=1132952 .................... Comment # 4 Ok. I believe the requirement to opencl is the culprit here. nvidia-computeG03 provides it and libOpenCL1 provides it as well. These packages conflict. I addressed this issue for recent nvidia driver series G04 and G05, but not for the rather old G03 series. Sun Jan 13 21:29:42 UTC 2019 - ...@suse.com - sle15-sp1/Leap15.1 and newer: switch to usage of update-alternatives for libOpenCL.so.1, so nvidia-computeG04 package no longer conflicts with libOpenCL1 package (boo#1108304 [bugzilla.opensuse.org]) Comment # 9
Can't G03 be added as well to updates alternatives?
I have no plans to do so, no. Originally I even haven't planned to provide G03 at all for Leap >=15, since it doesn't support libglvnd yet and I thought it wouldn't work at all. Then somebody build it manually and told me that it would work fine for him. So I went ahead, built it also for Leap 15 and now even 15.1. Looks like this has been wrong decision. :-( .................... The main functionality is there. But not all. FlightGear can not be installed. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Am 09.09.19 um 07:18 schrieb Basil Chupin:
More random thoughts on the Saga of Daniel's Nvidia Graphics :-D.
Now, reviewing all the tos/fros re your problem I think it is safe to say that it has all to do with graphics -- be it either the monitor or the nvidia card or the driver(s).
According to you, all seemed well until you upgraded from 42.3 to 15.1 (a clean, new install you say, with the 42.3 root (/) partition formatted before 15.1 was written to it, right?).
The root partition is on the brand new SSD.
At the same time as you upgraded to 15.1 you installed extra RAM (into the correct, clean, slot(s) as per the manual), also installed a 500GB SSD and a new (?size) HDD. This is when the sky fell in, right? :-)
The 500GB SSD is physically plugged where before was the first HDD. It is here as sda with sda1 (8MB BIOS-Boot) sda2 (1GB EFI-System, FAT, mounted as /boot) sda3 (encrypted Linux LVM, containing swap, /, and a partition for virtualbox On the second plug (formerly old second HD) is the new 4TB HD, freshly formatted and encrypted, as sdb, sdb1 (ext4) mounted as /home/daniel/fotos On the third plug (new) is the formerly disk1, 2TB, freshly formatted and encrypted, as sdc, sdc1 (ext4) mounted as /home/daniel/digikam On the forth plug (new) is the formerly disk2, 2TB, freshly formatted and encrypted, as sdd, sdd1 (ext4) mounted as /home RAM seems to be at the right place. All fans are clean and work. Installed 15.1 from USB-stick-image. Updated. Installed all programs freshly from the repos. Added all the settings manually. Copied only data (not settings) from my backups. All went fine. Also the screen went almost fine, except that I could not use the 2 most right rows of the desktop to place icons or they would be redistributed after a fresh login. Freezes began later, after some weeks and several updates, also of the nvidia drivers.
I really cannot understand why even self-compiled Nvidia driver causes hassles but a nouveau driver (appears) to 'work' OK. Something not quite right...
Neither do I.
OK, your gpu is GTX 460 which is now 9 years old. Perhaps it's time has come? One small component on it has now aged and is playing up? Maybe not, maybe yes -- but something is not quite right.
I still think that it can't be a hardware defect. If it would be a hardware issue it should show up using nouveau, too, wouldn't it?
I looked up the specs for your Gigabyte m/board, X58A-UD3R, and noticed what is states in the Notes -- see the attachment. Which did the SSD go in relation to the PCIe slot for the GTX460?
I don't understand that. The SSD is plugged just as a normal HD. The Nvidia card is in fact in slot 2, because - years ago, probably with 13.x or even earlier - there suddenly occured problems when it was in slot 1 that were resolved when I changed it to slot 2. -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/9/19 6:31 pm, Daniel Bauer wrote:
Am 09.09.19 um 07:18 schrieb Basil Chupin:
More random thoughts on the Saga of Daniel's Nvidia Graphics :-D.
Now, reviewing all the tos/fros re your problem I think it is safe to say that it has all to do with graphics -- be it either the monitor or the nvidia card or the driver(s).
According to you, all seemed well until you upgraded from 42.3 to 15.1 (a clean, new install you say, with the 42.3 root (/) partition formatted before 15.1 was written to it, right?).
The root partition is on the brand new SSD.
At the same time as you upgraded to 15.1 you installed extra RAM (into the correct, clean, slot(s) as per the manual), also installed a 500GB SSD and a new (?size) HDD. This is when the sky fell in, right? :-)
The 500GB SSD is physically plugged where before was the first HDD.
Daniel, I will have to reread tomorrow morning what you wrote. Methinks that we are talking at cross purposes here. I cannot see how you can have an HDD plugged in a *PCIe* slot and which now has the new SDD plugged in -- AND having the nVidia GTX 460 also plugged in in the SECOND *PCIe* slot (which you mention below). HDDs are conncted to the SATA plugs...
It is here as sda with sda1 (8MB BIOS-Boot) sda2 (1GB EFI-System, FAT, mounted as /boot) sda3 (encrypted Linux LVM, containing swap, /, and a partition for virtualbox
On the second plug (formerly old second HD) is the new 4TB HD, freshly formatted and encrypted, as sdb, sdb1 (ext4) mounted as /home/daniel/fotos
On the third plug (new) is the formerly disk1, 2TB, freshly formatted and encrypted, as sdc, sdc1 (ext4) mounted as /home/daniel/digikam
On the forth plug (new) is the formerly disk2, 2TB, freshly formatted and encrypted, as sdd, sdd1 (ext4) mounted as /home
RAM seems to be at the right place.
All fans are clean and work.
Installed 15.1 from USB-stick-image. Updated. Installed all programs freshly from the repos. Added all the settings manually. Copied only data (not settings) from my backups.
All went fine. Also the screen went almost fine, except that I could not use the 2 most right rows of the desktop to place icons or they would be redistributed after a fresh login.
Freezes began later, after some weeks and several updates, also of the nvidia drivers.
I really cannot understand why even self-compiled Nvidia driver causes hassles but a nouveau driver (appears) to 'work' OK. Something not quite right...
Neither do I.
OK, your gpu is GTX 460 which is now 9 years old. Perhaps it's time has come? One small component on it has now aged and is playing up? Maybe not, maybe yes -- but something is not quite right.
I still think that it can't be a hardware defect. If it would be a hardware issue it should show up using nouveau, too, wouldn't it?
I looked up the specs for your Gigabyte m/board, X58A-UD3R, and noticed what is states in the Notes -- see the attachment. Which did the SSD go in relation to the PCIe slot for the GTX460?
I don't understand that. The SSD is plugged just as a normal HD. The Nvidia card is in fact in slot 2, because - years ago, probably with 13.x or even earlier - there suddenly occured problems when it was in slot 1 that were resolved when I changed it to slot 2.
-- A three-year-old boy was examining his testicles while taking a bath. "Mum" he asked, "are these my brains?" "Not yet," she replied. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 09.09.19 um 12:33 schrieb Basil Chupin:
On 9/9/19 6:31 pm, Daniel Bauer wrote:
Am 09.09.19 um 07:18 schrieb Basil Chupin:
More random thoughts on the Saga of Daniel's Nvidia Graphics :-D.
Now, reviewing all the tos/fros re your problem I think it is safe to say that it has all to do with graphics -- be it either the monitor or the nvidia card or the driver(s).
According to you, all seemed well until you upgraded from 42.3 to 15.1 (a clean, new install you say, with the 42.3 root (/) partition formatted before 15.1 was written to it, right?).
The root partition is on the brand new SSD.
At the same time as you upgraded to 15.1 you installed extra RAM (into the correct, clean, slot(s) as per the manual), also installed a 500GB SSD and a new (?size) HDD. This is when the sky fell in, right? :-)
The 500GB SSD is physically plugged where before was the first HDD.
Daniel, I will have to reread tomorrow morning what you wrote. Methinks that we are talking at cross purposes here. I cannot see how you can have an HDD plugged in a *PCIe* slot and which now has the new SDD plugged in -- AND having the nVidia GTX 460 also plugged in in the SECOND *PCIe* slot (which you mention below). HDDs are conncted to the SATA plugs...
Of course, the SSD and the HDDs are plugged to the SATA. The only thing in a PCI slot is the nvidia card. The other PCI slots are empty. -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/9/19 11:21 pm, Daniel Bauer wrote:
Am 09.09.19 um 12:33 schrieb Basil Chupin:
On 9/9/19 6:31 pm, Daniel Bauer wrote:
Am 09.09.19 um 07:18 schrieb Basil Chupin:
More random thoughts on the Saga of Daniel's Nvidia Graphics :-D.
Now, reviewing all the tos/fros re your problem I think it is safe to say that it has all to do with graphics -- be it either the monitor or the nvidia card or the driver(s).
According to you, all seemed well until you upgraded from 42.3 to 15.1 (a clean, new install you say, with the 42.3 root (/) partition formatted before 15.1 was written to it, right?).
The root partition is on the brand new SSD.
At the same time as you upgraded to 15.1 you installed extra RAM (into the correct, clean, slot(s) as per the manual), also installed a 500GB SSD and a new (?size) HDD. This is when the sky fell in, right? :-)
The 500GB SSD is physically plugged where before was the first HDD.
Daniel, I will have to reread tomorrow morning what you wrote. Methinks that we are talking at cross purposes here. I cannot see how you can have an HDD plugged in a *PCIe* slot and which now has the new SDD plugged in -- AND having the nVidia GTX 460 also plugged in in the SECOND *PCIe* slot (which you mention below). HDDs are conncted to the SATA plugs...
Of course, the SSD and the HDDs are plugged to the SATA. The only thing in a PCI slot is the nvidia card. The other PCI slots are empty.
Daniel, is this the SSD 'we' are talking about? (see attached) BC -- A three-year-old boy was examining his testicles while taking a bath. "Mum" he asked, "are these my brains?" "Not yet," she replied.
On Tue, 10 Sep 2019 17:38:07 +1000 Basil Chupin wrote: 8< - - - - - trimmed - - - - - >8
Daniel, is this the SSD 'we' are talking about? (see attached)
8< - - - - - trimmed - - - - - >8 Hi Basil, Daniel, All, I've been watching this thread with interest and realized last night that I have an old laptop which is behaving exactly as Daniel's system seems to be behaving, not only with openSUSE, but with any contemporary (released within the last ~ 1.5 years) distribution that I've installed and tested on it (meaning the experience seems to be desktop agnostic.) It runs beautifully with nouveau, but with any of the available nVidia modules / drivers activated, it becomes unpredictable and unstable, ultimately locking up and requiring a hard reset. The BIOS date is from 2008 and the graphics adapter is a GeForce 9300M GS with 512MB vRAM. The most stable and best behaving distribution on it has been Linux Mint Cinnamon w/ nouveau. My take on this experience is that nVidia has probably chosen not to invest large numbers of development hours into maintaining peak performance and stability on their adapters which are very close to being officially EOL'd (support officially dropped.) regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/9/19 9:37 pm, Carl Hartung wrote:
On Tue, 10 Sep 2019 17:38:07 +1000 Basil Chupin wrote:
8< - - - - - trimmed - - - - - >8
Daniel, is this the SSD 'we' are talking about? (see attached) 8< - - - - - trimmed - - - - - >8
Hi Basil, Daniel, All,
I've been watching this thread with interest and realized last night that I have an old laptop which is behaving exactly as Daniel's system seems to be behaving, not only with openSUSE, but with any contemporary (released within the last ~ 1.5 years) distribution that I've installed and tested on it (meaning the experience seems to be desktop agnostic.) It runs beautifully with nouveau, but with any of the available nVidia modules / drivers activated, it becomes unpredictable and unstable, ultimately locking up and requiring a hard reset. The BIOS date is from 2008 and the graphics adapter is a GeForce 9300M GS with 512MB vRAM. The most stable and best behaving distribution on it has been Linux Mint Cinnamon w/ nouveau. My take on this experience is that nVidia has probably chosen not to invest large numbers of development hours into maintaining peak performance and stability on their adapters which are very close to being officially EOL'd (support officially dropped.)
regards,
Carl
Hi Carl, As you would already know a list of drivers which are no longer maintained by nVidia are listed at- https://devtalk.nvidia.com/default/topic/533434/linux/current-graphics-drive... The driver for your 9300M is one of them but the one for GTX460 which Daniel is using is still maintained (390.129). So why Daniel is having such a problem with graphics will remain a mystery... BC -- A three-year-old boy was examining his testicles while taking a bath. "Mum" he asked, "are these my brains?" "Not yet," she replied. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 11 Sep 2019 14:08:30 +1000 Basil Chupin wrote:
On 10/9/19 9:37 pm, Carl Hartung wrote:
On Tue, 10 Sep 2019 17:38:07 +1000 Basil Chupin wrote:
8< - - - - - trimmed - - - - - >8
Daniel, is this the SSD 'we' are talking about? (see attached) 8< - - - - - trimmed - - - - - >8
Hi Basil, Daniel, All,
I've been watching this thread with interest and realized last night that I have an old laptop which is behaving exactly as Daniel's system seems to be behaving, not only with openSUSE, but with any contemporary (released within the last ~ 1.5 years) distribution that I've installed and tested on it (meaning the experience seems to be desktop agnostic.) It runs beautifully with nouveau, but with any of the available nVidia modules / drivers activated, it becomes unpredictable and unstable, ultimately locking up and requiring a hard reset. The BIOS date is from 2008 and the graphics adapter is a GeForce 9300M GS with 512MB vRAM. The most stable and best behaving distribution on it has been Linux Mint Cinnamon w/ nouveau. My take on this experience is that nVidia has probably chosen not to invest large numbers of development hours into maintaining peak performance and stability on their adapters which are very close to being officially EOL'd (support officially dropped.)
regards,
Carl
Hi Carl,
As you would already know a list of drivers which are no longer maintained by nVidia are listed at-
https://devtalk.nvidia.com/default/topic/533434/linux/current-graphics-drive...
The driver for your 9300M is one of them but the one for GTX460 which Daniel is using is still maintained (390.129). So why Daniel is having such a problem with graphics will remain a mystery...
BC
Hi Basil, Thanks for your reply and nice hearing from you! :) Support for my laptop's card isn't officially being dropped until the end of this year, but the "Legacy" driver actually stopped being useful on that system about a year and a half ago. Since that time only nouveau has functioned consistently and reliably well. Do I suspect this outcome may have arisen due to some internal cost calculations at nVidia HQ? Yes. Hopefully, Daniel's experience will ultimately be better since support for his card (albeit also via a "Legacy" driver) doesn't lapse until the end of 2022. In any event, my first point was that, as time recedes and hardware ages, there will be diminishing resources devoted to supporting it. This is obvious. My second point was to highlight the historically atypical similarity between Daniel's and my experiences; the nouveau driver working well as compared to the proprietary one. regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/09/2019 10.31, Daniel Bauer wrote:
I really cannot understand why even self-compiled Nvidia driver causes hassles but a nouveau driver (appears) to 'work' OK. Something not quite right...
Neither do I.
Nouveau doesn't support 3D. Which means, KDE can not try use it. So, it works. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Am 09.09.19 um 13:40 schrieb Carlos E. R.:
On 09/09/2019 10.31, Daniel Bauer wrote:
I really cannot understand why even self-compiled Nvidia driver causes hassles but a nouveau driver (appears) to 'work' OK. Something not quite right...
Neither do I.
Nouveau doesn't support 3D. Which means, KDE can not try use it. So, it works.
I have installed "Mesa-dri-nouveau" which gives 3D. I think the "wobbling windows" desktop effect uses it. It works... -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/9/19 11:25 pm, Daniel Bauer wrote:
Am 09.09.19 um 13:40 schrieb Carlos E. R.:
On 09/09/2019 10.31, Daniel Bauer wrote:
I really cannot understand why even self-compiled Nvidia driver causes hassles but a nouveau driver (appears) to 'work' OK. Something not quite right...
Neither do I.
Nouveau doesn't support 3D. Which means, KDE can not try use it. So, it works.
I have installed "Mesa-dri-nouveau" which gives 3D. I think the "wobbling windows" desktop effect uses it. It works...
Curiouser and curiouser... When installing the mesa driver there is a warning to say that the driver is experimental and that it is known to have problems with nVidia cards... But, hey, if it works for you, fine :-). BC -- A three-year-old boy was examining his testicles while taking a bath. "Mum" he asked, "are these my brains?" "Not yet," she replied. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/08/2019 08:12 AM, Daniel Bauer wrote:
So far it works with nouveau but I am not sure if nouveau renders the colors in a bit a different way. It's hard to say because I cannot have both at the same time to really compare. I just have the impression that colors are a bit less vivid now - colors are important for my work, of course.
What I can say for sure is that nouveau renders differently at least the font I use in email, it's obvious.
I have run nouveau in the past (since I don't game, it makes no difference what I run). I guess you are seeing the font differences in a just had Nvidia/now have Nouveau comparison. In just using one or the other, I really didn't pick up on any differences, but... I never did a change from one to the other. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin composed on 2019-09-08 04:47 (UTC-0500):
Secondly, according to the dmesg.txt/messages.txt you "posted" your motherboard is a Gigabyte X58A-UD3R which has 6 slots for RAM. When you added the new RAM-- (a) was it matched to the old RAM you had installed?;
The old Ram have been 2 slots of 8, now its 3 slots of 8
Yikes,
Double-triple check this in your manual. Generally in the 2010 vintage motherboards, you would install RAM in pairs to provide Dual-Channel capability enabling the RAM to use double the single-chip memory width.
So if you have 2-sticks attempting to run in dual-channel mode and 1 new stick that has no way to run in dual-channel mode -- I can see that causing issues.
The mobo should be smart enough to disable dual-channel all the way around, enabling your setup to run, but you need to check.
Three sticks are fine in a triple channel motherboard as OP has, as long as the sticks match. https://www.gigabyte.com/us/Motherboard/GA-X58A-UD3R-rev-20 https://en.wikipedia.org/wiki/Multi-channel_memory_architecture#Triple-chann... -- Evolution as taught in public schools is religion, not science. 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
participants (10)
-
Basil Chupin
-
Carl Hartung
-
Carlos E. R.
-
Daniel Bauer
-
David C. Rankin
-
Felix Miata
-
James Knott
-
jdd@dodin.org
-
Patrick Shanahan
-
stakanov