Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Alexander Markley <alex@cyberMalex.com>
To: linux-mips@linux-mips.org
Subject: SGI O2 MIPS R5000 bootp problems
Date: Mon, 17 May 2004 11:55:55 -0400	[thread overview]
Message-ID: <40A8E08B.7070203@cyberMalex.com> (raw)

Hi. I just get an SGI O2 with a MIPS R5000 chip in it, and I'd love to 
run linux on it. The machine seems to be in working order, and has been 
known to boot into IRIX in the recent past.

I have gotten the debian tftp boot images and things, and have properly 
set up dhcp and tftp, but I cannot make this machine boot!

...
 > boot f bootp():r5000_boot.img
Setting $netaddr to 192.168.1.235 (from server )
Obtaining r5000_boot.img from server
7536
Cannot load bootp():r5000_boot.img.
Range check failure: text start 0x88802000, size 0x1d70.
Text section would overwrite an already loaded program.Unable to execute 
bootp():r5000_boot.img:  not enough space
Unable to load bootp():r5000_boot.img: not enough space
 >
...

I'm not sure why this doesn't work for me when it works for everyone 
else... Is it because my machine only has 64 MB of ram?

Another strange bit is that this kernel does load and boot fine: 
http://www.linux-mips.org/~glaurung/O2/linux-2.6.1/kernel/vmlinux64

Of course, it can't finish booting since I didn't provide a root FS, but 
I wonder why the PROM doesn't want to jump to the debian image?

I'll keep trying different things, and keep you guys posted. In the 
meantime, and input would be much appriciated. Also, I haven't joined 
the list, so CCing me would also be appriciated.

ttyl
--Alex

             reply	other threads:[~2004-05-17 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 15:55 Alexander Markley [this message]
2004-05-17 16:15 ` SGI O2 MIPS R5000 bootp problems Ladislav Michl
2004-05-17 16:36   ` Ralf Baechle
2004-05-17 18:08     ` Karsten Merker
2004-05-17 18:12       ` Ilya A. Volynets-Evenbakh
2004-05-17 22:34     ` Alexander Markley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40A8E08B.7070203@cyberMalex.com \
    --to=alex@cybermalex.com \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox