Mohammad, Please use wvdial instead of gppp till you know that the connection works. carefully read wvdial.txt in /Modem directory of output of scanModem if slmodemd is already running open up another terminal $ sudo wvdialconf /etc/wvdial.conf will overwrite/write /etc/wvdial.conf you should see something like [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> $ sudo gedit /etc/wvdial.conf add your own username/pasword and phone number. add a line Carrier Check = no make it look 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 Carrier Check = no I personally change Init2 to the following Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 Also you got the message: <quote> WvDial<Err>: Warning: Could not modify /etc/ppp/pap-secrets: Permission denied WvDial<Err>: --> PAP (Password Authentication Protocol) may be flaky. WvDial<Err>: Warning: Could not modify /etc/ppp/chap-secrets: Permission denied WvDial<Err>: --> CHAP (Challenge Handshake) may be flaky. </quote> Warning: Could not modify /etc/ppp/pap-secrets: Permission denied Please see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html try to dialout with $ sudo wvdial Try to connect first and then report back. Regards, Antonio On Thu, Apr 17, 2008 at 10:40 AM, moonlight <moonlighthd@xxxxxxxxx> wrote: > after i installed the slamr-2.6.22-14-generic.tar.gz > and i tried to dial using gppp i got the following > log: > > /home/mohammad/.wvdial.conf<Warn>: Ignoring malformed > input line: ";Do NOT edit this file by hand!" > WvDial<*1>: WvDial: Internet dialer version 1.56 > WvModem<*1>: Cannot 1tion for serial port. > WvDial<*1>: Initializing modem. > WvDial<*1>: Sending: ATZ > WvDial Modem<*1>: ATZ > WvDial Modem<*1>: OK > WvDial<*1>: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > WvDial Modem<*1>: OK > WvDial<*1>: Modem initialized. > WvDial<*1>: Sending: ATM1L1DT198198 > WvDial<*1>: Waiting for carrier. > WvDial Modem<*1>: ATM1L1DT198198 > WvDial Modem<*1>: CONNECT 52000 > WvDial<*1>: Carrier detected. Waiting for prompt. > WvDial Modem<*1>: ~[7f]}#@!}!'} }9}"}&} }*} } > }#}%B#}%}%}&LjH~}'}"}(}"gx~ > WvDial<*1>: PPP negotiation detected. > WvDial<Notice>: Starting pppd at Thu Apr 17 15:07:52 > 2008 > WvDial<Err>: Warning: Could not modify > > /etc/ppp/pap-secrets: Permission denied > WvDial<Err>: --> PAP (Password Authentication > Protocol) may be flaky. > WvDial<Err>: Warning: Could not modify > /etc/ppp/chap-secrets: Permission denied > WvDial<Err>: --> CHAP (Challenge Handshake) may be > flaky. > WvDial<Notice>: Pid of pppd: 5880 > WvDial<*1>: Using interface ppp0 > WvDial<*1>: Disconnecting at Thu Apr 17 15:07:56 2008 > WvDial<*1>: The PPP daemon has died: Authentication > error. > WvDial<*1>: We failed to authenticate ourselves to the > peer. > WvDial<*1>: Maybe bad account or password? (exit code > = 19) > WvDial<*1>: man pppd explains pppd error codes in more > detail. > WvDial<Notice>: I guess that's it for now, exiting > WvDial<Notice>: The PPP daemon has died. (exit code = > 19) > > > Note: forwarded message attached. > > > > > > ____________________________________________________________________________________ > Be a better friend, newshound, and > know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ > > ---------- Forwarded message ---------- > From: moonlight <moonlighthd@xxxxxxxxx> > To: Discuss@xxxxxxxxxxxxx > Date: Wed, 16 Apr 2008 09:01:49 -0700 (PDT) > Subject: mohammad, syria kernel 2.6.22-14-generic > 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.22-14-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. > They will know your Country's modem code, which may > be essential for dialup service. > 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.22-14-generic (buildd@palmer) (gcc > version 4.1.3 20070929 (prerelease) (Ubuntu > 4.1.2-16ubuntu2)) #1 SMP Sun Oct 14 23:05:12 GMT 2007 > scanModem update of: 2008_04_06 > The modem symbolic link is /dev/modem -> ttySL0 > The slmodemd set symbolic link is /dev/ttySL0 -> > /dev/pts/0 > There are no blacklisted modem drivers in > /etc/modprobe* files > USB modem not detected by lsusb > > For candidate card in slot 00:0c.0, firmware > information and bootup diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- > -------------- > 00:0c.0 10b9:5459 10a5:5459 Modem: ALi > Corporation SmartLink SmartPCI561 56K Modem > > Modem interrupt assignment and sharing: > 11: 0 XT-PIC-XT SL1800 > --- Bootup diagnostics for card in PCI slot 00:0c.0 > ---- > [ 33.806195] ACPI: PCI Interrupt 0000:00:0c.0[A] -> > Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 > [ 33.812040] 0000:00:0c.0: ttyS2 at I/O 0xe828 (irq > = 11) is a 8250 > [ 33.815311] 0000:00:0c.0: ttyS3 at I/O 0xe840 (irq > = 11) is a 8250 > [ 33.816053] Couldn't register serial port > 0000:00:0c.0: -28 > [ 29.108000] ACPI: PCI interrupt for device > 0000:00:0c.0 disabled > [ 29.924000] ACPI: PCI Interrupt 0000:00:0c.0[A] -> > Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 > > The PCI slot 00:0c.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 firmware and bootup diagnostics, next > deducing cogent software. === > > Predictive diagnostics for card in bus 00:0c.0: > Modem chipset detected on > CLASS="Class 0703: 10b9:5459" > NAME="Modem: ALi Corporation SmartLink SmartPCI561 > 56K Modem" > PCIDEV=10b9:5459 > SUBSYS=10a5:5459 > IRQ=11 > IDENT=slamr > > For candidate modem in: 00:0c.0 > Class 0703: 10b9:5459 Modem: ALi Corporation > SmartLink SmartPCI561 56K Modem > Primary PCI_id 10b9:5459 > Support type needed or chipset: slamr > > > ----------------end Softmodem section -------------- > The modem is supported by the Smartlink slamr driver > plus the slmodemd helper utility. Read the > Smartlink.txt and Modem/YourSystem.txt for follow > through guidance. > > > Download slamr-2.6.22-14-generic.tar.gz from > http://linmodems.technion.il/packages/smartlink/Ubuntu/ > under Linux, open a terminal and unpack with: > $ tar zxvf slamr*.tar.gz > Move into the unpacked folder > $ cd slamr-2.6.22-14-generic > Look around > $ ls > Run the > $ sudo ./setup > > Afterwards do: > $ slmodemd --help > $ slmodemd --countrylist &> Clist.txt > If not in the USA, look for your COUNTRY_NAME > therein. > Do and edit with: > $ sudo gedit /etc/default/sl-modem-daemon > and therein replace the USA in the line: > SLMODEMD_COUNTRY=USA > This will provide for the correct Country setting in > the automated: > slmodemd -c COUNTRY /dev/slamr0 > > Read the Smartlink.txt and YourSystem.txt > Writing Smartlink.txt > ============ end Smartlink section > ===================== > > Completed candidate modem analyses. > > The base of the UDEV device file system is: > /dev/.udev > > Versions adequately match for the compiler > installed: 4.1.3 > and the compiler used in kernel > assembly: 4.1.3 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.1 > linuc_headers base folder > /lib/modules/2.6.22-14-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. > > > > 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 package > 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 269256 2007-10-04 21:57 > /usr/sbin/pppd > > In case of an "error 17" "serial loopback" problem, > see: > > http://linmodems.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 > > > 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 6 2008-04-11 01:30 /dev/modem -> ttySL0 > slmodemd created symbolic link /dev/ttySL0: > lrwxrwxrwx 1 root root 10 2008-04-11 01:30 /dev/ttySL0 > -> /dev/pts/0 > 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/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/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/alsa-base:options snd-atiixp-modem > index=-2 > /etc/modprobe.d/alsa-base:options snd-via82xx-modem > index=-2 > /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) > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf > files: > > --------- end modem support lines -------- > > > ____________________________________________________________________________________ > Be a better friend, newshound, and > know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ > >
