Bug 17900

Summary: 3Com 3C589D and 3CCE589ET doesn't during install of 4.0-RELEASE
Product: Base System Reporter: eraxpma <eraxpma>
Component: i386Assignee: Warner Losh <imp>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.0-RELEASE   
Hardware: Any   
OS: Any   

Description eraxpma 2000-04-10 15:10:01 UTC 
589D and 589E aren't properly recognized during installation. They are
configured and things seem to be alright, but they can never receive
any packets. This makes installation over these pc-cards really tricky.
Cards worked fine under 3.4-RELEASE and installation thereof.

How-To-Repeat: Boot 4.0-RELEASE floppies on (Thinkpad 560Z) laptop. Default pc-card
io range and irq options 1 or 2 (line 2 and 3). I tried nfs installation.
Can't ping anything on VT4.
Comment 1 Sheldon Hearn 2000-04-11 15:09:02 UTC 
On Mon, 10 Apr 2000 07:05:39 MST, eraxpma@verkstad.net wrote:

> >How-To-Repeat:
> Boot 4.0-RELEASE floppies on (Thinkpad 560Z) laptop. Default pc-card
> io range and irq options 1 or 2 (line 2 and 3). I tried nfs installation.
> Can't ping anything on VT4.

What revision of /etc/pccard.conf are you using?  There appears to have
been support for both your cards for quite a while.  Could you show us
your /etc/rc.conf and the output of dmesg(8) while you're at it?

Ciao,
Sheldon.
Comment 2 eraxpma 2000-04-12 16:31:19 UTC 
Sheldon Hearn wrote:
> 
> On Mon, 10 Apr 2000 07:05:39 MST, eraxpma@verkstad.net wrote:
> 
> > >How-To-Repeat:
> > Boot 4.0-RELEASE floppies on (Thinkpad 560Z) laptop. Default pc-card
> > io range and irq options 1 or 2 (line 2 and 3). I tried nfs installation.
> > Can't ping anything on VT4.
> 
> What revision of /etc/pccard.conf are you using?  There appears to have
> been support for both your cards for quite a while.  Could you show us
> your /etc/rc.conf and the output of dmesg(8) while you're at it?
> 
> Ciao,
> Sheldon.

First of all, this happened during UPGRADE from the kern and mfsroot
floppies, so it's running /stand/sysinstall. I have not access to dmesg
or netstat and things.

Excerpt from the console during boot:
pcic0: <Intel i82365> at port 0x3e0 iomem 0xd0000 irq 10 on isa0
pcic0: management irq 10
pccard0: <PC Card bus -- kludge version> on pcic0
pccard1: <PC Card bus -- kludge version> on pcic0

pccard: card inserted, slot 0


On VT2:
DEBUG: ioctl(3, TIOCCONS, NULL) = 0 (success)
ep0: <3Com Etherlink III 3C589> at port 0x240-0x24f irq 11 slot 0 on
pccard0
ep0: Ethernet address 00:10:5a:2d:52:e6
logger: not found
/etc/pccard_ether: not found


#ifconfig -au
ep0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	inet 10.50.0.18 netmask 0xffff0000 broadcast 10.50.255.255
	ether 00:10:5a:2d:52:e6
	media: 10baseT/UTP
	supported media: 10base2/BNC 10baseT/UTP 10base5/AUI

#tcpdump -n
tcpdump: listening on ep0
^C
0 packets received by filter
0 packets dropped by kernel


I can ping my own interface address, but nothing else. Card gets
activated, since led is lit. Is pccard.conf really used when booting off
installation floppies? What I then have is the one from 3.4, but do the
installation rely on what's on the hard drive?

/Mattias
Comment 3 Sheldon Hearn freebsd_committer freebsd_triage 2000-04-13 08:00:39 UTC 
Responsible Changed
From-To: freebsd-bugs->imp

The feedback provided by the originator makes this look like  
Warner's baby.
Comment 4 Warner Losh freebsd_committer freebsd_triage 2000-05-18 01:14:18 UTC 
State Changed
From-To: open->closed

This is a duplicate of the pccardd -i problem that iwasaki-san has fixed.