Marvin,
System freeze was solved by copying the init code generated by
agrsm-test to efax-gtk:
Init code=Z Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Reset code = Z
Now efax can dial and send documents to other fax machine over telephone
line.
Besides, I don't know why wvdial got an "segmentation fault" error when
it tried to adopt the connection to network interface using pppd. But I
only intend to fax documents, so 56k internet connection is not a
concern to me.
Thank you for your help!
Regards,
Antony
On Thursday, July 15, 2010 08:53 AM, Marvin Stodolsky wrote:
Antony,
A nother efax user reported that is the AT&F initi code which causes a
problem when using efax.
MarvS
On Wed, Jul 14, 2010 at 12:02 PM, Antonio Olivares
<olivares14031@xxxxxxxxx> wrote:
Antony,
On 7/14/10, Antony Chan<antony_css@xxxxxxxxxxxx> wrote:
Antonio,
The script "agrsm-test" works fine, but these deb's causes system freeze
when testing with wvdial and efax. I can't find any error (if any) from
the output because the screen was frozen, and I can't save the console
output because the keyboard was locked. I have to restart the computer
by pressing the power-switch.
Do I have to compile the modules from source?
No, if you used dkms, the drivers would be automagically created after
installing newer kernels.
By the way, I am not sure
if it can be compiled, because the symbol of ALSA modules may have been
changed a lot in version=1.0.21 (I am now using Ubuntu Lucid Lynx 10.04)
This is why using dkms is suggested. However, if the system freezes,
you may have gotten kernel panics and thus the problem could be with
the driver.
Don't know how to advice.
Regards,
Antonio
Regards,
Antony
On Friday, July 02, 2010 09:29 PM, Antonio Olivares wrote:
Antony,
scanModem reports that your modem is supported through
agrsm-11c11040-20091225.deb package and agrsm-tools
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
If you cannot find newer dkms package, use this one here:
http://linmodems.technion.ac.il/packages/ltmodem/11c11040/dkms-agrsm_2.1.80-7_i386.deb
$ sudo dpkg -i agrsm_2.180-7_i386.deb
Download
agrsm-11c11040-2.1.80~20091225.deb& agrsm-tools_0.0.1_all.deb
from
http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
install with
$ sudo dpkg -i agsrm*
Predictive diagnostics for card in bus 00:1b.0:
Modem chipset detected on
NAME="Audio device: Intel Corporation 82801I "
CLASS=0403
PCIDEV=8086:293e
SUBSYS=103c:3072
IRQ=17
HDA2=00:1b.0
SOFT=8086:293e.HDA
HDAchipVendorID=11c1
CHIP=0x11c11040
IDENT=agrsm
Driver=agrsm
package=agrsm-11c11040
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801I
Primary device ID: 8086:293e
Subsystem PCI_id 103c:3072
Softmodem codec or chipset from diagnostics: 0x11c11040
from Archives:
The HDA card softmodem chip is 0x11c11040
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 -------------------
If you load the driver correctly, but the modem responds, it might be
because:
For candidate card in slot 00:1b.0, firmware information and bootup
diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:293e 103c:3072 Audio device: Intel Corporation 82801I
Modem interrupt assignment and sharing:
17: 1813 271 IO-APIC-fasteoi uhci_hcd:usb4, HDA Intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.292845] pci 0000:00:1b.0: reg 10 64bit mmio:
[0xd8900000-0xd8903fff]
[ 0.292912] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.292918] pci 0000:00:1b.0: PME# disabled
[ 11.788787] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
[ 11.788873] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
[ 11.788952] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 17 (level,
low) -> IRQ 17
[ 11.789074] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 12.314656] input: HDA Digital PCBeep as
/devices/pci0000:00/0000:00:1b.0/input/input9
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.
Regards,
Antonio
On 7/2/10, Antony Chan<antony_css@xxxxxxxxxxxx> wrote:
