On Fri, Jun 02, 2000 at 02:17:05PM -0400, Eric wrote:
>
> The beta 3 snapshot won't install on my dual pentium II machine.
> after clicking ok on the first window of the install packages section,
> I get a 'divide by 0' error window. I found no errors in any of the log
> windows except for one saying that it couldn't find kernel-smp.
I had some kind of same experience. that was weird:
Have a Tekram U2W controller and a IBM DNES 9.1 gb disk.
The following happened (expert mode)
in the partitioning tool, i cleared all partitions from my air installation
and made new ones, this time including a /boot.
Installing process went fine, but could not reboot because my root partition
is not the root partition that was installed with lilo.
Had to boot with tom's and repair/install lilo.
Ok so far, due to some issues i decided to reinstall again, and now
it begins.
After the first 7.1 installation, my scsi controller complains
while booting up with something
like "expecting sectors xyz", that means, disk was formatted with different
controller.
I had to make some tweaks in the tekram bios. (enable 13H, disable >1GB. Why? worked
with air)
With or without that tweak, i was not able to install 7.1 again.
After partitioning and selecting mount points, i got something like
"no base packages found". Hitting "back" brings me to partition tool,
hitting "done" again brings me to that "divide by 0" error.
Wrote fresh dos partition table to the disk, no success.
Tried that several times with different setups and configs.
Air CD shows the same error.
I had the idea to install something like a partition skeleton with a
non-mandrake partition tool, i did that
with an old redhat distro cd. Then booted with 7.1 again, i only had
to set up the mountpoints.
Installation works then. Thats why i'm writing from hydrogen now ;).
It selected the wrong root partition for lilo again tho, but thats not that
bad, if one has tom's handy.
I have a feeling that partition tool is buggy.
It did something bad to my harddisk, dunno exactly.
Spent a whole weekend with that, i'm glad everything seems fine now.
-cteg
erm, forgot to mention, i don't have beta3 and decided not to post my
experiences because my beta is kind of "outdated" (b2).
After reading the above email i thought maybe the bug is still there.
--
damn i'm looking good
