> Frank - this sounds familiar to me.  When I first set up 9.0 I could
> boot into  that, but not into 8.2.  After much help from the list I
> found that it  happened because I had a /boot directory in each install
> (which is what  happens if you don't make a separate /boot partition).
> You need to know  which of those is being read by the boot process.  If
> you can't find out, try  this solution on both of them - it will do no
> harm, although only one of them  will be used.
>
> In the old /boot directory,find the file called initrd-2.4.whatever and
> the  vmlinuz-2.4.whatever.  Copy them into the new /boot directory.  Do
> the same  the other way round, copying them from the new into the old.
> You will end up  with two similarly named files for each, in my case
> initrd-2.4.18-6mdk.img  and initrd-2.4.19-16mdk.img, and the same for
> the vmlinuz entries.
>
> Boot is only reading one of these, and it needs to be able to find both
> versions, depending on which you choose in lilo.
>
> HTH
>
> Anne

Thanks for the attempt but that isn't the situation here.

My apologies for not making it clearer.  The problem seems to be linked
with my new motherboard in particular.

It runs Mandrake 8.1 and 8.2 beautifully.  It just won't install Mandrake
9.0 (I also tried RedHat 8.0 for that matter).
I know the installation CDs are fine because I used them on other PCs.  I
know the CDRom drive isn't the problem because it reads the cds without a
problem.  It seems to be the actual installation that causes the freeze to
the system.

When booting from a disk after writing an cdrom.img to it, it still
freezes just before the 2nd phase of the installation startup.
The same goes for any attempt booting from the harddrive as I copy the
entire 3 CDs to another hardrive in a fat32 partition and use a floppy
with the hd.img image to boot.  BTW, that is an awesome trick to
accelerate installation for those whom are curious.  It has other benefits
too.

If I try to do the install in text mode rather than vga mode I get up to
this just before it freezes:

Posix conformance testing by UNFIX
enabled by Extint on CPU#0
ESR value before enabling vector:0000002

and Blamo!  Just a blank screen....NumLock jammed up, etc....

Not that part seems to be resolved (see mandrakeuser) but the initial
startup after a successful installation seems to be the next problem I am
hoping to get resolved.

There isn't any redundant /boot files in my case because Mandrake 8.2 was
erased from that drive already.

I have a feeling that if I install 9.0 with the CTL/Alt/F2 and rm
/usr/blah/blah/blah trick, I will probably be able complete the install
and boot up to the newly installed linux if I do an immediate upgrade of
the kernel using an old 8.2 rescue disk and the newest kernel burned onto
CD ready to mount and install.  This seems like the most promising idea I
can come up with.  Problem is, is it worth the time to experiment??

But thank you again for the immediate response Anne.





Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to