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.25.10-86.fc9.i686
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,
Linux version 2.6.25.10-86.fc9.i686 (mockbuild@) (gcc version 4.3.0
20080428 (Red Hat 4.3.0-8) (GCC) ) #1 SMP Mon Jul 7 20:46:03 EDT 2008
scanModem update of: 2008_07_25
There are no blacklisted modem drivers in /etc/modprobe* files
Attached USB devices are:
ID 058f:6366 Alcor Micro Corp.
ID 1d6b:0002 Linux Foundation 2.0 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0002 Linux Foundation 2.0 root hub
ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface
[Integrated Module]
ID 1d6b:0001 Linux Foundation 1.1 root hub
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 103c:30d8 Audio device: Intel Corporation 82801H
Modem interrupt assignment and sharing:
16: 290 671000 IO-APIC-fasteoi uhci_hcd:usb3, HDA Intel,
i915@pci:0000:00:02.0
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
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 drivers are in the kernel modules tree at:
/lib/modules/2.6.25.10-86.fc9.i686/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.25.9-76.fc9.i686/kernel/sound/pci/hda/snd-hda-intel.ko
The ALSA verion is 1.0.16rc2
The modem cards detected by "aplay -l" are: None
The /proc/asound/pcm file reports:
-----------------------
00-00: AD198x Analog : AD198x Analog : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xe4624000 irq 16
=== 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 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (rev 0c)
00:19.0 Ethernet controller: Intel Corporation 82562GT 10/100 Network
Connection (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)
10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG
Network Connection (rev 02)
------------------------------------------------
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 DOCs/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. 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/ALSAroot.tgz
Predictive diagnostics for card in bus 00:1b.0:
Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801H "
CLASS=0403
PCIDEV=8086:284b
SUBSYS=103c:30d8
IRQ=16
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
0403 Audio device: Intel Corporation 82801H
Primary device ID: 8086:284b
Subsystem PCI_id 103c:30d8
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.3.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
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
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.3.0
and the compiler used in kernel assembly: 4.3.0
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.3
linuc_headers base folder /lib/modules/2.6.25.10-86.fc9.i686/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 n. 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 318024 Май 13 13:13 /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
Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 ppp0
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:
/etc/udev/rules.d/50-udev-default.rules~:KERNEL=="mwave",
NAME="modems/mwave", GROUP="uucp"
/etc/udev/rules.d/50-udev-default.rules.rpmsave:KERNEL=="mwave",
NAME="modems/mwave", GROUP="uucp"
/etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave",
NAME="modems/mwave", GROUP="uucp"
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 --------
