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.32-21-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=x86_64, Ubuntu , ALSA_version=1.0.21
Linux version 2.6.32-21-generic (buildd@yellow) (gcc version 4.4.3
(Ubuntu 4.4.3-4ubuntu5) ) #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC 2010
scanModem update of: 2010_05_29
Distrib_ID=Ubuntu
DistribCodeName=lucid
AptRepositoryStem=http://nz.archive.ubuntu.com/ubuntu/
Presently install your Linux Distributions dkms package. It provides for
automated driver updates,
following upgrade of your kernel. For details see
http://linux.dell.com/projects.shtml#dkms
Some modem drivers can only be used in 32 bit modem on x86_64 systems,
while some others are competent on x86_64 Systems. Cases are:
1) http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html
for the snd-hda-intel audio+modem driver. Also applicable to AC97 modem
controllers.
In both cases, 32 bit libraries must be installed to support the
slmodemd helper having a precompiled 32 bit component.
2) For USB modems using the slusb.ko driver. 32 bit libraries must be
installed to support the slmodemd helper having a precompiled 32 bit
component
3) The hsfmodem and hcfpcimodem drivers for Conexant chipsest modes are
x86_64 competent.
4) agrsm packages for LSI/AgereSystems softmodems are not competent on
x86_64 systems.
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
snd_hda_intel
Attached USB devices are:
ID 058f:6387 Alcor Micro Corp. Transcend JetFlash Flash Drive
ID 04a9:173b Canon, Inc.
ID 03f0:7d04 Hewlett-Packard DeskJet F2100 Printer series
ID 0718:0611 Imation Corp.
ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
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
Hey all,
Can anyone give me simple directions on how to make this modem work?
Ive heard that there are new modems that dont have linux support, should
I instead be looking for an older external serial modem?
Here is my scanModem output.
Cheers
Glenn.
Candidate PCI devices with modem chips are:
01:05.0 Communication controller: Agere Systems Lucent V.92 Data/Fax Modem
00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio
(rev a2)
High Definition Audio cards can host modem chips.
For candidate card in slot 01:05.0, firmware information and bootup
diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
01:05.0 11c1:0620 11c1:0620 Communication controller: Agere
Systems Lucent V.92 Data/Fax Modem
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 01:05.0 ----
[ 0.169110] pci 0000:01:05.0: reg 10 io port: [0xec00-0xecff]
[ 0.169141] pci 0000:01:05.0: PME# supported from D3hot D3cold
[ 0.169144] pci 0000:01:05.0: PME# disabled
The PCI slot 01:05.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 00:05.0, firmware information and bootup
diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:05.0 10de:03f0 103c:3039 Audio device: nVidia Corporation
MCP61 High Definition Audio
Modem interrupt assignment and sharing:
23: 35605 IO-APIC-fasteoi ehci_hcd:usb1, HDA Intel
--- Bootup diagnostics for card in PCI slot 00:05.0 ----
[ 0.168689] pci 0000:00:05.0: reg 10 32bit mmio: [0xfe024000-0xfe027fff]
[ 0.168711] pci 0000:00:05.0: PME# supported from D3hot D3cold
[ 0.168714] pci 0000:00:05.0: PME# disabled
[ 15.630525] HDA Intel 0000:00:05.0: PCI INT B -> Link[AAZA] -> GSI 23
(level, low) -> IRQ 23
[ 15.630553] HDA Intel 0000:00:05.0: setting latency timer to 64
[ 17.962658] input: HDA Digital PCBeep as
/devices/pci0000:00/0000:00:05.0/input/input5
The PCI slot 00:05.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 01:05.0:
Modem chipset detected on
NAME="Communication controller: Agere Systems Lucent V.92 Data/Fax Modem"
CLASS=0780
PCIDEV=11c1:0620
SUBSYS=11c1:0620
IRQ=10
HDA2=00:05.0
IDENT=agrsm
For candidate modem in: 01:05.0
0780 Communication controller: Agere Systems Lucent V.92 Data/Fax Modem
Primary device ID: 11c1:0620
Support type needed or chipset: agrsm
There is no agrsm software support for x86_64 systems, through the
modem may be
supported on Intel/i386 installations, which do more slowly servce
x86_64 processors.
The AgereSystems/LSI agrsm code supports compiling of a agrmodem +
agrserial driver pair.
There are a few different chipsets which use this driver pair, but they
use different code resources:
Chipsets KV* PackageNames (most current as of November 2009)
----------------------------------------------------------------------------------------------
11c1:048c and 11c1:048f 2.6.29
agrsm048pci-2.1.60_20100108_i386.deb or agrsm048pci-2.1.60_20100108.tar.gz
11c1:0620 2.6.31
agrsm06pci-2.1.80_20100106_i386.deb or agrsm06pci-2.1.80~20100106.tar.gz !!
11c11040 (on HDA audio cards) 2.6.31 agrsm-11c11040_20091225_i386.deb
or agrsm-11c11040-2.1.80~20091225.tar.bz2 !!
All available at:
http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
Additionally there are;
automation & testing agrsm-tools_0.0.1_all.deb or
agrsm-tools-0.0.1-2.noarch.rpm
General background agrsm_howto.txt
------------------------------------------------------------------------------------------------
* KV == latest kernel release with a reported success
!! Latest update with major credit to Nikolay Zhuravlev
But see conflict issue:
http://linmodems.technion.ac.il/bigarch/archive-nineth/msg02753.html
For the 11c11040 chip with kernels 2.6.31 and later a change in a
modules loading settingmay be necessary.
Within the file /etc/modprobe.d/alsa-base.conf (or equivalent for
your Distro), change the phrase:
options snd-hda-intel power_save=10
to:
options snd-hda-intel power_save=0
or the agrsm drivers will not function. For Ubuntu related systems
this can be done with:
$ sudo gedit /etc/modprobe.d/alsa-base.conf
Report from Bjorn Wielens:
Please note- trying to load the modules on a OpenSuSE 11.2 system gives
an error about the module_version symbol. Using:
# modprobe --force agrmodem
# modprobe --force agrserial
is necessary to load the drivers, and does not appear to cause ill effects.
All of the above packages are dkms competent. This means that if your
Linux distros dkms package
is previously installed, if provides for future updates matching
forthcoming kernels.
-------------- end Agere Systems section -------------------
Predictive diagnostics for card in bus 00:05.0:
Modem chipset not detected on
NAME="Audio device: nVidia Corporation MCP61 High Definition Audio "
CLASS=0403
PCIDEV=10de:03f0
SUBSYS=103c:3039
IRQ=23
For candidate modem in: 00:05.0
0403 Audio device: nVidia Corporation MCP61 High Definition Audio
Primary device ID: 10de:03f0
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.4.3
and the compiler used in kernel assembly: 4.4.3
The patch utility is needed for compiling ALSA drivers, and possibly
others.
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.4
linuc_headers base folder /lib/modules/2.6.32-21-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 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
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
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:
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
Within /etc/modprobe.conf files:
/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
/etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf: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 --------
