Re: kppp setup with a wisecom - Progress

[Bruce Smith <bruce@xxxxxxxxxxx>]

> > 1)  You have COM2 disabled in your BIOS
> >     (unless it's an external modem plugged into COM2! :)
> Disabled, but I switched it to Com 4 IRQ 3 and it is working better now

COM2 & COM4 both share the same IRQ3.  Having both of those COM 
ports active could create a conflict.  Same for COM1 & COM3 (IRQ4).

> > 3)  /dev/modem is linked to /dev/ttyS1
> 
> I have /dev/modem linked to /dev/ttyS3

Right, ttyS0=COM1  ttyS1=COM2  ttyS2=COM3  ttyS3=COM4

> OK, now the point where it stops is the dialing process.  The modem has
> been moved to COM4, irq 3 and when I query it, information pops up in
> the ATI commands (which didn't happen before). When I click connect (the
> account information is in there...) it sets volume and initializes then
> goes to dial.  I hear one click but then I do not *hear* it dialing.  It
> just seems to try to keep on dialing, no further.  Does this indicate
> here that I need to play with the init strings?
> 
> This seems to be the hardest thing that I have encountered with linux.
> I will feel so much better when this modem issue is resolved!

I personally like to debug modems in minicom.

See if you can get minicom running and connect directly to the modem
and issue some AT commands.  Also try dialing MANUALLY from minicom
(do not use it dialer menu).  If your ISP's modem number is:  555-1234
then issue the command, and see if your modem dials:

ATDT5551234

--------------------------------------------
Bruce Smith                bruce@armintl.com
System Administrator / Network Administrator
Armstrong International, Inc.
Three Rivers, Michigan  49093  USA
http://www.armstrong-intl.com/
--------------------------------------------