Re: Modem Data

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 8/29/09, Sreehari. T. <sreeharigvr@xxxxxxxxx> wrote:
> On 12/08/2009, Antonio Olivares <olivares14031@xxxxxxxxx> wrote:
>>
>> Sreehari,
>>
>> Do download wvstreams + wvdial:
>>
>> http://www.slax.org/modules.php?action=detail&id=624
>>
>> http://www.slax.org/modules.php?action=detail&id=368
>>
>> Regards,
>>
>>
>> Antonio
>>
>>
>> On 8/12/09, Sreehari. T. <sreeharigvr@xxxxxxxxx> wrote:
>> > I am trying from slax 6.1.2
>> > Can you post the link of wvdial ...................
>> >
>> > 2009/8/12 Antonio Olivares <olivares14031@xxxxxxxxx>
>> >
>> >> Sreehari,
>> >>
>> >> Are you trying this from Slax 6.1.1 or from Slax 6.1.2?
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> Aug 11 21:34:16 (none) /usr/sbin/gpm[5463]: *** info [startup.c(95)]:
>> >> Aug 11 21:34:16 (none) /usr/sbin/gpm[5463]: Started gpm successfully.
>> >> Entered daemon mode.
>> >> Aug 11 21:34:17 (none) acpid: client connected from 5513[0:0]
>> >> Aug 11 21:34:17 (none) acpid: 1 client rule loaded
>> >> Aug 11 21:34:21 (none) init: Switching to runlevel: 4
>> >> Aug 11 21:34:21 (none) acpid: client connected from 5710[0:0]
>> >> Aug 11 21:34:21 (none) acpid: 1 client rule loaded
>> >> Aug 11 21:34:23 (none) kernel: [drm] Initialized drm 1.1.0 20060810
>> >> Aug 11 21:34:23 (none) kernel: pci 0000:00:02.0: PCI INT A -> GSI 16
>> >> (level, low) -> IRQ 16
>> >> Aug 11 21:34:23 (none) kernel: [drm] Initialized i915 1.6.0 20060119
>> >> on
>> >> minor 0
>> >> Aug 11 21:43:04 (none) kernel: agrsm 0000:05:00.0: PCI INT A -> GSI 21
>> >> (level, low) -> IRQ 21
>> >> Aug 11 21:43:04 (none) kernel: agrsm: created 1 infos
>> >> Aug 11 21:43:04 (none) kernel: ttyAGS3 at I/O 0x1000 (irq = 21) is a
>> >> AgereModem
>> >> Aug 11 21:43:04 (none) kernel: agrserial: Loading module Agere Modem
>> >> Interface driver version 2.1.60.0.Linspire (2005-11-16)
>> >> Aug 11 21:43:37 (none) kernel: PPP generic driver version 2.4.2
>> >> Aug 11 21:43:37 (none) pppd[7870]: pppd 2.4.4 started by root, uid 0
>> >>
>> >> Hugo has reported success but by using wvdial and wvstreams modules
>> >> respectively.  Do please try with using wvdial since KPPP in this case
>> >> might be causing some problems.  If the problem still persists while
>> >> using wvdial, then there are other things that we may try to do.
>> >>
>> >> Regards,
>> >>
>> >> Antonio
>> >>
>> >>
>> >> On 8/11/09, Sreehari. T. <sreeharigvr@xxxxxxxxx> wrote:
>> >> > Dear antonio ,
>> >> > I have followed your instructions and created the asked file.
>> >> > File has been attached..........
>> >> > When the last entry to the above file was made system hanged and
>> >> > mouse
>> >> > stood stilll..........
>> >> > then i was forced to press the reset button.......
>> >> > This occurs every time i connect to net.....
>> >> > i guess that there is a mistake in my kppp configuration.........
>> >> > Please send me the correct config for BSNL(my net provider)
>> >> > INDIA........
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On 06/08/2009, Antonio Olivares <olivares14031@xxxxxxxxx> wrote:
>> >> >> Sreehari,
>> >> >>
>> >> >> When trying to connect, would you mind doing the following before
>> >> >> connecting:
>> >> >>
>> >> >> open up a terminal and run
>> >> >> # tail -f /var/log/messages
>> >> >>
>> >> >> and kppp dies with an error message, let us know what it is(back to
>> >> >> list) others may have the same problem and maybe a workaround is
>> >> >> found.  Hope this helps and also thank you for testing the driver
>> >> >> :)
>> >> >> Hopefully it is a WIN WIN situation.
>> >> >>
>> >> >> Regards,
>> >> >>
>> >> >> Antonio
>> >> >>
>> >> >> On 8/5/09, Sreehari. T. <sreeharigvr@xxxxxxxxx> wrote:
>> >> >>> Dear Antonio Olivares,
>> >> >>>
>> >> >>> Thanks For sending me the right driver............
>> >> >>> Now my modem is detected and dialing .
>> >> >>> But when "CONNECT" appears in log screen of KPPP dialer,
>> >> >>> the system hangs..........
>> >> >>> Once it showed ppp error ...........
>> >> >>> Please help me..........
>> >> >>> You are the only peson who has replied for my request..........
>> >> >>>
>> >>
>> Thanks,Thanks,Thanks,Thanks,Thanks,Thanks,Thanks,Thanks,Thanks,Thanks,Thanks,Thanks................
>> >> >>>
>> >> >>> On 27/07/2009, Antonio Olivares <olivares14031@xxxxxxxxx> wrote:
>> >> >>>> Sreehari,
>> >> >>>>
>> >> >>>> I have a confirmed report that slax can connect with the
>> >> >>>> 11c1:0620
>> >> >>>> chipset.  Here's the slax forum page:
>> >> >>>>
>> >> >>>> http://www.slax.org/forum.php?action=view&parentID=43687
>> >> >>>>
>> >> >>>> and the module that should get the job done!
>> >> >>>>
>> >> >>>> http://www.slax.org/modules.php?action=detail&id=2593
>> >> >>>>
>> >> >>>> Provided that there are no IRQ conflicts or sharing problems.  I
>> >> >>>> hope
>> >> >>>> that it does work for you.  In my case, I will be honest as I
>> >> >>>> have
>> >> >>>> not
>> >> >>>> been able to get it to work, but I have one success report and I
>> >> >>>> hope
>> >> >>>> you add to the success statistic :)
>> >> >>>>
>> >> >>>> Regards,
>> >> >>>>
>> >> >>>> Antonio
>> >> >>>>
>> >> >>>> On 7/23/09, Sreehari. T. <sreeharigvr@xxxxxxxxx> wrote:
>> >> >>>>> Modem data.txt attached with this mail..........
>> >> >>>>> Please help me to find the correct driver for my modem......
>> >> >>>>> Thanks in advance..
>> >> >>>>>
>> >> >>>>
>> >> >>>
>> >> >>
>> >> >
>> >>
>> >
>>
> I have dialed out with wvdial+wvstreams. Now the computer is not
> hanging,but
> can't connect to internet. The wvdial shown me the below information......
>
>
> root@slax:~# wvdial
> --> WvDial: Internet dialer version 1.60
>
> --> Initializing modem.
> --> Sending: ATZ
> ATZ
> OK
> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
> OK
> --> Modem initialized.
> --> Sending: ATDT172222
> --> Waiting for carrier.
> ATDT172222
> CONNECT 46666 V42bis
> --> Carrier detected.  Waiting for prompt.
> --> Connected, but carrier signal lost!  Retrying...
> --> Sending: ATDT172222
> --> Waiting for carrier.
> Welcome to UTStarcom Total Control HiPer ARC (TM)
> Networks That Go The Distance (TM)
> login:
> login:
> login:
> NO CARRIER
> --> No Carrier!  Trying again.
> --> Sending: ATDT172222
> --> Waiting for carrier.
> ATDT172222
> CONNECT 45333 V42bis
> --> Carrier detected.  Waiting for prompt.
> --> Connected, but carrier signal lost!  Retrying...
> --> Sending: ATDT172222
> --> Waiting for carrier.
> Welcome to UTStarcom Total Control HiPer ARC (TM)
> Networks That Go The Distance (TM)
> login:
> NO CARRIER
> --> No Carrier!  Trying again.
> --> Sending: ATDT172222
> --> Waiting for carrier.
> ATDT172222
> disconnect
> NO CARRIER
> --> No Carrier!  Trying again.
>
>
> Please reply soon................
>

Sreehari,

In your wvdial.conf file, do you have  a line "Carrier Check = no" ?,
if you don't please insert it and save your new wvdial.conf file and
try to connect again.  Report back to list(discuss@xxxxxxxxxxxxx) and
cc to me if you like, but others can also help you too.

Regards,

Antonio

[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux