Greetings from Cuba,
I am having a curious problem with an Agere Lucent 11c1:0620 Modem:
---------------------------------------------------------------------
$ sudo lspci -s 02:02.0 -v
02:02.0 Communication controller: Agere Systems Lucent V.92 Data/Fax
Modem
Subsystem: Agere Systems Lucent V.92 Data/Fax Modem
Flags: fast Back2Back, medium devsel, IRQ 17
I/O ports at 1000 [size=256]
Capabilities: [f8] Power Management version 3
---------------------------------------------------------------------
I'm using 'agrsm06pci-2.1.80~20100106.tar.gz' drivers with Ubuntu Lucid
Lynx 10.04.1 LTS and they work just fine until I Suspend or Hibernate my
PC, you can see the 'ModemData-before-hibernation.txt' attached for
detailed information.
Whenever I resume the PC from a suspended/hibernated state the Modem
fails to work, although the drivers are still loaded.
Using 'wvdial' hangs the OS for about 30 sec and fails:
---------------------------------------------------------------------
$ time wvdial
--> WvDial: Internet dialer version 1.60
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
--> Re-Sending: ATZ
--> Modem not responding.
real 0m26.185s
user 0m0.004s
sys 0m15.241s
---------------------------------------------------------------------
'wvdialconf' hangs too when trying with '115200 baud', and fails in
detecting the Modem:
---------------------------------------------------------------------
$ wvdialconf /tmp/delme
Editing `/tmp/delme'.
Scanning your serial ports for a modem.
WvModem<*1>: Cannot set information for serial port.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S1 S2 S3
ttySAGR<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttySAGR<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttySAGR<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
---------------------------------------------------------------------
Normally the output of 'wvdialconf' is like this:
---------------------------------------------------------------------
$ wvdialconf /tmp/delme
Editing `/tmp/delme'.
Scanning your serial ports for a modem.
WvModem<*1>: Cannot set information for serial port.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S1 S2 S3
WvModem<*1>: Cannot set information for serial port.
ttySAGR<*1>: ATQ0 V1 E1 -- OK
ttySAGR<*1>: ATQ0 V1 E1 Z -- OK
ttySAGR<*1>: ATQ0 V1 E1 S0=0 -- OK
ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttySAGR<*1>: Modem Identifier: ATI -- Agere SoftModem Version 2.1.80.0
ttySAGR<*1>: Speed 4800: AT -- OK
ttySAGR<*1>: Speed 9600: AT -- OK
ttySAGR<*1>: Speed 19200: AT -- OK
ttySAGR<*1>: Speed 38400: AT -- OK
ttySAGR<*1>: Speed 57600: AT -- OK
ttySAGR<*1>: Speed 115200: AT -- OK
ttySAGR<*1>: Max speed is 115200; that should be safe.
ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found a modem on /dev/ttySAGR.
/tmp/delme<Warn>: Can't open '/tmp/delme' for reading: No such file or
directory
/tmp/delme<Warn>: ...starting with blank configuration.
Modem configuration written to /tmp/delme.
ttySAGR<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
---------------------------------------------------------------------
The other attachment 'ModemData-after-hibernation.txt' which is as its
name suggests 'ModemData.txt' after an hibernate/suspend shows subtle
differences in 'Modem interrupt assignment and sharing' from the
original one, I can only assume the issue is with assigning IRQs for the
Modem and conflicting with the Sound Card, but I'm just guessing here...
---------------------------------------------------------------------
The workaround that I've been using is unloading the drivers *before*
hibernating/suspending:
---------------------------------------------------------------------
$ sudo modprobe -r agrserial && sudo modprobe -r agrmodem
---------------------------------------------------------------------
...and reloading it again *after* resuming:
---------------------------------------------------------------------
$ sudo modprobe agrmodem && sudo modprobe agrserial
$ if test ! -L /dev/modem -a ! -L /dev/ttySAGR; then \
sudo ln -s /dev/ttyAGS3 /dev/ttySAGR && \
sudo ln -s /dev/ttyAGS3 /dev/modem; \
fi
---------------------------------------------------------------------
If I try to unload/load the drivers *after* a problematic
hibernate/suspend (without unloading the drivers previously) the OS
hangs, becoming unresponsive even to Alt+SysRq keys, leaving me only
with the hard way to reboot :/
I tried to set the subject the most generic way possible, I know this
affects all Ubuntu 10.04 PC using this specific Modem and Drivers, I've
tried this configuration in other two PCs, with the same results.
Any help would be greatly appreciated, if there is no solution at the
moment, I gladly would like to help fixing it with the help of experts
out there.
Regards,
Aliet
--
Este mensaje le ha llegado mediante el servicio de correo electronico que ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema Nacional de Salud. La persona que envia este correo asume el compromiso de usar el servicio a tales fines y cumplir con las regulaciones establecidas
Infomed: http://www.sld.cu/
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-24-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=i686, Ubuntu , ALSA_version=1.0.21
Linux version 2.6.32-24-generic (buildd@palmer) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #42-Ubuntu SMP Fri Aug 20 14:24:04 UTC 2010
scanModem update of: 2011_02_04
The modem symbolic link is /dev/modem -> /dev/ttyAGS3
Distrib_ID=Ubuntu
DistribCodeName=lucid
AptRepositoryStem=http://cu.archive.ubuntu.com/ubuntu/ file:///media/DATA_750/ubuntu/mirror/ubuntu.fcie.uclv.edu.cu/ file:///home/under/Aliet/lucid_lynx/mirror/10.12.43.44/ubuntu/ deb
The dkms driver upgrade utilities are installed,
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
snd_hda_intel agrmodem agrserial
Attached USB devices are:
ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
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
Candidate PCI devices with modem chips are:
02:02.0 Communication controller: Agere Systems Lucent V.92 Data/Fax Modem
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01)
High Definition Audio cards can host modem chips.
For candidate card in slot 02:02.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
02:02.0 11c1:0620 11c1:0620 Communication controller: Agere Systems Lucent V.92 Data/Fax Modem
Modem interrupt assignment and sharing:
17: 974826 0 IO-APIC-fasteoi
--- Bootup diagnostics for card in PCI slot 02:02.0 ----
[ 0.192159] pci 0000:02:02.0: reg 10 io port: [0x1000-0x10ff]
[ 0.192210] pci 0000:02:02.0: PME# supported from D3hot D3cold
[ 0.192215] pci 0000:02:02.0: PME# disabled
[ 1417.818836] pci 0000:02:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[33891.598230] pci 0000:02:02.0: PCI INT A disabled
[33892.081780] pci 0000:02:02.0: restoring config space at offset 0x1 (was 0x2900207, writing 0x2900203)
[33892.222808] pci 0000:02:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[57549.312661] pci 0000:02:02.0: PCI INT A disabled
[57549.869677] pci 0000:02:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
[57549.869694] pci 0000:02:02.0: restoring config space at offset 0x4 (was 0x1, writing 0x1001)
[57549.869699] pci 0000:02:02.0: restoring config space at offset 0x3 (was 0x0, writing 0x2000)
[57549.869706] pci 0000:02:02.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900203)
[57549.970708] pci 0000:02:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
The PCI slot 02:02.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:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:27d8 8086:d607 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller
Modem interrupt assignment and sharing:
22: 13562 0 IO-APIC-fasteoi HDA Intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.191036] pci 0000:00:1b.0: reg 10 64bit mmio: [0x901c0000-0x901c3fff]
[ 0.191081] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.191086] pci 0000:00:1b.0: PME# disabled
[ 13.155513] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 13.155544] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 13.286999] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input5
[33891.700562] HDA Intel 0000:00:1b.0: PCI INT A disabled
[33891.716091] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete after 117.648 msecs
[33892.081350] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100006, writing 0x100002)
[33892.216191] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[33892.216198] HDA Intel 0000:00:1b.0: setting latency timer to 64
[57549.432058] HDA Intel 0000:00:1b.0: PCI INT A disabled
[57549.448029] PM: suspend of drv:HDA Intel dev:0000:00:1b.0 complete after 119.891 msecs
[57549.869091] HDA Intel 0000:00:1b.0: restoring config space at offset 0xf (was 0x100, writing 0x109)
[57549.869106] HDA Intel 0000:00:1b.0: restoring config space at offset 0x4 (was 0x80000004, writing 0x901c0004)
[57549.869111] HDA Intel 0000:00:1b.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[57549.869116] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100002)
[57549.968184] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[57549.968191] HDA Intel 0000:00:1b.0: setting latency timer to 64
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@xxxxxxxxxxxxx
if help is needed.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 02:02.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=17
HDA2=00:1b.0
IDENT=agrsm
For candidate modem in: 02:02.0
0780 Communication controller: Agere Systems Lucent V.92 Data/Fax Modem
Primary device ID: 11c1:0620
Support type needed or chipset: agrsm
Writing DOCs/Intel.txt
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:1b.0:
Modem chipset not detected on
NAME="Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller "
CLASS=0403
PCIDEV=8086:27d8
SUBSYS=8086:d607
IRQ=22
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller
Primary device ID: 8086:27d8
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
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.4
linuc_headers base folder /lib/modules/2.6.32-24-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.
Compressed files at: /usr/src/alsa-driver.tar.bz2
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:
-rwsr-xr-- 1 root dip 273312 2010-03-06 22:59 /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
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.
Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link: lrwxrwxrwx 1 root root 12 2011-03-21 20:22 /dev/modem -> /dev/ttyAGS3
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
Within /etc/modprobe.conf files:
/etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
/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
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
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-24-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=i686, Ubuntu , ALSA_version=1.0.21
Linux version 2.6.32-24-generic (buildd@palmer) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #42-Ubuntu SMP Fri Aug 20 14:24:04 UTC 2010
scanModem update of: 2011_02_04
The modem symbolic link is /dev/modem -> /dev/ttyAGS3
Distrib_ID=Ubuntu
DistribCodeName=lucid
AptRepositoryStem=http://cu.archive.ubuntu.com/ubuntu/ file:///media/DATA_750/ubuntu/mirror/ubuntu.fcie.uclv.edu.cu/ file:///home/under/Aliet/lucid_lynx/mirror/10.12.43.44/ubuntu/ deb
The dkms driver upgrade utilities are installed,
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
snd_hda_intel agrmodem agrserial
Attached USB devices are:
ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
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
Candidate PCI devices with modem chips are:
02:02.0 Communication controller: Agere Systems Lucent V.92 Data/Fax Modem
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01)
High Definition Audio cards can host modem chips.
For candidate card in slot 02:02.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
02:02.0 11c1:0620 11c1:0620 Communication controller: Agere Systems Lucent V.92 Data/Fax Modem
Modem interrupt assignment and sharing:
17: 1257466 0 IO-APIC-fasteoi LSI Mdm
--- Bootup diagnostics for card in PCI slot 02:02.0 ----
[ 0.192159] pci 0000:02:02.0: reg 10 io port: [0x1000-0x10ff]
[ 0.192210] pci 0000:02:02.0: PME# supported from D3hot D3cold
[ 0.192215] pci 0000:02:02.0: PME# disabled
[ 1417.818836] pci 0000:02:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[33891.598230] pci 0000:02:02.0: PCI INT A disabled
[33892.081780] pci 0000:02:02.0: restoring config space at offset 0x1 (was 0x2900207, writing 0x2900203)
[33892.222808] pci 0000:02:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[57549.312661] pci 0000:02:02.0: PCI INT A disabled
[57549.869677] pci 0000:02:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
[57549.869694] pci 0000:02:02.0: restoring config space at offset 0x4 (was 0x1, writing 0x1001)
[57549.869699] pci 0000:02:02.0: restoring config space at offset 0x3 (was 0x0, writing 0x2000)
[57549.869706] pci 0000:02:02.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900203)
[57549.970708] pci 0000:02:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[66872.670499] pci 0000:02:02.0: PCI INT A disabled
[66873.045766] pci 0000:02:02.0: restoring config space at offset 0x1 (was 0x2900207, writing 0x2900203)
[66873.174809] pci 0000:02:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
The PCI slot 02:02.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:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:27d8 8086:d607 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller
Modem interrupt assignment and sharing:
22: 20631 0 IO-APIC-fasteoi HDA Intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.191036] pci 0000:00:1b.0: reg 10 64bit mmio: [0x901c0000-0x901c3fff]
[ 0.191081] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.191086] pci 0000:00:1b.0: PME# disabled
[ 13.155513] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 13.155544] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 13.286999] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input5
[33891.700562] HDA Intel 0000:00:1b.0: PCI INT A disabled
[33891.716091] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete after 117.648 msecs
[33892.081350] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100006, writing 0x100002)
[33892.216191] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[33892.216198] HDA Intel 0000:00:1b.0: setting latency timer to 64
[57549.432058] HDA Intel 0000:00:1b.0: PCI INT A disabled
[57549.448029] PM: suspend of drv:HDA Intel dev:0000:00:1b.0 complete after 119.891 msecs
[57549.869091] HDA Intel 0000:00:1b.0: restoring config space at offset 0xf (was 0x100, writing 0x109)
[57549.869106] HDA Intel 0000:00:1b.0: restoring config space at offset 0x4 (was 0x80000004, writing 0x901c0004)
[57549.869111] HDA Intel 0000:00:1b.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[57549.869116] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100002)
[57549.968184] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[57549.968191] HDA Intel 0000:00:1b.0: setting latency timer to 64
[66872.772092] HDA Intel 0000:00:1b.0: PCI INT A disabled
[66872.788034] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete after 117.332 msecs
[66873.045332] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100006, writing 0x100002)
[66873.168191] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[66873.168198] HDA Intel 0000:00:1b.0: setting latency timer to 64
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@xxxxxxxxxxxxx
if help is needed.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 02:02.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=17
HDA2=00:1b.0
IDENT=agrsm
For candidate modem in: 02:02.0
0780 Communication controller: Agere Systems Lucent V.92 Data/Fax Modem
Primary device ID: 11c1:0620
Support type needed or chipset: agrsm
Writing DOCs/Intel.txt
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:1b.0:
Modem chipset not detected on
NAME="Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller "
CLASS=0403
PCIDEV=8086:27d8
SUBSYS=8086:d607
IRQ=22
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller
Primary device ID: 8086:27d8
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
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.4
linuc_headers base folder /lib/modules/2.6.32-24-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.
Compressed files at: /usr/src/alsa-driver.tar.bz2
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:
-rwsr-xr-- 1 root dip 273312 2010-03-06 22:59 /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
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: lrwxrwxrwx 1 root root 12 2011-03-21 20:22 /dev/modem -> /dev/ttyAGS3
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
Within /etc/modprobe.conf files:
/etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
/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
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
