The solution should be simple.. you just need to assign com3 (ttyS2) to
your serial control using set serial.. here is how u do it:
This is u're serial controller.
> Serial controller: Unknown vendor Unknown device (rev 0).
> Vendor id=131f. Device id=2000.
> Medium devsel. Fast back-to-back capable. IRQ 10.
> I/O at 0x6100 [0x6101].
> the setserial for ttyS0-ttys3 shows as follows
> /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
> /dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3
> /dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
> /dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3
now link whatever com port device to /dev/modem (should be > COM2).. so say
ln -s /dev/ttyS2 /dev/modem
this will make the serial cotroller a COM3 device..
now run,
setserial /dev/modem uart 16550A port 0x6100 irq 10
and your are done!.. now select /dev/modem as your modem in kppp and check
if it queries fine :)
this is the exact procedure for any PCI h/w modem. Kernel 2.4 will do this
automagically :)
> How to check the new serial ports and where are they located.
there are no new serial ports.. all machines have 2 serial ports.. the
others are all virtual!
let us know if this works.
-sarang
>
> Thanks for the help
> Sridhar
