Bug 13184 - nv + NVidia Quadro NVS 140M: blank screen, 100% cpu load
Summary: nv + NVidia Quadro NVS 140M: blank screen, 100% cpu load
Status: RESOLVED DUPLICATE of bug 12637
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nVidia (open) (show other bugs)
Version: 7.3 (2007.09)
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Aaron Plattner
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-11 11:50 UTC by Stefan Ehlen
Modified: 2007-11-12 01:23 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg.conf (2.52 KB, application/octet-stream)
2007-11-11 11:52 UTC, Stefan Ehlen
no flags Details
Log file (41.38 KB, text/x-log)
2007-11-11 11:54 UTC, Stefan Ehlen
no flags Details

Description Stefan Ehlen 2007-11-11 11:50:13 UTC
Hi,

my laptop has a NVidia Quadro NVS 140M graphics chipset with 128MB. All attempts to get the nv-driver running gave the same result:

- blank screen as soon as X is started
- not possible to switch to console
- backlight is not turned of (I still can see the that one pixel error)
- login via ssh is possible, xorg is running with 100% cpu-load and it takes a
  "kill -9" to stop it. The display remains blank till reboot.

This happens with xorg 7.2 / 7.3 and nv 2.1.3 / 2.1.5 on Debian testing/unstable

The xorg.conf is quite simple and works with the vesa and proprietary nvidia drivers. 

Please let me know if there's anything I can do.
Comment 1 Stefan Ehlen 2007-11-11 11:52:09 UTC
Created attachment 12461 [details]
xorg.conf
Comment 2 Stefan Ehlen 2007-11-11 11:54:45 UTC
Created attachment 12462 [details]
Log file

There's a line saying: "(--) PCI:*(1:0:0) nVidia Corporation unknown chipset (0x0429) rev 161, Mem @ ....". Is that a hint?
Comment 3 Aaron Plattner 2007-11-12 01:23:57 UTC
Try 2.1.6.

*** This bug has been marked as a duplicate of bug 12637 ***


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.