After upegrade Ubuntu dont start: no resolution available

Asked by pwrdesc on 2014-05-06

I have a 16/10 17inch screen and a graphic card nVidia GeForce. Starting UBUNTU 14.04 after upgrade, the process abort with a little window saying "Correct screen resolution not found" (or something like that). With UBUNTU 13.10 I used a 1400x900 screen size.
Hopefully I can use KUBUNTU 14.04 but with a 1280x1024 resolution wich is wrong for a wide screen.
How can I restart UBUNTU ?

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
Uname: Linux 3.8.0-31-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: kwin
Date: Tue May 6 11:57:35 2014
DistUpgraded: 2014-04-19 06:02:25,370 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7: added
 nvidia-331-updates, 331.38: added
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation C77 [GeForce 8300] [10de:0848] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:82e2]
InstallationDate: Installed on 2013-08-11 (267 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=addcc404-72ab-423b-9b9a-72188ac6be96 ro quiet splash
SourcePackage: xorg
UnitySupportTest:
 Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 5: Xlib: extension "GLX" missing on display ":0".
 Error: GLX is not available on the system
UpgradeStatus: Upgraded to trusty on 2014-04-19 (17 days ago)
dmi.bios.date: 09/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4N78 PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue May 6 11:51:48 2014
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Video Bus KEYBOARD, id 7
 input Power Button KEYBOARD, id 8
 input Logitech USB-PS/2 Optical Mouse MOUSE, id 9
 input AT Translated Set 2 keyboard KEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu xorg Edit question
Assignee:
No assignee Edit question
Last query:
2014-05-06
Last reply:
2014-05-06

Converting to a question because user is running unsupported kernel.

You are using an old kernel: 3.8.0-31.46-generic 3.8.13.8
Subsequently, the nvidia driver/kernel module does not load and you get stuck with generic VESA driver.

Boot into the regular Trusty kernel (3.13.x) and remove the old kernel.

Can you help with this problem?

Provide an answer of your own, or ask pwrdesc for more information if necessary.

To post a message you must log in.