linux-mips-fnet
[Top] [All Lists]

Re: Still no-go/gcc 2.7.2/binutils 2.8.1

To: linux-mips@fnet.fr
Subject: Re: Still no-go/gcc 2.7.2/binutils 2.8.1
From: Florian Lohoff <flo@rfc822.org>
Date: Thu, 31 Dec 1998 23:18:16 +0100
In-reply-to: <XFMail.981228170701.harald.koerfgen@netcologne.de>; from Harald Koerfgen on Mon, Dec 28, 1998 at 05:07:01PM +0100
References: <19981226022844.A6814@mini.gt.owl.de> <XFMail.981228170701.harald.koerfgen@netcologne.de>
Sender: flo@mini.gt.owl.de
On Mon, Dec 28, 1998 at 05:07:01PM +0100, Harald Koerfgen wrote:
> 
> Hmmm... May it be that you have a PROM with a buggy TFTP loader?
> 
> According to the NetBSD people some PROMs have interesting bugs. You may want
> to check http://www.netbsd.org/Ports/pmax/board-list.html#proms.

I have an KN04 V2.1k -> The page says:

---------------
   KN04 V2.1k No known problems TFTP booting as of NetBSD 1.2G
      (don't tftpboot with kernels made by old elf2ecoff)
---------------

and an KN03-AA V5.2b

-----------
   KN03-AA V5.2b No known problems TFTP booting
-----------

Both stop ...

> Another possibility would be to keep the .text and .data segment sizes
> below 1MB.
> 
> With the following .config

[...]

> linux/arch/mips/dec/boot > mipsel-linux-objdump --section-headers nbImage
> 
> nbImage:     file format ecoff-littlemips
> 

[...]

Ok looks the same for me - But - no-go 

> > BTW: This is binutils 2.8.1 + patches and gcc 2.7.2 + patches.
> > 
> > Ok - Ill wait 4 weeks until i retry otherwise i cant stand this unsuccess.
> 
> FYI, it took me two weeks of hard work to make my DS5k/133 grok the kernel 
> image.
> I found out that the PROM of this machine (KN02-BA V5.7j) wants to have
> .sdata and .sbss sections, even if empty. That's why elf2ecoff doesn't work 
> and
> the NetBSD people say that this PROM doesn't boot via TFTP.
> 
> Don't trust your PROM. Never.

Could you send me a binary image of the above config - Maybe that'll
boot ...

There is a funny thing in tftpbooting - (tcpdump)
-----schnipp---
23:06:04.162006 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xfddf0000 
[|bootp] (DF)
23:06:04.162243 10.1.1.10.bootps > 10.1.1.11.bootpc: xid:0xfddf0000 Y:10.1.1.11 
S:10.1.1.10 [|bootp]
23:06:04.236310 10.1.1.11.57342 > 10.1.1.10.tftp: 27 RRQ "/data/mips/nbImage" 
(DF)
23:06:04.411642 10.1.1.10.1033 > 10.1.1.11.57342: udp 516
23:06:04.483248 10.1.1.11.57342 > 10.1.1.10.1033: udp 4 (DF)
[...]
23:06:15.140257 10.1.1.11.57342 > 10.1.1.10.1033: udp 4 (DF)
23:06:15.140300 10.1.1.10.1033 > 10.1.1.11.57342: udp 516
23:06:15.153934 10.1.1.11.57342 > 10.1.1.10.1033: udp 4 (DF)
23:06:15.153978 10.1.1.10.1033 > 10.1.1.11.57342: udp 516
23:06:15.169259 10.1.1.11.57342 > 10.1.1.10.1033: udp 4 (DF)
23:06:15.169314 arp who-has 10.1.1.11 tell 10.1.1.10
23:06:16.164465 arp who-has 10.1.1.11 tell 10.1.1.10
23:06:17.164399 arp who-has 10.1.1.11 tell 10.1.1.10
23:06:18.164336 arp who-has 10.1.1.11 tell 10.1.1.10
23:06:20.164286 arp who-has 10.1.1.11 tell 10.1.1.10
23:06:21.164152 arp who-has 10.1.1.11 tell 10.1.1.10
23:06:22.164085 arp who-has 10.1.1.11 tell 10.1.1.10
23:06:23.164024 arp who-has 10.1.1.11 tell 10.1.1.10
----------schnapp--------

First the machine boots correct and afterwards suddenly i havnt
got an arp entry asking for it on the ethernet and nobody answering ...

*Aaaaaaaarghl*

Ok - got it - The machine wont answer arp requests on tftp download
and it seems that the development kernels (running 2.2pre1ac4/i386)
do have very small arp timeouts ... When i hardcode the MAC Addr
in my arp table it fully downloads the kernel ...

The 5000/150 shows me a "Launching Kernel"
"This is a 5000/1xx" .. and stops ...

The 5000/260 shows me a "Launsching kernel ..."
"This DECstation is a DS5000/2x0" and stops ... Hmm

Flo
--
Florian Lohoff          flo@rfc822.org                  +49-5241-470566
Good, Fast, Cheap: Pick any two (you can't have all three).  (RFC 1925)

<Prev in Thread] Current Thread [Next in Thread>