From owner-freebsd-alpha Sun Jan 2 5:57:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id B1DE014E67 for ; Sun, 2 Jan 2000 05:57:44 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id NAA27873; Sun, 2 Jan 2000 13:58:54 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 2 Jan 2000 13:57:36 +0000 (GMT) From: Doug Rabson To: Chuck Robey Cc: FreeBSD-alpha@freebsd.org Subject: Re: fxp0 & splimp In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 2 Jan 2000, Chuck Robey wrote: > On Sun, 2 Jan 2000, Chuck Robey wrote: > > > I was trying to bring an Alpha with a kernel from 11/15/99 to current, and > > I can't seem to get kernel right. I see that there were a lot of config > > changes, so perhaps I don't have my config file in sync, but it looks > > roughly like GENERIC, so I will toss the diag information in your laps. > > > > The kernel boots, but it can't find the onboard Intel Pro-100 (it's a > > Intel DK440LX, integrated everything). The boot message tells me: > > > > link_elf: symbol splimp undefined > > > > This just stops the network from working, so I'm not in trouble (I have > > the old kernel cached away too). Seeing as I didn't find the ax0 device > > in GENERIC, I took it out of my config file, and this causes more > > confusion, because the ax0 device IS being caught on the dmesg, but the > > fxp0 device (which is in the new config, instead of ax0) isn't being > > caught. > > Followup to my own question, because I just found out that dmesg on the > Alpha doesn't clear out the old boot message, and when I made real sure > that I *was* reading the right dmesg, ax0 isn't showing up. Neither is > fxp0, and the splimp message is still there, so most of the question still > holds. I'm getting the link error on boot, and fxp0 isn't being seen on > probe. I think the ax driver was removed since the new dc driver was committed. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message