All of lore.kernel.org
 help / color / mirror / Atom feed
From: Flo <debianflo-RbZlAiThDcE@public.gmane.org>
To: Pekka Paalanen <pq-X3B1VOXEql0@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: GeForce 5500 crashes driver
Date: Thu, 26 May 2011 07:47:47 +0200	[thread overview]
Message-ID: <4DDDE983.3040000@gmx.at> (raw)
In-Reply-To: <20110525181758.11bb1663-DA5HUFbJnAM@public.gmane.org>

Thank you for your reply

>> .) Is it reasonable to track down the error? (Maybe it would make sense
>> for driver improvement?). What should I start with?
> 
> We have bug reporting guidelines here:
> http://nouveau.freedesktop.org/wiki/Bugs
> 
> Complete kernel and X logs are required to get any insight to
> the problem. You also need to specify what versions of all
> the software components you use.
> 

Since I am using the Debian packages, I have to file the bug at the
Debian maintainer.

> Going through the TroubleShooting page is also worth it to
> eliminate the usual user errors.
> 

I will do this before.

>> .) How are the chances that the problem will go away if I buy a similar
>> (maybe also GeForce 5500) video card from another manufacturer.
> 
> Without further information, I'd say very unlikely.
> 

This would have been the easy way ...

Regards,
Flo

  parent reply	other threads:[~2011-05-26  5:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25  8:11 GeForce 5500 crashes driver Flo
     [not found] ` <4DDCB9BB.7090304-RbZlAiThDcE@public.gmane.org>
2011-05-25 15:17   ` Pekka Paalanen
     [not found]     ` <20110525181758.11bb1663-DA5HUFbJnAM@public.gmane.org>
2011-05-26  5:47       ` Flo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-05-25  8:08 Flo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DDDE983.3040000@gmx.at \
    --to=debianflo-rbzlaithdce@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=pq-X3B1VOXEql0@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.