Bug 15882

Summary:	Etherexpress 16 doesn't work in 3.4 install
Product:	Base System	Reporter:	jrm <jrm>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	3.4-STABLE
Hardware:	Any
OS:	Any

Description jrm 2000-01-04 14:40:00 UTC

Can not do install with set of boot images that were current as of 12/31/99 on a machine with an Intel Etherexpress 16 set to 0x300, IRQ 10, mem 0xd0000.  Get warning about improper memory address of 0.  Ran softset2 (intel's settings utility) and properly set the mem address as well as forced card to use 10BaseT instead of autodetect (possibly choosing AUI).  Same results including warning about improper memory address.  Install continues until dhcp or static IP address is attempted, then machine hangs.  Other machines can not ping if static IP address is set.

How-To-Repeat: Run install, deselect all ethernet drivers except ie0, resolve any conflicts, attempt ftp install.  Not known if this occurs on all x86 hardware.

Comment 1 tedm 2000-01-12 09:04:55 UTC

What are the exact softset settings of the card?  Did you have
a memory window configured, and how large was it?

Ted

Comment 2 tedm 2000-03-10 07:25:30 UTC

I have duplicated this behavior on FreeBSD 3.4 with the ie driver.
The driver is recognizing the card, but it appears that it is not properly
initializing the EtherExpress16 hardware.  Link lights on the card that
are normally lit are not.  This was tested on a Win95 system that was
being upgraded - the card worked fine when Win95 was running on the system.

Also on the same hardware I have found that the 3com 3c507 is not
being recognized by the driver, the driver reports an unknown board
identifier error message, even though the driver lists support
for it.

I recommend combining this PR with PR i386/16214

Comment 3 Sheldon Hearn freebsd_committer

2000-03-10 11:13:13 UTC

State Changed
From-To: open->closed

Superseded by PR 16214.