Bug 25691 - Installation From Floppy Disk Of RedHat Personal Server 7.0
Summary: Installation From Floppy Disk Of RedHat Personal Server 7.0
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: bootpc   
(Show other bugs)
Version: 7.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Elliot Lee
QA Contact:
URL: robypicc@tin.it
Depends On:
TreeView+ depends on / blocked
Reported: 2001-02-02 11:54 UTC by roberto picciol
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-07-16 13:30:43 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description roberto picciol 2001-02-02 11:54:52 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

I can not install Linux RedHat 7.0 with floppy disk, when I use Cd-rom an 
error I see: "Not redhat cd in cdrom .... ", I have Scsi adaptec 2940Au 
and Cd-rom Plextor Scsi. I can install Linux RH 6.2 from floppy disk and 
my plextor work very good. I think an error in Driver for Adaptec 2940.

Reproducible: Always
Steps to Reproduce:
1.Boot from Floppy Disk
2.All Ok
3.When the installation works with Plextor (Scsi adaptec 2940Au) the 
system crash or an error I see: "not cd redhat 7.0 ..."

Actual Results:  I can not install Redhat linux Professional server 7.0.
I will push ctrl-alt-canc.

Expected Results:  I like install Redhat 7.0.

I have:
1) Qdi Advancer 9
2) 4 Hd eide Ibm
3) Scsi 2940Au
4) Cd-rom Plextor 40 max scsi
5) Plextor 12/10/32S Scsi
6) Hp scan jet 5p scsi
7) Zip 250 externa scsi
8) matrox g400 DH Agp
9) sound blaster 64 awe Isa

My computer work very well with Linux RH 6.2.

Comment 1 Elliot Lee 2001-08-08 04:37:14 UTC

I apologize for the unresponsiveness of the previous bootpc packager... 
However, this sounds to me like an installation support request that you need 
to take to Red Hat Support - please talk to them if you are still experiencing 
this problem.

Note You need to log in before you can comment on or make changes to this bug.