Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!umn.edu!csus.edu!netcomsv!mork!kwan From: kwan@netcom.com (Kwan-Seng Low) Newsgroups: comp.unix.bsd Subject: Re: help putting 386bsd0.1 -> ethernet... Message-ID: <y2cmm0#.kwan@netcom.com> Date: 20 Jul 92 17:52:06 GMT Article-I.D.: netcom.y2cmm0#.kwan References: <t=cm2q.kwan@netcom.com> <LMJM.92Jul20113416@raquel.doc.ic.ac.uk> Organization: Netcom - Online Communication Services (408 241-9760 guest) Lines: 21 In article <LMJM.92Jul20113416@raquel.doc.ic.ac.uk> lmjm@doc.ic.ac.uk (Lee M J McLoughlin) writes: >You may be getting hit by the same bug as me (see my article posted >last night: <LMJM.92Jul19233423@raquel.doc.ic.ac.uk>). > >Look at the irq number reported by the probe on startup and check that >it matches that of your hardware. If they differ then we are in the >same boat and require a kernel hack to get the irq right. > > Lee >-- >-- >Lee McLoughlin. Phone: +44 71 589 5111 X 5085 >Dept of Computing, Imperial College, Fax: +44 71 581 8024 >180 Queens Gate, London, SW7 2BZ, UK. Email: L.McLoughlin@doc.ic.ac.uk The boot messages did indicate we0 with irq 9, which is my setting on the wd8003e card (set the jumper to irq9). I suspect the OS doesn't talk to the ethernet card, as some others on the net use the same ifconfig line and works. As least I didn't see the transmit light blink when I issue the command. I'll keep trying with different card. Kwan-Seng Low