On Sunday 07 December 2003 09:16 pm, Jim wrote: > On Sunday 07 December 2003 01:55 pm, Ernie Schroder wrote: > > On Sunday 07 December 2003 12:41 pm, collins wrote: > > > On Sun, 2003-12-07 at 07:31, Ernie Schroder wrote: > > > > On Sunday 07 December 2003 01:38 am, Ian Truelsen wrote: > > > > > On Sun, 7 Dec 2003 02:06:08 -0500 > > > > > > > > > > Ernie Schroder <[EMAIL PROTECTED]> wrote: > > > > > > You're not using a KT133 based motherboard, are you? > > > > > > Using any AGP at all, locked up my kt133 box every time I > > > > > > tried to use a GLX app. Nforce2 based boards ROCK with > > > > > > Nvidia graphics cards, but VIA board are problematic. > > > > > > > > > > I have a kt133 mobo with an nVidia card. Everything seems > > > > > to be working fine, though I get occasional problems with X > > > > > not being able to open the display to launch apps. This > > > > > forces me to restart X, but nothing that locks up the > > > > > computer proper. > > > > > > > > Great. I'm glad someone can get the boards to work. I had 3 > > > > slot1 (athlon/slot) boards here 2 of which were KT133 > > > > chipsets. I has solid lockups on both of the VIA boards but > > > > the 3rd board ran GLX fine. I believe that it was an AMD > > > > chipset. That board lost the primary IDE or else I might > > > > still be using it. At one point I was so ticked off at VIA > > > > that I was consideringchanging my signature to the below: > > > > > > I've been curious about this problem for some time. Is the > > > problem really the KT133 chipset, or just that NVIDIA and > > > others are too lazy to produce code that will work with the > > > KT133 chipset? > > > > Good question.... I did a lot of searching for answers and never > > was able to assign blame. All I know is that I was able to get > > AGP and GLX to work on the AMD chipset board (if I only ran 2 > > drives hdc and hdd). > > My reason for going to the nforce2 board was the fact that my > > research showed that Nvidia had done some extra work to insure > > optimum performance with their chipset/video adapter combination. > > My guess would be that nvidia saw little need to bend code for > > the KT133 chipset as it was mostly obsolete when they wrote Linux > > drivers for their cards. This is probably not the best situation > > for Linux users using older equipment, but the drivers are free > > (as in free beer). > > I recall something about a weak signal (can't recall if it was > nvidia or the mobo) and that there was an interim fix with changing > some bios settings, but i believe that was all worked out in the > drivers. That was a couple years ago. Another fix was to disable > agp 4x in the bios. That was in my pre linux days, and M$ disabled > agp 4x support by default in the drivers.
I went through all that without help If I remember correctly, I could run glx apps for up to 10 minutes or so by setting AGP to 1x sideband addressing was death though.This WAS 8 or 9 months ago so the nvidia drivers might work OK with KT133 chipsets, but I can tell you that my framerate is 20 or 25 times what it was with the same video card and my nforce2 based mobo. -- Regards, Ernie 100% Microsoft and Intel free -- [EMAIL PROTECTED] mailing list
