[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 8003EP nic installation woes...



On 14 Aug 2001 16:19:19 -0500, mullena@iwon.com wrote:
> Greetings;
> 
> I have a 8003EP nic in a 32MB/3GB 486/50.  I have the base system installed
> via floppy (no cd).  I *could* install more of Debian via ppp.  But since
> I have access to a T1+ line I'd much prefer to install via the network.
> 
> But I can't get the dang-blamed card configured.
> 
> I went to www.smc.com and picked up a copy of ezstart and diagnose.  Diagnose
> gave me parameters of io=0x300 irq=5 mem=0xCA000, with a ram size of 8k.
>  EZStart gave me parameters io=0x300 irq=5 and what it said was a ram window
> of CA00-CBFF.

You don't happen to have a soundcard with a midi port around there do
you?  What does /proc/ioports /proc/interrupts look like on your system?


> 
> Both programs performed tests and the card passed all of them.
> 
> Here are the parameters I used with the wd module with no success;
> io=0x300 irq=5 (these never changed)
> mem=0xCA000 mem_end=0xCBFFF
> mem=0xCA000 mem_end=0xCC000
> mem=0xCA00 mem_end=CxCBFF
> mem=0xCA000
> mem=0xCA00
> 
> The error messages are:
> wd.c: No wd0x3 card found (i/o = 0x300)
> /lib/modules/2.2.18pre21/net/wd.o init_module: Device or resource busy
> Hint: this error can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters
> /lib/modules/2.2.18pre21/net/wd.o: insmod /lib/modules/2.2.18pre21/net/wd.o
> failed
> /lib/modules/2.2.18pre21/net/wd.o: insmod wd failed
> 
> I even opened up the box to look at the card.  The jumper is set to 0x300
> 5 0xCA000.

Just a question, but what does pnpdump say about cards on your system.
You're saying the card is jumpered but I just want to be sure nothing
else is getting in the way.

--mike




Reply to: