Date: Mon, 29 Jan 2001 20:06:44 -0600 (CST) From: John Kenagy <jktheowl@bga.com> To: jpaetzel@hutchtel.net Cc: freebsd-questions@FreeBSD.ORG, Greg Lehey <grog@lemis.com> Subject: Re: linksys ne2000 card not detected on 4.2R Message-ID: <Pine.BSF.4.21.0101291957200.902-100000@barnowl.roost.net> In-Reply-To: <3A748D7A.19516.24A951@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Josh, Thanks for the reply. On Sun, 28 Jan 2001 jpaetzel@hutchtel.net wrote: > On 27 Jan 2001, at 15:24, John Kenagy wrote: > > > Hi Greg, > > > > On Sat, 27 Jan 2001, Greg Lehey wrote: > > > > > On Friday, 26 January 2001 at 21:36:24 -0600, John Kenagy wrote: > > > > Well, new release new problem. > > > > > > > > On loading 4.2R the ed0 interface does not appear at all. The > > > > configuration utility (during installation) was used to create the > > > > kernel.conf file. This is the first time in several upgrades (skipped 4.0 > > > > and 4.1) where this has happened and results in no network. > > > > > > Well, I suppose the obvious question is "are you sure you have the I/O > > > address and IRQ right?". If you still have a /var/log/messages from a > > > previous version of the system, you could check. Otherwise the thing > > > to do is to boot with the verbose option. During the countdown on > > > booting, hit the space bar and type: > > > > Yep, I got them right. I don't have any old log files but did make a copy > > of the kernel configuration file and it is specified the same way. > > > > > > > > ok set boot_verbose > > > ok boot > > > > I never get this. The space bar has no effect and there is no countdown. > > > > Something I did not notice (my bad) was that during boot > > I get an error complaining that /boot/loader cannot be found. It is there > > where it is supposed to be. The system will go on and boot after a delay > > of a few seconds. > > > > I've been doing a bit of reading on this but I'm not clear enough on it to > > play with it for fear of losing control. This is a "dangerously > > dedicated" machine as all installs have been but I'm guessing that that > > choice had some hidden negative impact. > > > > Thanks, John > > > > > > > > That might give some more information. > > > > > > Greg > > I am sorry to break into the middle of this, especially since I didn't > catch the original question, but I have a ton of linksys cards here > and use them all the time. I just built a 4.2-RELEASE machine > today using a pci linksys card that was picked up as a ed0. I tried a little head scratching and concluded that, since my /boot/loader file is "not found" (but present) the configuration file that reassigns the ed0 port to 0x300 wasn't being implemented. Instead the vanilla kernel was loading. So I built a new kernel, making all necessary changes and presto, it works now. The issue of _why_ the loader does not get found is not addressed, but with a custom built kernel it really is not an issue. Just one of them thangs I guess. Thanks for the offer of your help. John > Here is the line for it in my kernel config: > > device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 > > Here is how it is detected at boot: > > ed0: <NE2000 PCI Ethernet (ProLAN)> port 0x6100-0x611f irq 11 > at device 11.0 on pci0. > > I don't know what kind of card you are using, but I have a ton of > linksys cards here and some test machines, so if there is any way > that I can help you out let me know. > > Josh > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0101291957200.902-100000>