This is strange one :
AMD K6-2 3DNOW 350Mhz
AMD reference system (I work for a chip company)
IDE HD and CD Drive
Boot from floppy to kickoff the install process. Finds the
CD drive ok, and select workstation or server as your
configuration.Let Linux take over the entire HD and destroy
whatever exists on it. Make a boot disk just in case during
After the install you'll need to reboot, at which point
linux fails to boot. If you boot from the floppy you made
during install, then the HD will boot up fine.
Now boot an MS disk, and activate the Linux boot partition,
and suddenly Linux will boot from the machines hard drive,
and not require the floppy at all.
Now, this is the fun part. I reinstalled Linux on this
machine again, told linux to reinstall itself and destry
the data. I finished the install, and BAM - Same problem,
Linux fails to boot from the Hard Drive. I again boot from
an MS floppy,FDISK the system, and once again it boots from
the hard drive.
The same install process as above has worked on a number of
other machines, so I was really surprised when it failed on
the AMD. There is obviously something strange about this
machine, but I'm not sure what. If you have any tests/need
more info, let me know. email me at firstname.lastname@example.org or
email@example.com (my work email)
We have observed this to be a bug and have verified it on machines in
our test lab. It is being assigned to a developer for further review.
One of six users at LULA's Jan 99 installfest ran into this. A fix
would benefit real users.
*** Bug 932 has been marked as a duplicate of this bug. ***
When using the built-in "Server" installation type, the
first reboot FAILS, despite having LILO installed. None of
the partitions on either /dev/hda or /dev/hdb were marked
I'm not sure if the interaction is with LILO, or with a
"smart" BIOS in some newer PCs. There are two solutions:
1) re-boot off the CD-ROM (or the install floppy), get to
the point where you can pick between fdisk and Disk Druid,
run fdisk on /dev/hda, mark the partition active, WRITE
changes to disk, wait for disks to sync, then press the
RESET button (ie. hard boot)
2) boot of the boot floppy that got created during install
(if you made one :-) and re-run LILO. I have no idea why
re-running LILO fixes this problem. This method did *NOT*
fix the problem on one PC with a *single* root partition
that was over the 1024 cylinder mark. There may have been
some other interaction there.
I'm not certain, but I believe that the same behaviour
happens when using Disk Druid instead of fdisk. Last time
I tried was a while back, so I could be wrong.
------- Additional Comments From firstname.lastname@example.org 02/05/99 12:24 -------
Is this a duplicate of #909?
Fixed in the next release.