Hamid,
scanModem reports that you have an HSF;HCF modem, either one or the
other, but not both. You may try the first one though hsfmodem
through linuxant:
Predictive diagnostics for card in bus 05:00.0:
Modem chipset detected on
NAME="Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem "
CLASS=0780
PCIDEV=14f1:2f30
SUBSYS=14f1:2075
IRQ=3
HDA2=00:1b.0
IDENT=hsfmodem
Driver=hsfmodem-drivers
For candidate modem in: 05:00.0
0780 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem
Primary device ID: 14f1:2f30
Support type needed or chipset: hsfmodem
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
Start at http://www.linuxant.com/drivers/hsf/full for
eventually download of a hsfmodem-7.68.00.12full_k.???.zip package
with ??? the package type (deb, rpm, tar etc)
These packages have compiled drivers but will also compile a driver,
if there is a mismatch between the resident kernel and provided driver.
The generic hsfmodem-7.68.00.12full.tar.gz package only provides
compiling support
Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to find the
hsfmodem package matching your System. For several Linux distros, there are
precompiled drivers matched to specific kernels. These have within
the FileName,
your KernelVersion: 2.6.31.5_127.fc12.i686.PAE
They can be found through
http://www.linuxant.com/drivers/hsf/full/downloads.php
A more precise location may be given a few paragraphs below.
If an EXACT Match with your your KernelVersion is not found, one of the
"Generic packages with source" near the bottom of the page must be used.
Downloaded packages must be moved into the Linux partition (home folder is OK)
and unzipped with:
unzip hsf*.zip
The installation command for a .deb suffic packages is, with root/adm
permission:
dpkg -i hsf*.deb
while for .rpm suffix it is, with:
rpm -i hsf*.rpm
Read DOCs/Conexant.txt
NOTE:
You may need to install alsa-driver-1.23-???.rpm from linuxant to make
the driver work. Check the linuxant website for details.
Regards,
Antonio
On 4/15/10, Hamid Hoorzad <hoorzad.sharif@xxxxxxxxx> wrote:
> Hi,
>
> I'm totally beginner and I just don't understand how to use the
> information in ModemData.txt. I'll be very thankful if you help me
> setup my modem in Linux. My modem manufacturer is Gigabyte, but I
> don't know the model. I don't have internet connection in Linux.
>
> Here is ModemData.txt:
>
> 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.31.5-127.fc12.i686.PAE
> 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, fedora , ALSA_version=1.0.22
> Linux version 2.6.31.5-127.fc12.i686.PAE
> (mockbuild@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.4.2 20091027
> (Red Hat 4.4.2-7) (GCC) ) #1 SMP Sat Nov 7 21:25:57 EST 2009
> scanModem update of: 2010_03_18
>
> /etc/lsb-release not found
>
>
> 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:
> snd_hda_intel
>
> Attached USB devices are:
> ID 0a81:0101 Chesen Electronics Corp. Keyboard
> ID 09da:0006 A4 Tech Co., Ltd Optical Mouse WOP-35 / Trust 450L Optical
> Mouse
> 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:
> 05:00.0 Communication controller: Conexant Systems, Inc. HSF 56k
> Data/Fax Modem (rev 01)
> 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
> Controller (rev 02)
> High Definition Audio cards can host modem chips.
>
> For candidate card in slot 05:00.0, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 05:00.0 14f1:2f30 14f1:2075 Communication controller: Conexant
> Systems, Inc. HSF 56k Data/Fax Modem
>
> Modem interrupt assignment and sharing:
> 23: 0 0 IO-APIC-fasteoi ehci_hcd:usb2, uhci_hcd:usb6
> --- Bootup diagnostics for card in PCI slot 05:00.0 ----
> pci 0000:05:00.0: reg 10 32bit mmio: [0xfb000000-0xfb00ffff]
> pci 0000:05:00.0: reg 14 io port: [0xd000-0xd007]
> pci 0000:05:00.0: PME# supported from D3hot D3cold
> pci 0000:05:00.0: PME# disabled
>
> The PCI slot 05:00.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.
>
>
> For candidate card in slot 00:1b.0, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 00:1b.0 8086:293e 1458:a002 Audio device: Intel Corporation 82801I
>
> Modem interrupt assignment and sharing:
> 29: 382 2638 PCI-MSI-edge HDA Intel
> --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
> pci 0000:00:1b.0: reg 10 64bit mmio: [0xfb100000-0xfb103fff]
> pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:1b.0: PME# disabled
> HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
> HDA Intel 0000:00:1b.0: irq 29 for MSI/MSI-X
> HDA Intel 0000:00:1b.0: setting latency timer to 64
> input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input6
>
> The PCI slot 00:1b.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.
>
>
> New HCF.HSF device 8086:293e
> === 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 82801I "
> package="both hcfpcimodem and hsfmodem"
> CLASS=0403
> PCIDEV=8086:293e
> SUBSYS=1458:a002
> IRQ=29
> IDENT=HCF.HSF
>
> For candidate modem in: 00:1b.0
> 0403 Audio device: Intel Corporation 82801I
> Primary device ID: 8086:293e
> Support type needed or chipset: HCF.HSF
>
>
>
> 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
>
> 8086:293e could be either a HSF or HCF Conexant modem, because of ambiguous
> use of the PCI ID by modem assemblers. First try the hcfpcimodem package.
> If the installation aborts, then use the hsfmodem package. Read
> DOCs/Conexant.txt
> for details and Modem/DOCs/YourSystem.txt for follow through guidance.
>
> Start at http://www.linuxant.com/drivers/hsf/full for
> eventually download of a hsfmodem-7.68.00.12full_k.???.zip package
> with ??? the package type (deb, rpm, tar etc)
> These packages have compiled drivers but will also compile a driver,
> if there is a mismatch between the resident kernel and provided driver.
> The generic hsfmodem-7.68.00.12full.tar.gz package only provides
> compiling support
>
>
> Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to find
> the
> hsfmodem package matching your System. For several Linux distros, there are
> precompiled drivers matched to specific kernels. These have within the
> FileName,
> your KernelVersion: 2.6.31.5_127.fc12.i686.PAE
> They can be found through
> http://www.linuxant.com/drivers/hsf/full/downloads.php
> A more precise location may be given a few paragraphs below.
> If an EXACT Match with your your KernelVersion is not found, one of the
> "Generic packages with source" near the bottom of the page must be used.
> Downloaded packages must be moved into the Linux partition (home folder is
> OK)
> and unzipped with:
> unzip hsf*.zip
> The installation command for a .deb suffic packages is, with root/adm
> permission:
> dpkg -i hsf*.deb
> while for .rpm suffix it is, with:
> rpm -i hsf*.rpm
> Read DOCs/Conexant.txt
>
> Writing DOCs/Conexant.txt
>
>
>
> Predictive diagnostics for card in bus 05:00.0:
> Modem chipset detected on
> NAME="Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax
> Modem "
> CLASS=0780
> PCIDEV=14f1:2f30
> SUBSYS=14f1:2075
> IRQ=3
> HDA2=00:1b.0
> IDENT=hsfmodem
> Driver=hsfmodem-drivers
>
> For candidate modem in: 05:00.0
> 0780 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax
> Modem
> Primary device ID: 14f1:2f30
> Support type needed or chipset: hsfmodem
>
>
>
> 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
>
> Start at http://www.linuxant.com/drivers/hsf/full for
> eventually download of a hsfmodem-7.68.00.12full_k.???.zip package
> with ??? the package type (deb, rpm, tar etc)
> These packages have compiled drivers but will also compile a driver,
> if there is a mismatch between the resident kernel and provided driver.
> The generic hsfmodem-7.68.00.12full.tar.gz package only provides
> compiling support
>
>
> Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to find
> the
> hsfmodem package matching your System. For several Linux distros, there are
> precompiled drivers matched to specific kernels. These have within the
> FileName,
> your KernelVersion: 2.6.31.5_127.fc12.i686.PAE
> They can be found through
> http://www.linuxant.com/drivers/hsf/full/downloads.php
> A more precise location may be given a few paragraphs below.
> If an EXACT Match with your your KernelVersion is not found, one of the
> "Generic packages with source" near the bottom of the page must be used.
> Downloaded packages must be moved into the Linux partition (home folder is
> OK)
> and unzipped with:
> unzip hsf*.zip
> The installation command for a .deb suffic packages is, with root/adm
> permission:
> dpkg -i hsf*.deb
> while for .rpm suffix it is, with:
> rpm -i hsf*.rpm
> Read DOCs/Conexant.txt
>
> Writing DOCs/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.4.2
> and the compiler used in kernel assembly: 4.4.2
>
>
>
> Minimal compiling resources appear complete:
> make utility - /usr/bin/make
> Compiler version 4.4
> linuc_headers base folder /lib/modules/2.6.31.5-127.fc12.i686.PAE/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.
>
>
>
>
> 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:
> -r-xr-xr-x. 1 root root 324136 2009-09-16 22:33 /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)
> 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
>
> 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 virbr0
> 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:
>
> Within any ancient /etc/devfs files:
>
> Within ancient kernel 2.4.n /etc/module.conf files:
>
> --------- end modem support lines --------
>
