NVIDIA SLI System nForce 780i, 2xGF8800, system reports DRI 'Yes', but desktop effects disabled

Bug #474864 reported by MBeale
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xorg

Xlib: extension "RANDR" missing on display ":0.0".

ProblemType: Bug
Architecture: amd64
CheckboxCommand: resolution_test
CheckboxDescription:
 This display is using the following resolution:

 $output

 Is this acceptable for your display?
CheckboxTest: resolution
Date: Thu Nov 5 06:53:06 2009
DistroRelease: Ubuntu 9.10
Lsusb:
 Bus 001 Device 004: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 046d:c525 Logitech, Inc.
 Bus 002 Device 002: ID 045e:008c Microsoft Corp. Wireless Intellimouse Explorer 2.0
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTeK Computer INC. P5N-T DELUXE
NonfreeKernelModules: nvidia
Package: xorg 1:7.4+3ubuntu7
ProcCmdLine: root=UUID=87044255-9748-4f64-b6e7-d017b6b8b123 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_AU.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: xorg
Tags: checkbox-bug
Uname: Linux 2.6.31-14-generic x86_64
Xrandr:
 Error: command ['xrandr', '--verbose'] failed with exit code 1: Xlib: extension "RANDR" missing on display ":0.0".
 RandR extension missing
dmi.bios.date: 12/19/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N-T DELUXE ACPI BIOS Revision 0502
dmi.board.name: P5N-T DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-TDELUXEACPIBIOSRevision0502:bd12/19/2007:svnASUSTeKComputerINC.:pnP5N-TDELUXE:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-TDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5N-T DELUXE
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK Computer INC.
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-14-generic

Revision history for this message
MBeale (malcolm-beale-yahoo) wrote :
Revision history for this message
Bryce Harrington (bryce) wrote :

Thank you for seeking to improve Ubuntu. It seems you have filed a bug
against X using the new System Testing utility. Unfortunately, this tool
is filing bugs without collecting sufficient information to properly
diagnose the issues. I wish we could reply to every report to guide you
to gather the correct information, but it happens that so many people
are using this testing feature to file bug reports that we simply cannot
keep up with the influx. I'm replying in bulk so I can get everyone
pointed into a direction most likely to result in getting you a useful
workaround and us a complete bug report that can be solved.

Most of these problems describe issues that have documented
troubleshooting procedures, so perhaps the most helpful thing I can
do is point you to them:

  http://wiki.ubuntu.com/X/Troubleshooting

These guides explain why things break the way they do, and in some cases
provide workarounds.

I would ask that you first go through the appropriate guide for your
problem, particularly if you are having problems with resolution,
crashes, fonts, or blank screen issues, and then file a bug report using
the following command:

   ubuntu-bug xorg

This collects more detailed information than the System Testing tool
does. Please also write a detailed explanation, indicating when you
first discovered the problem, analysis steps you've done, workarounds
that work, and so on.

Or, if you suspect the problem has something to do with the way the test
script itself is working (such as if Ubuntu worked fine until you ran
the script), then file the bug against the test suite:

   ubuntu-bug checkbox

Thanks again, and good luck!

Changed in xorg (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.