Antonis.
Is your modem internal of external?
Try to get modem information under a Microsoft boot, if possible.
Otherwise the best guess for an internal modem is that there is a
Conexant modem chip on the Subsystem of:
Class 0403: 8086:284b Audio device: Intel Corporation 82801H
Primary PCI_id 8086:284b
Subsystem PCI_id 1179:ff00
To check out this possibility under Linux
1) compiling is necessary. Packages must be installed, providing:
gcc-4.2
make
kernel-source-2.6.24.2-desktop586-4mdv
or corresponding kernel-headers
2) Read Conexant.txt about the hsfmodem package.
Note that www.linuxant.com has software for dectecting/diagnosing
Conexant modem chips.
MarvS
scanModem maintainer
On Wed, Apr 2, 2008 at 12:15 PM, Antonis Tsolomitis
<antonis.tsolomitis@xxxxxxxxx> wrote:
>
> Dear All.
>
> I try to use the modem on this laptop. I attach the ModemData.txt file. I
> do not see inside it any detection. Maybe I am wrong.
>
>
> thanks for the help,
>
> Antonis.
>
>
> 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 Mandriva Linux release 2008.1 (Cooker) for
> i586
> Kernel 2.6.24.2-desktop586-4mdv on a Dual-processor i686 / kernel
> 2.6.24.2-desktop586-4mdv
> With this Subject Line cogent experts will be alerted, and useful case
> names left in the Archive.
> YourCountry will enable Country specific guidance. Your contry's local
> Linux experts
> 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, Mandriva Linux release 2008.1 (Cooker) for i586
> Kernel 2.6.24.2-desktop586-4mdv on a Dual-processor i686 /
> Linux version 2.6.24.2-desktop586-4mdv (lcapitulino@xxxxxxxxxxxxxxx) (gcc
> version 4.2.2 20071128 (prerelease) (4.2.2-2mdv2008.1)) #1 SMP Thu Feb 21
> 19:29:15 CET 2008
> scanModem update of: 2008_03_31
>
> There are no blacklisted modem drivers in /etc/modprobe* files
> USB modem not detected by lsusb
>
> 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 1179:ff00 Audio device: Intel
> Corporation 82801H
>
> Modem interrupt assignment and sharing:
> 22: 14703 14345 IO-APIC-fasteoi HDA Intel
> --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 22
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
>
> For candidate card in slot 01:00.1, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 01:00.1 1002:aa08 1002:aa08 Audio device: ATI
> Technologies Inc RV630 audio device [Radeon HD 2600 Series]
>
> Modem interrupt assignment and sharing:
> 17: 5961 5943 IO-APIC-fasteoi HDA Intel, ohci1394, eth0
> --- Bootup diagnostics for card in PCI slot 01:00.1 ----
> ACPI: PCI Interrupt 0000:01:00.1[B] -> GSI 17 (level, low) -> IRQ 17
> PCI: Setting latency timer of device 0000:01:00.1 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.
>
> The ALSA verion is 1.0.16
> The modem cards detected by "aplay -l" are:
>
>
> The /proc/asound/pcm file reports:
> -----------------------
> 00-04: ALC268 Analog : ALC268 Analog : capture 1
> 00-00: ALC268 Analog : ALC268 Analog : playback 1 : capture 1
> 01-03: ATI HDMI : ATI HDMI : playback 1
>
> about /proc/asound/cards:
> ------------------------
> 0 [Intel ]: HDA-Intel - HDA Intel
> HDA Intel at 0xfc400000 irq 22
> 1 [HDMI ]: HDA-Intel - HDA ATI HDMI
> HDA ATI HDMI at 0xfc010000 irq 17
> === Finished firmware and bootup diagnostics, next deducing cogent
> software. ===
>
> A candidate modem is not evident among the PCI devices:
> ------------------------------------------------
> 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:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 9581
> 01:00.1 Audio device: ATI Technologies Inc RV630 audio device [Radeon HD
> 2600 Series]
> 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E PCI
> Express Fast Ethernet controller (rev 01)
> 05:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network
> Connection (rev 02)
> 0c:04.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE
> 1394 Host Controller
> 0c:04.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card
> Reader (SD/MMC/MS/MS PRO/xD)
> 0c:04.3 SD Host controller: Texas Instruments PCIxx12 SDA Standard
> Compliant SD Host Controller
> ------------------------------------------------
> 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
> $ wvdialconf /etc/wvdial.conf
> to detect these modem types and some USB modems.
> If the detection is successful, read the wvdial.txt .
> Edit the /etc/wvdial.conf with Root permission:
> gedit /etc/wvdial.conf
> will be able to dial out with Root permission:
> 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.
> 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/ALSAroot.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 "
> PCIDEV=8086:284b
> SUBSYS=1179:ff00
> IRQ=22
> 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:
> wvdialconf /etc/wvdial.conf
>
> For candidate modem in: 00:1b.0
> Class 0403: 8086:284b Audio device: Intel Corporation 82801H
> Primary PCI_id 8086:284b
> Subsystem PCI_id 1179:ff00
> 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 Conexant.txt
> The following ALSA alternative CANNOT work with Conexant modems.
>
> 2) An ALSA modem driver plus slmodemd. Read 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 --------------
>
> 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
>
> Read Conexant.txt
>
> Writing Conexant.txt
>
> Writing Smartlink.txt
> ============ end Smartlink section =====================
>
>
> Predictive diagnostics for card in bus 01:00.1:
> Modem chipset not detected on
> CLASS="Class 0403: 1002:aa08"
> NAME="Audio device: ATI Technologies Inc RV630 audio device [Radeon HD 2600
> Series]"
> PCIDEV=1002:aa08
> SUBSYS=1002:aa08
> IRQ=17
>
> For candidate modem in: 01:00.1
> Class 0403: 1002:aa08 Audio device: ATI Technologies Inc RV630 audio
> device [Radeon HD 2600 Series]
> Primary PCI_id 1002:aa08
> Support type needed or chipset:
>
>
> ----------------end Softmodem section --------------
>
> scanModem could not identify the Support Type needed from diagnosics or
> archives.
> 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.
> 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 base of the UDEV device file system is: /dev/.udev
>
> The kernel was compiled with gcc version 4.2.2 and a compiler is not
> installed
>
> linux-headers-2.6.24.2-desktop586-4mdv resources needed for compiling are
> not manifestly ready!
>
> If compiling is necessary packages must be installed, providing:
> gcc-4.2 make kernel-source-2.6.24.2-desktop586-4mdv
>
>
> 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-t 1 root root 317284 2008-02-01 01:41 /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
> noauth
> noipdefault
> usepeerdns
>
> 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
> Which can interfere with Browser naviagation.
>
> Don't worry about the following, it is for the experts
> should trouble shooting be necessary.
> ==========================================================
>
> M slamr0 c 242 0
> M slamr1 c 242 1
> M slusb0 c 243 0
> M slusb1 c 243 1
> 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-default.rules:KERNEL=="mwave",
> NAME="modems/mwave", GROUP="uucp"
> /etc/udev/rules.d/00-hcfpci.rules:KERNEL=="ttySHCF0", SYMLINK="modem"
> Within /etc/modprobe.conf files:
>
> Within any ancient /etc/devfs files:
>
> Within ancient kernel 2.4.n /etc/module.conf files:
> /etc/modules.conf:alias /dev/modem /dev/ttySHCF
> --------- end modem support lines --------
>
>
>
