Bob Taylor wrote:
> In message <>, "Adam C. Powell, IV" writes:
> > Bob Taylor wrote:
> >
> > > In message <[EMAIL PROTECTED]>, "Adam C. Powell, IV" writes:
> > > > Bob Taylor wrote:
> > > >
> > > > > I cp'd the new kernel to /vmlinux.gz and rebooted. Naturally, I have
> > > > > forgotten a step or ten as the new kernel will not boot. So ...
> > > >
> > > > Er, you did rename the old kernel, right? Let's say you renamed it to
> > > > oldvmlinux.gz.
> > > >
> > > > In MILO, just type:
> > > > boot <partition>:oldvmlinux.gz root=/dev/<partition>
> > > >
> > > > where <partition> is the disk partition where root lives (hda2 for mine).
> > > >
> > > > If you didn't rename the old kernel (i.e. you overwrote it with the new
> > > > one), this will be somewhat more involved... But it is definitely still
> > > > possible to recover.
> > >
> > > Ah ... I cp'd the old kernel to /mvlinux-old.gz and cp'd the new kernel
> > > to /vmlinux.gz. I understood milo looked for a file name so that's why
> > > I did this.
> > >
> > > My system is using AlphaBIOS so milo > is nowwhere to be seen. I could
> > > really use some guidance.
> > >
> > > I have dd'd milo, lx164, and ramdisk images from the Alpha CD onto seperate
> > > floppies on my Intel box. I tried booting that way with no luck. I have
> > > the official boxed set from Red Hat.
> >
> > Okay, when the BIOS comes up, after it has tested RAM and probed for disks
> > etc., does it give you an OS selection menu and count down for start? If so,
> > press F2 to change the configuration, and follow the menus to (I think it's
> > called) OS selection utility. In that area, either add a new selection with
> > the same parameters as before but with the old kernel's filename
> > (vmlinux-old.gz), or else just change the existing selection to point to the
> > old kernel. (A new selection is probably better, so you can try a bunch of
> > different configurations and switch easily between new and old if they don't
> > work.)
>
> I had done all of this.
>
> > I hope this works! (It is odd, though, that the floppies don't boot...
> > I don't know what might be wrong there.)
>
> I finally got the milo prompt. I then ran the command "boot floppy" with
> the kernel boot disk and have successfully re-installed 5.1. After the
> installation told me to reboot and I did so, I executed dd if=/dev/fd0
> of=/dev/sda2 bs=1440k where /dev/fd0 was the milo disk and sda2 is the
> milo partition. I'm hesitant to reboot until I settle some questions.
>
> 1. Is the dd command I did correct?
Interesting- a direct inverse of the dd to make a milo floppy. I'm not sure if
this will work. Try mounting /dev/sda2 as, say, /milo, and see what you find.
You should see two executables: linload.exe and milo. My guess is that you just
created a single .img-style file with dd. But you should be able to make a viable
linload.exe and milo just by mounting the milo floppy and copying * into /milo
(=/dev/sda2). (This is how I updated milo from RH 5.0 to 5.1, though I'm not
certain it's the "right" way to do things. :-)
> 2. What argument to make to compile a new kernel--boot or zImage or ?
I use "make dep clean boot modules modules_install", where boot is the important
one, then "cp arch/alpha/boot/vmlinux.gz /vmlinux-2.1.125.gz" and edit the OS
selection next time I cycle power. Since milo can boot a gzipped kernel, there's
no need for zimage on Alpha.
> 3. On the HD originally there was a file named lx164 in /boot. Now /boot is
> empty. Why?
My /boot has always been empty. Shouldn't be a problem.
> 4. Executing man <whatever> segfaults. Is this a known problem?
Yes. It is listed in the RedHat 5.1 errata. Get and install the new rpm, or
download the source .tar.gz from ftp.win.tue.nl:/pub/linux/util/man .
Zeen,
-Adam `Cold Fusion' Powell, IV _/\_ http://www.ctcms.nist.gov/~powell/
Call with Netscape Conference! \/ http://dls.netscape.com/ ____
USDoC, National Institute of Standards & Technology (NIST) |\ ||< |
Center for Theoretical and Computational Materials Science | \||_> |
