Dear friends, sorry for the delay to reply.
I did the tests described below and did not work.
/* ************************************************************** */
Driver:
agrsm-11c11040-2.1.80~20091225.tar.bz2
Install:
cd agrsm-11c11040-2.1.80~20091225/
make
make modules_install
/* ************************************************************** */
Librix ~ # modprobe agrserial
Librix ~ # lsmod |grep agr
agrserial 7825 0
agrmodem 1233373 1
snd_hda_codec 37602 4
agrmodem,snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel
snd 28813 13
agrmodem,snd_seq,snd_seq_device,snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
/* ************************************************************** */
dmesg:
[ 101.091528] * Hello Agere Driver **
[ 101.091580] usbcore: registered new interface driver agr12dec2006
[ 103.926484] Loading module Agere Modem Controller driver version
2.1.80 (2007-10-01)
[ 103.926490] Disabling lock debugging due to kernel taint
[ 103.978765] serial8250_register_ports: BaseAddress 0x0400 Irq 3
[ 103.978769] ttyAGS3 at I/O 0x400 (irq = 3) is a AgereModem
[ 103.978916] agrserial - ret_val 0, call: lt_modem_ops.init_modem
[ 103.978919] Loading module Agere Modem Interface driver version
2.1.80.0 (2007-10-01)
/* ************************************************************** */
Librix ~ # ls -l /dev/ttyAGS3
crw-rw---- 1 root uucp 62, 67 Out 20 09:47 /dev/ttyAGS3
Librix ~ # ls -l /dev/ttySAGR
lrwxrwxrwx 1 root root 12 Out 20 09:47 /dev/ttySAGR -> /dev/ttyAGS3
/* ************************************************************** */
Librix ~ # wvdialconf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
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.
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
/* ************************************************************** */
Some idea.
Thank you.
____________________________
Adriano Loren7
loren7@xxxxxxxxx
2010/10/6 Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>:
> Adiano,
> If you have not also installed the agrsm-tools package, please do so.
> If provides for loading of drivers and port creation, through a single:
> $ sudo modprobe agrserial
> which will also preload agrmodem and create
> /dev/ttySAGR --> /dev/ttyAGR3
> the latter being the real modem port
> Otherwise you must do:
> $ sudo modprobe agrmodem
> $ sudo modprobe agrserial
> and then specify the port as /dev/ttyAGR3
> Our preference is that modem testing be done through
> $ sudo wvdialconf
> which is a first test of modem responsiveness.
> If the modem is found
> $ sudo gedit /etc/wvdial.conf
> rmoving the symbols ; < > and entering your personal data.
> Then try a dialout with
> $ sudo wvdial
> MarvS
> scanModem maintainer
>
> On Wed, Oct 6, 2010 at 4:04 PM, Adriano Lorencetti <loren7@xxxxxxxxx> wrote:
>>
>> Antonio, thanks for the reply.
>>
>> I tested this driver that you told me, but the issue is the same as
>> the previous email:
>> >> When I try to connect through kppp software, the modem stop at step
>> >> "Initializing modem" ...
>>
>> I noticed the following message in /var/log/messages when I try to
>> connect through kppp software:
>> [ 1757.377343] ==> codecType = 0x31
>> [ 1757.377349] ERR: Control Interface failed
>>
>> I'm using kernel 2.6.33, is this driver supported ?
>>
>> I too found this question at a support's website:
>> http://comments.gmane.org/gmane.linux.linmodem/28755
>> It is the same audio and I think that is the same modem too.
>>
>> Regards.
>> ____________________________
>> Adriano Loren7
>> loren7@xxxxxxxxx
>>
>>
>>
>> 2010/10/5 Antonio Olivares <olivares14031@xxxxxxxxx>:
>> > Adriano,
>> >
>> > You need the following driver:
>> >
>> > 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/
>> >
>> >
>> > Download it and install it. Try to remove the other drivers because
>> > they will likely conflict with the correct one. Report back
>> > presently.
>> >
>> > Regards,
>> >
>> >
>> > Antonio
>> >
>> > On 10/5/10, Adriano Lorencetti <loren7@xxxxxxxxx> wrote:
>> >> Hello friends ...
>> >> I'm trying to install a modem driver, but I'm having some problems:
>> >>
>> >> ModemData.txt attached.
>> >>
>> >> NAME="Communication controller: Intel Corporation 5 Series/3400 Series
>> >> Chipset HECI Controller "
>> >> CLASS=0780
>> >> PCIDEV=8086:3b64
>> >> SUBSYS=1509:5020
>> >> IRQ=11
>> >> HDA2=00:1b.0
>> >> HDAchipVendorID=11c1
>> >> CHIP=0x11c11040
>> >> IDENT=agrsm
>> >> Driver=agrsm
>> >> package=agrsm-11c11040
>> >>
>> >> As ScanModem told me, I used a driver from:
>> >> http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
>> >>
>> >> I used the most recent driver:
>> >> agrsm06pci-2.1.80~20100106.tar.gz
>> >>
>> >> To install:
>> >> make clean
>> >> make
>> >> make modules_install
>> >>
>> >> The driver was installed perfectly, and the modules too.
>> >> The /dev/ttyAGS3 was created perfectly.
>> >>
>> >> The problem happens when I try to connect through kppp software. The
>> >> function "Configue, Modem, Ask to Modem" works but returns no
>> >> information.
>> >> And, when I try to connect, the modem stop at step "Initializing
>> >> modem" ... at this point the kppp stop ... no error appears ... and I
>> >> can "Cancel" and "Connect" again (no freeze), but always stop at the
>> >> point "Initializing modem".
>> >>
>> >> Any idea ?
>> >>
>> >> Tanks
>> >>
>> >> ____________________________
>> >> Adriano Loren7
>> >> loren7@xxxxxxxxx
>> >>
>> >
>
>
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
This is kernel 2.6.33-librix
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,
This , ALSA_version=1.0.21
Linux version 2.6.33-librix (root@grima) (gcc version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5) ) #1 SMP PREEMPT Fri Jul 2 18:30:47 Local time zone must be set--s
scanModem update of: 2010_05_29
/etc/lsb-release not found
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
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
snd_hda_intel
slamrTest=
Attached USB devices are:
ID 8087:0020
ID 0bda:0138 Realtek Semiconductor Corp.
ID 8087:0020
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:
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
High Definition Audio cards can host modem chips.
For candidate card in slot 00:16.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:16.0 8086:3b64 1509:5020 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 00:16.0 ----
[ 0.488618] pci 0000:00:16.0: reg 10: [mem 0xf0904000-0xf090400f 64bit]
[ 0.488676] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[ 0.488681] pci 0000:00:16.0: PME# disabled
The PCI slot 00:16.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:3b56 1509:5020 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio
Modem interrupt assignment and sharing:
30: 315 318 308 313 PCI-MSI-edge hda_intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.488851] pci 0000:00:1b.0: reg 10: [mem 0xf0900000-0xf0903fff 64bit]
[ 0.488908] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.488912] pci 0000:00:1b.0: PME# disabled
[ 13.157002] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 13.157063] HDA Intel 0000:00:1b.0: irq 30 for MSI/MSI-X
[ 13.157093] 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 00:16.0:
Modem chipset detected on
NAME="Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller "
CLASS=0780
PCIDEV=8086:3b64
SUBSYS=1509:5020
IRQ=11
HDA2=00:1b.0
HDAchipVendorID=11c1
CHIP=0x11c11040
IDENT=agrsm
Driver=agrsm
package=agrsm-11c11040
For candidate modem in: 00:16.0
0780 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller
Primary device ID: 8086:3b64
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 5 Series/3400 Series Chipset High Definition Audio "
CLASS=0403
PCIDEV=8086:3b56
SUBSYS=1509:5020
IRQ=30
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio
Primary device ID: 8086:3b56
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.3.4
and the compiler used in kernel assembly: 4.3.4
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.3
linuc_headers base folder /lib/modules/2.6.33-librix/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:
-r-s--x--x 1 root root 294116 Abr 6 12:09 /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
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 wlan0
Which can interfere with Browser naviagation.
Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================
KERNEL=="slamr", NAME="slamr0" GROUP="dialout"
# do not edit this file, it will be overwritten on update
ACTION!="add|change", GOTO="nm_modem_probe_end"
SUBSYSTEM!="tty", GOTO="nm_modem_probe_end"
DRIVERS=="serial_cs|nozomi", IMPORT{program}="nm-modem-probe --delay 1000 --timeout 5000 --export $tempnode", GOTO="nm_modem_probe_end"
# Only probe known mobile broadband drivers
DRIVERS=="option|sierra|hso|cdc_acm|qcserial|moto-modem", GOTO="probe"
GOTO="nm_modem_probe_end"
LABEL="probe"
# Don't probe new-style beagleboard cdc-acm ports
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0525", GOTO="nm_modem_probe_end"
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", DRIVERS=="?*", ENV{NM_MODEM_DRIVER}="$attr{driver}"
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}=="?*", ENV{NM_MODEM_USB_INTERFACE_NUMBER}="$attr{bInterfaceNumber}"
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="?*", IMPORT{program}="nm-modem-probe --vid 0x$attr{idVendor} --pid 0x$attr{idProduct} --usb-interface $env{NM_MODEM_USB_INTERFACE_NUMBER} --driver $env{NM_MODEM_DRIVER} --delay 5000 --timeout 8000 --export $tempnode", GOTO="nm_modem_probe_end"
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="?*", ATTRS{idProduct}=="?*", IMPORT{program}="nm-modem-probe --vid 0x$attr{idVendor} --pid 0x$attr{idProduct} --usb-interface $env{NM_MODEM_USB_INTERFACE_NUMBER} --driver $env{NM_MODEM_DRIVER} --delay 1000 --timeout 5000 --export $tempnode", GOTO="nm_modem_probe_end"
LABEL="nm_modem_probe_end"
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link:
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
/etc/udev/rules.d/77-nm-probe-modem-capabilities.rules:ACTION!="add|change", GOTO="nm_modem_probe_end"
/etc/udev/rules.d/77-nm-probe-modem-capabilities.rules:SUBSYSTEM!="tty", GOTO="nm_modem_probe_end"
/etc/udev/rules.d/77-nm-probe-modem-capabilities.rules:DRIVERS=="serial_cs|nozomi", IMPORT{program}="nm-modem-probe --delay 1000 --timeout 5000 --export $tempnode", GOTO="nm_modem_probe_end"
/etc/udev/rules.d/77-nm-probe-modem-capabilities.rules:DRIVERS=="option|sierra|hso|cdc_acm|qcserial|moto-modem", GOTO="probe"
/etc/udev/rules.d/77-nm-probe-modem-capabilities.rules:GOTO="nm_modem_probe_end"
/etc/udev/rules.d/77-nm-probe-modem-capabilities.rules:SUBSYSTEMS=="usb", ATTRS{idVendor}=="0525", GOTO="nm_modem_probe_end"
/etc/udev/rules.d/77-nm-probe-modem-capabilities.rules:SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="?*", IMPORT{program}="nm-modem-probe --vid 0x$attr{idVendor} --pid 0x$attr{idProduct} --usb-interface $env{NM_MODEM_USB_INTERFACE_NUMBER} --driver $env{NM_MODEM_DRIVER} --delay 5000 --timeout 8000 --export $tempnode", GOTO="nm_modem_probe_end"
/etc/udev/rules.d/77-nm-probe-modem-capabilities.rules:SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="?*", ATTRS{idProduct}=="?*", IMPORT{program}="nm-modem-probe --vid 0x$attr{idVendor} --pid 0x$attr{idProduct} --usb-interface $env{NM_MODEM_USB_INTERFACE_NUMBER} --driver $env{NM_MODEM_DRIVER} --delay 1000 --timeout 5000 --export $tempnode", GOTO="nm_modem_probe_end"
/etc/udev/rules.d/77-nm-probe-modem-capabilities.rules:LABEL="nm_modem_probe_end"
Within /etc/modprobe.conf files:
/etc/modprobe.d/slmodem.conf:# slmodem 2.9.x kernel modules configuration file
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
