Bug 8355

Summary:	Other CDrom brain damage.
Product:	[Retired] Red Hat Linux	Reporter:	Stephen John Smoogen <smooge>
Component:	installer	Assignee:	Erik Troan <ewt>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	jturner
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-02-04 17:40:22 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 Stephen John Smoogen 2000-01-11 00:28:58 UTC

486 DX66
16 megs of Ram
AHA 1540 SCSI
  100 meg scsi ID 0
  800 meg scsi ID 3
MAD16 2xcdrom (panasonic)
3c509B

Bug 2:
System goes into a loop if wrong cdrom is selected on this screen. I
selected a MAD16 and let it autoprobe. Next screen shown was that no Red
Hat Cdrom could be found <RETRY> <BACK>. Retry of course failed as it
wasnt a device that was there. Going back took me to the <LOCAL CDROM>
<HARDRIVE> screen. However selecting <OTHER> brought me back to the "No
Red Hat CDROM had been found." I am guessing some variables are not
being re-initialized correctly.

Only cdrom which does NOT have this problem is the SoundBlaster one.

Comment 1 Stephen John Smoogen 2000-01-11 00:42:59 UTC

Damn. Sorry this is for component installer and NOT aboot. Sorry about that.

Comment 2 Jay Turner 2000-02-03 18:35:59 UTC

This appears to be fixed in Beta3 code.  Let us know if it is not.