Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List Server.
Do use the following as the email Subject Line:
SomeName, YourCountry Ubuntu 7.04 kernel 2.6.20-15-generic
This will alert cogent experts, and distinguish cases in the Archives.
YourCountry will enable Country Code guidance.
Occassionally responses are blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org .
Local Linux experts can be found through:
http://www.linux.org/groups/index.html
-------------------------- System information ----------------------------
CPU=i686, Ubuntu 7.04
Linux version 2.6.20-15-generic (root@palmer) (gcc version 4.1.2
(Ubuntu 4.1.2-0ubuntu4)) #2 SMP Sun Apr 15 07:36:31 UTC 2007
scanModem update of: 2007_May_11
The modem symbolic link is /dev/modem -> ttySL0
ALSAversion 1.0.13
USB modem not detected by lsusb
Modem or host audio card candidates have firmware information:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1e.3 8086:266d 1179:0001 Modem: Intel Corporation
82801FB/FBM/FR/FW/FRW
Modem interrupt assignment and sharing:
20: 624 IO-APIC-fasteoi ohci1394, eth0
--- Bootup diagnositcs for card in PCI slot 00:1e.3 ----
[ 5.853594] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 20 (level,
low) -> IRQ 20
[ 6.893429] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 20 (level,
low) -> IRQ 20
[ 6.893438] ACPI: PCI interrupt for device 0000:00:1e.3 disabled
[ 19.208000] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 20 (level,
low) -> IRQ 20
[ 19.732000] PCI: Setting latency timer of device 0000:00:1e.3 to 64
[ 19.756000] ACPI: PCI interrupt for device 0000:00:1e.3 disabled
[ 19.756000] hsfich: probe of 0000:00:1e.3 failed with error -5
[ 19.860000] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 20 (level,
low) -> IRQ 20
[ 19.860000] PCI: Setting latency timer of device 0000:00:1e.3 to 64
[ 19.864000] ACPI: PCI interrupt for device 0000:00:1e.3 disabled
[ 28.684000] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 20 (level,
low) -> IRQ 20
[ 28.684000] PCI: Setting latency timer of device 0000:00:1e.3 to 64
[ 28.688000] ACPI: PCI interrupt for device 0000:00:1e.3 disabled
[ 28.752000] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 20 (level,
low) -> IRQ 20
[ 28.752000] PCI: Setting latency timer of device 0000:00:1e.3 to 64
[ 28.756000] ACPI: PCI interrupt for device 0000:00:1e.3 disabled
[ 596.352000] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 20 (level,
low) -> IRQ 20
[ 596.352000] PCI: Setting latency timer of device 0000:00:1e.3 to 64
[ 596.352000] ACPI: PCI interrupt for device 0000:00:1e.3 disabled
[ 649.880000] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 20 (level,
low) -> IRQ 20
[ 649.880000] PCI: Setting latency timer of device 0000:00:1e.3 to 64
[ 649.884000] ACPI: PCI interrupt for device 0000:00:1e.3 disabled
[ 649.948000] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 20 (level,
low) -> IRQ 20
[ 649.948000] PCI: Setting latency timer of device 0000:00:1e.3 to 64
[ 649.952000] ACPI: PCI interrupt for device 0000:00:1e.3 disabled
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 ===
Bootup diagnostic [ 19.732000] HSF: ERROR: SILICON Laboratories or
LUCENT AC97 modem detected!<3>
[ 19.732000] HSF: ERROR: This driver only supports CONEXANT devices<3>
[ 19.732000] HSF: ERROR: not a Conexant modem<3>
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 1179:0001
Softmodem codec or Vendor from diagnostics:
from Archives: SIL27, an AgereSystems type.
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-1.0.13.tar.gz having a compiled slmodemd. Unpack
under Linux with:
$ tar zxf SLMODEMD-1.0.13.tar.gz
and read instructions therein. But briefly, the modem is setup with command:
sudo 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.
The diagnostic outputs for this softmodem section have their raw information in
folders and text files under /proc/asound/ which you can browse. The information
is from files:
/proc/asound/pcm
-------------------------------
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
/proc/asound/modules
-------------------------------
0 snd_intel8x0
and from the command:
aplay -l | grep -i modem
----------------end Softmodem section --------------
Writing Intel.txt
The modem is supported by the Smartlink slamr driver
plus the slmodemd helper utility. Read the
Smartlink.txt and Modem/YourSystem.txt for follow through guidance.
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.2
and the compiler used in kernel assembly: 4.1.2
Kernel-header resources needed for compiling are not manifestly ready!
If compiling is necessary packages must be installed, providing:
linux-headers-2.6.20-15-generic
Compressed files at: /usr/src/sl-modem.tar.bz2
Checking pppd properties:
-rwsr-xr-- 1 root dip 269224 2007-04-04 21:41 /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)
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
replacedefaultroute
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 eth1
eth0:avah eth1:avah
Which can interfere with Browser naviagation.
Don't worry about the following, it is for the experts
should trouble shooting be necessary.
==========================================================
# start/stop the daemon when the USB modem is connected
KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link: lrwxrwxrwx 1 root root 6
2007-06-16 02:40 /dev/modem -> ttySL0
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
/etc/udev/rules.d/00-hsf.rules:KERNEL=="ttySHSF0", SYMLINK="modem"
/etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon
when the USB modem is connected
/etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*",
GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
/etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB
modem is connected
/etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*",
GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
Within /etc/modprobe.conf files:
/etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to
blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
/etc/modprobe.d/sl-modem-daemon.modutils:install slamr modprobe
--ignore-install ungrab-winmodem ; modprobe --ignore-install slamr;
test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0
2>/dev/null && chgrp dialout /dev/slamr0)
/etc/modprobe.d/hsf.conflicts:install snd-via82xx-modem /bin/true #
temporarily disabled by hsf - conflicts with hsfmc97via
/etc/modprobe.d/hsf.conflicts:install snd-atiixp-modem /bin/true #
temporarily disabled by hsf - conflicts with hsfmc97ati
/etc/modprobe.d/hsf:alias /dev/modem /dev/ttySHSF
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
Within any ancient /etc/devfs files:
/etc/devfs/conf.d/hsf.conf:LOOKUP ^(ttySHSF[0-9]|modem$) EXECUTE
nice /sbin/modprobe /dev/ttySHSF
/etc/devfs/conf.d/hsf.conf:REGISTER ^ttySHSF0$ CFUNCTION GLOBAL
symlink $devname modem
/etc/devfs/conf.d/hsf.conf:UNREGISTER ^ttySHSF0$ CFUNCTION GLOBAL
unlink modem
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
I'm still confused as to which driver I should be installing.
