Re: Are there Nvidia drivers on Trixie repositories right now ?
On 27/7/23 16:10, rudu wrote: Le 26/07/2023 à 23:16, Greg Wooledge a écrit : On Wed, Jul 26, 2023 at 11:15:13PM +0200, rudu wrote: Thank you David, but I thought that non-free-firmware should be enough for the new testing repositories. Should I had "non-free" to "main contrib non-free-firmware" ? Sounds weird to me ... ?? The non-free-firmware section only contains firmware. Not drivers. If you need to build non-free drivers (e.g. nvidia) you'll need both sections. Thanks to David and Greg, I finally understood the difference between firmwares and drivers ... ;) Indeed adding the non-free section to my source.list was what I needed. Sorry for the noise. Nice Day to all Rudu I believe that a proverb exists, with wording something like "It is better to look a fool for the time that it takes to ask a question, than to look a fool forever, for not asking the question.". If you did not ask, you would not have learned, and, your having asked, can mean that others can also learn what you have learned, from your having asked the question. People should never have to apologise for asking to learn what they do not know. .. Bret Busby Armadale West Australia (UTC+0800) ..
Re: Are there Nvidia drivers on Trixie repositories right now ?
Le 26/07/2023 à 23:16, Greg Wooledge a écrit : On Wed, Jul 26, 2023 at 11:15:13PM +0200, rudu wrote: Thank you David, but I thought that non-free-firmware should be enough for the new testing repositories. Should I had "non-free" to "main contrib non-free-firmware" ? Sounds weird to me ... ?? The non-free-firmware section only contains firmware. Not drivers. If you need to build non-free drivers (e.g. nvidia) you'll need both sections. Thanks to David and Greg, I finally understood the difference between firmwares and drivers ... ;) Indeed adding the non-free section to my source.list was what I needed. Sorry for the noise. Nice Day to all Rudu
Re: Are there Nvidia drivers on Trixie repositories right now ?
On Wed, Jul 26, 2023 at 11:15:13PM +0200, rudu wrote: > Thank you David, but I thought that non-free-firmware should be enough for > the new testing repositories. > Should I had "non-free" to "main contrib non-free-firmware" ? > Sounds weird to me ... ?? The non-free-firmware section only contains firmware. Not drivers. If you need to build non-free drivers (e.g. nvidia) you'll need both sections.
Re: Are there Nvidia drivers on Trixie repositories right now ?
Le 26/07/2023 à 17:12, David Wright a écrit : # cat /etc/apt/sources.list # deb cdrom:[Debian GNU/Linux testing_Bookworm_ - Official Snapshot amd64 NETINST 20221031-03:18]/ bookworm main #deb cdrom:[Debian GNU/Linux testing_Bookworm_ - Official Snapshot amd64 NETINST 20221031-03:18]/ bookworm main debhttp://ftp.fr.debian.org/debian trixie main contrib non-free-firmware deb-srchttp://ftp.fr.debian.org/debian trixie main contrib non-free-firmware debhttp://ftp.fr.debian.org/debian-security/ trixie-security main contrib non-free-firmware deb-srchttp://ftp.fr.debian.org/debian-security/ trixie-security main contrib non-free-firmware debhttp://ftp.fr.debian.org/debian trixie-updates main contrib non-free-firmware deb-srchttp://ftp.fr.debian.org/debian trixie-updates main contrib non-free-firmware You appear to be lacking non-free in your sources.list. Cheers, David. Thank you David, but I thought that non-free-firmware should be enough for the new testing repositories. Should I had "non-free" to "main contrib non-free-firmware" ? Sounds weird to me ... ?? Rudu
Re: Are there Nvidia drivers on Trixie repositories right now ?
On Wed 26 Jul 2023 at 15:39:49 (+0200), rudu wrote: > Switching from the nouveau driver to some nvidia-driver does not seam > to be possible on my laptop running Debian Testing/Trixie. > Now, it can be found right here apparently : > https://packages.debian.org/trixie/nvidia-driver > Am I missing something ? > # cat /etc/apt/sources.list > # deb cdrom:[Debian GNU/Linux testing _Bookworm_ - Official Snapshot > amd64 NETINST 20221031-03:18]/ bookworm main > > #deb cdrom:[Debian GNU/Linux testing _Bookworm_ - Official Snapshot > amd64 NETINST 20221031-03:18]/ bookworm main > > deb http://ftp.fr.debian.org/debian trixie main contrib non-free-firmware > deb-src http://ftp.fr.debian.org/debian trixie main contrib > non-free-firmware > > deb http://ftp.fr.debian.org/debian-security/ trixie-security main > contrib non-free-firmware > deb-src http://ftp.fr.debian.org/debian-security/ trixie-security main > contrib non-free-firmware > > deb http://ftp.fr.debian.org/debian trixie-updates main contrib > non-free-firmware > deb-src http://ftp.fr.debian.org/debian trixie-updates main contrib > non-free-firmware You appear to be lacking non-free in your sources.list. Cheers, David.
Are there Nvidia drivers on Trixie repositories right now ?
Hi there, Switching from the nouveau driver to some nvidia-driver does not seam to be possible on my laptop running Debian Testing/Trixie. Now, it can be found right here apparently : https://packages.debian.org/trixie/nvidia-driver Am I missing something ? Some information about my system is following, just ask for more if needed. Thanks Rudu $ LANG=C inxi -G Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel Device-2: NVIDIA GM204GLM [Quadro M3000M] driver: nouveau v: kernel Device-3: Bison ThinkPad P50 Integrated Camera driver: uvcvideo type: USB Display: server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris,nouveau gpu: i915 tty: 158x38 resolution: 1920x1080 API: OpenGL Message: GL data unavailable in console. Try -G --display $ LANG=C nvidia-detect Detected NVIDIA GPUs: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204GLM [Quadro M3000M] [10de:13fa] (rev a1) Checking card: NVIDIA Corporation GM204GLM [Quadro M3000M] (rev a1) Uh oh. Failed to identify your Debian suite. # LANG=C apt policy nvidia-driver nvidia-driver: Installed: (none) Candidate: (none) Version table: # cat /etc/apt/sources.list # deb cdrom:[Debian GNU/Linux testing _Bookworm_ - Official Snapshot amd64 NETINST 20221031-03:18]/ bookworm main #deb cdrom:[Debian GNU/Linux testing _Bookworm_ - Official Snapshot amd64 NETINST 20221031-03:18]/ bookworm main deb http://ftp.fr.debian.org/debian trixie main contrib non-free-firmware deb-src http://ftp.fr.debian.org/debian trixie main contrib non-free-firmware deb http://ftp.fr.debian.org/debian-security/ trixie-security main contrib non-free-firmware deb-src http://ftp.fr.debian.org/debian-security/ trixie-security main contrib non-free-firmware deb http://ftp.fr.debian.org/debian trixie-updates main contrib non-free-firmware deb-src http://ftp.fr.debian.org/debian trixie-updates main contrib non-free-firmware # This system was installed using small removable media # (e.g. netinst, live or single CD). The matching "deb cdrom" # entries were disabled at the end of the installation process. # For information about how to configure apt package sources, # see the sources.list(5) manual.
Re: Trouble with nvidia drivers in Debian 12 Bookworm
Solved my own problem: I had to do `apt install linux-headers-cloud-amd64` instead of `apt install linux-headers-amd64` On Thu, Jul 13, 2023 at 2:28 PM Sam Clearman wrote: > > Hi, > I'm trying to get a Tesla T4 working under Debian 12. > > So far I've tried two approaches: > 1. Using the Debian provided drivers, per > https://wiki.debian.org/NvidiaGraphicsDrivers > 2. Using the nVidia provided drivers installed via runfile, per > https://docs.nvidia.com/datacenter/tesla/tesla-installation-notes/index.html > > For 1 (installing the drivers in the debian nonfree repository), > everything seems to install fine but the drivers don't load properly. > Systemctl returns the following: > > $ systemctl status systemd-modules-load > × systemd-modules-load.service - Load Kernel Modules > Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static) > Active: failed (Result: exit-code) since Thu 2023-07-13 21:05:08 > UTC; 18min ago >Docs: man:systemd-modules-load.service(8) > man:modules-load.d(5) > Process: 220 ExecStart=/lib/systemd/systemd-modules-load > (code=exited, status=1/FAILURE) >Main PID: 220 (code=exited, status=1/FAILURE) > CPU: 29ms > > Jul 13 21:05:08 localhost systemd-modules-load[226]: modprobe: ERROR: > could not insert 'nvidia': Invalid argument > Jul 13 21:05:08 localhost systemd-modules-load[230]: modprobe: FATAL: > Module nvidia-current-modeset not found in directory > /lib/modules/6.1.0-10-cloud-amd64 > Jul 13 21:05:08 localhost systemd-modules-load[223]: modprobe: ERROR: > ../libkmod/libkmod-module.c:1047 command_do() Error running install > command 'modprobe nvidia ; modprobe -i nvidia-current-modeset ' for m> > Jul 13 21:05:08 localhost systemd-modules-load[223]: modprobe: ERROR: > could not insert 'nvidia_modeset': Invalid argument > Jul 13 21:05:08 localhost systemd-modules-load[232]: modprobe: FATAL: > Module nvidia-current-drm not found in directory > /lib/modules/6.1.0-10-cloud-amd64 > Jul 13 21:05:08 localhost systemd-modules-load[220]: Error running > install command 'modprobe nvidia-modeset ; modprobe -i > nvidia-current-drm ' for module nvidia_drm: retcode 1 > Jul 13 21:05:08 localhost systemd-modules-load[220]: Failed to insert > module 'nvidia_drm': Invalid argument > Jul 13 21:05:08 localhost systemd[1]: systemd-modules-load.service: > Main process exited, code=exited, status=1/FAILURE > Jul 13 21:05:08 localhost systemd[1]: systemd-modules-load.service: > Failed with result 'exit-code'. > Jul 13 21:05:08 localhost systemd[1]: Failed to start > systemd-modules-load.service - Load Kernel Modules. > > When I try to use the runfile (specifically, this file: > https://us.download.nvidia.com/tesla/535.54.03/NVIDIA-Linux-x86_64-535.54.03.run) > it is unable to read the kernel headers that I have installed (if I > don't specify a location, it says it can't find them, no matter which > location I specify, it finds something unexpected about what's there). > > Any help is appreciated! > > PS: Secureboot is disabled, I get the following from mokutil: > $ mokutil --sb-state > SecureBoot disabled
Trouble with nvidia drivers in Debian 12 Bookworm
Hi, I'm trying to get a Tesla T4 working under Debian 12. So far I've tried two approaches: 1. Using the Debian provided drivers, per https://wiki.debian.org/NvidiaGraphicsDrivers 2. Using the nVidia provided drivers installed via runfile, per https://docs.nvidia.com/datacenter/tesla/tesla-installation-notes/index.html For 1 (installing the drivers in the debian nonfree repository), everything seems to install fine but the drivers don't load properly. Systemctl returns the following: $ systemctl status systemd-modules-load × systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static) Active: failed (Result: exit-code) since Thu 2023-07-13 21:05:08 UTC; 18min ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 220 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 220 (code=exited, status=1/FAILURE) CPU: 29ms Jul 13 21:05:08 localhost systemd-modules-load[226]: modprobe: ERROR: could not insert 'nvidia': Invalid argument Jul 13 21:05:08 localhost systemd-modules-load[230]: modprobe: FATAL: Module nvidia-current-modeset not found in directory /lib/modules/6.1.0-10-cloud-amd64 Jul 13 21:05:08 localhost systemd-modules-load[223]: modprobe: ERROR: ../libkmod/libkmod-module.c:1047 command_do() Error running install command 'modprobe nvidia ; modprobe -i nvidia-current-modeset ' for m> Jul 13 21:05:08 localhost systemd-modules-load[223]: modprobe: ERROR: could not insert 'nvidia_modeset': Invalid argument Jul 13 21:05:08 localhost systemd-modules-load[232]: modprobe: FATAL: Module nvidia-current-drm not found in directory /lib/modules/6.1.0-10-cloud-amd64 Jul 13 21:05:08 localhost systemd-modules-load[220]: Error running install command 'modprobe nvidia-modeset ; modprobe -i nvidia-current-drm ' for module nvidia_drm: retcode 1 Jul 13 21:05:08 localhost systemd-modules-load[220]: Failed to insert module 'nvidia_drm': Invalid argument Jul 13 21:05:08 localhost systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Jul 13 21:05:08 localhost systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. Jul 13 21:05:08 localhost systemd[1]: Failed to start systemd-modules-load.service - Load Kernel Modules. When I try to use the runfile (specifically, this file: https://us.download.nvidia.com/tesla/535.54.03/NVIDIA-Linux-x86_64-535.54.03.run) it is unable to read the kernel headers that I have installed (if I don't specify a location, it says it can't find them, no matter which location I specify, it finds something unexpected about what's there). Any help is appreciated! PS: Secureboot is disabled, I get the following from mokutil: $ mokutil --sb-state SecureBoot disabled
Re: Authentication required message window after nvidia drivers installation.
The problem was what the message was about, there was a problem with the login keyring. Usually, the login keyring has the same password as the user's account. For some reason this had somehow changed in my case, and since I could not remember the login keyring password, I deleted it. I have a GNOME desktop environment, and the installation of Nvidia drivers somehow made it get activated in the cases I mentioned earlier. On Fri, Jan 21, 2022 at 3:24 PM Thanos Katsiolis wrote: > Hello, > > the title of the post says pretty much everything. > I have the NVIDIA Quadro P400 graphics card and installed the NVIDIA > drivers as described in Debian wiki NVIDIA Proprietary Driver > <https://wiki.debian.org/NvidiaGraphicsDrivers> for Debian 11.2. > > The message appears when an Application starts or when a window from an > application opens. Some applications were left with a blank screen > when launching, but after a restart, when I press escape on the message, > the application starts normally. > Any ideas on how to fix it? >
Re: Authentication required message window after nvidia drivers installation.
The problem was what the message was about, there was a problem with the login keyring. Usually, the login keyring has the same password with the user's account. For some reason this had somehow changed in my case, and since I could not remember the login keyring password, I deleted it. I have GNOME desktop environment, and the installation of Nvidia drivers somehow made it get activated in the cases I mention earlier. >
Re: Authentication required message window after nvidia drivers installation.
Hello Andrei, thank you for your answer, and sorry for my late answer, but today again I have access to this machine. On Sat, Jan 22, 2022 at 9:51 AM Andrei POPESCU wrote: > > This is likely completely unrelated to installing the NVIDIA drivers. > > I am certain that it has to be something with the NVIDIA drivers installation, because this started immediately after installing the drivers. For over a month that the drivers were not installed, there was no problem. > Please provide more information about your Desktop Environment and the > applications that exhibit this behaviour. > > Any other non-Debian software on the system? > I use the GNOME Wayland. Furthermore, there are various applications that exhibit this behavior like Spotify, Skype and PyCharm. The message appears when an application launches or when it opens a new window and not while using the application, for example when browsing Spotify. > > The output of 'id' in a terminal might provide some hints as well (feel > free to obscure your user and group name, the interesting part is what > other groups, if any, your user is a member of). > > The output of the command says that me account is also part of a group. This is not a home setup. Can should I see particularly from 'id'? > Kind regards, > Andrei > -- > http://wiki.debian.org/FAQsFromDebianUser Kind regards, - Thanos.
Re: Authentication required message window after nvidia drivers installation.
On Vi, 21 ian 22, 15:24:29, Thanos Katsiolis wrote: > Hello, > > the title of the post says pretty much everything. > I have the NVIDIA Quadro P400 graphics card and installed the NVIDIA > drivers as described in Debian wiki NVIDIA Proprietary Driver > <https://wiki.debian.org/NvidiaGraphicsDrivers> for Debian 11.2. > > The message appears when an Application starts or when a window from an > application opens. Some applications were left with a blank screen > when launching, but after a restart, when I press escape on the message, > the application starts normally. > Any ideas on how to fix it? This is likely completely unrelated to installing the NVIDIA drivers. Please provide more information about your Desktop Environment and the applications that exhibit this behaviour. Any other non-Debian software on the system? The output of 'id' in a terminal might provide some hints as well (feel free to obscure your user and group name, the interesting part is what other groups, if any, your user is a member of). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Authentication required message window after nvidia drivers installation.
Hi, this is certainly very strange behaviour which I never experienced at the time when I was using the NVDIA closed-source drivers. It actually sounds a little bit alarming to me. Regards, Christian On 2022-01-21 14:24 UTC+0100, Thanos Katsiolis wrote: > Hello, > > the title of the post says pretty much everything. > I have the NVIDIA Quadro P400 graphics card and installed the NVIDIA > drivers as described in Debian wiki NVIDIA Proprietary Driver > <https://wiki.debian.org/NvidiaGraphicsDrivers> for Debian 11.2. > > The message appears when an Application starts or when a window from an > application opens. Some applications were left with a blank screen > when launching, but after a restart, when I press escape on the message, > the application starts normally. > Any ideas on how to fix it?
Authentication required message window after nvidia drivers installation.
Hello, the title of the post says pretty much everything. I have the NVIDIA Quadro P400 graphics card and installed the NVIDIA drivers as described in Debian wiki NVIDIA Proprietary Driver <https://wiki.debian.org/NvidiaGraphicsDrivers> for Debian 11.2. The message appears when an Application starts or when a window from an application opens. Some applications were left with a blank screen when launching, but after a restart, when I press escape on the message, the application starts normally. Any ideas on how to fix it?
Re: problemas al compilar nvidia drivers
El jue, 11 nov 2021 a las 21:34, Alejandro G. Sanchez Martinez () escribió: > > Hola tengo una tarjeta de video vieja y necesito los dirver propietarios > de nvidia los 340 pero ya no son soportado por debian bulleye (lastima > que se esta olvidando el soporte para cosas viejas) > > ya desactive los drivers nouvea que al ser utilizados con kdenlive que > es lo que mas me urge utilizar en este momento no puedo compilarlos, el > erro que me arroja es el siguiente: > > echo >&2 " ERROR: Kernel configuration is invalid.";\ > echo >&2 " include/generated/autoconf.h or > include/config/auto.conf are missing.";\ > echo >&2 " Run 'make oldconfig && make prepare' on kernel src > to fix it."; \ > > No se si a alguien le a pasado algo parecido y pueda apoyarme ya que me > urge editar 60 videos y debian no me esta dado el ancho con los driver > libres de nvidia se bloquea muy seguido con el kdenelive. > > Gracias. > > > el kernel que tengo es el que se instalar por default, no esta > recompilado por mi. > > uname -a > 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux > Saldos. Yo estoy en un caso similar al tuyo y resolví el asunto a la "debian way". 1.- Agrega el repositorio de fuentes de sid (en donde todavía están las fuentes debanizadas del controlador NVIDIA viejo) 2.- crea un directorio como usuario no root y entra en el 3.- Baja las fuentes: apt-get source nvidia-graphics-drivers-legacy-340xx 4.- Luego instala las dependencias: apt-get build-dep nvidia-graphics-drivers-legacy-340xx 5.- Entras al directorio que se creó con las fuentes descomprimidas 6.- Ejecutas dpkg-buildpackage -rfakeroot (debes tener instalado fakeroot y las debianutils) 7.- Al terminar la compilacion te deben quedar los archivos .deb del instalador en el directorio padre. Comentarios: Se presentan ciertos fallos e inestabilidades, pero en mi caso puedo obviarlos. Suerte -- Por favor, NO utilice formatos de archivo propietarios para el intercambio de documentos, como DOC y XLS, sino HTML, PDF, TXT, CSV o cualquier otro que no obligue a utilizar un programa de un fabricante en concreto. Internet Explorer y Outlook son muy peligrosos por sus continuos problemas de seguridad. Utilice alternativas libres: http://www.mozillaes.org/ Usuario linux registrado #387231 http://counter.li.org Por favor evite enviar adjuntos de powerpoint y word vea http://www.gnu.org/philosophy/no-word-attachments.es.html
Re: problemas al compilar nvidia drivers
El 2021-11-11 a las 19:12 -0600, Alejandro G. Sanchez Martinez escribió: > Hola tengo una tarjeta de video vieja y necesito los dirver propietarios > de nvidia los 340 pero ya no son soportado por debian bulleye (lastima > que se esta olvidando el soporte para cosas viejas) EL ecosistema linux en general y Debian en particular, suelen ser bastante amables con los viejos componentes, si no está disponible su razón técnica habrá. Los controladores que buscas están en el repositorio de Debian pero para versiones antiguas (buster, strech): https://packages.debian.org/buster/nvidia-legacy-340xx-driver En nVidia indican que la versión 340 (legacy) no admite versiones de kernel modernas, motivo por el cual no está disponible en los repos: https://www.nvidia.com/Download/driverResults.aspx/135161/en-us The 340.xx legacy Unified Memory kernel module is incompatible with recent Linux kernels, and the GPU hardware generations that the 340.xx legacy driver series is intended to support do not support Unified Memory. > ya desactive los drivers nouvea que al ser utilizados con kdenlive que > es lo que mas me urge utilizar en este momento no puedo compilarlos, el > erro que me arroja es el siguiente: > > echo >&2 " ERROR: Kernel configuration is invalid."; \ > echo >&2 " include/generated/autoconf.h or > include/config/auto.conf are missing.";\ > echo >&2 " Run 'make oldconfig && make prepare' on kernel src > to fix it."; \ > > No se si a alguien le a pasado algo parecido y pueda apoyarme ya que me > urge editar 60 videos y debian no me esta dado el ancho con los driver > libres de nvidia se bloquea muy seguido con el kdenelive. > > Gracias. > > > el kernel que tengo es el que se instalar por default, no esta > recompilado por mi. > > uname -a > 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux Mira a ver si lo que comentan en este hilo te sirve o te da alguna pista de dónde buscar: Need 340 driver patch for kernel 5.8 https://forums.developer.nvidia.com/t/need-340-driver-patch-for-kernel-5-8/165517/2 Saludos, -- Camaleón
problemas al compilar nvidia drivers
Hola tengo una tarjeta de video vieja y necesito los dirver propietarios de nvidia los 340 pero ya no son soportado por debian bulleye (lastima que se esta olvidando el soporte para cosas viejas) ya desactive los drivers nouvea que al ser utilizados con kdenlive que es lo que mas me urge utilizar en este momento no puedo compilarlos, el erro que me arroja es el siguiente: echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ No se si a alguien le a pasado algo parecido y pueda apoyarme ya que me urge editar 60 videos y debian no me esta dado el ancho con los driver libres de nvidia se bloquea muy seguido con el kdenelive. Gracias. el kernel que tengo es el que se instalar por default, no esta recompilado por mi. uname -a 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux
What is the average time NVIDIA drivers driving their newest cards reach Debian?
Hello dear Debian users! I'm a long time lurker of this newsletter, and a Debian user for about four years now (on multiple machines). This is my very first post on this legendary mailing list, so please, be forgiving. :) For a couple of last months I've been planning to upgrade my old GTX 660Ti video card to an RTX, mostly because of a real-time ray tracing that RTX cards offer, which is becoming crucial to my work. I was about to purchase an RTX 2070 Super, when I recently read that a new line of RTX 30 cards are about to have their premiere within the next two months. According to GPU Mag[1], the RTX 3070 card, in which I would be interested in the most, will come around October, and two additional months is the time I am willing to wait. But the question is, what is the usual time the newest proprietary NVIDIA drivers drivin' their newest products hit the Debian Testing repo? Over the years, I've learned to recognize NVIDIA as a corporation, which is not a friend of GNU/Linux and the free software movement. Hence, I imagine that pushing their driver to our operating system isn't their biggest priority. If it's a matter of a month or two, I guess I could wait it out. But if it usually takes them over half a year to ship the drivers for their newest cards, then perhaps I should wait for AMD's RDNA2...? What do you think? [1] https://www.gpumag.com/nvidia-geforce-rtx-3000-series/
Why is X loading my Nvidia drivers?
Hi, On my Optimus laptop (with both Intel and Nvidia GPUs), I'm trying to avoid loading the Nvidia drivers on startup (in order to power down the Nvidia card with bbswitch). When I blacklist them in /etc/modprobe.d/, they don't load on boot, but X seems to be loading them, despite the fact that X is using the Intel card. I'm not using an xorg.conf file and there's no mention of nvidia in the Xorg.0.log, but syslog and dmesg show that X is loading the nvidia driver - these lines appear in the logs when I start X: nvidia-nvlink: Nvlink Core is being initialized, major device number 242 NVRM: loading NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31 CDT 2019 Further investigation: lsof /dev | grep nvidia Xorg 8553user 12u CHR 195,255 0t0 40974 /dev/nvidiactl Xorg 8553user 13u CHR 195,0 0t0 38875 /dev/nvidia0 Xorg 8553user 14u CHR 195,0 0t0 38875 /dev/nvidia0 lsmod | grep nvidia nvidia 19111936 9 ipmi_msghandler65536 2 ipmi_devintf,nvidia grep -i nvidia /var/log/Xorg.0.log [no output] grep -i intel /var/log/Xorg.0.log [10.084] (II) modeset(0): glamor X acceleration enabled on Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2) [plus HDA stuff] grep -i modesetting /var/log/Xorg.0.log [ 9.202] (==) Matched modesetting as autoconfigured driver 0 [ 9.202] (II) LoadModule: "modesetting" [ 9.203] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 9.205] (II) Module modesetting: vendor="X.Org Foundation" [ 9.206] (II) modesetting: Driver for Modesetting Kernel Drivers: kms How can I track down and fix what's going on here? Celejar
Re: How to get a clean situation for nvidia drivers
-- Boyan Penkov www.boyanpenkov.com > On Mar 13, 2019, at 07:55, Andrea Borgia wrote: > > Yup, my bad: I assumed that the package still had a reason to be installed. > It might have been a mistake or a requirement of an earlier video card, the > system is more than 10 yrs old and I am not sure anymore if the card is still > the original one. > Hey folks — just a though on this: would it be worth filing a bug against nvidia-checker to have it tell you when you have a non-nvidia card installed, and should look at other drivers? > Thanks. > > Il giorno mer 13 mar 2019 alle ore 12:47 Brad Rogers <mailto:b...@fineby.me.uk>> ha scritto: > On Wed, 13 Mar 2019 12:27:51 +0100 > Andrea Borgia mailto:and...@borgia.bo.it>> wrote: > > Hello Andrea, > > >Perhaps a silly question but... how do I know whether my card is a > > Maybe. > > >[AMD/ATI] RV370 [Radeon X300/X550/X1050 Series] > > .It's a Radeon card. nVidia drivers are worthless to you. > > -- > Regards _ > / ) "The blindingly obvious is > / _)radnever immediately apparent" > No guarantee the stimuli must be perceived the same... > Gary Gilmore's Eyes - The Adverts
Re: How to get a clean situation for nvidia drivers
Good idea, I'll check the metapackage, though. Il giorno mer 13 mar 2019 alle ore 13:17 Brad Rogers ha scritto: > On Wed, 13 Mar 2019 12:55:40 +0100 > Andrea Borgia wrote: > > Hello Andrea, > > >Yup, my bad: I assumed that the package still had a reason to be > >installed. It might have been a mistake or a requirement of an earlier > > The probable reason is that you've got the video drivers metapackage > (exact name escapes me ATM) installed. As a result, all drivers, whether > needed or not, are installed. > > Unless disk space is at a premium, you may as well leave them all in > place. If nothing else, should you need to change your GFX card in > future, no matter from what manufacturer it comes, the drivers will most > likely already be in place. > > -- > Regards _ > / ) "The blindingly obvious is > / _)radnever immediately apparent" > I'm doubling the rent 'coz the building's condemned > Let's Lynch The Landlord - Dead Kennedys >
Re: How to get a clean situation for nvidia drivers
On Wed, 13 Mar 2019 12:55:40 +0100 Andrea Borgia wrote: Hello Andrea, >Yup, my bad: I assumed that the package still had a reason to be >installed. It might have been a mistake or a requirement of an earlier The probable reason is that you've got the video drivers metapackage (exact name escapes me ATM) installed. As a result, all drivers, whether needed or not, are installed. Unless disk space is at a premium, you may as well leave them all in place. If nothing else, should you need to change your GFX card in future, no matter from what manufacturer it comes, the drivers will most likely already be in place. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" I'm doubling the rent 'coz the building's condemned Let's Lynch The Landlord - Dead Kennedys pgp11vJjnbDQ1.pgp Description: OpenPGP digital signature
Re: How to get a clean situation for nvidia drivers
On Wed, Mar 13, 2019 at 12:51:58PM +0100, Andrea Borgia wrote: > Duh :) > Other than feeling a bit stupid [...] Take it easy. Happens to me on a daily basis ;-) On a more positive note, your question and the answers you got might help somebody else to solve their problem... Cheers -- t signature.asc Description: Digital signature
Re: How to get a clean situation for nvidia drivers
Yup, my bad: I assumed that the package still had a reason to be installed. It might have been a mistake or a requirement of an earlier video card, the system is more than 10 yrs old and I am not sure anymore if the card is still the original one. Thanks. Il giorno mer 13 mar 2019 alle ore 12:47 Brad Rogers ha scritto: > On Wed, 13 Mar 2019 12:27:51 +0100 > Andrea Borgia wrote: > > Hello Andrea, > > >Perhaps a silly question but... how do I know whether my card is a > > Maybe. > > >[AMD/ATI] RV370 [Radeon X300/X550/X1050 Series] > > .It's a Radeon card. nVidia drivers are worthless to you. > > -- > Regards _ > / ) "The blindingly obvious is > / _)radnever immediately apparent" > No guarantee the stimuli must be perceived the same... > Gary Gilmore's Eyes - The Adverts >
Re: How to get a clean situation for nvidia drivers
Duh :) Other than feeling a bit stupid, now I have to find out why the system had that package installed. Thanks, Andrea. Il giorno mer 13 mar 2019 alle ore 12:37 ha scritto: > On Wed, Mar 13, 2019 at 12:27:51PM +0100, Andrea Borgia wrote: > > Il giorno mar 12 mar 2019 alle ore 22:34 Boyan Penkov < > > boyan.pen...@gmail.com> ha scritto: > > > > > > > > > I installed nvidia-legacy-390, uninstalled nvidia-legacy-checker, and > my > > > machine survived a reboot with the GUI coming up nicely. > > > > > > > Perhaps a silly question but... how do I know whether my card is a > "Fermi" > > card as the warning in nvidia-graphics-drivers says? > > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > > RV370 [Radeon X300/X550/X1050 Series] > > This one is definitely not: Fermi is an NVIDIA family (well, architecture > [1]), whereas yours is ATI (now part of AMD), which is NVIDIA's rival [2] > > [1] https://en.wikipedia.org/wiki/Fermi_(microarchitecture) > [2] https://en.wikipedia.org/wiki/ATI_Technologies > > Cheers > -- tomás > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.12 (GNU/Linux) > > iEYEARECAAYFAlyI618ACgkQBcgs9XrR2kaByACbBXjFFSkadEHad/uAx+Zi9/K1 > OpUAn0hMx+k/aMQrkiy39Mp0+kCIKoJi > =nLAp > -END PGP SIGNATURE- >
Re: How to get a clean situation for nvidia drivers
On Wed, 13 Mar 2019 12:27:51 +0100 Andrea Borgia wrote: Hello Andrea, >Perhaps a silly question but... how do I know whether my card is a Maybe. >[AMD/ATI] RV370 [Radeon X300/X550/X1050 Series] .It's a Radeon card. nVidia drivers are worthless to you. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" No guarantee the stimuli must be perceived the same... Gary Gilmore's Eyes - The Adverts pgpH3Z_D67qz2.pgp Description: OpenPGP digital signature
Re: How to get a clean situation for nvidia drivers
On Wed, Mar 13, 2019 at 12:27:51PM +0100, Andrea Borgia wrote: > Il giorno mar 12 mar 2019 alle ore 22:34 Boyan Penkov < > boyan.pen...@gmail.com> ha scritto: > > > > > I installed nvidia-legacy-390, uninstalled nvidia-legacy-checker, and my > > machine survived a reboot with the GUI coming up nicely. > > > > Perhaps a silly question but... how do I know whether my card is a "Fermi" > card as the warning in nvidia-graphics-drivers says? > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > RV370 [Radeon X300/X550/X1050 Series] This one is definitely not: Fermi is an NVIDIA family (well, architecture [1]), whereas yours is ATI (now part of AMD), which is NVIDIA's rival [2] [1] https://en.wikipedia.org/wiki/Fermi_(microarchitecture) [2] https://en.wikipedia.org/wiki/ATI_Technologies Cheers -- tomás signature.asc Description: Digital signature
Re: How to get a clean situation for nvidia drivers
Il giorno mar 12 mar 2019 alle ore 22:34 Boyan Penkov < boyan.pen...@gmail.com> ha scritto: > I installed nvidia-legacy-390, uninstalled nvidia-legacy-checker, and my > machine survived a reboot with the GUI coming up nicely. > Perhaps a silly question but... how do I know whether my card is a "Fermi" card as the warning in nvidia-graphics-drivers says? 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300/X550/X1050 Series] Thanks, Andrea.
Re: How to get a clean situation for nvidia drivers
On Wed, 13 Mar 2019 09:35:53 +0100 Erwan David wrote: Hello Erwan, >drivers. However, here I got a system in a dirty state, and no standard >way to get it clean (how can I say "Ok revert the partial installation >and keep the installed version" ?). As it happens, I ended up in a similar position. That is, some v410 stuff installed along side the 390xx-legacy packages. I had to expunge the 410 packages by hand(1), and substitute with the comparable legacy packages. Installing the 390xx drivers metapackage went a long way helping in that regard. Along the way, the legacy nvidia driver got marked for removal, but watching and reading carefully I spotted that, and managed to clear the removal marker without problem(2). I agree that the process could be cleaner, but not being anywhere near knowledgeable enough about the upgrade processes, I have no idea how feasible that is. >I installed the nvidia-legacy-39xx, but I do like doing things like that >in a hurry, I think you meant to say 'I do not like.' and I can't say I blame you. (1) Whether it was strictly necessary, IDK. But as this computer will now forever be on the legacy drivers, nvidia-detect and its ilk are no longer necessary. (2) I find it rather a tense time, after such an update, rebooting the computer to see if I've managed the video driver update process properly, or screwed it up royally, and ended up with no running X. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Looking for something I can call my own Chairman Of The Bored - Crass pgpwCDP2KUv8f.pgp Description: OpenPGP digital signature
Re: How to get a clean situation for nvidia drivers
On 12/03/2019 19:33, Brad Rogers wrote: > On Tue, 12 Mar 2019 19:03:12 +0100 > Erwan David wrote: > > Hello Erwan, > >> And what should I have done ? Install non working drivers ? > You should have read the warning; It tells which version of the legacy > packages you need to install. Yes it does, but once I have said I do not want to install the nvidia-driver package, it then stops with the nvidia packages and several other unrelated packages partially installed. I would have understood, that it stopped, allowing me to do the other upgrades, keeping the nvidia stuff (and what depends on it) at the current version then have a look at the alternatives for the graphic drivers. However, here I got a system in a dirty state, and no standard way to get it clean (how can I say "Ok revert the partial installation and keep the installed version" ?). I installed the nvidia-legacy-39xx, but I do like doing things like that in a hurry, signature.asc Description: OpenPGP digital signature
Re: How to get a clean situation for nvidia drivers
On 3/12/19 2:03 PM, Erwan David wrote: When upgrading my lenovo T530 I was warned that nvidia-driver does not support anymore my graphic card. Thus I chose to not upgrade in the dialog. Now I have partially installed packages for nvidia driver, so what should I do with this ? And what should I have done ? Install non working drivers ? I am on a W520, equipped with a Quadro-1000M; I saw the same warning you did, and the card was identified correctly. I am on Buster. I installed nvidia-legacy-390, uninstalled nvidia-legacy-checker, and my machine survived a reboot with the GUI coming up nicely. YMMV. On a totally separate note, I have no idea actually if I am using this driver over nouveau, since I was messing with bumblebee a while back and don't push the graphics capabilities here
Re: How to get a clean situation for nvidia drivers
On Tue, 12 Mar 2019 19:03:12 +0100 Erwan David wrote: Hello Erwan, >And what should I have done ? Install non working drivers ? You should have read the warning; It tells which version of the legacy packages you need to install. I'm guessing, based on the fact that you updated today, you're using testing. Further guess work suggests (because you give NO technical info at all, like which GFX card you're using) you should use the 390xx legacy packages. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" This disease is catching Into The Valley - Skids pgpXSFNYFHxQ6.pgp Description: OpenPGP digital signature
How to get a clean situation for nvidia drivers
When upgrading my lenovo T530 I was warned that nvidia-driver does not support anymore my graphic card. Thus I chose to not upgrade in the dialog. Now I have partially installed packages for nvidia driver, so what should I do with this ? And what should I have done ? Install non working drivers ?
Re: NVIDIA drivers and virtual console problem
On 09/15/2018 10:28 AM, Thakur Mahashaya wrote: //"Есть два великих грехов в мире... ..грех невежества, грех от глупости.// So stupidity is the mode of ignorance. As the Sorting Hat once said, "I know what to do with YOU!" ...and off you go into my junk folder. :) Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html
Re: NVIDIA drivers and virtual console problem
//here are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity.// So stupidity is the mode of ignorance. 15.09.2018, 17:20, "Ric Moore" : > On 09/14/2018 07:54 AM, Marco Righi wrote: >> Hello, >> the NVIDIA drivers (384 from Debian and 390 repositories from the nvidia >> site) do not allow me to have "virtual consoles" (to be clear, those that >> are activated with Ctrl-Alt-F1 .. F6). By installing Nouveau the problem >> disappears, with the two different versions of the NVIDIA drivers the >> problem appears. >> >> The video card is: >> >> VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev >> a1) > > Are you running the correct nvidia driver version?? A 520 is pretty long > in the tooth and might need the legacy driver. Ric > > -- > My father, Victor Moore (Vic) used to say: > "There are two Great Sins in the world... > ..the Sin of Ignorance, and the Sin of Stupidity. > Only the former may be overcome." R.I.P. Dad. > http://linuxcounter.net/user/44256.html
Re: NVIDIA drivers and virtual console problem
//"Есть два великих грехов в мире... ..грех невежества, грех от глупости.// So stupidity is the mode of ignorance. 15.09.2018, 17:20, "Ric Moore" : > On 09/14/2018 07:54 AM, Marco Righi wrote: >> Hello, >> the NVIDIA drivers (384 from Debian and 390 repositories from the nvidia >> site) do not allow me to have "virtual consoles" (to be clear, those that >> are activated with Ctrl-Alt-F1 .. F6). By installing Nouveau the problem >> disappears, with the two different versions of the NVIDIA drivers the >> problem appears. >> >> The video card is: >> >> VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev >> a1) > > Are you running the correct nvidia driver version?? A 520 is pretty long > in the tooth and might need the legacy driver. Ric > > -- > My father, Victor Moore (Vic) used to say: > "There are two Great Sins in the world... > ..the Sin of Ignorance, and the Sin of Stupidity. > Only the former may be overcome." R.I.P. Dad. > http://linuxcounter.net/user/44256.html
Re: NVIDIA drivers and virtual console problem
On 09/14/2018 07:54 AM, Marco Righi wrote: Hello, the NVIDIA drivers (384 from Debian and 390 repositories from the nvidia site) do not allow me to have "virtual consoles" (to be clear, those that are activated with Ctrl-Alt-F1 .. F6). By installing Nouveau the problem disappears, with the two different versions of the NVIDIA drivers the problem appears. The video card is: VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev a1) Are you running the correct nvidia driver version?? A 520 is pretty long in the tooth and might need the legacy driver. Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html
NVIDIA drivers and virtual console problem
Hello, the NVIDIA drivers (384 from Debian and 390 repositories from the nvidia site) do not allow me to have "virtual consoles" (to be clear, those that are activated with Ctrl-Alt-F1 .. F6). By installing Nouveau the problem disappears, with the two different versions of the NVIDIA drivers the problem appears. The video card is: VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev a1) With the Nouveau drivers during the Boot there is a time when the video card switches from text mode to graphic mode (so to speak, when the [ok] in green are starting to appear). With the NVIDIA dirver it crashes while remaining in the text mode (lightdm is executed correctly). I reported the bug with reportbug-ng, let's see what happens. Thanks for your help. m
Re: Nvidia drivers
Thanks for being a good guy and following up; I was looking into this and this report was keeping me from apt-get dist-upgrade this evening, so I know I'm OK now... Silent thanks to all that have faffed with getting this sorted in the last week -- cheers! On 07/09/2018 02:17 PM, Matthew Crews wrote: On 7/9/18 5:55 AM, Matthew Crews wrote: On Fri, Jul 06, 2018 at 09:55:45AM +0100, Darac Marjal wrote: On Thu, Jul 05, 2018 at 08:03:22PM -0500, Mark Allums wrote: This requires a workaround, a kernel parameter at boot. GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=y" Edit the config file like this, $sudo gedit /etc/default/grub Then run $sudo update-grub. Actually, as of version 390.67-2, that's no longer needed. Quoting [1]: I just tested with 4.16 kernel and 390.67-2 nvidia-driver, and unfortunately this work-around is still required on my system. I was unable to boot my system properly without the kernel parameter in GRUB. You know what? Thats actually not true. I didn't realize that I was still using the old driver version when I tested. 臘♂️ You can disregard. The kernel parameter is not needed with 390.67-2
Re: Nvidia drivers
On 7/9/18 5:55 AM, Matthew Crews wrote: > On Fri, Jul 06, 2018 at 09:55:45AM +0100, Darac Marjal wrote: >>> On Thu, Jul 05, 2018 at 08:03:22PM -0500, Mark Allums wrote: >>> This requires a workaround, a kernel parameter at boot. >>> GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=y" >>> Edit the config file like this, >>> $sudo gedit /etc/default/grub >>> Then run $sudo update-grub. >> Actually, as of version 390.67-2, that's no longer needed. Quoting [1]: > > I just tested with 4.16 kernel and 390.67-2 nvidia-driver, and > unfortunately this work-around is still required on my system. I was > unable to boot my system properly without the kernel parameter in GRUB. > You know what? Thats actually not true. I didn't realize that I was still using the old driver version when I tested. 臘♂️ You can disregard. The kernel parameter is not needed with 390.67-2
Re: Nvidia drivers
On Fri, Jul 06, 2018 at 09:55:45AM +0100, Darac Marjal wrote: >> On Thu, Jul 05, 2018 at 08:03:22PM -0500, Mark Allums wrote: >> This requires a workaround, a kernel parameter at boot. >> GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=y" >> Edit the config file like this, >> $sudo gedit /etc/default/grub >> Then run $sudo update-grub. > Actually, as of version 390.67-2, that's no longer needed. Quoting [1]: I just tested with 4.16 kernel and 390.67-2 nvidia-driver, and unfortunately this work-around is still required on my system. I was unable to boot my system properly without the kernel parameter in GRUB. pEpkey.asc Description: application/pgp-keys
Re: Nvidia drivers
On Sat, 07 Jul 2018 11:47:59 +0200 Francisco Mariano-Neto wrote: Hello Francisco, >maintainers) that the 390.67-2 solved this problem. Since that's the >version that is in sid, that explains why sid doesn't have this issue. That version arrived as the fix. Prior to that, sid & testing shared the same version of the nvidia-drivers package for a few days. As Floris pointed out, various reports from sid users *did* occur - I simply didn't check properly. Floris has also pointed out a bug report that has arisen from using the fixed version. It may not affect me, but 'Forewarned is forearmed', as they say. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Every single one of us Devil Inside - INXS pgpbRjbCpXW5h.pgp Description: OpenPGP digital signature
Re: Nvidia drivers
Hey all, On Fri, 2018-07-06 at 11:37 +0100, Brad Rogers wrote: > > nVidia have made changes to the driver that negate the effects of a > change in the kernel. > > So, it appears to be 'six of one, half a dozen of the other'. That > said, maybe nVidia should have kept a closer eye on kernel changes to > mitigate this problem. Thanks for the clarification. I'm no kernel hacker myself, so sadly I can't really get a grasp on what happened, so this is good enough =) > It's strange also that nobody using sid /seems/ to have been affected > by > the problem. Or maybe they were, knew the workaround and forgot to > report the bug. Who knows? IIRC someone said earlier on this thread (and I've also seen the same in other threads about this problem, including the package maintainers) that the 390.67-2 solved this problem. Since that's the version that is in sid, that explains why sid doesn't have this issue. In any case, using the workaround worked for me. It caused GNOME to take a very long time to load, but I'm assuming that's GNOME's fault. Thanks all! Francisco signature.asc Description: This is a digitally signed message part
Re: Nvidia drivers
On Fri, 06 Jul 2018 16:10:40 +0200 floris wrote: Hello floris, >and there is a new bug: >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903121 >So be careful if you use the nvidia module. Thanks for the warning. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Is she really going out with him? New Rose - The Damned pgpU9W47WSIjV.pgp Description: OpenPGP digital signature
Re: Nvidia drivers
On Fri, 06 Jul 2018 16:06:19 +0200 floris wrote: Hello floris, >They have found and reported this bug multiple times: > >see bug numbers: 901919, 901932, 901990, 902248, 902661, 902773, >902868, 902891 Fair enough. As I was pointed to the initial report quite quickly, I didn't search for others. Also, as I subscribed to the bug, I didn't look closely at the web page for it - thereby missing the "merged with..." notes. I also misread the date of the initial report, too; It was made quite some time before migration to testing. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Save me from everybody else Prisoners - Judgement Centre pgpfjlkWZuvFj.pgp Description: OpenPGP digital signature
Re: Nvidia drivers
Matthew Crews schreef op 2018-07-06 13:55: On 07/06/2018 01:55 AM, Darac Marjal wrote: Actually, as of version 390.67-2, that's no longer needed. Quoting [1]: nvidia-graphics-drivers (390.67-2) unstable; urgency=high * Add kmem_cache_create_usercopy.patch from Red Hat, fixing "Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache'" on Linux kernels that have disabled CONFIG_HARDENED_USERCOPY_FALLBACK (i.e. linux-image-4.16.0-2-* or newer). (Closes: #901919) -- Andreas Beckmann Thu, 05 Jul 2018 02:01:31 +0200 [1] http://metadata.ftp-master.debian.org/changelogs/non-free/n/nvidia-graphics-drivers/nvidia-graphics-drivers_390.67-2_changelog Thats good to know. Unfortunately, Stretch-backports and Buster Nvidia-drivers are not in sync with Sid right now. So this is still a necessary workaround for Stretch-backports and Buster users. and there is a new bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903121 So be careful if you use the nvidia module. --- Floris
Re: Nvidia drivers
Brad Rogers schreef op 2018-07-06 12:37: It's strange also that nobody using sid /seems/ to have been affected by the problem. Or maybe they were, knew the workaround and forgot to report the bug. Who knows? They have found and reported this bug multiple times: see bug numbers: 901919, 901932, 901990, 902248, 902661, 902773, 902868, 902891 --- Floris
Re: Nvidia drivers
On 07/06/2018 01:55 AM, Darac Marjal wrote: > Actually, as of version 390.67-2, that's no longer needed. Quoting [1]: > > nvidia-graphics-drivers (390.67-2) unstable; urgency=high > > * Add kmem_cache_create_usercopy.patch from Red Hat, fixing "Bad or > missing > usercopy whitelist? Kernel memory exposure attempt detected > from SLUB > object 'nvidia_stack_cache'" on Linux kernels that have disabled > CONFIG_HARDENED_USERCOPY_FALLBACK (i.e. linux-image-4.16.0-2-* > or newer). > (Closes: #901919) > >-- Andreas Beckmann Thu, 05 Jul 2018 02:01:31 +0200 > > [1] > http://metadata.ftp-master.debian.org/changelogs/non-free/n/nvidia-graphics-drivers/nvidia-graphics-drivers_390.67-2_changelog > Thats good to know. Unfortunately, Stretch-backports and Buster Nvidia-drivers are not in sync with Sid right now. So this is still a necessary workaround for Stretch-backports and Buster users.
Re: Nvidia drivers
On Fri, 06 Jul 2018 12:09:59 +0200 Francisco M Neto wrote: Hello Francisco, >assume it was something that was changed in the kernel since it was the >kernel upgrade that "broke" the driver, but it might also have been >something in the driver that was addressed in the kernel. nVidia have made changes to the driver that negate the effects of a change in the kernel. So, it appears to be 'six of one, half a dozen of the other'. That said, maybe nVidia should have kept a closer eye on kernel changes to mitigate this problem. It's strange also that nobody using sid /seems/ to have been affected by the problem. Or maybe they were, knew the workaround and forgot to report the bug. Who knows? -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" It couldn't adapt so it couldn't survive The Great British Mistake - The Adverts pgpi5NYuYkN3c.pgp Description: OpenPGP digital signature
Re: Nvidia drivers
Thanks for the answer! First, checking installed kernel headers was the first thing I tried when dkms failed. I'll try using the workaround when I get home tonight and see how it goes. I try not to use too much stuff from sid, especially on essential systems like this. However I did not understand exactly what was the problem. I assume it was something that was changed in the kernel since it was the kernel upgrade that "broke" the driver, but it might also have been something in the driver that was addressed in the kernel. What exactly happened? I'm not a driver hacker so I don't really understand what is the issue... Francisco On Fri, 2018-07-06 at 09:55 +0100, Darac Marjal wrote: > On Thu, Jul 05, 2018 at 08:03:22PM -0500, Mark Allums wrote: > > On 7/5/18 5:42 PM, Francisco Mariano-Neto wrote: > > > Hey all, > > > > > > I'm running kernel 4.15 with nvidia-driver 390.48-3 with no > > > problems. However, recently my kernel was automatically upgraded > > > to 4.16 > > > and it broke the nvidia driver. > > > > > > Running 'dkms autoinstall --all' does not help, it complains > > > about not finding kernel headers (which are installed) and quits. > > > > > > Any ideas on how I can rebuild the kernel module for the new > > > kernel version? > > > > > > Thanks > > > Francisco > > > > > > > This requires a workaround, a kernel parameter at boot. > > > > GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=y" > > > > Edit the config file like this, > > > > $sudo gedit /etc/default/grub > > > > Then run $sudo update-grub. > > > > Actually, as of version 390.67-2, that's no longer needed. Quoting > [1]: > > nvidia-graphics-drivers (390.67-2) unstable; urgency=high > > * Add kmem_cache_create_usercopy.patch from Red Hat, fixing > "Bad or missing > usercopy whitelist? Kernel memory exposure attempt > detected from SLUB > object 'nvidia_stack_cache'" on Linux kernels that have > disabled > CONFIG_HARDENED_USERCOPY_FALLBACK (i.e. linux-image- > 4.16.0-2-* or newer). > (Closes: #901919) > >-- Andreas Beckmann Thu, 05 Jul 2018 > 02:01:31 +0200 > > [1] http://metadata.ftp-master.debian.org/changelogs/non-free/n/nvidi > a-graphics-drivers/nvidia-graphics-drivers_390.67-2_changelog > -- -- []s, Francisco M Neto signature.asc Description: This is a digitally signed message part
Re: Nvidia drivers
On Thu, Jul 05, 2018 at 08:03:22PM -0500, Mark Allums wrote: On 7/5/18 5:42 PM, Francisco Mariano-Neto wrote: Hey all, I'm running kernel 4.15 with nvidia-driver 390.48-3 with no problems. However, recently my kernel was automatically upgraded to 4.16 and it broke the nvidia driver. Running 'dkms autoinstall --all' does not help, it complains about not finding kernel headers (which are installed) and quits. Any ideas on how I can rebuild the kernel module for the new kernel version? Thanks Francisco This requires a workaround, a kernel parameter at boot. GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=y" Edit the config file like this, $sudo gedit /etc/default/grub Then run $sudo update-grub. Actually, as of version 390.67-2, that's no longer needed. Quoting [1]: nvidia-graphics-drivers (390.67-2) unstable; urgency=high * Add kmem_cache_create_usercopy.patch from Red Hat, fixing "Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache'" on Linux kernels that have disabled CONFIG_HARDENED_USERCOPY_FALLBACK (i.e. linux-image-4.16.0-2-* or newer). (Closes: #901919) -- Andreas Beckmann Thu, 05 Jul 2018 02:01:31 +0200 [1] http://metadata.ftp-master.debian.org/changelogs/non-free/n/nvidia-graphics-drivers/nvidia-graphics-drivers_390.67-2_changelog -- For more information, please reread. signature.asc Description: PGP signature
Re: Nvidia drivers
On Fri, Jul 6, 2018, 5:57 AM Matthew Crews wrote: > On 07/05/2018 06:03 PM, Mark Allums wrote: > > On 7/5/18 5:42 PM, Francisco Mariano-Neto wrote: > >> Hey all, > >> > >> I'm running kernel 4.15 with nvidia-driver 390.48-3 with no > >> problems. However, recently my kernel was automatically upgraded to 4.16 > >> and it broke the nvidia driver. > >> > >> Running 'dkms autoinstall --all' does not help, it complains > >> about not finding kernel headers (which are installed) and quits. > >> > >> Any ideas on how I can rebuild the kernel module for the new > >> kernel version? > >> > >> Thanks > >> Francisco > >> > > This requires a workaround, a kernel parameter at boot. > > > > GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=y" > > > > Edit the config file like this, > > > > $sudo gedit /etc/default/grub > > > > Then run $sudo update-grub. > > > > As an aside, thank you for posting this fix. Although my drivers were > not broken, I did have a problem where xorg would not start correctly > with the 4.16 kernel and nvidia drivers 390.48 (both from Stretch > backports). That GRUB command seemed to resolve it my issue. > > Cheers. > > I have 304xx working fine dkms with 4.16. of course these are now > deprecated. If only nouveau would work. I prefer it..
Re: Nvidia drivers
On 07/05/2018 06:03 PM, Mark Allums wrote: > On 7/5/18 5:42 PM, Francisco Mariano-Neto wrote: >> Hey all, >> >> I'm running kernel 4.15 with nvidia-driver 390.48-3 with no >> problems. However, recently my kernel was automatically upgraded to 4.16 >> and it broke the nvidia driver. >> >> Running 'dkms autoinstall --all' does not help, it complains >> about not finding kernel headers (which are installed) and quits. >> >> Any ideas on how I can rebuild the kernel module for the new >> kernel version? >> >> Thanks >> Francisco >> > This requires a workaround, a kernel parameter at boot. > > GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=y" > > Edit the config file like this, > > $sudo gedit /etc/default/grub > > Then run $sudo update-grub. > As an aside, thank you for posting this fix. Although my drivers were not broken, I did have a problem where xorg would not start correctly with the 4.16 kernel and nvidia drivers 390.48 (both from Stretch backports). That GRUB command seemed to resolve it my issue. Cheers.
Re: Nvidia drivers
Sorry, I failed to read your whole message. Make sure you have installed the the kbuild and headers for your current running kernel. Then consider upgrading your nvidia driver to the latest version (in sid, still, I believe). If you do the latter, be sure and use the kernel parameter I showed you in my earlier post. Mark On 7/5/18 8:03 PM, Mark Allums wrote: On 7/5/18 5:42 PM, Francisco Mariano-Neto wrote: Hey all, I'm running kernel 4.15 with nvidia-driver 390.48-3 with no problems. However, recently my kernel was automatically upgraded to 4.16 and it broke the nvidia driver. Running 'dkms autoinstall --all' does not help, it complains about not finding kernel headers (which are installed) and quits. Any ideas on how I can rebuild the kernel module for the new kernel version? Thanks Francisco This requires a workaround, a kernel parameter at boot. GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=y" Edit the config file like this, $sudo gedit /etc/default/grub Then run $sudo update-grub.
Re: Nvidia drivers
On 7/5/18 5:42 PM, Francisco Mariano-Neto wrote: Hey all, I'm running kernel 4.15 with nvidia-driver 390.48-3 with no problems. However, recently my kernel was automatically upgraded to 4.16 and it broke the nvidia driver. Running 'dkms autoinstall --all' does not help, it complains about not finding kernel headers (which are installed) and quits. Any ideas on how I can rebuild the kernel module for the new kernel version? Thanks Francisco This requires a workaround, a kernel parameter at boot. GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=y" Edit the config file like this, $sudo gedit /etc/default/grub Then run $sudo update-grub.
Re: Nvidia drivers
You sure you have the 4.16 headers installed and not the 4.15 headers? Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. Original Message On Jul 5, 2018, 15:42, Francisco Mariano-Neto wrote: > Hey all, > > I'm running kernel 4.15 with nvidia-driver 390.48-3 with no > problems. However, recently my kernel was automatically upgraded to 4.16 > and it broke the nvidia driver. > > Running 'dkms autoinstall --all' does not help, it complains > about not finding kernel headers (which are installed) and quits. > > Any ideas on how I can rebuild the kernel module for the new > kernel version? > > Thanks > Francisco
Nvidia drivers
Hey all, I'm running kernel 4.15 with nvidia-driver 390.48-3 with no problems. However, recently my kernel was automatically upgraded to 4.16 and it broke the nvidia driver. Running 'dkms autoinstall --all' does not help, it complains about not finding kernel headers (which are installed) and quits. Any ideas on how I can rebuild the kernel module for the new kernel version? Thanks Francisco signature.asc Description: This is a digitally signed message part
Re: Problem installing nvidia-drivers
On 2015-05-30, Stefan Malte Schumacher stefanma...@gmail.com wrote: Yes, I have. You have the non-free archive mentioned in your /etc/apt/sources.list? You need contrib also, it would appear. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmmlna5.21r.cu...@einstein.electron.org
Re: Problem installing nvidia-drivers
On 2015-05-30, Stefan Malte Schumacher stefanma...@gmail.com wrote: Hello This is the english version of the output of aptitude. You have the non-free archive mentioned in your /etc/apt/sources.list? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmmjq9n.1v0.cu...@einstein.electron.org
Re: Problem installing nvidia-drivers
Yes, I have. 2015-05-30 18:45 GMT+02:00 Curt cu...@free.fr: On 2015-05-30, Stefan Malte Schumacher stefanma...@gmail.com wrote: Hello This is the english version of the output of aptitude. You have the non-free archive mentioned in your /etc/apt/sources.list? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmmjq9n.1v0.cu...@einstein.electron.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKJwqUNdRPR_Gq4CVUZa=ampemduovpvrutjkwat_h_kz11...@mail.gmail.com
Re: Problem installing nvidia-drivers
On 05/30/2015 04:18 PM, Stefan Malte Schumacher wrote:
Hello
I am trying to install the proprietary Nvidia-Drivers on my Laptop. I
have read
https://wiki.debian.org/NvidiaGraphicsDrivers#Debian_8_.22Jessie.22
and have entered the following command according to the description:
aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
nvidia-kernel-dkms
As a result I get the the output following this section. How should I proceed?
Unfortunately using Noveau is not an alternative since the current version has
a bug which causes my screen to flicker, making it practically unreadable.
Thanks in advance
Stefan
root@deimos:~# aptitude -r install linux-headers-$(uname -r|sed
's,[^-]*-[^-]*-,,') nvidia-kernel-dkms
Die folgenden NEUEN Pakete werden zusätzlich installiert:
libegl1-nvidia{a} libgl1-nvidia-glx{ab} libgles1-nvidia{a}
libgles2-nvidia{a} libnvidia-eglcore{a} libnvidia-ml1{a} nvidia-alternative{ab}
nvidia-driver{ab} nvidia-driver-bin{a} nvidia-kernel-dkms{b}
nvidia-vdpau-driver{ab} xserver-xorg-video-nvidia{ab}
0 Pakete aktualisiert, 12 zusätzlich installiert, 0 werden entfernt und 0 nicht
aktualisiert.
23,8 MB an Archiven müssen heruntergeladen werden. Nach dem Entpacken werden
133 MB zusätzlich belegt sein.
Die folgenden Pakete haben verletzte Abhängigkeiten:
nvidia-alternative : Hängt ab von: glx-alternative-nvidia (= 0.5), welches
ein virtuelles Paket ist.
Hängt ab von: nvidia-modprobe, welches ein virtuelles
Paket ist.
nvidia-driver : Hängt ab von: nvidia-support, welches ein virtuelles Paket
ist.
Hängt ab von (vorher): nvidia-installer-cleanup, welches ein
virtuelles Paket ist.
xserver-xorg-video-nvidia : Hängt ab von: nvidia-support (= 20120630),
welches ein virtuelles Paket ist.
Hängt ab von (vorher): nvidia-installer-cleanup,
welches ein virtuelles Paket ist.
libgl1-nvidia-glx : Hängt ab von: nvidia-support, welches ein virtuelles
Paket ist.
Hängt ab von (vorher): nvidia-installer-cleanup, welches
ein virtuelles Paket ist.
nvidia-kernel-dkms : Hängt ab von: nvidia-kernel-common (= 20110213),
welches ein virtuelles Paket ist.
Hängt ab von (vorher): nvidia-installer-cleanup, welches
ein virtuelles Paket ist.
nvidia-vdpau-driver : Hängt ab von (vorher): nvidia-installer-cleanup,
welches ein virtuelles Paket ist.
Die folgenden Aktionen werden diese Abhängigkeiten auflösen:
Beibehalten der folgenden Pakete in ihrer aktuellen Version:
1) libegl1-nvidia [Nicht installiert]
2) libgl1-nvidia-glx [Nicht installiert]
3) libgles1-nvidia [Nicht installiert]
4) libgles2-nvidia [Nicht installiert]
5) libnvidia-ml1 [Nicht installiert]
6) nvidia-alternative [Nicht installiert]
7) nvidia-driver [Nicht installiert]
8) nvidia-driver-bin [Nicht installiert]
9) nvidia-kernel-dkms [Nicht installiert]
10) nvidia-vdpau-driver [Nicht installiert]
11) xserver-xorg-video-nvidia [Nicht installiert]
Die folgenden Abhängigkeiten unaufgelöst lassen:
12) nvidia-driver empfiehlt libgles1-nvidia (= 340.65-2)
13) nvidia-driver empfiehlt libgles2-nvidia (= 340.65-2)
14) nvidia-driver-bin empfiehlt nvidia-driver
15) nvidia-kernel-dkms empfiehlt nvidia-driver (= 340.65) | libcuda1 (=
340.65)
16) nvidia-vdpau-driver empfiehlt nvidia-kernel-dkms (= 340.65-2) |
nvidia-kernel-340.65
17) xserver-xorg-video-nvidia empfiehlt nvidia-driver (= 340.65)
18) xserver-xorg-video-nvidia empfiehlt nvidia-vdpau-driver (= 340.65)
19) xserver-xorg-video-nvidia empfiehlt nvidia-kernel-dkms (= 340.65-2) |
nvidia-kernel-340.65
Hi,
Some questions:
- Which release are you running? Jessie?
- Do you have contrib and non-free included in your apt sources? Maybe
paste the contents of /etc/apt/sources.list here.
- Do you have other (3rd party) apt sources, maybe in sources.list.d?
glx-alternative-nvidia being a virtual package, strikes me as odd.
Best regards,
Matthijs
Re: Problem installing nvidia-drivers
On 05/30/2015 01:54 PM, Matthijs Wensveen wrote: glx-alternative-nvidia being a virtual package, strikes me as odd. It just whirrs a bit and sets alternatives for GLX libs to nvidia directories rather than Mesa, and then goes away. It's like oatmeal in the morning, it's always there. :) Ric p/s If the OP has one of the newest nVidia cards, there are some laptop issues requiring more than plain nvidia drivers. I forget the name of the special install system. But, the Op can just go to the nvidia site for more info on his card's driver requirements Or, he could rip out ALL nvidia installed packages, (apt-get purge nvidia*) to create a clean slate, and re-install. I've had to resort to that more than once over the years. Be sure to keep a copy of /etc/X11/xorg.conf somewhere safe, like the /home/$USERNAME directory, in case you need it again. http://linuxconfig.org/nvidia-geforce-driver-installation-on-debian-jessie-linux-8-64bit -- My father, Victor Moore (Vic) used to say: There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome. R.I.P. Dad. http://linuxcounter.net/user/44256.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/556a2386.10...@gmail.com
Problem installing nvidia-drivers
Hello
I am trying to install the proprietary Nvidia-Drivers on my Laptop. I have
read https://wiki.debian.org/NvidiaGraphicsDrivers#Debian_8_.22Jessie.22
and have entered the following command according to the description:
aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
nvidia-kernel-dkms
As a result I get the the output following this section. How should I
proceed? Unfortunately using Noveau is not an alternative since the
current version has a bug which causes my screen to flicker, making it
practically unreadable.
Thanks in advance
Stefan
root@deimos:~# aptitude -r install linux-headers-$(uname -r|sed
's,[^-]*-[^-]*-,,') nvidia-kernel-dkms
Die folgenden NEUEN Pakete werden zusätzlich installiert:
libegl1-nvidia{a} libgl1-nvidia-glx{ab} libgles1-nvidia{a}
libgles2-nvidia{a} libnvidia-eglcore{a} libnvidia-ml1{a}
nvidia-alternative{ab} nvidia-driver{ab} nvidia-driver-bin{a}
nvidia-kernel-dkms{b}
nvidia-vdpau-driver{ab} xserver-xorg-video-nvidia{ab}
0 Pakete aktualisiert, 12 zusätzlich installiert, 0 werden entfernt
und 0 nicht aktualisiert.
23,8 MB an Archiven müssen heruntergeladen werden. Nach dem Entpacken
werden 133 MB zusätzlich belegt sein.
Die folgenden Pakete haben verletzte Abhängigkeiten:
nvidia-alternative : Hängt ab von: glx-alternative-nvidia (= 0.5),
welches ein virtuelles Paket ist.
Hängt ab von: nvidia-modprobe, welches ein
virtuelles Paket ist.
nvidia-driver : Hängt ab von: nvidia-support, welches ein virtuelles Paket ist.
Hängt ab von (vorher): nvidia-installer-cleanup,
welches ein virtuelles Paket ist.
xserver-xorg-video-nvidia : Hängt ab von: nvidia-support (=
20120630), welches ein virtuelles Paket ist.
Hängt ab von (vorher):
nvidia-installer-cleanup, welches ein virtuelles Paket ist.
libgl1-nvidia-glx : Hängt ab von: nvidia-support, welches ein
virtuelles Paket ist.
Hängt ab von (vorher): nvidia-installer-cleanup,
welches ein virtuelles Paket ist.
nvidia-kernel-dkms : Hängt ab von: nvidia-kernel-common (=
20110213), welches ein virtuelles Paket ist.
Hängt ab von (vorher): nvidia-installer-cleanup,
welches ein virtuelles Paket ist.
nvidia-vdpau-driver : Hängt ab von (vorher):
nvidia-installer-cleanup, welches ein virtuelles Paket ist.
Die folgenden Aktionen werden diese Abhängigkeiten auflösen:
Beibehalten der folgenden Pakete in ihrer aktuellen Version:
1) libegl1-nvidia [Nicht installiert]
2) libgl1-nvidia-glx [Nicht installiert]
3) libgles1-nvidia [Nicht installiert]
4) libgles2-nvidia [Nicht installiert]
5) libnvidia-ml1 [Nicht installiert]
6) nvidia-alternative [Nicht installiert]
7) nvidia-driver [Nicht installiert]
8) nvidia-driver-bin [Nicht installiert]
9) nvidia-kernel-dkms [Nicht installiert]
10) nvidia-vdpau-driver [Nicht installiert]
11) xserver-xorg-video-nvidia [Nicht installiert]
Die folgenden Abhängigkeiten unaufgelöst lassen:
12) nvidia-driver empfiehlt libgles1-nvidia (= 340.65-2)
13) nvidia-driver empfiehlt libgles2-nvidia (= 340.65-2)
14) nvidia-driver-bin empfiehlt nvidia-driver
15) nvidia-kernel-dkms empfiehlt nvidia-driver (= 340.65) |
libcuda1 (= 340.65)
16) nvidia-vdpau-driver empfiehlt nvidia-kernel-dkms (= 340.65-2)
| nvidia-kernel-340.65
17) xserver-xorg-video-nvidia empfiehlt nvidia-driver (= 340.65)
18) xserver-xorg-video-nvidia empfiehlt nvidia-vdpau-driver (=
340.65)
19) xserver-xorg-video-nvidia empfiehlt nvidia-kernel-dkms (=
340.65-2) | nvidia-kernel-340.65
Re: Problem installing nvidia-drivers
On Saturday 30 May 2015 15:18:34 Stefan Malte Schumacher wrote:
Hello
I am trying to install the proprietary Nvidia-Drivers on my Laptop. I have
read https://wiki.debian.org/NvidiaGraphicsDrivers#Debian_8_.22Jessie.22
and have entered the following command according to the description:
aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
nvidia-kernel-dkms
As a result I get the the output following this section. How should I
proceed? Unfortunately using Noveau is not an alternative since the
current version has a bug which causes my screen to flicker, making it
practically unreadable.
I have installed the proprietary NVidia driver without a problem, but I'm
afraid that my German is not up to helping with this.
See:
http://serverfault.com/questions/71026/change-the-locale-language-of-apt-get-aptitude
and perhaps try again?
Lisi
Thanks in advance
Stefan
root@deimos:~# aptitude -r install linux-headers-$(uname -r|sed
's,[^-]*-[^-]*-,,') nvidia-kernel-dkms
Die folgenden NEUEN Pakete werden zusätzlich installiert:
libegl1-nvidia{a} libgl1-nvidia-glx{ab} libgles1-nvidia{a}
libgles2-nvidia{a} libnvidia-eglcore{a} libnvidia-ml1{a}
nvidia-alternative{ab} nvidia-driver{ab} nvidia-driver-bin{a}
nvidia-kernel-dkms{b}
nvidia-vdpau-driver{ab} xserver-xorg-video-nvidia{ab}
0 Pakete aktualisiert, 12 zusätzlich installiert, 0 werden entfernt
und 0 nicht aktualisiert.
23,8 MB an Archiven müssen heruntergeladen werden. Nach dem Entpacken
werden 133 MB zusätzlich belegt sein.
Die folgenden Pakete haben verletzte Abhängigkeiten:
nvidia-alternative : Hängt ab von: glx-alternative-nvidia (= 0.5),
welches ein virtuelles Paket ist.
Hängt ab von: nvidia-modprobe, welches ein
virtuelles Paket ist.
nvidia-driver : Hängt ab von: nvidia-support, welches ein virtuelles Paket
ist. Hängt ab von (vorher): nvidia-installer-cleanup,
welches ein virtuelles Paket ist.
xserver-xorg-video-nvidia : Hängt ab von: nvidia-support (=
20120630), welches ein virtuelles Paket ist.
Hängt ab von (vorher):
nvidia-installer-cleanup, welches ein virtuelles Paket ist.
libgl1-nvidia-glx : Hängt ab von: nvidia-support, welches ein
virtuelles Paket ist.
Hängt ab von (vorher): nvidia-installer-cleanup,
welches ein virtuelles Paket ist.
nvidia-kernel-dkms : Hängt ab von: nvidia-kernel-common (=
20110213), welches ein virtuelles Paket ist.
Hängt ab von (vorher): nvidia-installer-cleanup,
welches ein virtuelles Paket ist.
nvidia-vdpau-driver : Hängt ab von (vorher):
nvidia-installer-cleanup, welches ein virtuelles Paket ist.
Die folgenden Aktionen werden diese Abhängigkeiten auflösen:
Beibehalten der folgenden Pakete in ihrer aktuellen Version:
1) libegl1-nvidia [Nicht installiert]
2) libgl1-nvidia-glx [Nicht installiert]
3) libgles1-nvidia [Nicht installiert]
4) libgles2-nvidia [Nicht installiert]
5) libnvidia-ml1 [Nicht installiert]
6) nvidia-alternative [Nicht installiert]
7) nvidia-driver [Nicht installiert]
8) nvidia-driver-bin [Nicht installiert]
9) nvidia-kernel-dkms [Nicht installiert]
10) nvidia-vdpau-driver [Nicht installiert]
11) xserver-xorg-video-nvidia [Nicht installiert]
Die folgenden Abhängigkeiten unaufgelöst lassen:
12) nvidia-driver empfiehlt libgles1-nvidia (= 340.65-2)
13) nvidia-driver empfiehlt libgles2-nvidia (= 340.65-2)
14) nvidia-driver-bin empfiehlt nvidia-driver
15) nvidia-kernel-dkms empfiehlt nvidia-driver (= 340.65) |
libcuda1 (= 340.65)
16) nvidia-vdpau-driver empfiehlt nvidia-kernel-dkms (= 340.65-2)
| nvidia-kernel-340.65
17) xserver-xorg-video-nvidia empfiehlt nvidia-driver (= 340.65)
18) xserver-xorg-video-nvidia empfiehlt nvidia-vdpau-driver (=
340.65)
19) xserver-xorg-video-nvidia empfiehlt nvidia-kernel-dkms (=
340.65-2) | nvidia-kernel-340.65
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201505301531.49460.lisi.re...@gmail.com
Re: Problem installing nvidia-drivers
Hello
This is the english version of the output of aptitude.
aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
nvidia-kernel-dkmsThe following NEW packages will be installed:
libegl1-nvidia{a} libgl1-nvidia-glx{ab} libgles1-nvidia{a}
libgles2-nvidia{a} libnvidia-eglcore{a}
libnvidia-ml1{a} nvidia-alternative{ab} nvidia-driver{ab}
nvidia-driver-bin{a} nvidia-kernel-dkms{b}
nvidia-vdpau-driver{ab} xserver-xorg-video-nvidia{ab}
0 packages upgraded, 12 newly installed, 0 to remove and 0 not upgraded.
Need to get 23.8 MB of archives. After unpacking 133 MB will be used.
The following packages have unmet dependencies:
nvidia-alternative : Depends: glx-alternative-nvidia (= 0.5) which
is a virtual package.
Depends: nvidia-modprobe which is a virtual package.
nvidia-driver : Depends: nvidia-support which is a virtual package.
PreDepends: nvidia-installer-cleanup which is a
virtual package.
xserver-xorg-video-nvidia : Depends: nvidia-support (= 20120630)
which is a virtual package.
PreDepends: nvidia-installer-cleanup
which is a virtual package.
libgl1-nvidia-glx : Depends: nvidia-support which is a virtual package.
PreDepends: nvidia-installer-cleanup which is a
virtual package.
nvidia-kernel-dkms : Depends: nvidia-kernel-common (= 20110213)
which is a virtual package.
PreDepends: nvidia-installer-cleanup which is a
virtual package.
nvidia-vdpau-driver : PreDepends: nvidia-installer-cleanup which is a
virtual package.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) libegl1-nvidia [Not Installed]
2) libgl1-nvidia-glx [Not Installed]
3) libgles1-nvidia [Not Installed]
4) libgles2-nvidia [Not Installed]
5) libnvidia-ml1 [Not Installed]
6) nvidia-alternative [Not Installed]
7) nvidia-driver [Not Installed]
8) nvidia-driver-bin [Not Installed]
9) nvidia-kernel-dkms [Not Installed]
10) nvidia-vdpau-driver [Not Installed]
11) xserver-xorg-video-nvidia [Not Installed]
Leave the following dependencies unresolved:
12) nvidia-driver recommends libgles1-nvidia (= 340.65-2)
13) nvidia-driver recommends libgles2-nvidia (= 340.65-2)
14) nvidia-driver-bin recommends nvidia-driver
15) nvidia-kernel-dkms recommends nvidia-driver (= 340.65) |
libcuda1 (= 340.65)
16) nvidia-vdpau-driver recommends nvidia-kernel-dkms (= 340.65-2)
| nvidia-kernel-340.65
17) xserver-xorg-video-nvidia recommends nvidia-driver (= 340.65)
18) xserver-xorg-video-nvidia recommends nvidia-vdpau-driver (=
340.65)
19) xserver-xorg-video-nvidia recommends nvidia-kernel-dkms (=
340.65-2) | nvidia-kernel-340.65
Bye
Stefan
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/cakjwqunywbc50am78yjwbqtej8f_ymddmnrpbdovhbzchtt...@mail.gmail.com
Re: Problem installing nvidia-drivers
On 30/05/2015, Stefan Malte Schumacher stefanma...@gmail.com wrote: Hello I am trying to install the proprietary Nvidia-Drivers on my Laptop. Hello. Whilst the above scenario relates to Debian 8, what is the nVidia device that you have in your laptop? I have not yet resolved a problem with a system that I have, that involves an nVidia GEForce GT-750M, and, if your nVidia device happened to be the same, perhaps, when a solution to your problem is found, it may also solve my problem, in previous versions of Debian.. -- Bret Busby Armadale West Australia .. So once you do know what the question actually is, you'll know what the answer means. - Deep Thought, Chapter 28 of Book 1 of The Hitchhiker's Guide to the Galaxy: A Trilogy In Four Parts, written by Douglas Adams, published by Pan Books, 1992 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CACX6j8Mg+YQKmDFRGC2GscKpz4VBvs+fa=zprkps3urfulq...@mail.gmail.com
Re: Problem installing nvidia-drivers
On Saturday 30 May 2015 15:36:52 Stefan Malte Schumacher wrote:
Hello
This is the english version of the output of aptitude.
aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
nvidia-kernel-dkmsThe following NEW packages will be installed:
libegl1-nvidia{a} libgl1-nvidia-glx{ab} libgles1-nvidia{a}
libgles2-nvidia{a} libnvidia-eglcore{a}
libnvidia-ml1{a} nvidia-alternative{ab} nvidia-driver{ab}
nvidia-driver-bin{a} nvidia-kernel-dkms{b}
nvidia-vdpau-driver{ab} xserver-xorg-video-nvidia{ab}
0 packages upgraded, 12 newly installed, 0 to remove and 0 not upgraded.
Need to get 23.8 MB of archives. After unpacking 133 MB will be used.
The following packages have unmet dependencies:
nvidia-alternative : Depends: glx-alternative-nvidia (= 0.5) which
is a virtual package.
Depends: nvidia-modprobe which is a virtual package.
nvidia-driver : Depends: nvidia-support which is a virtual package.
PreDepends: nvidia-installer-cleanup which is a
virtual package.
xserver-xorg-video-nvidia : Depends: nvidia-support (= 20120630)
which is a virtual package.
PreDepends: nvidia-installer-cleanup
which is a virtual package.
libgl1-nvidia-glx : Depends: nvidia-support which is a virtual package.
PreDepends: nvidia-installer-cleanup which is a
virtual package.
nvidia-kernel-dkms : Depends: nvidia-kernel-common (= 20110213)
which is a virtual package.
PreDepends: nvidia-installer-cleanup which is a
virtual package.
nvidia-vdpau-driver : PreDepends: nvidia-installer-cleanup which is a
virtual package.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) libegl1-nvidia [Not Installed]
2) libgl1-nvidia-glx [Not Installed]
3) libgles1-nvidia [Not Installed]
4) libgles2-nvidia [Not Installed]
5) libnvidia-ml1 [Not Installed]
6) nvidia-alternative [Not Installed]
7) nvidia-driver [Not Installed]
8) nvidia-driver-bin [Not Installed]
9) nvidia-kernel-dkms [Not Installed]
10) nvidia-vdpau-driver [Not Installed]
11) xserver-xorg-video-nvidia [Not Installed]
Leave the following dependencies unresolved:
12) nvidia-driver recommends libgles1-nvidia (= 340.65-2)
13) nvidia-driver recommends libgles2-nvidia (= 340.65-2)
14) nvidia-driver-bin recommends nvidia-driver
15) nvidia-kernel-dkms recommends nvidia-driver (= 340.65) |
libcuda1 (= 340.65)
16) nvidia-vdpau-driver recommends nvidia-kernel-dkms (= 340.65-2)
| nvidia-kernel-340.65
17) xserver-xorg-video-nvidia recommends nvidia-driver (= 340.65)
18) xserver-xorg-video-nvidia recommends nvidia-vdpau-driver (=
340.65)
19) xserver-xorg-video-nvidia recommends nvidia-kernel-dkms (=
340.65-2) | nvidia-kernel-340.65
Sorry - things have moved on! I installed NVidia over two years ago, on
Wheezy. I initially used nouveau, but it wasn't satisfactory, so as seemed
to be the only alternative at the time, I installed the relevant proprietary
driver from the NVidia website.
It works beautifully. Apart from updates, I have done nothing for over two
years!
I could look up details, I hope, but they are unlikely to be helpful to you,
having seen this.
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201505301642.54044.lisi.re...@gmail.com
Re: Very small fonts in KDE after installing Nvidia drivers
Ok, that worked brilliantly! I just followed Mark's suggestion of putting that line in my 20-nvidia.conf. Thanks! On 26 February 2015 at 19:46, Mark Neyhart mark.neyh...@akleg.gov wrote: On 02/26/2015 02:28 AM, James Allsopp wrote: Hello, I've just installed the nvidia drivers after following the instructions here https://wiki.debian.org/NvidiaGraphicsDrivers but now my fonts are so small they are unreadable. My display is a HDMI television. I think this could be related to the EDID settings but I'm not sure how to set this. I'm using the small piecewise Xorg described in the document. echo -e 'Section Device\n\tIdentifier My GPU\n\tDriver nvidia\nEndSection' /etc/X11/xorg.conf.d/20-nvidia.conf I just went through this last week with Debian Wheezy using a large television driven by an Nvidia card with the proprietary Nvidia driver. I added Option DPI 100 x 100 to my xorg.conf in the Device section for the Nvidia card. In your case I think you should be able to replace your echo statement with: echo -e 'Section Device\n\tIdentifier My GPU\n\tDriver nvidia\n\tOption DPI 100 x 100\nEndSection' /etc/X11/xorg.conf.d/20-nvidia.conf Watch out for line wrapping, this should all be on one line. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54ef7802.3010...@akleg.gov
Re: Very small fonts in KDE after installing Nvidia drivers
On 2015-02-26, James Allsopp jamesaalls...@googlemail.com wrote: I can't run nvidia-settings as I can't read the text, Any ideas what changes I need to make to fix this please? Searching, I find sudo nvidia-xconfig --no-use-edid-dpi which generates a etc/X11/xorg.conf file disabling the DPI info from the monitor's EDID. Then you would edit the xorg.conf file's monitor section and put something agreeable here: Option DPI 96 x 96 I guess the DPI ratio should correspond to your TV's resolution (or something). In other words, unless you got a square TV, 96 x 96 is probably not the way you want to go. HTH. -- Meaning is not in things but in between; in the iridescence, the interplay: in the interconnections; at the intersections, at the crossroads. Meaning is transitional as it is transitory, in the puns or bridges, the correspondence. — Mallarmé -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmeufho.2am.cu...@einstein.electron.org
Re: Very small fonts in KDE after installing Nvidia drivers
On 02/26/2015 02:28 AM, James Allsopp wrote: Hello, I've just installed the nvidia drivers after following the instructions here https://wiki.debian.org/NvidiaGraphicsDrivers but now my fonts are so small they are unreadable. My display is a HDMI television. I think this could be related to the EDID settings but I'm not sure how to set this. I'm using the small piecewise Xorg described in the document. echo -e 'Section Device\n\tIdentifier My GPU\n\tDriver nvidia\nEndSection' /etc/X11/xorg.conf.d/20-nvidia.conf I just went through this last week with Debian Wheezy using a large television driven by an Nvidia card with the proprietary Nvidia driver. I added Option DPI 100 x 100 to my xorg.conf in the Device section for the Nvidia card. In your case I think you should be able to replace your echo statement with: echo -e 'Section Device\n\tIdentifier My GPU\n\tDriver nvidia\n\tOption DPI 100 x 100\nEndSection' /etc/X11/xorg.conf.d/20-nvidia.conf Watch out for line wrapping, this should all be on one line. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54ef7802.3010...@akleg.gov
Very small fonts in KDE after installing Nvidia drivers
Hello, I've just installed the nvidia drivers after following the instructions here https://wiki.debian.org/NvidiaGraphicsDrivers but now my fonts are so small they are unreadable. My display is a HDMI television. I think this could be related to the EDID settings but I'm not sure how to set this. I'm using the small piecewise Xorg described in the document. echo -e 'Section Device\n\tIdentifier My GPU\n\tDriver nvidia\nEndSection' /etc/X11/xorg.conf.d/20-nvidia.conf I can't run nvidia-settings as I can't read the text, Any ideas what changes I need to make to fix this please? Thanks, James
Using NVIDIA drivers in Jessie
Short version: they worked for me for just under 1 day. After that the system won't boot--at the point the NVIDIA logo should be displayed the system hangs on a black screen, and the only thing I can do is power off. I can start in single-user mode, supply the root password and startx as root. From the root prompt I can also start kdm. I can't login, though--I get System is booting up -- see pam_login(8). Since the graphics driver works for root but not for my normal user this seems like a permissions problem, but I can't understand why for almost a day I could boot the system normally and log in as a user. I've collected some logs that might help a developer; I hesitate to post them because they're REALLY long. Can someone point me to the right person to send them to, or a good place to post them? Kevin -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150108123637.0a74e1e6@sirius
Re: Procedure to uninstall nvidia drivers and restore nouveau
After purging the nvidia drivers with the following command: #aptitude purge nvidia-kernel-dkms nvidia-glx The nvidia driver is still present and functioning. During the [failed] purge, I received the message 'No packages will be installed, upgraded, or removed'. On 10 November 2013 21:44, Alex Naysmith yeoman.pyt...@gmail.com wrote: After following the procedure at https://wiki.debian.org/NvidiaGraphicsDrivers to install the nvidia-glx-legacy-173xx package for my GeForce FX5550 card [Debian 7 Wheezy], I would like to know the best method to return to the nouveau driver with the files from the glx-legacy-1733 package removed including the /etc/X11/xorg.d directory. I think users would benefit from an 'uninstall nvidia driver' wiki page. Regards
Re: Procedure to uninstall nvidia drivers and restore nouveau
On Sun, 17 Nov 2013 15:47:40 + Alex Naysmith yeoman.pyt...@gmail.com wrote: Hello Alex, #aptitude purge nvidia-kernel-dkms nvidia-glx The nvidia driver is still present and functioning. During the [failed] purge, I received the message 'No packages will be installed, upgraded, or removed'. nvidia-glx is a transitional package, which installed nvidia-driver. The nvidia-driver is a meta-package. The removal of a meta-package does not necessarily remove the packages it depends on. Therefore, you need to investigate which packages should also be removed. -- Regards _ / ) The blindingly obvious is / _)radnever immediately apparent I guess I shouldn't have strangled her to death Ugly - The Stranglers signature.asc Description: PGP signature
Re: Procedure to uninstall nvidia drivers and restore nouveau
Am Sonntag, 17. November 2013, 16:57:30 schrieb Brad Rogers: On Sun, 17 Nov 2013 15:47:40 + Alex Naysmith yeoman.pyt...@gmail.com wrote: Hello Alex, #aptitude purge nvidia-kernel-dkms nvidia-glx The nvidia driver is still present and functioning. During the [failed] purge, I received the message 'No packages will be installed, upgraded, or removed'. nvidia-glx is a transitional package, which installed nvidia-driver. The nvidia-driver is a meta-package. The removal of a meta-package does not necessarily remove the packages it depends on. Therefore, you need to investigate which packages should also be removed. Best way, to uninstall all nvidia stuff for me: apt-get --purge remove nvidia-* then apt-get autoremove and last (but not recommended) orphaner The last one deinstalls also all orphaned libs. Have fun! Hans -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1535375.5npIBm16Nl@protheus2
Re: Procedure to uninstall nvidia drivers and restore nouveau
On Jo, 14 nov 13, 18:52:25, Kailash Kalyani wrote: I've used the sgfxi script and it supports removing non-free drivers and installing free ones instead. http://smxi.org/site/about.htm#sgfxi What is sgfxi (simple graphics installer - s gfx i) The primary purpose of sgfxi is to install non-free graphics drivers. It also supports removing non-free graphics drivers and replacing them with the free version. To do this it cleans out the system of any previous drivers, then installs the latest versions of the driver you have requested. One of the reasons I run Debian is that I don't need to run some script from some website to fix my system. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: Procedure to uninstall nvidia drivers and restore nouveau
On Monday 11 November 2013 11:11 PM, Curt wrote: On 2013-11-11, Chris Bannister cbannis...@slingshot.co.nz wrote: Will the nouveau driver be unblacklisted after the purge? Ask yourself - Would you, as system administrator, expect this? then Oh, sorry, I thought you were answering the OP, a newbie who asked for the procedure (even a wiki) involved in going back to the nouveau driver from the nvidia packages, which might involve manually unblacklisting the nouveau driver (or not), a potentially lethal point which I don't believe you mentioned. Hi All, I've used the sgfxi script and it supports removing non-free drivers and installing free ones instead. http://smxi.org/site/about.htm#sgfxi What is sgfxi (simple graphics installer - s gfx i) The primary purpose of sgfxi is to install non-free graphics drivers. It also supports removing non-free graphics drivers and replacing them with the free version. To do this it cleans out the system of any previous drivers, then installs the latest versions of the driver you have requested. Sincerely, Kailash -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5284ce91.5080...@gmail.com
Re: Procedure to uninstall nvidia drivers and restore nouveau
On 11/12/2013 02:56 AM, Alex Naysmith wrote: From the nvidia install procedure is the following command: # aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') nvidia-kernel-legacy-173xx-dkms I can see the pipe | symbol and the regular expressions but I don't really understand what this command is doing. It installs the linux headers related to the currently running kernel. It takes the output of uname -r and pipes it to sed. Sed is doing a substitution, replacing the version numbers with nothing. For example, on my lubuntu system: paul@Serenity:~$ uname -r 3.11.0-13-generic paul@Serenity:~$ uname -r | sed 's,[^-]*-[^-]*-,,' generic paul@Serenity:~$ echo linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') linux-headers-generic I used echo instead of aptitude, since I don't want to actually install the package. From: http://www.gnu.org/software/sed/manual/html_node/The-_0022s_0022-Command.html The syntax of the s (as in substitute) command is ‘s/regexp/replacement/flags’. From: http://www.grymoire.com/Unix/Sed.html#uh-6 I believe [^-] in the regular expression means globally match anything except a dash. I'm a little weak on sed (and awk), so I might be a little off on the specifics. I'm sure others will correct/elaborate for me. :) - PaulNM Alex -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5281ef6e.6080...@paulscrap.com
Re: Procedure to uninstall nvidia drivers and restore nouveau
On Tue, 2013-11-12 at 07:56 +, Alex Naysmith wrote: linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') It does complete the name linux-headers-. Run echo $(uname -r|sed 's,[^-]*-[^-]*-,,') or uname -r|sed 's,[^-]*-[^-]*-,,' to see what it does add. uname -r does show the kernel release, the sed command does format it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1384251324..161.camel@archlinux
Re: Procedure to uninstall nvidia drivers and restore nouveau
Thank you all for the sed regex explanation. What possible kernel variations other than 'generic' are possible to require the sed substitution? After some googling, I've discovered that I'm actually compiling the nvidia driver and hence the business with the Linux header. On 12 November 2013 07:56, Alex Naysmith yeoman.pyt...@gmail.com wrote: From the nvidia install procedure is the following command: # aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') nvidia-kernel-legacy-173xx-dkms I can see the pipe | symbol and the regular expressions but I don't really understand what this command is doing. Alex On 10 November 2013 21:44, Alex Naysmith yeoman.pyt...@gmail.com wrote: After following the procedure at https://wiki.debian.org/NvidiaGraphicsDrivers to install the nvidia-glx-legacy-173xx package for my GeForce FX5550 card [Debian 7 Wheezy], I would like to know the best method to return to the nouveau driver with the files from the glx-legacy-1733 package removed including the /etc/X11/xorg.d directory. I think users would benefit from an 'uninstall nvidia driver' wiki page. Regards
Re: Procedure to uninstall nvidia drivers and restore nouveau
On Tue, 2013-11-12 at 21:17 +, Alex Naysmith wrote: Thank you all for the sed regex explanation. What possible kernel variations other than 'generic' are possible to require the sed substitution? I guess there isn't a kernel named generic available by Debian repositories and the name extension not always is at the end of the name, however there are tons of kernels rt rtai lowlatency pae xen desktop and others -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1384294694.1079.16.camel@archlinux
Re: Procedure to uninstall nvidia drivers and restore nouveau
Le 10.11.2013 22:44, Alex Naysmith a écrit : After following the procedure at https://wiki.debian.org/NvidiaGraphicsDrivers [1] to install the nvidia-glx-legacy-173xx package for my GeForce FX5550 card [Debian 7 Wheezy], I would like to know the best method to return to the nouveau driver with the files from the glx-legacy-1733 package removed including the /etc/X11/xorg.d directory. I think users would benefit from an 'uninstall nvidia driver' wiki page. Regards Links: -- [1] https://wiki.debian.org/NvidiaGraphicsDrivers If you installed NVidia through the Debian's package in non-free sections, then simply remove it, with #aptitude purge nvidia-kernel-dkms nvidia-glx You will then need to install nouveau drivers, and you can do that with: #aptitude install xserver-xorg-videa-nouveau -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/d8b8f0f302842b201f8b9a9297380...@neutralite.org
Re: Procedure to uninstall nvidia drivers and restore nouveau
On Mon, 2013-11-11 at 15:25 +0100, berenger.mo...@neutralite.org wrote: Le 10.11.2013 22:44, Alex Naysmith a écrit : After following the procedure at https://wiki.debian.org/NvidiaGraphicsDrivers [1] to install the nvidia-glx-legacy-173xx package for my GeForce FX5550 card [Debian 7 Wheezy], I would like to know the best method to return to the nouveau driver with the files from the glx-legacy-1733 package removed including the /etc/X11/xorg.d directory. I think users would benefit from an 'uninstall nvidia driver' wiki page. Regards Links: -- [1] https://wiki.debian.org/NvidiaGraphicsDrivers If you installed NVidia through the Debian's package in non-free sections, then simply remove it, with ^^ I guess this is incorrect ... #aptitude purge nvidia-kernel-dkms nvidia-glx ^^ ... but the command is correct ;), but I'm not sure how Debian handles /etc/X11/xorg... You will then need to install nouveau drivers, and you can do that with: #aptitude install xserver-xorg-videa-nouveau -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1384183104.666.39.camel@archlinux
Re: Procedure to uninstall nvidia drivers and restore nouveau
Le 11.11.2013 16:18, Ralf Mardorf a écrit : On Mon, 2013-11-11 at 15:25 +0100, berenger.mo...@neutralite.org wrote: Le 10.11.2013 22:44, Alex Naysmith a écrit : After following the procedure at https://wiki.debian.org/NvidiaGraphicsDrivers [1] to install the nvidia-glx-legacy-173xx package for my GeForce FX5550 card [Debian 7 Wheezy], I would like to know the best method to return to the nouveau driver with the files from the glx-legacy-1733 package removed including the /etc/X11/xorg.d directory. I think users would benefit from an 'uninstall nvidia driver' wiki page. Regards Links: -- [1] https://wiki.debian.org/NvidiaGraphicsDrivers If you installed NVidia through the Debian's package in non-free sections, then simply remove it, with ^^ I guess this is incorrect ... #aptitude purge nvidia-kernel-dkms nvidia-glx ^^ ... but the command is correct ;), but I'm not sure how Debian handles /etc/X11/xorg... You got me. Indeed, it need to be purged. Probably. I simply never use the remove commands... If I want to remove a package, I want no traces. I did not switched away from windows for nothing btw... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/049a1efc56f1938fe88aa2601e13d...@neutralite.org
Re: Procedure to uninstall nvidia drivers and restore nouveau
On Mon, 2013-11-11 at 16:20 +0100, berenger.mo...@neutralite.org wrote: Le 11.11.2013 16:18, Ralf Mardorf a écrit : On Mon, 2013-11-11 at 15:25 +0100, berenger.mo...@neutralite.org wrote: Le 10.11.2013 22:44, Alex Naysmith a écrit : After following the procedure at https://wiki.debian.org/NvidiaGraphicsDrivers [1] to install the nvidia-glx-legacy-173xx package for my GeForce FX5550 card [Debian 7 Wheezy], I would like to know the best method to return to the nouveau driver with the files from the glx-legacy-1733 package removed including the /etc/X11/xorg.d directory. I think users would benefit from an 'uninstall nvidia driver' wiki page. Regards Links: -- [1] https://wiki.debian.org/NvidiaGraphicsDrivers If you installed NVidia through the Debian's package in non-free sections, then simply remove it, with ^^ I guess this is incorrect ... #aptitude purge nvidia-kernel-dkms nvidia-glx ^^ ... but the command is correct ;), but I'm not sure how Debian handles /etc/X11/xorg... You got me. Indeed, it need to be purged. Probably. I simply never use the remove commands... If I want to remove a package, I want no traces. I did not switched away from windows for nothing btw... I suspect that xorg.conf will not be removed, even not when using purge. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1384183745.666.40.camel@archlinux
Re: Procedure to uninstall nvidia drivers and restore nouveau
On 2013-11-11, Ralf Mardorf ralf.mard...@alice-dsl.net wrote: I suspect that xorg.conf will not be removed, even not when using purge. Will the nouveau driver be unblacklisted after the purge? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnl822np.1ul.cu...@einstein.electron.org
Re: Procedure to uninstall nvidia drivers and restore nouveau
On Mon, Nov 11, 2013 at 04:50:36PM +, Curt wrote: On 2013-11-11, Ralf Mardorf ralf.mard...@alice-dsl.net wrote: I suspect that xorg.conf will not be removed, even not when using purge. Will the nouveau driver be unblacklisted after the purge? Ask yourself - Would you, as system administrator, expect this? then maybe. The other consideration is that if the details are in a configuration file that the system administrator has changed then I think no, but you will see a message from dpkg along the lines of directory xxx not empty so not removed I think. You could always try it and see. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2013171439.GD8413@tal
Re: Procedure to uninstall nvidia drivers and restore nouveau
Le 11/11/2013 18:14, Chris Bannister a écrit : On Mon, Nov 11, 2013 at 04:50:36PM +, Curt wrote: On 2013-11-11, Ralf Mardorf ralf.mard...@alice-dsl.net wrote: I suspect that xorg.conf will not be removed, even not when using purge. Will the nouveau driver be unblacklisted after the purge? Ask yourself - Would you, as system administrator, expect this? then maybe. The other consideration is that if the details are in a configuration file that the system administrator has changed then I think no, but you will see a message from dpkg along the lines of directory xxx not empty so not removed I think. You could always try it and see. As defaullt the blacklisting is in a file in /etc/modules.d that the nvidia driver installs and that should be removed by purging all nvidia packages -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52811100.9010...@rail.eu.org
Re: Procedure to uninstall nvidia drivers and restore nouveau
On 2013-11-11, Chris Bannister cbannis...@slingshot.co.nz wrote: Will the nouveau driver be unblacklisted after the purge? Ask yourself - Would you, as system administrator, expect this? then Oh, sorry, I thought you were answering the OP, a newbie who asked for the procedure (even a wiki) involved in going back to the nouveau driver from the nvidia packages, which might involve manually unblacklisting the nouveau driver (or not), a potentially lethal point which I don't believe you mentioned. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnl825nm.1ul.cu...@einstein.electron.org
Re: Procedure to uninstall nvidia drivers and restore nouveau
From the nvidia install procedure is the following command: # aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') nvidia-kernel-legacy-173xx-dkms I can see the pipe | symbol and the regular expressions but I don't really understand what this command is doing. Alex On 10 November 2013 21:44, Alex Naysmith yeoman.pyt...@gmail.com wrote: After following the procedure at https://wiki.debian.org/NvidiaGraphicsDrivers to install the nvidia-glx-legacy-173xx package for my GeForce FX5550 card [Debian 7 Wheezy], I would like to know the best method to return to the nouveau driver with the files from the glx-legacy-1733 package removed including the /etc/X11/xorg.d directory. I think users would benefit from an 'uninstall nvidia driver' wiki page. Regards
Procedure to uninstall nvidia drivers and restore nouveau
After following the procedure at https://wiki.debian.org/NvidiaGraphicsDrivers to install the nvidia-glx-legacy-173xx package for my GeForce FX5550 card [Debian 7 Wheezy], I would like to know the best method to return to the nouveau driver with the files from the glx-legacy-1733 package removed including the /etc/X11/xorg.d directory. I think users would benefit from an 'uninstall nvidia driver' wiki page. Regards
Re: libGL.so.1 and nvidia drivers
On 07/16/13 at 09:13pm, Brad Alexander wrote: I'm using the nvidia drivers from the repos on a sid machine. They were just upgraded to the long-term 319.32-1 from the repos. However, I have cisco's anyconnect, and when I launch it, I get $ /opt/cisco/anyconnect/bin/vpnui /opt/cisco/anyconnect/bin/vpnui: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory However, the library is installed (part of libgl1-nvidia-glx), even though it does not appear in ldconfig -v, and through a whole series of /etc/alternatives symlinks, On a different troubleshooting tack, why are you running a UI that requires OpenGL? I've found that the vpnc package works just fine for Cisco VPNs. -- WIlliam signature.asc Description: Digital signature
Re: libGL.so.1 and nvidia drivers
Am Tue, 16 Jul 2013 21:13:40 -0400 schrieb Brad Alexander stor...@gmail.com: I'm using the nvidia drivers from the repos on a sid machine. They were just upgraded to the long-term 319.32-1 from the repos. However, I have cisco's anyconnect, and when I launch it, I get $ /opt/cisco/anyconnect/bin/vpnui /opt/cisco/anyconnect/bin/vpnui: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory To find out which path is asked exactly, try $ strace /opt/cisco/anyconnect/bin/vpnui | grep libGL HTH, Kardan -- Kardan kar...@riseup.net Encrypt your email: http://gnupg.org/documentation Public GPG key 9D6108AE58C06558 at hkp://pool.sks-keyservers.net fpr: F72F C4D9 6A52 16A1 E7C9 AE94 9D61 08AE 58C0 6558 signature.asc Description: PGP signature
libGL.so.1 and nvidia drivers
I'm using the nvidia drivers from the repos on a sid machine. They were just upgraded to the long-term 319.32-1 from the repos. However, I have cisco's anyconnect, and when I launch it, I get $ /opt/cisco/anyconnect/bin/vpnui /opt/cisco/anyconnect/bin/vpnui: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory However, the library is installed (part of libgl1-nvidia-glx), even though it does not appear in ldconfig -v, and through a whole series of /etc/alternatives symlinks, /usr/lib/x86_64-linux-gnu/libGL.so.1 - /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 - /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 - libGL.so.319.32 -rw-r--r-- 1 root root 1144680 Jun 19 17:55 /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.319.32 So what is it I'm missing here? Why is libGL.so.1 not in ldconfig? ldconfig -v | grep GL /sbin/ldconfig.real: Can't stat /lib/i486-linux-gnu: No such file or directory /sbin/ldconfig.real: Can't stat /usr/lib/i486-linux-gnu: No such file or directory /sbin/ldconfig.real: Path `/lib/x86_64-linux-gnu' given more than once /sbin/ldconfig.real: Path `/usr/lib/x86_64-linux-gnu' given more than once libEGL.so.1 - libEGL.so.1.0.0 libGLEWmx.so.1.7 - libGLEWmx.so.1.7.0 libGLEW.so.1.7 - libGLEW.so.1.7.0 libGLU.so.1 - libGLU.so.1.3.1 libQtOpenGL.so.4 - libQtOpenGL.so.4.8.5 libEGL.so.1 - libEGL.so.1.0.0 I need to get the vpn client running. Can someone shed some light? Thanks, --b
Re: Nvidia drivers problem Geforce 570
On Thu, Jun 7, 2012 at 6:20 PM, jeremy jozwik jerjoz.for...@gmail.com wrote: sorry for not being so clear. i dont have the machine in front of me at the moment to type out the exact error but i installed the driver ones. the install was building the man triggers and i tossed up an error for the nvidia driver. since then EVERYTHING i install ones complete APT tries to fix the nvidia install and that same error shows up. i have just been ignoring it. everything works fine so im not very concerned. here you go, i just updated my system last night. after the openoffice install process apt tried to fix the nvidia install again: Setting up openoffice.org-emailmerge (1:3.2.1-11+squeeze6) ... Copying: mailmerge.py Enabling: mailmerge.py unopkg done. Processing triggers for libgl1-nvidia-alternatives ... update-alternatives: error: alternative path /usr/lib/nvidia/diversions/libGL.so.1 doesn't exist. dpkg: error processing libgl1-nvidia-alternatives (--configure): subprocess installed post-installation script returned error exit status 2 configured to not write apport reports Processing triggers for menu ... Errors were encountered while processing: libgl1-nvidia-alternatives E: Sub-process /usr/bin/dpkg returned an error code (1) # -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAN=ioVnRUYNk=vr1yh2zyo_vkincpn4rvpafkmuzptfbasw...@mail.gmail.com
RE: Nvidia drivers problem Geforce 570
Well i have started from fresh again to attempt to get my resolution problem
fixed with my Geforce 570 but it now seems that i have a misconfiguration in my
xorg.conf
so this is exactly what i have done so far
# apt-get install module-assistant nvidia-kernel-common
# m-a auto-install nvidia-kernel${VERSION}-source
# apt-get install nvidia-glx${VERSION}
And then to configure X to use the nvidia driver there are 2 ways, manually
creating xorg or modifying existing or to use
nvidia-xconfig. Due to a bug at the moment with nvidia-xconfig i tried it and
failed so this time i decided to try the xorg.conf way
Since this is a fresh install i didnt have an existing xorg.conf i made one
with the cut and paste config from wiki.debian.org
then i pasted in this
Section Module
Loadglx
EndSection
Section Device
Identifier Video Card
Driver nvidia
EndSection
So by me saving this xorg.conf then running
invoke-rc.d gdm3 restart
I get a screen with a white little flashing - up in top left
i can ctrl-alt F2 to another screen so i can fix it. It seems apparent to me
that my xorg.conf is misconfigured but because
i dont have another .conf to compare it to i dont know what its missing.
when running glxinfo |grep rendering i get the following output
Xlib: extension GLX missing on display :0.0.
Xlib: extension GLX missing on display :0.0.
Xlib: extension GLX missing on display :0.0.
Xlib: extension GLX missing on display :0.0.
Xlib: extension GLX missing on display :0.0.
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension GLX missing on display :0.0.
Xlib: extension GLX missing on display :0.0.
Xlib: extension GLX missing on display :0.0.
Xlib: extension GLX missing on display :0.0.
Xlib: extension GLX missing on display :0.0.
and then in the xorg.0.log i found
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
(--) VESA(0): Virtual size is 1600x1200 (pitch 1600)
They werent one line after another i just found them from the log and pasted
them here like this.
The monitor i am using i want to run at 2560x1440 but is only currently using
1600x1200
Does anyone have a working xorg.conf with an nvidia card that i could test with
please?
And also does anyone know if the xorg.conf is configured correctly to use the
GLX driver then does Vesa get disabled
by default or do i have to explicitly define X not to use the drivers elsewhere?
Sorry that its quite a long post but appreciate any help in advance
Thanks,
Nathan
Date: Fri, 8 Jun 2012 07:22:44 -0700
Subject: Re: Nvidia drivers problem Geforce 570
From: jerjoz.for...@gmail.com
To: debian-user@lists.debian.org
On Thu, Jun 7, 2012 at 6:20 PM, jeremy jozwik jerjoz.for...@gmail.com wrote:
sorry for not being so clear. i dont have the machine in front of me
at the moment to type out the exact error but i installed the driver
ones. the install was building the man triggers and i tossed up an
error for the nvidia driver. since then EVERYTHING i install ones
complete APT tries to fix the nvidia install and that same error shows
up.
i have just been ignoring it. everything works fine so im not very
concerned.
here you go, i just updated my system last night. after the openoffice
install process apt tried to fix the nvidia install again:
Setting up openoffice.org-emailmerge (1:3.2.1-11+squeeze6) ...
Copying: mailmerge.py
Enabling: mailmerge.py
unopkg done.
Processing triggers for libgl1-nvidia-alternatives ...
update-alternatives: error: alternative path
/usr/lib/nvidia/diversions/libGL.so.1 doesn't exist.
dpkg: error processing libgl1-nvidia-alternatives (--configure):
subprocess installed post-installation script returned error exit status 2
configured to not write apport reports
Processing triggers for menu ...
Errors were encountered while processing:
libgl1-nvidia-alternatives
E: Sub-process /usr/bin/dpkg returned an error code (1)
#
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAN=ioVnRUYNk=vr1yh2zyo_vkincpn4rvpafkmuzptfbasw...@mail.gmail.com
Nvidia drivers problem Geforce 570
Hello everyone! I wanted to know has anyone had any issues getting nvidia drivers working for a Geforce 5xx series card under Debian 6 squeeze? I'm running a Geforce 570 running a Dell 27 IPS screen that has a res of 2560 x 1440, the res isn't displaying correctly, it has blurry lines over the text like its not doing any anti-aliasing. I followed http://wiki.debian.org/NvidiaGraphicsDrivers and everything seemed to go well as far as installing went. The problem protruded its ugly head when i attempted to tell xorg.conf to use the glx driver both by creating my own xorg or nvidia-xconfig. I realize there is a bug reported with nvidia-xconfig so i dont expect any help on that one. I'm not on the machine right now so cant give you an exact error from xorg.log or excerpt from my xorg.conf but that will come, will provide these later tonight. I just wanted to know if anyone has had success with closed source nvidia drivers in Debian 6 squeeze :)
Re: Nvidia drivers problem Geforce 570, Have not used this model GPU, sorry.
On 06/07/2012 08:11 PM, Nathan D'elboux wrote: Hello everyone! I wanted to know has anyone had any issues getting nvidia drivers working for a Geforce 5xx series card under Debian 6 squeeze? I'm running a Geforce 570 running a Dell 27 IPS screen that has a res of 2560 x 1440, the res isn't displaying correctly, it has blurry lines over the text like its not doing any anti-aliasing. I followed http://wiki.debian.org/NvidiaGraphicsDrivers and everything seemed to go well as far as installing went. The problem protruded its ugly head when i attempted to tell xorg.conf to use the glx driver both by creating my own xorg or nvidia-xconfig. I realize there is a bug reported with nvidia-xconfig so i dont expect any help on that one. I'm not on the machine right now so cant give you an exact error from xorg.log or excerpt from my xorg.conf but that will come, will provide these later tonight. I just wanted to know if anyone has had success with closed source nvidia drivers in Debian 6 squeeze :)
RE: Nvidia drivers problem Geforce 570, Have not used this model GPU, sorry.
Sorry was suppose to reply all :) RE: Nvidia drivers problem Geforce 570, Have not used this model GPU, sorry. What model are you using? I also have a 5xxx series and a 8800GTX and 8800GT to swap out and see, i just haven't tried that yet Date: Thu, 7 Jun 2012 20:19:49 -0400 From: saqman2...@gmail.com To: debian-user@lists.debian.org Subject: Re: Nvidia drivers problem Geforce 570, Have not used this model GPU, sorry. On 06/07/2012 08:11 PM, Nathan D'elboux wrote: Hello everyone! I wanted to know has anyone had any issues getting nvidia drivers working for a Geforce 5xx series card under Debian 6 squeeze? I'm running a Geforce 570 running a Dell 27 IPS screen that has a res of 2560 x 1440, the res isn't displaying correctly, it has blurry lines over the text like its not doing any anti-aliasing. I followed http://wiki.debian.org/NvidiaGraphicsDrivers and everything seemed to go well as far as installing went. The problem protruded its ugly head when i attempted to tell xorg.conf to use the glx driver both by creating my own xorg or nvidia-xconfig. I realize there is a bug reported with nvidia-xconfig so i dont expect any help on that one. I'm not on the machine right now so cant give you an exact error from xorg.log or excerpt from my xorg.conf but that will come, will provide these later tonight. I just wanted to know if anyone has had success with closed source nvidia drivers in Debian 6 squeeze :)
Re: Nvidia drivers problem Geforce 570
On Thu, Jun 7, 2012 at 5:11 PM, Nathan D'elboux naf...@hotmail.com wrote: Hello everyone! I wanted to know has anyone had any issues getting nvidia drivers working for a Geforce 5xx series card under Debian 6 squeeze? I'm running a Geforce 570 running a Dell 27 IPS screen that has a res of 2560 x 1440, the res isn't displaying correctly, it has blurry lines over the text like its not doing any anti-aliasing. I followed http://wiki.debian.org/NvidiaGraphicsDrivers and everything seemed to go well as far as installing went. The problem protruded its ugly head when i attempted to tell xorg.conf to use the glx driver both by creating my own xorg or nvidia-xconfig. I realize there is a bug reported with nvidia-xconfig so i dont expect any help on that one. I'm not on the machine right now so cant give you an exact error from xorg.log or excerpt from my xorg.conf but that will come, will provide these later tonight. I just wanted to know if anyone has had success with closed source nvidia drivers in Debian 6 squeeze :) i have my gtx 580 working ok with the nvidia linux driver. sadly it throws an install error for every install since i ran the nvidia driver. i dont have the machine in front of me right now to list the specific error. but the card itself is working well. i went with the nvidia driver because the linux one at the time did no support the card. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAN=ioVk1BNZSWXH=e+v+dhmrr-hq+vmddg+m+5eavrpt9ki...@mail.gmail.com
