Baslinux mailing list

[sindi keesan <keesan AT sdf.lonestar.org>]

On Fri, 13 May 2005, David Moberg wrote:

> ----- Original Message -----
> From: "sindi keesan" <keesan AT sdf.lonestar.org>
>
> > Progress!  (Using the modeline from the websites, which does not
> > tell me Dotclock expected, and the Clocks line is back).
> >
> > error opening security policy file
> > /usr/X11R6/lib/X11/xserver/SecurityPolicy  (all on one line)
> >
> > I got this one time earlier with the vga or maybe the mono server.
> > I don't even have /usr/X11R6/lib/X11.  Perhaps this file needs to
> > be added from somewhere (in Steven's little no-xvesa.tgz package).
> > I can't figure this out from a websearch - what does security have
> > to do with X_SVGA? The server worked with three other video chips.
>
> I found a suggestion online to touch the file:
>
> mkdir -p /usr/X11R6/lib/X11/xserver/SecurityPolicy
> touch /usr/X11R6/lib/X11/xserver/SecurityPolicy
>
> Are you sure that this is the only problem?


Apparently not.  I found /bin/touch and did as you suggested above and for 
a second after typing startx I saw the X screen and then it exited.

Mode "640x480":  mode clock = 28.320, clock used = 28.320
Virtual resolution set to 640x480
        (I had removed the 320 modelines which is why that did not work)
SpeedUp code selection modified because virtualX != 1024
PVGA1:  SpeedUps selected (Flags=0xf)

Did this last line somehow kill X?  Do I  need SpeedUp?  What is virtualX?

I next tried uncommenting, before the Clocks line,

# VideoRam 1024
Then I changed to 512 since something online said something about
only 512K sometimes being available (something to do with switching to 
CRT?)


> > > 1) XFree86 won't allow modes outside the HorizSync, VertSync, and
> > > resolution settings which you have chosen.
> >
> > Why did setting a range work, when setting the exact frequencies
> > did not? I notice you said 67.4 and someone else 67.36.
>
> The frequency which I specified was likely not exactly correct. Ranges
> work OK, and if there are no other ModeLines besides the one which you
> are using, there is no problem.
>
> > > 2) Your graphics card may not allow bad modes (which is the case
> > > here)
> > > 3) As a last resort, a good monitor will not allow incorrect
> > > modes.
> > Can an LCD monitor be damaged by the wrong modes?
>
> Probably. Wrong modes will also make a very ugly display.
>
> > > > Does Vertical Refresh mean the number of lines put on the screen in
> > > > one scan from top to bottom?
> > >
> > > It means the number of times the electron beam of a CRT goes from top
> > > to bottom (round-trip) each second.
> >
> > 67 times per second. This monitor or chip is also 60Hz - what is
> > that measuring?
>
> Vsync. LCDs usually accept 60Hz as input, but they have no electron beam
> scanning up and down, so this doesn't really affect them.
>
> David
>
> --
> _______________________________________________
> NEW! Lycos Dating Search. The only place to search multiple dating sites at 
> once.
> http://datingsearch.lycos.com
>
> _______________________________________________
> BasLinux mailing list
> BasLinux AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/baslinux

keesan AT sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org