Bug 85416 - can't install phoebe beta, won't recognize cdrom
can't install phoebe beta, won't recognize cdrom
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-03-01 10:28 EST by Need Real Name
Modified: 2008-01-17 12:49 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-04-22 12:31:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2003-03-01 10:28:00 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030217

Description of problem:
I have tekram DC-390 scsi card with two scsi cdroms on Redhat 8.0 box.  When
booting with floppy syslinux to install phoebe , tmscsim module loads, but
installation process can't recognize Redhat phoebe cd in either drive.  cdrom
drives work in same machine; already have Redhat 8.0 loaded and drives read cd
fine under redhat 8.   I tested cd in other machines and the cd is ok all
machines can read it.  

Version-Release number of selected component (if applicable):
Phoebe release 15 Feb 2003; earlier phoebe release did same thing

How reproducible:

Steps to Reproduce:
1.boot from floppy 
2.load tmscim module
3. Installation stands still system doesn't recognize redhat cd's

Actual Results:  nothing happens

Expected Results:  drives should have loaded second stage install (anaconda)

Additional info:

athlon system xp 1600 512 meg ram, geforce 2 video,tekram scsi, ide hard drive
Comment 1 Jeremy Katz 2003-03-04 16:15:26 EST
Are there any messages on tty4 about recognizing the cdrom?
Comment 2 Michael Fulbright 2003-04-22 12:31:11 EDT
Closing due to inactivity. If you have new information to add please reopen the
issue report.

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