SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just installed suse 10.1, and what a step back from 9.1 the monitor configuration options are: I can't add custom resolutions in yast anymore, and I can't even choose refresh rates significantly below the maximum for most resolutions.
Anyone have any idea if copying parts from my old xfree86 config file to my new xorg config file would be safe?
The lines for 1024x768x85hz in the two files look the same to me, does that mean it would be okay to replace a section or two from the new file with that of the old one?
I tried replacing the modes and screen sections in the new file with that of the old one, that resulted in x11 not starting, then I appended the modes section of the old file to the new one and removed all duplicate lines, that worked, but for some reason my monitor does not recognize the display modes as the same ones as before.
You could use the "gtf" program to create a custom modeline.
gtf 960 720 78 -x
Also the krandrtray program will allow you to switch the resolution and refresh rate on the fly.
Also read through the /var/log/xorg.0.log file. Check if there is a problem at that resolution & refresh rate when X starts up.
You could use the "gtf" program to create a custom modeline.
gtf 960 720 78 -x
Thanks, for me that will be very useful. However, for most people, setting resolutions manually would mean calculating maximum refresh rates and risking damaging the monitor if they accidentally exceed one, compared to suse 9.1 automatically adding options for the maximum refresh rate for any and also for a refresh rate just a little below it.
The custom resolution options in suse 9 were something that really impressed me about linux, that's why I find the removal of them so absurd.
Quote:
Originally Posted by liaty
Have you tried setting up with xorgconfig?
I have tried the xfree86 version of it, it seemed to only be able to generate an extremely basic configuration.
I used the values that you gave as having used in the past. You could use conservative values. I think that for LCD monitors a refresh rate of 56 HZ is pretty standard. Any multisync monitor should be able to handle 60HZ at a minimum.
For the most part you don't need to worry if you set the refresh rate too high. Most monitors that are fairly modern won't try to sync if it's outside of what they support (usually the OSD will show a message to the effect of "out of sync range" or the screen just stays black). Overdriving the refresh rate and causing damage is more of an issue with older monitors. Especially with fixed frequency ones. Speaking of, it's very critical to accurately know exactly what the sync related specs for fixed frequency monitors are.
However, with all of that being said, it's always better to try to error on the side of caution. So it should be avoided, where ever possible, to never try to use sync frequency beyond what the monitor is capable of. Also, perhaps there is a slim chance that the monitor isn't perfect and may try to display at refresh rate that isn't very easy on it. So the best thing to do is find out what your monitor's specs are and follow them. I know that sometimes this isn't an option though (like you got a monitor at a garage sale or it's a hand-me-down, and you don't have the manual, and the manufacturer is long gone as is any vestige of information on the internet about it. Ran into this delimma with mine in fact. At first thought I could only get 75Hz vertrefresh, but later was able to coerce it into getting 85Hz). If that's the case, then you've got two choices -- take your chances and carefully expirement, or stick to a conservative setting and possible not getting optimal viewing. If your monitor doesn't have such protection built in, then it will damage it if it's overdriven. It's just that it seems that it mostly only older monitors that don't have this, but one never knows for sure if there isn't possible even newer ones that do not have such protection or that could have faults to where the protection doesn't work as it should in theory.
I just mention that to try to put the delimma into perspective. Alot of the docs (how-tos, tutorial etc.) always warn about overdriving the monitor. It's good that they do. They're trying to be thorough and make it clear of what one may be getting themselve's into, or at least make it clear of some important things that a person should keep in mind. I think alot them print that because alot of those docs are old where it was more of likelyhood that a user may happen to have a monitor that is susceptable to damaging itself (like I said earlier, most fairly modern monitors won't allow themselve's to operate outside their specs. Can't say all for certain though. I don't think anyone can.). I also believe they warn to error on the side of caution and that they're employing the good philosophy of "an ounce of caution/prevention is worth a pound of cure".
Now when it comes to setting modelines, that really gets into the deep down nitty gritty where you'll be hard pressed to find all the specs you need (if your manual goes that in depth about the monitor's specs, then kudos to them. I wish more hardware manufacturers for everything were like that). I would avoid messing with that particular setting unless of course you know what you're doing and/or you don't really have any choice but to take things there (i.e. how X can be a PITA to get it to use optimal resolution and refresh rate that you know you can use for a fact. Sometimes it will all work like it should without much fuss, but sometimes it takes hacking the XF86Config-4 or xorg.conf to get it to behave like you want). I've found that this tends to come down to the combination of xserver/x-video-driver and monitor. Some combos are a PITA.
Like mentioned, if in doubt or you want to play it safe, then go with conservative setting if you're forced to have to guess. You lessenned likelyhood that you'll possible damage the monitor at the cost of not necessarily setting it to it's fullest display potential. The user is in the driver's seat and it's really a judgement call on their part as to how they want to weigh it all out.
So if anyone damages their monitor. Don't come crying to me. We all make our own bed and make our own choices and judgement calls. Just saying that to make it clear that this is only my adviced based upon my own personal experiences and opinion and that if someone does, for some reason, fry their monitor, then it's not my fault since I made sure to give a warning in spite of most people are already aware of the risks to begin with.
In other words, I'm saying that chances are probably pretty good that you don't have to worry if your monitor isn't real old or using some strange non-standard technology, but if a person makes their own call about how cautious they want to be and does anything less cautious at their own risk. I just wanted to be clear about that since I would hate for someone to have troubles by misunderstanding what I'm trying to say. So if in doubt, play it safe.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Where the %@#$ did my resolution options go?
