Hello,
Attached is ModemData.txt.
Basically, I'm trying to setup SM56 modem on 64b system.
Tried all packages at http://linmodems.technion.ac.il/packages/smartlink/
All but last ,slmodem-2.9.11-20100718.tar.gz , failed to compile.
The slmodem-2.9.11-20100718.tar.gz compile is good but does not
compile slamr module as it is not 64b compatible.
Can anyone please advice?
Thanks,
Yuly
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.34
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,
This , ALSA_version=
Linux version 2.6.34 (root@pluto) (gcc version 4.4.3 (Gentoo 4.4.3-r2 p1.2) ) #5 SMP Sat Sep 4 01:10:19 EDT 2010
scanModem update of: 2010_12_12
/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
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:
Attached USB devices are:
ID 8087:0020
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:
09:01.0 Modem: Motorola SM56 Data Fax Modem (rev 04)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
01:00.1 Audio device: ATI Technologies Inc RV710/730
High Definition Audio cards can host modem chips.
For candidate card in slot 09:01.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
09:01.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem
Modem interrupt assignment and sharing:
16: 26 0 0 0 IO-APIC-fasteoi ehci_hcd:usb1
--- Bootup diagnostics for card in PCI slot 09:01.0 ----
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 1043:8375 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio
Modem interrupt assignment and sharing:
23: 30 0 0 0 IO-APIC-fasteoi ehci_hcd:usb2
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
For candidate card in slot 01:00.1, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
01:00.1 1002:aa38 1043:aa38 Audio device: ATI Technologies Inc RV710/730
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 01:00.1 ----
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 09:01.0:
Modem chipset detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=16
IDENT=slamr
For candidate modem in: 09:01.0
0703 Modem: Motorola SM56 Data Fax Modem
Primary device ID: 1057:3052
Support type needed or chipset: slamr
1057:3052 has a Motorola chipset, poorly supported by Motorola itself
However Zello discovered that drivers written to support Smartlink modems do support the 1057:3052 chipset!!
It sufficed to add 1057:3052 to the list of modem cards recognized by the Smartlink slamr driver.
There is a ungrab-winmodem driver used in conjunction with slamr, which must have 1057:3052
similarly added. See messages from Zello:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html
and Alvaro Aguirre about the ungrab-winmodem fix:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html
For general guidance on ungrab-winmodem + slamr usage, read the DOCs/Smartlink.txt
There is a package sl-modem-source providing a source code the modem driver ,
If can be searched for at http://pacakge.ubuntu.com. After downloading install under Linux with:
$ sudo dpkg -i sl*.deb
If DKMS support installed, driver updates with kernel updates will be automatically done.
The modem is supported by the Smartlink
plus the slmodemd helper utility. Read the
DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance.
For 2.6.34 compiling drivers is necessary. As of October 2007 the current packages at
http://linmodems.technion.ac.il/packages/smartlink/ are the
ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz
Writing DOCs/Smartlink.txt
============ end Smartlink 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=1043:8375
IRQ=3
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:
Predictive diagnostics for card in bus 01:00.1:
Modem chipset not detected on
NAME="Audio device: ATI Technologies Inc RV710/730"
CLASS=0403
PCIDEV=1002:aa38
SUBSYS=1043:aa38
IRQ=5
For candidate modem in: 01:00.1
0403 Audio device: ATI Technologies Inc RV710/730
Primary device ID: 1002:aa38
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
linux-headers-2.6.34 resources needed for compiling are not manifestly ready!
If compiling is necessary packages must be installed, providing:
kernel-source-2.6.34
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
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:
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
