Re: please help
Antonio Olivares <[email protected]> Wed, 14 Dec 2011 09:31:25 -0600
| Newsgroups | gmane.linux.linmodem |
|---|---|
| Message-ID | <CAJ5UdcMQx2yVizLxkTUX7+RuETt_eKryTfaFfafK+9UeJE1fgQ@mail.gmail.com> |
Hesham, It is getting close to working, but not quite there yet. You may well try to edit file /etc/wvdial.conf with root priviledges and add some quirks to see if it might become responsive? or restart the modem script? Try modifying /etc/wvdial to if /dev/modem does not respond try /dev/ttyAGR [Dialer Defaults] Modem =3D /dev/modem Baud =3D 57600 Init1 =3D ATZ Init2 =3D ATQ0 V1 E1 S0=3D0 &C1 &D2 Init3 =3D Area Code =3D Phone =3D PHONE_NO_GOES_HERE Username =3DYOUR_USERNAME_GOES_HERE Password =3D********** Ask Password =3D 0 Dial Command =3D ATDT Stupid Mode =3D 1 Compuserve =3D 0 Force Address =3D Idle Seconds =3D 300 DialMessage1 =3D DialMessage2 =3D ISDN =3D 0 Auto DNS =3D 1 Please try that and report back. Regards, Antonio On Wed, Dec 14, 2011 at 7:33 AM, Hesham M.Hafez <[email protected]> wrot= e: > On 12/14/2011 04:03 AM, Antonio Olivares wrote: >> >> Hesham, >> >> You are on the right path. =A0if >> # wvdialconf /etc/wvdial.conf >> >> did not find the modem, you may still check if the modem responds or >> not by using a wvdial.conf file with /dev/modem as the modem link, and >> try to connect with it, >> >> Create a file as root /etc/wvdial.conf with your favorite text editor >> with the following: >> >> [Dialer Defaults] >> Init2 =3D ATQ0 V1 E1 S0=3D0&C1&D2 +FCLASS=3D0 >> >> Modem Type =3D Analog Modem >> Phone =3D 9719099 >> ISDN =3D 0 >> Username =3D 1 >> Init1 =3D ATZ >> Password =3D 1 >> Modem =3D /dev/ttySAGR >> Baud =3D 115200 >> >> Then save it and as root type >> >> # wvdial >> >> What do you see? =A0can you connect to internet? =A0Please let us know h= ow >> we can help. >> >> Regards, >> >> >> Antonio >> >> On Tue, Dec 13, 2011 at 7:21 PM, Hesham M.Hafez<[email protected]> >> =A0wrote: >>> >>> Dear sir >>> After sending ModemData.txt =A0to you and you informed me that it's agr= sm i >>> search the net and did the following >>> >>> 1. installed all required packages gcc,dkms,.. etc and kernel-headers a= nd >>> kernel-devel >>> 2. installed agrsm-11c11040-2.1.80-20110811.tar.bz2 and followed the >>> instructions using dodkms >>> 3. laoded the modules using modprobe and made the symlinks and setseria= l >>> 4. but when I used agrs-test i got the following output >>> >>> Checking for utility wvdialconf >>> Found /usr/bin/wvdialconf, preparing to run: >>> =A0 =A0wvdialconf /etc/wvdial.conf >>> >>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >>> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>> Modem Port Scan<*1>: S1 =A0 S2 =A0 S3 >>> ttySAGR<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>> ttySAGR<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >>> ttySAGR<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>> >>> A reboot may be necessary before modem detection through: >>> =A0 =A0sudo modprobe agrserial >>> Which will load agrmodem, agrserial and create the symbolic link needed >>> for: >>> =A0 =A0sudo wvdialconf >>> >>> The installation record has been written to ./agrsm-test.txt >>> >>> 5. I tried to disable the audio from bios and use pci kernel option but >>> no >>> use >>> >>> >>> Any help will be appreciated as I'm working with this issue from 3 days >>> >>> Useful Info >>> >>> kernel version 2.6.32-71.el6.i686 >>> Distrb =A0 =A0 =A0 =A0CentOS 6 >>> >>> also I don't know if this version of the driver is compatible with the >>> kernel version or not and I need to know how can I remove this driver i= f >>> i >>> need to install another one >>> >>> Thanks in advance.... >>> >>> Best Regards > > thanks alot Antonio > I did as you said and got the following output > > [root@localhost ~]# wvdial > --> WvDial: Internet dialer version 1.60 > --> Initializing modem. > --> Sending: ATZ > --> Sending: ATQ0 > --> Re-Sending: ATZ > --> Modem not responding. > > but did I used the driver that is compatible with my current kernel > please advise since the issue drive me insane >