Sorry for the delay fellows... anyways, I did "sudo wvdialconf" but got that answer... WvModem<*1>: Cannot set information for serial port. ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. WvModem<*1>: Cannot set information for serial port. ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Modem Port Scan<*1>: S2 S3 any ideas? I tried this time with Linux Mint 9 kernel 2.6.32.22-generic Alain > > This is our first encounter with: > Communication controller: Motorola Wildcard X100P" > CLASS=0780 > PCIDEV=1057:5608 > > But doing a Google search: > ------------------------- > Re: X100P with Motorola Chipset - Config Problems. > Wed, 01/03/2007 - 10:00am > (1). Wildcard X100P, Wildcard X101P, Generic X100P include OEM card > fully supported by Asterisk and Run on most of Linux distributions > such as centOS, Fedora, Debian, Gentoo, Red Hat, SuSE, Slackware, > Mandrake,,,; FreeBSD > (2). Always run stable software to test your voice card(hardware) > otherwise you will be confused whether the problem rising from your > voice card(hardware) or software. > InfoMatrix systems > Adam Z > ------------------------ > This indicates that 1057:5608 has a Controller Chipset, and should be > supported by the serial driver included in the Linux kernel. > This is provided that: > [ 0.188146] pci 0000:01:0a.0: PME# supported from D0 D2 D3hot D3cold > [ 0.188151] pci 0000:01:0a.0: PME# disabled > can be overcome. > > Try running > $ sudo wvdialconf > to assess if the modem is at all accessed. > > Report back to the List, not me directly. > Also copy to Cary, who can advise you on "in Cuba" issues. > > MarvS > > > On Mon, May 10, 2010 at 10:39 PM, Alain Rodriguez Lugones > <alain.rguez@xxxxxxxxxxxx> wrote: >>  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 Linux Mint 8 Helena - Main Edition >>  kernel >> 2.6.31-14-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 ,  ALSA_version=1.0.20 >> Linux version 2.6.31-14-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu >> 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 >>  scanModem update of:  2010_03_18 >> >> Distrib_ID=LinuxMint >> DistribCodeName=helena >> >> >> Presently install your Linux Distributions dkms package. It provides for >> automated driver updates, >> following upgrade of your kernel.  For details see >> http://linux.dell.com/projects.shtml#dkms >> >>  There are no blacklisted modem drivers in /etc/modprobe*  files >> >>  Potentially useful modem drivers now loaded are: >> >> >> Attached USB devices are: >>  ID 090c:1000 Feiya Technology Corp. Flash Drive >> 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: >> 01:0a.0 Communication controller: Motorola Wildcard X100P >> High Definition Audio cards can host modem chips. >> >> For candidate card in slot 01:0a.0, firmware information and bootup >> diagnostics >> are: >>  PCI slot    PCI ID      SubsystemID   Name >>  ----------   ---------    ---------    -------------- >>  01:0a.0     1057:5608    1057:0000    Communication >> controller: Motorola Wildcard X100P >> >>  Modem interrupt assignment and sharing: >>  --- Bootup diagnostics for card in PCI slot 01:0a.0 ---- >> [   0.188089] pci 0000:01:0a.0: reg 10 io port: [0xd800-0xd8ff] >> [   0.188098] pci 0000:01:0a.0: reg 14 32bit mmio: [0xfe5fe000-0xfe5fefff] >> [   0.188143] pci 0000:01:0a.0: supports D2 >> [   0.188146] pci 0000:01:0a.0: PME# supported from D0 D2 D3hot D3cold >> [   0.188151] pci 0000:01:0a.0: PME# disabled >> >>  The PCI slot 01:0a.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 01:0a.0: >>     Modem chipset  detected on >> NAME="Communication controller: Motorola Wildcard X100P" >> CLASS=0780 >> PCIDEV=1057:5608 >> SUBSYS=1057:0000 >> IRQ=11 >> IDENT=Motorola >> >>  For candidate modem in:  01:0a.0 >>  0780 Communication controller: Motorola Wildcard X100P >>    Primary device ID:  1057:5608 >>  Support type needed or chipset:     Motorola >> >> >> >>  Completed candidate modem analyses. >> >>  The base of the UDEV device file system is: /dev/.udev >> >>  Versions adequately match for the compiler installed: 4.4.1 >>       and the compiler used in kernel assembly: 4.4.1 >> >>  The patch utility is needed for compiling ALSA drivers, and possibly others. >> >> >>  Minimal compiling resources appear complete: >>  make utility - /usr/bin/make >>  Compiler version 4.4 >>  linuc_headers base folder /lib/modules/2.6.31-14-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. >> >> >> >> For Debian and some related distributions, a package kernel-kbuild-2.6-31 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 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/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 -------- >> >> >> >> >
