Subject: RE: Can't detect internal Modem
To: Dave Burgess <burgess@cynjut.neonramp.com>
From: Adam Glass <adamg@Exchange.Microsoft.com>
List: port-i386
Date: 07/20/2000 00:21:58
This is a multi-part message in MIME format.
------_=_NextPart_001_01BFF21B.30828684
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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.
> =09
I went out to the 56k.com website to see if I could ascertain the modem=20
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=20
get a better handle on the problems.
>=20
> On Tue, 18 Jul 2000, Manuel Bouyer wrote:
>=20
> > 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:
> > >=20
> > > Compaq Presario 336-DF 56K upgradable, interrupt 03, 02F8-02FF
> > >=20
> > > The modem works perfectly under Windows 95.
> > >=20
> > > NetBSD only detects com0 for serial port 1 at boot time, please
see the dmesg out put at the end of this message.
> > >=20
> > > 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.
> >=20
> > 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.
> >=20
>=20
------_=_NextPart_001_01BFF21B.30828684
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4408.0">
<TITLE>RE: Can't detect internal Modem</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=3D2>This is likely a ISAPNP or PNPBIOS enumerated modem =
with the device id of CPQB024 or CPQB025.</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Dave Burgess [<A =
HREF=3D"mailto:burgess@cynjut.neonramp.com">mailto:burgess@cynjut.neonram=
p.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, July 19, 2000 9:36 PM</FONT>
<BR><FONT SIZE=3D2>To: rshakin@unixfreak.org</FONT>
<BR><FONT SIZE=3D2>Cc: bouyer@antioche.lip6.fr; wqiu@webcombo.net; =
port-i386@netbsd.org;</FONT>
<BR><FONT SIZE=3D2>netbsd-help@netbsd.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: Can't detect internal Modem</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>> I would like to see the output of the pnpdump, =
that is if you have it.</FONT>
<BR><FONT SIZE=3D2>> =
</FONT>
</P>
<P><FONT SIZE=3D2>I went out to the 56k.com website to see if I could =
ascertain the modem </FONT>
<BR><FONT SIZE=3D2>type from the description below.</FONT>
</P>
<P><FONT SIZE=3D2>No such luck - Compaq doesn't even list a 336 model =
number in their</FONT>
<BR><FONT SIZE=3D2>inventory anymore. With more information, a =
definitive identification</FONT>
<BR><FONT SIZE=3D2>would be possible. There are several pointers =
to identifying modems</FONT>
<BR><FONT SIZE=3D2>on their site. Perhaps you could try a couple =
of those and see if you can </FONT>
<BR><FONT SIZE=3D2>get a better handle on the problems.</FONT>
</P>
<P><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> On Tue, 18 Jul 2000, Manuel Bouyer wrote:</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> > On Fri, Jul 14, 2000 at 01:14:43PM -0600, =
Wenning Qiu wrote:</FONT>
<BR><FONT SIZE=3D2>> > > 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:</FONT></P>
<P><FONT SIZE=3D2>> > > </FONT>
<BR><FONT SIZE=3D2>> > > Compaq =
Presario 336-DF 56K upgradable, interrupt 03, 02F8-02FF</FONT>
<BR><FONT SIZE=3D2>> > > </FONT>
<BR><FONT SIZE=3D2>> > > The modem works perfectly under =
Windows 95.</FONT>
<BR><FONT SIZE=3D2>> > > </FONT>
<BR><FONT SIZE=3D2>> > > NetBSD only detects com0 for serial =
port 1 at boot time, please see the dmesg out put at the end of this =
message.</FONT>
<BR><FONT SIZE=3D2>> > > </FONT>
<BR><FONT SIZE=3D2>> > > 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.</FONT></P>
<P><FONT SIZE=3D2>> > </FONT>
<BR><FONT SIZE=3D2>> > i guess you mean 0x2f8 here.</FONT>
<BR><FONT SIZE=3D2>> > It's possible that this is a =
"winmodem"; in which case it doesn't have an</FONT>
<BR><FONT SIZE=3D2>> > UART and NetBSD can't use it.</FONT>
<BR><FONT SIZE=3D2>> > </FONT>
<BR><FONT SIZE=3D2>> </FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01BFF21B.30828684--