Hello, I am new to Ubuntu and am trying to set up my fax modem. I
have installed the drivers from here:
http://groups.google.com/group/ubuntu-modems/web/intel536ep-maverick_1-Philippe.Vouters_i386.deb
and when I run wvdialconf I get:
smcink@ubuntu:~$ wvdialconf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
WvModem<*1>: Cannot set information for serial port.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
WvModem<*1>: Cannot set information for serial port.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S2 S3
Sorry, no modem was detected! Is it in use by another program?
--
What should I do next?
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.35-25-generic
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, Ubuntu , ALSA_version=1.0.23
Linux version 2.6.35-25-generic (buildd@palmer) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #44-Ubuntu SMP Fri Jan 21 17:40:48 UTC 2011
scanModem update of: 2011_02_04
The modem symbolic link is /dev/modem -> ttySL0
Distrib_ID=Ubuntu
DistribCodeName=maverick
AptRepositoryStem=http://us.archive.ubuntu.com/ubuntu/
The dkms driver upgrade utilities are installed,
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
slamr
slamrTest=
Attached USB devices are:
ID 0430:0005 Sun Microsystems, Inc. Type 6 Keyboard
If a cellphone is not detected, see http://ubuntuforums.org/archive/index.php/t-878554.html
A sample report is: http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html
If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@xxxxxxxxxxxxx
Candidate PCI devices with modem chips are:
02:0b.0 Communication controller: Intel Corporation 536EP Data Fax Modem
High Definition Audio cards can host modem chips.
For candidate card in slot 02:0b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
02:0b.0 8086:1040 8086:1000 Communication controller: Intel Corporation 536EP Data Fax Modem
Modem interrupt assignment and sharing:
9: 0 IO-APIC-fasteoi acpi
--- Bootup diagnostics for card in PCI slot 02:0b.0 ----
[ 0.110366] pci 0000:02:0b.0: reg 10: [mem 0xed000000-0xed3fffff]
[ 0.110424] pci 0000:02:0b.0: supports D2
[ 0.110429] pci 0000:02:0b.0: PME# supported from D2 D3hot D3cold
[ 0.110436] pci 0000:02:0b.0: PME# disabled
The PCI slot 02:0b.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.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 02:0b.0:
Modem chipset detected on
NAME="Communication controller: Intel Corporation 536EP Data Fax Modem"
CLASS=0780
PCIDEV=8086:1040
SUBSYS=8086:1000
IRQ=9
IDENT=INTEL536EP
For candidate modem in: 02:0b.0
0780 Communication controller: Intel Corporation 536EP Data Fax Modem
Primary device ID: 8086:1040
Support type needed or chipset: INTEL536EP
Since 2006, Intel appears to have ceased its modem code updates for Linux.
The outdated official Intel support packages can be accessed through:
http://developer.intel.com/design/modems/support/drivers.htm
Beneficially, Philippe Vouters has been provided updates as the Linux kernel evolves.
But intensive personal support is not feasible, see: http://archives.linmodems.org/24939
The code for the INTEL537 and INTEL536 chipset modems is now at:
http://vouters.dyndns.org/Intel/ , previously http://x9000.fr
Copies are also stored at:
http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/
For Ubuntu Linux users with Intel 536 and 537 chipsets, there are driver
installation packages available thru http://groups.google.com/group/ubuntu-modems
Read DOCs/Intel.txt and Modem/DOCs/YourSystem.txt for follow through guidance.
Writing DOCs/Intel.txt
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.4.5
and the compiler used in kernel assembly: 4.4.5
linux-headers-2.6.35-25-generic resources needed for compiling are not manifestly ready!
If compiling is necessary packages must be installed, providing:
linux-headers-2.6.35-25-generic
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-x 1 root dip 273248 2010-07-09 10:41 /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)
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
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
For guidance on FAX usage, get from http://linmodems.technion.ac.il/packages/ get faxing.tar.gz
It has samples for a modem using port /dev/ttySL0, which must be changed to match your modem's port.
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: lrwxrwxrwx 1 root root 6 2011-02-25 12:03 /dev/modem -> ttySL0
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
/etc/udev/rules.d/10-intel536maverick.rules:KERNEL=="536ep*", SYMLINK+="modem", MODE="0666", OWNER="root", GROUP="dialout"
Within /etc/modprobe.conf files:
/etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem
/etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
/etc/modprobe.d/sl-modem.conf:install slamr /sbin/modprobe -qb ungrab-winmodem; /sbin/modprobe --ignore-install slamr; test -e /dev/slamr0 && (chmod 660 /dev/slamr0 && chgrp dialout /dev/slamr0) || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0)
/etc/modprobe.d/sl-modem.conf:install slusb /sbin/modprobe -qb ungrab-winmodem; /sbin/modprobe --ignore-install slusb; test -e /dev/slusb0 && (chmod 660 /dev/slusb0 && chgrp dialout /dev/slusb0) || (/bin/mknod -m 660 /dev/slusb0 c 243 0 2>/dev/null && chgrp dialout /dev/slusb0)
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
