Everytime the system update I can't access Unity 3d

Asked by Mudito on 2012-05-25

This already happened 3 times, the solution is to re-install manually the package from NVidia web site, but when a new Ubuntu update is released all that work is lost and I have to do it again.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
Uname: Linux 3.2.0-24-generic-pae i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module 295.49 Mon Apr 30 23:30:07 PDT 2012
 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,place,vpswitch,regex,gnomecompat,session,commands,animation,move,snap,grid,mousepoll,imgpng,resize,wall,unitymtgrabhandles,workarounds,expo,ezoom,fade,scale,unityshell]
CompositorRunning: None
Date: Sat May 26 10:00:01 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
DkmsStatus:
 nvidia-current, 295.40, 3.2.0-24-generic-pae, i686: installed
 nvidia-current-updates, 295.49, 3.2.0-24-generic-pae, i686: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation G72M [Quadro NVS 110M] [10de:01da] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Device [1179:0001]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
JockeyStatus:
 xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use)
 pkg:sl-modem-daemon - Software modem (Proprietary, Enabled, In use)
 xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use)
MachineType: TOSHIBA Portable PC
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic-pae root=UUID=faaabe0a-924b-41d0-8298-26243bceffc3 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 3.70
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.70:bd01/29/2008:svnTOSHIBA:pnPortablePC:pvrVersion1.0:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: Portable PC
dmi.product.version: Version 1.0
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.7.8-0ubuntu1
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu nvidia-graphics-drivers Edit question
Assignee:
No assignee Edit question
Solved by:
Mudito
Solved:
2012-08-10
Last query:
2012-08-10
Last reply:
2012-08-10
Mudito (mudito-f) said : #1

More or less solved: removed NVIDA alltogether and reinstalled from "Adtional Drivers", before this procedure didn't work, now it did. But still, if anyone wants to use the latest provided by NVidia they will have problems everytime the system updates. I get the impression it is the kernel update which is screwing it.

Mudito (mudito-f) said : #2

Used the Additional Drivers function, this time it worked.