Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: STB Velocity 3D and XFree 3.3.2
- To: tlug@example.com, sstone@example.com
- Subject: Re: tlug: STB Velocity 3D and XFree 3.3.2
- From: "Manuel M. T. Chakravarty" <chak@example.com>
- Date: Fri, 24 Jul 1998 10:27:07 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: Text/Plain; charset=us-ascii
- In-Reply-To: Your message of "Thu, 23 Jul 1998 17:48:11 +0900 (JST)"<Pine.LNX.3.96LJ1.1b7.980723174701.6832E-100000@example.com>
- References: <Pine.LNX.3.96LJ1.1b7.980723174701.6832E-100000@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
From: Scott Stone <sstone@example.com> > On Thu, 23 Jul 1998, Manuel M. T. Chakravarty wrote: > > > Some more experiments resulted in the following: The card > > works *exactly once* after booting. When I leave X and > > start it again, the machine freezes. Actually, all video > > modes (including the second above) seem to work (I tried > > about five), but all of them work only when the card is > > `freshly' booted. I guess that it is the probing of the > > clock that freezes the machine when it is done after I have > > started X already once. In particular, if, after starting > > X, I run `turboxcfg' to set up video modes, the machine > > already freezes after the dialog where I have to select the > > color depth -- `turboxcfg' seems to probe for the possible > > video modes, which I guess requires probing the clock. > > why would you run turboxcfg when X is already running? You're supposed to > run turboxcfg BEFORE starting X... Of course I left X again before starting `turboxcfg' a second time :-) > > Apart from this problem, everything seems to work fine, even > > the acceleration (though I have a slight distortion on the top > > 1cm of the screen image, which I cannot remember to have > > seen before installing the new server). > > > > > When you run at 1280, which dot clock does it use? > > > > I append the output of the SVGA server below (but for > > 1152x900 -- otherwise, I have to boot again, and somebody else > > is currently also logged in). It says > > > > (--) SVGA: Maximum allowed dot-clock: 135.000 MHz > > > > I guess, the server probed for this value? Can I just tell > > it the value, so that it doesn't probe? (I didn't find any > > such option in the manual -- but maybe I just didn't > > recognize it.) > > > > Any idea why the card behaves differently the second time I > > start X? > > So, is it still only with 1152x900, or all resolutions? All color depth/resolution combinations that I tested (maybe five) are fine -- given the machine is freshly booted. > What happens if > you run Win95/98 in 1152x900? This machine is M$ clean ;-) But I had a Slackware installation with AcceleratedX running on the same hardware for about a year without these problems -- so, it is not simply the card. But I'd prefer to do without AcceleratedX, as I had other problems with it. Manuel -------------------------------------------------------------- Next Meeting: 8 August, Tokyo Station Yaesu central gate 12:30 featuring Linux on multiple platforms: i386, Sparc, PA-Risc, Amiga, SGI, Alpha, PalmPilot, ... Next Nomikai: September, 19:30 Tengu TokyoEkiMae 03-3275-3691 -------------------------------------------------------------- Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp
- References:
- Re: tlug: STB Velocity 3D and XFree 3.3.2
- From: Scott Stone <sstone@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: custom keyboard
- Next by Date: Re: tlug: custom keyboard
- Prev by thread: Re: tlug: STB Velocity 3D and XFree 3.3.2
- Next by thread: tlug: mkext2fs error...?
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links