Topic: SME 6.5 Install Crash on IBM Netvista

[tas]

Greetings fellow SME users.

I am trying to install SME 6.5 on an IBM Netvista PC (866Mhz PIII). The install locks up during the initial install boot sequence with the last message of:
======================================================
Checking 'hlt' instruction...
======================================================

Both Smoothwall and Fedora Core 3 installs on the same PC locked up at the "Checking 'hlt' instruction..." during the install boot sequence. Both gave the option to add commandline parameters early in the boot sequence and installed sucessfully after adding "no-hlt" to the linux boot command line, but the  SME install does not give the option to add command line parameters during the boot sequence.

Is there any way to add the "no-hlt" parameter to the SME install boot command line?

Regards
Tas

[boss_hog]

Hey tas,
during the initial boot when you see the "syslinux", hit CTL+C to stop the boot process. At this point you should  get a prompt and be able to pass the parameters.
Hope this helps
Joe

Edit: One thing unique to the SME family of software is the "accept". Here is an example of the parameters on boot.
BOOT: accept mem=512M no-hlt

[tas]

Thanks Joe

The Ctrl+C worked, I was able to install SME on the Netvista PC.

Then I had a problem with the Netvista PC crashing during the SME boot sequence, this took some working out as the Ctrl+C does not seem to work during the normal SME boot sequence.  

The following process was used to resolve the problem:
1. Mount (on another Linux box) the boot/rescue floppy created during the install.
2. Edit the syslinux.cfg file and added "no-hlt" to the "append" line.
3. Boot the Netvista PC from the modified floppy.
4. Logon as root
5. Edit the /etc/lilo.conf file and add
       

Code: [Select]

append = "no-hlt"
   as a global option
6. Save the file
7. Run the lilo command to update the boot loader.
8. Reboot

Now the Netvista PC boots SME successfully.

The above took several re-installs and much cursing at lilo until I discovered that the errors the lilo command was giving was not caused by by my modification but the incorrect "default=..." line in the original lilo.conf file.

Once again, thankyou for your assistance, it is greatly appreciated.

Regards
tas