Please help with:
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 Debian GNU/Linux 4.0 kernel 2.6.18-6-amd64
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=x86_64, Debian GNU/Linux 4.0
Linux version 2.6.18-6-amd64 (Debian 2.6.18.dfsg.1-18etch6)
(dannf@xxxxxxxxxx) (gcc version 4.1.2 20061115 (prerelease) (Debian
4.1.1-21)) #1 SMP Sat Jun 7 00:05:42 UTC 2008
scanModem update of: 2008_07_12
The modem symbolic link is /dev/modem -> ttySL0
Some modem drivers can only be used in 32 bit modem on x86_64 systems,
while some others are competent on x86_64 Systems. Cases are:
1) http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html
for the snd-hda-intel audio+modem driver. Also applicable to AC97
modem controllers.
In both cases, 32 bit libraries must be installed to support the
slmodemd helper having a precompiled 32 bit component.
2) For USB modems using the slusb.ko driver. 32 bit libraries must be
installed to support the slmodemd helper having a precompiled 32 bit
component
3) The hsfmodem and hcflinmodem drivers for Conexant chipsest modes
are x86_64 competent.
There are no blacklisted modem drivers in /etc/modprobe* files
USB modems not recognized
For candidate card in slot 09:0d.0, firmware information and bootup
diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
09:0d.0 1057:3052 1057:3020 Modem: Motorola
Unknown device 3052
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 09:0d.0 ----
ACPI: PCI Interrupt 0000:09:0d.0[A] -> GSI 16 (level, low) -> IRQ 169
0000:09:0d.0: ttyS2 at I/O 0x1008 (irq = 169) is a 16450
0000:09:0d.0: ttyS3 at I/O 0x1010 (irq = 169) is a 8250
Couldn't register serial port 0000:09:0d.0: -28
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 09:0d.0:
Modem chipset detected on
NAME="Modem: Motorola Unknown device 3052 "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=169
IDENT=slamr
For candidate modem in: 09:0d.0
0703 Modem: Motorola Unknown device 3052
Primary device ID: 1057:3052
Support type needed or chipset: slamr
----------------end Softmodem section --------------
1057:3052 has a Motorola chipset, poorly supported by Motorola itself
However Zello discovered that drivers written to support Smartlink
modems do support the 1057:3052 chipset!!
It sufficed to add 1057:3052 to the list of modem cards recognized by
the Smartlink slamr driver.
There is a ungrab-winmodem driver used in conjunction with slamr,
which must have 1057:3052
similarly added. See messages from Zello:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html
and Alvaro Aguirre about the ungrab-winmodem fix:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html
For general guidance on ungrab-winmodem + slamr usage, read the
DOCs/Smartlink.txt
The modem is supported by the Smartlink
plus the slmodemd helper utility. Read the
DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance.
For 2.6.18-6-amd64 compiling drivers is necessary. As of October 2007
the current packages at
http://linmodems.technion.ac.il/packages/smartlink/ are the
ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz
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.1.2
and the compiler used in kernel assembly: 4.1.2
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.1
linuc_headers base folder /lib/modules/2.6.18-6-amd64/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.
For Debian and some related distributions, a package
kernel-kbuild-2.6-18 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 settings of: /etc/ppp/options
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 eth1
Which can interfere with Browser naviagation.
Don't worry about the following, it is for 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
2008-07-16 06:19 /dev/modem -> ttySL0
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
/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/sl-modem-daemon.modutils:install slamr modprobe
--ignore-install ungrab-winmodem ; modprobe --ignore-install slamr;
test -e /dev/slamr0 || (/bin/mknod -m 660 /de
v/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0)
/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/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:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
