Bug 28140 - console and X display do not work with NVIDIA Quadro NVS 295
Summary: console and X display do not work with NVIDIA Quadro NVS 295
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium blocker
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-17 01:02 UTC by Vincent Lefevre
Modified: 2010-07-21 15:31 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
kernel logs (compressed with bzip2) (15.28 KB, application/x-bzip2)
2010-05-17 01:02 UTC, Vincent Lefevre 		no flags Details
View All

Description Vincent Lefevre 2010-05-17 01:02:33 UTC 
Created attachment 35703 [details]
kernel logs (compressed with bzip2)

Using a HP Z800 with NVIDIA Quadro NVS 295, under GNU/Linux (Debian/unstable with linux-image-2.6.32-5-amd64, the first kernel image using the nouveau driver):

When I boot, the screen goes black after a few lines and the monitor goes to sleep. Some time after (once X has started, I assume) the monitor wakes up, but with a corrupt image.

The machine is still accessible by SSH. Otherwise one cannot do anything except switching it off.

I've attached the beginning of the logs (compressed). Then I got the same message (thousands of times a second) until I switched off the machine:

  [drm] nouveau 0000:0f:00.0: PFIFO_INTR 0x00000010 - Ch 1

The problem disappears after blacklisting "nouveau" (and rebooting).

Bug also reported on the Debian BTS:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581830
Comment 1 Vincent Lefevre 2010-07-21 05:06:19 UTC 
Any news? FYI, the bug still occurs with an up-to-date Debian/unstable installation. The screen goes black a bit after the message

  waiting for /dev to be fully populated

appears on the screen.
Comment 2 Ben Skeggs 2010-07-21 15:31:50 UTC 
This is fixed in nouveau git.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.