From nobody@FreeBSD.org  Fri Apr  7 23:12:47 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 A9BDF37C083
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  7 Apr 2000 23:12:47 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id XAA40330;
	Fri, 7 Apr 2000 23:12:47 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Message-Id: <200004080612.XAA40330@freefall.freebsd.org>
Date: Fri, 7 Apr 2000 23:12:47 -0700 (PDT)
From: dmitry@asbaikaltv.ru
Sender: nobody@FreeBSD.org
To: freebsd-gnats-submit@FreeBSD.org
Subject: pnp isa ed device problem on 4.0-RELEASE
X-Send-Pr-Version: www-1.0

>Number:         17858
>Category:       kern
>Synopsis:       pnp isa ed device problem on 4.0-RELEASE
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Apr  7 23:20:01 PDT 2000
>Closed-Date:    Wed Apr 12 01:04:35 PDT 2000
>Last-Modified:  Wed Apr 12 01:05:11 PDT 2000
>Originator:     dmitry
>Release:        4.0-RELEASE
>Organization:
>Environment:
i can't use this machine without network card :(
>Description:
when boot:
unknown0: RL2000A Compex Ethernet PNP Adapter at 0x220-0x23f irq 5 on isa0

but this device very good worked on 3.1-RELEASE, this pnpinfo out on 3.1

Checking for Plug-n-Play devices...

Card assigned CSN #1
Vendor ID CPX1501 (0x0115180e), Serial Number 0x48af5e0b
PnP Version 1.0, Vendor Version 1
Device Description: Compex RL2000A PNP Ethernet Adapter

Logical Device ID: CPX1501 0x0115180e #0
	Device powers up active
	Device supports I/O Range Check
	Vendor register funcs 00
Compatible Device ID: PNP80d6 (d680d041)
    I/O Range 0x220 .. 0x3e0, alignment 0x20, len 0x20
	[not 16-bit addr]
    IRQ: 5 10 11 12 15 IRQ: High true edge sensitive
End Tag

Successfully got 6 resources, 1 logical fdevs
-- card select # 0x0001

CSN CPX1501 (0x0115180e), Serial Number 0x48af5e0b

Logical device #0
IO:  0x0220 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
IRQ 5 0
DMA 4 4
IO range check 0x00 activate 0x01
>How-To-Repeat:
install this card ..
>Fix:
i don't know how

>Release-Note:
>Audit-Trail:

From: Peter Wemm <peter@netplex.com.au>
To: dmitry@asbaikaltv.ru
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: kern/17858: pnp isa ed device problem on 4.0-RELEASE 
Date: Sat, 08 Apr 2000 13:50:26 -0700

 dmitry@asbaikaltv.ru wrote:
 > >Number:         17858
 > >Synopsis:       pnp isa ed device problem on 4.0-RELEASE
 [..]
 > Logical Device ID: CPX1501 0x0115180e #0
 > 	Device powers up active
 > 	Device supports I/O Range Check
 > 	Vendor register funcs 00
 > Compatible Device ID: PNP80d6 (d680d041)
                         ^^^^^^^^^^^^^^^^^^
 >     I/O Range 0x220 .. 0x3e0, alignment 0x20, len 0x20
 > 	[not 16-bit addr]
 >     IRQ: 5 10 11 12 15 IRQ: High true edge sensitive
 
 Hmm.  We check for that specific compatable pnpid, it should have matched
 the if_ed driver.
 
 However, can you try a couple of things please?  First, try this patch
 and see if it makes any difference:
 
 Index: if_ed_isa.c
 ===================================================================
 RCS file: /home/ncvs/src/sys/dev/ed/if_ed_isa.c,v
 retrieving revision 1.5
 diff -u -r1.5 if_ed_isa.c
 --- if_ed_isa.c	1999/11/20 09:28:01	1.5
 +++ if_ed_isa.c	2000/04/08 20:41:41
 @@ -58,6 +58,7 @@
  	{ 0x19808c4a,	NULL },		/* RTL8019 */
  	{ 0x0090252a,	NULL },		/* JQE9000 */
  	{ 0x0020832e,	NULL },		/* KTC2000 */
 +	{ 0x0115180e,	NULL },		/* CPX1501 */
  	{ 0,		NULL }
  };
 
 cd to /sys/dev/ed and apply it with patch and reconfigure/rebuild a kernel
 and reboot.
 
 If this makes a difference, then we have a bug in our compatable device
 matching code.
 
 Can you please check your kernel config file?  You should be able to have
 'device ed' in there with no 'at isa? port ...' or anything like that.
 
 Also, if it's still not working, please try a 'boot -v' and see if the
 if_ed driver prints any clues about resource conflicts or reasons for the
 probe failure.
 
 Cheers,
 -Peter
 
 
 
State-Changed-From-To: open->closed 
State-Changed-By: sheldonh 
State-Changed-When: Wed Apr 12 01:04:35 PDT 2000 
State-Changed-Why:  
Closed on originator's request. 
>Unformatted:
