Hide Forgot
+++ This bug was initially created as a clone of Bug #115679 +++ My copy of FC4 is a copy I downloaded on 10/23/05. My hardware platform: Compaq Proliant 850R Dual PPro-200MHz (256K Cache) 128MB RAM Compaq SMART2-SL RAID Controller 3x4.3 GB SCSI in RAID5 Array System has onboard SCSI Controller with nothing attached IDE CD-ROM (Appears to require ide=nodma) Anaconda probes the onbaord video as Cirrus Logic GD543x I've tried two different monitors: OptiQuest Q17 17" CRT NEC MultiSync LCD M7000+ 17" Flat Panel I've tried all of the following commands with both monitors: <enter> at initial load screen linux ide=nodma linux resolution=800x600 linux resolution=640x480 linux resolution=1024x768 linux ide=nodma resolution=800x600 linux ide=nodma resolution=640x480 linux ide=nodma nofb resolution=800x600 linux ide=nodma nofb resolution=640x480 What happens is that on all three of these commands, when anaconda loads, it's the same resolution everytime...which pushes the bottom and right sides out of my monitor, leaving me unable to view things like the buttons. With either monitor, anaconda can probe the video card, but is unable to probe the monitor. With the flat panel hooked up, I am able to have it tell me what resolution it is at. In all the above commands, my flat panel continues to tell me that it is ALWAYS being shown in 640x480@60Hz. The 'resolution' keyword appears to make little difference once anaconda comes up. As a verification of the video card itself, I installed Win2K on this system. Win2K will allow me to choose 640x480, 800x600, 1024x768 (256 Colors), or 1280x1024 (16 colors). So, it appears that the video card should be handling these resolutions just fine.
Does it work better if you boot with 'linux nofb'?
I had nofb in the command line when I tried booting on the last two occasions. I'll go ahead and try nofb as the only option and get back to you.
I have tried linux nofb Same results. The monitor's resolution is 640x480, but the screen that shows up is formatted for a larger resolution and thus, it doesn't display correctly on the screen and is unusable.
I see this problem with FC5test3 on an SGI 330 with an nVidia NV10GL [Quadro] video card hooked up via a DVI-D connection to a Dell 2005FPW monitor running at 1680x1050 native resolution. If I start the installer without specifying a resolution, it dies complaining that the window manager can't open the display (i.e. something like the message in bug 72088). If I specify resolution=1680x1050 when booting, on the other hand, the graphical installer starts up fine, but as with the original reporter it displays at an unusably low resolution (720x400 70Hz according to my monitor). Note that my video card and my monitor have VGA connectors, and if I connect them via a VGA cable instead of a DVI-D cable the graphical installer starts up in 800x600 resolution, which seems like the minimum necessary to navigate its screens. But if I specify resolution=800x600 when booting with the DVI-D cable I get the same "window manager can't open display" error as when I don't specify a resolution. So the problem seems to be specific to the DVI connection.
Please try again with FC6 or FC6 test 2. Lots of work has gone into X configuration and startup for this release.
requested by Jams Antill
This should be fixed in later releases of Fedora.