Olemis,
agrsm-test loads the drivers and then runs:
$ sudo wvdialconf
which you can do manually.
During this test Stupid Mode is not relevant.
You shouldn't have to deal with the routing table.
When you have a CONNECT, the IP will send the DNS to be used, which
will be written to /etc/resolv.conf
You should shutdown ethernet and wireless channels before trying to dialout.
On my System:
$ ifconfig
eth1 Link encap:Ethernet HWaddr 00:23:6c:84:f8:67
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::223:6cff:fe84:f867/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7072 errors:0 dropped:0 overruns:0 frame:28527
TX packets:7146 errors:6 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5166077 (5.1 MB) TX bytes:1798654 (1.7 MB)
Interrupt:23
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:960 (960.0 B) TX bytes:960
and eth1 must be shutdown before trying a dialout with:
$ sudo ifconfig eth1 down.
Otherwise the eth1 DNS will block that needed by the dialup ppp0
Please send us the full ModemData.txt from your System so we'll the
full diagnostics.
MarvS
On Mon, May 17, 2010 at 12:22 AM, Olemis Lang <olemis@xxxxxxxxx> wrote:
> Hello once again, thnx for your patience !
>
> My first attempts were performed using agrsm-test which (AFAIK) uses
> wvdial under the hood. Initially agrsm-test just hung after outputting
> S1 S2 ... to stdout and couldn't kill it using Ctrl+C :$ . After
> rebooting a few times and touching a few things (e.g. work in stupid
> mode , ...) I could make it work , but process (driver) hangs from
> time to time ... Anyway, after setting up the routing table (I'm
> curious, is it a *MUST* ? I don't imagine end-users doing that; sorry
> about the criticism but I'm just hoping there's an OOTB way to do that
> , similar to Windows perhaps; as you can imaging I'm a developer but
> also a neophyte regarding modems ;o)
>
> Q:
> - It seems I have to modprobe agrsm* KOs
> manually so that they will be loaded. Is it normal ?
> - Even if it started to work I can't hear the modem tones
> Please, how could I ?
>
> Thnx very much !!! I liked DKMS stuff . Cool !!!
>
> PS: /me trying (undocumented ?) `options` workaround (why would I use
> gedit rather than vim especially considering that green is better than
> blue ? :P )
>
> However there is no such power_save=10
>
> {{{
> #!sh
>
> $ grep "options snd-" /etc/modprobe.d/alsa-base.conf
> options snd-atiixp-modem index=-2
> options snd-intel8x0m index=-2
> options snd-via82xx-modem index=-2
> options snd-usb-audio index=-2
> options snd-usb-us122l index=-2
> options snd-usb-usx2y index=-2
> options snd-usb-caiaq index=-2
> options snd-cmipci mpu_port=0x330 fm_port=0x388
> options snd-pcsp index=-2
>
> $ grep "power_save" /etc/modprobe.d/alsa-base.conf
> }}}
>
>
> On 5/14/10, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:
>> Olemis,
>>
>> Have you done:
>> For the 11c11040 chip with kernels 2.6.31 and later a change in a
>> modules loading setting may be necessary.
>> Within the file /etc/modprobe.d/alsa-base.conf (or equivalent for
>> your Distro), change the phrase:
>> options snd-hda-intel power_save=10
>> to:
>> options snd-hda-intel power_save=0
>> or the agrsm drivers will not function. For Ubuntu related systems
>> this can be done with:
>> $ sudo gedit /etc/modprobe.d/alsa-base.conf
>>
>> Then reboot and retest.
>>
>> Please do your first testing using wvdial directly as wvdial is the
>> front end to gnome-ppp
>> Also gnome-ppp has its own setup and uses a different config file than
>> wvdial.
>>
>>
>>
>> On Fri, May 14, 2010 at 8:05 AM, Olemis Lang <olemis@xxxxxxxxx> wrote:
>>> On Thu, May 13, 2010 at 8:27 AM, Olemis Lang <olemis@xxxxxxxxx> wrote:
>>>> On Wed, May 12, 2010 at 6:52 PM, Marvin Stodolsky
>>>> <marvin.stodolsky@xxxxxxxxx> wrote:
>>>>> You don't need to compile, when using
>>>>> agrsm-11c11040_20091225_i386.deb, the DKMS system will manage all, per
>>>>> below
>>>>>
>>>>> MarvS
>>>>
>>>> Apologies, too much was included in my previous sending , so it might
>>>> have been confusing.
>>>> This is the the essential components:
>>>>
>>>
>>> Hello MarvS ! Thnx for your kindly help . I did all this and everything
>>> seems to be installed . Modem device is even detected by gnome-ppp :o)
>>> . However I hear nothing when I try to connect to the ISP and the log
>>> shows "connecting" message, and nothing else
>>>
>>> Q:
>>> - Should I install anything else to hear the tones ?
>>> - What else should I do to troubleshoot my modem connection ?
>>> - How could I know that everything is configured correctly ?
>>>
>>> Thnx in advance !
>>>
>>> --
>>> Regards,
>>>
>>> Olemis.
>>>
>>> Blog ES: http://simelo-es.blogspot.com/
>>> Blog EN: http://simelo-en.blogspot.com/
>>>
>>> Featured article:
>>>
>>
>
>
> --
> Regards,
>
> Olemis.
>
> Blog ES: http://simelo-es.blogspot.com/
> Blog EN: http://simelo-en.blogspot.com/
>
> Featured article:
>
