modem MDC 1.5 (AZALIA) - ou - Agere delphi AM3 D40

giant_trunade · 20 de Fevereiro de 2009, 15:47

Olá Pessoal!!

Bom aqui estou eu novamente com problemas de hardware rsrss... principalmente softmodems...

O desafio da vez é um modem que é produzido para Notebooks.

Na documentação no cd do fabricante do note (OBS.: drivers so para XP e Vista) há as seguintes especificaçoes:

--------
56K Fax Modem -> MDC 1.5 (AZALIA)
I/F -> Azalia s/w modem
Controller -> Azalia Enbedded
wake on ring -> Support on S1/S2/S3 state

---------

Um amigo que trabalha na empresa fabricante / dristribuidora do note me disse que esse seria um nome GENERICO para o modem... e que o modelo seria:

MODELO: Agere Delphi AM3 D40 - 56Kbps

---------------

Pesquisando no google, me parece ser um driver da QCom Techinologies.

O mesmo nao é listado no lspci, mesmo assim segue o mesmo:

00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
01:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
01:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
01:04.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
01:04.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11)
01:04.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

TESTES EFETUADOS:

O primeiro teste foi:

com o Gnome ppp instalado, tentar detectar o modem (via gnome-ppp)

- Resposta do gnome-ppp: "Nenhum modem foi encontrando em seu sistema".

Osegundo teste foi:

Apos pesquisar bastante (em portugues, ingles, chines e outros) fui na pagina: http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/ e então instalei e testei:

1º: scanModem.gz 03-Oct-2006 12:16 64K

Resultado: o script roda, porem apos listar as informações (creio que o script dá um lspci), o mesmo não faz mais nada, porem tambem nao para sua execução. Creio que por que o modem nao é listado no lspci.

2º : baixei e instalei o Ungrab-winmodem (instalou sem problemas) e o slmodem (smartlink - generico para vários modems).

ungrab-winmodem-20080126.tar.gz 01-Feb-2008 10:20 2.3K
slamr-2.6.27-7-generic.tar.gz 07-Dec-2008 12:30 1.3M (sim, este é meu kernel... rsrsrs)

Ambos instalaram sem problemas... porem o modem continua nao sendo reconhecido nem pelo Gnome-ppp nem pelo kppp. tambem nao aparece no lspci.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Galera, qualquer informação já iria me ajudar muuuuuito...

se alguem já instalou este modem, se estou seguindo algo incorretamente, se sabe qual arquivo ou referencia devo usar, agradeceria muito!!!

Desde já agradeço muiiito a colaboração de todos.

PS.: Me baseei nos passos de uma instalação de outro modem ao qual o Alarcom me ajudou com modem tambem.

Abraços a todos

giant_trunade · 20 de Fevereiro de 2009, 15:54

Me esqueci de citar:

Em pesquisas no google nao encontrei muitas referencias uteis, e geramente eram de foruns onde o era feito reviews dos notebooks da empresa e opinioes...

O note é da marca mirax, que produz projetos / modelos da MSI. Em ambos os sites somente há drivers para XP e Vista...

Algumas referencias que achei interessante citar:

Site do fabricante:

http://www.mirax.com.br/exibeinfo.asp?mid=44

http://www.msimiami.com/portugues/index.htm

Se houverem mais informações que nao postei irei postar assim que lembrar

Abraços

alarcon · 26 de Fevereiro de 2009, 17:34

Primeiro você não tem um modem em específico e sim uma placa de som especial que faz o papel de modem também que é:

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)

São conhecidos como modems HDA e portanto se já era difícil fazer um modem normal para conexões discadas funcionar no linux, imagine um tipo deste. Só conheço o driver Conexant e o driver Smartlink que são capazes de fazer alguns destes tipos de modems (HDA) funcionar, sendo o driver conexant de mais fácil uso e o Smartlink de difícil uso.

Cola aqui o resultado do comando lspci -n também para ver a ID do modem.

O Ideal mesmo seria rodar o script scanModem para poder obter todas as informações sobre o modem para ser orientado de como proceder. Lembre-se que o script scanModem.gz ainda está compactado (extensão .gz) e para descompactá-lo basta clicar com o botão direito sobre ele e escolher a opção extrair aqui. Para executá-lo, pelo terminal, antes é necessário dar permissão de execução com o comando chmod +x scanModem* (não precisa ser como root) e depois para rodá-lo no terminal, como usuário comum, digitar:

./scanModem*

e aguardar o processo terminar. Depois disso é só entrar na pasta que estava guardado o script e no qual foi rodado que deverá ter uma pasta chamada Modem com vários arquivos de texto com informações úteis sendo a principal chamada de ModemData.txt ok.

giant_trunade · 26 de Fevereiro de 2009, 18:46

FALA ALARCON!

novamente muito obrigado pela ajuda!

o resultado do lspci -n é:

00:00.0 0600: 8086:2a00 (rev 03)
00:02.0 0300: 8086:2a02 (rev 03)
00:02.1 0380: 8086:2a03 (rev 03)
00:19.0 0200: 8086:1049 (rev 03)
00:1a.0 0c03: 8086:2834 (rev 03)
00:1a.1 0c03: 8086:2835 (rev 03)
00:1a.7 0c03: 8086:283a (rev 03)
00:1b.0 0403: 8086:284b (rev 03)
00:1c.0 0604: 8086:283f (rev 03)
00:1d.0 0c03: 8086:2830 (rev 03)
00:1d.1 0c03: 8086:2831 (rev 03)
00:1d.2 0c03: 8086:2832 (rev 03)
00:1d.7 0c03: 8086:2836 (rev 03)
00:1e.0 0604: 8086:2448 (rev f3)
00:1f.0 0601: 8086:2815 (rev 03)
00:1f.1 0101: 8086:2850 (rev 03)
00:1f.2 0101: 8086:2828 (rev 03)
00:1f.3 0c05: 8086:283e (rev 03)
01:04.0 0607: 1180:0476 (rev ba)
01:04.1 0c00: 1180:0832 (rev 04)
01:04.2 0805: 1180:0822 (rev 21)
01:04.3 0880: 1180:0592 (rev 11)
01:04.4 0880: 1180:0852 (rev 11)
03:00.0 0280: 8086:4229 (rev 61)

Cara eu já rodei o scanmodem...

- 1º vez:
UPDATE=2009_02_21
Continuing as this update is only 1 weeks old,
but the current Update is always at: http://linmodems.technion.ac.il

(NAO FEZ MAIS NADA!!)

- 2º vez (como root):

root@mirax-notebook:/home/mirax# ./scanModem
UPDATE=2009_02_21
Continuing as this update is only 1 weeks old,
but the current Update is always at: http://linmodems.technion.ac.il

Identifying PCI bus slots with candidate modems.
Running PCIbus cases
Analysing card in PCI bus 00:1b.0, writing to scanout.00:1b.0
Using scanout.00:1b.0 data, and writing guidance to ModemData.txt
Writing DOCs/Intel.txt
Writing DOCs/Conexant.txt
Writing DOCs/Smartlink.txt
Writing residual guidance customized to your System.
A subfolder Modem/ has been written, containing these files with more detailed Information:
------------------------------------------------------------------------------------------
1stRead.txt Bootup.txt dmesg.txt DOCs ModemData.txt scanout.00:1b.0 tmp
and in the DOCs subfolder:
Conexant.txt    DriverCompiling.txt InfoGeneral.txt Intel.txt
Rational.txt    Smartlink.txt     SoftModem.txt Testing.txt
UNSUBSCRIBE.txt wvdial.txt     YourSystem.txt
-------------------------------------------------------------------------------------------
Please read 1stRead.txt first for Guidance.

...

No arquivo ModemData.txt há as informações:

If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@linmodems.org

For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
PCI slot   PCI ID      SubsystemID   Name
----------   ---------   ---------   --------------
00:1b.0   8086:284b   1462:3783   Audio device: Intel Corporation 82801H

Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.473531] PCI: 0000:00:1b.0 reg 10 64bit mmio: [feaf8000, feafbfff]
[ 0.473589] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.473594] pci 0000:00:1b.0: PME# disabled

OUTRO TRECHO:

Predictive diagnostics for card in bus 00:1b.0:
   Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801H "
CLASS=0403
PCIDEV=8086:284b
SUBSYS=1462:3783
IRQ=10
HDA=8086:284b
SOFT=8086:284b.HDA

ESTE É SO UM TRECHO, TEM BEM MAIS COISA...
...

Quer que eu te poste algum arquivo por completo ou coisa do tipo???

qq coisa que for necessário é so citar ok?

muito obrigado!

alarcon · 01 de Março de 2009, 12:09

cola aqui o conteúdo completo do arquivo ModemData.txt oriundo da execução do script scanModem

giant_trunade · 11 de Março de 2009, 16:29

Olá Alarcon!

Desculpe a demora em postar mas eu tive uns probleminhas e não pude responder.. realmente desculpe.

Segue abaixo o texto do ModemData.txt:

Código Selecionar



 Only plain text email is forwarded by the  Discuss@Linmodems.org List Server,
 as HTML can contain viruses. Use as the email Subject Line:
           YourName, YourCountry  kernel 2.6.27-7-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@Linmodems.org 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,  
Linux version 2.6.27-7-generic (buildd@rothera) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu10) ) #1 SMP Fri Oct 24 06:42:44 UTC 2008
 scanModem update of:  2009_02_21
The modem symbolic link is /dev/modem -> ttySL0
 There are no blacklisted modem drivers in /etc/modprobe*  files 
 Potentially useful modem drivers now loaded are:
       slamr         

slamrTest=
Attached USB devices are:
 ID 0c45:62c0 Microdia Pavilion Webcam
If a cellphone is not detected, see http://ubuntuforums.org/archive/index.php/t-878554.html

If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@linmodems.org

For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
 PCI slot	PCI ID		SubsystemID	Name
 ----------	---------	---------	--------------
 00:1b.0	8086:284b	1462:3783	Audio device: Intel Corporation 82801H 

 Modem interrupt assignment and sharing: 
 --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[    0.473531] PCI: 0000:00:1b.0 reg 10 64bit mmio: [feaf8000, feafbfff]
[    0.473589] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[    0.473594] pci 0000:00:1b.0: PME# disabled

 The PCI slot 00:1b.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@linmodems.org
 if help is needed.
 


Packages needed for support of Advanced Linux Sound Architecture (ALSA) support should be installed: alsa-base and alsa-utilities!!
They are necessary for support of ALSA modem drivers, many Conexant chipset modems and success of modem diagnostics for modems requiring slmodemd actions.

=== Finished firmware and bootup diagnostics, next deducing cogent software. ===

A candidate modem is not evident among the PCI devices:
------------------------------------------------
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
01:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
01:04.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
01:04.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11)
01:04.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
------------------------------------------------
 with USB and bridge devices not displayed.

 If your modem is connected by an external serial cable,
 or mounted internally on an ISA card, scanModem would not access it. 
 Try with Root permission
 $ sudo wvdialconf  /etc/wvdial.conf
 to detect these modem types and some USB modems.
 If the detection is successful, read the DOCs/wvdial.txt .
 Edit the /etc/wvdial.conf with Root permission:
 	sudo  gedit  /etc/wvdial.conf
  will be able to dial out with Root permission:
	sudo wvdial

 Many modems for which scanModem fails have Conexant chips. 
 From http://www.linuxant.com/drivers/modemident.php
 get the ListModem tool, which will report on Conexant chipset modems

 If the above tests fail, please provide any independent information available on your modem.
 If an alternative boot into Microsoft windows can be done, do mouse
clicks on:
   Start > Settings > Control Panel > Classical View (for Window XP) > System
> Hardware > Device Manager > Modems > Click on the + > Modem. Double click to
expand the graphic. Manufacturer information may be displayed. For example, CXT
stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor
and device information. From the Driver Details TAB, copy out the VENdor and DEVice information.
Next do the Query Modem and record the ATI specifications displayed such as:
    ATI3 - Agere SoftModem Version 2.1.22
    ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
Try to identify the modem setup file, with name perhaps MODEM.INF.
If may contain chipset Vendor informaton.


Predictive  diagnostics for card in bus 00:1b.0:
	Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801H "
CLASS=0403
PCIDEV=8086:284b
SUBSYS=1462:3783
IRQ=10
HDA=8086:284b
SOFT=8086:284b.HDA


 High Definition Audio (HDA) cards MAY host a modem chip in their Subsystem, 
 and many are supported by the ALSA audio+modem driver snd-hda-intel
 A modem was not detected on HDA card 8086:284b.
 If another modem card is present, then most likely 8086:284b does not host a modem.
 If another modem card has not been detected, then possibilities are:
	1) A Conexant modem chip is present on 8086:284b, as Conexant chips
 are frequently not detectable by ALSA diagnostics
	2) The modem may be of the older non-PCI Controller Chipset (hardware) type.
Try detection with Root permission:
	sudo wvdialconf  /etc/wvdial.conf

 For candidate modem in:  00:1b.0
   0403 Audio device: Intel Corporation 82801H 
      Primary device ID:  8086:284b
    Subsystem PCI_id  1462:3783 
    Softmodem codec or chipset from diagnostics: 
                               from    Archives: 
                        
      

Support type needed or chipset:	

Support can likely be achieved through two mutually exclusive alternatives:
1) The hsfmodem software for Conexant chipset modems: Read DOCs/Conexant.txt
The following ALSA alternative CANNOT work with Conexant modems.

2) An ALSA modem driver plus slmodemd.  Read DOCs/Smartlink.txt for details, and
to test get the package SLMODEMD.gcc4.3.tar.gz from:
	http://linmodems.technion.ac.il/packages/smartlink/

----------------end Softmodem section --------------

Writing DOCs/Intel.txt

For owners of a Dell PCs with Conexant HSF modems, a driver source package with full speed enabled is available, but requires driver compiling. Read DOCs/Conexant.txt


Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to find the
hsfmodem package matching your System. For several Linux distros, there are
precompiled drivers matched to specific kernels. These have within the FileName,
your KernelVersion:	2.6.27_7_generic
They can be found through http://www.linuxant.com/drivers/hsf/full/downloads.php 
A more precise location may be given a few paragraphs below.
If an EXACT Match with your your KernelVersion is not found, one of the 
"Generic packages with source" near the bottom of the page must be used.
Downloaded packages must be moved into the Linux partition (home folder is OK)
and unzipped with:
	unzip hsf*.zip
The installation command for a .deb suffic packages is, with root/adm permission:
  sudo dpkg -i hsf*.deb
while for .rpm suffix it is, with:
  rpm -i hsf*.rpm

Support for Conexant chips hosted on High Definition Audio cards may require
installation of additional packages, one of the alsa-driver-linuxant packages
on  http://www.linuxant.com/alsa-driver/  At the same time download the 
alsa-driver-1.0.17-1.patch , in case it prove to be later needed. During the
hsfmodem install, there will be a message if there is necessary installation of
alsa-driver-linuxant

The installation command for a .deb suffic packages is, with root/adm permission:
  sudo alsa* -i hsf*.deb
while for .rpm suffix it is, with:
  rpm -i hsf*.rpm

There may a message that "Dependencies" are not satisfied.  In this case the Ubuntu/Debian packages to be installed are linux-libc-dev & libc6-dev. Package
names may be different for other Linuxes. If not on your install CD, these
packages can be searched for at http://packages.ubuntu.com.  After download,
they can be coinstalled with:
	sudo dpkg -i li*.deb
Again try the alsa-driver-linuxant

There may be a message that the patch must be applied.  In this case get the
ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.17.tar.bz2 
Under Linux, this package is unpacked with:
$ tar jxf alsa*.tar.bz2
Next the patch is applied with:
$ patch -p0 < alsa-driver-1.0.17-1.patch

See http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html
for details on compiling and installing replacement snd-hda-intel + its
dependent drivers.
After the installation is completed, rerun the hsfmodem installation.
Reboot and try to detect the modem with Root permission:
	sudo wvdialconf  /etc/wvdial.conf

 From  http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
 download hsfmodem-7.80.02.02full_k2.6.27_7_generic_ubuntu_i386.deb.zip 
 Under Linux unpack with:
 $ unzip hsfmodem*.zip
 Then install with:
 $ sudo dpkg -i hsfmodem*.deb
 Subsequently, the modem should be found with
 $ sudo wvdialconf /etc/wvdial.conf
 Edit in your personal information with:
 $ sudo gedit /etc/wvdial.conf
 and try dialing out with:
 $ sudo wvdial.
 See DOCs/Testing.txt  for details.
 
 Read DOCs/Conexant.txt

Writing DOCs/Conexant.txt

Writing DOCs/Smartlink.txt
============ end Smartlink section =====================


 The base of the UDEV device file system is: /dev/.udev

 Versions adequately match for the compiler installed: 4.3.2
             and the compiler used in kernel assembly: 4.3.2


 
 Minimal compiling resources appear complete:
   make utility - /usr/bin/make
   Compiler version 4.3
   linuc_headers base folder /lib/modules/2.6.27-7-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:
	-rwsrwsrwt 1 root dip 273064 2008-10-15 22:51 /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
proxyarp
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

Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 wlan0 wmaster0
Which can interfere with Browser naviagation.

 Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================

# start/stop the daemon when the USB modem is connected
KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
 Checking for modem support lines:
 --------------------------------------
     /device/modem symbolic link:   lrwxrwxrwx 1 root root 6 2009-02-26 16:39 /dev/modem -> ttySL0
slmodemd created symbolic link /dev/ttySL0:  
     Within /etc/udev/ files:
/etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected
/etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
/etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected
/etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
     Within /etc/modprobe.conf files:
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
/etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
/etc/modprobe.d/sl-modem-daemon.modutils:install slamr modprobe --ignore-install ungrab-winmodem ;  modprobe --ignore-install slamr; test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0) 
     Within any ancient /etc/devfs files:

     Within ancient kernel 2.4.n /etc/module.conf files:
agrmodem --force-modversion
--------- end modem support lines --------

como eu disse realmente desculpe a demora!

um grande abraço e desde já muito obrigado.

modem MDC 1.5 (AZALIA) - ou - Agere delphi AM3 D40

giant_trunade

giant_trunade

alarcon

giant_trunade

alarcon

giant_trunade