From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-discuss/2012-August/008555.html | 136 +++++++++++++++++++++++++ 1 file changed, 136 insertions(+) create mode 100644 zarb-ml/mageia-discuss/2012-August/008555.html (limited to 'zarb-ml/mageia-discuss/2012-August/008555.html') diff --git a/zarb-ml/mageia-discuss/2012-August/008555.html b/zarb-ml/mageia-discuss/2012-August/008555.html new file mode 100644 index 000000000..e4c96ab1a --- /dev/null +++ b/zarb-ml/mageia-discuss/2012-August/008555.html @@ -0,0 +1,136 @@ + + + + [Mageia-discuss] How to re-enable nvidia driver for new kernel? + + + + + + + + + +

[Mageia-discuss] How to re-enable nvidia driver for new kernel?

+ Len Lawrence + tarazed25 at gmail.com +
+ Thu Aug 23 20:47:40 CEST 2012 +

+
+ +
On 23/08/12 19:21, Thomas Backlund wrote:
+> 23.08.2012 20:15, Len Lawrence skrev:
+>> Kernel update troubles.  The 3.3.8 kernel came down this afternoon
+>> along with the nvidia modules.  Installed them and restarted the PC as
+>> advised.  No video driver but a message flashed by which said
+>> something like nvidia 297.51 already installed against this kernel
+>> (which was true of 3.3.6).  The log messages gave no clue.  All they
+>> said was could not load nvidia, presumably because the module had not
+>> been compiled against the kernel.
+>>
+>
+> Hm,
+> the prebuilt modules for 3.3.8 should have been installed along with
+> the new kernel.
+>
+> What does theese commands say:
+>
+> rpm -qa |grep nvidia
+>
+> rpm -qa kernel*
+>
+>
+>> X fails also under the new kernel with xdriver=nouveau.  Maybe vesa
+>> would work but I did not try that.
+>>
+>> Now this sort of problem occurs again and again but on some lucky
+>> occasions dkms (?) comes into action at the reboot and recompiles the
+>> module and all is well.  Why should it be so hit and miss, mostly
+>> miss?
+>>
+>
+> dkms will only work if matching kernel-*-devel are installed...
+>
+>
+These are some of the checks I made:
+
+[root at belexeuli lcl]# urpmi kernel-headers
+Package kernel-userspace-headers-3.3.8-2.mga2.x86_64 is already installed
+
+[lcl at belexeuli ~]$ rpm -qa |grep nvidia
+x11-driver-video-nvidia-current-295.71-1.mga2.nonfree
+nvidia-current-doc-html-295.71-1.mga2.nonfree
+nvidia-current-kernel-3.3.6-desktop-2.mga2-295.49-4.mga2.nonfree
+dkms-nvidia-current-295.71-1.mga2.nonfree
+nvidia-current-kernel-desktop-latest-295.71-1.mga2.nonfree
+nvidia-current-kernel-3.3.8-desktop-2.mga2-295.71-1.mga2.nonfree
+
+[lcl at belexeuli ~]$ rpm -qa kernel*
+rpm: No match.
+
+[root at belexeuli lcl]# urpmi kernel-desktop-devel
+In order to satisfy the 
+'kernel-desktop-devel-3.3.8-2.mga2|kernel-desktop-devel-3.3.8-1.mga2|kernel-desktop-devel-3.3.6-2.mga2|kernel-desktop-devel-3.3.8-2.mga2|kernel-desktop-devel-3.3.8-2.mga2|kernel-desktop-devel-3.3.8-2.mga2|kernel-desktop-devel-3.3.6-2.mga2|kernel-desktop-devel-3.3.8-1.mga2' 
+dependency, one of the following packages is needed:
+  1- kernel-desktop-devel-3.3.6-2.mga2-1-1.mga2.x86_64: The kernel-devel 
+files for kernel-desktop-3.3.6-2.mga2 (to upgrade)
+  2- kernel-desktop-devel-3.3.8-2.mga2-1-1.mga2.x86_64: The kernel-devel 
+files for kernel-desktop-3.3.8-2.mga2 (to upgrade)
+What is your choice? (1-2) 2
+Package kernel-desktop-devel-3.3.8-2.mga2-1-1.mga2.x86_64 is already 
+installed
+
+Very puzzling.  Maybe something does need to be urpme'd as Doug suggested.
+
+Len
+
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-discuss +mailing list
+ -- cgit v1.2.1