On Mon, Feb 01, 1999 at 08:40:00AM -0700, Jim Reiss wrote:
> No, it always looks the same (and I'm using Milo 0.27.1). After more
> investigation I have discovered that it only seems to happen if I try to run
> anything from the original hard drive that came with the system (a Maxtor
> hard drive which has had its ROM changed to say it's a "MIPS" drive). A
> Seagate drive I have in the same box does not seem to have the problem,
> fortunately.
Weired problem.
> It's "Run a program". I guess I should get the latest kernel, because
> 2.1.90 doesn't work this way. Maybe I'll try the precompiled m700 kernel,
> it has a later creation date.
Yes, the M700 is almost identical with the Magnum 4000, the only difference
is the onboard seven segment display. So the M700 kernel should work for
you.
> The sonic.c was 0.50 in the precompiled kernel on ftp.linux.sgi.com in the
> /pub/linux/mips/test directory, as well as the kernel source in that
> directory. Doesn't work for me anyway, so I'm using an NE2000 card instead.
NE2000 used to work just perfect when I last used one two years ago.
> I thought the 2.8 tools had a bug which made 2.x kernels unreliable?
That only refers to gcc 2.8. binutils 2.8.1 and above have have an bug
which requires you to remove the -N switch from LDFLAGS in arch/mips/Makefile
and that's all the problems.
> I did, but the "autoconfigure" of the network caused our corporate ethernet
> to get a little confused. I finally managed to rebuild the kernel without
> this option by building it right on the Magnum 4000, though I then had to
> reinstall everything because the glibc files I installed to build it were
> not compatible with the "root" filesystem from the "test" directory.
The kernel Documentation/ stuff explains the options which you need to
setup for manual booting via NFS. The other option is that you attach the
Magnum's disk to a PC running Linux, and put three partitions on it
partition 1: MSDOS, let's say 10mb for Milo and kernels.
partition 2 and on swap / and all what else you want.
Then copy the root filesystem to it, boot and start upgrading the stuff as
you see fit.
> > Native RPM packages of many of the tools are also available there.
> Is there a suggested best procedure to install these RPMs? It does not appear
> that there is an installation image to provide the framework for installing
> them. The root-le-980323.tar.gz file seems to be based on an earlier Red Hat
> release.
Yes, but upgrading to the newest available little endian binaries should
just work. You should also be able to run Cobalt's rpm packages.
Ralf
