Le 05/05/2019 à 20:43, Felix Miata a écrit :
> Erwan David composed on 2019-05-05 15:01 (UTC+0200):
>
>> ...the nvidia driver does not work (at least with the modesetting DDX).
> The featured component of an NVidia "driver" installation is its DDX. If
> you're
> using NVidia's proprietary "driv
Erwan David composed on 2019-05-05 15:01 (UTC+0200):
> ...the nvidia driver does not work (at least with the modesetting DDX).
The featured component of an NVidia "driver" installation is its DDX. If you're
using NVidia's proprietary "driver", you're not using the modesetting DDX or the
nouveau
Le 05/05/2019 à 11:52, Felix Miata a écrit :
>> will renaming my .kde directory to something else be sufficient for a test
> Highly unlikely. KDE rudely mixes most of its settings with other apps in
> ~/.config/. I don't think ~/.kde/ is used at all any more. Better to create a
> new
> user for
Le 05/05/2019 à 13:08, Ivan Ivanov a écrit :
> fglrx is a really old proprietary AMD driver which does not work on
> anything newer than Ubuntu 14.04.4 . Perhaps AMD was disgusted by it
> as well, because they abandoned it and created a really good
> replacement opensource driver - that's working
Le 05/05/2019 à 12:58, Ivan Ivanov a écrit :
> AMD has a really great opensource graphic drivers, so maybe just
> change your GPU ? To solve this kind of problems once and forever...
>
It is a laptop, so not possible. (and I had bad experience with fglrx
drivers, but it may have changed)
> will renaming my .kde directory to something else be sufficient for a test
Highly unlikely. KDE rudely mixes most of its settings with other apps in
~/.config/. I don't think ~/.kde/ is used at all any more. Better to create a
new
user for testing to see if the problem survives there. If the pr
Erwan David composed on 2019-05-04 22:06 (UTC+0200):
>> Have you tried disabling compositing in systemsettings5?
> No, but has it an effect on the globall display ?
It can reduce overhead and make problems go away. It can serve as a
troubleshooting step, as simple to engage as disengage.
>> D
Le 04/05/2019 à 21:33, Felix Miata a écrit :
> Erwan David composed on 2019-05-04 20:52 (UTC+0200):
>
I have some display problems
> ...
>> Graphics: Device-1: NVIDIA GF108M [NVS 5400M] vendor: Lenovo driver:
>> nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0def
>> Display: x11
Erwan David composed on 2019-05-04 20:52 (UTC+0200):
>>> I have some display problems
...
> Graphics: Device-1: NVIDIA GF108M [NVS 5400M] vendor: Lenovo driver:
> nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0def
> Display: x11 server: X.Org 1.20.3 driver: modesetting
> unloaded: fb
Le 04/05/2019 à 20:24, Felix Miata a écrit :
> Erwan David composed on 2019-05-04 20:06 (UTC+0200):
>
>> I have some display problems, I thought I was using the
>> nvidia-legacy-39xx driver (the packages are installed) but I see the
>> nouveau module loaded.
>> How can I check wether I use the no
Erwan David composed on 2019-05-04 20:06 (UTC+0200):
> I have some display problems, I thought I was using the
> nvidia-legacy-39xx driver (the packages are installed) but I see the
> nouveau module loaded.
> How can I check wether I use the nouveau driver or not, and how can I
> switch the used
11 matches
Mail list logo
