And thanks Volker for an excellent example of how to report a solution
to a problem in such a way so that google will index it in order that
anybody that has the same problem and asks google a half-sensible
question will get your answer and save themselves the troubles you've
had both finding a so
Thanks Nick for a spot-on analysis of the current state of affairs.
Yes I could hook up some kit to the signal lines and just measure the
frequencies, but the tradeoff between that effort and needing to know
that answer currently speaks against it. Besides it doesn't solve the
problem for "next ti
On Tue, 27 Jun 2006 11:20:33 +1200
Ross Drummond wrote:
> On Tue, 27 Jun 2006 00:01, Christopher Sawtell wrote:
> > On Monday 26 June 2006 22:29, Nick Rout wrote:
> > > On Mon, 26 Jun 2006 21:17:12 +1200
> > >
> > > Steve Holdoway <[EMAIL PROTECTED]> wrote:
> > > > On Mon, 26 Jun 2006 17:05:16 +1
On Tue, 27 Jun 2006 00:01, Christopher Sawtell wrote:
> On Monday 26 June 2006 22:29, Nick Rout wrote:
> > On Mon, 26 Jun 2006 21:17:12 +1200
> >
> > Steve Holdoway <[EMAIL PROTECTED]> wrote:
> > > On Mon, 26 Jun 2006 17:05:16 +1200
> > >
> > > Christopher Sawtell <[EMAIL PROTECTED]> wrote:
> Ah ye
On Monday 26 June 2006 22:29, Nick Rout wrote:
> On Mon, 26 Jun 2006 21:17:12 +1200
>
> Steve Holdoway <[EMAIL PROTECTED]> wrote:
> > On Mon, 26 Jun 2006 17:05:16 +1200
> >
> > Christopher Sawtell <[EMAIL PROTECTED]> wrote:
> > > On Monday 26 June 2006 15:21, Steve Holdoway wrote:
> > > > OSD???
>
On Mon, 26 Jun 2006 21:17:12 +1200
Steve Holdoway <[EMAIL PROTECTED]> wrote:
> On Mon, 26 Jun 2006 17:05:16 +1200
> Christopher Sawtell <[EMAIL PROTECTED]> wrote:
>
> > On Monday 26 June 2006 15:21, Steve Holdoway wrote:
> > > OSD???
> > On Screen Display.
> >
> > --
> > CS
> It was a suggestio
On Mon, 26 Jun 2006 17:05:16 +1200
Christopher Sawtell <[EMAIL PROTECTED]> wrote:
> On Monday 26 June 2006 15:21, Steve Holdoway wrote:
> > OSD???
> On Screen Display.
>
> --
> CS
It was a suggestion (:
On Monday 26 June 2006 15:21, Steve Holdoway wrote:
> OSD???
On Screen Display.
--
CS
> "what is the monitor running with right now".
I'm not running X with a monitor you insensitive clod.
Actually, I am running X in a VNC session. It isn't connected to a monitor
at all. It is only visible when I run a VNC client on another machine.
I suppose that really means that X is not re
On Mon, 26 Jun 2006, Volker Kuhlmann wrote:
the question was "what is the monitor running with
right now".
su
cd /var/log
xwininfo -root
xwininfo -root
xwininfo: Window id: 0x44 (the root window) (has no name)
Absolute upper-left X: 0
Absolute upper-left Y: 0
Relative upper-left X:
On Mon, 26 Jun 2006 15:15:23 +1200
Volker Kuhlmann <[EMAIL PROTECTED]> wrote:
> > The hardware detection utility on the System Rescue CD should be able to
> > deliver the info.
>
> You misunderstood as well. The question was not "what is this monitor
> capable of" (you can only find this out aut
> The hardware detection utility on the System Rescue CD should be able to
> deliver the info.
You misunderstood as well. The question was not "what is this monitor
capable of" (you can only find this out automatically if the monitor
supports DDC(sp)), the question was "what is the monitor runnin
On Monday 26 June 2006 13:47, John Carter wrote:
> On Fri, 16 Jun 2006, Volker Kuhlmann wrote:
> > How can I determine the actually running monitor frequencies? The
> > monitor(s) doesn't show it in some menu place.
>
> I'm a bit late on this one, but isn't it fairly simply calculable from
> your r
> I'm a bit late on this one, but isn't it fairly simply calculable from
> your resolution & refresh rate.
>
> hsync = refresh rate / number of lines
>
> vsync == refresh rate
>
> dot clock ~ ((N cols +some smallish overshoot) * M rows + smallish sweep
> back time)
> * refresh rate
On Fri, 16 Jun 2006, Volker Kuhlmann wrote:
How can I determine the actually running monitor frequencies? The
monitor(s) doesn't show it in some menu place.
I'm a bit late on this one, but isn't it fairly simply calculable from
your resolution & refresh rate.
hsync = refresh rate / number of
xvidtune works, but displays the message 'Video modes are not settable on this
chip' on my FX 5200 nvidia atx card (FC4), but does work as normal on the
server, which has an onboard, much newer nvidia controller (ubuntu) described
as a C51 pci-x.
Steve
On Sat, 17 Jun 2006 14:02:49 +1200
Nick R
On Fri, 16 Jun 2006 16:10:18 +1200
Volker Kuhlmann <[EMAIL PROTECTED]> wrote:
> > Is it in /var/log/Xorg.0.log?
>
> Good thinking. Shows quite a few things (depending on the driver used),
> but not what I'm looking for.
>
> Googling shows that this is more widespread, but I didn't see anyone
> m
> Is it in /var/log/Xorg.0.log?
Good thinking. Shows quite a few things (depending on the driver used),
but not what I'm looking for.
Googling shows that this is more widespread, but I didn't see anyone
mentioning the actual cause and how to fix it. Looks to me like it's
caused by something outsi
> cvs -d :pserver:[EMAIL PROTECTED]:/cvs/xorg co xc/programs/xvidtune
xmkmf -a
make
./xvidtune
Please install the program before using
Exit 3
make -k install
install -c -m 0444 Xvidtune.ad /usr/X11R6/lib/X11/app-defaults/Xvidtune
install: cannot remove `/usr/X11R6/lib/X11/app-defaults/Xvidtune':
Is it in /var/log/Xorg.0.log?
or does that only show the detected range?
PS
is xvidtune another casualty of SuSE's beta policy?
/me ducks for cover
On Fri, 16 Jun 2006 14:31:42 +1200
Volker Kuhlmann wrote:
> > I use the vendors website.
>
> Which would of course tell me what my monitor is c
On Fri, 16 Jun 2006 14:32:52 +1200
Steve Holdoway <[EMAIL PROTECTED]> wrote:
> Sorry... bit of word blindness on my part.
>
> On Fri, 16 Jun 2006 14:31:42 +1200
> Volker Kuhlmann <[EMAIL PROTECTED]> wrote:
>
> > > I use the vendors website.
> >
> > Which would of course tell me what my monitor
Sorry... bit of word blindness on my part.
On Fri, 16 Jun 2006 14:31:42 +1200
Volker Kuhlmann <[EMAIL PROTECTED]> wrote:
> > I use the vendors website.
>
> Which would of course tell me what my monitor is currently running at...
>
> The manual tells me what the allowable frequency range is. Not
> I use the vendors website.
Which would of course tell me what my monitor is currently running at...
The manual tells me what the allowable frequency range is. Not the same
as what it is actually running at.
Volker
--
Volker Kuhlmann is list0570 with the domain in header
http:
I use the vendors website.
On Fri, 16 Jun 2006 14:17:24 +1200
Volker Kuhlmann <[EMAIL PROTECTED]> wrote:
> How can I determine the actually running monitor frequencies? The
> monitor(s) doesn't show it in some menu place.
>
> xvidtune reliably showed this in the past, but it stopped working and
How can I determine the actually running monitor frequencies? The
monitor(s) doesn't show it in some menu place.
xvidtune reliably showed this in the past, but it stopped working and
now only gives "Please install the program before using". Neither strace
nor google tell me anything to get it work
25 matches
Mail list logo
