Re: 4.2: Boot -> reboot -> reboot -> ...

[Stephen Smoogen <smooge redhat com>]

Ok the problem you have listed below looks like it is linked to the fact
that you have a 4.1 initrd being loaded. The initial ramdisk gets loaded
when the kernel is looking for certain modules and the kernel that is
inside this ramdisk is the one that gets booted. Since you are having
problems with the 4.2 boot floppy (which would be my way of getting around
the problem..) I dont know exactly what could be happening. Do you know
what other hard-ware you added so that it could see a big hard-drive?

[Please reply to the list... email sent to me sometimes gets shuffled away
by procmail to someplace west :)]

On Mon, 29 Sep 1997, Peter Wiemer-Hastings wrote:

> Hi,
> I've had Redhat 4.1 running on my Dell 486 (Optiplex 466 MTe) for
> several months now, crammed in with Windoze 95 on a 500M IDE disk.
> Finally I got the department to spring for a big (6.5G IDE) disk, and
> thought I'd go ahead and install the newer version (4.2) on that
> disk. 
> Got through the whole installation process fine, but when it rebooted
> to start up again, I get this behavior:
> 
>    General information about the machine.
>    Memory Check
>    LILO: boot
>    Loading LINUX
>    Uncompressing LINUX
>    Now booting
>    Console something-or-other (flashed too quick to read)
> REBOOT!?!?!
> That is, it starts the whole process again.
> 
> In my troubleshooting activities, I got the newer version of the
> Redhat installation boot disk, and found that it does the same thing.
> When I tell it to boot from floppy, it goes for a while and reboots.
> 
> As a result of further troubleshooting, I can now boot 4.2 using the
> old LILO which I reinstalled.  But it seems to be confused about the
> version number.  After booting up, it says it's running 4.2 Biltmore,
> with kernel version 2.0.27!  And this misinformation about the version
> number seems to be messing up the boot.  It can't find the proper
> modules, and consequently (I'm guessing) has trouble with networking
> setup.  Whatever the cause, I can't access anything on the network
> when I boot up with 4.2 now.  (I still can with 4.1.)
> 
> Any hope of getting this old guy running with 4.2, or should I just go
> back to 4.1?
> 
> Thanks,
> Peter
> 
> -- 
> Peter Wiemer-Hastings
> Departments of Psychology and Mathematical Sciences
> University of Memphis
> Memphis TN 38152
> pwmrhstn memphis edu
> 
> 
> 
> --
>   PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
>          To unsubscribe: mail redhat-install-list-request redhat com
>                      with "unsubscribe" as the Subject.
> 

-------------------------------------------------------------------
SJS