Re: wvdial doesn't detect agrmodem 11c1:048c

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

 



Robin & all,

I need to rectify my statement:

From:

I have noticed that wvdial does not detect the modem ports.
 Workaround this issue by supplying the modem port.  If you have a
 symbolic link
 # ln -s /dev/ttyAGR /dev/modem

To:

I have noticed that *SOMETIMES* wvdial does not detect the modem ports.
 Workaround this issue by supplying the modem port.  If you have a
 symbolic link
 # ln -s /dev/ttyAGR /dev/modem

This has happened to me with the agrsm modems, namely 11c1:0620 and
11c1:0630 respectively, but I can still dialout with wvdial :),

This is what I tried to state below.  I am sorry for any confusion if
I caused any,

Regards,

Antonio

On 3/13/10, Antonio Olivares <olivares14031@xxxxxxxxx> wrote:
> Robin,
>
> I have noticed that wvdial does not detect the modem ports.
> Workaround this issue by supplying the modem port.  If you have a
> symbolic link
> # ln -s /dev/ttyAGR /dev/modem
>
> do a
> # ls /dev/modem -l
>
> Setup a wvdial.conf file by looking at samples from Modem/DOCs/wvdial.txt
>
> and use /dev/modem as the port(provided you have the link above)
>
> Try to connect, and then report back.  I can connect with 1cc1:0620
> and 11c1:0630 agrsm modems and wvdialconf does not appear to find them
> , but I can dialout and connect.
>
> Try that and let us know if this works or not.
>
> Regards,
>
> Antonio
>
> On 3/13/10, Robin <modem@xxxxxxxxxx> wrote:
>> Hi,
>>
>> I'm in the process of installing a WinModem from Agere/Lucent on Debian
>> Lenny.
>>
>> According to scanModem the modem's PCI ID is 11c1:048c.
>> Knowing this I successfully installed the driver from
>> agrsm048pci-2.1.60_20100106_i386.deb onto my system.
>> Inserting the created kernel modules (agrmodem & agrserial) don't give
>> any errors in /var/log/messages.
>> After confirming that /dev/ttyAGR3 exists and creating symbolic links to
>> it (/dev/ttySAGR & /dev/modem) I try to run wvdialconf to confirm that
>> everything went correctly.
>>
>> But unfortunatly wvdialconf returns the following:
>>
>>     box:/home/me# wvdialconf /etc/wvdial.conf
>>     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 -- 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.
>>
>>
>>     Sorry, no modem was detected!  Is it in use by another program?
>>     Did you configure it properly with setserial?
>>
>>     Please read the FAQ at http://open.nit.ca/wiki/?WvDial
>>
>>     If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>.
>>
>> I tried changing kernels, 2.6.30 and 2.6.32, both have the same
>> behaviour ( 2.6.26 won't compile citing an error in a struct definition).
>> Also tried various boot parameters: pci=pollirq pci=routeirq pci=noacpi
>> and disabling the on-board soundcard.
>> And i tried older versions of the driver
>> (agrsm048pci-2.1.60_20090905_i386.deb) and compiling by hand
>> (agrsm048pci-2.1.60_20100108.tar.gz)
>>
>> Seeing as there are no error message I don't know where to look for a
>> problem, can anyone point me in the right direction?
>>
>> P.S. I don't quite understand the relationship between the agrsm driver
>> and ALSA, should my modem be listed in /proc/asound/cards ? Because it
>> currently reports: --- no soundcards ---
>>
>>
>

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

  Powered by Linux