I am new to linux and recently installed a fresh copy of Mandrake 10.1. I am using a Dell 1703FP monitor that has a native resolution of 1280x1024, with a refresh rate of 60kHz. In my new install I can't view anything on the GUI because it has set the resolution to 800x600 with a refresh rate of 70kHz. Is there any command that I can use to set the default resolution??


Thanks in advance for any advice that you may be able to offer.

-Peter

I'm also having the exact same problem with my Dell monitor

Go into the Mandrake Control Panel, and select "Screen Resolution" in the hardware section.

You should be able to adjust to your heart's content.

If that doesn't work (and Mandrake for some reason sometimes does fail to update files after it appears it HAS done so...) you can edit /etc/X11/XF86Config by hand. You'll se a "Section 'Monitor'" that has your current settings first thing in it. It's easy to change. Back up the file first in case you make some horrible mistake, or else (simpler) just comment out the current lines and rewrite them the way they should be.

You will have to do that editing as root, of course.

But chances are the Control Panel operation will work OK.

The one problem with this is that they don't know what to do at the "blank" screen that they currently have...

Do this...

At the "blank" screen press [CTRL][ALT][F1]

This will put you at a text screen and your monitor should wake up again.

Log in as root.

At the prompt type

service dm stop

Now type

XFDrake

You will get a text based configuration screen that will permit you to choose a different monitor setting.

Do so and test it.

If you do not see anything during the test just wait. After 12 seconds it will return to text mode.

Once you see the rainbow test screen, click OK with the mouse and SAVE the changes.

Now restart the DM service with

service dm start

You're done!

Sorry, I was assuming they got a display but it was just a bad 800x600 one but usable. Thanks for the more helpful version!

First, thanks to both of you for your willingness to help.

I was able to login as root and stop the display service but when I type "XFDrake" it tells me that the command cannot be found. Any ideas?

I should also add that I CAN see something in the GUI but it isn't usable at all. It seems like whatever settings that it's defaulting to are outside of the acceptable range for the monitor (I've tried both a CRT and LCD at this point). I've seen something like this before when the refresh rate is set too high. You can see something (such as a mouse cursor) that appears multiple times accross the screen but there's nothing that is visibly usable.

Thanks again!

-Pete

XFdrake instead.

Or hit XF[TAB] and Linux will display anything which matches.

Once you have it running make sure you select an LCD or "flat panel" display which will automatically use 60hz timings.

My setup (Mdk 10.1 OE) has XFdrake (spelled exactly like that) in /usr/sbin, but /usr/sbin is not in the path, so that's probably why no response to that command.

So yet another alternative is to specify /usr/sbin/XFdrake as the command (full path included).

Still no luck! I was able to run Xdrake but none of the monitor/resolution combonations would work for me. I even tried a custom setting to 1280X1024 @ 60kHz and still get the indistinguishable screen. Any other ideas - other than not using Dell monitors?

It's crucial to some monitors, like mine, that you put the EXACT refresh rates. For example, you can't just put 100 Hz. Some monitors get close to 100 Hz but are actually 99.6 Hz. You have to look at your manual documentation. Sometimes the menu on the monitor will display your exact refresh rates.

There's always POWERSTRIP....

Manderino, first of all I'm very sorry you're having so much trouble with an extremely necessary function for your computer system. First time something like this happened to me, I felt sweaty and convinced I'd never be able to use my system again at least without a complete reinstall.

But I just looked in my Mandrake Control panel and under "Dell" under "Monitors," it lists both a 1703FP Analog and a 1703FP Digital. It's unlikely but possible you have the newer digital connector on yours. It's a 24-in connector that looks unlike anything else on earth. Your computer has to be fairly new to have a port to plug it into.

If you DO have a digital connection, try selecting that machine. If you (as probable) have the analog version, try that selection.

Now since you are unable to see the control panel properly and click where you need to, I will copy the settings for both of these, if I can, and then report them here. It will take a few minutes, especially if I lose control of my display in the process. But I'll get back, I promise.

So stay tuned.

OK, here's what I found out by changing "my" monitor to yours:

It makes the /etc/X11/XF86Config file read this way:

Section "Monitor:
Identifier "monitor1"
VendorName "Dell"
ModelName "Dell 1703FP(Analog)"
HorizSync 30.0-80.0
VertRefresh 56.0-76.0

For the Digital version, it's exactly the same except for the word "Digital" replacing "Analog" in the parentheses.

Just for kicks, I tried using my monitor with the "Digital" setting for yours and it tested just fine. Mine has digital
capability but my old (1999! ANCIENT!) computer doesn't have a digital output, so I use the analog connector.

Mine's a Princeton VL1916 and I love it! It's so bright I have to turn the brightness down to 20% or less for text work.

For Graphics 50% (factory default) is plenty bright.

Hope you can get yours working just right now.

(Edited for typing too fast.)

I brought the system home from work becasue I still couldn't get it to work with everything that you all thoroughly described. By the way, thanks again for helping me through this. It still will not work on my home flat panel, or both the Dell flat panel and Dell CRT at work. This is a Dell system with the Intel 865 chipset (Intel Extreme Graphics 2). The system does detect the correct type of video card but could there be something wrong with that. What about the GUI iteself??

Thanks again,
Peter