NVidia driver failure on new system
Andrej Marjan
andrej-igvx78u1SeH3fQ9qLvQP4Q at public.gmane.org
Thu Jun 2 15:59:01 UTC 2011
That's your personal user account's error log. If you're having system
problems, they're more likely to show up in the X server log at
/var/log/Xorg.0.log or maybe in the syslog. What can you find there?
On Thu, Jun 2, 2011 at 8:04 AM, Thomas Milne
<thomas.bruce.milne-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org>wrote:
> My 'new' system has a GForce GT520. I installed Debian Squeeze, installed
> nvidia-dkms, and upgraded to unstable. As soon as I enable the nvidia
> driver, though, the system become totally unresponsive. All I get is a
> rapidly flashing cursor and a flashing numlock. If I reboot I can get into
> recovery mode and switch back to the generic driver, but that only gives me
> 800x600.
>
> I found this in xsession-errors:
>
> /etc/gdm3/Xsession: Beginning session setup...
> GNOME_KEYRING_CONTROL=/tmp/keyring-pmldst
> GNOME_KEYRING_CONTROL=/tmp/keyring-pmldst
> GNOME_KEYRING_CONTROL=/tmp/keyring-pmldst
> SSH_AUTH_SOCK=/tmp/keyring-pmldst/ssh
> librdf warning - Model does not support contexts
> librdf warning - Model does not support contexts
> librdf warning - Model does not support contexts
> Window manager warning: Failed to read saved session file
> /home/joehill/.config/metacity/sessions/
> 107e382d5a521abc3113070141156434900000021170023.ms: Failed t$
> ** Message: applet now removed from the notification area
> ** Message: applet now embedded in the notification area
> Initializing nautilus-gdu extension
>
> (gnome-power-manager:2179): GLib-GObject-CRITICAL **: g_object_unref:
> assertion `G_IS_OBJECT (object)' failed
> ** Message: applet now removed from the notification area
> Shutting down nautilus-gdu extension
> ** Message: Got disconnected from the session message bus; retrying to
> reconnect every 10 seconds
> gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable)
> on X server :0.
> ** Message: <info> disconnected by the session bus.
>
> polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource
> temporarily unavailable) on X server :0.
> kerneloops-applet: Fatal IO error 11 (Resource temporarily unavailable) on
> X server :0.
> update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X
> server :0.
> gdu-notification-daemon: Fatal IO error 11 (Resource temporarily
> unavailable) on X server :0.
> gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on
> X server :0.
> nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server
> :0.
> system-config-printer-applet: Fatal IO error 11 (Resource temporarily
> unavailable) on X server :0.
> The application 'gnome-panel' lost its connection to the display :0;
> most likely the X server was shut down or you killed/destroyed
> the application.
>
> but it looks like all that is just to do with missing panel and applets and
> so on.
>
> Where else can I look for clues?
>
> --
> Thomas Milne
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/legacy/attachments/20110602/c01d3317/attachment.html>
More information about the Legacy
mailing list