Hey Una:
Let me start by saying that,. when I first installed Linux on my previous computer, I had the exact same problem (except for the LCD screen thing). I didn’t know what to do about it, and I couldn’t find a good answer as to how to fix it, and it frustrated the fuck out of me, to the point where I nearly gave up on installing Linux. In other words, I know where you’re coming from.
Nowadays, I don’t use anything else. The difference is that I had to teach myself what was broken and how to fix it. I agree, however, that most people don’t like being presented with problems to solve as a part of their user experience. This is definitely an area where Linux needs to improve if it wishes to be used more broadly.
(technical dissection of your problem follows):
The big problem with X configuration, specifically, is that most auto-configuration tools (which 99% of even very technical people use, because manual configuration is about as much fun as choking on glass slivers) assume that the display should default to the lowest supported resolution. Since you say you can change resolutions, whatever tool Red Hat uses for configuration most likely behaves in exactly this way. What you want to do is manually change a few lines in one file, after which your problem should go away.
The main X configuration file, XF86Config, might be located in one of several places, but on a modern system it’s probably under /etc/X11 . use any text editor to find the following string:
Section "Screen"
That’s a single space between the two words, with quotes included.
What you will see beneath this text are (probably) several “Display” subsections with a bunch of resolutions listed underneath them. When X starts up, it tries these resolutions in the order listed; if they are listed in ascending order, X will always start in the lowest supported resolution which isn’t what you (or any other person) wants.
Simply edit every instance of these resolution lines to try supported resolutions in descending order (being sure to back the file up first , just in case), and your problem should go away. To test it, you don’t have to reboot, or even shut X down - just type the following from an xterm to reset the server:
su -c "kill -HUP $(pidof X)"
This will require the root password to operate, but will not leave you running as root.
(Yes, I deliberately used on of those inscrutable command lines. This is to prove a point - if you like the flexibility implied by something like that, you’ll like Linux. If you find it painful to behold, you probaly will feel likewise about Linux.)