| 2007-02-11 23:30:51 |
Zen-Owl |
bug |
|
|
added bug |
| 2007-02-11 23:33:16 |
Zen-Owl |
description |
This is a problem concerning updating to the latest NVIDIA drivers.
When the package linux-restricted-modules-* is installed a system, and one tries to install the NVIDIA drivers with their third-party installer, the linux-restricted-modules package keeps it's kernel module, while the X server tries to use the driver from the installer; causing a difficult to fix version mismatch. This version mismatch obviously stops the X server from starting.
The ways to fix this are,
1) To remove the installers components, `sh NVIDIA-* --uninstall`
2) To manually delete the modules in /lib that conflict (hackish)
3) To use a third party to gain a more up to date version of linux-restricted-modules
As you can see none of these fixes are very easy or user friendly, so this behavior should be fixed. |
This is a problem concerning updating to the latest NVIDIA drivers.
When the package linux-restricted-modules-* is installed on a system, and one tries to install the NVIDIA drivers with their third-party installer, the linux-restricted-modules package keeps it's kernel module, while the X server tries to use the driver from the installer; causing a difficult to fix version mismatch. This version mismatch obviously stops the X server from starting.
The ways to fix this are,
1) To remove the installers components, `sh NVIDIA-* --uninstall`
2) To manually delete the modules in /lib that conflict (hackish)
3) To use a third party to gain a more up to date version of linux-restricted-modules
As you can see none of these fixes are very easy or user friendly; so, in my opinion, this behavior should be fixed. |
|
| 2007-02-11 23:34:44 |
Zen-Owl |
description |
This is a problem concerning updating to the latest NVIDIA drivers.
When the package linux-restricted-modules-* is installed on a system, and one tries to install the NVIDIA drivers with their third-party installer, the linux-restricted-modules package keeps it's kernel module, while the X server tries to use the driver from the installer; causing a difficult to fix version mismatch. This version mismatch obviously stops the X server from starting.
The ways to fix this are,
1) To remove the installers components, `sh NVIDIA-* --uninstall`
2) To manually delete the modules in /lib that conflict (hackish)
3) To use a third party to gain a more up to date version of linux-restricted-modules
As you can see none of these fixes are very easy or user friendly; so, in my opinion, this behavior should be fixed. |
This is a problem concerning updating to the latest NVIDIA drivers.
When the package linux-restricted-modules-* is installed on a system, and one tries to install the NVIDIA drivers with their third-party installer, the linux-restricted-modules package keeps it's kernel module, while the X server tries to use the driver from the installer; causing a difficult to fix version mismatch. This version mismatch obviously stops the X server from starting.
The ways to fix this are,
1) To remove the installers components, `sh NVIDIA-* --uninstall`
2) To manually delete the modules in /lib that conflict (hackish)
3) To use a third party repository to gain a more up to date version of linux-restricted-modules
As you can see none of these fixes are very easy or user friendly; so, in my opinion, this behavior should be fixed. |
|
| 2008-02-07 23:06:55 |
Timo Aaltonen |
linux-restricted-modules-2.6.17: status |
New |
Won't Fix |
|
