RAM, For PULSE as constrasted to Touch Tone, AT is replaced by AP So use Modem = /dev/ttySHF0 Init1 = APZ Init2 = APQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 # set the country code 53 for India with Init3 = AP+CGI=53 MarvS On Dec 5, 2007 5:17 AM, ramnarayan.k@xxxxxxxxx <ramnarayan.k@xxxxxxxxx> wrote: > Hi > > Am attaching the modemdata.txt and the wvdial.txt. > > have installed all the packages that were required. Including the free > version of the hsfmodem driver. Given below > > hsfmodem_7.68.00.04full_k2.6.20_16_generic_ubuntu_i386.deb.zip > > After that , as per the wvdial text i edited my wvdial text and included > the following lines: > > [Dialer Defaults] > # added on 5dec to try hfs modem > Modem = /dev/ttySL0 > Baud = 115200 > Init1 = ATZ > Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > ISDN = 0 > Modem Type = Analog Modem > Phone = 172233 > Username = rramnarayan > Password = XXXXXXXXX > > however i get this error message when trying wvdial > > ram@ram-laptop:~$ sudo wvdial > --> WvDial: Internet dialer version 1.56 > --> Cannot open /dev/ttySL0: No such file or directory > --> Cannot open /dev/ttySL0: No such file or directory > --> Cannot open /dev/ttySL0: No such file or directory > > so i replaced the line > Modem = /dev/ttySL0 > to > Modem = /dev.ttySHSF0 > > *AND the wvdial works* WOW > > *BUT* the phone lines here are in pulse mode and the defalu dialing is > in tone mode. > > What line do i add to change from Tone to Pulse in wvdial.conf (or any > other place) > > Am close to getting my modem to work on Linux and am *very excited* > > will much appreciate you input on this. > > regards > ram > India > > > Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server, > as HTML can contain viruses. Use as the email Subject Line: > YourName, YourCountry kernel 2.6.20-16-generic > With this Subject Line cogent experts will be alerted, and useful case names left in the Archive. > YourCountry will enable Country specific guidance. Your contry's local Linux experts > can be found through: http://www.linux.org/groups/index.html > Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an Internet Provider mail filters. > So in a day, also check the Archived responses at http://www.linmodems.org > -------------------------- System information ---------------------------- > CPU=i686, > Linux version 2.6.20-16-generic (root@terranova) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Sun Sep 23 19:50:39 UTC 2007 > scanModem update of: 2007-20-07 > The modem symbolic link is /dev/modem -> ttySHSF0 > > There are no blacklisted modem drivers in /etc/modprobe* files > > Potentially useful modem drivers now loaded are: > hsfhda > hsfusbcd2 > hsfmc97sis > hsfmc97ati > hsfmc97ali > hsfmc97via > hsfmc97ich > hsfpcibasic3 > hsfpcibasic2 > hsfserial > hsfengine > hsfosspec > hsfsoar > > > The Advanced Linux Sound Architecture (ALSA) packages providing audio support on your System, > also includes drivers for some modems. High Definition Audio (HDA) cards can themselves host > a softmodem chipset, with both audio+modem supported by a snd-hda-intel driver. > The ALSA diagnostics are written during bootup to /proc/asound/ folders. > > > The modem codec file for the the HDA card is: /proc/asound/card0/codec#1 > -------------------------------------------------------- > Codec: Conexant HSF > Address: 1 > Vendor Id: 0x14f12bfa > Subsystem Id: 0x17aa201b > Revision Id: 0x90000 > > The audio card hosts a softmodem chip with Vendor ID: 0x14f12bfa > > 14f1 is the Conexant Vendor ID, and 0x0x14f12bfa a softmodem chipset. > Get a hsfmodem package through http://www.linuxant.com > Summary card and chipset information is in: > /proc/asound/cards: > 0 [Intel ]: HDA-Intel - HDA Intel > HDA Intel at 0xee400000 irq 21 > > /proc/asound/pcm: > 00-06: Conexant HSF Modem : Conexant HSF Modem : playback 1 : capture 1 > 00-01: AD198x Digital : AD198x Digital : playback 1 > 00-00: AD198x Analog : AD198x Analog : playback 1 : capture 1 > > PCI slot 00:1b.0 has a High Definition Audio Card > USB modem not detected by lsusb > > For candidate card, firmware information and bootup diagnostics are: > > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:1b.0 8086:27d8 17aa:2010 Audio device: Intel Corporation 82801G > > Modem interrupt assignment and sharing: > 21: 87740 0 IO-APIC-fasteoi uhci_hcd:usb2, ipw3945, HDA Intel > --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- > [ 20.124000] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 21 > [ 20.124000] PCI: Setting latency timer of device 0000:00:1b.0 to 64 > [ 1362.056000] ACPI: PCI interrupt for device 0000:00:1b.0 disabled > [ 1371.320000] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 21 > [ 1371.320000] PCI: Setting latency timer of device 0000:00:1b.0 to 64 > [ 1374.088000] ACPI: PCI interrupt for device 0000:00:1b.0 disabled > [ 1375.472000] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 21 > [ 1375.472000] PCI: Setting latency timer of device 0000:00:1b.0 to 64 > > The PCI slot 00:1b.0 of the modem card may be disabled early in > a bootup process, but then enabled later. If modem drivers load > but the modem is not responsive, read Bootup.txt about possible fixes. > Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx > if help is needed. > > > === Finished modem firmware and bootup diagnostics section. === > === Next deducing cogent software === > > The High Defintion Audio card with PCI ID 8086:27d8 may host a soft modem chip. > > There is candidate modem software. > > Completed candidate modem analyses. > > The base of the UDEV device file system is: /dev/.udev > > Versions adequately match for the compiler installed: 4.1.2 > and the compiler used in kernel assembly: 4.1.2 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.1 > linuc_headers base folder /lib/modules/2.6.20-16-generic/build > > However some compilations and executable functions may need additional files, > in the FileNames.h (so called kernel "h"eaders) collection installed in /usr/include/ . > For martian_modem, additional required packages are libc6-dev (and for Debian/Ubuntu, linux-libc-dev). The also required headers of package libc6 are commonly installed by default. > > Compressed files at: /usr/src/cdfs.tar.bz2 > > > If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), then > Some additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-dev > and any of its dependents, under Ubuntu linux-libc-dev > > If an alternate ethernet connection is available, > $ apt-get update > $ apt-get -s install linux-kernel-devel > will install needed pacakage > For Debian/Ubuntu related distributions, run the following command to display the needed package list: > > Otherwise packages have to be found through http://packages.ubuntu.com > Once downloaded and transferred into a Linux partition, > they can be installed alltogether with: > $ sudo dpkg -i *.deb > > > Checking pppd properties: > -rwsr-xr-- 1 root dip 269224 2007-04-05 09:11 /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 > noauth > 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 > > Read Modem/YourSystem.txt concerning other COMM channels: eth0 eth0:avah > Which can interfere with Browser naviagation. > > Don't worry about the following, it is for the experts > should trouble shooting be necessary. > ========================================================== > > # start/stop the daemon when the USB modem is connected > KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon" > Checking for modem support lines: > -------------------------------------- > /device/modem symbolic link: lrwxrwxrwx 1 root root 8 2007-12-05 11:20 /dev/modem -> ttySHSF0 > slmodemd created symbolic link /dev/ttySL0: > Within /etc/udev/ files: > /etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected > /etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon" > /etc/udev/rules.d/00-hsf.rules:KERNEL=="ttySHSF0", SYMLINK="modem" > /etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected > /etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon" > 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/hsf.conflicts:install snd-via82xx-modem /bin/true # temporarily disabled by hsf - conflicts with hsfmc97via > /etc/modprobe.d/hsf.conflicts:install snd-atiixp-modem /bin/true # temporarily disabled by hsf - conflicts with hsfmc97ati > /etc/modprobe.d/sl-modem-daemon.modutils:install slamr modprobe --ignore-install ungrab-winmodem ; modprobe --ignore-install slamr; test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0) > /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 > /etc/modprobe.d/hsf:alias /dev/modem /dev/ttySHSF > Within any ancient /etc/devfs files: > /etc/devfs/conf.d/hsf.conf:LOOKUP ^(ttySHSF[0-9]|modem$) EXECUTE nice /sbin/modprobe /dev/ttySHSF > /etc/devfs/conf.d/hsf.conf:REGISTER ^ttySHSF0$ CFUNCTION GLOBAL symlink $devname modem > /etc/devfs/conf.d/hsf.conf:UNREGISTER ^ttySHSF0$ CFUNCTION GLOBAL unlink modem > Within ancient kernel 2.4.n /etc/module.conf files: > > --------- end modem support lines -------- > > > > > Modem usage is accomplished through drivers, sometimes some helper software, > and the core communication work horse "pppd". Usually it will be found at > /usr/sbin/pppd with permissions shown on my Ubuntu system by: > $ ls -l /usr/sbin/pppd > -rwsr-xr-- 1 root dip 257720 2006-07-05 08:58 /usr/sbin/pppd > The s means "sticky" meaning only one person can use pppd at a time. > As installed, it requires Root/Adm permissions to use pppd, directly or > through front end dialer tools. This is a security precaution common to > all COMM channels. But if you want to enable a simple User to dialout, > as is basically OK for a single user PC, do: > $ su - root > # chmod a+x /usr/sbin/pppd > or for Ubuntu: > $ sudo chmod a+x /usr/sbin/pppd > after which there will be seen: > $ ls -l /usr/sbin/pppd > -rwsr-xr-x 1 root dip 257720 2006-07-05 08:58 /usr/sbin/pppd > with the last x meaning any one can execute pppd, either directly or > much more commonly through a front end dialer such as wvdial of KPPP. > > Configuration file for wvdial > ------------------------------- > There is a very smart dialer utility "wvdial" > which can be used once basic modem setup is accomplished. A configuration file > is needed, which begins below with [Dialer defaults]. This file can be accessed > any where by: > $ wvdial --config Path_to/configuration_file > Most commonly the configuration file is saved as: > /etc/wvdial.conf > whereat it will serve all Users of the computer. If saved as: > /home/LoginName/.wvdial.rc > it will be found and used before /etc/wvdial.conf. Note that "." beginning > a file name means "do not show it", excess through usage of: > $ ls -a > Many local configuration files are thus "hidden" in your /home/LoginName/ folder > > Some Linux installations have dialup tools like Kinternet, GnomePPP, and the > Redhat/Fedora Internet Connection Wizard which are front ends for wvdial and > will write /etc/wvdial.conf files. For this reason, it is advisable to test > your configuration file first, before copying it to /etc/wvdial.conf. Typically > a first test is run with: > $ sudo wvdialconf wvtest > WvModem<*1>: Cannot get information for serial port. > ttySL0<*1>: ATQ0 V1 E1 -- OK > ttySL0<*1>: ATQ0 V1 E1 Z -- OK > ttySL0<*1>: ATQ0 V1 E1 S0=0 -- OK > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK > ttySL0<*1>: Modem Identifier: ATI -- SmartLink Soft Modem > ttySL0<*1>: Speed 4800: AT -- OK > ttySL0<*1>: Speed 9600: AT -- OK > ttySL0<*1>: Speed 19200: AT -- OK > ttySL0<*1>: Speed 38400: AT -- OK > ttySL0<*1>: Speed 57600: AT -- OK > ttySL0<*1>: Speed 115200: AT -- OK > ttySL0<*1>: Speed 230400: AT -- OK > ttySL0<*1>: Speed 460800: AT -- OK > ttySL0<*1>: Max speed is 460800; that should be safe. > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK > > Found a modem on /dev/ttySL0. > Modem configuration written to wvtest. > ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" > ------ > will be included in a successful run, where in this case /dev/ttySL0 > is the responding device port. The generated wvtest file is: > [Dialer Defaults] > Modem = /dev/ttySL0 > Baud = 460800 > 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> > > which at a minimim must be edited to a form like: > [Dialer Defaults] > Modem = /dev/ttySL0 > Baud = 115200 > Init1 = ATZ > Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > ISDN = 0 > Modem Type = Analog Modem > Phone = 3334445555 > Username = Your_Login_Name > Password = Your_Password > > Additional if your modem port is of the type /dev/pts/N , with N a number, > then there MUST be added a line: > Carrier Check = no > This requirement currently applies to dialups using the helper utility: slmodemd > together with slamr, slusb or ALSA modem drivers, OR the " " : martian_helper > used with the martian_dev for Lucent/Agere modems with DSP chipsets. > > Then a test dialput can be done with: > $ sudo wvdial --config wvtest > > There are some Systems for which the wvdialcon test will stall at rfcomm ports. > This is a wvdialconf bug and can be bypassed by just using wvdial with a trial > wvtest, but you need to specify the port appropriate to your modem. > > If the configuration file below, lines beginning with # are comments. > Removing a # will activate a line with wvdial instructions appropriate to > special circumstances. > > > [Dialer defaults] > # Lines begining with # are comments. > # wvdial will look for this file at /etc/wvdial.conf or /home/LoginName/.wvdial.rc > > # Redhat/Fedora have an Internet Connection Wizard in the popup menus > # ICW will write a two part /etc/wvdial.conf supporting multiple modem usage. > > Modem = /dev/ttySL0 > Init1 = ATZ > Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > # Lack of dialtone acquisition can be due to low line voltage, > # a common problem in Italy. > # Try inserting a "dial without waiting": X3 > # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0 > # In case of connection instabilities, specify a lower frequency: > # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=34 > # a MS=90 option is sometimes necessary for Internet Providers with buggy V92 protocols: > # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > ISDN = 0 > Modem Type = Analog Modem > Phone = Dialout_phone_number > # if going through a switch board, a perhaps necessary pause can produced with a comma: > # Phone = 1,Dialout_phone_number > Username = LoginName > # if Internet Provider is MSN.net, use under Linux: MSN/LoginName > Password = YourPassWord > > # the following lines is NEEDED only for usage with slmodemd or martian_helper > Carrier check = no > # Kinternet appears to add it automatically. > > ## If CONNECT is achieved but browsing fails, try activating the following line > # Auto DNS = yes > ## To make a logfile wvdial.out > # wvdial 2>&1 | tee wvdial.out > # # For some Internet providers, the following line is necessary > # Stupid Mode = yes > ## for other wvdial options, do "man wvdial" or see the documentation in > ## /usr/share/doc/wvdial/ > > # to dial an alternate provide use "wvdial 2nd" which will preferentially read: > [Dialer 2nd] > Phone = 2nd_phone_number > Username = 2nd_LoginName > Password = 2nd_PassWord > > ## End wvdial config file > > > >
