Re: Ubuntu x86 slamr trouble

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

 



Daniel,

I believe the main issue is that slamr.ko is not created because your
machine is 64 bit and it only works for 32 bit versions of linux

CPU=x86_64,  Ubuntu ,  ALSA_version=1.0.21
Linux version 2.6.32-34-generic (buildd@yellow) (gcc version 4.4.3
(Ubuntu 4.4.3-4ubuntu5) ) #77-Ubuntu SMP Tue Sep 13 19:39:17 UTC 2011

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.

This example cited above is for SLMODEMD + ALSA and not slamr.ko which
is 32 bit dependent.  I do not know if installing a 32 bit kernel + 32
bit userland will yield a working driver?  I would recommend
installing 32 bit linux if you do not mind the trouble or try to
virtualize it and see if you can communicate with the modem that way?

HTH,

Antonio


On Mon, Oct 10, 2011 at 5:26 PM, Daniel <speedbug78@xxxxxxxxxxxxxxxxx> wrote:
> uname -r: 2.6.32-34-generic
>
> lspci includes:
> 02:02.0 Modem: Smart Link Ltd. SmartPCI2800 V.92 PCI Soft DFT (rev 02)
>
> ModemData.txt
>
>  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.32-34-generic
>  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,  Ubuntu ,  ALSA_version=1.0.21
> Linux version 2.6.32-34-generic (buildd@yellow) (gcc version 4.4.3
> (Ubuntu 4.4.3-4ubuntu5) ) #77-Ubuntu SMP Tue Sep 13 19:39:17 UTC 2011
>  scanModem update of:  2011_08_08
>
> Distrib_ID=Ubuntu
> DistribCodeName=lucid
> AptRepositoryStem=http://us.archive.ubuntu.com/ubuntu/
>
>
> The dkms driver upgrade utilities are installed,
>
>
> 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:
>  snd_atiixp_modem snd_via82xx_modem snd_intel8x0m
>
> Attached USB devices are:
>  ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
>  ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver
> 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:
> 02:02.0 Modem: Smart Link Ltd. SmartPCI2800 V.92 PCI Soft DFT (rev 02)
> 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        2000:2800       163c:2800       Modem: Smart Link Ltd. SmartPCI2800 V.92
> PCI Soft DFT
>
>  Modem interrupt assignment and sharing:
>  22:      35874   IO-APIC-fasteoi   sata_sil
>  --- Bootup diagnostics for card in PCI slot 02:02.0 ----
> [    0.168745] pci 0000:02:02.0: reg 10 32bit mmio pref:
> [0xfc000000-0xfcffffff]
> [    0.168823] pci 0000:02:02.0: PME# supported from D3hot D3cold
> [    0.168829] pci 0000:02:02.0: PME# disabled
> [    0.315005] serial 0000:02:02.0: PCI INT A -> GSI 22 (level, low) ->
> IRQ 22
> [    0.315013] 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 02:02.0:
>        Modem chipset  detected on
> NAME="Modem: Smart Link Ltd. SmartPCI2800 V.92 PCI Soft DFT "
> CLASS=0703
> PCIDEV=2000:2800
> SUBSYS=163c:2800
> IRQ=22
> IDENT=slamr
>
>  For candidate modem in:  02:02.0
>   0703 Modem: Smart Link Ltd. SmartPCI2800 V.92 PCI Soft DFT
>      Primary device ID:  2000:2800
>  Support type needed or chipset:        slamr
>
>
>
> 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 2.6.32-34-generic 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.
>
>  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
>
>
>
>  Minimal compiling resources appear complete:
>   make utility - /usr/bin/make
>   Compiler version 4.4
>   linuc_headers base folder /lib/modules/2.6.32-34-generic/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.
>
>
>
>
> 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 321680 2010-03-06 21:37 /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)
>        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
> noauth
> 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
>
> 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/alsa-base.conf:options snd-atiixp-modem index=-2
> /etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
> /etc/modprobe.d/sl-modem.conf:install slamr /sbin/modprobe -qb
> ungrab-winmodem; /sbin/modprobe --ignore-install slamr; test
> -e /dev/slamr0 && (chmod 660 /dev/slamr0 && chgrp dialout /dev/slamr0)
> || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp
> dialout /dev/slamr0)
> /etc/modprobe.d/sl-modem.conf:install slusb /sbin/modprobe -qb
> ungrab-winmodem; /sbin/modprobe --ignore-install slusb; test
> -e /dev/slusb0 && (chmod 660 /dev/slusb0 && chgrp dialout /dev/slusb0)
> || (/bin/mknod -m 660 /dev/slusb0 c 243 0 2>/dev/null && chgrp
> dialout /dev/slusb0)
> /etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in order
> to blacklist unwanted modem drivers
> /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem
> /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem
>     Within any ancient /etc/devfs files:
>
>     Within ancient kernel 2.4.n /etc/module.conf files:
>
> --------- end modem support lines --------
>
>
> Trouble:
> I am trying to compile/install slamr, but having frustration.
>
> I downloaded slmodem-2.9.11-20110321 from:
> http://linmodems.technion.ac.il/packages/smartlink/
>
> sudo make clean:
> [sudo] password for melody:
> make -C modem clean &&  make -C drivers clean &&  echo "done."
> make[1]: Entering directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/modem'
> rm -f slmodemd modem_test modem_main.o modem_cmdline.o modem_test.o
> modem.o modem_datafile.o modem_at.o modem_timer.o modem_pack.o
> modem_ec.o modem_comp.o modem_param.o modem_debug.o homolog_data.o
> dp_sinus.o dp_dummy.o sysdep_common.o
> rm -f *~ *.orig *.rej
> make[1]: Leaving directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/modem'
> make[1]: Entering directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
> rm -f kernel-ver   *st7554.o amrmo_init.o sysdep_amr.o *.mod.* .*.cmd *~
> slusb.*
> rm -f -r .tmp_versions
> make[1]: Leaving directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
> done.
>
>
> sudo make:
> make -C modem all
> make[1]: Entering directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/modem'
> rebuild profile...
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o modem_main.o -c
> modem_main.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o modem_cmdline.o -c
> modem_cmdline.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o modem.o -c modem.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o modem_datafile.o -c
> modem_datafile.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o modem_at.o -c
> modem_at.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o modem_timer.o -c
> modem_timer.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o modem_pack.o -c
> modem_pack.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o modem_ec.o -c
> modem_ec.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o modem_comp.o -c
> modem_comp.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o modem_param.o -c
> modem_param.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o modem_debug.o -c
> modem_debug.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o homolog_data.o -c
> homolog_data.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o dp_sinus.o -c
> dp_sinus.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o dp_dummy.o -c
> dp_dummy.c
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o sysdep_common.o -c
> sysdep_common.c
> gcc -m32 -o slmodemd modem_main.o modem_cmdline.o modem.o
> modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o
> modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o
> dp_dummy.o dsplibs.o sysdep_common.o
> gcc -m32 -Wall -g -O -I. -DCONFIG_DEBUG_MODEM   -o modem_test.o -c
> modem_test.c
> modem_test.c: In function ‘modem_test_start’:
> modem_test.c:110: warning: ignoring return value of ‘write’, declared
> with attribute warn_unused_result
> gcc -m32 -o modem_test modem_test.o modem_cmdline.o modem.o
> modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o
> modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o
> dp_dummy.o dsplibs.o sysdep_common.o
> make[1]: Leaving directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/modem'
> make -C drivers KERNEL_DIR=/lib/modules/2.6.32-34-generic/build
> make[1]: Entering directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
> doing kernel-ver::
> cc -I/lib/modules/2.6.32-34-generic/build/include -o kernel-ver
> kernel-ver.c
> make all KERNEL_VER=2.6.32-34-generic
> make[2]: Entering directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
>        obj-m=
>        slamr-objs=amrmo_init.o sysdep_amr.o amrlibs.o
> make modules -C /lib/modules/2.6.32-34-generic/build
> SUBDIRS=/home/melody/Downloads/slmodem-2.9.11-20110321/drivers
> make[3]: Entering directory `/usr/src/linux-headers-2.6.32-34-generic'
>  Building modules, stage 2.
>  MODPOST 0 modules
> make[3]: Leaving directory `/usr/src/linux-headers-2.6.32-34-generic'
>        finished all:
> make[2]: Leaving directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
> make[1]: Leaving directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
>
>
> sudo make install:
> make -C modem all
> make[1]: Entering directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/modem'
> make[1]: Leaving directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/modem'
> make -C drivers KERNEL_DIR=/lib/modules/2.6.32-34-generic/build
> make[1]: Entering directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
> doing kernel-ver::
> cc -I/lib/modules/2.6.32-34-generic/build/include -o kernel-ver
> kernel-ver.c
> make all KERNEL_VER=2.6.32-34-generic
> make[2]: Entering directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
>        obj-m=
>        slamr-objs=amrmo_init.o sysdep_amr.o amrlibs.o
> make modules -C /lib/modules/2.6.32-34-generic/build
> SUBDIRS=/home/melody/Downloads/slmodem-2.9.11-20110321/drivers
> make[3]: Entering directory `/usr/src/linux-headers-2.6.32-34-generic'
>  Building modules, stage 2.
>  MODPOST 0 modules
> make[3]: Leaving directory `/usr/src/linux-headers-2.6.32-34-generic'
>        finished all:
> make[2]: Leaving directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
> make[1]: Leaving directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
> make install -C drivers KERNEL_DIR=/lib/modules/2.6.32-34-generic/build
> make[1]: Entering directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
> doing kernel-ver::
> cc -I/lib/modules/2.6.32-34-generic/build/include -o kernel-ver
> kernel-ver.c
> mkdir -p /dev
> mknod -m 600 /dev/slamr0 c 242 0 ;   mknod -m 600 /dev/slamr1 c 242 1 ;
> mknod -m 600 /dev/slamr2 c 242 2 ;   mknod -m 600 /dev/slamr3 c 242 3 ;
> echo -n
> make install KERNEL_VER=2.6.32-34-generic
> make[2]: Entering directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
> /sbin/depmod -a
> make[2]: Leaving directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
> make[1]: Leaving directory
> `/home/melody/Downloads/slmodem-2.9.11-20110321/drivers'
> install -D -m 755 modem/slmodemd /usr/sbin/slmodemd
> rm -f -rf /var/lib/slmodem
> install -d -D -m 755 /var/lib/slmodem
>
>
> sudo modprobe slamr:
> FATAL: Module slamr not found.
>
>
> Comparing my compile with the "compile_example.txt" in the documentation
> folder leads me to believe that the line "MODPOST 0 modules" means no
> modules are actually being built, but why?
>
>
>



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

  Powered by Linux