thanks! actually both debians are in the same disk. the modem linux driver is for 2.2, so i have to install 2.2, though i'm quite happy with 2.1.
below is part of syslog. the first n lines is about modem's modules loading. the last few lines is about dialing. kernel: hamcore module loaded kernel: ham: loading HaM PRE-Release 333-5 INT - Feb 22 2002 kernel: ham: /PCI/VENDOR_1813/DEVICE_4000/SUBSYS_00000000 on bus 0 kernel: ham: Device Class=0780 IRQ line=10 IRQ pin=1 kernel: ham: DSP base address: phys=f0412000 virt=c188a000 kernel: ham: I/O Addr1=6000 Mask=ffffff01 Range=256 kernel: hamcore_init kernel: hamcore_init:done kernel: ham:init:uart kernel: ham:init:serialdriver kernel: ham:init:serial driver registered kernel: ham:init:callout driver registered kernel: ham:init:rs_event_bh initialized kernel: CSLIP: code copyright 1989 Regents of the University of California kernel: PPP: version 2.3.7 (demand dialling) kernel: PPP line discipline registered. kernel: registered device ppp0 pppd[163]: pppd 2.3.11 started by root, uid 0 chat[164]: Can't get terminal parameters: Input/output error pppd[163]: Connect script failed pppd[163]: Exit. "Can't get terminal parameters: Input/output error" means what? ----- Original Message ----- From: "dman" <[EMAIL PROTECTED]> To: <debian-user@lists.debian.org> Sent: Friday, February 22, 2002 10:00 AM Subject: Re: 2 questions > On Fri, Feb 22, 2002 at 09:07:40AM +0800, a wrote: > | i have 2 debians: 2.1 and 2.2. the 1st question is about 2.1 and the 2nd is > | about 2.2. > > Oh, ok. If the slink box isn't too underpowered (ie a 386 with 5MB > RAM) then I recommend upgrading it. I'm currently getting my 486 box > up to woody (and kernel 2.4) to serve as a router (and maybe a > secondary MX). > > | ttyS3 is the port used by modem in MS-Windows, its irq is 10. > | i type "pon" and there is no ring from the modem. > | then i type plog. it says something like "connect script fails and exit" > > Look in /var/log/syslog then. (I think that's what 'plog' does > anyways) There should be a whole bunch of entries for each thing the > chat script did. That should at least show you how far it got before > it failed. To debug it, use 'minicom' to manually interact with the > modem and determine what sequence of expect-send pairs will configure > the modem (namely to turn off the speaker), dial the other side, and > initiate a PPP connection. When you have worked it out manually (the > interactivity of the method really helps) you can record it in a "chat > script" which 'pon' will use next time you connect. For more details > on minicom and chat scripts and the linux architecture in this area, > read the modem howto on linuxdoc.org. > > -D > > -- > > Windows, hmmm, does it come with a GUI interface that works or just > pretty blue screens? > >
