SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I want to have a resolution somewhere between 640x480 and 800x600. But, according to the man page of xorg.conf, the resolutions in the Screen section must satisfy certain requirements. If I specified a fixed horizontal and a fixed vertical frequency, then I could compute the resolution. But their are given as ranges in the Monitor section and do not want to touch them. Any ideas?
I think making up your own screen settings is kind of a "lost art". It was common with CRT monitors to do this, but LCD monitors have a native resolution and refresh rate, and don't work nearly as well in any other mode. If you really want to do this anyway, I suggest starting with this rather old file on your Slackware install: /usr/doc/Linux-HOWTOs/XFree86-Video-Timings-HOWTO
I'm not sure how much of it still applies, but it will give you an idea of what is involved in those timing values in the Mode lines of the Monitor configuration section.
You should be able to look through the /var/log/Xorg.*.log files and see what is available.
The monitor you use will dictate sizes... and not necessarily by frequency. LCD monitors don't work that way. They have a native display (usually the largest they will do), then smaller ones where it is an even division of that size... outside a list of supported resolutions, they tend to display nothing (a black screen).
Mine has an odd (to me) way of doing a 800x600... It does it by creating a display of 800x600... using 1920x1024 resolution, then centering it. Is it a 800x600 ... well sort of. Doesn't fill the screen though - the pixels are the same size as that used for 1920x1024.
Example of an xorg.conf file used to set the resolution to 1920x1080 - (delete the stuff that does not apply to you and) modify the "Modes" line at the very bottom to change resolution to anything you want.
Keep in mind of what jpollard wrote and have a look at your Xorg.0.log to know which resolutions are natively supported after that your graphics card spoke with your monitor. Resolutions that are not listed are possible but 1) you'll have to set a modeline and 2) have usually to spend 3 to 4 hrs trying to convince your graphics card to use it (was always different in my case depending on the graphics card, cable (vga, dvi, hdmi) and monitor used.
Thank you for your reply, ljb643. My monitor is a CRT, thanks God. I've just found Rev.3 of the same HOWTO you mentioned, which I had from a very old version of Slackware. The reason behind my post is the tiny fonts used nowadays in GUIs (and in the text console too as I could see when installing slack 14), which render them almost unintelligible for even people with normal vision. So, my usual remedy has been to diminish the resolution and cope with a virtual screen.
By the way, is there a utility that queries the monitor and dumps its data, such as dot clock frequency, max horizontal scan frequency et cetera?
EDIT: thank you guys for your posts.
@dugan: xvidtune gets a 'Video modes are not settable on this chip' message. My video adapter is a cheep one.
Most CRTs don't have EDID data available. It has to be taken from the manual associated with the CRT.
The only dot frequency available otherwise is taken from the video card. I believe what the Xserver tries to do is cross match the EDID data against the video card data and come up with the appropriate resolutions. When that fails it falls back to a default value such as 640x480 or VGA (depending on what the video card supports).
When the EDID data IS available, the /var/log/Xorg... log files will list what modes are available.
This monitor is Philips 107ESI (maybe 107ES1) although Xorg.0.log lists it as 107E5. It has EDID data available (I lack the manual). From Xorg.0.log:
Supported detailed timing:
[ 63.352] (II) VESA(0): clock: 25.2 MHz Image Size: 306 x 230 mm
[ 63.352] (II) VESA(0): h_active: 640 h_sync: 656 h_sync_end 752 h_blank_end 800 h_border: 0
[ 63.352] (II) VESA(0): v_active: 350 v_sync: 387 v_sync_end 389 v_blanking: 449 v_border: 0
[ 63.352] (II) VESA(0): Serial No: BZ 314405
[ 63.352] (II) VESA(0): Monitor name: PHILIPS 107E5
[ 63.352] (II) VESA(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 71 kHz, PixClock max 115 MHz
I guess the numbers given after 'Monitor name' are monitor data whereas those given before are the card data. However, assuming both 'clock' and 'PixClock' are video dot frequencies, there is a big difference between 25.2 and 115. Perhaps the monitor is much better than the video card despite the fact that the former is much older. Thanks for you post.