Bug 78079
Summary: | During startup xcdroast reports the following: Failed to scan the SCSI-bus. Either no permission to access the generic scsi device or now SCSI support enabled in the kernel. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <iraskygazer1> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-11-18 20:16:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2002-11-18 20:08:19 UTC
You have specified to invoke the ide-scsi module, right? On your kernel line in grub.conf (or lilo.conf) you need to have something like the following "hdc=ide-scsi" (without quotes) to tell the kernel to invoke that module. Replace "hdc" with whatever drive designation your combo drive is. Michael, Thanks for the hint about needing the additional startup parameter. I had to add the hdc=ide-scsi to the append line in my syslinux.cfg file on the boot floppy. I checked for the lilo.conf file and it didn't exist. So I checked the syslinux.cfg file on the 2.4.18-14 floppy I've maintained and found the parameter just as you'd suggested. So I simply added the param to my 2.4.18-18.8.0 boot floppy and the x-cdroaster responded fine. So my problem is now fixed. But, I still have a question. Why did the 2.4.18-14 syslinux.cfg file have the hdc=ide-scsi param but the mkbootdisk command didn't pick up this parameter automatically for the upgraded kernel? According to the info file for mkbootdisk the SCSI drivers should be loaded automatically when creating the boot disk. Is this a small gotcha related to an upgrade of the kernel that should be published in big letters as a note to those who may run into the same problem I've encountered. It seems this is just a simple option for the loader but it disables hardware capability when not present in the config file. Just a thought. My problem is now fixed. Note that the boot loader config file is now named syslinux.cfg. Thanks again for the assistance. |