From owner-freebsd-alpha Tue Jan 22 13: 4: 1 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 95D2537B402 for ; Tue, 22 Jan 2002 13:03:53 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020122210353.VTPC10199.rwcrmhc53.attbi.com@peter3.wemm.org> for ; Tue, 22 Jan 2002 21:03:53 +0000 Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id g0ML3rs16171 for ; Tue, 22 Jan 2002 13:03:53 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (Postfix) with ESMTP id 0BAB939F1; Tue, 22 Jan 2002 13:03:53 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Bernd Walter Cc: alpha@FreeBSD.ORG Subject: Re: Is anybody actually able to netboot at the moment? In-Reply-To: <20020122173953.K71841@cicely8.cicely.de> Date: Tue, 22 Jan 2002 13:03:53 -0800 From: Peter Wemm Message-Id: <20020122210353.0BAB939F1@overcee.wemm.org> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bernd Walter wrote: > On Tue, Jan 22, 2002 at 03:46:34AM -0800, Peter Wemm wrote: > > By netboot, I mean having something like ewa0_protocols = BOOTP and > > 'boot ewa0' (or ewb0 in some of my cases).. ? > > At least 4.5-RC doesn't behave that badly: > >>>boot ewa0 > (boot ewa0.0.0.11.0 -flags 0) > > Trying BOOTP boot. > > Broadcasting BOOTP Request... > Received BOOTP Packet File Name is: netboot > local inet address: 10.1.1.128 > remote inet address: 10.1.7.11 > TFTP Read File Name: netboot > netmask = 255.255.255.0 > Server is NOT on same subnet as client... > Router used = 10.1.1.8 > .... > bootstrap code read in > base = 110000, image_start = 0, image_bytes = 33520 > initializing HWRPB at 2000 > initializing page table at 102000 > initializing machine state > setting affinity to the primary CPU > jumping to bootstrap code > Console: SRM firmware console > VMS PAL rev: 0x1000400010538 > OSF PAL rev: 0x100090002012d > Switch to OSF PAL code succeeded. > > FreeBSD/alpha SRM net boot, Revision 0.1 > (root@ds10.wbnet, Wed Jan 9 11:06:27 GMT 2002) > Memory: 32768 k > boot: ethernet address: 00:00:92:90:7f:26 > net_open: server addr: 10.1.7.11 > net_open: server path: /var/d7/testroot/ > Loader version 0.3+ required > Aborted! > start not found > > Hit [Enter] to boot immediately, or any other key for command prompt. That's where I get stuck... peter@axp0[4:12am]/local0/src/lib-434# uname -a FreeBSD axp0.freebsd.org 4.5-RC FreeBSD 4.5-RC #0: Fri Jan 11 14:27:13 PST 2002 peter@axp1.freebsd.org:/home/src/sys/compile/MIATA alpha I took /boot/netboot from that machine and served it out via tftp to the clients. I also tried the -current netboot image and it has the same problem. > The testroot is plain from the 4.5-RC iso. > the netboot tftp file is also from there. > > I can hardly remember there is need for a different kernel. > Would be nice for installing to have them build with release. > > > And if so, how are you doing it? I've been fighting with a group of > > cranky PWS 500au's (MIATAs) on a (fairly high powered) switch. > > > > If I run a tcpdump on the machine running dhcpd, I see about (maybe) one in > > 50 broadcast bootp (or dhcp discover) packets actually arriving. However, > > when net_open() switches to RARP, I see every single one of those arrive. > > Sometimes even SRM fails to have its bootp broadcasts seen and has to > > retry. Most of the times when the server actually sees the query and > > replies, the reply isn't seen by the client. However, the tftp downloads > > and rarp/arp broadcasts seem 100% reliable. > > > > Eventually, if I am lucky, the client will actually get a response to the > > packets it sends and will magically snap into life, and fire up the NFS > > root mount etc. > > > > The only holdup seems to be the dhcp query.. :-( > > > > I wish I had a hub to plug these boxes into, but right now I am having to > > rely on tcpdump. Doing a hexdump of the packets that netboot uploads to > > the prom packet send code shows nothing obviously wrong. I might have to > > dig up a hub and go looking at the wire to see if SRM is sending but the > > switch is somehow deciding to filter the packets. However, If that were th e > > case, I'd be wondering why the x86 boxes on the same switch can netboot > > just fine. (yes, the MAC addresses are explicitly listed). > > > > Anyway.. the final straw is that when it finally does get up to a loader > > 'ok' prompt, doing a "load kernel" causes a 'kernel stack not valid' > > trap back to SRM. (doh!) > > > > Can anybody please sanity check this for me? On several different > > combinations of hardware if possible. > > > > What is really bizzare is that my PC164SX at home has the same problem. > > I only have a cheap switch at home (no hubs anywhere... :-/ ) > > I have one switch a hub and a FreeBSD router in between. Hmm. can you be more specific? Is your client box connected to the hub and then routing via the freebsd router? The reason I ask is that freebsd may be more forgiving about packet construction. I suspect the switch is detecting something wrong with the packets that libstand is generating and killing them before they make it out to the fabric. > > Both the Miatas and the AlphaPC164SX have current (albeit old) firmware. My > > PC164SX at home recognizes a fxp, I must try it with that instead of a > > 2104x, 21140A, or 21143 card. > > I will try -current next. > > -- > B.Walter COSMO-Project http://www.cosmo-project.de > ticso@cicely.de Usergroup info@cosmo-project.de > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message