flags, CUBA, kernel 2.6.15-27-386

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

 



I haven't been able to make my modem works. I get errors during
installation of slamr-2.6.15-26-386.
The output I get is something like this:
_______________________
When asked about your country, Enter:
	USA

Installing the Debian packages supporting autoloading
(Reading database ... 86089 files and directories currently installed.)
Preparing to replace sl-modem-daemon 2.9.10+2.9.9d+e-pre2-5build1
(using sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5build1_i386.deb) ...
Shutting down SmartLink Modem driver normally ... no slmodemd daemon running.
Unloading modem driver from kernel ... slamr.
Unpacking replacement sl-modem-daemon ...
Setting up sl-modem-daemon (2.9.10+2.9.9d+e-pre2-5build1) ...


Copying over newer files
Making folder /lib/modules/2.6.15-27-386/extra
Copying drivers to /lib/modules/2.6.15-27-386/extra
Checking driver install
slamr.ko
slusb.ko
ungrab-winmodem.ko
Finished installs.
Informing the System

Starting function tests, loading drivers:
Running diagnostic:

[17179605.072000] slamr: module license 'Smart Link Ltd.' taints kernel.
[17179605.076000] slamr: SmartLink AMRMO modem.
[17179955.436000] slamr: SmartLink AMRMO modem.
[17180357.620000] slamr: SmartLink AMRMO modem.

ports should be created by:
slmodemd -c USA /dev/slamr0
Checking for success
Port creation with slmodemd failed.
Read the Slamr.txt record, other 1st_Read.txt CountryList.txt
output.txt Smartlink.txt Testing.txt wvdial.txt files and the sample
wvdial.conf.

cp: cannot stat `sl-modem-daemon.modutils': No such file or directory
error: mdm setup: cannot open dev `/dev/slamr0': No such device
error: cannot setup device `/dev/slamr0'
 Only plain text email is forwarded by the  DISCUSS@xxxxxxxxxxxxx List Server.
 Do use the following as the email Subject Line:
           SomeName, YourCountry  kernel 2.6.15-27-386 
 This will alert cogent experts, and  distinguish cases in the Archives.
 YourCountry will enable Country Code guidance.
 Occassionally responses are blocked by an Internet Provider mail filters.
 So in a day, also check the Archived responses at http://www.linmodems.org .
 Local Linux experts can be found through: http://www.linux.org/groups/index.html
--------------------------  System information ----------------------------
CPU=i686,  
Linux version 2.6.15-27-386 (buildd@terranova) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 PREEMPT Fri Dec 8 17:51:56 UTC 2006
 scanModem update of:  2007_Sept_07
The modem symbolic link is /dev/modem -> ttySL0

 There are no blacklisted modem drivers in /etc/modprobe*  files 
USB modem not detected by lsusb

 === Finished modem firmware and bootup diagnostics section. ===
 === Next deducing cogent software ===

 For candidate modem in PCI bus:  0000:02:0a.0
   Class 0703: 1057:3052 Modem: Motorola: Unknown device 3052
      Primary PCI_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 Smartlink.txt

The modem is supported by the Smartlink slamr driver
plus the slmodemd helper utility.  Read the
Smartlink.txt and Modem/YourSystem.txt for follow through guidance.


 Download slamr-2.6.15-27-386.tgz from http://linmodems.technion.il/packages/smartlink/
 under Linux, open a terminal and unpack with:
 $ tar zxvf slamr*.tgz
 Move into the unpacked folder
 $ cd slamr-2.6.15-27-386
 Look around
 $ ls
 Run the 
 $  sudo ./setup

 Afterwards do:
 $ slmodemd --help
 $ slmodemd --countrylist &> Clist.txt
 If not in the USA, look for your COUNTRY_NAME therein.
 Do and edit with:
 $ sudo gedit  /etc/default/sl-modem-daemon
 and therein replace the USA in the line:
 SLMODEMD_COUNTRY=USA
 This will provide for the correct Country setting in the automated:
    slmodemd -c COUNTRY /dev/slamr0

 Read the Smartlink.txt and YourSystem.txt 
Writing Smartlink.txt
============ end Smartlink section =====================

 Completed candidate modem analyses.

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

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


 
 Minimal compiling resources appear complete:
   make utility - /usr/bin/make
   Compiler version 4.0
   linuc_headers base folder /lib/modules/2.6.15-27-386/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 libc6-dev (and for Debian/Ubuntu,  linux-libc-dev). The also required headers of package libc6 are commonly installed by default. 



If a driver compilation files with message including some lack of some FileName.h (stdio.h for example. 
Some additional kernel-header files need installation to /usr/include.
For Debian/Ubuntu related distributions, run the following command to display the needed package list:
$ sudo apt-get -s install linux-kernel-devel
While some of the files may be on the install CD, others may have to be found through http://packages.ubuntu.com

For Ubuntu Feisty, additional packages required were:
 libc6-dev linux-libc-dev
available through http://packages.ubuntu.com/ , if not on the install CD.
Such packages may have different names for other Linux distributions.
Try installing just the libc6-dev, then test the compile again.


Checking pppd properties:
	-rwsr-xr-- 1 root dip 257720 2006-07-05 09:00 /usr/sbin/pppd

In case of an "error 17" "serial loopback" problem, see:
    http://phep2.technion.ac.il/linmodems/archive-sixth/msg02637.html

To enable dialout without Root permission do:
	$ su - root  (not for Ubuntu)
        sudo chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
	sudo 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

Read Modem/YourSystem.txt concerning other COMM channels: eth0
Which can interfere with Browser naviagation.

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

# 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:   lrwxrwxrwx 1 root root 6 2007-09-11 14:06 /dev/modem -> ttySL0
slmodemd created symbolic link /dev/ttySL0:  
     Within /etc/udev/ files:
/etc/udev/rules.d/60-symlinks.rules:# Create /dev/modem symlink
/etc/udev/rules.d/60-symlinks.rules:KERNEL=="ttyLTM[0-9]*",			SYMLINK+="modem"
/etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected
/etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
/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/blacklist-modem:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem:# 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 --------

   
                The files in this Modem/ folder have the following roles:

ModemData.txt - Diagnostics and accumulated information cogent to your modem and host system.
     This is the ONLY file which should be sent to the List  DISCUSS@xxxxxxxxxxxxx , 
     if further help is needed. Send your email and attachments as plain text as 
     other formats are rejected by the List Server, to avoid virus transmission.
     Always send the ENTIRE ModemData.txt,  as It includes subtle diagnostic ouputs needed 
     to best guide you. Please in the covering email mention your Country, to enable Country 
     specific advice.
     Always use the most recent update of scanModem accessed ONLY at
	   http://linmodems.technion.ac.il/packages/scanModem.gz 
     to produce ModemData.txt
     URLs to cogent advice are regularly updated, so your problem may be solved therein.
     Please Do NOT send  Do NOT send other files in this folder Modem/

A file(s) specific to your modem chipset will be written, such as:
  Smartlink.txt, Conexant.txt, Intel.txt , etc

YourModem.txt - Guidance about operating your particular System, for your benefit
     It should NOT be sent to Discuss@xxxxxxxxxxxxx

Rational.txt - Motivations of this scanModem package.  

DriverCompiling.txt -  Explains the roles of additional files which may have to be installed
   to support compiling of modem drivers, and the steps to take.   

SoftModem.txt - Information and instructions about "soft modems".
     For these modems, additional steps may be necessary for choice of supporting software.
     The primary PCI ID is that of the host audio or modem controller, which can support diverse Subsystems. It is the chipset of the Subsystem which determines the software needed.

ModemTesting.txt SHOULD be read, but after drivers have been installed.

InfoGeneral.txt has general information about the status of winmodem support under Linux,
    Do read it if ModemData.txt  reports that your current modem is not supported under Linux. 

Unsubscribe.txt - Howto terminate email tranmissions from the List.

If you are Linux newcomer, please do locate your local Linux group through:
    http://www.linux.org/groups/index.html  .  If you are not comfortable with English,
    a local Linux user can often be of substantial assistance in getting you on to the Internet.
 

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

  Powered by Linux