nvidia drivers and synaptic issues

Post your update and upgrade related errors here
Forum rules
Before you post please read this

nvidia drivers and synaptic issues

Postby mercier on Sun Dec 11, 2011 1:27 pm

tried to install nvidia-glx drivers through synaptic, and now i'm getting :

Code: Select all
E: nvidia-kernel-common: subprocess installed post-installation script returned error exit status 1
E: nvidia-kernel-dkms: dependency problems - leaving unconfigured


on every install of files with synaptic. searcehd for the solution, but i found too many to dare to try and fix it myself.

the following command
Code: Select all
 aptitude search nvidia|egrep -v "^p   |^v   "


gives:
Code: Select all
i   glx-alternative-nvidia          - allows the selection of NVIDIA as GLX prov
i   libgl1-nvidia-alternatives      - transition libGL.so* diversions to glx-alt
i   libgl1-nvidia-glx               - NVIDIA binary OpenGL libraries           
i   libglx-nvidia-alternatives      - transition libgl.so diversions to glx-alte
i   nvidia-alternative              - allows the selection of NVIDIA as GLX prov
i   nvidia-installer-cleanup        - Cleanup after driver installation with the
C   nvidia-kernel-common            - NVIDIA binary kernel module support files
u   nvidia-kernel-dkms              - NVIDIA binary kernel module DKMS source   
i   nvidia-support                  - NVIDIA binary graphics driver support file
i   nvidia-vdpau-driver             - NVIDIA vdpau driver                       
i   xserver-xorg-video-nvidia       - NVIDIA binary Xorg driver 


furthermore, upon starting windows 7 in vmware player the following message appears:
Code: Select all
Direct rendering is not available.
As a result, this virtual machine may experience very low graphics performance. Follow the instructions provided by your graphics card vendor or Linux distribution in order to update your computer's OpenGL drivers.


lmde 64 bit.

thank you in advance
mercier
Level 3
Level 3
 
Posts: 141
Joined: Sun Jan 06, 2008 1:37 pm

Linux Mint is funded by ads and donations.
 

Re: nvidia drivers and synaptic issues

Postby Lendo on Tue Dec 13, 2011 1:59 am

try this in a terminal.

apt install nvidia-kernel-dkms nvidia-glx build-essential nvidia-settings nvidia-xconfig

also, see viewtopic.php?f=191&t=82424

I had to remove the nouveau drivers too.
Life is too short to waste it on Microsoft.
User avatar
Lendo
Level 2
Level 2
 
Posts: 85
Joined: Thu Mar 31, 2011 4:47 pm
Location: Snow Covered Canada

Re: nvidia drivers and synaptic issues

Postby mercier on Tue Dec 13, 2011 5:19 am

thank you for trying to help. it did not work, though.

this is the terminal output in full:

Code: Select all
Reading package lists... Done
Building dependency tree       
Reading state information... Done
build-essential is already the newest version.
nvidia-xconfig is already the newest version.
nvidia-glx is already the newest version.
nvidia-kernel-dkms is already the newest version.
The following NEW packages will be installed:
  nvidia-settings
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
3 not fully installed or removed.
Need to get 858 kB of archives.
After this operation, 1,860 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://debian.linuxmint.com/incoming/ testing/contrib nvidia-settings amd64 280.13-1 [858 kB]
Fetched 858 kB in 11s (75.3 kB/s)                                             
Selecting previously deselected package nvidia-settings.
(Reading database ... 189176 files and directories currently installed.)
Unpacking nvidia-settings (from .../nvidia-settings_280.13-1_amd64.deb) ...
Processing triggers for menu ...
Processing triggers for man-db ...
Processing triggers for gnome-menus ...
Processing triggers for desktop-file-utils ...
Setting up nvidia-kernel-common (20110729+1) ...
insserv: warning: script 'K01vmware' missing LSB tags and overrides
insserv: warning: script 'S50vmware-USBArbitrator' missing LSB tags and overrides
insserv: warning: script 'vmware' missing LSB tags and overrides
insserv: warning: script 'vmware-USBArbitrator' missing LSB tags and overrides
insserv: There is a loop at service rc.local if started
insserv: There is a loop between service vmware-USBArbitrator and mountnfs if started
insserv:  loop involving service mountnfs at depth 7
insserv:  loop involving service portmap at depth 6
insserv: There is a loop between service rc.local and mountall if started
insserv:  loop involving service mountall at depth 4
insserv:  loop involving service checkfs at depth 3
insserv:  loop involving service mountnfs-bootclean at depth 9
insserv:  loop involving service networking at depth 6
insserv: There is a loop between service vmware-USBArbitrator and checkroot if started
insserv:  loop involving service checkroot at depth 3
insserv:  loop involving service keyboard-setup at depth 2
insserv:  loop involving service alsa-utils at depth 11
insserv:  loop involving service cryptdisks at depth 5
insserv:  loop involving service hwclockfirst at depth 3
insserv: There is a loop between service vmware-USBArbitrator and checkroot if started
insserv:  loop involving service hostname at depth 4
insserv:  loop involving service cryptdisks-early at depth 6
insserv:  loop involving service module-init-tools at depth 6
insserv: There is a loop between service rc.local and ifupdown-clean if started
insserv:  loop involving service ifupdown-clean at depth 6
insserv: There is a loop between service rc.local and mountoverflowtmp if started
insserv:  loop involving service mountoverflowtmp at depth 11
insserv:  loop involving service mountall-bootclean at depth 10
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv:  loop involving service hddtemp at depth 2
insserv:  loop involving service rsyslog at depth 16
insserv:  loop involving service vmware-USBArbitrator at depth 1
insserv:  loop involving service kbd at depth 11
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing nvidia-kernel-common (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
                                      dpkg: dependency problems prevent configuration of nvidia-kernel-dkms:
 nvidia-kernel-dkms depends on nvidia-kernel-common (>= 20100522); however:
  Package nvidia-kernel-common is not configured yet.
dpkg: error processing nvidia-kernel-dkms (--configure):
 dependency problems - leaving unconfigured
configured to not write apport reports
                                      dpkg: dependency problems prevent configuration of nvidia-glx:
 nvidia-glx depends on nvidia-kernel-280.13; however:
  Package nvidia-kernel-280.13 is not installed.
  Package nvidia-kernel-dkms which provides nvidia-kernel-280.13 is not configured yet.
dpkg: error processing nvidia-glx (--configure):
 dependency problems - leaving unconfigured
configured to not write apport reports
                                      Setting up nvidia-settings (280.13-1) ...
Processing triggers for menu ...
Errors were encountered while processing:
 nvidia-kernel-common
 nvidia-kernel-dkms
 nvidia-glx
E: Sub-process /usr/bin/dpkg returned an error code (1)


the above link states to remove noveau driver after installing nvidia, but does that apply in my case- since obviously installation of nvidia driver is not working...

if i follow the instructions from your link with this:
Code: Select all
apt-get purge xserver-xorg-video-nouveau libdrm-nouveau1a

i get this in the terminal:
Code: Select all
sudo apt-get purge xserver-xorg-video-nouveau libdrm-nouveau1a
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  libdrm-nouveau1a* xserver-xorg-video-all* xserver-xorg-video-nouveau*
0 upgraded, 0 newly installed, 3 to remove and 2 not upgraded.
3 not fully installed or removed.
After this operation, 1,053 kB disk space will be freed.
Do you want to continue [Y/n]?


do i go for Y now or not? :D
mercier
Level 3
Level 3
 
Posts: 141
Joined: Sun Jan 06, 2008 1:37 pm

Re: nvidia drivers and synaptic issues

Postby twa on Tue Dec 13, 2011 6:21 am

mercier,
may I suggest U to install smxi and let it take care of sysm updates and NVidia installation.??
have always used it since my first install of LMDE on sept-2010 and never had problems.
http://smxi.org/
once U have understood how it works, it's very simple.
read tutorial first !
cheers
When an issue has been resolved for you, please edit the original post to include <SOLVED> in the title. This provides a good indicator for users with a similar problem to check out the thread.
User avatar
twa
Level 4
Level 4
 
Posts: 231
Joined: Fri Sep 17, 2010 8:11 am
Location: Somewhere in the sky

Re: nvidia drivers and synaptic issues

Postby mercier on Thu Dec 15, 2011 3:26 am

well, thank you both. i managed to get to myself out of x and no way back in.

finally, after some two months, i gave up on lmde "stability". now, i am enjoying the stability of lisa :D
mercier
Level 3
Level 3
 
Posts: 141
Joined: Sun Jan 06, 2008 1:37 pm

Re: nvidia drivers and synaptic issues

Postby Lendo on Thu Dec 15, 2011 11:20 pm

Only removing nouveau drivers worked for me. When I tried black listing I had problems with .conf files.
Life is too short to waste it on Microsoft.
User avatar
Lendo
Level 2
Level 2
 
Posts: 85
Joined: Thu Mar 31, 2011 4:47 pm
Location: Snow Covered Canada


Return to Update/Upgrade Issues

Who is online

Users browsing this forum: No registered users and 4 guests