David,
0780 Communication controller: Agere Systems V.92 56K WinModem
Primary device ID: 11c1:048c
is indeed among the most difficult modem hardware to service.
Success had mostly been with the older agrsm-20080203.tar.gz at
http://linmodems.technion.ac.il/packages/ltmodem/sv92/
If you haven't tested those, uninstall/delete the current drivers and
try those. Do leave installed the agrsm-tools, as they are effective
with all the driver versions.
MarvS
On Thu, Jul 16, 2009 at 1:42 AM, David Hazel<dhazel@xxxxxxxxx> wrote:
> I have a Lucent-Agere winmodem that I would like to get working under Jaunty.
>
> The contents of my ModemData file are appended further below.
>
> Here is what I've tried so far:
> * compiled the agrserial and agrmodem drivers
> * tried both 2.6.27-9 and 2.6.27-11 kernels
> * have the agrsm tools installed
> * have also tried the pre-built binary package for the 2.6.27-9 kernel
> * have tried adding (separately of course) each of pci=noacpi,
> pci=routeirq, and pci=pollirq to grub menu.lst
>
> Here is the consistent output I am getting from the agrsm-test program:
> """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
> Found drivers for boot kernel 2.6.27-11-generic at:
> /lib/modules/2.6.27-11-generic/extra/agrserial.ko
> /lib/modules/2.6.27-11-generic/extra/agrmodem.ko
>
>
> Loading drivers:
>
> Drivers loaded:
> agrserial 18976 0
> agrmodem 1193380 1 agrserial
>
> and symbolic link created:
> lrwxrwxrwx 1 root root 12 2009-07-12 22:14 /dev/ttySAGR -> /dev/ttyAGS3
>
> Checking for utility wvdialconf
>
> Found /usr/bin/wvdialconf, preparing to run:
> wvdialconf /etc/wvdial.conf
>
> Modem Port Scan<*1>: S0 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.
>
> A reboot may be necessary before modem detection through:
> sudo modprobe agrserial
> Which will load agrmodem, agrserial and create the symbolic link needed for:
> sudo wvdialconf
> """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
>
>
> Any ideas on what to do next?
>
> Last but not least, here is the contents of my ModemData file:
> """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
> 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.27-11-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,
> Linux version 2.6.27-11-generic (buildd@vernadsky) (gcc version 4.3.2
> (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Wed Apr 1 20:57:48 UTC 2009
> scanModem update of: 2009_07_02
>
> 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 05dc:a731 Lexar Media, Inc.
> ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
> 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@xxxxxxxxxxxxx
>
> For candidate card in slot 02:04.0, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 02:04.0 11c1:048c 11c1:044c Communication controller: Agere Systems
> V.92 56K WinModem
>
> Modem interrupt assignment and sharing:
> 16: 131933 0 IO-APIC-fasteoi uhci_hcd:usb4, HDA
> Intel, i915@pci:0000:00:02.0
> --- Bootup diagnostics for card in PCI slot 02:04.0 ----
> [ 0.512571] PCI: 0000:02:04.0 reg 10 32bit mmio: [cffff000, cffff0ff]
> [ 0.512580] PCI: 0000:02:04.0 reg 14 io port: [e480, e487]
> [ 0.512588] PCI: 0000:02:04.0 reg 18 io port: [e000, e0ff]
> [ 0.512629] pci 0000:02:04.0: supports D2
> [ 0.512631] pci 0000:02:04.0: PME# supported from D2 D3hot D3cold
> [ 0.512637] pci 0000:02:04.0: PME# disabled
> [ 86.523126] agrsm 0000:02:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> [ 94.579406] agrsm 0000:02:04.0: PCI INT A disabled
> [ 94.595000] agrsm 0000:02:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
>
> The PCI slot 02:04.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:2668 103c:2a09 Audio device: Intel Corporation
> 82801FB/FBM/FR/FW/FRW
>
> Modem interrupt assignment and sharing:
> 16: 131972 0 IO-APIC-fasteoi uhci_hcd:usb4, HDA
> Intel, i915@pci:0000:00:02.0
> --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
> [ 0.508643] PCI: 0000:00:1b.0 reg 10 64bit mmio: [cfdb8000, cfdbbfff]
> [ 0.508643] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
> [ 0.508643] pci 0000:00:1b.0: PME# disabled
> [ 8.670782] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level,
> low) -> IRQ 16
> [ 8.670814] 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.
>
>
> ===== 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.
> The ALSA verion is 1.0.17
> The modem cards detected by "aplay -l" are: None
>
> The /proc/asound/pcm file reports:
> -----------------------
> 00-04: ALC880 Analog : ALC880 Analog : capture 2
> 00-00: ALC880 Analog : ALC880 Analog : playback 1 : capture 1
> about /proc/asound/cards:
> ------------------------
> 0 [Intel ]: HDA-Intel - HDA Intel
> HDA Intel at 0xcfdb8000 irq 16
>
> PCI slot 00:1b.0 has a High Definition Audio Card
> The drivers are in the kernel modules tree at:
> /lib/modules/2.6.27-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko
> /lib/modules/2.6.28-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko
> UNEXPECTED HDA diagnostic outcome.
> === Finished firmware and bootup diagnostics, next deducing cogent software. ===
>
> Predictive diagnostics for card in bus 02:04.0:
> Modem chipset detected on
> NAME="Communication controller: Agere Systems V.92 56K WinModem "
> CLASS=0780
> PCIDEV=11c1:048c
> SUBSYS=11c1:044c
> IRQ=16
> IDENT=agrsm
>
> For candidate modem in: 02:04.0
> 0780 Communication controller: Agere Systems V.92 56K WinModem
> Primary device ID: 11c1:048c
> Support type needed or chipset: agrsm
>
>
> Writing DOCs/Intel.txt
>
> The AgereSystems/LSI agrsm code supports compiling of a agrmodem +
> agrsm driver pair.
> One resource site is http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
> Thereat get the agrsm_howto.txt and one of the agrsm-tools packages.
> The initial agrsm_howto.txt compiling steps are only cogent to modems
> with PCI IDs:
> 11c1:0620, 11c1:048c and 11c1:048f chips.
> They use the agrsm-20090418.tar.gz package.
>
> The agrsm-tools sets a useful symbolic link and a agrsm-test utlity
> For AgereSystems/LSI with Vendor 11c1 chips hosted on High Definition
> Audio cards, there may be support
> through the agrsm resources (providing an agrmodem + agrserial driver
> pair) as an alternative to usage
> of the snd-hda-intel driver + slmodemd helper. For the 11c11040 modem
> chip, ONLY the agrsm code is competent.
> Your Linux distro's dkms package should be first installed, as it
> directs the installation of modem
> specific dkms-agrsm resources, and also directs auto-installation of
> new drivers upon kernel upgrades.
>
> Currently, the dkms-agrsm code is NOT competent for 2.26.28 and later kernels.
> A short term fix is to install linux-image + linux-headers packages
> for earlier kernels.
> For example, for Ubuntu Jaunty with 2.6.28 kernels, linux-image +
> linux-headers packages
> for earlier 2.26.27 series Intrepid kernels can be installed. Search
> for them at:
> http://packages.ubuntu.com
>
> The primary dkms-agrsm resource site is
> http://linux.zsolttech.com/linmodem/agrsm/
> whereat a few different packaging types are available. Debian type
> installers (supporting Ubuntu too)
> are copied to http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
> . Thereat the current package
> is the dkms-agrsm_2.1.80-6_i386.deb is for Agere/LSI chipsets hosted
> on High Definition Audio cards.
> Read the Modem/DOCs/Agrsm.txt for details.
> -------------- end Agere Systems section -------------------
>
> Predictive diagnostics for card in bus 00:1b.0:
> Modem chipset not detected on
> NAME="Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW "
> CLASS=0403
> PCIDEV=8086:2668
> SUBSYS=103c:2a09
> IRQ=16
> HDA=8086:2668
> SOFT=8086:2668.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:2668.
> If another modem card is present, then most likely 8086:2668 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:2668, 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 82801FB/FBM/FR/FW/FRW
> Primary device ID: 8086:2668
> Subsystem PCI_id 103c:2a09
> 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/
>
> Writing DOCs/Smartlink.txt
> ============ end Smartlink section =====================
>
> Completed candidate modem analyses.
>
> 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.3
>
> The patch utility is needed and is needed for compiling ALSA drivers,
> and possibly others.
>
> Minimal compiling resources appear complete:
> make utility - /usr/bin/make
> Compiler version 4.3
> linuc_headers base folder /lib/modules/2.6.27-11-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:
> -rwsr-xr-- 1 root dip 277352 2009-02-20 09:25 /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
> 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/alsa-base.conf:options snd-atiixp-modem index=-2
> /etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
> /etc/modprobe.d/agrsm.conf:## setup agrsm modem with only: "sudo
> modprobe agrserial"
> /etc/modprobe.d/agrsm.conf:install agrserial /sbin/modprobe
> --ignore-install agrmodem ; /sbin/modprobe --ignore-install agrserial
> && \
> /etc/modprobe.d/agrsm.conf:remove agrserial /sbin/modprobe -r
> --ignore-remove agrserial ; /sbin/modprobe -r --ignore-remove agrmodem
> && { if test -L /dev/ttySAGR; then rm /dev/ttySAGR; fi } ; true
> /etc/modprobe.d/agrsm.conf:# to automate bootup "sudo modprobe agrmodem"
> /etc/modprobe.d/agrsm.conf:## to setup agrsm modem with only: "sudo
> modprobe agrmodem"
> /etc/modprobe.d/agrsm.conf:# install agrmodem /sbin/modprobe
> --ignore-install agrmodem && \
> /etc/modprobe.d/agrsm.conf:## of effects of agrmodem and agrserial loading
> /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 --------
>
