On Tuesday, August 16, 2011 05:46:26 AM Przemek Klosowski did opine:
> On Tue, Aug 16, 2011 at 12:15 AM, gene heskett <ghesk...@wdtv.com> wrote:
> > On Tuesday, August 16, 2011 12:02:31 AM Przemek Klosowski did opine:
> >> On Mon, Aug 15, 2011 at 6:06 PM, gene heskett <ghesk...@wdtv.com>
wrote:
> >> > On Monday, August 15, 2011 05:15:23 PM Przemek Klosowski did opine:
> >> >> Section "Monitor"
> >> >> Modeline "1360x768" 85.5 1360 1424 1536 1792 768 771 777 795
> >> >> EndSection
> >> >
> >> > Many thanks, I just added that to the top of an extensive list in
> >> > that machines xorg.conf, and I will go reboot it now for effects.
> >> >
> >> > I tried variations of 1360x768 and 1366x768. The log contains a
> >> > long list of available modes, which do not include either of
> >> > those, and are uniformly within a pixel of a 4x3 aspect ratio.
> >> > Does that list of modes come from the card? Or from the vesa
> >> > driver?
> >>
> >> It's possible that your xorg.conf is messing you up---I bet you it's
> >> a remnant of the old setup, and quite possibly not necessary. The
> >> long list of modelines was how I learned to do X11 back in the days
> >> when we had to whittle ones and zeros out of oak timbers but
> >> nowadays, xorg.conf is just few lines long, and the Xorg server
> >> finds out the video hardware, reads the monitor parameters over the
> >> video cable and matches it to the built-in list of VESA standard
> >> modes. It'd be interesting to try with a virgin minimalistic
> >> xorg.conf
> >>
> >> Section "Device"
> >> Identifier "Videocard0"
> >> EndSection
> >>
> >> Section "Screen"
> >> Identifier "Screen0"
> >> Device "Videocard0"
> >> DefaultDepth 24
> >> EndSection
> >>
> >> and maybe it'll figure something out on its own. I don't know if
> >> 1360x768 is on the VESA list so maybe you do need it after all.
> >>
> >> > The log says 136nx768 is not used because there is no mode of that
> >> > name even though I have added it to the "Monitor" section.
> >>
> >> It has to match the "Monitor" section your Screen section is using;
> >> there could be multiple Monitor sections
> >> ("Monitor1","myOldCRT","LCDmonitor2", etc). Say something like
> >>
> >> Section "Screen"
> >> Identifier "Screen0"
> >> Device "Videocard0"
> >> Monitor "MyMonitor"
> >> ...
> >> Section "Monitor"
> >> Identifier "MyMonitor"
> >> Modeline .....
> >> ...
> >>
> >> > If its the card, I wonder if it is flashable to add that mode?
> >>
> >> Nope, I doubt it, every VGA card is capable of any resolution from
> >> like 320x320 (?) to 8000x8000 (???) within the memory capabilities
> >> and video clock speed; the limitations come from the monitor and
> >> driver limitations.
> >>
> >> > Or should I shelve the card, an ATI X1650 and replace it with
> >> > something else that knows about 16x9 aspect ratios?
> >>
> >> I will bet you a beer that your card is capable of driving your
> >> monitor resolution.
> >
> > According to Alex D. at xorg, no. If the mode is not available in the
> > vesa bios, and it isn't, every mode available is a 4x3 variant, so no
> > twiddling with modelines will help.
>
> I think there's some sort of misunderstanding. The mode may be absent
> in VESA table, but the video hardware is almost certainly capable of
> producing it. Try the monitor/modeline I mentioned.
>
I did, both for 1360 and 1366 x 768. I remain stuck at 1024x768, a 4x3
mode.
> > The problem is that the vesa specs were carved in nice hard stone back
> > in crt days, so all these widescreen monitors have never worked their
> > way into
>
> Yes, true, it's not in VESA---that's why we're not using VESA but
> writing our own Modeline.
But I am using the vesa driver.
> > the vesa bios, and likely never will. The card of course is capable
> > of the mode, but only when running the fglrx drivers. The last time
> > I tried that,
>
> Nope, any video card made after 2000 or so can do this mode. You just
> need to program the clock and shift registers to cycle at 13?? and 7??
> basic video clocks---that's what the modeline tells teh server to do.
>
> > I couldn't nuke it fast enough, the backplot was running 3-5 seconds
> > behind the machine and I had to slow the base period to about a 3rd
> > of what its doing now to stop the stalls. Even then the motors were
> > making very rough tones.
>
> OK, performance might be an issue, but it's not related to the
> resolution!!
Performance of rtai, with the proprietary driver blobs, might be possible
with servo systems, but I am running steppers, which need a nice steady
heartbeat. Only vesa can give that.
Cheers, gene
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If swimming is so good for your figure, how come whales look the
way they do?
------------------------------------------------------------------------------
uberSVN's rich system and user administration capabilities and model
configuration take the hassle out of deploying and managing Subversion and
the tools developers use with it. Learn more about uberSVN and get a free
download at: http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
