Re: How to find HorizSync / VertRefresh rates?
On 5/4/07, Ted Mittelstaedt [EMAIL PROTECTED] wrote: [mailto:[EMAIL PROTECTED] Behalf Of Victor Engmark It works in the sense that I get the correct dimensions, Then it is working. Your done, quit diddling with it. but I'm unsure as to whether I risk frying the card or screen You cannot fry either. An LCD panel has a computer that will take a specified range of vert and horz sync frequencies. As I already mentioned these sync frequencies are meaningless with an LCD, since the display chip merely converts them to what the LCDs in the panel actually need. It is more expensive to make a display chip that takes extremely high frequencies and since they aren't needed for LCD that is why the display chips in the panels do not accept as high frequencies as a really high quality crt will. Alright, I'll take your word for it. Thanks to everybody who contributed! -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 5/2/07, Dag-Erling Smørgrav [EMAIL PROTECTED] wrote: Victor Engmark [EMAIL PROTECTED] writes: I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. These parameters are meaningless for an LCD panel. Leave them out, and X.org will DTRT. The wrong values will *not* fry your panel. OK, I'll settle for that one. But then, why do I get a warning that the default HorizSync rate is out of the DDC rates for my screen? I assume that the screen will report a bogus value when queried about the rate if it's not applicable. X.org should be able to detect such values, to avoid any false warnings. Anyone else think this warrants a bug report? -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Tuesday, 1 May 2007 at 9:28:27 +0200, Victor Engmark wrote: On 5/1/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Monday, 30 April 2007 at 11:02:54 +0200, Victor Engmark wrote: 1: Try XFree86. Maybe that will work better. I'm a bit reluctant to straying away from the recommended setup on my work machine. Even if the recommended setup doesn't work? Note that we have both in the ports collection, so the definition of recommended sounds more like default to me. It works in the sense that I get the correct dimensions, but I'm unsure as to whether I risk frying the card or screen by using the current values, and whether I can somehow establish which values would be optimal for my card and screen. Besides, isn't the code base for this and X.org still very similar? Yes, but there have been many edge cases where one works and the other doesn't. In general, X.org brings better results, but it's worth a try. Alright, thanks. I'll see about it. Get hold of the latest Knoppix CD from http://www.knoppix.org/, burn it to CD, boot from it and see if that works. Knoppix is a Linux distribution that runs from CD, so it's good for this kind of test. I still don't understand how it will provide the values I'm looking for. I note that none of the other messages that have gone by in this thread have addressed what I consider to be the crucial point: you have a BIOS mapping issue. It would be interesting to know what version of FreeBSD you're running. 6.2-RELEASE. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On Thursday, 3 May 2007 at 9:25:54 +0200, Victor Engmark wrote: On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Tuesday, 1 May 2007 at 9:01:26 +0200, Victor Engmark wrote: On 4/30/07, Erik Osterholm [EMAIL PROTECTED] wrote: Could you post your Xorg.0.log and xorg.conf? When Theory != Practice, it's often helpful to have information like this to help determine what went wrong, so that in the future, Theory can == Practice. Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this morning. I don't see the Xorg.0.log. Also, it would be interesting to see how the xorg.conf differs from the one you got from X -configure. The xorg.conf differs quite a lot. And how? Does it work? I used xorgconfig instead of X -configure , but xorgconfig doesn't autodetect any of the ranges, so there were none in the original file. Here's a cut'n'paste of the Xorg.0.log sent earlier: You didn't send it. This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the xorg product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation CVS repository. See http://wiki.x.org/wiki/CvsPage for CVS access instructions. X Window System Version 6.8.99.903 (6.9.0 RC 3) Release Date: 03 December 2005 + cvs Where did you get this from? 6.2-RELEASE used 6.9.0 release. Try rebuilding from the Ports Collection. Greg -- See complete headers for address and phone numbers. pgprKXEk3llAW.pgp Description: PGP signature
Re: How to find HorizSync / VertRefresh rates?
On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Thursday, 3 May 2007 at 9:25:54 +0200, Victor Engmark wrote: On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Tuesday, 1 May 2007 at 9:01:26 +0200, Victor Engmark wrote: On 4/30/07, Erik Osterholm [EMAIL PROTECTED] wrote: Could you post your Xorg.0.log and xorg.conf? When Theory != Practice, it's often helpful to have information like this to help determine what went wrong, so that in the future, Theory can == Practice. Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this morning. I don't see the Xorg.0.log. Also, it would be interesting to see how the xorg.conf differs from the one you got from X -configure. The xorg.conf differs quite a lot. And how? Does it work? For the currently applicable definition of work, no. I get a warning message from X.org every time I boot. I used xorgconfig instead of X -configure , but xorgconfig doesn't autodetect any of the ranges, so there were none in the original file. Here's a cut'n'paste of the Xorg.0.log sent earlier: You didn't send it. According to Gmail, I did. I copied the file from the email I sent :) This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the xorg product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation CVS repository. See http://wiki.x.org/wiki/CvsPage for CVS access instructions. X Window System Version 6.8.99.903 (6.9.0 RC 3) Release Date: 03 December 2005 + cvs Where did you get this from? 6.2-RELEASE used 6.9.0 release. Try rebuilding from the Ports Collection. I burned the 6.2-RELEASE CD from freebsd.org. After installing a lot of software, I ran portupgrade -a . Surely, I should have the same or newer than the release by then? Also, pkg_version -vIL= right now doesn't list X.org. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On Thursday, 3 May 2007 at 11:16:04 +0200, Victor Engmark wrote: On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Thursday, 3 May 2007 at 9:25:54 +0200, Victor Engmark wrote: On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Tuesday, 1 May 2007 at 9:01:26 +0200, Victor Engmark wrote: On 4/30/07, Erik Osterholm [EMAIL PROTECTED] wrote: Could you post your Xorg.0.log and xorg.conf? When Theory != Practice, it's often helpful to have information like this to help determine what went wrong, so that in the future, Theory can == Practice. Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this morning. I don't see the Xorg.0.log. Also, it would be interesting to see how the xorg.conf differs from the one you got from X -configure. The xorg.conf differs quite a lot. And how? Does it work? For the currently applicable definition of work, no. I get a warning message from X.org every time I boot. OK. Either you give me information on what happens, or I'll drop the case. What warning message? Why when you boot? What does the screen look like? What does the Xorg.0.log look like? I used xorgconfig instead of X -configure , but xorgconfig doesn't autodetect any of the ranges, so there were none in the original file. Here's a cut'n'paste of the Xorg.0.log sent earlier: You didn't send it. According to Gmail, I did. Here's what arrived here: Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this morning. ... [-- Attachment #2: xorg.conf --] [-- Type: application/octet-stream, Encoding: base64, Size: 6.0K --] [-- application/octet-stream is unsupported (use 'v' to view this part) --] [-- Attachment #3 --] [-- Type: text/plain, Encoding: 7bit, Size: 0.2K --] I copied the file from the email I sent :) Is it also in the mail you received? It's definitely not here. This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Where did you get this from? 6.2-RELEASE used 6.9.0 release. Try rebuilding from the Ports Collection. I burned the 6.2-RELEASE CD from freebsd.org. After installing a lot of software, From where? I ran portupgrade -a . Surely, I should have the same or newer than the release by then? Based on your statements, it's hard to say. Also, pkg_version -vIL= right now doesn't list X.org. This suggests that you installed it from elsewhere. As I said, Try rebuilding from the Ports Collection. I've given you a whole lot of suggestions. If you feel like trying some of them, please report with useful feedback. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgp4G0aObtIPC.pgp Description: PGP signature
Re: How to find HorizSync / VertRefresh rates?
On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Thursday, 3 May 2007 at 11:16:04 +0200, Victor Engmark wrote: On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Thursday, 3 May 2007 at 9:25:54 +0200, Victor Engmark wrote: On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Tuesday, 1 May 2007 at 9:01:26 +0200, Victor Engmark wrote: On 4/30/07, Erik Osterholm [EMAIL PROTECTED] wrote: Could you post your Xorg.0.log and xorg.conf? When Theory != Practice, it's often helpful to have information like this to help determine what went wrong, so that in the future, Theory can == Practice. Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this morning. I don't see the Xorg.0.log. Also, it would be interesting to see how the xorg.conf differs from the one you got from X -configure. The xorg.conf differs quite a lot. And how? Does it work? For the currently applicable definition of work, no. I get a warning message from X.org every time I boot. OK. Either you give me information on what happens, or I'll drop the case. What warning message? Please read the rest of the thread. I'm getting a warning that the HorizSync rate is outside the capabilities of my current hardware, whether I use the default (none), the values from MonitorsDB, or what other people have posted in their xorg.conf files for other Dell Latitude D610s. Why when you boot? Because I run KDE at boot. From /etc/ttys: ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure What does the screen look like? Fine. That's not the issue, as stated several times in this thread. What does the Xorg.0.log look like? I've sent it twice. What else do you want to know? I used xorgconfig instead of X -configure , but xorgconfig doesn't autodetect any of the ranges, so there were none in the original file. Here's a cut'n'paste of the Xorg.0.log sent earlier: You didn't send it. According to Gmail, I did. Here's what arrived here: Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this morning. ... [-- Attachment #2: xorg.conf --] [-- Type: application/octet-stream, Encoding: base64, Size: 6.0K --] [-- application/octet-stream is unsupported (use 'v' to view this part) --] [-- Attachment #3 --] [-- Type: text/plain, Encoding: 7bit, Size: 0.2K --] I copied the file from the email I sent :) Is it also in the mail you received? It's definitely not here. I only see the version which was sent by Gmail. It collates my emails when I receive one I sent myself. Maybe the attachment was too big for the list, but I didn't receive any error messages or warnings. Here are the headers for the attachment: --=_Part_133278_20384899.1178002886715 Content-Type: text/x-log; name=Xorg.0.log; charset=ANSI_X3.4-1968 Content-Transfer-Encoding: base64 X-Attachment-Id: f_f160abdg Content-Disposition: attachment; filename=Xorg.0.log This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Where did you get this from? 6.2-RELEASE used 6.9.0 release. Try rebuilding from the Ports Collection. I burned the 6.2-RELEASE CD from freebsd.org. After installing a lot of software, From where? Official FreeBSD mirrors. I don't know where to find the settings, but I used the first Swiss mirror in sysinstall. I ran portupgrade -a . Surely, I should have the same or newer than the release by then? Based on your statements, it's hard to say. Based on me installing from an official CD, and using the default settings for portupgrade? In that case, I don't understand why. Also, pkg_version -vIL= right now doesn't list X.org. This suggests that you installed it from elsewhere. As I said, I installed from the official FreeBSD mirrors. Try rebuilding from the Ports Collection. I've already done a portupgrade -a since I installed. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On Thursday, 3 May 2007 at 13:13:07 +0200, Victor Engmark wrote: On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: OK. Either you give me information on what happens, or I'll drop the case. What warning message? Please read the rest of the thread. Find somebody else to solve your problem. Or better still, do it yourself. You're wasting many people's time. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgpmtpIDNRuMh.pgp Description: PGP signature
Re: How to find HorizSync / VertRefresh rates?
On 03/05/07, Victor Engmark [EMAIL PROTECTED] wrote: Please read the rest of the thread. I'm getting a warning that the HorizSync rate is outside the capabilities of my current hardware Fairly normal. Many display adapters are capable of modes that the display does not support. The server will not use a mode outside of what it is told (/etc/X11/xorg.conf or whatnot) or what it detects and the warnings are just part of a global conspiracy to increase aerobic fitness through twitching. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
Victor Engmark [EMAIL PROTECTED] writes: OK, I'll settle for that one. But then, why do I get a warning that the default HorizSync rate is out of the DDC rates for my screen? I can't tell unless you show me the log. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 5/3/07, Dag-Erling Smørgrav [EMAIL PROTECTED] wrote: Victor Engmark [EMAIL PROTECTED] writes: OK, I'll settle for that one. But then, why do I get a warning that the default HorizSync rate is out of the DDC rates for my screen? I can't tell unless you show me the log. /var/log/Xorg.0.log has been posted twice in this thread. If you mean another log, then please specify. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
Victor Engmark [EMAIL PROTECTED] writes: On 5/3/07, Dag-Erling Smørgrav [EMAIL PROTECTED] wrote: Victor Engmark [EMAIL PROTECTED] writes: OK, I'll settle for that one. But then, why do I get a warning that the default HorizSync rate is out of the DDC rates for my screen? I can't tell unless you show me the log. /var/log/Xorg.0.log has been posted twice in this thread. If you mean another log, then please specify. All I found was this: (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. (II) I810(0): Dell Latitude D610 monitor: Using hsync range of 60.00-66.32kHz (II) I810(0): Dell Latitude D610 monitor: Using vrefresh value of 60.00 Hz which tells me you specified an incorrect range in your xorg.conf; I told you to remove it. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: How to find HorizSync / VertRefresh rates?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Victor Engmark Sent: Thursday, May 03, 2007 1:24 AM To: Greg 'groggy' Lehey Cc: FreeBSD Questions Subject: Re: How to find HorizSync / VertRefresh rates? It works in the sense that I get the correct dimensions, Then it is working. Your done, quit diddling with it. but I'm unsure as to whether I risk frying the card or screen You cannot fry either. An LCD panel has a computer that will take a specified range of vert and horz sync frequencies. As I already mentioned these sync frequencies are meaningless with an LCD, since the display chip merely converts them to what the LCDs in the panel actually need. It is more expensive to make a display chip that takes extremely high frequencies and since they aren't needed for LCD that is why the display chips in the panels do not accept as high frequencies as a really high quality crt will. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: How to find HorizSync / VertRefresh rates?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Victor Engmark Sent: Tuesday, May 01, 2007 12:28 AM To: Greg 'groggy' Lehey Cc: FreeBSD Questions Subject: Re: How to find HorizSync / VertRefresh rates? On 5/1/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Monday, 30 April 2007 at 11:02:54 +0200, Victor Engmark wrote: I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. I've tried the values presented in MonitorsDB http://sources.gentoo.org/viewcvs.py/gentoo/src/hwdata/MonitorsDB ?view=markup for Dell 1400x1050 Laptop Display Panel, which are HorizSync 31.5-90.0 and VertRefresh 59.0-75.0, but I get a warning in /var/log/Xorg.0.log for both of them saying they are not within DDC ranges. I've tried looking around the Dell web pages, but I haven't found any pages mentioning these parameters (not too surprising, really). I've tried to leave these settings out, but even then I get a warning: (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. I'm wondering if this has anything to do with the other warnings I get during startup: (WW) I810(0): Bad V_BIOS checksum and (WW) I810(0): Extended BIOS function 0x5f05 failed. This, along with the follow-ups, reminds me of a problem I had with a Dell Inspiron 5100 some years ago. In that case, X didn't map the video BIOS correctly, and so it wasn't able to read the information from the BIOS. The information includes things like the panel geometry, which in my case was being reported as 65535x65535 pixels. In your case we have: # From Xorg.0.log DisplaySize 286 214 That's clearly wrong too. It's equal to the values in the documentationhttp://support.euro.dell.com/support/edocs/systems/l atd610/en/ug_en/specs.htm, rounded off to integers. I feel the need to remind folks that the concept of refresh rates is completely meaningless with LCD panels. Flatpanels do not have a single scan gun that draws lines at a specific time and rate of speed across a phosphor. The computer in the LCD panel takes the video input at a range of refresh rates, and converts it to a bitmapped image that is fed to the display crystals. You can use whatever horizontal and vertical refresh rates you want, as long as they are in the table that the LCD panel's computer can decode, the resulting output is the same. I also will remind people that the pixel counts as resolution on flatpanels also have no meaning. A flat panel has a fixed natural resolution. Any other resolution that you feed to it is either dithered up or dithered down to match the actual resolution by the display computer in the flat panel. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 5/2/07, Ted Mittelstaedt [EMAIL PROTECTED] wrote: I feel the need to remind folks that the concept of refresh rates is completely meaningless with LCD panels. Flatpanels do not have a single scan gun that draws lines at a specific time and rate of speed across a phosphor. Well, the rates are both related to the video card, not the display. I'm not sure how the card feeds the image to an LCD display, but I guess that would depend on the enforced horizontal sync and vertical refresh rates. In any case, it's useful to have these rates if I should ever have the need to attach the card to an external CRT display. The computer in the LCD panel takes the video input at a range of refresh rates, and converts it to a bitmapped image that is fed to the display crystals. You can use whatever horizontal and vertical refresh rates you want, as long as they are in the table that the LCD panel's computer can decode, the resulting output is the same. Even though LCD displays don't flicker, it's useful to set the refresh as high as the panel is able to display, to get smooth transitions. I also will remind people that the pixel counts as resolution on flatpanels also have no meaning. A flat panel has a fixed natural resolution. Any other resolution that you feed to it is either dithered up or dithered down to match the actual resolution by the display computer in the flat panel. I'm well aware of that, but I would still like my video card and screen to perform to the best of their abilities, in order to display the biggest amount of data per second possible, without frying. Anything else is a waste of resources. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: How to find HorizSync / VertRefresh rates?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Victor Engmark Sent: Wednesday, May 02, 2007 2:06 AM To: Ted Mittelstaedt Cc: FreeBSD Questions Subject: Re: How to find HorizSync / VertRefresh rates? On 5/2/07, Ted Mittelstaedt [EMAIL PROTECTED] wrote: I feel the need to remind folks that the concept of refresh rates is completely meaningless with LCD panels. Flatpanels do not have a single scan gun that draws lines at a specific time and rate of speed across a phosphor. Well, the rates are both related to the video card, not the display. I'm not sure how the card feeds the image to an LCD display, but I guess that would depend on the enforced horizontal sync and vertical refresh rates. If your using a VGA connection then yes it does depend on the refresh rates. But the refresh rate has no meaning after the signal is processed by the LCD panel's computer. In any case, it's useful to have these rates if I should ever have the need to attach the card to an external CRT display. The computer in the LCD panel takes the video input at a range of refresh rates, and converts it to a bitmapped image that is fed to the display crystals. You can use whatever horizontal and vertical refresh rates you want, as long as they are in the table that the LCD panel's computer can decode, the resulting output is the same. Even though LCD displays don't flicker, it's useful to set the refresh as high as the panel is able to display, to get smooth transitions. Try different rates, I think you will find that once you get above 70 Hz you won't be able to see any difference. I also will remind people that the pixel counts as resolution on flatpanels also have no meaning. A flat panel has a fixed natural resolution. Any other resolution that you feed to it is either dithered up or dithered down to match the actual resolution by the display computer in the flat panel. I'm well aware of that, but I would still like my video card and screen to perform to the best of their abilities, in order to display the biggest amount of data per second possible, without frying. Anything else is a waste of resources. I think you misunderstand. If an LCD panel has a resolution of 1024x768 and you feed it 1280x1024, even though the panel can handle it, you still only get 1024x768 on the panel. In fact, you get worse because all of the sharp lines are blurred by the dithering down of 1280x1024 to 1024x768. And the human eye cannot see distinct pictures at refresh rates beyond about 30-40 frames per second. You may see flicker, but the human eye cannot even distinguish that, much beyond 65-70Hz. Speeding things up is equivalent to putting a blue fan with pretty lights that light up when it runs, inside a computer power supply. You can't see the difference, but I guess spending the extra money or just knowing it's there, is comfort food. What you really want in an LCD panel is a panel with the highest actual resolution as possible, and ignore the refresh rate. But that's expensive. Which is why so many people have crappy LCD panels. It never ceases to amaze me that people will take a perfectly good, sharp, CRT monitor that can do 1600 x 1400 or some such and toss it out and replace it with an LCD panel that is the same diagonal size but cannot do better than 1024x768, and think they have a better display. I suspect your confusing things like font size with screen resolution which is a common thing for people to do. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 5/2/07, Ted Mittelstaedt [EMAIL PROTECTED] wrote: [mailto:[EMAIL PROTECTED] Behalf Of Victor Engmark On 5/2/07, Ted Mittelstaedt [EMAIL PROTECTED] wrote: The computer in the LCD panel takes the video input at a range of refresh rates, and converts it to a bitmapped image that is fed to the display crystals. You can use whatever horizontal and vertical refresh rates you want, as long as they are in the table that the LCD panel's computer can decode, the resulting output is the same. Even though LCD displays don't flicker, it's useful to set the refresh as high as the panel is able to display, to get smooth transitions. Try different rates, I think you will find that once you get above 70 Hz you won't be able to see any difference. But then my card / screen may be fried. And the human eye cannot see distinct pictures at refresh rates beyond about 30-40 frames per second. You may see flicker, but the human eye cannot even distinguish that, much beyond 65-70Hz. http://www.100fps.com/how_many_frames_can_humans_see.htm - Interesting reading in that respect. Screens still have a long way to go. The rest of the mail looks like trolling, so I'll just leave those parts alone. I only need one of the following three: - Reference documentation where the capabilities of my screen is explained. - A working method for finding this information on my own. - A good explanation for why I should ignore the X.org warnings. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
Victor Engmark [EMAIL PROTECTED] writes: I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. These parameters are meaningless for an LCD panel. Leave them out, and X.org will DTRT. The wrong values will *not* fry your panel. If you're having trouble getting the correct resolution to work, you probably just need to run 915resolution to patch the BIOS so X.org will detect the correct mode. The best way to create a pristine xorg.conf, by the way, is to run 'X -configure' (after running 915resolution, if applicable). DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
Greg 'groggy' Lehey [EMAIL PROTECTED] writes: On Monday, 30 April 2007 at 11:02:54 +0200, Victor Engmark wrote: DisplaySize 286 214 That's clearly wrong too. No, those are the physical dimensions of his panel in millimeters. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
Victor Engmark [EMAIL PROTECTED] writes: Even though LCD displays don't flicker, it's useful to set the refresh as high as the panel is able to display, to get smooth transitions. Most LCD panels don't go higher than 60 fps, and you won't notice much difference beyond ~30 fps anyway due to persistence - the pixels are physically unable to change color faster than this. Setting your refresh rate to anything else than the default 60 Hz will simply generate heat and eat up your battery for no gain. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On Tuesday, 1 May 2007 at 9:28:27 +0200, Victor Engmark wrote: On 5/1/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Monday, 30 April 2007 at 11:02:54 +0200, Victor Engmark wrote: I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. I've tried the values presented in MonitorsDB http://sources.gentoo.org/viewcvs.py/gentoo/src/hwdata/MonitorsDB?view=markup for Dell 1400x1050 Laptop Display Panel, which are HorizSync 31.5-90.0 and VertRefresh 59.0-75.0, but I get a warning in /var/log/Xorg.0.log for both of them saying they are not within DDC ranges. I've tried looking around the Dell web pages, but I haven't found any pages mentioning these parameters (not too surprising, really). I've tried to leave these settings out, but even then I get a warning: (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. I'm wondering if this has anything to do with the other warnings I get during startup: (WW) I810(0): Bad V_BIOS checksum and (WW) I810(0): Extended BIOS function 0x5f05 failed. This, along with the follow-ups, reminds me of a problem I had with a Dell Inspiron 5100 some years ago. In that case, X didn't map the video BIOS correctly, and so it wasn't able to read the information from the BIOS. The information includes things like the panel geometry, which in my case was being reported as 65535x65535 pixels. In your case we have: # From Xorg.0.log DisplaySize 286 214 That's clearly wrong too. It's equal to the values in the documentationhttp://support.euro.dell.com/support/edocs/systems/latd610/en/ug_en/specs.htm, rounded off to integers. Yes, my bad. I was confusing it with the number of pixels. See http://www.lemis.com/grog/diary-jul2003.html#25 for more details. It's worth mentioning that the problem was fixed in a later version of the system, and I can now install X on it with no problems. If this looks familiar, a couple of suggestions: 1: Try XFree86. Maybe that will work better. I'm a bit reluctant to straying away from the recommended setup on my work machine. Even if the recommended setup doesn't work? Note that we have both in the ports collection, so the definition of recommended sounds more like default to me. Besides, isn't the code base for this and X.org still very similar? Yes, but there have been many edge cases where one works and the other doesn't. In general, X.org brings better results, but it's worth a try. 2: Get hold of the latest Knoppix CD and see if that works. If it does, it might help fix the problem under FreeBSD. Do you mean running Xorg -configure and see if it gives the right information? No. If not, could you elaborate a bit? Thanks! Get hold of the latest Knoppix CD from http://www.knoppix.org/, burn it to CD, boot from it and see if that works. Knoppix is a Linux distribution that runs from CD, so it's good for this kind of test. I note that none of the other messages that have gone by in this thread have addressed what I consider to be the crucial point: you have a BIOS mapping issue. It would be interesting to know what version of FreeBSD you're running. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgpn5aLc4Uhzx.pgp Description: PGP signature
Re: How to find HorizSync / VertRefresh rates?
On Tuesday, 1 May 2007 at 9:01:26 +0200, Victor Engmark wrote: On 4/30/07, Erik Osterholm [EMAIL PROTECTED] wrote: Could you post your Xorg.0.log and xorg.conf? When Theory != Practice, it's often helpful to have information like this to help determine what went wrong, so that in the future, Theory can == Practice. Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this morning. I don't see the Xorg.0.log. Also, it would be interesting to see how the xorg.conf differs from the one you got from X -configure. Greg -- See complete headers for address and phone numbers. pgpo9gxF4vDnB.pgp Description: PGP signature
Re: How to find HorizSync / VertRefresh rates?
On 4/30/07, Erik Osterholm [EMAIL PROTECTED] wrote: On Mon, Apr 30, 2007 at 08:33:03PM +0200, Victor Engmark wrote: On 4/30/07, J65nko [EMAIL PROTECTED] wrote: Follow the FBSD handbook to do a 'Xorg -configure' and a test run of X with the generated Xorg.conf file. I did. Then have a look at your your '/var/log/Xorg.0.log'. You will find a log of X using DDC to interrogate your LCD screen for it's capabilities and the acceptable modelines Nope. Already tried that, and the capabilities were /not/ listed in the log, the way it was described in several tutorials. rantThis is starting to look like one of the most common problems in F/OSS: Theory != Practice. In theory, any one of the methods already tried and suggested here should work. In practice, the documentation (MonitorsDB) is wrong (at least according to x.org), and none of the quoted methods work the way they should. An interesting result is that there are several fundamentally different tutorials for several closely related *nixes, all of which work only on a small subset of installations./rant Could you post your Xorg.0.log and xorg.conf? When Theory != Practice, it's often helpful to have information like this to help determine what went wrong, so that in the future, Theory can == Practice. Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this morning. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound xorg.conf Description: Binary data ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to find HorizSync / VertRefresh rates?
Hi all, I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. I've tried the values presented in MonitorsDB http://sources.gentoo.org/viewcvs.py/gentoo/src/hwdata/MonitorsDB?view=markup for Dell 1400x1050 Laptop Display Panel, which are HorizSync 31.5-90.0 and VertRefresh 59.0-75.0, but I get a warning in /var/log/Xorg.0.log for both of them saying they are not within DDC ranges. I've tried looking around the Dell web pages, but I haven't found any pages mentioning these parameters (not too surprising, really). I've tried to leave these settings out, but even then I get a warning: (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. I'm wondering if this has anything to do with the other warnings I get during startup: (WW) I810(0): Bad V_BIOS checksum and (WW) I810(0): Extended BIOS function 0x5f05 failed. It seems that a DDC (or, apparently, DDS) query should be able to determine these numbers, but cd /usr/ports make search name=ddc make search name=dds doesn't give any tools to deal with this. The relevant part of /etc/X11/xorg.conf: Section Monitor Identifier Dell Latitude D610 monitor VendorName SEC ModelName3450 # From Xorg.0.log DisplaySize 286 214 Option DPMS EndSection -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 4/30/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Mon, 30 Apr 2007, Victor Engmark wrote: I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. I've tried the values presented in MonitorsDB http://sources.gentoo.org/viewcvs.py/gentoo/src/hwdata/MonitorsDB?view=markup for Dell 1400x1050 Laptop Display Panel, which are HorizSync 31.5-90.0 and VertRefresh 59.0-75.0, but I get a warning in /var/log/Xorg.0.log for both of them saying they are not within DDC ranges. I've tried looking around the Dell web pages, but I haven't found any pages mentioning these parameters (not too surprising, really). I've tried to leave these settings out, but even then I get a warning: (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. I'm wondering if this has anything to do with the other warnings I get during startup: (WW) I810(0): Bad V_BIOS checksum and (WW) I810(0): Extended BIOS function 0x5f05 failed. It seems that a DDC (or, apparently, DDS) query should be able to determine these numbers, but cd /usr/ports make search name=ddc make search name=dds doesn't give any tools to deal with this. The relevant part of /etc/X11/xorg.conf: Section Monitor Identifier Dell Latitude D610 monitor VendorName SEC ModelName3450 # From Xorg.0.log DisplaySize 286 214 Option DPMS EndSection Get the info off any labels you might find on your monitor and go to: www.monitorworld.com You might get lucky Thanks, but no luck. There are no labels (it's a laptop screen), and the Dell product pagehttp://accessories.us.dell.com/sna/productdetail.aspx?sku=R6313doesn't provide any useful information. Too bad MonitorWorld doesn't allow indexing http://monitorworld.com/robots.txt, or it would actually be searchable (their search sucks). -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
Victor Engmark wrote: Hi all, I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. I've tried the values presented in MonitorsDB http://sources.gentoo.org/viewcvs.py/gentoo/src/hwdata/MonitorsDB?view=markup for Dell 1400x1050 Laptop Display Panel, which are HorizSync 31.5-90.0 and VertRefresh 59.0-75.0, but I get a warning in /var/log/Xorg.0.log for both of them saying they are not within DDC ranges. I've tried looking around the Dell web pages, but I haven't found any pages mentioning these parameters (not too surprising, really). I've tried to leave these settings out, but even then I get a warning: (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. I'm wondering if this has anything to do with the other warnings I get during startup: (WW) I810(0): Bad V_BIOS checksum and (WW) I810(0): Extended BIOS function 0x5f05 failed. It seems that a DDC (or, apparently, DDS) query should be able to determine these numbers, but cd /usr/ports make search name=ddc make search name=dds doesn't give any tools to deal with this. The relevant part of /etc/X11/xorg.conf: Section Monitor Identifier Dell Latitude D610 monitor VendorName SEC ModelName3450 # From Xorg.0.log DisplaySize 286 214 Option DPMS EndSection Hi Victor, Not sure if this will help, but there's some good information from a Linux Dell D610 user who seems to have a good xorg.conf which should be roughly the same for FreeBSD: http://www.kcore.org/?menumain=4menusub=2 He mentions a video BIOS patch called '915resolution'. There's a FreeBSD version at: http://www.freebsd.org/cgi/url.cgi?ports/sysutils/915resolution/pkg-descr More information on the hack here: http://www.geocities.com/stomljen/ -- HTH. John. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 4/30/07, John Murphy [EMAIL PROTECTED] wrote: Victor Engmark wrote: I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. I've tried the values presented in MonitorsDB http://sources.gentoo.org/viewcvs.py/gentoo/src/hwdata/MonitorsDB?view=markup for Dell 1400x1050 Laptop Display Panel, which are HorizSync 31.5-90.0 and VertRefresh 59.0-75.0, but I get a warning in /var/log/Xorg.0.log for both of them saying they are not within DDC ranges. I've tried looking around the Dell web pages, but I haven't found any pages mentioning these parameters (not too surprising, really). I've tried to leave these settings out, but even then I get a warning: (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. I'm wondering if this has anything to do with the other warnings I get during startup: (WW) I810(0): Bad V_BIOS checksum and (WW) I810(0): Extended BIOS function 0x5f05 failed. It seems that a DDC (or, apparently, DDS) query should be able to determine these numbers, but cd /usr/ports make search name=ddc make search name=dds doesn't give any tools to deal with this. The relevant part of /etc/X11/xorg.conf: Section Monitor Identifier Dell Latitude D610 monitor VendorName SEC ModelName3450 # From Xorg.0.log DisplaySize 286 214 Option DPMS EndSection Not sure if this will help, but there's some good information from a Linux Dell D610 user who seems to have a good xorg.conf which should be roughly the same for FreeBSD: http://www.kcore.org/?menumain=4menusub=2 The xorg.conf there doesn't define HorizSync or VertRefresh. He mentions a video BIOS patch called '915resolution'. There's a FreeBSD version at: http://www.freebsd.org/cgi/url.cgi?ports/sysutils/915resolution/pkg-descr More information on the hack here: http://www.geocities.com/stomljen/ I'm already using this. It's listed at the end of my email. In case my message was unclear, I've already managed to get the native resolution. I'm only looking for the proper HorizSync / VertRefresh rates, to avoid frying my graphics card or screen, and to get the maximum out of my hardware at the same time. I've already tried rates from several articles, but all of them result in warnings that the rates are outside the DDC spec, and none of them document where the numbers are from. The only reference I've found so far, MonitorsDB, is wrong, and Dell doesn't list the information I need. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On Mon, 2007-04-30 at 11:02 +0200, Victor Engmark wrote: Hi all, I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. Don't bother trying. If it works when you leave them unspecified, don't think any more about it. If it still doesn't work however, the easiest way is to construct a valid modeline specific to your monitor. Xorg can actually tell you what to put into your xorg.conf, see section 5.4.3.2 of the FreeBSD Handbook [1] The quickest way to get these values out is to grep your Xorg log (even from a failed run of Xorg). Eg (quoting from the Handbook) : $ grep -A 4 'Supported additional Video Mode' /var/log/Xorg.0.log (II) I810(0): Supported additional Video Mode: (II) I810(0): clock: 108.0 MHz Image Size: 340 x 270 mm (II) I810(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0 (II) I810(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0 (II) I810(0): Serial No: ETL5108015 This information is called EDID information. Creating a ModeLine from this is just a matter of putting the numbers in the correct order: ModeLine name clock 4 horiz. timings 4 vert. timings Heres one I made earlier (unfortunately, not the one from the log, that one works 'out-of-the-box') ModeLine 1680x1050 146.0 1680 1784 1960 2240 1050 1053 1059 1089 Cheers Tom [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html signature.asc Description: This is a digitally signed message part
Re: How to find HorizSync / VertRefresh rates?
On 4/30/07, Tom Evans [EMAIL PROTECTED] wrote: On Mon, 2007-04-30 at 11:02 +0200, Victor Engmark wrote: I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. Don't bother trying. If it works when you leave them unspecified, don't think any more about it. I'd rather not have to replace my laptop after a few weeks... If it still doesn't work however, the easiest way is to construct a valid modeline specific to your monitor. Xorg can actually tell you what to put into your xorg.conf, see section 5.4.3.2 of the FreeBSD Handbook [1] It works, but the issue is rather having the /correct/ configuration in order to utilize the hardware as well as possible without frying it. I've tried the method proposed, but I don't find the information mentioned. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 4/30/07, Victor Engmark [EMAIL PROTECTED] wrote: Hi all, I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. I've tried the values presented in MonitorsDB http://sources.gentoo.org/viewcvs.py/gentoo/src/hwdata/MonitorsDB?view=markup for Dell 1400x1050 Laptop Display Panel, which are HorizSync 31.5-90.0 and VertRefresh 59.0-75.0, but I get a warning in /var/log/Xorg.0.log for both of them saying they are not within DDC ranges. [snip] (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. [snip] It seems that a DDC (or, apparently, DDS) query should be able to determine these numbers, but [snip] I don't understand why people still configure X the old ancient way. Follow the FBSD handbook to do a 'Xorg -configure' and a test run of X with the generated Xorg.conf file. Then have a look at your your '/var/log/Xorg.0.log'. You will find a log of X using DDC to interrogate your LCD screen for it's capabilities and the acceptable modelines A snippet of my Xorg.0.log file -- (II) Loading sub module ddc (II) LoadModule: ddc (II) Loading /usr/X11R6/lib/modules/libddc.so (II) Module ddc: vendor=X.Org Foundation compiled for 6.9.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.8 (II) NV(0): I2C bus DDC initialized. (II) NV(0): Probing for EDID on I2C bus A... (II) NV(0): I2C device DDC:ddc2 registered at address 0xA0. (II) NV(0): I2C device DDC:ddc2 removed. (--) NV(0): DDC detected a CRT: (II) NV(0): Manufacturer: AOC Model: a770 Serial#: 30015 (II) NV(0): Year: 1998 Week: 15 (II) NV(0): EDID Version: 1.0 (II) NV(0): Analog Display Input, Input Voltage Level: 0.714/0.286 V (II) NV(0): Sync: Separate (II) NV(0): Max H-Image Size [cm]: horiz.: 32 vert.: 24 (II) NV(0): Gamma: 1.50 (II) NV(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display (II) NV(0): redX: 0.622 redY: 0.340 greenX: 0.282 greenY: 0.600 (II) NV(0): blueX: 0.147 blueY: 0.062 whiteX: 0.278 whiteY: 0.311 (II) NV(0): Supported VESA Video Modes: (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): Manufacturer's mask: 0 (II) NV(0): Supported Future Video Modes: (II) NV(0): #0: hsize: 640 vsize 480 refresh: 85 vid: 22833 (II) NV(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853 (II) NV(0): #2: hsize: 1024 vsize 768 refresh: 85 vid: 22881 [snip] (==) NV(0): Using gamma correction (1.0, 1.0, 1.0) (II) NV(0): Monitor0: Using default hsync range of 43.27-69.85 kHz (II) NV(0): Monitor0: Using default vrefresh range of 60.02-85.01 Hz (II) NV(0): Clock range: 12.00 to 350.00 MHz [snip](**) NV(0): *Default mode 1024x768: 94.5 MHz, 68.7 kHz, 85.0 Hz (II) NV(0): Modeline 1024x768 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (**) NV(0): *Default mode 800x600: 56.3 MHz, 53.7 kHz, 85.1 Hz (II) NV(0): Modeline 800x600 56.30 800 832 896 1048 600 601 604 631 +hsync +vsync (**) NV(0): Default mode 1024x768: 78.8 MHz, 60.1 kHz, 75.1 Hz (II) NV(0): Modeline 1024x768 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (**) NV(0): Default mode 1024x768: 75.0 MHz, 56.5 kHz, 70.1 Hz (II) NV(0): Modeline 1024x768 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (**) NV(0): Default mode 1024x768: 65.0 MHz, 48.4 kHz, 60.0 Hz (II) NV(0): Modeline 1024x768 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (**) NV(0): Default mode 832x624: 57.3 MHz, 49.7 kHz, 74.6 Hz [remainder snipped] - In your Xorg conf just put in the resolution you want and X will usually figure out which sync rates to use. Or copy the modelines you find in your Xorg.0.log file. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 4/30/07, J65nko [EMAIL PROTECTED] wrote: On 4/30/07, Victor Engmark [EMAIL PROTECTED] wrote: I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. I've tried the values presented in MonitorsDB http://sources.gentoo.org/viewcvs.py/gentoo/src/hwdata/MonitorsDB?view=markup for Dell 1400x1050 Laptop Display Panel, which are HorizSync 31.5-90.0 and VertRefresh 59.0-75.0, but I get a warning in /var/log/Xorg.0.log for both of them saying they are not within DDC ranges. [snip] (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. [snip] It seems that a DDC (or, apparently, DDS) query should be able to determine these numbers, but [snip] I don't understand why people still configure X the old ancient way. Follow the FBSD handbook to do a 'Xorg -configure' and a test run of X with the generated Xorg.conf file. I did. Then have a look at your your '/var/log/Xorg.0.log'. You will find a log of X using DDC to interrogate your LCD screen for it's capabilities and the acceptable modelines Nope. Already tried that, and the capabilities were /not/ listed in the log, the way it was described in several tutorials. rantThis is starting to look like one of the most common problems in F/OSS: Theory != Practice. In theory, any one of the methods already tried and suggested here should work. In practice, the documentation (MonitorsDB) is wrong (at least according to x.org), and none of the quoted methods work the way they should. An interesting result is that there are several fundamentally different tutorials for several closely related *nixes, all of which work only on a small subset of installations./rant -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On Mon, Apr 30, 2007 at 08:33:03PM +0200, Victor Engmark wrote: On 4/30/07, J65nko [EMAIL PROTECTED] wrote: Follow the FBSD handbook to do a 'Xorg -configure' and a test run of X with the generated Xorg.conf file. I did. Then have a look at your your '/var/log/Xorg.0.log'. You will find a log of X using DDC to interrogate your LCD screen for it's capabilities and the acceptable modelines Nope. Already tried that, and the capabilities were /not/ listed in the log, the way it was described in several tutorials. rantThis is starting to look like one of the most common problems in F/OSS: Theory != Practice. In theory, any one of the methods already tried and suggested here should work. In practice, the documentation (MonitorsDB) is wrong (at least according to x.org), and none of the quoted methods work the way they should. An interesting result is that there are several fundamentally different tutorials for several closely related *nixes, all of which work only on a small subset of installations./rant Could you post your Xorg.0.log and xorg.conf? When Theory != Practice, it's often helpful to have information like this to help determine what went wrong, so that in the future, Theory can == Practice. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On Monday, 30 April 2007 at 11:02:54 +0200, Victor Engmark wrote: Hi all, I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. I've tried the values presented in MonitorsDB http://sources.gentoo.org/viewcvs.py/gentoo/src/hwdata/MonitorsDB?view=markup for Dell 1400x1050 Laptop Display Panel, which are HorizSync 31.5-90.0 and VertRefresh 59.0-75.0, but I get a warning in /var/log/Xorg.0.log for both of them saying they are not within DDC ranges. I've tried looking around the Dell web pages, but I haven't found any pages mentioning these parameters (not too surprising, really). I've tried to leave these settings out, but even then I get a warning: (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. I'm wondering if this has anything to do with the other warnings I get during startup: (WW) I810(0): Bad V_BIOS checksum and (WW) I810(0): Extended BIOS function 0x5f05 failed. This, along with the follow-ups, reminds me of a problem I had with a Dell Inspiron 5100 some years ago. In that case, X didn't map the video BIOS correctly, and so it wasn't able to read the information from the BIOS. The information includes things like the panel geometry, which in my case was being reported as 65535x65535 pixels. In your case we have: # From Xorg.0.log DisplaySize 286 214 That's clearly wrong too. See http://www.lemis.com/grog/diary-jul2003.html#25 for more details. It's worth mentioning that the problem was fixed in a later version of the system, and I can now install X on it with no problems. If this looks familiar, a couple of suggestions: 1: Try XFree86. Maybe that will work better. 2: Get hold of the latest Knoppix CD and see if that works. If it does, it might help fix the problem under FreeBSD. 3: Use the method I described in my diary to build a server with a static version of the video BIOS. The real answer, of course, is to understand why the mapping doesn't work (if, indeed, that's the problem). But this could be a start. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgp1yqPd2eb2r.pgp Description: PGP signature
