Re: Khaja Canada Help for Agere Soft Modem

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

 



Antonio

hsfmodem is the Wrong package for this modem.
Khaja has data from Microsoft boot that it is an Agere 11c11040 chipset modem,


>From my earlier message.
There is information on this modem family using agrmodem + agrserial
drivers in http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
the agrsm_howto.txt
You could install the 15 MB   linux-image-2.6.21.0-22_2.6.21.0-22_i386.deb
with:
$ sudo dpkg -i  linux*.deb
which would include the agrmodem + agrserial drivers, but they will
ONLY serve under the 2.6.21.0-22 kernel.

MarvS
scanModem maintainer

On Thu, Jun 12, 2008 a t 8:21 PM, Antonio Olivares
<olivares14031@xxxxxxxxx> wrote:
>
>
>
> --- On Thu, 6/12/08, Ubiquitous Pervasive <ubiq3005@xxxxxxxxx> wrote:
>
>> From: Ubiquitous Pervasive <ubiq3005@xxxxxxxxx>
>> Subject: Re: Khaja Canada Help for Agere Soft Modem
>> To: olivares14031@xxxxxxxxx
>> Date: Thursday, June 12, 2008, 4:04 PM
>> I used hsfmodem-7.68.00.10x86_64full.tar.gz. After
>> Installing it I got new problems with my sound card. My
>> sound card driver was not loaded. What to do you?Please
>> help.
>
> I would ask you first if the modem works/connects?
>
> $ sudo wvdialconf /etc/wvdial.conf
>
> will look for the modem.  If it does not work uninstall the linuxant drivers.  There obviously has to be something wrong.  If you have windows, you can try to identify the driver by using the diagnostics found in scanModem, I am going to reattach your scanModem back to list in hopes that others can help fix this bad situation
>
> This part
> <quote>
> If an alternative boot into Microsoft windows can be done, do mouse
> clicks on:
>   Start > Settings > Control Panel > Classical View (for Window XP) > System
>> Hardware > Device Manager > Modems > Click on the + > Modem. Double click to
> expand the graphic. Manufacturer information may be displayed. For example, CXT
> stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor
> and device information. From the Driver Details TAB, copy out the VENdor and DEVice information.
> Next do the Query Modem and record the ATI specifications displayed such as:
>    ATI3 - Agere SoftModem Version 2.1.22
>    ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
> Try to identify the modem setup file, with name perhaps MODEM.INF.
> If may contain chipset Vendor informaton.
> </quote>
>
>
> <scanModem>
>  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-18-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,
> Linux version 2.6.24-18-generic (buildd@king) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed May 28 19:28:38 UTC 2008
>  scanModem update of:  2008_06_05
>
>
> 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 hcflinmodem drivers for Conexant chipsest modes are x86_64 competent.
>
>  There are no blacklisted modem drivers in /etc/modprobe*  files
> Attached USB devices are:
>  ID 0c45:62c0 Microdia
>  ID 0db0:a97a Micro Star International
>  ID 045e:00b9 Microsoft Corp. Wireless Optical Mouse 3.0
>
> 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       1462:3ff3       Audio device: Intel Corporation 82801H
>
>  Modem interrupt assignment and sharing:
>  20:        447        428   IO-APIC-fasteoi   HDA Intel
>  --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
> [   31.236791] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 20 (level, low) -> IRQ 20
> [   31.237290] 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.
>  PCI slot 00:1b.0 has a High Definition Audio Card
>
> The ALSA verion is 1.0.15
> The modem cards detected by "aplay -l"  are: None
>
>
> The /proc/asound/pcm file reports:
> -----------------------
> 00-02: ALC883 Analog : ALC883 Analog : capture 1
> 00-01: ALC883 Digital : ALC883 Digital : playback 1
> 00-00: ALC883 Analog : ALC883 Analog : playback 1 : capture 1
>
> about /proc/asound/cards:
> ------------------------
>  0 [Intel          ]: HDA-Intel - HDA Intel
>                      HDA Intel at 0xfe0f8000 irq 20
> === Finished firmware and bootup diagnostics, next deducing cogent software. ===
>
> A candidate modem is not evident among the PCI devices:
> ------------------------------------------------
> 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
> 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
> 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
> 00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
> 00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
> 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
> 01:04.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02)
> 01:04.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD Controller (rev 01)
> 01:04.4 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
> 03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
> 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
> ------------------------------------------------
>  with USB and bridge devices not displayed.
>
>  If your modem is connected by an external serial cable,
>  or mounted internally on an ISA card, scanModem would not access it.
>  Try with Root permission
>  $ sudo wvdialconf  /etc/wvdial.conf
>  to detect these modem types and some USB modems.
>  If the detection is successful, read the DOCs/wvdial.txt .
>  Edit the /etc/wvdial.conf with Root permission:
>        sudo  gedit  /etc/wvdial.conf
>  will be able to dial out with Root permission:
>        sudo wvdial
>
>  Many modems for which scanModem fails have Conexant chips.
>  From http://www.linuxant.com/drivers/modemident.php
>  get the ListModem tool, which will report on Conexant chipset modems
>
>  If the above tests fail, please provide any independent information available on your modem.
>  If an alternative boot into Microsoft windows can be done, do mouse
> clicks on:
>   Start > Settings > Control Panel > Classical View (for Window XP) > System
>> Hardware > Device Manager > Modems > Click on the + > Modem. Double click to
> expand the graphic. Manufacturer information may be displayed. For example, CXT
> stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor
> and device information. From the Driver Details TAB, copy out the VENdor and DEVice information.
> Next do the Query Modem and record the ATI specifications displayed such as:
>    ATI3 - Agere SoftModem Version 2.1.22
>    ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
> Try to identify the modem setup file, with name perhaps MODEM.INF.
> If may contain chipset Vendor informaton.
>
>  The /proc/asound/ audio+modem diagostics are being copied.
>  Finished copy to Modem/ALSAkhaja.tgz
>
> Predictive diagnostics for card in bus 00:1b.0:
>        Modem chipset not detected on
> CLASS="Class 0403: 8086:284b"
> NAME="Audio device: Intel Corporation 82801H "
> SUBSYS=1462:3ff3
> PCIDEV=8086:284b
> IRQ=20
> HDA=8086:284b
> SOFT=8086:284b.HDA
>
>
>  High Definition Audio (HDA) cards MAY host a modem chip in their Subsystem,
>  and many are supported by the ALSA audio+modem driver snd-hda-intel
>  A modem was not detected on HDA card 8086:284b.
>  If another modem card is present, then most likely 8086:284b does not host a modem.
>  If another modem card has not been detected, then possibilities are:
>        1) A Conexant modem chip is present on 8086:284b, as Conexant chips
>  are frequently not detectable by ALSA diagnostics
>        2) The modem may be of the older non-PCI Controller Chipset (hardware) type.
> Try detection with Root permission:
>        sudo wvdialconf  /etc/wvdial.conf
>
>  For candidate modem in:  00:1b.0
>   Class 0403: 8086:284b Audio device: Intel Corporation 82801H
>      Primary device ID:  8086:284b
>    Subsystem PCI_id  1462:3ff3
>    Softmodem codec or chipset from diagnostics:
>                               from    Archives:
>
>
>
> Support type needed or chipset:
>
> Support can likely be achieved through two mutually exclusive alternatives:
> 1) The hsfmodem software for Conexant chipset modems: Read DOCs/Conexant.txt
> The following ALSA alternative CANNOT work with Conexant modems.
>
> 2) An ALSA modem driver plus slmodemd.  Read DOCs/Smartlink.txt for details, and
> to test get the package SLMODEMD.gcc4.2.tar.gz from:
>        http://linmodems.technion.ac.il/packages/smartlink/
>
> ----------------end Softmodem section --------------
>
> Writing DOCs/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 DOCs/Conexant.txt
>
>  From  http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
>  download hsfmodem-7.68.00.07full_k2.6.24_18_generic_ubuntu_i386.deb.zip
>  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 DOCs/Testing.txt  for details.
>
>  Read DOCs/Conexant.txt
>
> Writing DOCs/Conexant.txt
>
> Writing DOCs/Smartlink.txt
> ============ end Smartlink section =====================
>
>
>  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
>
>  linux-headers-2.6.24-18-generic resources needed for compiling are not manifestly ready!
>
>  If compiling is necessary packages must be installed, providing:
>         linux-headers-2.6.24-18-generic
> Compressed files at: /usr/src/linux-source-2.6.24.tar.bz2
>
>
> 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 313600 2007-10-04 16:48 /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: eth0 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/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 --------
>
>
> </scanModem>
>
>> Thank you
>>
>> dmesg |grep snd
>> [   83.430677] snd_hda_codec: no version for
>> "snd_ctl_add" found: kernel tainted.
>> [   83.431035] snd_hda_codec: Unknown symbol
>> snd_ctl_elem_read
>> [   83.431075] snd_hda_codec: Unknown symbol
>> snd_ctl_elem_write
>> [   83.432637] snd_hda_intel: Unknown symbol
>> snd_hda_bus_new
>> [   83.432729] snd_hda_intel: Unknown symbol
>> snd_hda_build_pcms
>> [   83.432778] snd_hda_intel: Unknown symbol
>> snd_hda_codec_new
>> [   83.432871] snd_hda_intel: Unknown symbol
>> snd_hda_queue_unsol_event
>> [   83.433043] snd_hda_intel: Unknown symbol
>> snd_hda_calc_stream_format
>> [   83.433127] snd_hda_intel: Unknown symbol
>> snd_hda_suspend
>> [   83.433208] snd_hda_intel: Unknown symbol
>> snd_hda_codec_remove_notify_all
>> [   83.433302] snd_hda_intel: Unknown symbol snd_hda_resume
>> [   83.433374] snd_hda_intel: Unknown symbol
>> snd_hda_build_controls
>> [  779.759166] snd_hda_codec: Unknown symbol
>> snd_ctl_elem_read
>> [  779.759217] snd_hda_codec: Unknown symbol
>> snd_ctl_elem_write
>> [  779.761176] snd_hda_intel: Unknown symbol
>> snd_hda_bus_new
>> [  779.761271] snd_hda_intel: Unknown symbol
>> snd_hda_build_pcms
>> [  779.761322] snd_hda_intel: Unknown symbol
>> snd_hda_codec_new
>> [  779.761413] snd_hda_intel: Unknown symbol
>> snd_hda_queue_unsol_event
>> [  779.761595] snd_hda_intel: Unknown symbol
>> snd_hda_calc_stream_format
>> [  779.761682] snd_hda_intel: Unknown symbol
>> snd_hda_suspend
>> [  779.761778] snd_hda_intel: Unknown symbol
>> snd_hda_codec_remove_notify_all
>> [  779.761878] snd_hda_intel: Unknown symbol snd_hda_resume
>> [  779.761954] snd_hda_intel: Unknown symbol
>> snd_hda_build_controls
>> [  892.279633] snd_hda_codec: Unknown symbol
>> snd_ctl_elem_read
>> [  892.279685] snd_hda_codec: Unknown symbol
>> snd_ctl_elem_write
>> [  892.281701] snd_hda_intel: Unknown symbol
>> snd_hda_bus_new
>> [  892.281797] snd_hda_intel: Unknown symbol
>> snd_hda_build_pcms
>> [  892.281847] snd_hda_intel: Unknown symbol
>> snd_hda_codec_new
>> [  892.281939] snd_hda_intel: Unknown symbol
>> snd_hda_queue_unsol_event
>> [  892.282120] snd_hda_intel: Unknown symbol
>> snd_hda_calc_stream_format
>> [  892.282208] snd_hda_intel: Unknown symbol
>> snd_hda_suspend
>> [  892.282293] snd_hda_intel: Unknown symbol
>> snd_hda_codec_remove_notify_all
>> [  892.282393] snd_hda_intel: Unknown symbol snd_hda_resume
>> [  892.282469] snd_hda_intel: Unknown symbol
>> snd_hda_build_controls
>>
>>
>> ----- Original Message ----
>> From: Antonio Olivares <olivares14031@xxxxxxxxx>
>> To: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>
>> Cc: discuss@xxxxxxxxxxxxx
>> Sent: Thursday, June 12, 2008 18:58:07
>> Subject: Re: Khaja Canada Help for Agere Soft Modem
>>
>> I have recommended the hsfmodem driver because scanModem
>> reported the following:
>>
>> 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    1462:3ff3    Audio device: Intel
>> Corporation 82801H
>>
>> Modem interrupt assignment and sharing:
>> 20:        447        428   IO-APIC-fasteoi   HDA Intel
>> --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
>> [   31.236791] ACPI: PCI Interrupt 0000:00:1b.0[A] ->
>> GSI 20 (level, low) -> IRQ 20
>> [   31.237290] PCI: Setting latency timer of device
>> 0000:00:1b.0 to 64
>>
>> Predictive diagnostics for card in bus 00:1b.0:
>>     Modem chipset not detected on
>> CLASS="Class 0403: 8086:284b"
>> NAME="Audio device: Intel Corporation 82801H "
>> SUBSYS=1462:3ff3
>> PCIDEV=8086:284b
>> IRQ=20
>> HDA=8086:284b
>> SOFT=8086:284b.HDA
>>
>> Support type needed or chipset:
>>
>> Support can likely be achieved through two mutually
>> exclusive alternatives:
>> 1) The hsfmodem software for Conexant chipset modems: Read
>> DOCs/Conexant.txt
>> The following ALSA alternative CANNOT work with Conexant
>> modems.
>>
>> 2) An ALSA modem driver plus slmodemd.  Read
>> DOCs/Smartlink.txt for details, and
>> to test get the package SLMODEMD.gcc4.2.tar.gz from:
>>     http://linmodems.technion.ac.il/packages/smartlink/
>>
>> ----------------end Softmodem section --------------
>>
>> Writing DOCs/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 DOCs/Conexant.txt
>>
>> From
>> http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
>> download
>> hsfmodem-7.68.00.07full_k2.6.24_18_generic_ubuntu_i386.deb.zip
>> 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 DOCs/Testing.txt  for details.
>>
>> Read DOCs/Conexant.txt
>>
>> But installation failed since the driver from linuxant
>> website is for x86 and not for x86_64.  He will try the
>> generic tar.gz file for x86_64.
>>
>> Regards,
>>
>> Antonio
>>
>>
>> --- On Thu, 6/12/08, Marvin Stodolsky
>> <marvin.stodolsky@xxxxxxxxx> wrote:
>>
>> > From: Marvin Stodolsky
>> <marvin.stodolsky@xxxxxxxxx>
>> > Subject: Re: Khaja Canada Help for Agere Soft Modem
>> > To: "Ubiquitous Pervasive"
>> <ubiq3005@xxxxxxxxx>
>> > Cc: discuss@xxxxxxxxxxxxx
>> > Date: Thursday, June 12, 2008, 2:46 PM
>> > Khaja
>> >
>> > Under
>> > CPU=x86_64,  Linux version 2.6.24-18-generic
>> (buildd@king)
>> > with Agere Modem Vendor ID 11C1 and Product ID = 1040
>> > on the High Definition Audio card, there is currently
>> no
>> > support under Linux.
>> >
>> > If you upgrade your System to Ubuntu Feisty (2.6.22
>> > kernels) or Hardy
>> > (2.6.24 kernels) there is an option. BUT it will/may
>> work
>> > under one
>> > particular kernel.
>> > There is information on this modem family using
>> agrmodem +
>> > agrserial
>> > drivers in
>> >
>> http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
>> > the agrsm_howto.txt
>> > You could install the 15 MB
>> > linux-image-2.6.21.0-22_2.6.21.0-22_i386.deb
>> > with:
>> > $ sudo dpkg -i  linux*.deb
>> > which would include the agrmodem + agrserial drivers,
>> but
>> > they will
>> > ONLY serve under the 2.6.21.0-22 kernel.
>> >
>> > The alternative is to read the InfoGeneral.txt about
>> other
>> > modem hardware.
>> >
>> > Condolences,
>> >
>> > MarvS
>> > scanModem maintainer
>> >
>> > On Thu, Jun 12, 2008 at 5:12 PM, Ubiquitous Pervasive
>> > <ubiq3005@xxxxxxxxx> wrote:
>> > > Hi,
>> > > I am running Ubuntu 8.04. Kernel 2.6.24_14, AMD
>> 64 bit
>> > version.
>> > > I have Agere Modem Vendor ID 11C1 and Product ID
>> =
>> > 1040. I tried the
>> > > latest martian-full package but it failed to
>> compile.
>> > >
>> > > I also have few questions:
>> > > * Do this modem work in my system?
>> > > * If I compile it on 32 bit version computer will
>> it
>> > work in my system.
>> > >
>> > > I am sending ModemData.txt with this email. Thank
>> you
>> > for your help.
>> > >
>> > > Khaja
>> > >
>> > > Send instant messages to your online friends
>> > http://uk.messenger.yahoo.com
>>
>> Send instant messages to your online friends
>> http://uk.messenger.yahoo.com
>
>
>
>

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

  Powered by Linux