I have an old Dell PowerEdge SC1420, which ceased to be a server or to have any form of RAID years ago, when I inherited it. Over the years, I've run many releases of Fedora on it, one or two of CentOS, and I disremember what all else.
Some OSs figure out my HP w2207h monitor on contact, even from behind the KVM switch where I normally keep the SC1420; the last few Fedora releases have been good about that, iirc.
Some OSs don't find out how to display anything while behind the switch, but do if I shut everything down and connect the Dell directly and alone to the peripherals.
Some OSs never get it; I have had to tinker endlessly with xorg.conf a/o grub.conf.
But now F21 doesn't get it, and I can't seem to find a file that will let me tell it there is such a thing as a 27" 1680x1050 terminal. (The only plausible candidates so far open with DO NOT EDIT THIS FILE, and a reference to the other files that set them; but I'm drawing a blank about any way to reset the setting files.)
I can ssh into it, and have been updating it regularly; a few days ago it even accepted a fedup (nonproduct).
Also, for a little while today, I had a Gnome3 display; I managed to open a Mate-terminal; but before I could get to a panel, much less a workspace switcher (one of my must-haves), it suddenly jumped into a display that looked like a few lines torn from the normal boot messages.
I couldn't faze that, and finally hit Ctrl-Alt-Del. That got me to a normal looking boot, except for one "FAILED," which went by too fast to read. Then, for a little while, it went back to the Gnome3 screen, in which I had begun adding and removing apps.
It didn't want to start yumex as root *nor* as user; so I told it "yum remove evolution," thinking it would keep the data-server, or whatever that thing is that stays when I remove Evolution with Yumex. It didn't, and chaos ensued -- till it hit the abominable error message from the monitor, saying "Input out of range."
Clue, please?
On 12/26/2014 07:52 AM, Beartooth wrote:
I have an old Dell PowerEdge SC1420, which ceased to be a server or to have any form of RAID years ago, when I inherited it. Over the years, I've run many releases of Fedora on it, one or two of CentOS, and I disremember what all else.
Some OSs figure out my HP w2207h monitor on contact, even from behind the KVM switch where I normally keep the SC1420; the last few Fedora releases have been good about that, iirc.
Some OSs don't find out how to display anything while behind the switch, but do if I shut everything down and connect the Dell directly and alone to the peripherals.
Some OSs never get it; I have had to tinker endlessly with xorg.conf a/o grub.conf.
But now F21 doesn't get it, and I can't seem to find a file that will let me tell it there is such a thing as a 27" 1680x1050 terminal. (The only plausible candidates so far open with DO NOT EDIT THIS FILE, and a reference to the other files that set them; but I'm drawing a blank about any way to reset the setting files.)
I can ssh into it, and have been updating it regularly; a few days ago it even accepted a fedup (nonproduct).
Also, for a little while today, I had a Gnome3 display; I managed to open a Mate-terminal; but before I could get to a panel, much less a workspace switcher (one of my must-haves), it suddenly jumped into a display that looked like a few lines torn from the normal boot messages.
I couldn't faze that, and finally hit Ctrl-Alt-Del. That got me to a normal looking boot, except for one "FAILED," which went by too fast to read. Then, for a little while, it went back to the Gnome3 screen, in which I had begun adding and removing apps.
It didn't want to start yumex as root *nor* as user; so I told it "yum remove evolution," thinking it would keep the data-server, or whatever that thing is that stays when I remove Evolution with Yumex. It didn't, and chaos ensued -- till it hit the abominable error message from the monitor, saying "Input out of range."
Clue, please?
To get F21 to recognize your monitor you could put a file with the same monitor device sections that you normally put in xorg.conf into /etc/X11/xorg.conf.d. That directory is where xorg reads it configuration files from these days. You may still have to put the mode statements in there to get the right resolutions for your monitor. I'm not sure if the man entry on xorg.conf still has details on how to specify the information, its been quite some time since I've had to play around with those.
regards, Steve
On Fri, 26 Dec 2014 09:15:24 +1100, Stephen Morris wrote:
On 12/26/2014 07:52 AM, Beartooth wrote:
[....]
But now F21 doesn't get it, and I can't seem to find a file that will let me tell it there is such a thing as a 27" 1680x1050 terminal. (The only plausible candidates so far open with DO NOT EDIT THIS FILE, and a reference to the other files that set them; but I'm drawing a blank about any way to reset the setting files.)
I can ssh into it, and have been updating it regularly; a few days ago it even accepted a fedup (nonproduct).
[....]
It didn't want to start yumex as root *nor* as user; so I told it "yum remove evolution," thinking it would keep the data-server, or whatever that thing is that stays when I remove Evolution with Yumex. It didn't, and chaos ensued -- till it hit the abominable error message from the monitor, saying "Input out of range."
Clue, please?
To get F21 to recognize your monitor you could put a file with the same monitor device sections that you normally put in xorg.conf into /etc/X11/xorg.conf.d. That directory is where xorg reads it configuration files from these days.
That file does exist (to my surprise; dunno how I missed it). But it contains only a config file for the keyboard. There isn't any for the monitor at all.
If one existed, I could use it as a template for the format, just adding my "1680x1050" in its field, and anything else obvious elsewhere.
But I remember only that the monitor file (or files; sometimes there was one that demanded "Monitor0," apart from the one with the numbers.
You may still have to put the mode statements in there to get the right resolutions for your monitor. I'm not sure if the man entry on xorg.conf still has details on how to specify the information, its been quite some time since I've had to play around with those.
I didn't know man pages could exist for names as well as commands. I'll go study that. Many many thanks!
Stephen Morris:
To get F21 to recognize your monitor you could put a file with the same monitor device sections that you normally put in xorg.conf into /etc/X11/xorg.conf.d. That directory is where xorg reads it configuration files from these days.
Beartooth:
That file does exist (to my surprise; dunno how I missed it). But it contains only a config file for the keyboard. There isn't any for the monitor at all.
As I understand it, you fill that directory with whatever configuration files you want, and it'll go through all of them. Rather than have one xorg.conf file that did everything, you now have a file for your keyboard (if needed), another file for your screen (if needed), etc.
So, whatever you used to put into xorg.conf to customise your computer, now put it into a file in that directory.
On 12/28/2014 06:21 AM, Beartooth wrote:
On Fri, 26 Dec 2014 09:15:24 +1100, Stephen Morris wrote:
On 12/26/2014 07:52 AM, Beartooth wrote:
[....]
But now F21 doesn't get it, and I can't seem to find a file that will let me tell it there is such a thing as a 27" 1680x1050 terminal. (The only plausible candidates so far open with DO NOT EDIT THIS FILE, and a reference to the other files that set them; but I'm drawing a blank about any way to reset the setting files.)
I can ssh into it, and have been updating it regularly; a few days ago it even accepted a fedup (nonproduct).
[....]
It didn't want to start yumex as root *nor* as user; so I told it "yum remove evolution," thinking it would keep the data-server, or whatever that thing is that stays when I remove Evolution with Yumex. It didn't, and chaos ensued -- till it hit the abominable error message from the monitor, saying "Input out of range."
Clue, please?
To get F21 to recognize your monitor you could put a file with the same monitor device sections that you normally put in xorg.conf into /etc/X11/xorg.conf.d. That directory is where xorg reads it configuration files from these days.
That file does exist (to my surprise; dunno how I missed it). But it contains only a config file for the keyboard. There isn't any for the monitor at all.
If one existed, I could use it as a template for the format, just adding my "1680x1050" in its field, and anything else obvious elsewhere.
But I remember only that the monitor file (or files; sometimes there was one that demanded "Monitor0," apart from the one with the numbers.
You may still have to put the mode statements in there to get the right resolutions for your monitor. I'm not sure if the man entry on xorg.conf still has details on how to specify the information, its been quite some time since I've had to play around with those.
I didn't know man pages could exist for names as well as commands. I'll go study that. Many many thanks!
I've attached an old xorg.conf file of mine. If you take the "Screen", "Monitor" and possibly "ServerLayout" from that file and put them in separate files or a single file in /etc/X11/xorg.conf.d xorg will read those and configure itself accordingly. You will have the change the horizsync and vertrefresh parameters to values for your monitor.
regards, Steve
On Mon, 29 Dec 2014 07:04:51 +1100, Stephen Morris wrote: [....]
I've attached an old xorg.conf file of mine. If you take the "Screen", "Monitor" and possibly "ServerLayout" from that file and put them in separate files or a single file in /etc/X11/xorg.conf.d xorg will read those and configure itself accordingly. You will have the change the horizsync and vertrefresh parameters to values for your monitor.
# nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 319.23 (buildmeister@swio-display-x86-rhel47-11) Thu May 16 20:17:21 PDT 2013
Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" EndSection
Section "Files" EndSection
Section "Monitor" Identifier "Monitor0" VendorName "Samsung" ModelName "SyncMaster S20B300" HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option "DPMS" EndSection
Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection
Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 EndSubSection EndSection
[....]
I copied all that into /etc/X11/xorg.conf.d, and commented out most of it. Then I altered "Samsung" to "HP," and "SyncMaster S20B300" to "w2207h" and rebooted. That didn't suffice, even though I know that Fedora's list of monitors has in fact included mine for several years.
So I'll start tinkering with the rest of the entries in that section, starting with 1680x1050 screen resolution, and going on if necessary from there. Many many thanks!
-
Beartooth -
Stephen Morris -
Tim