--- Alan Hourihane <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 19, 2001 at 02:16:15PM -0800, Earl Hood wrote:
> > After my investigation, it appears that the glint driver imposes
> > a maximum pixel clock rate of 110, regardless of the specified
> > display depth. The only way I could get the glint driver to run
> > in 1280x1024 @ 75Hz was to set the DacSpeed configuration direction
> > in my XF86Config file. I faked the 32 depth speed since it appears
> > the driver is always using that as the maximum instead of the
> > 24 depth speed. Hence I have the following in my config:
> >
> No, your confusing depth and bitsperpixel.
Thanks for the clarification.
> DacSpeed is used by specifying the dacspeed at 8bpp, 16bpp, 24bpp and
> 32bpp. If you start the server with -depth 24, then by default you get
> 32bpp. If you start the server with -depth 24 -pixmap24 then you get
> 24bpp.
I added the ServerFlags option:
Option "Pixmap" "24"
The DefaultDepth of the screen is set to 24. When I comment out
the modeline statements, as you mentioned, and comment out the
DacSpeed statement, the display does go into 1280x1024@75Hz.
The problem though is that colored text is wacked out. Example,
when doing an ls in a color xterm, the colored text is "striped".
This striped behavior does not show up when I comment out the
"Pixmap" Option above. But the refresh rate is back to 60Hz which
is unusable for my eyes.
> I've noticed that it usually reprograms the memory clock on the board to
> a slightly higher rate that enables the PM2 board to use 75Hz refresh.
> We don't do that in the glint driver due to the wealth of PM2 boards out
> there. It's possible to add the feature though, but it could damage your
> boards in the longer term - another reason why I haven't done it.
Do you have any communications with the Accelerated X developers?
I had been using AccelX 5.x with the card for 3 years, and the card
had not crapped out. However, once in awhile, the screen would
boot up in permanent "static" mode. This also could happen when
I ran Win95 so I figured it was a problem with the card itself.
Typically a restart would correct things.
> A side question - what BIOS version is your Diamond FireGL 1000 Pro ?
>
> I think the last one was 1.54 which actually did the right thing for the
> memory clock. I'd check that out first.
I've got 1.54. I upgraded the BIOS back in '98 when I initially
got the computer. I checked earlier today to see if there was newer
updates at www.diamondmm.com, but 1.54 appears to be the latest.
So, will I have to live with 1024x768 mode? I got used to 1280x1024,
but I can cope if there is no real fix.
Thanks for your help,
--ewh
=====
Earl Hood,
[EMAIL PROTECTED]
<http://www.earlhood.com/>
__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com
_______________________________________________
Newbie mailing list
[EMAIL PROTECTED]
*** To unsubscribe , or change message options, see:
http://XFree86.Org/mailman/listinfo/newbie
