Bug 7651
| Summary: | Unable to upgrade 6.0 installation on DPT SCSI | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | spike |
| Component: | installer | Assignee: | Jay Turner <jturner> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1 | CC: | srevivo |
| 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: | 2000-02-15 00:40:00 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
spike
1999-12-07 13:54:41 UTC
Shall I interpret the silence as a recommendation to switch to Debian or SuSE? This appears to be related to the pcitable problem reported in bug #6463. I've tried to patch this on the boot floppy, but I can't make it detect the card. It's been over a month now, and still no sign of acknowledgement. As far as I can tell, the mechanism for loading modules after booting from an installation floppy is completely and utterly broken. I just hope you guys aren't too busy counting your stock options to read bug reports any more. Never mind. I finally stumbled across a workaround. The bootnet disk for network-based installs works fine. I was able to load the eata module in expert mode, which would not work under any circumstances when I booted from the CD or with the standard boot disk. This module was left off of the boot.img disk because Red Hat was not aware that you could hang a CDROM off of the card (we later found out that you could indeed do this :-)) We created a driver disk at that time so that people could load the driver disk and be able to access their DPT cards. In future releases we will either bundle this module into the boot disk or supply access to this driver disk (this is depending on the space available on the boot disk.) Issue is resolved in latest RawHide. The installer for 6.2 has indeed fixed this problem, but the kernel which gets installed fails to load the module and is thus unable to locate the root filesystem. I managed to restore my old custom kernel with the EATA driver built-in and fix the problem (with a little help from Tom's Root/Boot Disk), but I thought you would like to know about it anyway. |