Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 05 Jun 1997 08:34:34 -0500
From:      RICHARD@aaicorp.com
To:        freebsd-questions@freebsd.org
Subject:    Repost: Re: ex0 driver problem
Message-ID:  <s3967995.034@aaicorp.com>

next in thread | raw e-mail | index | archive | help
I am reposting several messages I sent to this group because our
mail server was down for a time yesterday and I never saw these
messages come in with my freebsd-questions mail.

Andreas Schulz writes
>
> Richard Dunn-Roberts writes
> > second hard drive in my PC at work.  During the configuration, I chose
> > the Intel EtherExpress 16/16TP driver (ex0) and modified the driver
>
> Use the ie0 driver. The Intel EtherExpress 16 is now integrated into the ie
> driver.
>
>
 >       ATS ( ats@first.gmd.de or ats@cs.tu-berlin.de )
>

I changed to the ie0 driver, and got the following results:

ie0: kernel configured maddr d0000 doesn't match board configured maddr 0
ie0 not found at 0x300

The next time I booted, I tried to change the maddr of the card to 0, but this
is not a valid choice.  Booting into DOS, I ran the softset utility that came with
the card to try to set maddr, but I'm not sure I did the right thing to set it.

Under the manual setup option of softset, it shows the following:
I/O address			300 - 30Fh
Interrupt			IRQ 5 (AT only)
Connector type			Auto-detect
Force 8-bit operation		No
Amount of RAM to map		None mapped
RAM start address		None mapped
FLASH/Boot ROM address	FLASH/Boot ROM disabled
FLASH remote boot program	None

Originally, the card was set up with a FLASH/Boot ROM address of 
D000h to D1FFh, but it is now disabled.  If I try to set the RAM start
address to D000h, softset reports that there is RAM or ROM at that
address, and that I should only choose that address if I plan on moving
the card to a computer without RAM or ROM at that address.  If I go
ahead anyway and set the RAM start address to 2000h, the message
that the kernel maddr does not match the board maddr goes away, but
the message ie0 not found at 0x300 remains.

I*ve confirmed that the ie0 driver is correct for EtherExpress 16/16TP,
based on comments in the driver source code, but I don*t know enough 
about FreeBSD internals, Ethernet, or the adaptor to know, from the driver 
source, what is going on.  I did call Intel Technical Support, and, while 
they do not have any suggestions on the FreeBSD side, they did suggest 
that I might want to remove the Flash ROM chip.  Does anyone know if 
this would work?  If so, why?

Any other suggestions?

PS. RobertC suggested that I change cards.  Since the machine is not mine,
I want to defer doing this until it becomes the only option.  Thanks for 
that suggestion, RobertC.

Richard Dunn-Roberts
richard@aaicorp.com, dunnro@aaicorp.com,
richard.dunn-roberts@usa.net





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?s3967995.034>