ModemData

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

 



Hi,

I just installed parsix and did scanModem, and I have attached the
modem data. I also compiled ungrab-winmodem and slmodemd according to
the version suggested by modemdata, but I don't know how to setup the
modem.

Waiting for your guidance,

Nitin.
 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.23-parsix-15 
 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.23-parsix-15 (root@memphis-mobile) (gcc version 4.2.3 20071123 (prerelease) (Debian 4.2.2-4)) #1 SMP PREEMPT Sun Dec 16 15:17:37 UTC 2007
 scanModem update of:  2008_11_06

 There are no blacklisted modem drivers in /etc/modprobe*  files 
Attached USB devices are:
 ID 13fe:1d00 Kingston Technology Company Inc. DataTraveler 2.0 1GB Flash Drive

USB modems not recognized

For candidate card in slot 05:03.0, firmware information and bootup diagnostics are:
 PCI slot	PCI ID		SubsystemID	Name
 ----------	---------	---------	--------------
 05:03.0	1057:3052	1057:3020	Modem: Motorola Unknown device 3052 

 Modem interrupt assignment and sharing: 
 --- Bootup diagnostics for card in PCI slot 05:03.0 ----
ACPI: PCI Interrupt 0000:05:03.0[A] -> GSI 16 (level, low) -> IRQ 18
0000:05:03.0: ttyS1 at I/O 0xc808 (irq = 18) is a 16450
0000:05:03.0: ttyS2 at I/O 0xc810 (irq = 18) is a 8250
0000:05:03.0: ttyS3 at I/O 0xc818 (irq = 18) is a 16450
Couldn't register serial port 0000:05:03.0: -28

For candidate card in slot 04:01.0, firmware information and bootup diagnostics are:
 PCI slot	PCI ID		SubsystemID	Name
 ----------	---------	---------	--------------
 04:01.0	1106:3288	1019:2171	Audio device: VIA Technologies, Inc. VIA High Definition Audio Controller 

 Modem interrupt assignment and sharing: 
 23:      17445   IO-APIC-fasteoi   HDA Intel
 --- Bootup diagnostics for card in PCI slot 04:01.0 ----
ACPI: PCI Interrupt 0000:04:01.0[A] -> GSI 17 (level, low) -> IRQ 23
PCI: Setting latency timer of device 0000:04:01.0 to 64


===== 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.14
The modem cards detected by "aplay -l"  are: None


The /proc/asound/pcm file reports:
-----------------------
00-01: ALC861VD Digital : ALC861VD Digital : playback 1
00-00: ALC861VD Analog : ALC861VD Analog : playback 1 : capture 2

about /proc/asound/cards:
------------------------
 0 [VT82xx         ]: HDA-Intel - HDA VIA VT82xx
                      HDA VIA VT82xx at 0xfbdfc000 irq 23

 PCI slot 04:01.0 has a High Definition Audio Card
 The drivers are in the kernel modules tree at:
 /lib/modules/2.6.23-parsix-15/kernel/sound/pci/hda/snd-hda-intel.ko
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===

Predictive  diagnostics for card in bus 05:03.0:
	Modem chipset  detected on
NAME="Modem: Motorola Unknown device 3052 "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=18
IDENT=slamr

 For candidate modem in:  05:03.0
   0703 Modem: Motorola Unknown device 3052 
      Primary device ID:  1057:3052
 Support type needed or chipset:	slamr
 

----------------end Softmodem section --------------

 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

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.23-parsix-15 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 04:01.0:
	Modem chipset not detected on
NAME="Audio device: VIA Technologies, Inc. VIA High Definition Audio Controller "
CLASS=0403
PCIDEV=1106:3288
SUBSYS=1019:2171
IRQ=23
HDA=1106:3288
SOFT=1106:3288.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 1106:3288.
 If another modem card is present, then most likely 1106:3288 does not host a modem.
 If another modem card has not been detected, then possibilities are:
	1) A Conexant modem chip is present on 1106:3288, 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:
	 wvdialconf  /etc/wvdial.conf

 For candidate modem in:  04:01.0
   0403 Audio device: VIA Technologies, Inc. VIA High Definition Audio Controller 
      Primary device ID:  1106:3288
    Subsystem PCI_id  1019:2171 
    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.2.tar.gz from:  
	http://linmodems.technion.ac.il/packages/smartlink/

----------------end Softmodem section --------------

 Completed candidate modem analyses.

 The base of the UDEV device file system is: /dev/.udev

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


 
 Minimal compiling resources appear complete:
   make utility - /usr/bin/make
   Compiler version 4.2
   linuc_headers base folder /lib/modules/2.6.23-parsix-15/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.


Compressed files at: /usr/src/linux-wlan-ng.tar.bz2

For Debian and some related distributions, a package kernel-kbuild-2.6-23 may be needed to support driver compiling.


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 260920 2007-04-14 04:29 /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
asyncmap 0
auth
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


 Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================

#
# UDEV rule for ltmodem
#  creates symlink /dev/modem to /dev/ttyLT?, and takes care of permissions

KERNEL=="ttyLTM[0-9]", MODE="0660", GROUP="dialout", SYMLINK="modem"

# start/stop the daemon when the USB modem is connected
KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
 Checking for modem support lines:
 --------------------------------------
     /device/modem symbolic link:   
slmodemd created symbolic link /dev/ttySL0:  
     Within /etc/udev/ files:
/etc/udev/ltmodem.rules:# UDEV rule for ltmodem
/etc/udev/ltmodem.rules:#  creates symlink /dev/modem to /dev/ttyLT?, and takes care of permissions
/etc/udev/ltmodem.rules:KERNEL=="ttyLTM[0-9]", MODE="0660", GROUP="dialout", SYMLINK="modem"
/etc/udev/rules.d/ltmodem.rules:# UDEV rule for ltmodem
/etc/udev/rules.d/ltmodem.rules:#  creates symlink /dev/modem to /dev/ttyLT?, and takes care of permissions
/etc/udev/rules.d/ltmodem.rules:KERNEL=="ttyLTM[0-9]", MODE="0660", GROUP="dialout", SYMLINK="modem"
/etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected
/etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
     Within /etc/modprobe.conf files:
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
/etc/modprobe.d/alsa-base-blacklist:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/alsa-base-blacklist:# blacklist snd-atiixp-modem
/etc/modprobe.d/alsa-base-blacklist:# blacklist snd-via82xx-modem
/etc/modprobe.d/sl-modem-daemon.modutils:install slamr modprobe --ignore-install ungrab-winmodem ;  modprobe --ignore-install slamr; test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0) 
     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