The installer does not list my scsi disks as installation targets, just my ide disk. Filing as a kernel bug as I assume the issue is due to linux not recognizing the scsi controller. I tried starting the installer with 'linux noacpi', no dice. This is an issue with FC4 x86_64 as well. The machine is an HP xw9300, the motherboard has an integrated ultra 320 scsi controller. bios is updated to latest rev 2.05. SuSE 9.3 (i386) and SuSE 10 beta 4 (x86_64) can both see the scsi disks when I start their installers with noacpi.
can you grab lspci output for that ? (and maybe dmesg too?)
Peter, Jeremy tells me you've got one of these beasts. Any ideas whats up ?
Booting with pci=noacpi fixes it. The machine's MP and ACPI tables don't tell the same interrupt routing story.
Created attachment 125736 [details] output of lspci once booted fc5 test3 x86_64 with pci=noacpi
Created attachment 125737 [details] dmesg once booted fc5 test3 x86_64 with pci=noacpi
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 bug has been mass-closed along with all other bugs that have been in NEEDINFO state for several months. Due to the large volume of inactive bugs in bugzilla, this is the only method we have of cleaning out stale bug reports where the reporter has disappeared. If you can reproduce this bug after installing all the current updates, please reopen this bug. If you are not the reporter, you can add a comment requesting it be reopened, and someone will get to it asap. Thank you.
Still no go both latest FC5 kernels and FC6 kernels require acpi=off in-order to detect all the devices on the PCI-X bridge. - Gilboa
Marking as info provided.
Closing since there was an error in previous mass-close and they remained in NEEDINFO.
Somehow I missed this bug. Still seeing the same in F10, x86_64. Nothing is seen on the PCI-X/PCI-E buses unless I add acpi=off - Gilboa
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.