Bug 8059
Summary: | Installing Tekram DC390 SCSI Controller module | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | gtmanning |
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-01-24 20:54:55 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
gtmanning
1999-12-30 04:09:40 UTC
assigned to kernel This bug seems to have been fixed in the time since 6.0 that it was reported. To answer the questions above. In the current release you would check to see if a kernel module had been loaded with the lsmod command. To see if any scsi objects were seen you can use a cat /proc/scsi/scsi command which will show if the scsi bus sees hard-drives etc in the machine. |