xorg Digest, Vol 3, Issue 53
Lestat V
dreameration at gmail.com
Sat Oct 22 08:49:00 PDT 2005
Hi, i have a question for someone's help. When I start X server or
switch between X and console, I always get a warning that reads :
(1024*768, SynMaster 510N ) mode clock 98MHz exceeds DDC 80MHz, or
(1280*1024, SynMaster 510N) mode clock 108MHz exceed DDC 80MHz. Need I
care about these warnings? Does it warn some problem? Or I just leave
it alone ? Besides I have a samsung Synmaster 510N LCD monitor, and it
never support 1280*1024, but actually supports 1024*768. Thank you!
On 10/22/05, xorg-request at lists.freedesktop.org
<xorg-request at lists.freedesktop.org> wrote:
> Send xorg mailing list submissions to
> xorg at lists.freedesktop.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freedesktop.org/mailman/listinfo/xorg
> or, via email, send a message with subject or body 'help' to
> xorg-request at lists.freedesktop.org
>
> You can reach the person managing the list at
> xorg-owner at lists.freedesktop.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of xorg digest..."
>
>
> Today's Topics:
>
> 1. Mesa 6.4 RC 4 (Brian Paul)
> 2. Unsubscribing from this list not possible! (Carsten Otto)
> 3. Re: Intel 915G with Dell 2005FPW TFT no bigger resolution
> then 1280x1024 (Philip Prindeville)
> 4. Re: Intel 915G with Dell 2005FPW TFT no bigger resolution
> then 1280x1024 (Scott J. Harmon)
> 5. Re: enabling DDC in the face of broken monitors
> (Philip Prindeville)
> 6. Re: Composite and MapNotifies (Keith Packard)
> 7. Re: Composite and MapNotifies (Keith Packard)
> 8. XSetInputFocus (Russell Shaw)
> 9. Re: Unsubscribing from this list not possible! (Henk Poley)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 21 Oct 2005 15:54:03 -0600
> From: Brian Paul <brian.paul at tungstengraphics.com>
> Subject: Mesa 6.4 RC 4
> To: Mesa3d-dev at lists.sourceforge.net, xorg at lists.freedesktop.org
> Message-ID: <4359637B.9070305 at tungstengraphics.com>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
>
> I'm going to hold off on the Mesa 6.4 release until Monday. I want to
> give people a little more time to test things.
>
> A new, 4th release candidate is at http://mesa3d.org/beta/
>
> This includes:
> - Ian's fix for compiling execmem.c
> - My fix for bug #4087
> (https://bugs.freedesktop.org/show_bug.cgi?id=4087)
> - some fragment program bug fixes
>
> -Brian
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 22 Oct 2005 00:40:44 +0200
> From: Carsten Otto <carsten.otto at gmail.com>
> Subject: Unsubscribing from this list not possible!
> To: xorg at lists.freedesktop.org
> Message-ID:
> <13e988610510211540r10a60707u25c79308a6f95a9a at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hello!
>
> I'd like to unsubscribe from this list, but I can't.
>
> I enter my adress (see signature) in field at the very bottom and go
> to the next site by clicking the button. There it says
>
> "Error: Illegal Email Address: carsten.otto at gmail.com"
>
> This is not true, the address is valid in my eyes.
> Pressing the unsubscribe button gives:
>
> "Error: No address given"
>
> Please help.
>
> Thanks,
> --
> Carsten Otto
> carsten.otto at gmail.com
> www.c-otto.de
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 21 Oct 2005 17:02:02 -0600
> From: Philip Prindeville <philipp_subx at redfish-solutions.com>
> Subject: Re: Intel 915G with Dell 2005FPW TFT no bigger resolution
> then 1280x1024
> To: Discuss issues related to the xorg tree
> <xorg at lists.freedesktop.org>
> Message-ID: <4359736A.6010406 at redfish-solutions.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Check your logs to see if it's ignoring the option "noDDC".
>
> -Philip
>
>
> Patrick Steiner wrote:
>
> > i have tried the noDDc Option but i dont work again. perhabs there is
> > another problem.
> >
> > should i try 915resolution or should this
> > (http://www.fairlite.demon.co.uk/intel.html) driver work better?
> > or should the original driver also work?
> >
> > i cant change my videocard because its an dell optiplex sx280 (small
> > version) with onboard video card :-(
> >
> > here is the videopart of my xorg.conf
> >
> >
> > Section "Monitor"
> > Identifier "Monitor0"
> > VendorName "Monitor Vendor"
> > ModelName "Dell 2005FPW (Digital)"
> > HorizSync 30.0 - 83.0
> > VertRefresh 56.0 - 75.0
> > ModeLine "1680x1050 (Dell)" 147.14 1680 1784 1960 2240 1050
> > 1058 1063 1103
> > Option ""noDDC" "on"
> > EndSection
> >
> > Section "Device"
> > Identifier "Videocard0"
> > Driver "i810"
> > VendorName "Videocard vendor"
> > BoardName "Intel 915"
> > EndSection
> >
> > Section "Screen"
> > Identifier "Screen0"
> > Device "Videocard0"
> > Monitor "Monitor0"
> > DefaultDepth 24
> > SubSection "Display"
> > Viewport 0 0
> > Depth 16
> > Modes "800x600" "640x480"
> > EndSubSection
> > SubSection "Display"
> > Viewport 0 0
> > Depth 24
> > Modes "1680x1050" "1600x1200" "1400x1050" "1280x960"
> > "1280x800" "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
> > EndSubSection
> > EndSection
> >
> > - patrick
> >
> >
> > Philip Prindeville wrote:
> >
> >> The EDID reported by this monitor is slightly broken, and I've been
> >> trying to get Dell to fix it, but they have no clue as to what I'm
> >> talking
> >> about, and their "award winning service" (in India) has no way of
> >> talking to anyone on the factory floor or in the design bureau in
> >> Texas or wherever that might be.
> >>
> >> The modeline I use is:
> >>
> >> ModeLine "1680x1050 (Dell)" 147.14 1680 1784 1960 2240 1050 1058
> >> 1063 1103
> >>
> >> (and I have to turn on "noDDC" to get it to work...)
> >>
> >> -Philip
> >>
> >
> > _______________________________________________
> > xorg mailing list
> > xorg at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/xorg
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 21 Oct 2005 18:07:26 -0500
> From: "Scott J. Harmon" <harmon at ksu.edu>
> Subject: Re: Intel 915G with Dell 2005FPW TFT no bigger resolution
> then 1280x1024
> To: Discuss issues related to the xorg tree
> <xorg at lists.freedesktop.org>
> Message-ID: <435974AE.5050906 at ksu.edu>
> Content-Type: text/plain; charset=ISO-8859-1
>
> >> Option ""noDDC" "on"
> What is that extra " doing in there?
>
> Philip Prindeville wrote:
> > Check your logs to see if it's ignoring the option "noDDC".
> >
> > -Philip
> >
> >
> > Patrick Steiner wrote:
> >
> >> i have tried the noDDc Option but i dont work again. perhabs there is
> >> another problem.
> >>
> >> should i try 915resolution or should this
> >> (http://www.fairlite.demon.co.uk/intel.html) driver work better?
> >> or should the original driver also work?
> >>
> >> i cant change my videocard because its an dell optiplex sx280 (small
> >> version) with onboard video card :-(
> >>
> >> here is the videopart of my xorg.conf
> >>
> >>
> >> Section "Monitor"
> >> Identifier "Monitor0"
> >> VendorName "Monitor Vendor"
> >> ModelName "Dell 2005FPW (Digital)"
> >> HorizSync 30.0 - 83.0
> >> VertRefresh 56.0 - 75.0
> >> ModeLine "1680x1050 (Dell)" 147.14 1680 1784 1960 2240 1050
> >> 1058 1063 1103
> >> Option ""noDDC" "on"
> >> EndSection
> >>
> >> Section "Device"
> >> Identifier "Videocard0"
> >> Driver "i810"
> >> VendorName "Videocard vendor"
> >> BoardName "Intel 915"
> >> EndSection
> >>
> >> Section "Screen"
> >> Identifier "Screen0"
> >> Device "Videocard0"
> >> Monitor "Monitor0"
> >> DefaultDepth 24
> >> SubSection "Display"
> >> Viewport 0 0
> >> Depth 16
> >> Modes "800x600" "640x480"
> >> EndSubSection
> >> SubSection "Display"
> >> Viewport 0 0
> >> Depth 24
> >> Modes "1680x1050" "1600x1200" "1400x1050" "1280x960"
> >> "1280x800" "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
> >> EndSubSection
> >> EndSection
> >>
> >> - patrick
> >>
> >>
> >> Philip Prindeville wrote:
> >>
> >>> The EDID reported by this monitor is slightly broken, and I've been
> >>> trying to get Dell to fix it, but they have no clue as to what I'm
> >>> talking
> >>> about, and their "award winning service" (in India) has no way of
> >>> talking to anyone on the factory floor or in the design bureau in
> >>> Texas or wherever that might be.
> >>>
> >>> The modeline I use is:
> >>>
> >>> ModeLine "1680x1050 (Dell)" 147.14 1680 1784 1960 2240 1050 1058
> >>> 1063 1103
> >>>
> >>> (and I have to turn on "noDDC" to get it to work...)
> >>>
> >>> -Philip
> >>>
> >>
> >> _______________________________________________
> >> xorg mailing list
> >> xorg at lists.freedesktop.org
> >> http://lists.freedesktop.org/mailman/listinfo/xorg
> >
> >
> >
> > _______________________________________________
> > xorg mailing list
> > xorg at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/xorg
>
> --
> "Computer Science is no more about computers than astronomy is about
> telescopes." - Edsger Dijkstra
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 21 Oct 2005 17:12:34 -0600
> From: Philip Prindeville <philipp_subx at redfish-solutions.com>
> Subject: Re: enabling DDC in the face of broken monitors
> To: Discuss issues related to the xorg tree
> <xorg at lists.freedesktop.org>
> Message-ID: <435975E2.20108 at redfish-solutions.com>
> Content-Type: text/plain; charset=ISO-8859-15; format=flowed
>
> Mike A. Harris wrote:
>
> > Philip Prindeville wrote:
> >
> >> Say it ain't so, Joe!
> >>
> >> I think this would be a big step backwards... It's like refusing to
> >> turn on the kitchen lights, because you then have to see all the
> >> cockroaches. ;-)
> >>
> >> Yeah, turning on DDC will reveal a lot of bugs, at least initially...
> >> but the product development cycle of monitors is fairly short,
> >> and eventually the bogus monitors will be retired.
> >
> >
> > Monitors last for years, so that line of reasoning is totally not
> > reasonable. People want their hardware to work out of the box
> > without messing around, in particular if it always worked out of
> > the box for them in the past.
> >
> > Telling them "buy a new monitor, your $1500 monitor is broken
> > hardware" when it worked before, is not a good way to make new
> > friends.
>
>
>
> All true. What I meant was that people eventually figure out a way
> to work around a broken monitor. After all, that's what we do right
> now... so we won't be any worse off in that case, and when the
> DDC/EDID is correct, things will magically work much better.
>
>
> >> building monitors that "just work" will get that reputation, and
> >> be rewarded... and those that don't... Well, they'll learn or perish.
> >
> > And... market forces being what they are, the manufacturers
> >
> > You think Dell is going to perish? I'd put my money on the
> > opposite. I'll go as far as to claim that Dell could probably
> > make their monitor EDID information random numbers and only
> > affect their sales slightly if at all.
>
>
> Well.. That may be true for other reasons. Windows drivers look
> at the shipped .inf files, or the .inf files fetch off the internet.
>
> They are heavily invested into the Windows market: it's a large part
> of their sales share. But assuming they weren't: shipping bad EDID
> information would be a real hit for them.
>
> >> Why isn't it more generic? Isn't that the point, after all?
> >
> > On another front... Why is the DDC stuff as per-driver as it is?
> >
> > For the same reason that 2D accelerated line drawing is different
> > on every piece of hardware out there, or other 2D or 3D primitives,
> > or accelerated video functionality, or pretty much anything at all
> > on any modern video hardware. It is a function of the hardware,
> > which is programmed in a unique manner from manufacturer to
> > manufacturer, and from card to card, and sometimes chip to chip.
> >
> > While DDC isn't a feature you generally think of "on screen" like
> > you might think of accelerated line drawing, nonetheless it is
> > handled by frobbing this, poking that, and those operations
> > differ on different hardware.
> >
> > If it were possible to probe DDC in a hardware generic manner
> > reliably (No, VBE is not reliable), then all of the drivers would
> > do it that way. The same can be said for line drawing or 3D, or
> > whatever also though.
> >
> > It is the job of the X server to call per video driver functions,
> > which then translate the "generic" request (ie: probe DDC info)
> > into card specific requests (when direct programming info is
> > known - or to use VBE otherwise, which is unreliable).
>
>
> I guess I thought that the card driver located the DDC mechanism,
> and then called into the generic DDC guts to do the I2C signalling
> to actual start the transfer, parse the results, etc.
>
> >
> >
> >> I've also been playing with the idea of having the DDC code
> >> prime the "modeline" list with manufacturer specific modes,
> >> and name them "Native#1", "Native#2", etc. sorted by
> >> highest to lowest resolution.
> >>
> >> Thereby, a person could have:
> >>
> >> Section "Screen"
> >> ...
> >> UseModes "builtin"
> >> Modes "Native#1" "Native#2" "Native#3"
> >> ...
> >> EndSection
> >>
> >> and the configuration would just work at the highest resolution
> >> the monitor would support (well, and the video adapter).
> >
> >
> > Which falls apart when a single monitor out there has broken modeline
> > EDID data. In theory, it could even fry the display. I'm not
> > aware of one, but there are enough monitors out there with broken
> > EDID data that it is reasonable to assume they exist.
>
>
> Another reason to use LCD monitors. ;-)
>
> Well, 'Options "noDDC"' will remain a workaround for a long time
> to come.
>
>
> >
> > Even if such monitors are rare, they're not so rare when they're
> > shipped by one of the largest computer manufacturers in mass
> > volume. Even if only 10000 users experience such a problem, that
> > is about 1000 bug reports to wade through from angry users who
> > have hardware that "just works fine in Windows, and in all previous
> > X releases".
>
>
> Ok.... so... we should come up with a .inf file parser... :-(
>
> I guess a larger problem is that the various Lini that support
> "yum" (or whatever) couldn't make use of more frequent
> updates of id information (such as /usr/share/hwdata/pcids.txt on
> Fedora, etc).
>
> If this information were pushed out with reasonable
> frequency (say weekly or better), then we could give various
> hints about new hardware (such as, "ignore edid info coming
> from this monitor because it's a liar and stick to VESA modes").
>
> -Philip
>
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 20 Oct 2005 13:48:13 -0700
> From: Keith Packard <keithp at keithp.com>
> Subject: Re: Composite and MapNotifies
> To: Discuss issues related to the xorg tree
> <xorg at lists.freedesktop.org>
> Cc: xorg at freedesktop.org
> Message-ID: <1129841293.4443.11.camel at evo.keithp.com>
> Content-Type: text/plain; charset="us-ascii"
>
> On Thu, 2005-10-20 at 22:14 +0200, Soeren Sandmann wrote:
>
> > So I propose the attached patch which turn off generation of the
> > Map/UnmapNotifies for the windows during the redirection process. The
> > window manager will then not even know that anything happened.
>
> I guess this is probably the easiest plan. I'm not fond of the proposed
> patch though; stealing another bit in the window structure for this very
> minor purpose seems like a waste to me. Covering this with a functional
> interface would let us use a simple global variable for now:
>
> DisableMapUnmapEvents (WindowPtr pWin) {
> windowHidingMapUnmapEvents = pWin;
> }
> EnableMapUnmapEvents (WindowPtr pWin) {
> windowHidingMapUnmapEvents = NULL;
> }
>
> Alternatives greatly appreciated...
>
> -keith
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 189 bytes
> Desc: This is a digitally signed message part
> Url : http://lists.freedesktop.org/archives/xorg/attachments/20051020/ae314acf/attachment-0002.pgp
>
> ------------------------------
>
> Message: 7
> Date: Thu, 20 Oct 2005 13:48:13 -0700
> From: Keith Packard <keithp at keithp.com>
> Subject: Re: Composite and MapNotifies
> To: Discuss issues related to the xorg tree
> <xorg at lists.freedesktop.org>
> Cc: xorg at freedesktop.org
> Message-ID: <1129841293.4443.11.camel at evo.keithp.com>
> Content-Type: text/plain; charset="us-ascii"
>
> On Thu, 2005-10-20 at 22:14 +0200, Soeren Sandmann wrote:
>
> > So I propose the attached patch which turn off generation of the
> > Map/UnmapNotifies for the windows during the redirection process. The
> > window manager will then not even know that anything happened.
>
> I guess this is probably the easiest plan. I'm not fond of the proposed
> patch though; stealing another bit in the window structure for this very
> minor purpose seems like a waste to me. Covering this with a functional
> interface would let us use a simple global variable for now:
>
> DisableMapUnmapEvents (WindowPtr pWin) {
> windowHidingMapUnmapEvents = pWin;
> }
> EnableMapUnmapEvents (WindowPtr pWin) {
> windowHidingMapUnmapEvents = NULL;
> }
>
> Alternatives greatly appreciated...
>
> -keith
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 189 bytes
> Desc: This is a digitally signed message part
> Url : http://lists.freedesktop.org/archives/xorg/attachments/20051020/ae314acf/attachment-0003.pgp
>
> ------------------------------
>
> Message: 8
> Date: Sat, 22 Oct 2005 15:57:50 +1000
> From: Russell Shaw <rjshaw at netspace.net.au>
> Subject: XSetInputFocus
> To: xorg at lists.freedesktop.org
> Message-ID: <4359D4DE.3010400 at netspace.net.au>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Hi,
> On P421 of "Xlib Programming Manual R4/R5", it says:
>
> "revert_to" can be set to "RevertToParent", then later on the
> same page it says it can be set to:
>
> "the parent of the window that is to be the new focus window"
>
> That last statement doesn't seem right. "revert_to" is not
> declared as a Window:
>
> XSetInputFocus(display, focus, revert_to, time)
> Display *display;
> Window focus;
> int revert_to;
> Time time;
>
>
> ------------------------------
>
> Message: 9
> Date: Sat, 22 Oct 2005 14:56:10 +0200
> From: Henk Poley <hpoley at dds.nl>
> Subject: Re: Unsubscribing from this list not possible!
> To: Discuss issues related to the xorg tree
> <xorg at lists.freedesktop.org>
> Message-ID: <200510221456.10866.hpoley at dds.nl>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Op zaterdag 22 oktober 2005 00:40, schreef Carsten Otto:
> > I'd like to unsubscribe from this list, but I can't.
> >
> > I enter my adress (see signature) in field at the very bottom and go
> > to the next site by clicking the button. There it says
> >
> > "Error: Illegal Email Address: carsten.otto at gmail.com"
> >
> > This is not true, the address is valid in my eyes.
> > Pressing the unsubscribe button gives:
>
> You may have subscribed without the dot in the name. With GMail you may add
> (or leave out) as many dots in the part before the @-sign as you like.
>
> Could that be the case? Not that I do not encourage the list maintainers to
> look into this :-P
>
> Henk Poley <><
>
>
> ------------------------------
>
> _______________________________________________
> xorg mailing list
> xorg at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xorg
>
> End of xorg Digest, Vol 3, Issue 53
> ***********************************
>
More information about the xorg
mailing list