Description of problem:
Did standard 32 bit FC2 install on a dual opteron 246 system based on
the Arima HDAMA-SATA (ATO2161) motherboard with 2GB of Memory (4 x
512M DIMMs) with a 40GB IDE boot disk and 2 x 250 GB SATA disks set
up as /home and /home1. Standard install runs fine using the onboard
ATI RageXL with 8MB Memory graphics port. Once installed and set to
come up in run level 5 EVERYTHING WORKS.
First: Used yum to update from local mirror of FC2 update directory
and then reboot. System does not run X and we get a blue screen with
the updates installed that says it can't start the Xserver and that
it can't attach to the 0:0 frame buffer.
Did a complete reinstall and again the stock release works fine. Only
installed/upgraded the kernel using "rpm -ivh kernel-smp-2.6.7-
1.494.2.2.i686.rpm" -- Same problem with X occurs. System booting
into run level 3 with no problems but startx causes a blank screen.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Standard FC2 install
2. run rpm -ivh kernel-smp-2.6.7-1.494.2.2.i686.rpm
3. reboot and select new kernel
4. System can't connect to onboard ATI RageXL graphics port and
Xserver fails to run.
Expected results: Expected the updates to install and run fine
Additional info: Can test this again once the ATI driver or X is
fixed as we will have a similar machine here for another 7 days.
mass update for old bugs:
Is this still a problem in the 2.6.9 based kernel update ?
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.