Description of problem: Trying to install on a Dual Xeon workstation with SATA hard disk connected to the onboard ICH5 controller fails because the install kernel doesn't detect the hard disk. Version-Release number of selected component (if applicable): How reproducible: Always, and also other distributions are suffering from that (e.g. FC3). Steps to Reproduce: 1. Boot from CD1 2. System shows that there are no hard disks detected, even with a SATA disk connected to the boad. Actual results: Unable to install RHEL 4 beta 2 on that system. Expected results: SATA disks work fine. Additional info: Problem seems to be limited to x86_64 architecture, trying out e.g. a Fedora Core 3 for i386 doesn't show it while FC3 for x86_64 shows it. Problem seems to be fixed in 2.6.10. At least an installation on a normal IDE disk was able to detect the SATA drive after installing kernel 2.6.10 from kernel.org.
Please attach the output of running "sysreport" as an initial step in the investigation...thanks!
Created attachment 110791 [details] Sysreport for 2GB RAM (this config is working)
Created attachment 110792 [details] Sysreport for 4GB RAM (this config is NOT working)
Ok, I installed RH4 Public Beta 2 on a normal IDE disk to get the sysreport information. And I found out one amazing thing: If the system is equipped with 2 GB RAM then it works, the SATA disk is recognized and working. If the system is equipped with 4 GB RAM then it does NOT work, the SATA disk is not recognized. So I uploaded 2 sysreports, one for the configuration with 4 GB and one for the configuration with 2 GB. My next step will be downgrading the BIOS to earlier versins that don't do remapping of the memory between 3 and 4 GB. That's one major difference I think, if I use 2 GB there is no remapping happening, if I use 4 GB BIOS is remapping some parts of the memory.
Latest development in this problem: I switched back to an earlier BIOS release and the problem disappeared with 4 GB, even with memory remapping enabled. As a result of this I do 2 things I lower the Severity to "normal" and on the other hand I'll try out what changes were applied to the BIOS.
oops... last sentence should be "try to find out what changes were applied to the BIOS". :-)
*** This bug has been marked as a duplicate of 138405 ***
If I try to see bug 138405 I get the following message: You are not authorized to access bug #138405. Nice :-(
Rainer, I don't know if I can give you access to bug 138405 or not. I can tell you that it was resolved as "CURRENTRELEASE", implying that the newly released RHEL4 should resolve the problem you are seeing. Please attempt to recreate the problem w/ the current RHEL4 release, and reopen this bug if the problem still occurs.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.