I remember that i got a isapnp modem running on my 1.4.2 and it was fine,
but it did have jumpers, but i had it in pnp mode. 
						--Roman 

----------------------------------------- 
Roman Shakin                            
rshakin@unixfreak.org - email
(949) 651-7563 		 - pager        
(949) 655-3000 ext. 1812 - voicemail/fax


On Thu, 20 Jul 2000, Adam Glass wrote:

> 
> This is likely a ISAPNP or PNPBIOS enumerated modem with the device id
> of CPQB024 or CPQB025.
> 
> -----Original Message-----
> From: Dave Burgess [mailto:burgess@cynjut.neonramp.com]
> Sent: Wednesday, July 19, 2000 9:36 PM
> To: rshakin@unixfreak.org
> Cc: bouyer@antioche.lip6.fr; wqiu@webcombo.net; port-i386@netbsd.org;
> netbsd-help@netbsd.org
> Subject: Re: Can't detect internal Modem
> 
> 
> > I would like to see the output of the pnpdump, that is if you have it.
> > 		
> 
> I went out to the 56k.com website to see if I could ascertain the modem 
> type from the description below.
> 
> No such luck - Compaq doesn't even list a 336 model number in their
> inventory anymore.  With more information, a definitive identification
> would be possible.  There are several pointers to identifying modems
> on their site.  Perhaps you could try a couple of those and see if you
> can 
> get a better handle on the problems.
> 
> > 
> > On Tue, 18 Jul 2000, Manuel Bouyer wrote:
> > 
> > > On Fri, Jul 14, 2000 at 01:14:43PM -0600, Wenning Qiu wrote:
> > > > I've installed NetBSD 1.4.2 on my Compaq Presario 4504 and it can
> not detect the internal modem. Win95 shows the modem configuration as:
> > > > 
> > > >     Compaq Presario 336-DF 56K upgradable, interrupt 03, 02F8-02FF
> > > > 
> > > > The modem works perfectly under Windows 95.
> > > > 
> > > > NetBSD only detects com0 for serial port 1 at boot time, please
> see the dmesg out put at the end of this message.
> > > > 
> > > > I also tried to rebuild the kernel and made sure I included
> line"com1 at isa? port 0x2firq 3" in the conf file, but I got the same
> result.
> > > 
> > > i guess you mean 0x2f8 here.
> > > It's possible that this is a "winmodem"; in which case it doesn't
> have an
> > > UART and NetBSD can't use it.
> > > 
> > 
>