Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 24 Jan 1999 18:29:29 -0500
From:      gkaplan <gkaplan@castle.net>
To:        Mark Ovens <marko@uk.radan.com>, Patrick Gardella <patric@cre8tivegroup.com>, freebsd-questions@FreeBSD.ORG
Subject:   Re: PnP modem installation
Message-ID:  <36ABACD9.494277FE@castle.net>
References:  <36A8A6BE.329AB17@castle.net> <36A8AAD7.80BC39BB@uk.radan.com>

next in thread | previous in thread | raw e-mail | index | archive | help
additional information:
( boot time:)
Boot: -c
FreeBSD 2.2.8-RELEASE #2
config> pnp 2 0 irq0 3 drq0 0 port0 0x2f8
config> ls
device port     irq   drq    iomem   iosize    unit    flags    enabled
...
sio0    0x3f8   4     -1     0x0        0          0       0x0     yes
sio1    0x2f8   3     -1     0x0        0          1       0x0     yes
sio2    0x3e8  5     -1     0x0        0          2       0x0     no
sio3    0x2e8  9     -1     0x0        0          3       0x0     no
...
CSN   LDN  conf   en     irqs     drqs    other (PnP devices)
  1           0    os       y      3  0    0  0      port 0x2f8
  2           0    os       y      3  0    0  4      port 0x2f8
config> quit
#dmesg | more
...
Probing for PnP devices:
CSN 1 Vendor ID YMH0030 [0x3000a865] Serial 0x80860001
PnP: override config for CSN 1 LDN 0 vend-id 0x3000a865
CSN 2 Vendor ID USR2090[0x90207256] Serial 0xffff9f80
PnP: override config for CSN 2 LDN 0 vend-id 0x9027256
sio4: type 16550A
sio4: siopnp<USR2090> sn 0xffff9f80 at 0x2f8 irq 3drq -1 flags 0x0 id 21
Probing for devices on the ISA  bus:
...
sio0: at 0x3f8-0x3ff irq 4 on isa
sio0 type 16650A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1 type 16550A
------------
changed /etc/remote to include the line
usr:dv=dev/cuaa1:br#115200:pa=none:
------------
# tip usr
connected
~.
# tip usr 4044224        # a legitimate phone number
tip: unknown host tip0
____________________________________

1.) There is still an inconstancy between  my parameter setting and my
hardware assignment.
2.) When that is cleared up I would first try to communicate with my isp using
a shell account and then a graphical browser
shell ( telnet, or minicom ) graphical browser (? navigator)
================================
Patrick Gardella wrote:

>I'm not a pnp guru, but I'll try to help.
>dmesg is reporting your modem on CSN 2.
>Your pnp command from below is trying to configure CSN 1 (hence pnp 1 0)
>
>The pnp works like this:
>pnp CSN LDN ...
>
>So I would suggest the following (in order):
>1.  if your BIOS supports PnP, try the command "pnp 2 0 enable bios"
>2.  if that doesn't work, try "pnp 2 0 enable os irq0 3 drq0 0 port0
>0x2f8"
>
>Also list the devices when you boot using -c.  It may make something clear to

>you (I once had port1 set instead of port0).
>
>No need to modify the sio.c.

>Patrick

Mark Ovens wrote:

> gkaplan wrote:
> >
> > With    kernel 2.2.8 , following suggestions in FAQ: " internal PnP
> > modem can't find"  I have the following result:
> > --------  from  dmsage  output:
> > Probe  PnP devices
> > CSN 1 Vendor ID YMH0030 [0x3000a865] Serial 0x80860001
> > CSN  2 Vendor ID USR2090 [0x90207256] Serial 0xffff9f80
> > CSN  2 is disabled
> >           ----------
> > sio1 configured irq 3 not in bitmap of probed irqs 0
> > sio1 not found at 0x2f8
> > ------------ The irq and port address agrees with values reported from
> > win95 i.e.,
> > com2  port 2f8 ns16550an
> > Identifier USR2090ISAPNP\USR2090
> > ------------
> > I have edited the table siopnp_ids[]  in  /sys/i386/isa/sio.c  to
> > include the line :
> > { 0x9020756, "USR2090"},     .
> > and then rebuilt the kernel.
> > ------------
> > The  FAQ  also mentions a pnp command:" you may have to manually
> > configure the PnP device using the 'pnp' command at boot time, with a
> > command like :
> >     'pnp 1 0 enable os irq0 3 drq0 0 port0 0x2f8'
>            ^^^
> I think you will find that this should be ``2 1'' as its Card Select
> Number is 2 and therefore it's Logical Device Number is 1.
>
> > ------- I have tried this,  with no noticeable effect.
> > ------- I was told by the modem manufacturer that this  modem is an oem
> > product and the the computer's oem  is the responsible party of the
> > installation and proper working of the modem.
> > ------- I was told by the computer oem that the modem in question is not
> > a winmodem.
> >
> > ANY SUGGESTIONS?  thank you.
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-questions" in the body of the message




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36ABACD9.494277FE>