Andrea,
When modem A begins a connection to modem B it dials the number of modem
B; if modem B answers it sends a sound wave with a first frequency tune;
modem A recognizes it and both modems start exchanging various tunes of
various frequencies while checking for errors in the transmission of the
tunes, until they reach an agreement on the best trade off between speed
and rate of errors (which grows as the rate grows). At the end of such a
process modem A reports on your screen the message
CONNECT 50667
which means: we modems A and B managed to connect and decided to work at 50667 bauds (bits per second) for the time being (as long as the error rate does not become wuch higher than now).
Since you got the message
CONNECT 50667
your modem is working.
The reason why you do not hear the noises which you rightly expect is that the driver software (slmodem in your case if I understood correctly) does not include the function of making this sound reach the loudspeaker of your modem. Simply, nobody needs this noise, and the author of the driver, who was not paid and did the work as a volunteer for the Linux version of this driver, did not find it useful to waste time on this feature.
The reason for the connection failure is therefore not in those sounds.
The failure has to do with the negotiation of the login procedure, which starts and does not succeed. The fact that it starts is the proof that the modem hardware and software work correctly.
The first thing to do now is to:
1-decide that during all the testing you use only directly wvdialconf and wvdialconf, and the file /etc/wvdial.conf, and not gnomeppp because this nice interface to hidden wvdial hides all details
(as happens every time a Linux GUI is created to make Linux look like Windows).
2-make sure to first run one time (at least, no more needed) the command wvdialconf /etc/wvdial.conf
(preceeded by sudo under Ubuntu and other Debian based Linux distributions). Be careful to remember that wvdialconf and gnomeppp (which uses wvdialconf) do not place the modem configuration file named wvdial.conf at the same place!
3-make sure to correctly modify the file /etc/wvdial.conf so that the Username and the Password are correctly typed.
4-that you have in this file a line
Carrier Check = no
and that you do not have a line
Stupid Mode = yes (if you have yes or 1 put no or 0)
If the login still fails, to find out why please follow, as Antonio suggested, the instructions in http://linmodems.technion.ac.il/post-install.html . Use the instructions to produce debug messages at the end (at the time the modem is trying to connnect) of the file /var/log/messages
If you do not understand the messages please copy as explained in the web page just quoted the relevant part of /var/log/messages.
Ciao
Jacques
On 09/03/2010 11:59 PM, Antonio Olivares wrote:
Andrea,
I apologize for not responding before. I saw your ModemData.txt and
from it I saw that it is apparently supported through
SLMODEMD.gcc4.4.tar.gz drivers:
This part is the one that bothers me a bit:
CodecArchived=CXT SIL22
Predictive diagnostics for card in bus 00:02.6:
Modem chipset detected on
NAME="Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller "
CLASS=0703
PCIDEV=1039:7013
SUBSYS=1558:4201
IRQ=5
SOFT=1039:7013.MC97
CodecArchived=CXT SIL22
CodecDiagnosed=SIL22
CodecClass=SIL
IDENT=slmodemd
SLMODEMD_DEVICE=modem:1
Driver=snd-intel8x0m
For candidate modem in: 00:02.6
0703 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller
Primary device ID: 1039:7013
Subsystem PCI_id 1558:4201
Softmodem codec or chipset from diagnostics: SIL22, a Smartlink type
from Archives:
This is a NEW softmodem case! Please send the output ModemData.txt
to DISCUSS@xxxxxxxxxxxxx to enrich the Archive and help others!
If further assistance is not needed, please use email Subject:
New Case Only
-------------------------------------------
Support type needed or chipset: slmodemd
An ALSA (Advanced Linux Sound Architecture) modem driver: snd-intel8x0m
provides Low Level support enabling contact with the modem hardware.
For all BUT Conexant chip soft modems (using hsfmodem software)
complementary High Level support is through a Smartlink utility: slmodemd
Download from http://linmodems.technion.ac.il/packages/smartlink/
the package SLMODEMD_gcc4.4_alsa1.0.21.tar.gz having a compiled
slmodemd. Unpack under
Linux with:
$ tar zxf SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
and read instructions therein. But briefly, the modem is setup with command:
sudo slmodemd -c YOUR_COUNTRY --alsa modem:1
reporting dynamic creation of ports:
/dev/ttySL0 --> /dev/pts/N , with N some number
Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow
through guidance.
Regards,
Antonio
On Fri, Sep 3, 2010 at 5:54 AM, andrea<andrea@xxxxxxxxxxxxxx> wrote:
i follow this thread:
<http://linmodems.org/cgi-bin/ezmlm-cgi?1:mss:36960:201009:oiheklhnmlbdpnojhdpi>
the modem seems ok, I can see it with gnomePPP, and wvdial, I even
connect to it with minicom, but id does'nt play any sound.
I even try to let it call my cell phone: I had the call but it was mute.
Does a modem wait for a tune, befor emitting sounds? I was expecting to
hear something like a fax.
Can this explain that the connection ends with a login fail?
-- gnome PPP log: --
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATX3
ATX3
OK
--> Sending: ATQ0 V1 E1 S0=0&C1&D2 +FCLASS=0
ATQ0 V1 E1 S0=0&C1&D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATM1L3DT7020005002
--> Waiting for carrier.
ATM1L3DT7020005002
CONNECT 50667
User Access Verification
Password:
--> Carrier detected. Waiting for prompt.
--> Connected, but carrier signal lost! Retrying...
--> Sending: ATM1L3DT7020005002
--> Waiting for carrier.
% Authentication failed.
Password:
% Authentication failed.
Password:
% Authentication failed.
NO CARRIER
--> No Carrier! Trying again.
--> Maximum Attempts Exceeded..Aborting!!
--> Disconnecting at Fri Sep 3 12:50:53 2010
-- end of log --
thank you
But this could be an authentication error. Which is your ISP? and did
you use the correct username and password? This might not be a driver
problem, but a post-install problem. You may read Jacques'
PostInstall howto
http://linmodems.technion.ac.il/post-install.html
Regards,
Antonio
