Nvidia G102M not working

[h1z]

Binary package hint: xserver-xorg-video-nouveau

After loading xorg, the screen becomes colored cubes and can not switch to virtual console.

[Bryce Harrington (bryce)]

Hi h1z,

Please run the command 'apport-collect BUGNUMBER', which will attach several files we need for debugging.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[tatsuno (carlos-troncoso)]

Architecture: amd64
DistroRelease: Ubuntu 10.04
DkmsStatus:
 nvidia-current, 195.36.15, 2.6.32-21-generic, x86_64: installed
 nvidia-current, 195.36.15, 2.6.32-22-generic, x86_64: installed
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK Computer Inc. K50IN
NonfreeKernelModules: nvidia
Package: xserver-xorg-video-nouveau 1:0.0.15+git20100219+9b4118d-0ubuntu5
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=2fb15fb4-b2bf-41b5-943d-08f524d9cb07 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=es_ES.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Tags: lucid lucid
Uname: Linux 2.6.32-21-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
dmi.bios.date: 08/26/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 217
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K50IN
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr217:bd08/26/2009:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: K50IN
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-21-generic

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[tatsuno (carlos-troncoso)]

apport information

[Bryce Harrington (bryce)]

@carlos-troncoso - thanks for providing that info, but we would like to see it from the original reporter. We may want to send this bug report upstream, but upstream has a hard and fast rule that logs from someone other than the original reporter are not acceptable. The reason for that is that quite often with X.org bug reports, two people may *think* they have the same issue based on commonality of symptoms and/or hardware, but in truth they have separate issues and mixing the report and the files can cause the developers some confusion.

If this bug report seems not to be getting attention, I would encourage you to file a new bug report with this data, and simply reference this bug report in your bug description.

[tatsuno (carlos-troncoso)]

@Bryce Thanks very much, I will do as you suggest.

[Julien Fouquet (julien-fouquet)]

I manage to have the proprietary drivers work with the release candidate of 10.04 by using the recover section of the install cd, using a console on sda1 (my root partition), downloading the drivers (195, not 185 anymore) from the NVIDIA server, uncompressing ( chmod +x ./NVIDIA-drivers.run ) then uncompressing with ./NVIDIA-drivers.run -x and eventually cd NVI(tab) and ./NVIDIA(tab) .

It would work this way with the RC. It does no more with the final version. A screen pops up reporting graphics are in degraded mode and offering options.

Just in case it helps. I'm now looking for a way to have this work with the final release...

[papukaija (papukaija)]

@h1z: We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[h1z (h1z)]

@papukaija
How me send requested information, if i can't switch to virtual console? I can send requested information from work system. Need this?

If i use customize kernel options(nouveau.modeset=0) then bug lost!

[h1z (h1z)]

I'm write from Ubuntu 10.10 Alpha 1 and this bug fixed.

[tatsuno (carlos-troncoso)]

You mean nouveau is working in 10.10 for G102M? I wonder if we can upgrade the xserver-xorg-video-nouveau package to solve the problem in 10.04.

[h1z (h1z)]

@tatsuno yes, nouveau is working in 10.10.

>I wonder if we can upgrade the xserver-xorg-video-nouveau package to solve the problem in 10.04.
may be

[Chris Halse Rogers (raof)]

Marking as fix released, as it's reported to be fixed in Maverick.

It may well be worth fixing in Lucid, though. If we could get some logs from Lucid it would be easier to identify what commits in Maverick have fixed it, then we can work out if they're feasible to backport to Lucid.

[Julien Fouquet (julien-fouquet)]

Hi Chris, I've got a laptop with the very same graphics card and I'd be willing to help fix this in Lucid. What can I do to help? Could you give me instructions or redirect me to some page with instructions appropriate in this case?

I would take care of this the coming Sunday.
Cheers.

[papukaija (papukaija)]

@Steven: This bug is fixed in Maverick. Please use that developpement version of Ubuntu or wait to its official stable release (scheduled for 10.10.2010). The fix won't probably come to Lucid.

[yodaanneaux (romain-yoda)]

Thanks everybody!

[Julien Fouquet (julien-fouquet)]

Hi papukaija, it is not fixed in Lucid yet, and Chris asked for logs so as to, I quote :
"to identify what commits in Maverick have fixed it, then we can work out if they're feasible to backport to Lucid."

I just offered my help for that.
Regards.

[papukaija (papukaija)]

@Steven: I have never written that this bug is fixed in Lucid. Please read again comment 35