Antonio,
thank you for your help. Unfortunately replacing +FCLASS=0 to +MS=90 or
+MS=34 in the Init2 string, don't make any difference: still "NO DIALTONE"
message.
Looking at the "Linmodem Post Install Problems" in the "troubleshooting"
section, I found this interesting suggestion:
3. NO DIALTONE message: please check your IRQ's, wrong, or conflicting.
Use setserial -agv /dev/modem and cat /proc/interrupts, the latter
should not show the IRQ reported by the former.
but setserial is not available in my system ("bash: setserial: command not
found") :\
emanuele@emanuele-desktop:~$ setserial -agv /dev/modem
Il programma «setserial» non è attualmente installato. È possibile
installarlo digitando:
sudo apt-get install setserial
bash: setserial: command not found
emanuele@emanuele-desktop:~$ cat /proc/interrupts
CPU0 CPU1 0: 156 0 IO-APIC-edge
timer
1: 9015 0 IO-APIC-edge i8042
6: 5 0 IO-APIC-edge floppy
7: 0 0 IO-APIC-edge parport0
8: 3 0 IO-APIC-edge rtc
9: 1 0 IO-APIC-fasteoi acpi
10: 0 0 IO-APIC-edge MPU401 UART
12: 164053 0 IO-APIC-edge i8042
14: 64493 0 IO-APIC-edge libata
15: 145204 0 IO-APIC-edge libata
16: 14471 0 IO-APIC-fasteoi SL1800
17: 2 0 IO-APIC-fasteoi ehci_hcd:usb1
18: 451126 0 IO-APIC-fasteoi uhci_hcd:usb2,
uhci_hcd:usb5, radeon@pci:0000:01:00.0
19: 0 0 IO-APIC-fasteoi uhci_hcd:usb3
20: 1016 0 IO-APIC-fasteoi uhci_hcd:usb4, libata
21: 749 0 IO-APIC-fasteoi eth0
22: 388 0 IO-APIC-fasteoi Intel ICH5
NMI: 0 0 LOC: 259493 221273 ERR: 0
MIS: 0
For what concerns the following suggestion, instead:
4. Still NO DIALTONE: edit /etc/wvdial.conf. By default it shows place
holders
or text for 3 Init strings (you can add more up to 7). Try to add
ATH1 as last command in last non empty string. Return to step vwdial.
I got (I think --- and hope! --- that the addition of the ATM0 command it's
not important)
emanuele@emanuele-desktop:~$ sudo wvdial
WvDial<*1>: WvDial: Internet dialer version 1.56
WvModem<*1>: Cannot get information for serial port.
WvDial<*1>: Initializing modem.
WvDial<*1>: Sending: ATZ
WvDial Modem<*1>: ATZ
WvDial Modem<*1>: OK
WvDial<*1>: Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0
WvDial Modem<*1>: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0
WvDial Modem<*1>: OK
WvDial<*1>: Sending: ATM0 ATH1
WvDial Modem<*1>: ATM0 ATH1
WvDial<*1>: Sending: ATQ0
WvDial Modem<*1>: NO CARRIER
WvDial<*1>: Re-Sending: ATM0 ATH1
WvDial Modem<*1>: ATM0 ATH1
WvDial<Err>: Modem not responding.
Now I don't have no more the "NO DIALTONE" error, but things don't look
better. Equal results are obtained using +MS=90 or +MS=34 in place of
+FCLASS=0.
I hope that someone understands why my modem don't dial if the installation
process seems ok...
Thanks, bye.
Emanuele
Antonio Olivares ha scritto:
----- Original Message ----
From: Emanuele Pagone <epagone@xxxxxxxxxxxxx>
To: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>
Cc: discuss@xxxxxxxxxxxxx
Sent: Thursday, April 10, 2008 6:01:08 PM
Subject: Re: Emanuele, Italy kernel 2.6.22-14-generic
Thanks for the help, but I'm still having problems.
I edited wvdial.conf and sl-modem-daemon as Marvin said, then I typed:
emanuele@emanuele-desktop:~$ ls -l /dev/ttySL0 /dev/pts/*
crw-rw---- 1 root uucp 136, 0 2008-04-10 23:08 /dev/pts/0
crw--w---- 1 emanuele tty 136, 1 2008-04-10 23:31 /dev/pts/1
lrwxrwxrwx 1 root root 10 2008-04-10 23:08 /dev/ttySL0 ->
/dev/pts/0
all seemed right.
Unfortunately, when I made:
emanuele@emanuele-desktop:~$ sudo wvdial
WvDial<*1>: WvDial: Internet dialer version 1.56
WvModem<*1>: Cannot get information for serial port.
WvDial<*1>: Initializing modem.
WvDial<*1>: Sending: ATZ
WvDial Modem<*1>: ATZ
WvDial Modem<*1>: OK
WvDial<*1>: Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0
WvDial Modem<*1>: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0
WvDial Modem<*1>: OK
WvDial<*1>: Modem initialized.
WvDial<*1>: Sending: ATDT0803761010
WvDial<*1>: Waiting for carrier.
WvDial Modem<*1>: ATDT0803761010
WvDial Modem<*1>: NO DIALTONE
WvDial<Err>: No dial tone.
WvDial<*1>: Disconnecting at Thu Apr 10 23:43:44 2008
I got a "NO DIALTONE" message. This is my wvdial.conf:
emanuele@emanuele-desktop:~$ cat /etc/wvdial.conf
[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0
Change this +FCLASS=0 to +MS=90 or +MS=34 and try the process again.
Maybe that is what you need.
Hope this helps,
Antonio
; Init3 = ATM0
Modem Type = Analog Modem
Baud = 460800
New PPPD = yes
Modem = /dev/ttySL0
ISDN = 0
Phone = 0803761010
Username = REMOVED
Password = REMOVED
Carrier Check = no
; Stupid Mode = yes
I removed my username and password. About the phone number, the first
digit '0' is the first part of a regional area code (I'm not passing through
a switchboard to make a call): under Ms Windows, the modem works perfectly
using that number.
I have also an ethernet card in my computer so, following what's suggested
in the "YourSystem.txt", I disconnected the RJ-45 cable and I made:
emanuele@emanuele-desktop:~/Modem$ sudo ifconfig eth0 down
emanuele@emanuele-desktop:~/Modem$ ifconfig
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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX
bytes:0 (0.0 b)
Nothing changed. I also tried to remove the X3 command from the Init2
string, but the result it's just the same: "NO DIALTONE".
What's wrong?
Thank you.
Emanuele
Marvin Stodolsky ha scritto:
Emanuele
Stop running the
$ sudo ./setup
your installation is OK now
Just do an edit:
$ sudo gedit /etc/wvdial.conf
to a final format like:
[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0
# X3 meaning "dial without dialtone detection" is often necessary in
ITALY
Modem Type = Analog Modem
Baud = 460800
New PPPD = yes
Modem = /dev/ttySL0
ISDN = 0
Phone = 3015560020
Username = LoginName@xxxxxxxxxxxxxxxx
Password = YourPassword
Carrier Check = no
# needed for /dev/pts/N modem ports
## end /etc/wvdial.conf
Also
$ sudo gedit /etc/default/sl-modem-daemon
and change
SLMODEMD_COUNTRY=USA
to
SLMODEMD_COUNTRY=ITALY
Then reboot and the modem should be automatically setup.
Check with
$ ls -l /dev/ttySL0 /dev/pts/*
whose output should include
/dev/ttySL0 --> /dev/pts/SomeNumber
If so, try dialing out with
$ sudo wvdial
MarvS
scanModem maintainer
On Wed, Apr 9, 2008 at 6:21 PM, Emanuele Pagone <epagone@xxxxxxxxxxxxx>
wrote:
Jacques,
unfortunately, I'm not able to reproduce again the message that you
highlighted:
The cause of the failure is in this message:
[ 28.192512] slamr: device 10b9:5459 is grabbed by another driver
After sending the previous email, I tried again several times to
execute "$
sudo ./setup", but I wasn't able to obtain again that message, instead
I got
another one:
emanuele@emanuele-desktop:~/slamr-2.6.22-14-generic$ sudo ./setup
installing drivers for kernel version 2.6.22-14-generic
driver=slamr
Installing the Debian packages supporting autoloading
(Lettura del database ... 176085 file e directory attualmente
installati.)
Mi preparo a sostituire sl-modem-daemon
2.9.10+2.9.9d+e-pre2-5ubuntu4 (con
sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5ubuntu4_i386.deb) ...
Shutting down SmartLink Modem driver normally probably failed.
Trying it the hard way (send SIGKILL all slmodemd processes):
Unloading
modem driver from kernel ... slamr.
Spacchetto il sostituto di sl-modem-daemon ...
Configuro sl-modem-daemon (2.9.10+2.9.9d+e-pre2-5ubuntu4) ...
L'utente «Slmodemd» già esiste come utente di sistema. Uscita.
Starting SmartLink Modem driver for: slamr0.
Creating /dev/modem symlink, pointing to: /dev/ttySL0.
Copying over newer files
Making folder /lib/modules/2.6.22-14-generic/extra
Copying drivers to /lib/modules/2.6.22-14-generic/extra
Checking driver install
slamr.ko slusb.ko ungrab-winmodem.ko
Copying newer slmodemd to /usr/sbin/
Checking slmodemd version. Should be 2.9.11
SmartLink Soft Modem: version 2.9.11 May 26 2007 13:41:57
Finished installs.
Informing the System
Starting function tests, loading drivers:
Running diagnostic:
[ 169.999471] slamr: module license 'Smart Link Ltd.' taints
kernel.
[ 170.006535] slamr: SmartLink AMRMO modem.
[ 170.009099] slamr: probe 10b9:5459 SL1800 card...
[ 170.011636] slamr: mc97 codec is SIL26
[ 170.011805] slamr: slamr0 is SL1800 card.
[ 807.310486] slamr: SmartLink AMRMO modem.
[ 807.310936] slamr: probe 10b9:5459 SL1800 card...
[ 807.313860] slamr: mc97 codec is SIL26
[ 807.314046] slamr: slamr0 is SL1800 card.
[ 1383.434767] slamr: SmartLink AMRMO modem.
[ 1383.437638] slamr: probe 10b9:5459 SL1800 card...
[ 1383.439842] slamr: mc97 codec is SIL26
[ 1383.440011] slamr: slamr0 is SL1800 card.
ports should be created by:
slmodemd -c USA /dev/slamr0
error: mdm setup: cannot open dev `/dev/slamr0': Device or resource
busy
error: cannot setup device `/dev/slamr0'
Checking for success
Running 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.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200
baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S2 S3 WvModem<*1>: Cannot get information
for
serial port.
ttySL0<*1>: ATQ0 V1 E1 -- OK
ttySL0<*1>: ATQ0 V1 E1 Z -- OK
ttySL0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttySL0<*1>: Modem Identifier: ATI -- SmartLink Soft Modem
ttySL0<*1>: Speed 4800: AT -- OK
ttySL0<*1>: Speed 9600: AT -- OK
ttySL0<*1>: Speed 19200: AT -- OK
ttySL0<*1>: Speed 38400: AT -- OK
ttySL0<*1>: Speed 57600: AT -- OK
ttySL0<*1>: Speed 115200: AT -- OK
ttySL0<*1>: Speed 230400: AT -- OK
ttySL0<*1>: Speed 460800: AT -- OK
ttySL0<*1>: Max speed is 460800; that should be safe.
ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found a modem on /dev/ttySL0.
Modem configuration written to /etc/wvdial.conf.
ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
Modem detection successful
Read wdial.txt
Then edit /etc/wvdial.conf with:
sudo gedit /etc/wvdial.conf
at the lines beginning with ; and deleting the ; < > Then dialout
with:
sudo wvdial
Running setup again is NOT necessary. Only for dialout the:
sudo wvdial
Read the Slamr.txt record, other *.txt files and the sample
wvdial.conf .
I'm a bit confused...
Anyway, if I do
emanuele@emanuele-desktop:~/slamr-2.6.22-14-generic$ sudo lsmod >
2>&1
ungrab.problem.txt
bash: syntax error near unexpected token `2'
as you can see, I get an error.
I hope you could give me some guidance. Thank you.
Emanuele
P.S.: If you are wandering why the numbers in the list of the
"Running
diagnostic:" is different than the others in the previous email, it's
just
because the list was becoming very long (I ran "./setup" a lot of
times),
and I tried to obtain a "clean" list. So I opened with gvim the
"setup" file
and I found the "dsmeg" command, and after reading its man page, I
gave
"sudo dsmeg -c", restarted the computer and made just two or three
attempts
with "./setup"... I was just trying to learn something about linux,
but I
swear to be more cautious from now :) .
Jacques Goldberg ha scritto:
The cause of the failure is in this message:
[ 28.192512] slamr: device 10b9:5459 is grabbed by another driver
Please do EXACTLY what follows:
sudo lsmod > 2>&1 ungrab.problem.txt
sudo ungrab-winmodem >> 2>&1 ungrab.problem.txt
sudo modprobe slamr >> 2>&1 ungrab.problem.txt
sudo lsmod >> 2&1 ungrab.problem.txt
sudo slmodemd -c ITALY /dev/slamr0 >> 2&1 ungrab.problem.txt
and send us the file ungrab.problem.txt which these five commands
will
produce.
Jacques
Emanuele Pagone wrote:
Jacques,
your guess is right! (sorry if you didn't understand me easily,
but I'm
not so comfortable in writing in English...): I did not run "sudo
./setup"
at all.
Now I made it (sl-modem-daemon package is NOT installed, I removed
it
completely), but there are some errors:
emanuele@emanuele-desktop:~/slamr-2.6.22-14-generic$ sudo
./setup
[sudo] password for emanuele:
installing drivers for kernel version 2.6.22-14-generic
driver=slamr
Installing the Debian packages supporting autoloading
Selezionato il pacchetto sl-modem-daemon, che non lo era.
(Lettura del database ... 176073 file e directory attualmente
installati.)
Spacchetto sl-modem-daemon (da
sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5ubuntu4_i386.deb) ...
Configuro sl-modem-daemon (2.9.10+2.9.9d+e-pre2-5ubuntu4) ...
L'utente «Slmodemd» già esiste come utente di sistema. Uscita.
Starting SmartLink Modem driver for: slamr0.
Creating /dev/modem symlink, pointing to: /dev/ttySL0.
Copying over newer files
Making folder /lib/modules/2.6.22-14-generic/extra
Copying drivers to /lib/modules/2.6.22-14-generic/extra
Checking driver install
slamr.ko slusb.ko ungrab-winmodem.ko
Copying newer slmodemd to /usr/sbin/
Checking slmodemd version. Should be 2.9.11
SmartLink Soft Modem: version 2.9.11 May 26 2007 13:41:57
Finished installs.
Informing the System
Starting function tests, loading drivers:
Running diagnostic:
[ 28.186723] slamr: module license 'Smart Link Ltd.' taints
kernel.
[ 28.192496] slamr: SmartLink AMRMO modem.
[ 28.192512] slamr: device 10b9:5459 is grabbed by another
driver
ports should be created by:
slmodemd -c USA /dev/slamr0
error: mdm setup: cannot stat `/dev/slamr0': No such file or
directory
error: cannot setup device `/dev/slamr0'
Checking for success
Port creation with slmodemd failed.
Read the Slamr.txt record, other *.txt files and the sample
wvdial.conf .
I try to translate the Italian-language lines from the terminal
output:
Selezionato il pacchetto sl-modem-daemon, che non lo era.
(Lettura del database ... 176073 file e directory attualmente
installati.)
Spacchetto sl-modem-daemon (da
sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5ubuntu4_i386.deb) ...
Configuro sl-modem-daemon (2.9.10+2.9.9d+e-pre2-5ubuntu4) ...
L'utente «Slmodemd» già esiste come utente di sistema. Uscita.
sl-modem-daemon package selected, it wasn't selected.
(Reading database ... 176073 files and directories now installed.)
Unpacking sl-modem-daemon (from
sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5ubuntu4_i386.deb) ...
Configuring sl-modem-daemon (2.9.10+2.9.9d+e-pre2-5ubuntu4) ...
«Slmodemd» user existed as system user. Exit.
If I checked the slmodemd version, the output seems good:
emanuele@emanuele-desktop:~/slamr-2.6.22-14-generic$ slmodemd
--version
SmartLink Soft Modem: version 2.9.11 May 26 2007 13:41:57
Can I move on with the last steps:
$ slmodemd --help
$ slmodemd --countrylist &> Clist.txt
If not in the USA, look for your COUNTRY_NAME therein.
Do and edit with:
$ sudo gedit /etc/default/sl-modem-daemon
and therein replace the USA in the line:
SLMODEMD_COUNTRY=USA
This will provide for the correct Country setting in the
automated:
slmodemd -c COUNTRY /dev/slamr0
?
Thanks for your help!
Emanuele
Jacques Goldberg ha scritto:
Emanuele,
In addition to my previous mail, I now think again and possibly
did
not understand what you want,
Can it be that you wrote your message below BEFORE having run
the
command sudo ./setup ? Or perhaps you did not run
sudo ./setup at all?
The correct version of slmodemd is created and installed by the
command sudo ./setup
slamr is a driver.
slmodemd is a control utility which starts the operation of the
slamr
driver in your case, or of several versions of the ALSA driver which
are not
relevant in your case.
The package sl-modem-daemon installs an obsolete version of
slmodemd
in your system.
sudo ./setup installs the right one at the same place.
The package sl-modem-daemon is NOT necessary to use your modem.
All it does is to automatically start the program slmodemd when
you
boot the computer. Without sl-modem-daemon you must type
sudo slmodemd -c ITALY /dev/slamr0
and leave slmodemd running in the window where you typed the
command
before you can use the modem
sl-modem-daemon saves you the work of typing
sudo slmodemd -c ITALY /dev/slamr0
Jacques
Jacques
Emanuele Pagone wrote:
Jacques,
first of all, thank you for your answer.
Jacques Goldberg ha scritto:
Emanuele,
Your ModemData.txt tells you what you have to do step by
step!
Have you tried to read it and apply the instructions?
Yes, I read the instructions, but what makes me ask for your
help is
the emphatized part in the text:
The modem is supported by the Smartlink slamr driver
*plus the slmodemd helper utility.* Read the
Smartlink.txt and Modem/YourSystem.txt for follow through
guidance.
Now, I don't have any slmodemd utility installed. Infact:
$ slmodemd --version
Il programma «slmodemd» non è attualmente installato. È
possibile
installarlo digitando:
sudo apt-get install sl-modem-daemon
*bash: slmodemd: command not found*
I read Smartlink.txt, but (for me) it's not enough clear about
the
way to install the slmodemd utility. I tried to install the
sl-modem-daemon
package (via Synaptic package manager), but if I understood correctly
some
previous messages, in Ubuntu there is a wrong version of the utility.
To be
sure about this, when I finished to install the sl-modem-daemon
package, I
wrote in the console:
$ slmodemd --version
and I got something like "2.9.9e" that should be wrong (infact
in
other messages I read that the right version must be 2.9.11). Am I
right?
I removed the slmodemd package, but now I don't know how to
install
the slmodemd utlity. ModemData.txt don't cover this part of the
procedure.
Can you help me?
Thanks, bye.
Emanuele
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com