Suse 12.1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I have a USB Modem and a PCI Modem-Card. My system is a Suse 12.1 with
the following characterisrica:

Linux twisrv 3.1.9-1.4-default #1 SMP Fri Jan 27 08:55:10 UTC 2012 (efb5ff4) i686 i686 i386 GNU/Linux

The characteristica of the Modems can be seen in the attached file
(any more necessary?). The USB-Modem is working like a charme. But the
PCI-Modem not. The slmodem and ungrab-winmodem sources I found are
only for kernel 2.x. Are there any versions for 3.1 Kernels?

Thanks in advance,
Thomas
 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 Welcome to openSUSE 12.1 "Asparagus" - Kernel  kernel 3.1.9-1.4-default 
 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,  Welcome ,  ALSA_version=1.0.24
Linux version 3.1.9-1.4-default (geeko@buildhost) (gcc version 4.6.2 (SUSE Linux) ) #1 SMP Fri Jan 27 08:55:10 UTC 2012 (efb5ff4)
 scanModem update of:  2011_08_08

/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:
      cdc_acm            

Attached USB devices are:
 ID 03f0:1004 Hewlett-Packard DeskJet 970c/970cse
 ID 0baf:0303 U.S. Robotics 
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

Candidate PCI devices with modem chips are:
02:02.0 Modem: Motorola SM56 Data Fax Modem (rev 04)
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	1057:3052	1057:3020	Modem: Motorola SM56 Data Fax Modem 

 Modem interrupt assignment and sharing: 
 --- Bootup diagnostics for card in PCI slot 02:02.0 ----
[    0.119684] pci 0000:02:02.0: [1057:3052] type 0 class 0x000703
[    0.119708] pci 0000:02:02.0: reg 10: [mem 0xec004000-0xec004fff]
[    0.119721] pci 0000:02:02.0: reg 14: [io  0xc400-0xc4ff]
[    0.119795] pci 0000:02:02.0: PME# supported from D0 D3hot D3cold
[    0.119801] pci 0000:02:02.0: PME# disabled
[    1.208834] serial 0000:02:02.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[    1.208881] serial 0000:02:02.0: PCI INT A disabled

 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.
 

=== Finished firmware and bootup diagnostics, next deducing cogent software. ===

Predictive  diagnostics for card in bus 001:
	Modem chipset  detected on
SLOT="Bus 001 Device 003:"
NAME="U.S. Robotics "
bus=001
USBmodemID=0baf:0303
IDENT=cdc_acm
Driver=cdc_acm

For a detailed USB cellphone usage report, see http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03240.html 
 For candidate modem in:  001
    U.S. Robotics 
      Primary device ID:  0baf:0303
 Support type needed or chipset:	cdc_acm
 



Predictive  diagnostics for card in bus 02:02.0:
	Modem chipset  detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=18
IDENT=slamr

 For candidate modem in:  02:02.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
It is preferable to install the dkms package first.
With 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 3.1.9-1.4-default 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 =====================

 Completed candidate modem analyses.

 A UDEV device file system is not active.

 Versions adequately match for the compiler installed: 4.6.2
             and the compiler used in kernel assembly: 4.6

 linux-headers-3.1.9-1.4-default resources needed for compiling are not manifestly ready!

 If compiling is necessary packages must be installed, providing:
	 kernel-source-3.1.9-1.4-default


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:
	-rwxr-xr-x 1 root dialout 334808 Oct 29 19:43 /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
noipdefault
noauth
crtscts
lock
modem
asyncmap 0
nodetach
lcp-echo-interval 30
lcp-echo-failure 4
lcp-max-configure 60
lcp-restart 2
idle 600
noipx
file /etc/ppp/filters

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:
/etc/modprobe.d/00-system.conf:# Linux ACP modem (Mwave)
     Within any ancient /etc/devfs files:

     Within ancient kernel 2.4.n /etc/module.conf files:

--------- end modem support lines --------


[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux