Je modem qui poses problème est le modem RTC, cars il n'est pas détecter
Je ne connais pas la marque du modem , mais dans le log ( Fichier généré se nommant 'ModemData.txt' ) il est marqué
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:0d.0 134d:7892 134d:0001 Communication controller: PCTel Inc HSP MicroModem 56
Donc je pense que la marque du modem est PCTel Inc HSP MicroModem 56
Je rajoute le fichier 'vdial.txt'
Modem usage is accomplished through drivers, sometimes some helper software,
and the core communication work horse "pppd". Usually it will be found at
/usr/sbin/pppd with permissions shown on my Ubuntu system by:
$ ls -l /usr/sbin/pppd
-rwsr-xr-- 1 root dip 257720 2006-07-05 08:58 /usr/sbin/pppd
The s means "sticky" meaning only one person can use pppd at a time.
As installed, it requires Root/Adm permissions to use pppd, directly or
through front end dialer tools. This is a security precaution common to
all COMM channels. But if you want to enable a simple User to dialout,
as is basically OK for a single user PC, do:
$ su - root
# chmod a+x /usr/sbin/pppd
or for Ubuntu:
$ chmod a+x /usr/sbin/pppd
after which there will be seen:
$ ls -l /usr/sbin/pppd
-rwsr-xr-x 1 root dip 257720 2006-07-05 08:58 /usr/sbin/pppd
with the last x meaning any one can execute pppd, either directly or
much more commonly through a front end dialer such as wvdial of KPPP.
Configuration file for wvdial
-------------------------------
There is a very smart dialer utility "wvdial"
which can be used once basic modem setup is accomplished. A configuration file
is needed, which begins below with [Dialer defaults]. This file can be accessed
any where by:
$ wvdial --config Path_to/configuration_file
Most commonly the configuration file is saved as:
/etc/wvdial.conf
whereat it will serve all Users of the computer. If saved as:
/home/LoginName/.wvdial.rc
it will be found and used before /etc/wvdial.conf. Note that "." beginning
a file name means "do not show it", except through usage of:
$ ls -a
Many local configuration files are thus "hidden" in your /home/LoginName/ folder
Some Linux installations have dialup tools like Kinternet, GnomePPP, and the
Redhat/Fedora Internet Connection Wizard which are front ends for wvdial and
will write /etc/wvdial.conf files. For this reason, it is advisable to test
your configuration file first, before copying it to /etc/wvdial.conf. Typically
a first test is run with:
$ wvdialconf wvtest
which will search ports with names: /dev/modem /dev/ttyS* /dev/rfcomm*.
A successful ouput include a section like:
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
Note: above lines are testing the driver, modem firmware is then first read by ATI
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 wvtest.
ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
------
will be included in a successful run, where in this case /dev/ttySL0
is the responding device port. The generated wvtest file is:
[Dialer Defaults]
Modem = /dev/ttySL0
Baud = 460800
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = Analog Modem
; Phone = <Target Phone Number>
; Username = <Your Login Name>
; Password = <Your Password>
which at a minimim must be edited to a form like:
[Dialer Defaults]
Modem = /dev/ttySL0
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = Analog Modem
Phone = 3334445555
Username = Your_Login_Name
Password = Your_Password
Additional if your modem port is of the type /dev/pts/N , with N a number,
then there MUST be added a line:
Carrier Check = no
This requirement currently applies to dialups using the helper utility: slmodemd
together with slamr, slusb or ALSA modem drivers, OR the " " : martian_helper
used with the martian_dev for Lucent/Agere modems with DSP chipsets.
Then a test dialput can be done with:
$ wvdial --config wvtest
There are some Systems for which the wvdialconf test will stall at rfcomm ports.
This is a wvdialconf bug and can be bypassed by just using wvdial with a trial
wvtest, but you need to specify the port appropriate to your modem.
If the configuration file below, lines beginning with # are comments.
Removing a # will activate a line with wvdial instructions appropriate to
special circumstances.
[Dialer defaults]
# Lines begining with # are comments.
# wvdial will look for this file at /etc/wvdial.conf or /home/LoginName/.wvdial.rc
# Redhat/Fedora have an Internet Connection Wizard in the popup menus
# ICW will write a two part /etc/wvdial.conf supporting multiple modem usage.
Modem = ModemPort
# typically a symbolic link to the true port is used, /dev/modem or /dev/ttyS*
# wvdialconf will test all port names /dev/modem and /dev/ttyS*
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
# Lack of dialtone acquisition can be due to low line voltage,
# a common problem in Italy.
# Try inserting a "dial without waiting": X3
# Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0
# In case of connection instabilities, specify a lower frequency:
# Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=34
# a MS=90 option is sometimes necessary for Internet Providers with buggy V92 protocols:
# Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
ISDN = 0
Modem Type = Analog Modem
# Dial Command = ATDP
## replaces Touch Tone prefix ATDT to Dialout_phone_number, with older Pulse prefix ATDP
Phone = Dialout_phone_number
# if going through a switch board, a perhaps necessary pause can produced with a comma:
# Phone = 1,Dialout_phone_number
Username = LoginName
# if Internet Provider is MSN.net, use under Linux: MSN/LoginName
Password = YourPassWord
# the following lines is NEEDED only for usage with slmodemd or martian_helper
Carrier check = no
# Kinternet appears to add it automatically.
## If CONNECT is achieved but browsing fails, try activating the following line
# Auto DNS = yes
## To make a logfile wvdial.out
# wvdial 2>&1 | tee wvdial.out
# # For some Internet providers, the following line is necessary
# Stupid Mode = yes
## for other wvdial options, do "man wvdial" or see the documentation in
## /usr/share/doc/wvdial/
# to dial an alternate provide use "wvdial 2nd" which will preferentially read:
[Dialer 2nd]
Phone = 2nd_phone_number
Username = 2nd_LoginName
Password = 2nd_PassWord
## End wvdial config file
et le fichier 'Pctel.txt' généré
Vendor=134d is PCTel, but their modem sector has been sold to Conexant,
and Conexant is Not providing official code updates.
The volunteer maintainer for current updates is Robert Thornburrow, with
downloads from http://linmodems.technion.ac.il/pctel-linux/
Use the most recent pctel-0.9.7-9-rht-N package.
The AMR variants are supported by the pctel driver only under 2.4.n kernels
Under 2.6.n kernels, the AMR Pctel variants and the HSP56 MicroModem 688T
have support through the Smartlink software. The rest of this text is only
cogent to modems using the 2.6.n driver triplet: pctel, ptserial and linmodem.
Under 2.6.x kernels, these modems are supported by the pctel-0.9.7-9-rht-8
From the README file therein:
PCI ID (x) Name Chip(set) HAL
~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~
134d:7890 PCtel HSP MicroModem 56 PCT789T-C1 pct789
134d:7891 PCtel HSP MicroModem 56 PCT 789T pct789
134d:7892 PCtel HSP MicroModem 56 PCT 789T-A pct789
134d:7893 PCtel HSP MicroModem 56 S911 K017 pct789
134d:7894 PCtel HSP MicroModem 56 FT13 pct789
134d:7895 PCtel HSP MicroModem 56 PCT789T-C1 pct789
134d:7896 PCtel HSP MicroModem 56 PCT789T-C1 pct789
134d:7897 PCtel HSP MicroModem 56 PCT789T pct789
13f6:0211 C-Media CM8738 CM8738 cm8738
Do the following preliminary steps:
Unpack with command: tar zxvf pctel-0.9.7-*.tar.gz
Change directory: cd pctel-0.9.7-9 (for example).
Read README file less README (space bar goes to next page)
Is a compiler installed? Test with: gcc
If not found, install it from your Linux distribution.
Become root: su root
Seeing lspci? lspci
If not, install the package pciutils .
Now you can follow instructions in README
The ISA card pct388p modem is not supported by the current driver series.
During PCtel code installations, the node made is character device /dev/ttyS_PCTEL0 c 62 69
Check with:
ls -l /dev/ttyS_PCTEL0
There is a pre-compiled binary component in the Pctel code which was assembled with a gcc 2.95 compiler
A consequence is the loading fails under kernels compiled with gcc 3.n ,
unless forcing (-f) is used:
# insmod -f pctel
# insmod ptserial
This can be automated by adding the following lines to /etc/modules.conf
####### for pctel modem ######
alias char-major-62 pctel
alias /dev/modem ptserial
install pctel /sbin/insmod "-f" "pctel"
post-install pctel /sbin/insmod ptserial
# country code for pctel modem, for USA
options ptserial country_code=1
######## pctel end ####
then run:
# depmod -a
to inform the System and thereafter
# modprobe ptserial
will load all three drivers,
For some Systems, PCTel function requires disablement of apmd power monitoring function.
System problems of various severity have been reported after modem usage.
These may be alleviated by the following steps after a modem usage session.
Log into a console as:
# su - root
# lsmod
to display loaded modules.
# modprobe -r ptserial
# lsmod
====== end Pctel section =======