public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nix N. Nix" <nix@go-nix.ca>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: linux-kernel@vger.kernel.org
Subject: Re: hangs using opengl
Date: 17 Jan 2002 16:45:00 -0500	[thread overview]
Message-ID: <1011303957.15470.7.camel@tux> (raw)
In-Reply-To: <200201171926.g0HJQUE19410@Port.imtp.ilyichevsk.odessa.ua>
In-Reply-To: <3C4712DB.6090201@kabelfoon.nl> <1011292729.12873.27.camel@tux> <1011294257.13517.1.camel@tux>  <200201171926.g0HJQUE19410@Port.imtp.ilyichevsk.odessa.ua>

On Thu, 2002-01-17 at 18:26, Denis Vlasenko wrote:
> 
> Athlon bug stomper is already in mainline. If latest kernel does not work for 
> you, check that register (man lspci) and 0x95 also. Try to disable them (man 
> setpci). Report back - we may need to further improve stomper.

Uh-oh !  agpgart says I have an VIA Apollo Pro KT266 chipset, but
NVdriver says I have a VIA Apollo KT133 chipset.  Is that OK ?  Could
that be causing my problems ?



Thanks for all the help & info.

> --
> vda
> 



  parent reply	other threads:[~2002-01-17 21:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 18:07 hangs using opengl Nick Martens
     [not found] ` <1011292729.12873.27.camel@tux>
2002-01-17 19:03   ` Nix N. Nix
     [not found]     ` <200201171926.g0HJQUE19410@Port.imtp.ilyichevsk.odessa.ua>
2002-01-17 21:38       ` Nix N. Nix
2002-01-19 19:13         ` Nick Martens
2002-01-17 21:45       ` Nix N. Nix [this message]
     [not found] <20020117191450.932B64ADB4@drie.kotnet.org>
2002-01-17 19:38 ` Nick Martens
2002-01-17 20:44   ` Reid Hekman
     [not found]     ` <3C473A57.3000206@lexus.com>
     [not found]       ` <1011302680.639.12.camel@zeus>
     [not found]         ` <3C47429B.7060306@lexus.com>
2002-01-17 22:04           ` Reid Hekman
2002-01-18  0:06   ` Alan Cox
2002-01-19 19:33     ` Nick Martens

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=1011303957.15470.7.camel@tux \
    --to=nix@go-nix.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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