O note não identifica o modem (RESOLVIDO)

Miguel steffen · 17 de Setembro de 2007, 14:43

Nada denovo, veja o resultado

miguel@miguel:~$ sudo ./scanModem.sept07

From http://limodems.technion.ac.il , get a recent update of scanModem,
if this copy was not there obtained. There are weekly updates.
Updated on: 2007_Sept_07

Please rename this script scanModem, or some files will not print out.
Abort with Ctrl-C, or wait 5 seconds to continue.

Identifying PCI bus slots with candidate modems.
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===

Analysing card in PCI bus 00:1b.0, writing to scanout.00:1b.0
Modem with PCI ID 8086:27d8 is in the software modem category.
Checking for match with Archived softmodem information.
IDENT=hsfmodem
Using scanout.00:1b.0 data, and writing guidance to ModemData.txt
cat: 14f12c06: Arquivo ou diretório inexistente
./scanModem.sept07: line 1952: /proc/asound/card0/codec#1: Permissão negada
Writing Intel.txt
Writing Conexant.txt

Writing residual guidance customized to your System.
A subfolder Modem/ has been written, containing these files with more detailed Information:
------------------------------------------------------------------------------------------
1stRead.txt ALSAroot.tgz Conexant.txt DriverCompiling.txt
InfoGeneral.txt Intel.txt ModemData.txt Rational.txt
scanout.00:1b.0 SoftModem.txt Testing.txt UNSUBSCRIBE.txt
wvdial.txt YourSystem.txt
-------------------------------------------------------------------------------------------
Please read 1stRead.txt first for Guidance.

alarcon · 17 de Setembro de 2007, 14:48

Citação de: Miguel steffen online 17 de Setembro de 2007, 14:43
Nada denovo, veja o resultado

miguel@miguel:~$ sudo ./scanModem.sept07

From http://limodems.technion.ac.il , get a recent update of scanModem,
if this copy was not there obtained. There are weekly updates.
Updated on: 2007_Sept_07

Please rename this script scanModem, or some files will not print out.
Abort with Ctrl-C, or wait 5 seconds to continue.

Identifying PCI bus slots with candidate modems.
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===

Analysing card in PCI bus 00:1b.0, writing to scanout.00:1b.0
Modem with PCI ID 8086:27d8 is in the software modem category.
Checking for match with Archived softmodem information.
IDENT=hsfmodem
Using scanout.00:1b.0 data, and writing guidance to ModemData.txt
cat: 14f12c06: Arquivo ou diretório inexistente
./scanModem.sept07: line 1952: /proc/asound/card0/codec#1: Permissão negada
Writing Intel.txt
Writing Conexant.txt

Writing residual guidance customized to your System.
A subfolder Modem/ has been written, containing these files with more detailed Information:
------------------------------------------------------------------------------------------
1stRead.txt ALSAroot.tgz Conexant.txt DriverCompiling.txt
InfoGeneral.txt Intel.txt ModemData.txt Rational.txt
scanout.00:1b.0 SoftModem.txt Testing.txt UNSUBSCRIBE.txt
wvdial.txt YourSystem.txt
-------------------------------------------------------------------------------------------
Please read 1stRead.txt first for Guidance.

Na sua pasta de usuário dentro da /home/ foi criada uma pasta chamada de Modem que contém vários arquivos, portanto cole aqui o conteúdo do arquivo chamado de ModemData.txt

alarcon · 17 de Setembro de 2007, 15:06

Encontrou?

é que estou desconfiando que seu modem não vai usar o driver Smartlink e sim o Conexant e para isso preciso saber a ID do subsystem do modem e o arquivo em questão vai me fornecer.

se não estiver encontrando, então faça assim do terminal:

lspci -nv

e cole aqui as seis linhas que tem esta informação 8086:27d8

Por exemplo o meu modem tem esta ID 14f1:2702

ao dar o comando lspci -nv procurei pela linha que aparece a minha ID e copie as 6 linhas ficando assim:

Citar00:0b.0 0780: 14f1:2702 (rev 01)
Subsystem: 14f1:2004
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at ed100000 (32-bit, non-prefetchable) [size=64K]
I/O ports at c400
Capabilities: <access denied>

a informação que quero é a que está em vermelho.

Miguel steffen · 17 de Setembro de 2007, 17:22

Olá,

Tentei, mas deu o mesmo resultado...

miguel@miguel:~$ sudo ./scanModem.sept07
Password:

From http://limodems.technion.ac.il , get a recent update of scanModem,
if this copy was not there obtained. There are weekly updates.
Updated on: 2007_Sept_07

Please rename this script scanModem, or some files will not print out.
Abort with Ctrl-C, or wait 5 seconds to continue.

Identifying PCI bus slots with candidate modems.
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===

Analysing card in PCI bus 00:1b.0, writing to scanout.00:1b.0
Modem with PCI ID 8086:27d8 is in the software modem category.
Checking for match with Archived softmodem information.
IDENT=hsfmodem
Using scanout.00:1b.0 data, and writing guidance to ModemData.txt
cat: 14f12c06: Arquivo ou diretório inexistente
./scanModem.sept07: line 1952: /proc/asound/card0/codec#1: Permissão negada
Writing Intel.txt
Writing Conexant.txt

Writing residual guidance customized to your System.
A subfolder Modem/ has been written, containing these files with more detailed Information:
------------------------------------------------------------------------------------------
1stRead.txt ALSAroot.tgz Conexant.txt DriverCompiling.txt
InfoGeneral.txt Intel.txt ModemData.txt Rational.txt
scanout.00:1b.0 SoftModem.txt Testing.txt UNSUBSCRIBE.txt
wvdial.txt YourSystem.txt
-------------------------------------------------------------------------------------------
Please read 1stRead.txt first for Guidance.

alarcon · 18 de Setembro de 2007, 10:07

Por favor Edite seu texto acima e retire dele todas as entradas [size] e [size=valor] que tiver no seu texto para poder diminui-lo, pois assim está tomando muito espaço e dificultando a leitura.

Quando você executou o script scanModem ele criou dentro da sua pasta de usuário que está por sua vez dentro da pasta home uma pasta chamada de Modem, ou seja, /home/seu_usuario/Modem/, e lá existem vários arquivos .txt. Gostaria que você colasse aqui o conteúdo destes três: Conexant.txt, Intel.txt e ModemData.txt

alarcon · 18 de Setembro de 2007, 10:51

Seu notebook possui uma determinada placa de som que também faz o papel de modem, pois se você observar bem o papel que o modem faz nada mais é do que o envio de sinais sonoros.

O que pode se chamar de modem no seu sistema é isso aqui:

00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)

por isso que você diz que o sistema não identifica seu modem, por que na verdade o que existe é a placa de som com uma capacidade especial de executar as funções do modem também.

O driver Smartlink dá suporte para alguns modems High Definition Audio Controller (ICH7 Family), mas não da forma com que ele (o driver Smartlink) é usado por padrão.

O que fiz foi fazer você usar o meu pacote de instalação automática dos modems que usam o driver Smartlink para facilitar as coisas para você já que é um iniciante, mas não vamos utilizá-lo da forma padrão. Quando se instala o meu pacote ele cria um script chamado de sl-modem-daemon que é o responsável pela ativação do modem na hora do boot do PC, só que ele não é capaz de detectar sua forma só as outras formas de uso que são as padrões.

O que fiz foi alterar este script para um que funcionasse com você que ficou assim:

Citar#! /bin/sh
modprobe -r slamr
modprobe -r ungrab-winmodem
slmodemd -c BRAZIL --perm=0666 --alsa hw:0,1 ou hw:0,6 &

Seguindo aquele texto em inglês que colei aqui.

Não sei se você está fazendo os procedimentos de forma correta por que não sei o seu nível de conhecimento sobre linux e muitas vezes um passo que parece simples para mim pode ser difícil para você, portanto cabe a você me falar onde não entendeu o que eu disse ok.

Muitas vezes aqui te pedi determinada informação e você não me respondeu ou respondeu de maneira incompleta e as informações que te peço é muito importante para te ajudar, então peço maior atenção no que pergunto e no que você me responde.

Sei que fazer o modem funcionar, principalmente softmodems, não é uma tarefa fácil, em alguns casos, mas depois que se aprende como, fica-se com um conhecimento formidável sobre os modems e até sobre o linux.

Os passo são os que já informei a você se quiser releia-os e tente outras vezes. Se não funcionar, então tente um hardmodem mesmo.

O driver Smartlink é uma espécie de "coringa", pois funciona com uma quantidade enorme de modems e é sempre testado primeiro se o usuário não sabe qual é o driver correto para o seu modem. Caso não tenha dado certo com ele e você não tenha acesso a hardmodems, então tente drivers da Conexant e/ou da Intel, mas lembro a você sobre o usuário herculesso77 que me parece ter o mesmo tipo de modem que o seu e relatou sucesso usando o driver Smartlink.

Miguel steffen · 18 de Setembro de 2007, 11:10

Bom dia,

Realmente estou "apanhando" nessa brincadeira. Sou iniciante em Linux. Sempre trabalhei com software proprietário e estou decidido que não quero mais trabalhar com os Ruindows da vida.

Confesso também não achei que seria tão dificultoso, pois lendo e relendo tudo que conversamos, penso que fiz todos os procedimentos. Acho que posso ter derrapado em algum passo, vou abaixo tentar responder as últimas questões que você me pediu. Vamos tentar ir por passos. Preciso lembrar que também já estou com um plano B, mas é um pouco frustrante ter que abandonar o modem pelo fato de não conseguir instalar. Particularmente acho que seria uma derrota inclusive para os futuros "leigos" como eu que precisam acessar com discada.

Segue abaixo o comando e seu resultado:

miguel@miguel:~$ lspci -nv
00:00.0 0600: 8086:27a0 (rev 03)
Subsystem: 104d:820f
Flags: bus master, fast devsel, latency 0
Capabilities: <access denied>

00:02.0 0300: 8086:27a2 (rev 03) (prog-if 00 [VGA])
Subsystem: 104d:820f
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at d0100000 (32-bit, non-prefetchable)
I/O ports at 1800
Memory at b0000000 (32-bit, prefetchable)
Memory at d0200000 (32-bit, non-prefetchable)
Capabilities: <access denied>

00:02.1 0380: 8086:27a6 (rev 03)
Subsystem: 104d:820f
Flags: bus master, fast devsel, latency 0
Memory at d0180000 (32-bit, non-prefetchable)
Capabilities: <access denied>

00:1b.0 0403: 8086:27d8 (rev 02)
Subsystem: 104d:820f
Flags: bus master, fast devsel, latency 0, IRQ 22
Memory at d0240000 (64-bit, non-prefetchable)
Capabilities: <access denied>

00:1c.0 0604: 8086:27d0 (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=03, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: c8000000-c9ffffff
Prefetchable memory behind bridge: 00000000c0000000-00000000c1ffffff
Capabilities: <access denied>

00:1c.1 0604: 8086:27d2 (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=05, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: ca000000-cbffffff
Prefetchable memory behind bridge: 00000000c2000000-00000000c3ffffff
Capabilities: <access denied>

00:1c.2 0604: 8086:27d4 (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=06, subordinate=07, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: cc000000-cdffffff
Prefetchable memory behind bridge: 00000000c4000000-00000000c5ffffff
Capabilities: <access denied>

00:1c.3 0604: 8086:27d6 (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=08, subordinate=09, sec-latency=0
I/O behind bridge: 00005000-00005fff
Memory behind bridge: ce000000-cfffffff
Prefetchable memory behind bridge: 00000000c6000000-00000000c7ffffff
Capabilities: <access denied>

00:1d.0 0c03: 8086:27c8 (rev 02) (prog-if 00 [UHCI])
Subsystem: 104d:820f
Flags: bus master, medium devsel, latency 0, IRQ 20
I/O ports at 1820

00:1d.1 0c03: 8086:27c9 (rev 02) (prog-if 00 [UHCI])
Subsystem: 104d:820f
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at 1840

00:1d.2 0c03: 8086:27ca (rev 02) (prog-if 00 [UHCI])
Subsystem: 104d:820f
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 1860

00:1d.3 0c03: 8086:27cb (rev 02) (prog-if 00 [UHCI])
Subsystem: 104d:820f
Flags: bus master, medium devsel, latency 0, IRQ 17
I/O ports at 1880

00:1d.7 0c03: 8086:27cc (rev 02) (prog-if 20 [EHCI])
Subsystem: 104d:820f
Flags: bus master, medium devsel, latency 0, IRQ 20
Memory at d0444000 (32-bit, non-prefetchable)
Capabilities: <access denied>

00:1e.0 0604: 8086:2448 (rev e2) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=0a, subordinate=0e, sec-latency=32
I/O behind bridge: 00006000-00006fff
Memory behind bridge: d0000000-d00fffff
Prefetchable memory behind bridge: 0000000088000000-000000008bffffff
Capabilities: <access denied>

00:1f.0 0601: 8086:27b9 (rev 02)
Subsystem: 104d:820f
Flags: bus master, medium devsel, latency 0
Capabilities: <access denied>

00:1f.1 0101: 8086:27df (rev 02) (prog-if 8a [Master SecP PriP])
Subsystem: 104d:820f
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 01f0
I/O ports at 03f4
I/O ports at 0170
I/O ports at 0374
I/O ports at 1810

00:1f.2 0101: 8086:27c4 (rev 02) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: 104d:820f
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 21
I/O ports at 18d0
I/O ports at 18c4
I/O ports at 18c8
I/O ports at 18c0
I/O ports at 18b0
Memory at d0444400 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>

00:1f.3 0c05: 8086:27da (rev 02)
Subsystem: 104d:820f
Flags: medium devsel, IRQ 10
I/O ports at 18e0

02:00.0 0200: 11ab:4351 (rev 16)
Subsystem: 104d:820f
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at c8000000 (64-bit, non-prefetchable)
I/O ports at 2000
Capabilities: <access denied>

06:00.0 0280: 8086:4222 (rev 02)
Subsystem: 8086:1050
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at cc000000 (32-bit, non-prefetchable)
Capabilities: <access denied>

0a:03.0 0607: 104c:8039
Subsystem: 104d:820f
Flags: bus master, medium devsel, latency 168, IRQ 17
Memory at d0006000 (32-bit, non-prefetchable)
Bus: primary=0a, secondary=0b, subordinate=0e, sec-latency=176
Memory window 0: 88000000-8bfff000 (prefetchable)
Memory window 1: 8c000000-8ffff000
I/O window 0: 00006000-000060ff
I/O window 1: 00006400-000064ff
16-bit legacy interface ports at 0001

0a:03.1 0c00: 104c:803a (prog-if 10 [OHCI])
Subsystem: 104d:820f
Flags: bus master, medium devsel, latency 64, IRQ 17
Memory at d0005000 (32-bit, non-prefetchable)
Memory at d0000000 (32-bit, non-prefetchable)
Capabilities: <access denied>

0a:03.2 0180: 104c:803b
Subsystem: 104d:820f
Flags: bus master, medium devsel, latency 64, IRQ 16
Memory at d0004000 (32-bit, non-prefetchable)
Capabilities: <access denied>

na pŕoxima mensagem envio os txt.

Miguel steffen · 18 de Setembro de 2007, 11:19

Vamos aos txt

Conexant chipset modems section
--------------------------------
Vendors 14f1 is Conexant, inheritor of the former vendor 127a Rockwell modem technology.
There are also Conexant chipsets in some modems from vendors:
   158b Allied Data Tech.,
   1024 Zenith
   141a Apache Micro
   148d Digicom Systems.
Support types are:
hcflinmodem package - for older HCF chipset modems

Intel modems
==============================
Vendor=8086 is Intel, Inc. producing chipsets for 536EP host controller free (HCF) modems,
537 soft modems, several AC'97 softmodem controllers and HDA (High Definition Audio) cards.

For INTEL537 and INTEL536 chipset modems, to updated support sources are:
1) http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/
2) http://phep2.technion.ac.il/linmodems/packages/Intel/537/Intel-537EP-2.70.95.0-for-2.6.20.tar.gz

which was accessed through ArchLinux repository
http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/network/intel-537/?cvsroot=Extra&only_with_tag=CURRENT
and download all cogent patchs(*.patch) there from and also to the same folder as the patches:
http://archlinux.org/~james/kernel26beyond-modules/intel-537-beyond/Intel-537EP-2.70.95.0-suse9.3.tgz
With application of the patches with:
patch -Np0 -i ../flip.patch
patch -Np0 -i ../compile.patch
patch -Np1 -i ../module-parm.patch
patch -Np1 -i ../pm_unregister.patch
patch -Np1 -i ../asmlinkage.patch
patch -Np0 -i ../kernel-2.6.19.patch
patch -Np0 -i ../kernel-2.6.20.patch

After downloading the Intel-537EP-2.70.95.0-for-2.6.20.tar.gz and copying to a Linux partition,
Compile and install with Root permission:
$ make clean
$ make 537
$ su - root
# make install
or under Ubuntu with:
$ sudo make install

Formal Intel support for Linux appears to have ceased updates. But their offical
support packages can be accessed through:
http://developer.intel.com/design/modems/support/drivers.htm

The AC'97/CNR controllers of softmodems usually do NOT use Intel software.
Rather, the modem Subsystem determines the required software support.
Subsystems with Conexant chips require hsfmodem software from http:/www.linuxant.com
Other Subsytems are currently supported by Open Source ALSA drivers plus the slmodemd helper.

The HDA cards may host softmodem chipsets, through a different bridging then the AC'97 types.
Both Conexant chip and ALSA supported chipset types have been encountered.

For the 537 class softmodems, prior to software release 2.70.95.0,
there were distinct support packages:
PCI_id SubSystem_id Older_package Comment
-------------------------------------------------------------------------------
e159:0001 8086:0003 537 TJ320 v2.0 controller
8086:1080 8086:100[7,8,A,0] 537EP 8086:1080 AC'97 controller
8086:1040 8086:1005 537SP 8086:1080 AC'97 controller
various various 537AA_secure primary AC'97 controller
over si3054 chip with SIL25 codec
si == Silicon Instruments
various various 537EA primary CNR controller
over si3038 chip with INT65 codec
--------------------------------------------------------------------------------
But all are currently supported by a single Intel-537EP package
The 537AA and EA types may be alternatively be supported by an ALSA modem driver
and the Smartlink slmodemd.

Intel-536 chipset modems have an onboard DSP (digital signal processor) chip.
They may alternatively be served by the 537EP software, with added CPU burden.

A very detailed installation report cogent to 537 type modems is at:
http://linmodems.technion.ac.il/archive-fifth/msg00541.html

For Debian like distros, a modified install script is at:
http://members.lycos.co.uk/persianlinux/downloads/intel536EP/Intel536_inst_debian

   ======= end Intel section =======

modedata.txt

Only plain text email is forwarded by the DISCUSS@linmodems.org List Server.
Do use the following as the email Subject Line:
SomeName, YourCountry kernel 2.6.20-16-generic
This will alert cogent experts, and distinguish cases in the Archives.
YourCountry will enable Country Code guidance.
Occassionally responses are blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org .
Local Linux experts can be found through: http://www.linux.org/groups/index.html
-------------------------- System information ----------------------------
CPU=i686,
Linux version 2.6.20-16-generic (root@terranova) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Fri Aug 31 00:55:27 UTC 2007
scanModem update of: 2007_Sept_07

There are no blacklisted modem drivers in /etc/modprobe* files
USB modem not detected by lsusb

Several modems are supported by drivers with ALSA, the Advanced Linux Sound Architecture software.
Copying ALSA diagnostics to Modem/ALSAroot.tgz
ALSAversion = 1.0.13

Modem or candidate host audio card have firmware information and diagnostics:

PCI slot   PCI ID      SubsystemID   Name
----------   ---------   ---------   --------------
00:1b.0   8086:27d8   104d:820f   Audio device: Intel Corporation 82801G

Modem interrupt assignment and sharing:
22: 243272 0 IO-APIC-fasteoi HDA Intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 18.164000] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 22
[ 18.164000] PCI: Setting latency timer of device 0000:00:1b.0 to 64

=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===

8086:27d8 is a High Definition Audio card, possibly hosting a soft modem.
Bootup diagnostics lack ALSA data.

The HDA modem codec file is: /proc/asound/card0/codec#1
-----------------------------------
Codec: Conexant ID 2c06
Address: 1
Vendor Id: 0x14f12c06
Subsystem Id: 0x104d1700
Revision Id: 0x100000

The audio card hosts a softmodem chip with Vendor ID: 0x14f12c06

14f1 is the Conexant Vendor ID, and 0x14f12c06 a softmodem chipset.
Get a hsfmodem package through http://www.linuxant.com

For candidate modem in PCI bus: 00:1b.0
Class 0403: 8086:27d8 Audio device: Intel Corporation 82801G
Primary PCI_id 8086:27d8
Subsystem PCI_id 104d:820f
Softmodem codec or Vendor from diagnostics: ID
from Archives:

Lacking a dsp (digital signal processing) chip, the modem is a software
intensive or "softmodem" type. Its primary controller manages the traffic
with the CPU. But the software needed is specified in the Subsystem.
-----------------------------------------
Support type needed or chipset:   hsfmodem

The diagnostic outputs for this softmodem section have their raw information in
folders and text files under /proc/asound/ which you can browse. The information
is from files:
   /proc/asound/pcm
-------------------------------
00-02: ALC262 Analog : ALC262 Analog : capture 2
00-00: ALC262 Analog : ALC262 Analog : playback 1 : capture 2

   /proc/asound/modules
-------------------------------
0 snd_hda_intel
   14f12c06
-------------------------------

-------------------------------
Current support status of HDA cards is:
Vendor IDs Chip maker Support type
---------- ---------- -------------
0x14f12bfa Conexant hsfmodem , not slmodemd compatible
0x14f12c06 Conexant hsfmodem , not slmodemd compatible
0x11c13026 AgereSystems snd-hda-intel, slmodemd supported
0x11c11040 AgereSystems " " support not yet available.
0x11c13055 AgereSystems " " , "
0x163c3055 Smartlink " " , "
0x163c3155 " " " , "
0x10573055 Motorola " " , "
0x10573155 " " " , ""
as of October 2006.

   /proc/asound/card0/codec#1
-------------------------------

and from the command:
   aplay -l | grep -i modem

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

Writing 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 Conexant.txt

The hsfmodem package serves a great variety of Conexant chipset modems.
From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
download hsfmodem_VersionSpec_k2.6.20_16_generic_ubuntu_i386.deb.zip
with 2.6.20_16_generic equivalent to 2.6.20-16-generic, your kernel version.
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 Testing.txt for details.

Read Conexant.txt

Writing Conexant.txt

Completed candidate modem analyses.

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

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

Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.1
linuc_headers base folder /lib/modules/2.6.20-16-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 libc6-dev (and for Debian/Ubuntu, linux-libc-dev). The also required headers of package libc6 are commonly installed by default.

If a driver compilation files with message including some lack of some FileName.h (stdio.h for example.
Some additional kernel-header files need installation to /usr/include.
For Debian/Ubuntu related distributions, run the following command to display the needed package list:
$ sudo apt-get -s install linux-kernel-devel
While some of the files may be on the install CD, others may have to be found through http://packages.ubuntu.com

For Ubuntu Feisty, additional packages required were:
libc6-dev linux-libc-dev
available through http://packages.ubuntu.com/ , if not on the install CD.
Such packages may have different names for other Linux distributions.
Try installing just the libc6-dev, then test the compile again.

Checking pppd properties:
   -rwsr-xr-- 1 root dip 269224 2007-04-05 00:41 /usr/sbin/pppd

In case of an "error 17" "serial loopback" problem, see:
http://phep2.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/YourSystem.txt concerning other COMM channels: eth0
Which can interfere with Browser naviagation.

Don't worry about the following, it is for the 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:
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/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)
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
Within any ancient /etc/devfs files:

Within ancient kernel 2.4.n /etc/module.conf files:

--------- end modem support lines --------

hsfmodem package - for hsfmodem chipsets, including those hosted on some High Definition Audio (HDA) cards and some USB modems.

The 14f1:2f00 chipset has a free support package: http://ubuntuforums.org/showthread.php?t=180632

For owners of Dell computers there is a free package for HSF support requiring compiling. For details:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg01830.html
http://search.dell.com/results.aspx?s=gen&c=us&l=en&cs=&k=hsfmodem&cat=sup
The download for package hsfmodem_7.60.00.06oem_i386.deb is: http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R155004&SystemID=INSPIRONI6400/E1505&servicetag=&os=UBLN&osl=en&deviceid=8593&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=1&libid=20&fileid=206745

But the orginal source of the hsfmodem Linux code packages for
Conexant chipset modems is http://www.linuxant.com/drivers.
There are free test packages available there providing only a low 14K speed.
A software key must be purchased to enable full speed 56K service.
The HCF chipset modems have a dsp
(digital signal processing) chip, while the HSF lack a dsp and
this function is performed by the CPU under software direction.

For a crash issue with the 2.6.16 kernel, please make sure that your
kernel was not compiled with the CONFIG_4KSTACKS option is not set as
the HSF modem driver is known to requires more than 4K of stacks in a
few cases. The are several alternate kernels supporting hsfmodem
available at http://www.linuxant.com. Look for their Link/URL on the
page with your needed hsfmodem package.

To get software, go to http://www.linuxant.com/drivers
-Find the HCF or HSF menu in the left part of the screen.
-Read README.
-Read INSTALLATION.
-Click DOWNLOAD.
-Accept conditions.
-Find text: "You can download HCF (or HSF) modem packages from the driver
download page." and click there.
-Look for your distribution, your processor, and your kernel.
-Download the matching file.
-Read again and, if you do this under Windows, print the installation
instructions matching the kind of driver file which you downloaded.
-Now just follow these instructions.

http://www.linuxant.com/drivers/hsf/downloads-patches.php has patches
that may be necessary for recent kernels.

A detailed software installation example is provided at:
http://linmodems.technion.ac.il/archive-fourth/msg00350.html

After loading of HSF drivers, there will be selective displayed by command:
# /sbin/lsmod | grep hsf
with an output like:
-----------
Module Size Used by Tainted: P
hsfich 119116 0 (autoclean)
hsfserial 26388 0 (autoclean)
hsfengine 1126348 0 (autoclean) [hsfserial]
hsfosspec 35328 0 (autoclean) [hsfich hsfserial hsfengine]
---------
plus many others not modem related.
While drivers are pre-compiled for some Linux distributions,
the installation of the HCF/HSF packages DOES in general require kernel-source/
preparation, as described in Modem/DriverCompiling.txt.

There is good support from Linuxant.com, but first gather data.
In a terminal
# su - root or prefix commands with sudo for Ubuntu related distributions.
hsfconfig --dumpdiag
If this command crashes your machine, please try instead:
hsfconfig --dumpdiag --noprobe
Send the hsfdiag.txt located in the folder /tmp/
to MODEM.SUPPORT@linuxant.com

There is a conflict between modules snd-intel8x0m and hsfmc97ich.
The snd-intel8x0m Must be loaded first or the system may hang upon hsfmc97ich insertion.
http://linmodems.technion.ac.il/archive-fourth/msg03027.html

http://www.lorenzobettini.it/linux/LinuxSonyVaioVGN-S5VP_B reports a
problem and solution in stalling a key, after testing of the free low
speed test package.

From http://www.linuxant.com/drivers,
get package(s) with 2.6.20_16_generic included in the filename.
If such a package cannot be found, get the generic package,
for which compiling drivers will be necessary.

Copy the package to your Linux partition. Unpack with:
unzip *.zip
Under root/admin permission, install with package with
   sudo dpkg -i *.deb
Should the modem hardware not be a Conexant type,
the installation will ABORT with an informative message.

Continue with any output instructions. Following a successfull installation,
The modem should be detected during the root/admin command:
   wvdialconf /etc/wvdial.conf
Edit your personal information in with:
$ sudo gedit /etc/wvdial.conf
See details on dialout usage in Testing.txt

   ====== end Conexant section section =======

alarcon · 18 de Setembro de 2007, 11:21

pela sua resposta seu modem tem

Como ID 8086:27d8 e Subsystem 104d:820f

Se ele tive esta ID 8086:27d8 e este Subsystem 14F1:2bfa ou este outro Subsystem 14F1:2c06 usaria o driver Conexant e o driver Smartlink para este caso não funcionaria, mas não foi encontrado este subsystem no que você retornou.

Atenção: Retiro o que falei logo aqui acima neste mesmo texto.

Pelo que li agora no seu Modemdata.txt ele informa que seu modem é um Conexant com esta ID 14f1:2c06

CitarThe audio card hosts a softmodem chip with Vendor ID: 0x14f12c06

14f1 is the Conexant Vendor ID, and 0x14f12c06 a softmodem chipset.
Get a hsfmodem package through http://www.linuxant.com

e por esta tabela:

Current support status of HDA cards is:
Vendor IDs Chip maker Support type
---------- ---------- -------------
0x14f12bfa Conexant hsfmodem , not slmodemd compatible
0x14f12c06 Conexant hsfmodem , not slmodemd compatible
0x11c13026 AgereSystems snd-hda-intel, slmodemd supported
0x11c11040 AgereSystems " " support not yet available.
0x11c13055 AgereSystems " " , "
0x163c3055 Smartlink " " , "
0x163c3155 " " " , "
0x10573055 Motorola " " , "
0x10573155 " " " , ""
as of October 2006.

veja que ele não é compatível com o driver Smartlink (not slmodemd compatible).

Veja que todos os outros (AgereSystem, Smartlink,Motorola) poderiam usar o driver Smartlink, menos os Conexant.

A conexant tem um bom driver para softmodems no linux só que eles não são livres, ou seja, você terá de pagar por uma licença que libera sua velocidade para 56k, pois sem a licença ele só funciona em 14k o que é uma piada para os dias de hoje.

OBS: Te enviei agora uma mensagem particular (mp) veja aí.

README do driver Conexant:

CitarThe following modem devices are recognized by the driver:
HDA (High Definition Audio) Modems

   only under 2.6.16 or newer kernels

   HDA VENDOR ID 14F12BFA
   HDA VENDOR ID 14F12C06

Miguel steffen · 19 de Setembro de 2007, 09:16

Caríssimo Alarcon,

Bem, vamos aos agradecimentos. Finalmente meu modem está funcionando. Tá certo que com toda a precariedade de uma linha discada.

MUITO OBRIGADO!!!!

Abraços.

Miguel

alarcon · 19 de Setembro de 2007, 09:41

Citação de: Miguel steffen online 19 de Setembro de 2007, 09:16
Caríssimo Alarcon,

Bem, vamos aos agradecimentos. Finalmente meu modem está funcionando. Tá certo que com toda a precariedade de uma linha discada.

MUITO OBRIGADO!!!!

Abraços.

Miguel

OK Miguel !

Que bom.

Por favor, acrescente no seu título a palavra resolvido.

O note não identifica o modem (RESOLVIDO)

Miguel steffen

alarcon

alarcon

Miguel steffen

alarcon

alarcon

Miguel steffen

Miguel steffen

alarcon

Miguel steffen

alarcon