I am having trouble dialing with my ISA PnP InModem 336.
The Modem HOW TO says that if I have a PnP Modem
a PnP BIOS, and installed PnP Linux (version 2.2) then
I should be able to use the modem right away. When
using ezppp to dial my ISP, however, ezppp complains
that it can't open the device (cua2 or ttyS2 - which is the
COM port (3) that Windows 98 claims the modem is
installed in).
I tried the following:
> setserial -g /dev/ttyS2
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
so something was definitely wrong.
The HOWTO suggested I look through the isapnp.conf
file. Here is the relevant section:
___
# Card 2: (serial identifier 95 00 03 ba cb 03 03 49 0a)
# Vendor Id BRI0303, Serial Number 244427, checksum 0x95.
# ANSI string -->InModem 336 SVD <--
# Version 1.0, Vendor version 0.0
#
# Logical device id BRI0303
# Device support I/O range check register
# Device supports vendor reserved register @ 0x3a
# Device supports vendor reserved register @ 0x3c
# Device supports vendor reserved register @ 0x3d
#
# Edit the entries below to uncomment out the configuration required.
# Note that only the first value of any range is given, this may be changed
if required
# Don't forget to uncomment the activate (ACT Y) when happy
(CONFIGURE BRI0303/244427 (LD 4
# Multiple choice time, choose one only !
# Start dependent functions: priority acceptable
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x03f8
# Maximum IO base address 0x03f8
# IO base alignment 8 bytes
# Number of IO addresses required: 8
(IO 0 (BASE 0x03f8))
# IRQ 4.
# High true, level sensitive interrupt
(INT 0 (IRQ 4 (MODE +L)))
*snip*
# End dependent functions
(ACT Y)
))
# End tag... Checksum 0x00 (OK)
# Returns all cards to the "Wait for Key" state
(WAITFORKEY)
___
So I did the following:
> setserial -v /dev/ttyS2 port 0x03f8 autoconfig
Cannot set serial info: Address already in use
Which seemed strange to me. Especially after getting
this:
> setserial -g /dev/ttyS2
/dev/ttyS2, UART: 16550A, Port: 0x03f8, IRQ: 4
The result wasn't the same as before (where the UART
was given as unknown), but according to the HOWTO
this is the result I was suppose to get - so I assumed it
was OK.
Now back to using ezppp:
ezppp no longer complains about being unable to open
the device. Instead it says:
Initializing Modem
Expecting: OK
Then it freezes.
Have I done something wrong?
Help appreciated.
John
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
