Re: Problem with slmodemd

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

 



Victor

Your System is a bit complex,
From
>  PCI slot       PCI ID          SubsystemID     Name
>  ----------     ---------       ---------       --------------
>  00:1b.0        8086:284b       17aa:384e       Audio device: Intel Corporation
and archival information, there should be a Motorola  modem chip 10573055 on
the SubSystem  17aa:384e.
If principle it should  be activated as Antonio relates by
$ sudo slmodemd  -c GERMANY --alsa hw:0,1 (or hw:0,6)
However the ALSA diagnostics are incomplete, indicating there is some
problem with ALSA support on your System.

Quite separately:
 [ 3783.201432] usbcore: registered new interface driver ST7554 USB Modem
ST7554  USB modems typically have a Smartlink chipset.
However it is not evident among
Attached USB devices are:
 ID 0a5c:2101 Broadcom Corp.
 ID 08ff:2580 AuthenTec, Inc.

This would be explained in the USB modem was not attached, when you
ran scanModem.

Note that at http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/
there is a slamr-2.6.24-19-generic.tar.gz  driver installer package
including the slusb.ko driver, needed to .gz
work with a USB modem.

Under Linux, unpack with:
$ tar zxf slamr*.tar
$ cd slamr-2.6.24-19-generic
Browse the files and run the
$ sudo ../setup
There will be warning messages, because the messaging was wrote for
the slamr.ko utilization.  However the proper installation should
still be done.

Just reboot and while watching the kernel messages,
attach the USB modem.  If the modem is compatible, there should be an
unloading of driver lsusb.ko and creation of a port  /dev/slusb0.
Check with
$ lsmod | grep slusb
$ ls -l  /dev/slusb*

If successful
$ sudo slmodemd -c GERMANY  /dev/slusb0
should announce port creation
   /dev/ttySL0  --> /dev/pts/N

Try it that far and report back.

MarvS
scanModem maintainer

On Thu, Jul 31, 2008 at 9:44 AM, Victor Hahn <victor@xxxxxxxxxxxxx> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> I'm having some trouble trying to install my winmodem. I learned from
> scanModem that I probably need slmodemd (I attached ModemData.txt below). So
> I installed it an loaded the driver with modprobe slusb. This seems to have
> succeded as it says in dmesg:
>
> [ 3783.200100] Symbol usb_register_driver is being used by a non-GPL module,
> which will not be allowed in the future
> [ 3783.200112] Please see the file Documentation/feature-removal-schedule.txt
> in the kernel source tree for more details.
> [ 3783.200375] Symbol usb_deregister is being used by a non-GPL module, which
> will not be allowed in the future
> [ 3783.200378] Please see the file Documentation/feature-removal-schedule.txt
> in the kernel source tree for more details.
> [ 3783.201378] ST7554 USB Modem.
> [ 3783.201432] usbcore: registered new interface driver ST7554 USB Modem
>
> Anyway, starting slmodemd doesn't work:
>
> # slmodemd --country=GERMANY /dev/slusb0
> error: mdm setup: cannot open dev `/dev/slusb0': No such device
> error: cannot setup device `/dev/slusb0'
>
> Any hints what to do about this?
>
> Best regards,
> Victor
>
>
> ModemData.txt following:
>
>
>  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.24-19-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=i686,
> Linux version 2.6.24-19-generic (buildd@terranova) (gcc version 4.2.3 (Ubuntu
> 4.2.3-2ubuntu7)) #1 SMP Fri Jul 11 23:41:49 UTC 2008
>  scanModem update of:  2008_07_30
>
>  There are no blacklisted modem drivers in /etc/modprobe*  files
> Attached USB devices are:
>  ID 0a5c:2101 Broadcom Corp.
>  ID 08ff:2580 AuthenTec, Inc.
>
> USB modems not recognized
>
> For candidate card in slot 00:1b.0, firmware information and bootup
> diagnostics are:
>  PCI slot       PCI ID          SubsystemID     Name
>  ----------     ---------       ---------       --------------
>  00:1b.0        8086:284b       17aa:384e       Audio device: Intel Corporation 82801H
>
>  Modem interrupt assignment and sharing:
>  22:       6429       6462   IO-APIC-fasteoi   ohci1394, HDA Intel
>  --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
> [   57.633947] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) ->
> IRQ 22
> [   57.633983] PCI: Setting latency timer of device 0000:00:1b.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.16
> The modem cards detected by "aplay -l"  are: None
>
>
> The /proc/asound/pcm file reports:
> - -----------------------
> 00-00: ALC861VD Analog : ALC861VD Analog : playback 1 : capture 1
>
> about /proc/asound/cards:
> - ------------------------
>  0 [Intel          ]: HDA-Intel - HDA Intel
>                      HDA Intel at 0xfc300000 irq 22
>
>  PCI slot 00:1b.0 has a High Definition Audio Card
>  The drivers are in the kernel modules tree at:
>  /lib/modules/2.6.24-19-generic/ubuntu/sound/alsa-driver/pci/hda/snd-hda-intel.ko
> === Finished firmware and bootup diagnostics, next deducing cogent software.
> ===
>
> Predictive diagnostics for card in bus 00:1b.0:
>        Modem chipset  detected on
> NAME="Audio device: Intel Corporation 82801H "
> CLASS=0403
> PCIDEV=8086:284b
> SUBSYS=17aa:384e
> IRQ=22
> HDA=8086:284b
> SOFT=8086:284b.HDA
> ArchivedChip=0x10573055
> IDENT=slmodemd
>
>  For candidate modem in:  00:1b.0
>   0403 Audio device: Intel Corporation 82801H
>      Primary device ID:  8086:284b
>    Subsystem PCI_id  17aa:384e
>    Softmodem codec or chipset from diagnostics:
>                               from    Archives: 0x10573055
>
>
>
> Support type needed or chipset: slmodemd
>
>  An ALSA (Advanced Linux Sound Architecture) modem driver:
>  provides Low Level support enabling contact with the modem hardware.
>  For all BUT Conexant chip soft modems (using hsfmodem software)
>  complementary High Level support is through a Smartlink utility:  slmodemd
>
>  Download from http://linmodems.technion.ac.il/packages/smartlink/
>  the package SLMODEMD.gcc4.2.tar.gz having a compiled slmodemd. Unpack under
> Linux with:
>        $ tar zxf SLMODEMD.gcc4.2.tar.gz
>  and read instructions therein. But briefly, the modem is setup with command:
>        sudo slmodemd -c YOUR_COUNTRY --alsa hw:0,1_or_hw:0,6
>  reporting dynamic creation of ports:
>        /dev/ttySL0 --> /dev/pts/N   , with N some number
>  Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through
> guidance.
>
> - ----------------end Softmodem section --------------
>
> Writing DOCs/Intel.txt
> 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.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.24-19-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 n. 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 269256 2007-10-04 21:57 /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
>
> Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth1 wlan0
> wmaster0
> 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: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
>     Within any ancient /etc/devfs files:
>
>     Within ancient kernel 2.4.n /etc/module.conf files:
>
> - --------- end modem support lines --------
>
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFIkcHTHcN9/iUDLnoRAg/AAJ9rfPiKbLldx4ylaNaDbjQsQJDFGQCfRppZ
> wnFCiG4oCKs+Ulh4PZ6iP8s=
> =5Hnc
> -----END PGP SIGNATURE-----
>

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

  Powered by Linux