F10 autoconfig correct res & freq, but much overscan

[oryan_dunn]

I've just downloaded the Fedora 10 live cd. After boot, the graphics card is correctly detected (ATI Radeon 9700Pro), the monitor seems to be correctly detected and setup (Proview 19" widescreen, 1440x900 native, using VGA). The resolution is set at the correct 1440x900, and my monitor reports basically the same frequencies as ubuntu (55.4Khz hor, and 59.8Hz ver). However, my monitor cannot auto set so it is a 1:1 pixel map on the screen, and the image is about 20% wider than the monitor and about 5% taller. How do I correct this problem?

I've run
startx -- :2 -configure
and the resultant xorg.conf file looks to be correct, with the correct frequency ranges for my monitor.

Thanks,
Ryan

[oryan_dunn]

Here are some screenshots. Both Ubuntu and Fedora have autoconfigured xorg; no settings adjusted by me.

http://img363.imageshack.us/img363/2096/img2990fm5.th.jpg (http://img363.imageshack.us/my.php?image=img2990fm5.jpg)

http://img363.imageshack.us/img363/8750/img2991mx5.th.jpg (http://img363.imageshack.us/my.php?image=img2991mx5.jpg)

You can see the Fedora screenshot that the resolution is correct and the frequencies are very close to Ubuntu. The left is cut off, up to the firefox icon in the upper left. I have used the auto button on the monitor, but that is as close as it will get.

[jdelisle]

Similar problems here!

I'm using a 9700 pro, with a Samsung 226CW LCD.

Using DVI, works fine. VGA, all sorts of refresh-rate problems. I can't seem to get it to refresh at 60hz, except via DVI.

[oryan_dunn]

This still is quite annoying. The autoconfig in Ubuntu works; the autoconfig in Fedora does not.

[jdelisle]

This still is quite annoying. The autoconfig in Ubuntu works; the autoconfig in Fedora does not.

My solution is VNC from my mac..

Sad, but it works.

[oryan_dunn]

My solution is VNC from my mac..

Sad, but it works.

Well, that "solution" wont work for playing games, not to mention it requires a second computer.

[jdelisle]

Well, that "solution" wont work for playing games, not to mention it requires a second computer.

I guess that's why it's my solution, to my problem.

If you want to contribute to its resolution in a way which may be more meaningful and more broadly useful, why not go ahead and do it instead posting and criticizing my workaround.

Take your time, we'll all wait.

[LBCoder]

What happens when you set it to a lower resolution? Have you tried setting a custom modeline? Are you using VGA or DVI? What driver are you using (vesa or radeon)? Have you tried the other one to see what happens? Please post the contents of your xorg.conf and Xorg.0.log files.

[jdelisle]

What happens when you set it to a lower resolution? Have you tried setting a custom modeline? Are you using VGA or DVI? What driver are you using (vesa or radeon)? Have you tried the other one to see what happens? Please post the contents of your xorg.conf and Xorg.0.log files.

In my case (samsung syncmaster 226cw via VGA, ati 9700) I've tried:
- lower resolutions set via my xorg.conf
- custom modeline generated via gtf 1680 1050 60, added to xorg.conf monitor section

Findings:
- using DVI works fine, all resolutions I've tested work
- VGA results in my LCD popping an error, unsupported mode, try 1680x1050 @ 60hz or something like that.. hard to read, since the screen is going insane

This worked just fine, at all sorts of resolutions, back in F9. The only change was upgrading to F10.


xorg.conf:
# Xorg configuration created by system-config-display

Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"

# keyboard added by rhpxl
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105+inet"
Option "XkbLayout" "us"
EndSection

Section "Monitor"
Identifier "Monitor0"
ModelName "Samsung SyncMaster"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 75.0
Option "dpms" "true"
Modeline "1680x1050_60.00" 147.14 1680 1784 1968 2256 1050 1051 1054 1087 -HSync +Vsync
EndSection

Section "Device"
Identifier "Videocard0"
Driver "radeon"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection


xorg.0.log coming in 5 mins

[oryan_dunn]

I've got an ATI Radeon 9700pro using the "radeon" driver with a VGA cable to a 19" (1440x900) Proview PL926Wbi. I tried manually specifying monitor frequencies in the xorg.conf file, but the frequencies that my monitor reports receiving are well within the correct range. I will post my xorg.0.log when I am able to.

[jdelisle]

GOT IT!

This isn't related to X at all!!

It's that new boot menu thingy, Plymouth. It's the one kicking the system into a graphical mode. Eliminate Plymouth's graphical mode, and boom - everything worked.

I did it by adding nomodeset to my boot prompt. You can do that by pressing "e" at the boot menu to edit your boot strings, and selecting the middle long one, and adding "nomodeset" to the end. You'll get a text-based boot up, and when X started for me, it was perfect.

Hope that helps.

[vallimar]

That's the vesa framebuffer -- it might not be picking the correct setting.
You can try setting "vga=ask" and picking the correct vesa mode and see if that works.
If so, note the hex number and set that for future use, like "vga=0x318" or "vga=0x31b".

Try removing the "rhgb" from the line instead of adding nomodeset. Removing that should
disable attempting to use plymouth. To make changes permament, edit /etc/grub.conf.

[jdelisle]

That's the vesa framebuffer -- it might not be picking the correct setting.
You can try setting "vga=ask" and picking the correct vesa mode and see if that works.
If so, note the hex number and set that for future use, like "vga=0x318" or "vga=0x31b".


Tried that, no difference in results.


Try removing the "rhgb" from the line instead of adding nomodeset. Removing that should
disable attempting to use plymouth. To make changes permament, edit /etc/grub.conf.


Will try that tonight. Putting plymouth in text-mode (via nomodeset) works nicely, and still gives the quasi-graphical boot (animated text bar).

I've tried with no success to find the rhgb manuals, any suggestions? Perhaps I can force a res/refresh rate through it, if I could figure out how to tell it what I require.