Hi,
Please find the ModemData.txt file created by scanModem.
I cannot get my modem working.
Prity
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.32-33-generic-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, Ubuntu , ALSA_version=1.0.21
Linux version 2.6.32-33-generic-pae (buildd@zirconium) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #72-Ubuntu SMP Fri Jul 29 22:06:29 UTC 2011
scanModem update of: 2011_08_08
Distrib_ID=Ubuntu
DistribCodeName=lucid
AptRepositoryStem=http://ubuntu.oss.eznetsols.org/ubuntu/
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_atiixp_modem snd_via82xx_modem snd_intel8x0m snd_hda_intel
Attached USB devices are:
ID 0a5c:2145 Broadcom Corp.
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:
00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller (rev 07)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
High Definition Audio cards can host modem chips.
For candidate card in slot 00:03.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:03.0 8086:2a44 17aa:20e6 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 00:03.0 ----
[ 0.221432] pci 0000:00:03.0: reg 10 64bit mmio: [0xfc225800-0xfc22580f]
[ 0.221464] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[ 0.221467] pci 0000:00:03.0: PME# disabled
[ 0.224923] pci 0000:03:00.0: reg 10 64bit mmio: [0xf4300000-0xf4301fff]
[ 0.225048] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
[ 0.225059] pci 0000:03:00.0: PME# disabled
[ 22.315569] iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 22.315599] iwlagn 0000:03:00.0: setting latency timer to 64
[ 22.315652] iwlagn 0000:03:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54
[ 22.368721] iwlagn 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
[ 22.368804] iwlagn 0000:03:00.0: irq 31 for MSI/MSI-X
[ 22.660567] iwlagn 0000:03:00.0: firmware: requesting iwlwifi-5000-2.ucode
[ 22.772581] iwlagn 0000:03:00.0: loaded firmware version 8.24.2.12
[ 265.221611] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 08:76:ff:3f:bf:2c tid = 0
[ 1729.092274] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 08:76:ff:3f:bf:2c tid = 6
The PCI slot 00:03.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 17aa:20f2 Audio device: Intel Corporation 82801I
Modem interrupt assignment and sharing:
17: 152 692 IO-APIC-fasteoi uhci_hcd:usb7, ohci1394, HDA Intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.222108] pci 0000:00:1b.0: reg 10 64bit mmio: [0xfc020000-0xfc023fff]
[ 0.222168] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.222172] pci 0000:00:1b.0: PME# disabled
[ 23.363348] HDA Intel 0000:00:1b.0: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 23.363369] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 23.440262] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 23.440414] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 23.440599] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 23.440762] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
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.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
A candidate modem is not transparent among the PCI devices:
------------------------------------------------
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567LF Gigabit Network Connection (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
15:00.3 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev ff)
15:00.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11)
15:00.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)
------------------------------------------------
with USB, bridge, and RAM devices not displayed.
If a High Definition Audio card is present, if might be hosted on the Subsystem.
If your modem is an
external USB type,
connected by an external serial cable,
or mounted internally on an ISA card,
then 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.
Predictive diagnostics for card in bus 00:03.0:
Modem chipset not detected on
NAME="Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller "
CLASS=0780
PCIDEV=8086:2a44
SUBSYS=17aa:20e6
IRQ=11
HDA2=00:1b.0
For candidate modem in: 00:03.0
0780 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller
Primary device ID: 8086:2a44
Support type needed or chipset:
Predictive diagnostics for card in bus 00:1b.0:
Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801I "
CLASS=0403
PCIDEV=8086:293e
SUBSYS=17aa:20f2
IRQ=17
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801I
Primary device ID: 8086:293e
Support type needed or chipset:
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.4.3
and the compiler used in kernel assembly: 4.4.3
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.4
linuc_headers base folder /lib/modules/2.6.32-33-generic-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:
-rwsr-xr-- 1 root dip 273312 2010-03-07 06:59 /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
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 eth0:avahi wlan0
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/sl-modem.conf:install slamr /sbin/modprobe -qb ungrab-winmodem; /sbin/modprobe --ignore-install slamr; test -e /dev/slamr0 && (chmod 660 /dev/slamr0 && chgrp dialout /dev/slamr0) || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0)
/etc/modprobe.d/sl-modem.conf:install slusb /sbin/modprobe -qb ungrab-winmodem; /sbin/modprobe --ignore-install slusb; test -e /dev/slusb0 && (chmod 660 /dev/slusb0 && chgrp dialout /dev/slusb0) || (/bin/mknod -m 660 /dev/slusb0 c 243 0 2>/dev/null && chgrp dialout /dev/slusb0)
/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 --------
