recent updates broke the nvidia binary driver?! (64-current)
in [Slackware]
|
From: Martin on 5 Mar 2010 17:41 It seems that the recent updates broke my binary nvidia driver. The kernel and glibc is blacklisted so the slackpkg did not upgrade them. I'm still on 2.6.32.7 I did not switch off my computer for a few days. Today I did it and bump - can't startx I got the latest nvidia binary driver from their website. It seems to install fine, but when I startx: Warning: Error inserting agpgart (/lib/modules/2.6.32.7/kernel/drivers/char/agp/agpgart.ko): Invalid module format Fatal: Error inserting nvidia (lib/modules/2.6.32.7/kernel/drivers/video/nvidia.ko): invalid module format EE nvidia: failed to load the nvidia kernel module. Failed to load module 'nvidia' (module-specific error, 0) No drivers available Fatal server error: no screens found How could I solve it? thank you Martin
From: Andy on 5 Mar 2010 18:00 Martin wrote: > It seems that the recent updates broke my binary nvidia driver. > The kernel and glibc is blacklisted so the slackpkg did not upgrade > them. I'm still on 2.6.32.7 > I did not switch off my computer for a few days. Today I did it and bump > - can't startx > I got the latest nvidia binary driver from their website. It seems to > install fine, but when I startx: > > Warning: Error inserting agpgart > (/lib/modules/2.6.32.7/kernel/drivers/char/agp/agpgart.ko): Invalid > module format > Fatal: Error inserting nvidia > (lib/modules/2.6.32.7/kernel/drivers/video/nvidia.ko): invalid module > format EE nvidia: failed to load the nvidia kernel module. > Failed to load module 'nvidia' (module-specific error, 0) > No drivers available > Fatal server error: > no screens found > > > How could I solve it? > > thank you > Martin I had the same problem. As stupid as this sounds, try insmod. Worked for me. Something in the latest module-init-tools seems to be broken. Andy
From: Martin on 5 Mar 2010 18:09 On 03/05/2010 11:00 PM, Andy wrote: > Martin wrote: > >> It seems that the recent updates broke my binary nvidia driver. >> The kernel and glibc is blacklisted so the slackpkg did not upgrade >> them. I'm still on 2.6.32.7 >> I did not switch off my computer for a few days. Today I did it and bump >> - can't startx >> I got the latest nvidia binary driver from their website. It seems to >> install fine, but when I startx: >> >> Warning: Error inserting agpgart >> (/lib/modules/2.6.32.7/kernel/drivers/char/agp/agpgart.ko): Invalid >> module format >> Fatal: Error inserting nvidia >> (lib/modules/2.6.32.7/kernel/drivers/video/nvidia.ko): invalid module >> format EE nvidia: failed to load the nvidia kernel module. >> Failed to load module 'nvidia' (module-specific error, 0) >> No drivers available >> Fatal server error: >> no screens found >> >> >> How could I solve it? >> >> thank you >> Martin > > I had the same problem. As stupid as this sounds, try insmod. Worked for > me. Something in the latest module-init-tools seems to be broken. > > Andy Thanks Andy insmod nvidia insmod: can't read 'nvidia': no such file or directory modprobe nvidia gives me the warning and fatal error from the original error message I posted. -- regards Martin
From: Andy on 5 Mar 2010 18:22 Martin wrote: > On 03/05/2010 11:00 PM, Andy wrote: >> Martin wrote: >> >>> It seems that the recent updates broke my binary nvidia driver. >>> The kernel and glibc is blacklisted so the slackpkg did not upgrade >>> them. I'm still on 2.6.32.7 >>> I did not switch off my computer for a few days. Today I did it and bump >>> - can't startx >>> I got the latest nvidia binary driver from their website. It seems to >>> install fine, but when I startx: >>> >>> Warning: Error inserting agpgart >>> (/lib/modules/2.6.32.7/kernel/drivers/char/agp/agpgart.ko): Invalid >>> module format >>> Fatal: Error inserting nvidia >>> (lib/modules/2.6.32.7/kernel/drivers/video/nvidia.ko): invalid module >>> format EE nvidia: failed to load the nvidia kernel module. >>> Failed to load module 'nvidia' (module-specific error, 0) >>> No drivers available >>> Fatal server error: >>> no screens found >>> >>> >>> How could I solve it? >>> >>> thank you >>> Martin >> >> I had the same problem. As stupid as this sounds, try insmod. Worked >> for >> me. Something in the latest module-init-tools seems to be broken. >> >> Andy > Thanks Andy > > insmod nvidia > insmod: can't read 'nvidia': no such file or directory > > > modprobe nvidia gives me the warning and fatal error from the original > error message I posted. Try insmod /lib/modules/2.6.33/kernel/drivers/video/nvidia.ko Andy
From: Martin on 5 Mar 2010 18:31
On 03/05/2010 11:22 PM, Andy wrote: > Martin wrote: > >> On 03/05/2010 11:00 PM, Andy wrote: >>> Martin wrote: >>> >>>> It seems that the recent updates broke my binary nvidia driver. >>>> The kernel and glibc is blacklisted so the slackpkg did not upgrade >>>> them. I'm still on 2.6.32.7 >>>> I did not switch off my computer for a few days. Today I did it and bump >>>> - can't startx >>>> I got the latest nvidia binary driver from their website. It seems to >>>> install fine, but when I startx: >>>> >>>> Warning: Error inserting agpgart >>>> (/lib/modules/2.6.32.7/kernel/drivers/char/agp/agpgart.ko): Invalid >>>> module format >>>> Fatal: Error inserting nvidia >>>> (lib/modules/2.6.32.7/kernel/drivers/video/nvidia.ko): invalid module >>>> format EE nvidia: failed to load the nvidia kernel module. >>>> Failed to load module 'nvidia' (module-specific error, 0) >>>> No drivers available >>>> Fatal server error: >>>> no screens found >>>> >>>> >>>> How could I solve it? >>>> >>>> thank you >>>> Martin >>> >>> I had the same problem. As stupid as this sounds, try insmod. Worked >>> for >>> me. Something in the latest module-init-tools seems to be broken. >>> >>> Andy >> Thanks Andy >> >> insmod nvidia >> insmod: can't read 'nvidia': no such file or directory >> >> >> modprobe nvidia gives me the warning and fatal error from the original >> error message I posted. > > Try insmod /lib/modules/2.6.33/kernel/drivers/video/nvidia.ko > > Andy > Brilliant!!! It works. Thanks Where would I add it for it to be issued every time I restart the computer? -- regards Martin |