Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
My system was working fine. Then, I upgraded from Fedora 9 to 13. Now the system sets a scan range outside of what the monitor can handle when it hibernates. I copied /etc/X11/xorg.conf from the Fedora 9 installation. I added a monitor section with horizontal and vertical frequency ranges. Xorg restarts faster, but the problem is unchanged.
CTRL-ALT-BS doesn't recover the system. CTRL-ALT-F2 doesn't give me a viewable text screen. I can ssh in and "killall Xorg".
The monitor is an 11 year old Vivitron 17 CRT.
I'm using the on board video.
I'm using version: X.Org X Server 1.8.2
OS: Fedora 13 with KDE desktop
To my experience most of the times I've seen "out of range" warnings have been when the monitor is simply not receiving any video signal at all.
The default restart combination in X has been changed to alt+sysreq+k, because the previous combination was considered too easy to accidentally hit on some keyboard configurations. It's possible to set it back if you want, but the details may vary across distros. Here's a page about it in F11.
This is not very helpful, but I used to have a similar problem years ago, I think I was using Fedora 8. If I remember correctly, I think I upgraded my graphics card, and the problem started... You say it only comes up when it hibernates? What about when the screensaver turns on?
When the screen saver comes on, the screen just goes blank. That's the screen saver that set. It's after the system tries to hibernate the monitor that the monitor complains the signal is out of range.
KDE on Fedora 13 doesn't appear to have any bindings set for reset X server. It did let me set CTRL+ALT+BS, but not CTRL+ALT+SysReq. I haven't tested it yet because I have to leave the system alone for awhile.
chvt complains that it can get a file descriptor for the console if I'm not root. I don't want to give an account unpassworded sudo. I guess I could train myself to CTRL+ALT+F2 before I leave the system. It may be easier to find an other distro or go back to Fedora 9.
I'm not deliberately hibernating the system. It hibernates after not being used for a while. Unlike a lap top, it's only hibernating the monitor. It should just drop the sync pulses, but it appears to be changing the timing instead.
Hibernation already requires root access, so if you just wrap the script, chvt will be executed by root. And even if it were not so, you could give unpassworded sudo for this specific command, not for all commands.