*BSD News Article 53031


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!howland.reston.ans.net!newsserver.jvnc.net!news.ge.com!luss.is.ge.com!not-for-mail
From: jrs@tampa2.is.ge.com (Jim Smithson)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Intel Ether Express configuration
Date: 19 Oct 1995 14:20:33 -0400
Organization: GE Information Services, Inc.
Lines: 36
Distribution: na
Message-ID: <4664th$acm@tampa2.is.ge.com>
References: <45pv7a$7td@tzlink.j51.com> <45u4eg$jo3@mmddvan.mdd.comm.mot.com>
NNTP-Posting-Host: tampa2.is.ge.com

I had a similar problem but using the Intel `softset` utility and
PAYING CLOSE ATTENTION I soon figured out my mistake.
The EE16 card by default does not map RAM. 
You will have to change that at least.
That was my mistake. As soon as ifconfig ran I got a kernel panic.
Read the documentation that came with the board carefully.

I had to comment out the mcd drivers cause at first it thought the EE16 was
was one of those devices.

Here is my kernel config file /sys/i386/conf/MYKERNEL
# conflict with ix0 
#device		mcd0	at isa? port 0x300 bio irq 10 vector mcdintr
#device		mcd1	at isa? port 0x340 bio irq 11 vector mcdintr

device ix0 at isa? port 0x300 net irq 5 iomem 0xc8000 iosiz 32768 vector ixintr

The Intel `softset` utility is a bit strange in that it reports addresses
with a truncated last hex 0(e.g. 0xC8000 reported as 0xC800).

>I have installaed an Intel Ether express card on a 486 based system and as soon
>as I enable the configuration it panic faults.  There is obviously something I
>have missed in the configuration od this "beast" from either the address, iomem,
>irq, etc. or have I picked an "un-doable" address (0x340 irq 11 with all other
>"stuff" at these parameters disabled i.e. NO Mitsumi second cd-rom drive).
>
>If anyone has a working set of parameters, and any infor that has been added
>to the services, networks, etc. files in etc and any data in rd.* files, I
>would sure appreciate it.
>
>Thanks in advance,
>
>Ken Miller
>
>
>