Bug 72073

Summary: Can't install on IBM thinkpad 600 - isolinux related?
Product: [Retired] Red Hat Linux Reporter: Alan Cox <alan>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED WONTFIX QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-08 22:22:56 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 Alan Cox 2002-08-20 23:30:20 UTC 
ISOLinux 1.75 2002-06-14 isolinux: Failed to get sector size, assuming 0800
isolinux: Di0142758B

Limbo1 installs fine, 7.3 is fine "other vendors" are fine.
Comment 1 Jeremy Katz 2002-08-21 06:31:38 UTC 
Limbo1 was using the same version of syslinux (isolinux) and we haven't done
anything weird since then.  I also seem to remember that the tp600s we have were
working fine when I was using them to test the pcmcia code with pre-null code. 
Are you sure it worked with limbo1 / know if it works with other isolinux using
distributions?
Comment 2 Alan Cox 2002-08-21 12:37:38 UTC 
Yes on all counts. And tried both docked/undocked and with two different drives.

I talked to HPA (Isolinux maintainer) about it - he seemed to have some ideas. I
need to test isolinux 1.76pre1 and find out.

I'll try a floppy based install later to check the rest is ok
Comment 3 Alan Cox 2002-08-22 20:32:36 UTC 
Floppy install works.
Comment 4 Michael Fulbright 2002-09-27 20:39:58 UTC 
Dropping severity since floppy based installs do work.
Comment 5 Jeremy Katz 2003-01-03 06:02:24 UTC 
Does 2.00 in phoebe work?
Comment 6 Alan Cox 2003-01-03 11:43:32 UTC 
2.00 in Phoebe dies with

isolinux:  Disk error 01, AX=4229,8B

Same CD is ok on other systems
Comment 7 Jeremy Katz 2003-01-08 22:22:56 UTC 
I'm pretty sure this is a BIOS bug.
Comment 8 Alan Cox 2003-01-08 22:24:53 UTC 
Agreed - I've been discussing this with H Peter Anvin