Bug 78441

Summary:	boot loader hangs for certain Toshiba models with buggy bioses (int 13) problem
Product:	[Retired] Red Hat Linux	Reporter:	Stephen Mah <steve.mah>
Component:	syslinux	Assignee:	Peter Jones <pjones>
Status:	CLOSED WONTFIX	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-04-19 18:30:41 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 Mah 2002-11-22 22:20:57 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461)

Description of problem:
The Psyche boot CD is based on syslinux/isolinux 1.75. I have found that it 
freezes for about a minute on the ISOLINUX 1.75 screen, than installs without a 
problem. This message appears: Failed to get sector size. I have rebuild a 
custom CD with the version 2.0 isolinux.bin file. This problem seems to be 
fixed for the Toshiba 8100 and 8200 models.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Boot Psyche CD one
2. see message one screen
3. install normally.
	

Actual Results:  Installs fine, after 1 minute lag

Expected Results:  no lag, it should boot immediately

Additional info:

Redhat should consider using version 2.00 of syslinux/isolinux to create the 
iso files.

Comment 1 Stephen Mah 2002-11-22 22:23:27 UTC

Forgot to mention, the problem only affects certain models from Toshiba. 
Confirmed on Tecra 8100 and 8200. Problem does not appear to be an issue with 
other vendors.

Comment 2 Peter Jones 2005-04-19 18:30:41 UTC

This is really something that needs to be fixed or worked around in the upstream
sources, or more likely fixed with a new firmware on your laptop.

Sorry.