Okay, I know it is bad form to respond to one's own posts, however, I came across some new information. I rolled back to 280.13.really.275.28-1, and although the performance is back to being substandard, I have my X back.
I started thinking about this, and want to pose a question. This machine was last rebuilt in 2006 or 2007, and back then, amd64 wasn't "there" yet. So I built it i386 (its a c2d machine, so either would work). Sometime about 2 years ago, the system clock started running *really* fast (2-3 hours gained per day), even with ntp running. I posted to the list and someone suggested running an amd64 kernel. So I have this frankenbox that is on my todo list to rebuild with amd64 userspace as well as the kernel. This is the only thing I can figure that might be causing my problems on the workstation. I have never had problems with the nvidia configuration in previous versions and kernels, but is there something unique or new to 290.03 that might be causing the problem? Thanks, --b On Thu, Oct 27, 2011 at 2:30 PM, Brad Alexander <stor...@gmail.com> wrote: > Hey, > > I have been watching for the new nvidia drivers that fix the regression in > the trapezoid renderers with some anticipation. I found that 290.03-1 was > released to experimental, so I downloaded and installed them. > > I installed yesterday on my laptop, the Dell Latitude E6500 with the C2D > P9600 and the Quadro NVS 160M. It is running wheezy/amd64. After I upgraded > the nvnidia packages already installed and doing an upgrade to reinstall the > xserver-xorg packges I had downgraded, I rebooted, and everything came up > roses. > > Last night, I tried the same thing on my workstation, a C2D E4500 with a > GeForce 8600GT running sid/1386 (rebuild is pending). As before, I installed > the packages currently installed on the machine, and did an upgrade, but > this time after rebooting, I never made it out of the console. X refused to > start with the following message: > > Fatal server error: > no screens found > > ... > > Server terminated with error (1). Closing log file. > > No other changes were made (e.g. to the xorg.conf). I looked at > /var/log/Xorg.0.log, and saw the following errors: > > [ 37248.883] (**) NVIDIA(0): Option "NvAGP" "1" > [ 37248.883] (**) NVIDIA(0): Option "TwinView" "0" > [ 37248.883] (**) NVIDIA(0): Option "MetaModes" "1680x1050 +0+0; 1440x900 > +0+0; 1280x800 +0+0" > [ 37248.883] (**) NVIDIA(0): Option "AllowGLXWithComposite" "On" > [ 37248.883] (**) NVIDIA(0): Option "TripleBuffer" "true" > [ 37248.883] (**) NVIDIA(0): Use of NVIDIA internal AGP requested > [ 37248.883] (**) NVIDIA(0): Enabling 2D acceleration > [ 37250.012] (EE) NVIDIA(0): Failed to get supported display device(s) > [ 37250.012] (EE) NVIDIA(0): Failed to get supported display device(s) > [ 37250.013] (EE) NVIDIA(0): Failed to get supported display device(s) > [ 37250.013] (EE) NVIDIA(0): Failed to get supported display device(s) > [ 37250.013] (EE) NVIDIA(0): Failed to get supported display device(s) > [ 37250.014] (WW) NVIDIA(GPU-0): Failed to query OR info 0x20 > [ 37250.017] (II) NVIDIA(0): NVIDIA GPU GeForce 8600 GT (G84) at PCI:1:0:0 > (GPU-0) > [ 37250.017] (--) NVIDIA(0): Memory: 524288 kBytes > [ 37250.017] (--) NVIDIA(0): VideoBIOS: 60.84.41.00.00 > [ 37250.017] (II) NVIDIA(0): Detected PCI Express Link width: 16X > [ 37250.017] (--) NVIDIA(0): Interlaced video modes are supported on this > GPU > [ 37250.017] (--) NVIDIA(0): Connected display device(s) on GeForce 8600 GT > at PCI:1:0:0 > [ 37250.017] (--) NVIDIA(0): none > [ 37250.020] (EE) NVIDIA(0): No display devices found for this X screen. > [ 37250.293] (II) UnloadModule: "nvidia" > [ 37250.293] (II) Unloading nvidia > [ 37250.293] (II) UnloadModule: "wfb" > [ 37250.293] (II) Unloading wfb > [ 37250.293] (II) UnloadModule: "fb" > [ 37250.293] (II) Unloading fb > [ 37250.293] (EE) Screen(s) found, but none have a usable configuration. > > I've gone through the rest of the file, and this is the only area that > seems out of the ordinary...Though one thing I do see is that it detected > PCI Express Link Width of 16x. The card is an AGP interface. > > I thought the card may have been EOL'ed with this set of drivers, but the > docs said the GeForce 8600GT is, in fact, supported according to the docs in > /usr/share/doc... > > After all the issues with rolling back to xsesrver-xorg 1.10 breaking > upgrades, I'd really rather not go through that again. I'd like to get up > and running on the 290.03 drivers, especially since it works on the laptop. > > Does anyone see anything that might be a cause of the problem? > > Thanks, > --b >
