Re: Brankovic Milan

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

 



Milan,

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.

Regards,

Antonio

On 9/24/07, Milan <tenet@xxxxxxxxxx> wrote:
>
>
>  Only plain text email is forwarded by the  DISCUSS@xxxxxxxxxxxxx List Server.
>  Do use the following as the email Subject Line:
>           SomeName, YourCountry Fedora release 7 (Moonshine)
> Kernel  kernel 2.6.20-2925.9.fc7xen
>  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,  Fedora release 7 (Moonshine)
> Kernel
> Linux version 2.6.20-2925.9.fc7xen (kojibuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue May 22 08:53:03 EDT 2007
>  scanModem update of:  2007_Sept_07
>
>
>  There are no blacklisted modem drivers in /etc/modprobe*  files
> USB modem not detected by lsusb
>
>
> Several modems are supported by drivers with ALSA, the Advanced Linux Sound Architecture software.
> Copying ALSA diagnostics to Modem/ALSATENET.tgz
> ALSAversion = 1.0.14rc2
>
> Modem or candidate host audio card have firmware information and diagnostics:
>
>  PCI slot       PCI ID          SubsystemID     Name
>  ----------     ---------       ---------       --------------
>  00:12.0        1057:3052       1057:3020       Modem: Motorola SM56 Data Fax Modem
>
>  Modem interrupt assignment and sharing:
>  15:      55606  Phys-irq-level     libata
>  --- Bootup diagnostics for card in PCI slot 00:12.0 ----
>
>  === Finished modem firmware and bootup diagnostics section. ===
>  === Next deducing cogent software ===
>
>  For candidate modem in PCI bus:  00:12.0
>   Class 0703: 1057:3052 Modem: Motorola SM56 Data Fax Modem
>      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.
>
> 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.1.2
>             and the compiler used in kernel assembly: 4.1.2
>
>  linux-headers-2.6.20-2925.9.fc7xen resources needed for compiling are not manifestly ready!
>
>  If compiling is necessary packages must be installed, providing:
>         kernel-source-2.6.20-2925.9.fc7xen
>
>
> 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:
>        -r-xr-xr-x 1 root root 312332 Dec  1  2006 /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)
>         chmod a+x /usr/sbin/pppd
> or under Ubuntu related Linuxes
>         chmod a+x /usr/sbin/pppd
>
> Checking settings of:   /etc/ppp/options
> lock
>
> 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: virbr0
> Which can interfere with Browser naviagation.
>
>  Don't worry about the following, it is for the 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:
> /etc/udev/rules.d/50-udev.rules:KERNEL=="modems/mwave*",        NAME="%k", GROUP="uucp", MODE="0660"
>     Within /etc/modprobe.conf files:
>
>     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