Bug 7370 - Installer hangs on Checking 'hlt' instruction...
Summary: Installer hangs on Checking 'hlt' instruction...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.1
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jay Turner
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-11-27 04:23 UTC by tovecka
Modified: 2015-01-07 23:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-11-29 16:20:59 UTC
Embargoed:


Attachments (Terms of Use)

Description tovecka 1999-11-27 04:23:34 UTC
The Linux 6.1 installer hangs on line Checking 'hlt' instruction... when
installing on Intel Pentium Pro Motherboard AP440FX Bios 1.00.11.CT1
booting from the 6.1 boot floopy, also tried downloading the latest boot
img and received same result.

Comment 1 Christian Hechelmann 1999-11-28 19:02:59 UTC
Actually at this point the installer isn't running yet, as the kernel crashes
before any filesystems are mounted.

Try "linux no-hlt" on the prompt when you boot the installer floppy or CD.
If the installer does boot after that your motherboard/cpu/bios combination
does not like the hlt instruction.

Comment 2 Jay Turner 1999-11-29 16:20:59 UTC
Reopen this bug if the drdisk solution does not work for you.

Comment 3 tovecka 1999-11-30 05:10:59 UTC
Yes, during install typing F5 linux no-hlt text worked, however adding no-hlt on
the options line of the Lilo Configuration screen did not add append = "no-hlt"
to /etc/lilo.conf (allowing the system would reboot with this option). Also
manually editing lilo.conf and adding append = "no-hlt" did not work either.
Using linuxconf, which wrote the exact same line worked. (kinda strange?) You
may want to keep this in bugzilla as the above syntax is correct, some other
references on the net are not. Thanks again, you all are great! GO RHAT!


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