Please, somebody can help me with this modem ???
Attached is the file ModemData.txt generated by "scanModem" software ...
I try to install following the instructions by "Intel.txt" generated
by "scanModem" but "error" apear ...
Tank's ...
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
Bem-vindo ao Librix ( kernel 2.6.22-gentoo-r8_dsk_smp
With this Subject Line cogent experts will be alerted, and useful case names left in the Archive.
YourCountry will enable Country specific guidance. Your contry's local Linux experts
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,
Bem-vindo ao Librix (
Linux version 2.6.22-gentoo-r8_dsk_smp (root@padme) (gcc version 4.1.2 (Gentoo 4.1.2 p1.1)) #1 SMP PREEMPT Mon Apr 21 15:53:03 Local time zone must be set--
scanModem update of: 2008_05_02
Blacklisted modem driver lines in /etc/modprobe* files are:
/etc/modprobe.conf:blacklist snd-intel8x0m
/etc/modprobe.d/slmodem:blacklist snd-intel8x0m
Attached USB devices are:
ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
ID 08ff:1600 AuthenTec, Inc.
ID 05e3:0503 Genesys Logic, Inc.
USB modems not recognized
For candidate card in slot 00:03.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:03.0 8086:2a04 8086:5754 Communication controller: Intel Corporation Mobile MEI Controller
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 00:03.0 ----
For candidate card in slot 00:03.3, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:03.3 8086:2a07 8086:5754 Serial controller: Intel Corporation Mobile KT Controller
Modem interrupt assignment and sharing:
16: 4 1 IO-APIC-fasteoi serial
--- Bootup diagnostics for card in PCI slot 00:03.3 ----
ACPI: PCI Interrupt 0000:00:03.3[B] -> GSI 17 (level, low) -> IRQ 16
0000:00:03.3: ttyS0 at I/O 0x1440 (irq = 16) is a 16550A
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 8086:1001 Audio device: Intel Corporation 82801H
Modem interrupt assignment and sharing:
23: 3545 10 IO-APIC-fasteoi HDA Intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23
PCI: Setting latency timer of device 0000:00:1b.0 to 64
===== Advanced Linux Sound Architecture (ALSA) diagnostics =====
The ALSA packages provide audio support and also drivers for some modems.
ALSA diagnostics are written during bootup to /proc/asound/ folders.
PCI slot 00:1b.0 has a High Definition Audio Card
The ALSA verion is 1.0.14
The modem cards detected by "aplay -l" are:
The /proc/asound/pcm file reports:
-----------------------
00-02: ALC262 Analog : ALC262 Analog : capture 2
00-00: ALC262 Analog : ALC262 Analog : playback 1 : capture 2
about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0x50420000 irq 23
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 00:03.3:
Modem chipset detected on
CLASS="Class 0700: 8086:2a07"
NAME="Serial controller: Intel Corporation Mobile KT Controller "
SUBSYS=8086:5754
PCIDEV=8086:2a07
IRQ=16
SOFT=8086:2a07.MC97
IDENT=slmodemd
SLMODEMD_DEVICE=modem:1
For candidate modem in: 00:03.3
Class 0700: 8086:2a07 Serial controller: Intel Corporation Mobile KT Controller
Primary device ID: 8086:2a07
Subsystem PCI_id 8086:5754
Softmodem codec or chipset from diagnostics:
from Archives:
Support type needed or chipset: slmodemd
An ALSA (Advanced Linux Sound Architecture) modem driver:
provides Low Level support enabling contact with the modem hardware.
For all BUT Conexant chip soft modems (using hsfmodem software)
complementary High Level support is through a Smartlink utility: slmodemd
Download from http://linmodems.technion.ac.il/packages/smartlink/
the package SLMODEMD.gcc4.1.tar.gz having a compiled slmodemd. Unpack under Linux with:
$ tar zxf SLMODEMD.gcc4.1.tar.gz
and read instructions therein. But briefly, the modem is setup with command:
slmodemd -c YOUR_COUNTRY --alsa modem:1
reporting dynamic creation of ports:
/dev/ttySL0 --> /dev/pts/N , with N some number
Read Smartlink.txt and Modem/YourSystem.txt for follow through guidance.
----------------end Softmodem section --------------
Writing Intel.txt
Writing Smartlink.txt
============ end Smartlink section =====================
Predictive diagnostics for card in bus 00:03.0:
Modem chipset not detected on
CLASS="Class 0780: 8086:2a04"
NAME="Communication controller: Intel Corporation Mobile MEI Controller "
SUBSYS=8086:5754
PCIDEV=8086:2a04
IRQ=11
For candidate modem in: 00:03.0
Class 0780: 8086:2a04 Communication controller: Intel Corporation Mobile MEI Controller
Primary device ID: 8086:2a04
Support type needed or chipset:
----------------end Softmodem section --------------
scanModem could not identify the Support Type needed from diagnosics or archives.
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.
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
CLASS="Class 0403: 8086:284b"
NAME="Audio device: Intel Corporation 82801H "
SUBSYS=8086:1001
PCIDEV=8086:284b
IRQ=23
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:
wvdialconf /etc/wvdial.conf
For candidate modem in: 00:1b.0
Class 0403: 8086:284b Audio device: Intel Corporation 82801H
Primary device ID: 8086:284b
Subsystem PCI_id 8086:1001
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 Conexant.txt
The following ALSA alternative CANNOT work with Conexant modems.
2) An ALSA modem driver plus slmodemd. Read Smartlink.txt for details, and
to test get the package SLMODEMD.gcc4.1.tar.gz from:
http://linmodems.technion.ac.il/packages/smartlink/
----------------end Softmodem section --------------
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.22-gentoo-r8_dsk_smp/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. 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 package
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:
-r-s--x--x 1 root root 284948 2008-04-18 23:42 /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)
chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
lock
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.
==========================================================
#
# UDEV rule for ltmodem
# creates symlink /dev/modem to /dev/ttyLT?, and takes care of permissions
KERNEL=="ttyLTM[0-9]", NAME="%k", MODE="0660", GROUP="dialout", SYMLINK="modem"
KERNEL=="slamr", NAME="slamr0" GROUP="dialout"
KERNEL=="slusb", NAME="slusb0" GROUP="dialout" RUN+="slmodem_usb.sh"
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link:
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
/etc/udev/rules.d/55-ltmodem.rules:# UDEV rule for ltmodem
/etc/udev/rules.d/55-ltmodem.rules:# creates symlink /dev/modem to /dev/ttyLT?, and takes care of permissions
/etc/udev/rules.d/55-ltmodem.rules:KERNEL=="ttyLTM[0-9]", NAME="%k", MODE="0660", GROUP="dialout", SYMLINK="modem"
/etc/udev/rules.d/55-slmodem.rules:KERNEL=="slusb", NAME="slusb0" GROUP="dialout" RUN+="slmodem_usb.sh"
Within /etc/modprobe.conf files:
/etc/modprobe.conf:alias /dev/modem ltserial
/etc/modprobe.conf:### update-modules: start processing /etc/modprobe.d/slmodem
/etc/modprobe.conf:### update-modules: end processing /etc/modprobe.d/slmodem
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
/etc/modules.d/slmodem:# slmodem 2.9.x kernel modules' configuration file
/etc/modules.d/slmodem:# install slamr modprobe --ignore-install ungrab-winmodem ; sleep 5 ; modprobe --ignore-install slamr
/etc/modules.d/slmodem:# install slusb modprobe --ignore-install ungrab-winmodem ; sleep 5 ; modprobe --ignore-install slusb
/etc/modules.d/ltmodem:alias /dev/modem ltserial
--------- end modem support lines --------
