Here is the result of "grep EE /var/log/Xorg.0.log" :
(WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 350.468] (EE) Failed to load module "nv" (module does not exist, 0) [ 350.472] (EE) Failed to load module "vesa" (module does not exist, 0) [ 350.501] (EE) [drm] Failed to open DRM device for (null): -22 [ 350.502] (EE) [drm] Failed to open DRM device for pci:0000:02:00.0: -22 [ 350.503] (EE) Unable to find a valid framebuffer device [ 350.504] (EE) Screen 0 deleted because of no matching config section. [ 350.520] (II) Initializing extension MIT-SCREEN-SAVER [ 350.525] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
Shame on me, many errors. I want to install the nvidia driver non-free, this one is installed, downloaded on nvidia site : "NVIDIA-Linux-x86-340.107.run"
Thanks, regards.
André
Anno domini 2019 Wed, 13 Nov 10:04:39 +0100 ajh-valmer scripsit:
Here is the result of "grep EE /var/log/Xorg.0.log" :
(WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 350.468] (EE) Failed to load module "nv" (module does not exist, 0) [ 350.472] (EE) Failed to load module "vesa" (module does not exist, 0) [ 350.501] (EE) [drm] Failed to open DRM device for (null): -22 [ 350.502] (EE) [drm] Failed to open DRM device for pci:0000:02:00.0: -22 [ 350.503] (EE) Unable to find a valid framebuffer device [ 350.504] (EE) Screen 0 deleted because of no matching config section. [ 350.520] (II) Initializing extension MIT-SCREEN-SAVER [ 350.525] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
Shame on me, many errors. I want to install the nvidia driver non-free, this one is installed, downloaded on nvidia site : "NVIDIA-Linux-x86-340.107.run"
eek! uninstall anything nvoidia, reboot, if X comes up you can try to reinstall the nvidia drivers.
Thanks, regards.
André
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Anno domini 2019 Wed, 13 Nov 10:11:40 +0100 Dr. Nikolaus Klepp scripsit:
Anno domini 2019 Wed, 13 Nov 10:04:39 +0100 ajh-valmer scripsit:
Here is the result of "grep EE /var/log/Xorg.0.log" :
(WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 350.468] (EE) Failed to load module "nv" (module does not exist, 0) [ 350.472] (EE) Failed to load module "vesa" (module does not exist, 0) [ 350.501] (EE) [drm] Failed to open DRM device for (null): -22 [ 350.502] (EE) [drm] Failed to open DRM device for pci:0000:02:00.0: -22 [ 350.503] (EE) Unable to find a valid framebuffer device [ 350.504] (EE) Screen 0 deleted because of no matching config section. [ 350.520] (II) Initializing extension MIT-SCREEN-SAVER [ 350.525] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
Shame on me, many errors. I want to install the nvidia driver non-free, this one is installed, downloaded on nvidia site : "NVIDIA-Linux-x86-340.107.run"
eek! uninstall anything nvoidia, reboot, if X comes up you can try to reinstall the nvidia drivers.
forgot: you might want to delete /etc/X11/xorg.conf , too.
Thanks, regards.
André
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Wed, 13 Nov 2019 10:04:39 +0100 "ajh-valmer" ajh.valmer@free.fr wrote:
Here is the result of "grep EE /var/log/Xorg.0.log" :
(WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 350.468] (EE) Failed to load module "nv" (module does not exist, 0) [ 350.472] (EE) Failed to load module "vesa" (module does not exist, 0) [ 350.501] (EE) [drm] Failed to open DRM device for (null): -22 [ 350.502] (EE) [drm] Failed to open DRM device for pci:0000:02:00.0: -22 [ 350.503] (EE) Unable to find a valid framebuffer device [ 350.504] (EE) Screen 0 deleted because of no matching config section. [ 350.520] (II) Initializing extension MIT-SCREEN-SAVER [ 350.525] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
Shame on me, many errors. I want to install the nvidia driver non-free, this one is installed, downloaded on nvidia site : "NVIDIA-Linux-x86-340.107.run"
Oops. Never install nvidia .run files in debian, ever. You fuck up all the gl redirection libs this way. Only install nvidia drivers from debian repo (self compile using apt-src from experimental if you really need the latest ones). You now need to uninstall using nvidia installer, force reinstall all the gl related stuff (mesa, etc), than install nvidia drivers from repo.
On Wednesday 13 November 2019 04:40:53 am Nick Koretsky wrote:
On Wed, 13 Nov 2019 10:04:39 +0100
"ajh-valmer" ajh.valmer@free.fr wrote:
Here is the result of "grep EE /var/log/Xorg.0.log" :
(WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 350.468] (EE) Failed to load module "nv" (module does not exist, 0) [ 350.472] (EE) Failed to load module "vesa" (module does not exist, 0) [ 350.501] (EE) [drm] Failed to open DRM device for (null): -22 [ 350.502] (EE) [drm] Failed to open DRM device for pci:0000:02:00.0: -22 [ 350.503] (EE) Unable to find a valid framebuffer device [ 350.504] (EE) Screen 0 deleted because of no matching config section. [ 350.520] (II) Initializing extension MIT-SCREEN-SAVER [ 350.525] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
Shame on me, many errors. I want to install the nvidia driver non-free, this one is installed, downloaded on nvidia site : "NVIDIA-Linux-x86-340.107.run"
Oops. Never install nvidia .run files in debian, ever. You fuck up all the gl redirection libs this way. Only install nvidia drivers from debian repo (self compile using apt-src from experimental if you really need the latest ones). You now need to uninstall using nvidia installer, force reinstall all the gl related stuff (mesa, etc), than install nvidia drivers from repo.
From personal experience with MX Linux (non-systemd Debian 9 stretch), I concur with Nik and Nick (and I'll add nvidia is a twitchy little asshat).
- Get a working system with nouveau. - Install nvidia only from repo.
You probably can find info on the MX forums on how to completely remove nvidia. Thankfully when I needed to do it the MX script 'just' worked, so I can't give you any specifics.
Best, Michael
Michael composed on 2019-11-13 08:48 (UTC-0600):
From personal experience with MX Linux (non-systemd Debian 9 stretch), I concur with Nik and Nick (and I'll add nvidia is a twitchy little asshat).
- Get a working system with nouveau.
Or not. Do not confuse the nouveau kernel driver with the nouveau DDX (X and Wayland) driver. The nouveau kernel driver provides the kernel mode setting functionality that competent DDXes depend on.
Xserver-xorg-video-nouveau is a reverse-engineered, *optional*, DDX built only for NVidia GPUs. The default DDX is newer technology, automatically used when: 1-it supports any non-ancient (AMD or Intel or NVidia) GPU; 2-KMS is not disabled; and 3-no optional DDX is installed. It can also be explicitly configured to be used even though an applicable optional DDX is available. It's provided by the xserver-org package itself. When in use, modeset(0) will normally be found copiously in Xorg.0.log.
The modesetting DDX is in use here by all the NVidia GPUs I have that are new enough for it to support, those newer than approximately 10-12 years of age.
On Wednesday 13 November 2019 01:49:55 pm Felix Miata wrote:
Michael composed on 2019-11-13 08:48 (UTC-0600):
From personal experience with MX Linux (non-systemd Debian 9 stretch), I concur with Nik and Nick (and I'll add nvidia is a twitchy little asshat).
- Get a working system with nouveau.
Or not. Do not confuse the nouveau kernel driver with the nouveau DDX (X and Wayland) driver. The nouveau kernel driver provides the kernel mode setting functionality that competent DDXes depend on.
Xserver-xorg-video-nouveau is a reverse-engineered, *optional*, DDX built only for NVidia GPUs. The default DDX is newer technology, automatically used when: 1-it supports any non-ancient (AMD or Intel or NVidia) GPU; 2-KMS is not disabled; and 3-no optional DDX is installed. It can also be explicitly configured to be used even though an applicable optional DDX is available. It's provided by the xserver-org package itself. When in use, modeset(0) will normally be found copiously in Xorg.0.log.
The modesetting DDX is in use here by all the NVidia GPUs I have that are new enough for it to support, those newer than approximately 10-12 years of age.
Thank you Felix!
Old mainframe guys like myself probably shouldn't be giving GPU advice ;)
On Wednesday 13 November 2019 21:13:32 Michael wrote:
- Get a working system with nouveau.
Or not. Do not confuse the nouveau kernel driver with the nouveau DDX (X and Wayland) driver. The nouveau kernel driver provides the kernel mode setting functionality that competent DDXes depend on. Xserver-xorg-video-nouveau is a reverse-engineered, *optional*, DDX built only for NVidia GPUs. The default DDX is newer technology, automatically used when: 1-it supports any non-ancient (AMD or Intel or NVidia) GPU; 2-KMS is not disabled; and 3-no optional DDX is installed. It can also be explicitly configured to be used even though an applicable optional DDX is available. It's provided by the xserver-org package itself. When in use, modeset(0) will normally be found copiously in Xorg.0.log. The modesetting DDX is in use here by all the NVidia GPUs I have that are new enough for it to support, those newer than approximately 10-12 years of age.
Old mainframe guys like myself probably shouldn't be giving GPU advice ;)
It worked perfectly with Stretch, nvidia non free and xserver-xorg, and with Buster, completely broken.
I tried, nvidia free and non-free, no result.
I cannot spend hours and hours to repair...
André
On Wed, 13 Nov 2019 22:05:06 +0100 "ajh-valmer" ajh.valmer@free.fr wrote:
On Wednesday 13 November 2019 21:13:32 Michael wrote:
- Get a working system with nouveau.
Or not. Do not confuse the nouveau kernel driver with the nouveau DDX (X and Wayland) driver. The nouveau kernel driver provides the kernel mode setting functionality that competent DDXes depend on. Xserver-xorg-video-nouveau is a reverse-engineered, *optional*, DDX built only for NVidia GPUs. The default DDX is newer technology, automatically used when: 1-it supports any non-ancient (AMD or Intel or NVidia) GPU; 2-KMS is not disabled; and 3-no optional DDX is installed. It can also be explicitly configured to be used even though an applicable optional DDX is available. It's provided by the xserver-org package itself. When in use, modeset(0) will normally be found copiously in Xorg.0.log. The modesetting DDX is in use here by all the NVidia GPUs I have that are new enough for it to support, those newer than approximately 10-12 years of age.
Old mainframe guys like myself probably shouldn't be giving GPU advice ;)
It worked perfectly with Stretch, nvidia non free and xserver-xorg, and with Buster, completely broken.
I tried, nvidia free and non-free, no result.
I cannot spend hours and hours to repair...
First, do you have the correct driver package? There are ~7 nVidia proprietary driver series, each of which supports different cards. If you're not sure, check http://us.download.nvidia.com/XFree86/Linux-x86_64/430.50/README/supportedch...
Having the wrong driver, or parts of it not correcty installed, might create the symptoms you're seeing. Newer cards will sometimes work with older drivers, but it isn't guaranteed.
Keep in mind that, in addition to matching the card you're using, the driver must support your kernel version *and* your X server version. That's why it's safest to install from your distro's repository if you're going to use the nVidia proprietary drivers—they should have those details worked out for you.
Nouveau isn't a perfect solution either. It doesn't support the full range of nVidia cards, or the full range of features on every card it does handle, and it doesn't play nice with TDE if compiled into the kernel—you have to ensure it was built as a module. And you can't have it installed on the same system as the proprietary driver at the same time without blacklisting one kernel module or the other.
Your ultimate fallback is the vesa driver. Make sure it's installed. It should be enough for you to be able to bring up a graphical desktop in a pinch.
(Source: I have one desktop with a recent nVidia card running the proprietary driver, and one laptop with an ancient nVidia card that I transitioned to nouveau last year. Both run TDE. I have committed just about every possible nVidia-related idiocy at one time or another. However, I'm on a different distro from you, so my insight is a bit limited.)
E. Liddell
Thanks for your help.
I made a complete reset (purge) of xserver-xorg, nvidia and by nvidia-uninstall. I choosed the nvidia driver free. At reboot, victory ! It works.
Many configurations were lost by buster, long time to return them.
I think (maybe) that the non-free driver of nvidia, can not work with buster or the buster kernel 4.19.
Regards,
André
What graphics card do you have? Buster ships with newer drivers and it is possible that:
1. You card is now old enough that support for it has been moved to the legacy driver package 2. Documentation claims that your card is now old enough that support for it has been moved to the legacy package, but despite these claims in the documentation that is not the case.
I had (2) happen to me during upgrade, i.e. documentation said that my card is now supported by the legacy driver, but after spending hours on trying to get graphics running it turned out that this is not the case and my card is still supported by the main driver.
Janek
-
ajh-valmer -
deloptes -
Dr. Nikolaus Klepp -
E. Liddell -
Felix Miata -
Janek S. -
Michael -
Nick Koretsky