Lucid RC Live CD will not boot without NOMODESET flag

[Jim Brumbaugh]

Binary package hint: xorg

Computer Samsung M70 with an Nvidia GeForce Go 6600 128 MB graphics chipset with a 1680 x 1050 LCD display has not worked except in mode=771 on boot since upgrading to Ubuntu 9.10 from 9.04.

Tried the Lucid live cd RC .iso dated April 19th to see if problem had been fixed.

Live CD boot resulted in a very strange screen (looks like an analog effect). Correctly boots in generic mode when using the NOMODESET option on boot.

I should mention that on Nvdia's website, the Windows driver has apparently been withdrawn. There is in fact no mention of the GeForce Go 6600 chipset except on the part of the web site where they tout the specifications. Driver-wise this chip does not seem to exist.

As I will not install Ubuntu 10.04 until it goes live for my friends safety I don't know if the current drivers will currently work on his system. I just know that the Live CD fails to give back correct information about the LCD screen.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: x11-common 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Apr 25 00:27:23 2010
DkmsStatus: nvidia-current, 195.36.15, 2.6.32-21-generic, i686: installed
GdmLog1: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
Lsusb:
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: SAMSUNG ELECTRONICS CO.,LTD SM70S
PackageArchitecture: all
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- nomodeset
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 11/16/2005
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 02JD
dmi.board.name: SM70S
dmi.board.vendor: SAMSUNG ELECTRONICS CO.,LTD
dmi.board.version: Revision MP
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO.,LTD
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr02JD:bd11/16/2005:svnSAMSUNGELECTRONICSCO.,LTD:pnSM70S:pvrRevisionMP:rvnSAMSUNGELECTRONICSCO.,LTD:rnSM70S:rvrRevisionMP:cvnSAMSUNGELECTRONICSCO.,LTD:ct1:cvrN/A:
dmi.product.name: SM70S
dmi.product.version: Revision MP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO.,LTD
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-21-generic

[Bryce Harrington (bryce)]

Likely this bug is something in the linux kernel's nouveau drm driver. If that's true, then booting a newer version of the kernel might resolve it. Has anyone tested if this issue still exists with Lucid 10.04.4?

As we're on the cusp of the next LTS release, it would be worth testing if this issue exists in the 12.04 beta. This can be checked using a USB live image. You can get it at http://cdimage.ubuntu.com/daily/current/, and use USB Disk Creator to make a boot drive. Please update this bug report once you've tested. (If you've already tested any version of ubuntu newer than Lucid and already know it works, that's sufficient testing, just mention that here.)

[bugbot (bugbot)]

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.