Red Hat Bugzilla – Bug 3530
CD-ROM Problems while installing Red Hat Linux 6.0
Last modified: 2008-05-01 11:37:50 EDT
(Please note, the selection of the "bootpc" component is
merely a guess, since I could not identify for certain which
component was considered the boot disk)
In order to communicate my problem, I will first detail the
procedure that I used in order to get my CD-ROM drive to
work during the installation of Red Hat Linux 5.2.
RH 5.2 Procedure (SUCCESS):
I used the boot disk which I made from boot.img on the
CD-ROM. To start the installer, I typed hdb=cdrom. When the
installation came to the select CD-ROM prompt, I selected
the Soundblaster/Panasonic driver, and allowed the installer
to autoprobe for several minutes. After doing so, the CD-ROM
drive was identified and the installation proceeded without
Recently, I acquired a copy of Red Hat Linux 6.0. I made a
boot disk from the file boot.img on the CD-ROM. When I used
the boot disk, I tried two different procedures to get my
CD-ROM to work. Neither was successful.
RH 6.0 Procedure 1 (FAILURE):
I used the boot disk and simply pressed enter at the
first screen to start the installer. I selected the
Soundblaster/Panasonic CD-ROM driver. It autoprobed for
several minutes and then said that it could not find a
CD-ROM drive attached to my computer.
RH 6.0 Procedure 2 (FAILURE):
I used the boot disk and typed "linux hdb=cdrom" to
start the installation. When I reached the CD-ROM step, the
installer said that it could NOT find an ATAPI CD-ROM drive
attached to my computer, and it did not allow me to procede
to select the Soundblaster/Panasonic driver that I used when
installing Red Hat Linux 5.2.
I also try to install RedHat 6.0 from my SCSI CD-ROM. I have made a
boot floppy from 'boot.img' (DOS-command 'rawrite -f
e:\image\boot.img' -d a:'). The installation-program is unable to
mount my CD-ROM (0 scsi devices found), and also it is unable to set
up adaper 'aha152x'. My CD-ROM is a Toshiba XM-5201.
My CD-ROM works fine under my current Linux Slakware installation, and
also under Windows95.
This issue is resolved in the current installer.