Hello Linmodems crew,
I am attempting to config a modem on a laptop that was purchase through linux certified in San Jose CA. After running a modem probe utility a modem.txt file was created (info pasted below). The modem.text file indicates what is on my system and there is also a message prompting me to send this case information to linmodeds.org for help. There are multiple levels of configuration that need to be correct for this thing to work. I think I'm close to getting close. I the slmodemd is running, I can call the network configuration tool (neat), but when I manually initiate the 'slmodemd start' it fails. I'm not exactly sure which files support the configuration. More details are included below. Any help would be appreciated.
*****************Modem.txt output below***********************
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 Fedora Core release 6 (Zod)
Kernel kernel 2.6.18-1.2798.fc6
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, Fedora Core release 6 (Zod)
Kernel
Linux version 2.6.18-1.2798.fc6 (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Mon Oct 16 14:37:32 EDT 2006
scanModem update of: 2008_01_21
The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/1
There are no blacklisted modem drivers in /etc/modprobe* files
The Advanced Linux Sound Architecture (ALSA) packages providing audio support,
also includes drivers for some modems. The ALSA diagnostics are written during
bootup to /proc/asound/ folders.
The /proc/asound/ audio+modem diagostics are being copied.
Finished copy to Modem/ALSAroot.tgz
The /proc/asound/pcm file reports:
-----------------------
00-04: Intel ICH - IEC958 : Intel ICH6 - IEC958 : playback 1
00-03: Intel ICH - ADC2 : Intel ICH6 - ADC2 : capture 1
00-02: Intel ICH - MIC2 ADC : Intel ICH6 - MIC2 ADC : capture 1
00-01: Intel ICH - MIC ADC : Intel ICH6 - MIC ADC : capture 1
00-00: Intel ICH : Intel ICH6 : playback 1 : capture 1
01-00: Intel ICH - Modem : Intel ICH6 Modem - Modem : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [ICH6 ]: ICH4 - Intel ICH6
Intel ICH6 with VIA1612A at 0xffe3fc00, irq 169
1 [Modem ]: ICH-MODEM - Intel ICH6 Modem
Intel ICH6 Modem at 0xe800, irq 177
Modem firmware information is in /proc/asound/card1/codec97#0/mc97#1-1
-----------------------------------------------
Extended modem ID: codec=1 LIN1
Lines in: /proc/asound/card1/codec97#0/mc97#1-1+regs
-------------------------------
0:7c = 5349 and 0:7e = 4c22
are translated from hexadecimal code into the modem chip identifier: SIL22
USB modem not detected by lsusb
For candidate card in slot 00:1e.3, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1e.3 8086:266d 1584:400c Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW
Modem interrupt assignment and sharing:
177: 0 IO-APIC-level Intel ICH6 Modem
--- Bootup diagnostics for card in PCI slot 00:1e.3 ----
ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 20 (level, low) -> IRQ 177
ACPI: PCI interrupt for device 0000:00:1e.3 disabled
PCI: Enabling device 0000:00:1e.3 (0000 -> 0001)
ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 20 (level, low) -> IRQ 177
PCI: Setting latency timer of device 0000:00:1e.3 to 64
The PCI slot 00:1e.3 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 Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
if help is needed.
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===
For candidate modem in PCI bus: 00:1e.3
Class 0703: 8086:266d Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW
Primary PCI_id 8086:266d
Subsystem PCI_id 1584:400c
Softmodem codec or chipset from diagnostics: SIL22, a Smartlink type
from Archives:
This is a NEW softmodem case! Please send the output ModemData.txt
to DISCUSS@xxxxxxxxxxxxx to enrich the Archive and help others!
If further assistance is not needed, please use email Subject:
New Case Only
-------------------------------------------
Lacking a dsp (digital signal processing) chip, the modem is a software
intensive or "softmodem" type. Its primary controller manages the traffic
with the CPU. But the software needed is specified in the Subsystem.
-----------------------------------------
Support type needed or chipset: slmodemd
An ALSA (Advanced Linux Sound Architecture) modem driver: snd-intel8x0m
provides Low Level support enabling contact with the modem hardware.
For all BUT Conexant chip soft modems (using hsfmodem software)
complementary High Level support is through a Smartlink utility: slmodemd
Download from http://linmodems.technion.ac.il/packages/smartlink/
the package SLMODEMD.gcc4.1.tar.gz having a compiled slmodemd. Unpack under Linux with:
$ tar zxf SLMODEMD.gcc4.1.tar.gz
and read instructions therein. But briefly, the modem is setup with command:
slmodemd -c YOUR_COUNTRY --alsa modem:1
reporting dynamic creation of ports:
/dev/ttySL0 --> /dev/pts/N , with N some number
Read Smartlink.txt and Modem/YourSystem.txt for follow through guidance.
----------------end Softmodem section --------------
Writing Intel.txt
Writing Smartlink.txt
============ end Smartlink section =====================
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.1.1
and the compiler used in kernel assembly: 4.1.1
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.1
linuc_headers base folder /lib/modules/2.6.18-1.2798.fc6/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 libc6-dev (and for Debian/Ubuntu, linux-libc-dev). The also required headers of package libc6 are commonly installed by default.
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:
-r-xr-xr-x 1 root root 312492 Dec 1 2006 /usr/sbin/pppd
In case of an "error 17" "serial loopback" problem, see:
http://phep2.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/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.
==========================================================
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link:
slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10 Jan 22 14:57 /dev/ttySL0 -> /dev/pts/1
Within /etc/udev/ files:
/etc/udev/rules.d/50-udev.rules:KERNEL=="modems/mwave*", NAME="%k", GROUP="uucp", MODE="0660"
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 --------
