I managed to connect normally through Marvin's instructions, I'm
sending the latest ModemData.txt attached as requested.
---------
These are the messages produced by the last instructions I received:
---------
elven@ubuntu:~$ lsmod|grep slamr
slamr 425538 2
elven@ubuntu:~$ ls -l /dev/pts/* /dev/ttysl0
ls: impossível acessar /dev/ttysl0: Arquivo ou diretório não encontrado
crw--w---- 1 elven tty 136, 0 2011-09-02 11:48 /dev/pts/0
crw-rw---- 1 root dialout 136, 1 2011-09-02 11:45 /dev/pts/1
c--------- 1 root root 5, 2 2011-09-02 07:44 /dev/pts/ptmx
root@ubuntu:/home/elven# $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 S4 S5 S6 S7 S8
Modem Port Scan<*1>: S9 S10 S11 S12 S13 S14 S15 S16
Modem Port Scan<*1>: S17 S18 S19 S20 S21 S22 S23 S24
Modem Port Scan<*1>: S25 S26 S27 S28 S29 S30 S31
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"
root@ubuntu:/home/elven# $sudo wvdial
--> WvDial: Internet dialer version 1.61
--> Cannot get information for serial port.
--> 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.
--> Sending: ATDT17001442
--> Waiting for carrier.
ATDT17001442
CONNECT 46667
--> Carrier detected. Waiting for prompt.
~[7f]}#@!}!f} }8}"}&} }*} } }#}$@#}%}&%[02]8t}'}"}(}"ki~
--> PPP negotiation detected.
--> Starting pppd at Fri Sep 2 11:51:10 2011
--> Pid of pppd: 1805
--> Using interface ppp0
--> pppd: (�� @��
--> pppd: (�� @��
--> pppd: (�� @��
--> local IP address 200.164.47.234
--> pppd: (�� @��
--> remote IP address 200.222.117.2
--> pppd: (�� @��
--> primary DNS address 200.202.193.75
--> pppd: (�� @��
--> secondary DNS address 200.222.0.34
--> pppd: (�� @��
----------------------
I would like to add a few observations that could be helpful if
another linux newbie like me comes up with the same chipset and
distribution:
- Ubuntu 11.04 doesn't come with gnome-ppp or wvdial or any dialer,
one has to download them... and all their dependencies, and the
dependencies of their dependencies... from windows or somewhere else
and install manually inside Natty Narwhel.
-The scanModem.gz provided at the website doesn't match the
instructions, to run the scanner I had to type ./scanModem.2011080803
I hope any of this can be helpful to further assist other people in
need, the amount of people still using dial-up not only in my city is
higher than people might expect and I ran into a lot of misleading
information before being helped by you.
I don't know how to thank you enough, if not for you I wouldn't be
using Linux right now, thank you VERY MUCH.
Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.38-11-generic
With this Subject Line cogent experts will be alerted, and useful case names left in the Archive.
YourCountry will enable Country specific guidance. Linux experts in YourCountry
can be found through: http://www.linux.org/groups/index.html.
They will know your Country's modem code, which may be essential for dialup service.
Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org
-------------------------- System information ----------------------------
CPU=i686, Ubuntu , ALSA_version=1.0.23
Linux version 2.6.38-11-generic (buildd@rothera) (gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4) ) #48-Ubuntu SMP Fri Jul 29 19:05:14 UTC 2011
scanModem update of: 2011_08_08
The modem symbolic link is /dev/modem -> ttySL0
The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/0
Distrib_ID=Ubuntu
DistribCodeName=natty
AptRepositoryStem=http://br.archive.ubuntu.com/ubuntu/
The dkms driver upgrade utilities are installed,
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
snd_hda_intel slamr
slamrTest=
Attached USB devices are:
ID 054c:01bd Sony Corp. MRW62E Multi-Card Reader/Writer
If a cellphone is not detected, see http://ubuntuforums.org/archive/index.php/t-878554.html
A sample report is: http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html
If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@xxxxxxxxxxxxx
Candidate PCI devices with modem chips are:
04:04.0 Modem: Motorola SM56 Data Fax Modem (rev 04)
02:00.1 Audio device: ATI Technologies Inc RV710/730
80:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10)
High Definition Audio cards can host modem chips.
For candidate card in slot 04:04.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
04:04.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem
Modem interrupt assignment and sharing:
18: 477315 0 IO-APIC-fasteoi SL1900
--- Bootup diagnostics for card in PCI slot 04:04.0 ----
[ 0.228111] pci 0000:04:04.0: [1057:3052] type 0 class 0x000703
[ 0.228133] pci 0000:04:04.0: reg 10: [mem 0xdfdff000-0xdfdfffff]
[ 0.228147] pci 0000:04:04.0: reg 14: [io 0xbc00-0xbcff]
[ 0.228226] pci 0000:04:04.0: PME# supported from D0 D3hot D3cold
[ 0.228231] pci 0000:04:04.0: PME# disabled
[ 0.796983] serial 0000:04:04.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 0.796991] serial 0000:04:04.0: PCI INT A disabled
[ 14.863183] slamr 0000:04:04.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
The PCI slot 04:04.0 of the modem card may be disabled early in
a bootup process, but then enabled later. If modem drivers load
but the modem is not responsive, read DOCs/Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
if help is needed.
For candidate card in slot 02:00.1, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
02:00.1 1002:aa38 1682:aa38 Audio device: ATI Technologies Inc RV710/730
Modem interrupt assignment and sharing:
0: 49 0 IO-APIC-edge timer
--- Bootup diagnostics for card in PCI slot 02:00.1 ----
[ 0.223103] pci 0000:02:00.1: [1002:aa38] type 0 class 0x000403
[ 0.223123] pci 0000:02:00.1: reg 10: [mem 0xdfefc000-0xdfefffff 64bit]
[ 0.223193] pci 0000:02:00.1: supports D1 D2
[ 15.825776] HDA Intel 0000:02:00.1: PCI INT B -> GSI 25 (level, low) -> IRQ 25
[ 15.825866] HDA Intel 0000:02:00.1: setting latency timer to 64
[ 15.825879] HDA Intel 0000:02:00.1: PCI: Disallowing DAC for device
For candidate card in slot 80:01.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
80:01.0 1106:3288 1043:81b3 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC]
Modem interrupt assignment and sharing:
17: 2061 0 IO-APIC-fasteoi hda_intel
--- Bootup diagnostics for card in PCI slot 80:01.0 ----
[ 0.262346] pci 0000:80:01.0: [1106:3288] type 0 class 0x000403
[ 0.262374] pci 0000:80:01.0: reg 10: [mem 0xbfffc000-0xbfffffff 64bit]
[ 0.262446] pci 0000:80:01.0: PME# supported from D0 D3hot D3cold
[ 0.262451] pci 0000:80:01.0: PME# disabled
[ 15.910662] HDA Intel 0000:80:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 15.910745] HDA Intel 0000:80:01.0: setting latency timer to 64
[ 15.910750] HDA Intel 0000:80:01.0: PCI: Disallowing DAC for device
The PCI slot 80:01.0 of the modem card may be disabled early in
a bootup process, but then enabled later. If modem drivers load
but the modem is not responsive, read DOCs/Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
if help is needed.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 04:04.0:
Modem chipset detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=18
HDA2=02:00.1
HDA2=80:01.0
IDENT=slamr
For candidate modem in: 04:04.0
0703 Modem: Motorola SM56 Data Fax Modem
Primary device ID: 1057:3052
Support type needed or chipset: slamr
1057:3052 has a Motorola chipset, poorly supported by Motorola itself
However Zello discovered that drivers written to support Smartlink modems do support the 1057:3052 chipset!!
It sufficed to add 1057:3052 to the list of modem cards recognized by the Smartlink slamr driver.
There is a ungrab-winmodem driver used in conjunction with slamr, which must have 1057:3052
similarly added. See messages from Zello:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html
and Alvaro Aguirre about the ungrab-winmodem fix:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html
For general guidance on ungrab-winmodem + slamr usage, read the DOCs/Smartlink.txt
There is a package sl-modem-source providing a source code the modem driver ,
If can be searched for at http://pacakge.ubuntu.com. After downloading install under Linux with:
$ sudo dpkg -i sl*.deb
It is preferable to install the dkms package first.
With DKMS support installed, driver updates with kernel updates will be automatically done.
The modem is supported by the Smartlink
plus the slmodemd helper utility. Read the
DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance.
For 2.6.38-11-generic compiling drivers is necessary. As of October 2007 the current packages at
http://linmodems.technion.ac.il/packages/smartlink/ are the
ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz
Writing DOCs/Smartlink.txt
============ end Smartlink section =====================
Predictive diagnostics for card in bus 02:00.1:
Modem chipset not detected on
NAME="Audio device: ATI Technologies Inc RV710/730"
CLASS=0403
PCIDEV=1002:aa38
SUBSYS=1682:aa38
For candidate modem in: 02:00.1
0403 Audio device: ATI Technologies Inc RV710/730
Primary device ID: 1002:aa38
Support type needed or chipset:
Predictive diagnostics for card in bus 80:01.0:
Modem chipset not detected on
NAME="Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] "
CLASS=0403
PCIDEV=1106:3288
SUBSYS=1043:81b3
IRQ=17
For candidate modem in: 80:01.0
0403 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC]
Primary device ID: 1106:3288
Support type needed or chipset:
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.5.2
and the compiler used in kernel assembly: 4.5.2
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.5
linuc_headers base folder /lib/modules/2.6.38-11-generic/build
However some compilations and executable functions may need additional files,
in the FileNames.h (so called kernel "h"eaders) collection installed in /usr/include/ .
For martian_modem, additional required packages are needed. The also required headers of package libc6 are commonly installed by default.
Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev packages, for kernels 2.6.24 and later versions.
In not included on your install CD, search for them at http://packages.ubuntu.com
or comparable Repository for other Linux distros.
When compiling ALSA drivers, the utility "patch" will also be needed.
If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), then
Some additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-dev
and any of its dependents, under Ubuntu linux-libc-dev
If an alternate ethernet connection is available,
$ apt-get update
$ apt-get -s install linux-kernel-devel
will install needed packages.
For Debian/Ubuntu related distributions, run the following command to display the needed package list:
Otherwise packages have to be found through http://packages.ubuntu.com
Once downloaded and transferred into a Linux partition,
they can be installed alltogether with:
$ sudo dpkg -i *.deb
Checking pppd properties:
-rwsr-xr-- 1 root dip 273272 2011-02-04 04:43 /usr/sbin/pppd
In case of an "error 17" "serial loopback" problem, see:
http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html
To enable dialout without Root permission do:
$ su - root (not for Ubuntu)
sudo chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
sudo chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
asyncmap 0
noauth
crtscts
lock
hide-password
modem
lcp-echo-interval 30
lcp-echo-failure 4
noipx
In case of a message like:
Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html
For guidance on FAX usage, get from http://linmodems.technion.ac.il/packages/ get faxing.tar.gz
It has samples for a modem using port /dev/ttySL0, which must be changed to match your modem's port.
Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 ppp0
Which can interfere with Browser naviagation.
Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link: lrwxrwxrwx 1 root root 6 2011-09-03 12:56 /dev/modem -> ttySL0
slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10 2011-09-03 12:56 /dev/ttySL0 -> /dev/pts/0
Within /etc/udev/ files:
Within /etc/modprobe.conf files:
/etc/modprobe.d/sl-modem.conf:install slamr /sbin/modprobe -qb ungrab-winmodem; /sbin/modprobe --ignore-install slamr; test -e /dev/slamr0 && (chmod 660 /dev/slamr0 && chgrp dialout /dev/slamr0) || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0)
/etc/modprobe.d/sl-modem.conf:install slusb /sbin/modprobe -qb ungrab-winmodem; /sbin/modprobe --ignore-install slusb; test -e /dev/slusb0 && (chmod 660 /dev/slusb0 && chgrp dialout /dev/slusb0) || (/bin/mknod -m 660 /dev/slusb0 c 243 0 2>/dev/null && chgrp dialout /dev/slusb0)
/etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
/etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
