Re: agrsm048 successful connection on 2.6.33, and update for 2.6.31

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

 



On 18 March 2010 10:14, Nick <soapduk@xxxxxxxxx> wrote:
> Hi Joshua,
>
> On Thu, Mar 18, 2010 at 00:34, Joshua Gordon Crawford
> <jgcrawford@xxxxxxxxx> wrote:
>>
>> If you ran agrsm-test before wvdialconf, it would have created the
>> /dev/ttySAGR symlink, and wvdialconf should have at least tried
>> testing that. I'd like to see the output from wvdialconf, if you could
>> send it in to us.
>
> This is looking better to me: (wvdialconf)
>
> $ sudo wvdialconf
> Editing `/etc/wvdial.conf'.
>
> Scanning your serial ports for a modem.
>
> 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   S2   S3
> ttySAGR<*1>: ATQ0 V1 E1 -- OK
> ttySAGR<*1>: ATQ0 V1 E1 Z -- OK
> ttySAGR<*1>: ATQ0 V1 E1 S0=0 -- OK
> ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
> ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
> ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
> ttySAGR<*1>: Modem Identifier: ATI -- Agere SoftModem Version 2.1.40
> ttySAGR<*1>: Speed 4800: AT -- OK
> ttySAGR<*1>: Speed 9600: AT -- OK
> ttySAGR<*1>: Speed 19200: AT -- OK
> ttySAGR<*1>: Speed 38400: AT -- OK
> ttySAGR<*1>: Speed 57600: AT -- OK
> ttySAGR<*1>: Speed 115200: AT -- OK
> ttySAGR<*1>: Max speed is 115200; that should be safe.
> ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
>
> Found a modem on /dev/ttySAGR.
> Modem configuration written to /etc/wvdial.conf.
> ttySAGR<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"

Looks good. The modem is responding.

>> Actually, you _can_ test dialout without a valid account, if you are
>> delayed in getting those details. Just dialling any ISP then failing
>> to login would show that the modem works that far at least, and
>> there's usually no problems after CONNECT.
>
> Here is the log after dialing an ISP, does that look right?
>
> --> 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.
> --> Please enter password (or empty password to stop):
> --> Sending: ATM1L3DT086799209
> --> Waiting for carrier.
> ATM1L3DT086799209
> CONNECT 48000 V42bis
> --> Carrier detected.  Waiting for prompt.
> --> Connected, but carrier signal lost!  Retrying...

This is not encouraging. You've got CONNECT at a decent speed, but
then lost it. It could be that the phone line is noisy, or someone
picked up the phone. If not a physical problem like that, then maybe
you need 'Carrier Check = no' and/or 'Stupid Mode = yes' in
wvdial.conf.

> --> Sending: ATM1L3DT086799209
> --> Waiting for carrier.
>
> login:
> NO CARRIER
> --> No Carrier!  Trying again.
> --> Sending: ATM1L3DT086799209
> --> Waiting for carrier.
> ATM1L3DT086799209
>
> I'm guessing it will work with correct ISP login details now?
> Also, one question: Am I able to keep updating kernels or only within
> the 2.6.33 range? (I don't think this user on dial-up will be
> upgrading the kernal too much anyway).

I don't know what changes will be made to the kernel after 2.6.33, so
I can't guarantee anything. I will, of course, strive to update the
driver as those changes occur. I've kept this driver going through all
changes since 2.6.16 or thereabouts.

> Thanks
>
> Nick
>
>> > On Tue, Mar 16, 2010 at 23:59, Joshua Gordon Crawford <jgcrawford@xxxxxxxxx>
>> > wrote:
>> >>
>> >> Marvin, Nick, list,
>> >>
>> >> I had opportunity to do some testing today, using agrsm048 on various
>> >> kernel versions up to 2.6.33. Specifically, I have successfully
>> >> connected with 2.6.31, 2.6.31.1, 2.6.31.12, 2.6.32.2, and 2.6.33.
>> >>
>> >> It turns out my last update broke the compile on 2.6.31.*, which is
>> >> why it is not working on Nick's system. Sorry about that. Briefly, I
>> >> had made the changes applicable for 2.6.31 and later, when it should
>> >> have been 2.6.32. A patch is attached to fix that error.
>> >>
>> >> Nick, Marvin will probably have a new .deb available soon, but if you
>> >> want try it before then you can apply the patch yourself. To do so,
>> >> first save the agrsm048-2.6.32.patch.txt attached to this email, and
>> >> then:
>> >>
>> >> $ sudo cp agrsm048-2.6.32.patch.txt  /usr/src/agrsm048pci-2.1.60/patches
>> >> $ cd /usr/src/agrsm048pci-2.1.60
>> >> $ sudo patch -p0 < patches/agrsm048-2.6.32.patch.txt
>> >>
>> >> After the patch is applied, either reboot to let dkms compile and
>> >> install it for you or do so yourself with:
>> >>
>> >> $ sudo make clean
>> >> $ sudo make
>> >> $ sudo make install
>> >>
>> >> Then continue with agrsm-test and wvdialconf.
>> >> --
>> >> Joshua Crawford ... http://geocities.com/mortarn
>> >>
>> >> http://www.rewardscentral.com.au/Join/Default.aspx?refer=mortarn
>> >> Be rewarded! Join RewardsCentral today!
>> >
>> >
>>
>>
>>
>> --
>> Joshua Crawford ... http://geocities.com/mortarn
>>
>> http://www.rewardscentral.com.au/Join/Default.aspx?refer=mortarn
>> Be rewarded! Join RewardsCentral today!
>



-- 
Joshua Crawford ... http://geocities.com/mortarn

http://www.rewardscentral.com.au/Join/Default.aspx?refer=mortarn
Be rewarded! Join RewardsCentral today!


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

  Powered by Linux