Hi.
My Modem is
DataSheen 562is DataFax Modem
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 _____ _
| __
| |__) |_ _ _ __ ___ ___ __
| ___/ _' | '__/ __|
| | | (_| | |
|_|
Parsix GNU/Linux 1.0r0 (Ramon) kernel 2.6.23-parsix-16
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, _____ _
| __
| |__) |_ _ _ __ ___ ___ __
| ___/ _' | '__/ __|
| | | (_| | |
|_|
Parsix GNU/Linux 1.0r0 (Ramon)
Linux version 2.6.23-parsix-16 (root@memphis-mobile) (gcc version 4.2.3 20071123 (prerelease) (Debian 4.2.2-4)) #1 SMP PREEMPT Thu Jan 24 04:57:56 UTC 2008
scanModem update of: 2009_02_21
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 slamr snd_hda_intel
slamrTest=
If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@xxxxxxxxxxxxx
For candidate card in slot 03:00.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
03:00.0 2003:8800 1801:2800 Modem: Smart Link Ltd. Unknown device 8800
Modem interrupt assignment and sharing:
18: 0 0 IO-APIC-fasteoi SL2800
--- Bootup diagnostics for card in PCI slot 03:00.0 ----
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 20 (level, low) -> IRQ 18
ACPI: PCI interrupt for device 0000:03:00.0 disabled
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 20 (level, low) -> IRQ 18
PM: Writing back config space on device 0000:03:00.0 at offset 1 (was 2900002, writing 2900006)
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 20 (level, low) -> IRQ 18
The PCI slot 03:00.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:27d8 1458:a002 Audio device: Intel Corporation 82801G
Modem interrupt assignment and sharing:
16: 1188098 1 IO-APIC-fasteoi uhci_hcd:usb5, 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
ACPI: PCI interrupt for device 0000:00:1b.0 disabled
PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100002)
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
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.
The primary PCI & Subsystem pair is novel and
the Subsystem ID is not alone decisive for modem codec identification.
===== 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.14
The modem cards detected by "aplay -l" are: None
The /proc/asound/pcm file reports:
-----------------------
00-02: ALC883 Analog : ALC883 Analog : capture 2
00-01: ALC883 Digital : ALC883 Digital : playback 1 : capture 1
00-00: ALC883 Analog : ALC883 Analog : playback 1 : capture 2
about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xe2280000 irq 16
PCI slot 00:1b.0 has a High Definition Audio Card
The drivers are in the kernel modules tree at:
/lib/modules/2.6.23-parsix-16/kernel/sound/pci/hda/snd-hda-intel.ko
UNEXPECTED HDA diagnostic outcome.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 03:00.0:
Modem chipset detected on
NAME="Modem: Smart Link Ltd. Unknown device 8800 "
CLASS=0703
PCIDEV=2003:8800
SUBSYS=1801:2800
IRQ=18
SOFT=2003:8800.MC97
NEW=1801:2800
IDENT=mc97
For candidate modem in: 03:00.0
0703 Modem: Smart Link Ltd. Unknown device 8800
Primary device ID: 2003:8800
Subsystem PCI_id 1801:2800
Softmodem codec or chipset from diagnostics:
from Archives:
The soft modem is in the ac97/mc97 category. However the diagnostics were not effective,
and an archival record for is lacking for the modem codec of pair:
2003:8800 1801:2800
Try to acquire more information by running the modem diagnostics under a Microsoft boot,
as described in SoftModem.txt
----------------end Softmodem section --------------
Writing DOCs/Intel.txt
Predictive diagnostics for card in bus 00:1b.0:
Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801G "
CLASS=0403
PCIDEV=8086:27d8
SUBSYS=1458:a002
IRQ=16
HDA=8086:27d8
SOFT=8086:27d8.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:27d8.
If another modem card is present, then most likely 8086:27d8 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:27d8, 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 82801G
Primary device ID: 8086:27d8
Subsystem PCI_id 1458:a002
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.2.tar.gz from:
http://linmodems.technion.ac.il/packages/smartlink/
----------------end Softmodem section --------------
Writing DOCs/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.2.3
and the compiler used in kernel assembly: 4.2.3
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.2
linuc_headers base folder /lib/modules/2.6.23-parsix-16/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.
Compressed files at: /usr/src/linux-wlan-ng.tar.bz2
For Debian and some related distributions, a package kernel-kbuild-2.6-23 may be needed to support driver compiling.
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 260920 2007-04-14 04:29 /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
asyncmap 0
auth
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
Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================
#
# UDEV rule for ltmodem
# creates symlink /dev/modem to /dev/ttyLT?, and takes care of permissions
KERNEL=="ttyLTM[0-9]", MODE="0660", GROUP="dialout", SYMLINK="modem"
# 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:
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
/etc/udev/ltmodem.rules:# UDEV rule for ltmodem
/etc/udev/ltmodem.rules:# creates symlink /dev/modem to /dev/ttyLT?, and takes care of permissions
/etc/udev/ltmodem.rules:KERNEL=="ttyLTM[0-9]", MODE="0660", GROUP="dialout", SYMLINK="modem"
/etc/udev/rules.d/ltmodem.rules:# UDEV rule for ltmodem
/etc/udev/rules.d/ltmodem.rules:# creates symlink /dev/modem to /dev/ttyLT?, and takes care of permissions
/etc/udev/rules.d/ltmodem.rules:KERNEL=="ttyLTM[0-9]", MODE="0660", GROUP="dialout", SYMLINK="modem"
/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/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
/etc/modprobe.d/alsa-base-blacklist:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/alsa-base-blacklist:# blacklist snd-atiixp-modem
/etc/modprobe.d/alsa-base-blacklist:# 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)
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
/etc/modules:ungrab_winmodem
/etc/modules-2.6.23-parsix-16:ungrab_winmodem
--------- end modem support lines --------
