From nobody@FreeBSD.org  Mon Apr 10 07:05:39 2000
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 3733137BA92
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 10 Apr 2000 07:05:39 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id HAA61601;
	Mon, 10 Apr 2000 07:05:39 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Message-Id: <200004101405.HAA61601@freefall.freebsd.org>
Date: Mon, 10 Apr 2000 07:05:39 -0700 (PDT)
From: eraxpma@verkstad.net
Sender: nobody@FreeBSD.org
To: freebsd-gnats-submit@FreeBSD.org
Subject: 3Com 3C589D and 3CCE589ET doesn't during install of 4.0-RELEASE
X-Send-Pr-Version: www-1.0

>Number:         17900
>Category:       i386
>Synopsis:       3Com 3C589D and 3CCE589ET doesn't during install of 4.0-RELEASE
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    imp
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Apr 10 07:10:01 PDT 2000
>Closed-Date:    Wed May 17 18:14:18 MDT 2000
>Last-Modified:  Wed May 17 18:15:58 MDT 2000
>Originator:     Mattias Pettersson
>Release:        4.0-RELEASE
>Organization:
Ericsson Radio Systems
>Environment:
Can't get that far...
>Description:
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.
>Fix:


>Release-Note:
>Audit-Trail:

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: eraxpma@verkstad.net
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: i386/17900: 3Com 3C589D and 3CCE589ET doesn't during install of 4.0-RELEASE 
Date: Tue, 11 Apr 2000 16:09:02 +0200

 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.
 

From: Mattias Pettersson <eraxpma@verkstad.net>
To: Sheldon Hearn <sheldonh@uunet.co.za>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: i386/17900: 3Com 3C589D and 3CCE589ET doesn't during install of 
 4.0-RELEASE
Date: Wed, 12 Apr 2000 17:31:19 +0200

 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
 
Responsible-Changed-From-To: freebsd-bugs->imp 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Thu Apr 13 00:00:39 PDT 2000 
Responsible-Changed-Why:  
The feedback provided by the originator makes this look like  
Warner's baby. 
State-Changed-From-To: open->closed 
State-Changed-By: imp 
State-Changed-When: Wed May 17 18:14:18 MDT 2000 
State-Changed-Why:  
This is a duplicate of the pccardd -i problem that iwasaki-san has fixed. 

>Unformatted:
