>> I can run milo or pandora fine from >> that DOS partition, but the linux kernel always hangs after printing a >> few lines (the last line is the "Console: Colour G364 128x48" one)...most of >> the screen is white on red, while the kernel messages are white on black. >> This also happens sometimes with the floppy boot, but not consistently. >I received such bug reports ages ago, they're supposed to be fixed. Does >your screen more or less jump up by a random number of lines; the red area on >the bottom of the screen is filled with random garbage? The solution is to >use a newer version of Milo. You should be using at least version 0.27; >0.27.1 is current. 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. > Note that the current kernels doesn't need Milo anymore for booting. You > can for example run it from the firmware function ``Execute command'' 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. > I don't know where you got a version 0.50 from; the > version in our CVS, Vger's CVS and Linus' release are all 0.10. Have to > check if something got messed up. 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. >> int-handler.S: Assembler messages: >> int-handler.S:66: Error: .previous without corresponding .section; ignored >> Do I need a newer binutils? Some change to the configuration? > Yes, that's an as bug. There are also much newer kernels available on > ftp.linux.sgi.com. In order to use them you'll have to upgrade gcc and > binutils to a newer version. At this time egcs-1.0.2 + patches and > binutils-2.8.1 + patches is recommended; I haven't released binaries of > these. I thought the 2.8 tools had a bug which made 2.x kernels unreliable? > However, in order to make your live so much easier, just get a kernel > binary from ftp.linux.sgi.com:/pub/linux/mips/. 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. > 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.
