Subject: kern/33382: Davicom isapnp modem attachment
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <jakllsch@kollasch.net>
List: netbsd-bugs
Date: 04/27/2006 21:30:00
>Number:         33382
>Category:       kern
>Synopsis:       add devlogic for another com(4) at isapnp(4)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 27 21:30:00 +0000 2006
>Originator:     Jonathan A. Kollasch
>Release:        NetBSD 3.0
>Organization:
>Environment:
System: NetBSD kirkkit.kollasch.net 3.0 NetBSD 3.0 (GENERIC) #0: Mon Dec 19 01:04:02 UTC 2005 builds@works.netbsd.org:/home/builds/ab/netbsd-3-0-RELEASE/i386/200512182024Z-obj/home/builds/ab/netbsd-3-0-RELEASE/src/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386
>Description:
This Davicom modem I found in my stack of ISA cards didn't always attach
properly until I added a proper ISA PnP attachment.  This seems to work
with the jumper on the card set to Win95 rather than Jumperless.
>How-To-Repeat:
Find another one of this obsolete 33.6k modem and try using it.
>Fix:
Add a line like so:

devlogic       com     DAV0336         0       Davicom 33.6 PnP

to src/sys/dev/isapnp/isapnpdevs, and regenerate the .c and .h file.
Recompile kernel, and see this modem attach as a comX at isapnp0.

I did need to futz with the com port setings in my OptiPlex GX1p's BIOS
so stuff didn't conflict, but that may just be a buggy PnP implementation.