mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Athanasios Leontaris <aleontar@ucsd.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.2 Kernel Badness with 1.0-5336 NVIDIA driver
Date: Tue, 17 Feb 2004 17:54:14 +0000	[thread overview]
Message-ID: <200402171754.14513.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <200402170808.21530.aleontar@ucsd.edu>

On Tuesday 17 February 2004 16:08, you wrote:
> Hi to all,
>
> Pls cc me as I am not subscribing.
> I know that the kernel is tainted so pls don't flame ;)
> The kernel is 2.6.2 from www.kernel.org and I use AGPGART for AGP (_not_
> NvAGP). Fast Writes and SBA are enabled. FC1 is the distro. The mobo is
> Abit KG7 and the video card an FX5600.
>
> X stopped responding out of the blue, at a KDE 3.2 desktop, and it could
> not be killed either. The following messages were uncovered in
> my /var/log/messages:
[snip]

Please first check to see if /etc/X11/XF86Config or /etc/X11/XF86Config-4 
contains the string:

Option "RenderAccel" "1"

If it does, either remove the line or replace it with:

Option "RenderAccel" "0"

Render acceleration is still not working with the proprietary driver. I'm not 
saying it's definitely this, it just might not be related to the messages in 
syslog.

I occasionally see these badness messages in syslog, but my machine never 
locks up. I was under the impression that these were only warnings.

-- 
Cheers,
Alistair.

personal:   alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student:    CS/AI Undergraduate
contact:    7/10 Darroch Court,
            University of Edinburgh.

  parent reply	other threads:[~2004-02-17 17:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17 16:08 Athanasios Leontaris
2004-02-17 16:56 ` Matt H.
2004-02-17 17:54 ` Alistair John Strachan [this message]
2004-02-17 17:57   ` Athanasios Leontaris
2004-02-17 20:31     ` Thomas Weich
2004-02-18  0:40       ` Athanasios Leontaris

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=200402171754.14513.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=aleontar@ucsd.edu \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®