From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4 Description of problem: The monitor in question is a Samsung SyncMaster model 213T which was recognized by anaconda of FC3 without problems. FC4 doesn't know it. Graphics card is Matrox G550 correctly identified by anaconda and the monitor is attached to the analogue port. When it switches to whatever kind of monitor it believes will work the display becomes blurred and is completely unreadable. Booting with linux-lowres doesn't help. It looks like the ability to handle this monitor has been dropped with FC4. Is there a way I can run the starter system of FC3 to install FC4? Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Boot DVD with FC4 using default options. 2. 3. Actual Results: Anaconda comes to the point where it asks you to accept or decline mediacheck and after a short while display becomes blurred as mentioned above. Expected Results: Normal installation procedure starting with chosing language etc. Additional info:
The file /usr/share/hwdata/MonitorsDB in the package hwdata-0.158.1-1 for FC4 has the following line: Samsung; Samsung SyncMaster 213T/CX210T; SAMOO91; 30-81; 56-75; 1 Hence, if you can install FC4 on this machine using a different monitor, there's a good chance it will still work when you put the 213T back.
Does booting with "linux nofb" help?
No, "linux nofb" doesn't help. Still blurred and unreadable display.
Does X work after installation?
Installation is impossible.
What if you do a text install?
I have never done that, so I don't know what to do. Can I find a step by step documentation on the process somewhere?
It's basically the same as a graphical install but without using the mouse. Insert CD #1. Type "linux text" and press Enter. Do your normal install but without using a mouse.
OK, did text install yesterday and it went smouth until I was supposed to reboot, because then the ugly unreadable screen returned. This situation is even worse because now I have a Fedora Core 4 system that I cannot use. It looks like the hardware data in /usr/share/hwdata/MonitorsDB is incorrect.
I think it's a dup of bug #163331. Your problem should be fixed in 6.8.2-45. Can you give it a try?
I have tried to install 6.8.2-45 but it's a horrible complicated update with more than 30 rpms.
It may be appropriate to use yum: yum --enable=development -y update xorg-x11
*** This bug has been marked as a duplicate of 163331 ***