Subject: Re: PnP V34 Modem problem
To: None <port-i386@netbsd.org>
From: Kent Polk <kent@endicor.com>
List: port-i386
Date: 12/20/1998 21:54:57
In article <199812201921.AA27070@zel459> drochner@zel459.zel.kfa-juelich.de writes:
> 
> > on boot:
> >  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
> 
> > however:
> >  isapnp0 at isa0 port 0x279: read port 0x203
> >  isapnp0: <CIRRUS LOGIC PnP V24 MODEM, CIR3000, , > port 0x2e8/8 irq3 not config
> ured
> 
> It is simply not recognized as PnP device. You could try
> 
> Index: com_isapnp.c
> ===================================================================
> RCS file: /cvsroot/src/sys/dev/isapnp/com_isapnp.c,v
> retrieving revision 1.6.2.2
> diff -c -2 -r1.6.2.2 com_isapnp.c
> *** com_isapnp.c	1998/05/08 06:50:40	1.6.2.2
> --- com_isapnp.c	1998/12/20 19:08:07
> ***************
> *** 82,85 ****
> --- 82,86 ----
> + 	    strcmp(ipa->ipa_devlogic, "CIR3000") && /* Cirrus Logic V43 */

> In any case, once the device is known to the kernel it will
> hopefully "just work". You can still get false positives, so
> watch the boot output and use the right one.

Ok... Did the above and took out the com2 entry in the config.
It configured with IRQ4, which conflicted with the mouse. I
set the BIOS PnP settings to not use IRQ3/4 and it STILL came
up using irq4.

Pulled the board (no config info came with the board or is available
at the co's web site), figured out how to turn off PnP and set for
irq5 on the board and put the com2 entry back in the config. I.e.
I gave up on PnP figuring out the correct irq.

But it works now.

Thanks Much!