David Maxwell wrote:
> 
> On Tue, Jun 15, 1999 at 09:37:34PM -0600, Al Urbaitis wrote:

al> > Internal modem, In DOS it shows up on com3
 
dave > Okay, as someone else said then, looks like it's being detected
dave > ok, but you have an irq conflict on 5.

Hmmm...
I took the Soundblaster out of the machine and booted 
with just the Modem installed, dmesg reported...

Copyright (c) 1996, 1997, 1998
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 1.3.2 (rebellion) #0: Tue Jul 20 18:55:39 PDT 1999
    root@rebellion:/usr/src/sys/arch/i386/compile/rebellion
cpu0: family 5 model 2 step 6
cpu0: Intel Pentium (P54C) (586-class)
real mem  = 83488768
avail mem = 79302656
using 1044 buffers containing 4276224 bytes of memory
mainbus0 (root)
pci0 at mainbus0 bus 0: configuration mode 1
pchb0 at pci0 dev 0 function 0
pchb0: Intel 82439HX System Controller (TXC) (rev. 0x01)
pcib0 at pci0 dev 7 function 0
pcib0: Intel 82371SB PCI-to-ISA Bridge (PIIX3) (rev. 0x00)
Intel 82371SB IDE Interface (PIIX3) (IDE mass storage, interface 0x80) at pci0 dev 7 function 1 not
configured
Matrox MGA Millennium 2064W ("Storm") (VGA display, revision 0x01) at pci0 dev 18 function 0 not
configured
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
com2 at isa0 port 0x3e8-0x3ef irq 5: ns16550a, working fifo
lpt0 at isa0 port 0x378-0x37b irq 7
wdc0 at isa0 port 0x1f0-0x1f7 irq 14
atapibus0 at wdc0
wd0 at wdc0 drive 0: <QUANTUM FIREBALL_TM3200A>
wd0: using 16-sector 16-bit pio transfers, lba mode
wd0: 3067MB, 6281856 sec, 512 bytes/sec
wd1 at wdc0 drive 1: <Maxtor 90845D4>
wd1: using 16-sector 16-bit pio transfers, lba mode
wd1: 8063MB, 16514064 sec, 512 bytes/sec
wdc1 at isa0 port 0x170-0x177 irq 15
atapibus1 at wdc1
cd0 at atapibus1 drive 0: <GCD-R580B, , 1.03> type 5 cdrom removable
npx0 at isa0 port 0xf0-0xff: using exception 16
pc0 at isa0 port 0x60-0x6f irq 1: color
pms0 at pc0 irq 12
pc0: console
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
isapnp0 at isa0 port 0x279: read port 0x203
isapnp0: <Internal Fax Data         , BRI1500, , > port 0x2e8/8 irq 3 not configured
biomask c040 netmask c040 ttymask d0c2
wd0: no disk label
boot device: wd1
root on wd1a dumps on wd1b
root file system type: ffs

When I remove the modem both entries go away that is ...

com2 at isa0 port 0x3e8-0x3ef irq 5: ns16550a, working fifo
isapnp0: <Internal Fax Data         , BRI1500, , > port 0x2e8/8 irq 3 not configured

are no longer present.

Perhaps you could help me with some fundamentals...
In this case dmesg seems to be telling me that there are three serial devices
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
com2 at isa0 port 0x3e8-0x3ef irq 5: ns16550a, working fifo

further it tells me that there is another device
isapnp0: <Internal Fax Data         , BRI1500, , > port 0x2e8/8 irq 3 not configured

Does this imply that the modem has multiple devices on the card. That is something
that looks like a serial port and something else (like some sort of fax machine thingy)

This would still seem to indicate a conflict between ....
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo and
isapnp0: <Internal Fax Data         , BRI1500, , > port 0x2e8/8 irq 3 not configured

So is the idea to try to change what com1 wants as an IRQ or to try to chage what
the modem (or whatever else is on the card) wants for an IRQ

al> > If the modem is not recognized as it is then what would be a reasonable approach ?
al> > Is there another way to tell NetBSD how to treat the device ?
 
dave> Yes, if you know what it is, you can add an entry to the table

dave> /usr/src/sys/dev/isapnp/isapnpdevs already contains this:
dave> devlogic        com     BRI1400         0       Boca 33.6 PnP
dave> 
dave> So I'd guess it's a Boca, not a USR. 

Yes it is a Boca (sorry about that)...

dave>Add a similar entry,
dave> do a 'make -f Makefile.isapnpdevs' in that directory, then
dave> compile a new kernel, and your device will appear cleanly
dave> at startup.
 
dave> Note that except for your irq conflict, the modem would
dave> probably work fine already. I think the devices entries are
dave> only needed for hardware that does 'special' things, but
dave> it is nice to have the name in the list anyway.

I took the SB board out and did a MAKEDEV tty2, then I rebooted and
unfortunately the machine hung where it is trying to set up
ttys.

Does this indicate anything deeper...

dave> Also, please use send-pr to report your addition so other
dave> people will see it in future...


al