Phantom, First follow the instructions below for setting up for compiling. Separately I'll send you the modem specific package as the repository is off line for a few days. MarvS scanModem maintainer On 3/22/07, phantomissac@xxxxxxxxxxxx <phantomissac@xxxxxxxxxxxx> wrote:
Archives. YourCountry will enable Country Code guidance. Occassionally responses are blocked by an Internet Provider mail filters. So in a day, also check the Archived responses at http://www.linmodems.org . Local Linux experts can be found through: http://www.linux.org/groups/index.html -------------------------- System information ---------------------------- CPU=i686, Ubuntu 6.06 LTS Linux version 2.6.15-23-386 (buildd@rothera) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 PREEMPT Tue May 23 13:49:40 UTC 2006 scanModem update of: 2007_March_15 USB modem not detected by lsusb Modem or host audio card candidates have firmware information: PCI slot PCI ID SubsystemID Name ---------- --------- --------- -------------- 0000:00:0a.0 8086:1040 8086:1000 Communication controller: Intel Corporation 536EP Data Fax Modem Modem interrupt assignment and sharing: --- Bootup diagnositcs for card in PCI slot 0000:00:0a.0 ---- === Finished modem firmware and bootup diagnostics section. === === Next deducing cogent software === Completed candidate modem analyses. The base of the UDEV device file system is: /dev/.udev The kernel was compiled with gcc version 4.0.3 and a compiler is not installed If compiling a modem driver proves to be necessary, one of the two procedures must be followed. If not yet on the Internet, put the Dapper install CD in the drive Open a terminal and therein: $ sudo apt-get install gcc-4.0 make Additionally the package linux-headers-2.6.15-23-386 must be downloaded. Go to http://packages.ubuntu.com/ and search for linux-headers-2.6.15-23-386 After downloading, it can be installed with: $ sudo dpkg -i linux-header*.deb Or alternatively if online through Ethernet do: $ sudo apt-get update $ sudo apt-get install build-essential will do all the necessary installations mentioned above. In either installation case, set a symbolic link which will be expected later: $ sudo ln -s /usr/bin/gcc-4.0 /usr/bin/gcc After check with: $ ls -l /usr/bin/gcc* which should display: lrwxrwxrwx 1 root root 16 2006-07-09 21:53 /usr/bin/gcc -> /usr/bin/gcc-4.0 -rwxr-xr-x 1 root root 93584 2006-04-20 18:22 /usr/bin/gcc-4.0 -rwxr-xr-x 1 root root 16245 2006-04-20 18:13 /usr/bin/gccbug-4.0 Kernel-header resources needed for compiling are not manifestly ready! If compiling is necessary packages must be installed, providing: gcc-4.0 make linux-headers-2.6.15-23-386 Checking pppd properties: -rwsr-xr-- 1 root dip 257720 2006-02-23 11:33 /usr/sbin/pppd In case of an "error 17" "serial loopback" problem, see: http://phep2.technion.ac.il/linmodems/archive-sixth/msg02637.html To enable dialout without Root permission do: $ su - root (not for Ubuntu) sudo chmod a+x /usr/sbin/pppd or under Ubuntu related Linuxes sudo chmod a+x /usr/sbin/pppd Checking settings of: /etc/ppp/options asyncmap 0 auth crtscts lock hide-password modem proxyarp lcp-echo-interval 30 lcp-echo-failure 4 noipx In case of a message like: Warning: Could not modify /etc/ppp/pap-secrets: Permission denied see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html Don't worry about the following, it is for the experts should trouble shooting be necessary. ========================================================== Checking for modem support lines: -------------------------------------- /device/modem symbolic link: slmodemd created symbolic link /dev/ttySL0: Within /etc/udev/ files: /etc/udev/rules.d/60-symlinks.rules:# Create /dev/modem symlink /etc/udev/rules.d/60-symlinks.rules:KERNEL=="ttyLTM[0-9]*", SYMLINK+="modem" Within /etc/modprobe.conf files: /etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2 /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2 /etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to blacklist unwanted modem drivers /etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem /etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem Within any ancient /etc/devfs files: Within ancient kernel 2.4.n /etc/module.conf files: --------- end modem support lines --------
Attachment:
intel-536EP-2.56.76.0_23_02_2007.tgz
Description: GNU Zip compressed data
Intel modems
==============================
Vendor=8086 is Intel, Inc. producing chipsets for 536EP host controller free (HCF) modems,
537 soft modems, several AC'97 softmodem controllers and HDA (High Definition Audio) cards.
For INTEL537 and INTEL536 chipset modems, the most current support is provided at:
http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/
In 2006, Intel appears to have ceased updates for Linux. But their offical
support packages can be accessed through:
http://developer.intel.com/design/modems/support/drivers.htm
The AC'97/CNR controllers of softmodems usually do NOT use Intel software.
Rather, the modem Subsystem determines the required software support.
Subsystems with Conexant chips require hsfmodem software from http:/www.linuxant.com
Other Subsytems are currently supported by Open Source ALSA drivers plus the slmodemd helper.
The HDA cards may host softmodem chipsets, through a different bridging then the AC'97 types.
Both Conexant chip and ALSA supported chipset types have been encountered.
For the 537 class softmodems, prior to software release 2.70.95.0,
there were distinct support packages:
PCI_id SubSystem_id Older_package Comment
-------------------------------------------------------------------------------
e159:0001 8086:0003 537 TJ320 v2.0 controller
8086:1080 8086:100[7,8,A,0] 537EP 8086:1080 AC'97 controller
8086:1040 8086:1005 537SP 8086:1080 AC'97 controller
various various 537AA_secure primary AC'97 controller
over si3054 chip with SIL25 codec
si == Silicon Instruments
various various 537EA primary CNR controller
over si3038 chip with INT65 codec
--------------------------------------------------------------------------------
But all are currently supported by a single Intel-537EP package
The 537AA and EA types may be alternatively be supported by an ALSA modem driver
and the Smartlink slmodemd.
Intel-536 chipset modems have an onboard DSP (digital signal processor) chip.
They may alternatively be served by the 537EP software, with added CPU burden.
A very detailed installation report cogent to 537 type modems is at:
http://linmodems.technion.ac.il/archive-fifth/msg00541.html
For Debian like distros, a modified install script is at:
http://members.lycos.co.uk/persianlinux/downloads/intel536EP/Intel536_inst_debian
Intel 536EP Modem Driver For Fedora Core 5
from volunteer maintainer Philippe Vouters
If you have a look at 537_boot in the driver's root directory, you will
notice the device is /dev/537.
$ export MODEM_TYPE=<your 537 family type modem>
$ make 537
From a root account, you:
$ make uninstall
$ make install
$ dmesg
If you do not find any error, do proceed with the $ efax test in the
previously sent attachment. You may also recall this $ efax command
adding to the end "-t <your phone number> 537_inst". If efax answers
busy, then it does sound good. If it answers "NO DIALTONE", then check
if the modem is actually connected to a working phone line and if yes
does send your $ dmesg along with $ efax output.
If this does not work, reply with the $ efax output along with $ dmesg
output.
Note that the hamcore software is initializing with your data after a
fresh install and the modem may not be immediately responding. However
if the $ efax command works, then it should be responding on a wvdial
command.
Please do provide me with the exact command output along with $ dmesg
data. Without these, it is difficult for me to pinpoint to the actual
problem. Be also aware that in the AT+GCI=3D wvdial AT command the 3D is
for France. Read the readme.txt in the driver's root directory to find
out the correct AT+GCI command according to your country.
Also providing you attempted to install a Fedora Core 2 537EP driver
onto your Fedora Core 5 distribution, please do clean up all files.
Yours truly,
Philippe
For FC5 users under FC5, Please read prior to rebuilding the 537EP driver.
http://linmodems.org/cgi-bin/ezmlm-cgi?1:mss:23914:200607:amjpfhgkifkbjmnibmjf
<NOTICE>
Intel claiming partial source and providing binaries built on a 32-bit
Pentium aware computer, you may use the drivers ONLYon a 32-bit Linux
and a Pentium instruction set compatible processor.
The driver code also handles a SMP configuration, as found in modern
multi-core processors, such as the Opteron and Xeon processors.
</NOTICE>
1/ 536EP and 537EP installation:
First read the readme.txt file located in the detarred created directory.
Make sure your computer has all the prerequisites (kernel-devel rpm installed
in particuliar) and your /usr/src/kernels/'uname -r'/include/linux/autoconf.h
does match your processor configuration. With this, check especially for:
$ grep SMP /usr/src/kernels/'uname -r'/include/linux/autoconf.h
for CONFIG_SMP defined whereas your computer only
contains a single processor.
If you have such a mismatch, reinstall your Linux distribution from scratch.
2/ From any account, you can under the detarred created directory:
$ make clean
$ make 536
or
$ make 537
For a 537 family modem, you may have to:
$ export MODEM_TYPE=<your actual modem type>
prior to the:
$ make 537
3/ Only from a root account, you can
$ make install
or
$ make uninstall
Check with:
$ dmesg > dmesg.txt Read the dmesg.txt looking for any driver's run-time problem.
The 536EP driver has proved to work fine with efax, hylafax, wvdial, KPPP.
The 537 driver has proved to work fine on SuSE 10.1.
4/ Checking the installation.
Assuming you have a 536EP modem, you should see the following:
$ ls -l /dev/modem
lrwxrwxrwx 1 root root 10 jan 22 12:37 /dev/modem ->
/dev/536ep
$ ls -l /dev/536*
crw-rw-rw- 1 root root 240, 1 jan 22 13:08 /dev/536ep
crw-rw---- 1 root root 240, 1 jan 22 13:08 /dev/536ep0
With such /dev/536ep protection modes, your modem is ready for use by
software from any account. Such software includes efax.
Your modem being connected to a phone line, it is advised to perform the
following quick and simple check:
$ efax -v ewinchmart
wait for efax waiting for a phone call. Then abort it with
CTRL-C.
Check that driver is properly working with:
$ dmesg
5/ Testing the modem for an Internet connection with wvdial:
from a root account, gedit /etc/wvdial.conf containing information such as:
[Modem0]
Modem = /dev/modem
Baud = 115200
SetVolume = 3
Dial Command = ATDT
Init1 = ATZ
Init2 = AT+GCI=3D
Init3 = ATM1L3
Carrier Check = no
FlowControl = CRTSCTS
#Stupid Mode = yes
[Dialer tiscali]
Username = <your ISP provided user name>
Password = <your ISP provided password>
Phone = <your ISP phone number>
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Inherits = Modem0
tiscali is my Internet provider. You may replace the
string [Dialer tiscali] by
[Dialer <your provider name>].
Do not attempt to set the Baud rate to a value greater
than 115,200 bps.
Stressing TCP/IP performance tests have shown that you
will not get more overall performance, and you may cause the modem
driver to lock your computer, forcing you to power down it.
Still from a root account, test the Internet connection with the command:
$ wvdial <the provider Dialer name> &
Check if the modem correctly dials.
Check if the ppp daemon is correctly synchronizing and authenticates
you with no problem.
Providing the ppp daemon does not work correctly, then
$ kill 1%
to abort wvdial. If ppp daemon is not working properly, you might remove
in the proposed /etc/wvdial.conf file the comment on the line:
#Stupid Mode = yes
and restart
$ wvdial <the provider Dialer name> &
Check using an Internet browser, such as Firefox, that you can display
pages from the Web.
kill the wvdial program with the command:
$ kill %1
6/ Configuring with KPPP.
KPPP on Fedora Core 4 Gnome desktop can be configured clicking on
Applications->Internet->KPPP and clicking on Configure and New.
Enter the data relative to your Internet account.
For configuring the modem, in the peripheral tab:
Enter your string as the modem name.
As the peripheral device, select in the listbox: /dev/modem.
For flow control, select hardware [CRTSCTS]
End of line CR/LF
Connection speed 115200.
Do not use a lock file and select the modem response delay to
120 secondes (maximum). Unselect "wait tone before dialing" and set
"active wait" to 50 secondes.
In the modem tab, clicking on modem commands, I set my 536EP modem to
the following:
Pre-initialization delay: 100
Init String 1: ATZ
Init String 2 : <empty>
Post-initialization delay : 156
Dialing speed : 100
Response after initialization: OK
No tone detection : ATX3
Dialing string : ATDT
"Connected" Response: CONNECT
Busy Response: BUSY
No Carrier Response: NO CARRIER
No tone response: NO DIALTONE
Hangup command: +++ATH
Hangup response: OK
Modem query command: ATA
Ring response: RING
Response "Response": CONNECT
DLP response: DIGITAL LINE DETECTED
Escape string: +++
Escape response: OK
Guard time: 255
Mute/low/high volume: M0L0 M1L1 M1L3
If you freshly installed the modem and with KPPP you interrogate it
it might happen the modem does not answer ATI commands the first time.
Retrying once again, makes the modem answer.
======= end Intel section =======
MODEM TESTING This text is complemented by the Post-Install at http://linmodems.technion.ac.il Please so consult it if the following does not suffice. The wvdial package provides for an automated hardware+driver test. This utility searches through ports with syntax: /dev/ttyS* (i.e. S0, S1, SL0 etc.) and also follows a symbolic link: /dev/modem --> /dev/ModemPort If your modem port name does not satisfy these requirements already, do a console login as: su - root Make the symbolic links as: ln -sf /dev/ModemPort /dev/modem ln -sf /dev/ModemPort /dev/ttyS15 wherein /dev/ttyS15 is reserved for experimental usage. Should there be problems with wvdial version 1.54.1-1 , drop back to 1.54.0-1 For recent RedHat and Fedora releases, wvdialconf is used by the Internet Wizard. Within the pop-up menus find the Wizard. Its actions will write a configuration file: /etc/wvdial.conf For other Linux distros, open a console and login with su - root If necessary load the modem drivers: sudo modprobe DriverNames Then run the test: wvdialconf /etc/wvdial.conf Checks /dev/modem and ports /dev/ttyS*, a success at port /dev/ttySLT0 would be: ttySLT0<*1>: ATQ0 V1 E1 -- OK ttySLT0<*1>: ATQ0 V1 E1 Z -- OK ttySLT0<*1>: ATQ0 V1 E1 S0=0 -- OK ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK etc. The /etc/wvdial.conf written looks like: [Dialer Defaults] Modem = /dev/ttySLT0 Baud = 115200 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ISDN = 0 Modem Type = Analog Modem ; Phone = <Target Phone Number> ; Username = <Your Login Name> ; Password = <Your Password> For systems using the SmartLink slmodem drivers, the following line should be added to its /etc/wvdial.conf Carrier Check = no So after editing in your personal information a functional file is like: [Dialer Defaults] # lines beginning with # are Comments, not read by wvdial Modem = /dev/ttySLT0 Baud = 115200 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ## if there is problem with dial tone acquisition, add into the above line: # X3 # meaning "dial without waiting" ## for some Internet Provides, there may be problems with the new V92 mode codes. # This can be suppresses with an: # Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90 ## Within Italy it is sometimes necessary to even force a slower mode # ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=34 # This mode is also useful for PBX dialout lines. ISDN = 0 Modem Type = Analog Modem # edit in your IP's phone number below. Phone = 3334445555 # Do not use - or spaceds in the Phone = line # Introducing a pause with a , is sometimes necessary with hotel/company switchboards # Phone = 8,3334445555 or 8,,,3334445555 for s 3 second pause Username = Your_Login_Name # for MSN.net, use instead # Username = MSN/Your_Login_Name Password = Your_Password # if not using the SmartLink slmodemd, comment out with # the following line. Carrier Check = no [ Dialer 2nd_home ] Phone = 7778889999 Then dialout with $ sudo wvdial or use the 2nd dialup number with: $ sudo wvdial 2nd_home The /etc/wvdial.conf generated by the RedHat/Fedora Internet Wizard has a different format, adapted to its own dialer. This includes a line Stupid Mode = yes More informative dialup feedback May be obtained if it is commented out: # Stupid Mode = yes A dialout with wvdial will then display like: # wvdial & --> WvDial: Internet dialer version 1.53 --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 M1 S0=0 &C1 &D2 +FCLASS=0 ATQ0 V1 E1 M1 S0=0 &C1 &D2 +FCLASS=0 OK --> Modem initialized. --> Sending: ATDT3019178111 --> Waiting for carrier. ATDT3019178111 CONNECT 53333 V42bis --> Carrier detected. Waiting for prompt. ** APX1.LNH.MD.RCN.NET Terminal Server ** Login: --> Looks like a login prompt. --> Sending: LoginName LoginName Password: --> Looks like a password prompt. --> Sending: (password) Entering PPP Session. IP address is 66.44.1.6 MTU is 1006. --> Looks like a welcome message. --> Starting pppd at Sat Jul 26 13:59:03 2003 --> pid of pppd: 2404 : pppd 2.4.1 started by root, uid 0 : Using interface ppp0 : Connect: ppp0 <--> /dev/tts/LT0 Jul 26 13:59:08 stodolsklap kernel: PPP BSD Compression module registered Jul 26 13:59:08 stodolsklap kernel: PPP Deflate Compression module registered : local IP address 66.44.1.6 : remote IP address 208.59.89.132 : primary DNS address 207.172.3.8 The & in "wvdial &" puts the process into the background, allowing further usage of the command prompt. To stop a backgrounded process: # fg wvdial # Ctrl -C TROUBLE SHOOTING Check for modem driver loading. Do FIRST read INSTRUCTIONS files provided with the modem driver resource. Some may have installed to /usr/share/doc/Modem_or_Driver_Name/ For RPM using distros, documentation files will be listed through rpm -q -d packageName (less the version part, sometimes) and all directly installed files can be listed by rpm -q -l packageName Depending upon your installation, the modem drivers may/may_not be autoloaded. Login as Root in a console with: # su - root # lsmod If the modem drivers are not already loaded onto the kernel, insert them with command # sudo modprobe ModuleDriver If there are multiple drivers such as the lt_modem.o and lt_serial.o pair, commanding the serial like driver: # sudo modprobe lt_serial should autoload all modules it depends on. Check with: # lsmod This proceeds through a reading of dependency files written to /lib/modules/2.6.17.14-marv3/ during boot up through the "depmod -a" command. In constrast # insmod lt_serial would only attempt loading of that single driver and will FAIL, if its dependency on lt_modem.o has been satisfied by prior lt_modem.o insertion. Do read "man wvdial" and /usr/share/doc/vwdial documentation sometime browse the documentation that is written to /usr/share/doc/wvdial/ Therein are instructions for setting up alternative dialouts. %%% This wvdialconf action if successful generates the files: /etc/ppp/peers/wvdial /etc/ppp/peers/wvdial-pipe in addition to the /etc/wvdial.conf Many Users prefer to use the dialout utility KPPP. This is fine. But each User MUST run the configuration process separately. In principle, different Users on the same Linux System could have different Internet providers and/or use different modems. The configuration process generates a file: /home/UserFolder/.kde/share/config/kppprc Therein, non-standard modem port names can be entered, such as: [Modem] Device=/dev/ttySHSF0 for the Conexant hsfmodem port. Preparation for dialout if other COMM modes are active. --------------------------------------------------------------------------- Concurrent ethernet capability will compete for the Domain Name Service (DNS) needed for browser naviagation. So as root: # /sbin/ifconfig eth0 down before starting a dialout! With a Mandrake installation, it will be necessary to: # /etc/init.d/network stop Internet clients such as Netscape, Mozilla, Explorer etc. should be CLOSED during your first dial out trials. Should a URL on the Internet be specifed as the default URL/connect, then the Client may compete with ppp for connectivity functions. After PPP functionality has been verified, the effects of opened or launched browsers can be checked If you have installed the DIALD (dial on demand) package, stop it for initial tests: # /etc/init.d/diald stop Otherwise diald function will be initiated with modem usage, and could compilate issues. Test diald only after ppp by itself is fine. If your internet provider assigns DNS dynamically then add to /etc/ppp/options: usepeerdns To analyze a dialout attempt, it is useful to display kernel messages with: # tail -f /var/log/messages & The & puts the commanded process in the "background" allowing recovery of the command prompt. Some dialer packages (kppp etc) may automate the above steps. Note that for some Linux distributions (Mandrake for one), maintain modules in compressed module.gz format, if modem service was not specified during the Linux installation. A subsequent installation of any dialer package: wvdial - PPP dialer with built-in intelligence. kppp - PPP dialer for KDE dtmfdial - A DTMF Tone Dialer gkdial - Gtk-based PPP dial-up configuration tool. gkdial-gnome - GNOME-based PPP dial-up configuration tool. masqdialer - daemon for remote control of masqueraded dialup links pppconfig - Debian configuration toolset with command: pppconf will stimulate unpacking of ppp related modules during bootup. The cogent ppp related modules loaded during such a CONNECT are displayed within the output from: # lsmod ppp_deflate 3512 1 (autoclean) zlib_inflate 18980 0 (autoclean) [ppp_deflate] zlib_deflate 18648 0 (autoclean) [ppp_deflate] bsd_comp 4440 0 (autoclean) ppp_async 7744 1 (autoclean) ppp_generic 16380 3 (autoclean) [ppp_deflate bsd_comp ppp_async] slhc 5264 1 (autoclean) [ppp_generic For ealier 2.4.nn kernels, loading of these modules may require the following lines within /etc/module.conf : ### automate ppp modules loading ### alias /dev/ppp ppp_generic alias char-major-108 ppp_generic alias tty-ldisc-3 ppp_async alias tty-ldisc-14 ppp_synctty alias ppp-compress-21 bsd_comp alias ppp-compress-24 ppp_deflate alias ppp-compress-26 ppp_deflate ### end ppp block #### For more recent kernels with their modutils, these lines are no longer needed. For potential causes of a NO DIALTONE failure, read the Post-install.html at http://linmodems.technion.ac.il/ Not setting the Country Code may be and additional problem. COUNTRY CODE Issues ==================== The modem which you purchase locally or abroad may not be preset with the proper Country Code setting. An incorrect setting can hinder acquisition of dial tone. Inclusion of an X3 (dial without wainting) in the modem Init string of under wvdial, including in /etc/wvdial.conf a line Stupid Mode = yes Dialtone recognition depends on the setting of country and/or local phone line equipment. To properly get dialtone for your country phone experiment use AT+GCI=xx where xx is country code in hexidecimal format. Theoretically there could be 256 different countries but not all are valid. Tables in manuals are way off date, you have to write a small script to try all combinations for yourself if you can't guess by chance. After country select you can check textual name of the country it represents. For example: at+gci=00 OK ati9 Japan If you can't find exact country, choose the nearest one available. Nearby countries tend to have similar equipment and compatible dialtones. If a message like: Sep 20 09:32:42 localhost pppd[7355]: The remote system is required to authenticate itself is generated during an abort of a login, Then try adding a line to /etc/ppp/options no auth 8) After a successful CONNECT, the Domain Name Service (DNS) needed for Browser navigation can be checked with: # ping corel.com PING comcast.net (63.240.76.72): 56 data bytes 64 bytes from 63.240.76.72: icmp_seq=0 ttl=52 time=209.1 ms 64 bytes from 63.240.76.72: icmp_seq=1 ttl=52 time=189.9 ms 64 bytes from 63.240.76.72: icmp_seq=2 ttl=52 time=180.0 ms 64 bytes from 63.240.76.72: icmp_seq=3 ttl=52 time=179.9 ms # Ctrl-C aborts ping --- comcast.net ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 179.9/189.7/209.1 ms # ping 63.240.76.72 PING 63.240.76.72 (63.240.76.72): 56 data bytes 64 bytes from 63.240.76.72: icmp_seq=0 ttl=52 time=179.8 ms 64 bytes from 63.240.76.72: icmp_seq=1 ttl=52 time=190.0 ms 64 bytes from 63.240.76.72: icmp_seq=2 ttl=52 time=170.0 ms # Ctrl-C aborts ping Should there be a success with: # ping 63.240.76.72 BUT a failure with the named address: ping comcast.net Then DNS has not been acquired. Note that failure to stop ethernet service # /sbin/ifconfig eth0 down before starting a dialout, will commonly block DNS under ppp. To terminate the wvdial session, bring the action to the foreground (fg): # fg wvdial Ctrl-C to terminate: wvdial Caught signal #2! Attempting to exit gracefully... : secondary DNS address 207.172.3.9 : Terminating on signal 15. : Connection terminated. : Connect time 7.8 minutes. --> Disconnecting at Sat Jul 26 14:06:53 2003 The Debian distribution provides a utility: # pppconfig for setting up a chatscript for ppp initiation. Most dialers do use chatscripts and will produce similar records. Below is the record of a dial out initiated by: # pon : pppd 2.4.1 started by marv, uid 1000 : abort on (BUSY) : abort on (NO CARRIER) : abort on (VOICE) : abort on (NO DIALTONE) : abort on (NO DIAL TONE) : abort on (NO ANSWER) : abort on (DELAYED) : send (ATZ^M) : expect (OK) : ATZ^M^M : OK : -- got it : send (ATQ0V1E1M0S0=0W2&C1&D2+FCLASS=0^M) : expect (OK) : ^M : ATQ0V1E1M0S0=0W2&C1&D2+FCLASS=0^M^M : OK : -- got it : send (ATDT3019178111^M) : expect (CONNECT) : ^M : ATDT3019178111^M^M : CONNECT : -- got it : send (\d) : Serial connection established. : Using interface ppp0 : Connect: ppp0 <--> /dev/modem : kernel does not support PPP filtering Jul 26 14:08:39 stodolsklap kernel: PPP BSD Compression module registered Jul 26 14:08:39 stodolsklap kernel: PPP Deflate Compression module registered : local IP address 66.44.1.195 : remote IP address 208.59.89.132 : primary DNS address 207.172.3.8 Once your first CONNECT has been established, than in the future if should suffice just to use your dialer of choice: wvdial , kppp .gnomeppp or whatever. Good surfing to you. 10) GENERAL ITEMS If attemped insertion of a modem driver evokes a complaint like: unresolved symbol do_SAK_R9a0bcb74 then the kernel-headers using in compiling the modem drivers do not match those of your current kernel whose KernelVersion is displayed by: uname -r and whose kernel config file is often located at /boot/config-KernelVersion The section above "COMPILING DRIVERS, for Newbies" relates how to make corrections. There are definitely IPs whose login protocols are Linux hostile. If you cannot achieve a login, try another Internet Provider (IP). or ask for someone on discuss@xxxxxxxxxxxxx to test your IP. Many driver packages provide for loading modem drivers on bootup. Here is a description on how to set it up, if necessary: http://linmodems.technion.ac.il/archive-fourth/msg00451.html PLEASE include the diagnostic output of the following Root command in any problem reports: # setserial -agv /dev/ttyS* For instructions on having modem drivers loaded on bootup, particularly the SmartLink slmodem drivers see: http://linmodems.technion.ac.il/archive-fourth/msg00451.html For automated removel of drivers after a PPP session see: http://linmodems.technion.ac.il/archive-fourth/msg00145.html For general upto date advice: http://linmodems.technion.ac.il/ http://linmodems.technion.ac.il/resources.html available in Russian at http://linmodems.nm.ru for a general PCI_ID database http://www.pcidatabase.com/ the original Linux winmodems URL is: http://linmodems.org with a mailing list on Winmodems: discuss@xxxxxxxxxxxxx whose archives can be searched at: http://linmodems.technion.ac.il/ (near bottom of the page) There is an extensive modem database at: http://start.at/modem/ Locate your local Linux groups through: http://www.linux.org/groups/index.html USB modem information: http://www.linux-usb.org/USB-guide/x332.html Laptop users should browse http://tuxmobil.org/modem_linux_add1.html For debugging ppp: http://www.cisco.com/warp/public/471/debug_ppp_negotiation.html ---------- end FOLLOW UP STEPS ---------------
