Antonio Olivares wrote:
ddcc,
Please send us ModemData.txt, that way you'd be sure that your
modem/is/could be or is not supported.
Regards,
Antonio
After this, and knowing that your modem is not supported then you can look
at
the output of
$ cat Modem/DOCs/InfoGeneral.txt
which summarizes a bit which your alternatives are.
On 5/1/09, ddcc <d.c.ddcc@xxxxxxxxx> wrote:
I have an old Intel HaM modem, and according to scanModem is no longer
supported in the 2.6.xx kernels. I would like to confirm that there is
absolutely no way to get it working without downgrading my kernel,
meaning that there are no 3rd 'hacks' or other patches available? In
that case, what inexpensive (preferably internal) fax modem that
supports Linux could you guys recommended?
Thanks,
ddcc
It is an old Ambient MD5628D-L-A modem; I've attached ModemData.txt
Thanks,
ddcc
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.26-2-486
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.26-2-486 (Debian 2.6.26-15) (dannf@xxxxxxxxxx) (gcc
version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 Thu Mar 26
00:13:41 UTC 2009
scanModem update of: 2009_04_28
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
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 00:09.0, firmware information and bootup
diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:09.0 1813:4000 Communication controller: Ambient
Technologies Inc HaM controllerless modem
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 00:09.0 ----
PCIbus=00:09.0
00:09.0 Communication controller: Ambient Technologies Inc HaM
controllerless modem (rev 02)
Flags: medium devsel, IRQ 11
Memory at ec000000 (32-bit, non-prefetchable) [size=4K]
I/O ports at e400 [size=256]
Capabilities: [60] Power Management version 2
=== Finished firmware and bootup diagnostics, next deducing cogent software.
===
Predictive diagnostics for card in bus 00:09.0:
Modem chipset detected on
NAME="Communication controller: Ambient Technologies Inc HaM controllerless
modem "
CLASS=0780
PCIDEV=1813:4000
SUBSYS=none
IRQ=11
IDENT=AmbientTech
For candidate modem in: 00:09.0
0780 Communication controller: Ambient Technologies Inc HaM controllerless
modem
Primary device ID: 1813:4000
Support type needed or chipset: AmbientTech
Under Linux 2.6.n kernels, the chipset is NOT SUPPORTED . Read
DOCs/InfoGeneral.txt about alternatives.
Vendor=1813 Ambient Tech was acquired by Intel with its HaM (Host assisted
Modem) chipsets.
There is no support under 2.6.n kernels!!
Intel-v92ham-453.tgz 2.4.n kernels was the FINAL 2.4.n update for HaM
modems, available at:
http://linmodems.technion.ac.il/packages/Intel/ham/
http://developer.intel.com/design/modems/support/drivers.htm
It is NOT functional when compiled under 2.6.n kernels.
But under the 2.4.nn kernels, all HaM chipsets were supported,
with a single EXCEPTION: the odd PCI_ID 1813:4100 modems. For the
explanation, see message:
http://linmodems.org/cgi-bin/ezmlm-cgi?1:mss:9448:200210:fbhcoigfcimgkjdedjad
====== end AmbientTech 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.3
and the compiler used in kernel assembly: 4.1.3
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.1
linuc_headers base folder /lib/modules/2.6.26-2-486/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.
For Debian and some related distributions, a package kernel-kbuild-2.6-26
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
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/80-drivers.rules:SUBSYSTEM=="atm",
RUN+="dsl-modem.agent"
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 --------
For Debian users, the linux-headers-2.6.26-2-486.deb can be used instead of
kernel-source/
