Description of problem: intallation stops because of disk read errors (dma) on Abit KN8 SLI motherboard Version-Release number of selected component (if applicable): FC5 How reproducible: Happens every time. I don't have these problems with a custom kernel that I made for version 2.6.15.1. It seems that the anaconda kernel version is not configured right for my nforce nvidia motherboard or not recent enough. I replaced the vmlinuz image on the FC5 installation disk but ananconda would not recognize the disk in a susequent installation try. I need to know how to just replace the anaconda kernel and its cpio initrd with my working kernel and how to get it recognized. Steps to Reproduce: 1.try to install FC5 from a burned CD of the iso images 2. 3. Actual results: disk errors Expected results: should read my disks ok. Additional info:
Created attachment 129027 [details] kernel config file that works; unpatched kernel from kernel org
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
(this is a mass-close to kernel bugs in NEEDINFO state) As indicated previously there has been no update on the progress of this bug therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue still occurs for you and I will try to assist in its resolution. Thank you for taking the time to report the initial bug. If you believe that this bug was closed in error, please feel free to reopen this bug.