Civileme....hmmmm...my system consists of an AMI bios a 440BX chipset, a
400mhz PII, but the bios operates quite differently than yours in the
boot sequence area. It looks like this:
1st Boot Device Floppy
2nd Boot Device ARMD-FDD
3rd Boot Device SCSI
Try Other Boot Devices Yes
The ARMD-FDD is the Ls-120 and it works just fine for booting. An
Adaptec dual channel SCSI controller is built-into the motherboard.
There's a 10 gig hd, CDRom Drive, Zip Drive and Scanner attached to the
SCSI controller and the Ls-120 is the only IDE device and is on hda.
Alan
root wrote:
>
> Alan
>
> It is a mystery to me
>
> Processors : AMD K6-450 Celeron400 Cyrix 6x86 200
> Chipsets: SIS 530 LX TX
> VIA MVP4 SIS
> 5571
> FIVE target machines
>
> All LS120 at /dev/hdc
>
> mkbootdisk --device /dev/hdc -v 2.2.13-7mdk
>
> Output the same (this is a mkbootdisk that had extra echo instructions
> at several locations so I could see where the error(s) were arising.
> All Had the AMI BIOS and it each case it was set to LS120/C for boot
> sequence.
>
> NONE of this output seems to resemble yours.
>
> These were all relatively recent installs from the CDs with NO updates
> applied
>
> Civileme
>
> ------------------------------------------------------------------------
> [root@localhost /root]# mkbootdisk --device /dev/hdc -v 2.2.13-7mdk
> Insert a disk in /dev/hdc. Any information on the disk will be lost.
> Press <Enter> to continue or ^C to abort:
> Formatting /dev/hdc... done.
> Copying /boot/vmlinuz-2.2.13-7mdk... done.
> ^?Creating initrd image... /tmp/mkbootdisk
>
> --with 8390 with ne2k-pci ne2k-pci
> usage: mkinitrd <Snip>
> done.
> Setting up lilo...
> /tmp/mkbootdisk/etc
> /tmp/mkbootdisk/dev
> /tmp/mkbootdisk/boot
> 0 blocks
> ls /dev/hdc
> 0 blocks
> ls /dev/hda6
> rescue image made
> message
> done.
> running LILO
> mknod /tmp/dev.0: No such file or directory
>
>
>
