From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Description of problem: when installing, system automatically goes to text mode. however, after installation and the system reboots, linux starts up perfectly fine until it tries to start xorg, an error that the display cannot be initialised will be shown. i suspect it may be due to the radeon x700 mobility card on my acer 5502 laptop. Version-Release number of selected component (if applicable): rpm-4.1-1.06 How reproducible: Always Steps to Reproduce: 1.install 2.reboot 3.unable to initialise display Actual Results: system goes into mesh Expected Results: xorg should have started normally Additional info: system stats can be found at: http://www.acer.com.sg/products/aspire5500/psp_aspire5500.asp
Thanks for the report. (In reply to comment #0) > From Bugzilla Helper: > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) > > Description of problem: > when installing, system automatically goes to text mode. however, after installation and the system reboots, linux starts up perfectly fine until it tries to start xorg, an error that the display cannot be initialised will be shown. i suspect it may be due to the radeon x700 mobility card on my acer 5502 laptop. You'll need to do a text mode installation and configure X afterwards. I believe that hardware is incompatible with the X included in FC4 by default. Try updating the whole system after text mode installation, and then running "system-config-display --reconfig" > Version-Release number of selected component (if applicable): > rpm-4.1-1.06 The version of the rpm binary isn't useful information.. Rather that field is intended to tell us the version of the component you're filing the bug against, ie: the xorg-x11 version ;o) > How reproducible: > Always > > Steps to Reproduce: > 1.install > 2.reboot > 3.unable to initialise display We don't have such hardware, so it's not possible to reproduce directly. Do the steps suggested above and provide feedback, and hopefully things will work afterward for you. If not, try the "vesa" driver. After performing the text mode install, etc. if you still have a problem, please attach your X server log and config file to the report as individual uncompressed file attachments when you update the report. Thanks in advance.
If you could please review comment #1, and try my previous suggestions, and respond with your results, that would assist in further diagnosing this problem. Currently there is insufficient information to proceed. Thanks in advance.
Closing bug due to lack of information, and lack of feedback/response. If the issue is still present/relevent, please respond to the above engineering queries and reopen and we will re-review the issue. Setting status to "CANTFIX" (lack of response)