[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Help with ND5020 (NE2000 combatable) NIC.
- To: <nick@holland-consulting.net>, "Misc @OpenBSD" <misc@openbsd.org>
- Subject: Re: Help with ND5020 (NE2000 combatable) NIC.
- From: "Will Bober" <will@bober.com>
- Date: Sat, 1 Sep 2001 10:21:58 -0400
- References: <200108312130.f7VLUpX05267@openbsd.cs.colorado.edu> <3B902C94.F2AD1B8E@holland-consulting.net>
If just need a boot disk (assuming you have a net connection which you must
as you are posting :) goto http://www.bootdisk.com You can find just about
anytype of boot disk you will need.
- Will
----- Original Message -----
From: "Nick Holland" <nick@holland-consulting.net>
To: "Misc @OpenBSD" <misc@openbsd.org>
Sent: Friday, August 31, 2001 8:32 PM
Subject: Re: Help with ND5020 (NE2000 combatable) NIC.
> http://www.holland-consulting.net/tech/OBSDCommProbs.html#NE2000
>
> However, it sounds like you are on the right track -- the problem is
> card configuration, and more than that, it is you aren't set to the
> proper IRQ. Most likely your card is at a factory default position of
> 300/3, OpenBSD sees the 300, and assumes IRQ 10.
>
> You need to use that configuration program. You need to use DOS. No
> good way around it (unless your card has jumpers)
>
> IF you really have no access to a DOS boot disk or a Win9x boot disk,
> you can use FreeDOS or Caldera's DR-DOS (which I believe is available
> for free (no charge) use, though last time I looked I couldn't find
> it). Or borrow someone's DOS/Win9x boot disk. You don't need to
> install anything on your computer -- just enough to boot, switch
> floppies, run the config program.
>
> Nick.
>
> "Daniel T. Staal" wrote:
> >
> > Hi, OpenBSD newbie hoping to set up a firewall on a third-hand system
> > here.
> >
> > I've got one ISA NIC that I can't get working, its a ND5020, NE2000
> > compatable card, with a NDET07 bootable BIOS. It loads in fine, shows
> > up in dmesgs, etc., but if I try to use it, either through ifconfig or
> > hostname.ne1 (that's what it likes to show as, I can config the kernel
> > to get it as ne0), I get "ne1: Device timed out" messages. No pings go
> > through, although I can ping the card itself, and a "route show" just
> > stalls for ages. (Though it will complete, eventually.)
> >
> > I have a guess to the problem: the ne* driver doesn't do card config.
> > Unfortunatly the only way I've found to do card config for this card is
> > through a MS-DOS based program, and I don't have DOS anywhere.
> >
> > So am I overlooking something? (Easy for me to do, all I know about ISA
> > I've learned from reading this list recently.) Or am I up a creek?
> >
> > Thanks.
> >
> > Daniel T. Staal
> >
> > (dmesg follows, you want anything else just ask. This is without the
> > hostname.ne1 file.)
> >
>
> <dmesg snipped for message size, but THANKS for including it!>
> --
> http://www.holland-consulting.net/