Jonathan
This is an interesting novel (to us) case of a laptop with:
Class 0703: 8086:266d Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW
Primary PCI_id 8086:266d
Subsystem PCI_id 103c:30c4, chipset from diagnostics: CXT30, a
Conexant type
trying to dialout through a USB
Bus 001 Device 002: ID 22b8:4902 Motorola PCS E398 GSM Phone
with the USB cellphone and Laptop modem pair functional under Microsoft
Kinuthia,
RE: WvDial<*1>: Sending: ATDT*99***1#
If you insert a , it signals a one second pause in the string
Phone = *99,***1#
I'm not user whether it is a appropriate after the 99 as done above,
but you likely need a pause somewhere, to allow adequate COMM between
the Modem and Cellphone,
before the Cellphone starts its pass through dialout
Jonathan is your most capable help in this Linuxant modem case, and
will likely respond on Monday.
Information on any software used to couple the modem and USB cellular
under Microsoft will be useful.
Also if you search at www.google.com with
"Cellular phone" modem Linux
there will be returned some 19,000 URLs,
one (some) of which may solve your problem.
Let us know what works presently, so that the case acquires a URL for
others to follow in the Archives.
MarvS
On Sun, Mar 9, 2008 at 1:20 PM, Kinuthia Muchane <muchanek@xxxxxxxxx> wrote:
>
> MarvS,
>
> Thanks for the amazingly swift reply,I am overwhelmed! Anyway, the
> result of running lsusb is:
>
> Bus 001 Device 002: ID 22b8:4902 Motorola PCS E398 GSM Phone .
>
> And here are the contents of the ModemData.txt:
>
> CPU=i686,
> Linux version 2.6.22-14-generic (buildd@palmer) (gcc version 4.1.3
> 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Sun Oct 14
> 23:05:12 GMT 2007
> scanModem update of: 2008_02_07
>
>
> There are no blacklisted modem drivers in /etc/modprobe* files
>
> The Advanced Linux Sound Architecture (ALSA) packages providing audio
> support,
> also includes drivers for some modems. The ALSA diagnostics are written
> during
> bootup to /proc/asound/ folders.
>
> The /proc/asound/ audio+modem diagostics are being copied.
> Finished copy to Modem/ALSAroot.tgz
>
> The ALSA verion is 1.0.14
> The modem cards detected by "aplay -l" are:
> card 1: Modem [Intel ICH6 Modem], device 0: Intel ICH - Modem [Intel
> ICH6 Modem - Modem]
>
> The /proc/asound/pcm file reports:
> -----------------------
> 00-04: Intel ICH - IEC958 : Intel ICH6 - IEC958 : playback 1
> 00-03: Intel ICH - ADC2 : Intel ICH6 - ADC2 : capture 1
> 00-02: Intel ICH - MIC2 ADC : Intel ICH6 - MIC2 ADC : capture 1
> 00-01: Intel ICH - MIC ADC : Intel ICH6 - MIC ADC : capture 1
> 00-00: Intel ICH : Intel ICH6 : playback 1 : capture 1
> 01-00: Intel ICH - Modem : Intel ICH6 Modem - Modem : playback 1 :
> capture 1
>
> about /proc/asound/cards:
> ------------------------
> 0 [ICH6 ]: ICH4 - Intel ICH6
> Intel ICH6 with unknown codec at irq 17
> 1 [Modem ]: ICH-MODEM - Intel ICH6 Modem
> Intel ICH6 Modem at irq 17
>
>
> The driver snd-intel8x0m with its dependent drivers:
> snd_intel8x0m 18572 0
> snd_ac97_codec 100644 2 snd_intel8x0m,snd_intel8x0
> snd_pcm 80388 4
> snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss
> snd 54660 13
> snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
>
>
> snd_page_alloc 11400 3 snd_intel8x0m,snd_intel8x0,snd_pcm
> ----------
> provide modem + audio support.
>
> Lines in: /proc/asound/card1/codec97#0/mc97#0-0+regs
> -------------------------------
> 0:7c = 4358 and 0:7e = 5430
> are translated from hexadecimal code into the modem chip identifier: CXT30
>
> Support if provided only through hsfmodem drivers. Read Conexant.txt
> USB modem not detected by lsusb
>
> For candidate card in slot 00:1e.3, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 00:1e.3 8086:266d 103c:30c4 Modem: Intel Corporation
> 82801FB/FBM/FR/FW/FRW
>
> Modem interrupt assignment and sharing:
> 17: 388 IO-APIC-fasteoi Intel ICH6, Intel ICH6 Modem
> --- Bootup diagnostics for card in PCI slot 00:1e.3 ----
> [ 9.133792] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 17 (level,
> low) -> IRQ 17
> [ 9.133800] ACPI: PCI interrupt for device 0000:00:1e.3 disabled
> [ 309.052000] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 17 (level,
> low) -> IRQ 17
> [ 309.052000] PCI: Setting latency timer of device 0000:00:1e.3 to 64
>
> The PCI slot 00:1e.3 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 Bootup.txt about possible fixes.
> Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
> if help is needed.
>
>
>
> === Finished modem firmware and bootup diagnostics section. ===
> === Next deducing cogent software ===
>
>
>
>
> Predictive diagnostics for card in PCI bus 00:1e.3:
> Modem chipset detected on
> CLASS="Class 0703: 8086:266d"
> NAME="Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW "
> PCIDEV=8086:266d
> SUBSYS=103c:30c4
> SUBven=103c
> IRQ=17
> IDENT=hsfmodem
> CODECd=CXT30
> COD=CXT
> Driver=snd-intel8x0m
> SOFT=8086:266d.MC97
>
> For candidate modem in PCI bus: 00:1e.3
> Class 0703: 8086:266d Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW
> Primary PCI_id 8086:266d
> Subsystem PCI_id 103c:30c4
> Softmodem codec or chipset from diagnostics: CXT30, a Conexant type
> using hsfmodem software.
> from Archives:
> CXT is a generic for all CXTnumbers, with Linuxant hsfmodem
> software support.
>
>
> This is a NEW softmodem case! Please send the output ModemData.txt
> to DISCUSS@xxxxxxxxxxxxx to enrich the Archive and help others!
> If further assistance is not needed, please use email Subject:
> New Case Only
> -------------------------------------------
> Lacking a dsp (digital signal processing) chip, the modem is a software
> intensive or "softmodem" type. Its primary controller manages the traffic
> with the CPU. But the software needed is specified in the Subsystem.
> -----------------------------------------
> Support type needed or chipset: hsfmodem
>
>
> Writing Intel.txt
>
> For owners of a Dell PCs with Conexant HSF modems, a driver source
> package with full speed enabled is available, but requires driver
> compiling. Read Conexant.txt
>
> The hsfmodem package serves a great variety of Conexant chipset modems.
> From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
> download hsfmodem_VersionSpec_k2.6.22_14_generic_ubuntu_i386.deb.zip
> with 2.6.22_14_generic equivalent to
> 2.6.22-14-generic, your kernel version.
> Under Linux unpack with:
> $ unzip hsfmodem*.zip
> Then install with:
> $ sudo dpkg -i hsfmodem*.deb
> Subsequently, the modem should be found with
> $ sudo wvdialconf /etc/wvdial.conf
> Edit in your personal information with:
> $ sudo gedit /etc/wvdial.conf
> and try dialing out with:
> $ sudo wvdial.
> See Testing.txt for details.
>
> Read Conexant.txt
>
> Writing Conexant.txt
>
>
> Completed candidate modem analyses.
>
> The base of the UDEV device file system is: /dev/.udev
>
> Versions adequately match for the compiler installed: 4.1.3
> and the compiler used in kernel assembly: 4.1.3
>
>
>
> Minimal compiling resources appear complete:
> make utility - /usr/bin/make
> Compiler version 4.1
> linuc_headers base folder /lib/modules/2.6.22-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 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 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 package
> 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 22:57 /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
> 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/YourSystem.txt concerning other COMM channels: eth0 eth1
> 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:
>
> Within /etc/modprobe.conf files:
> /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/alsa-base:options snd-atiixp-modem index=-2
> /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
> Within any ancient /etc/devfs files:
>
> Within ancient kernel 2.4.n /etc/module.conf files:
>
> --------- end modem support lines --------
>
> I was having trouble getting to send you a plain text email,thats why I
> was not able to send you this output but I have managed to get round
> that now. So in the meantime,I went to Linuxant and downloaded the most
> compatible driver in reference to the above ,a hsfmodem which I went
> ahead and installed without a hitch but alas I cannot get connected.
> Here in Kenya nobody knows a whit about Linux,so you are kinda on your own.
> I hope this helps and if you need anymore information,I am ready. Once
> again thank you very much!
>
> Kinuthia.
>
>
>
