Phantom,
All the guidance below is also applicable to your
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
0000:00:0a.0 8086:1040 8086:1000 Communication controller:
Intel Corporation 536EP Data Fax Modem
Read the attached Intel.txt
MarvS
scanModem maintainer
---------- Forwarded message ----------
From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>
Date: Mar 21, 2007 7:50 PM
Subject: Re: Modem not setup
To: Mark Stevenson <markstevenson@xxxxxxxxx>
Cc: discuss@xxxxxxxxxxxxx
Mark,
Drivers will have to be compiled for your modem
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:09.0 8086:1040 8086:1007 Communication controller: Intel Corporation 536EP Data Fax Modem
for which your System is prepared. Would you please run the modem
diagnostics under Microsoft and report the outputs to us. The reason
is that the
PCI_ID 8086:1040 modems typically are 537EP types. The difference is
that the 536ep do have a signal processing chip while for the 537EP
types all signal processing proceeds on the CPU. If the diagnostics
had reported
8086:1040 with a Subsystem 8086:1005 , then instructions for Intel537ep
support would have been output. Please run:
$ ./scanModem test 8086:1040 8086:1005
to output some additional guidance into the Modem/ folder
A support package for 537EP packages can also support the 536EP types.
So read the attached intel.txt and from
http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/
download the intel-537EP_secure-2.60.80.1_19_01_2007.tgz
and copy into your Linux partition. Unpack with:
$ tar zxf Intel*.tgz
To make movement easier set a symbolic link:
$ ln -s intel-537EP_secure-2.60.80.1_19_01_2007 intel
Then you can move into the folder with:
$ cd intel
Look around
$ ls
Files can be browsed with
$ less filename
or any text browser.
In sequence do:
$ make clean
$ make 537
If succcessful, the driver should be displayed by:
$ ls *.ko
If so complete the installation with:
$ su - root
# make install
Follow the guidance in Testing.txt for setting up a dialout.
DO report back if additional help is needed.
MarvS
On 3/21/07, Mark Stevenson <markstevenson@xxxxxxxxx> wrote:
This is the ModemData file from scanModem.
I do not know what to do from here.
I am running Mandriva 2007 free and kerrnel 2.6.17-5mdv
what do I need to do to get the modem working. Please remember I am new
to this so be gental in the directions. :)
Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List
Server.
Do use the following as the email Subject Line:
SomeName, YourCountry Mandriva Linux release 2007.0
(Official) for i586
Kernel 2.6.17-5mdv on an i686 / kernel 2.6.17-5mdv
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, Mandriva Linux release 2007.0 (Official) for i586
Kernel 2.6.17-5mdv on an i686 /
Linux version 2.6.17-5mdv (rtp@xxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.1
20060724 (prerelease) (4.1.1-3mdk)) #1 SMP Wed Sep 13 14:32:31 EDT 2006
scanModem update of: 2007_March_15
USB modem not detected by lsusb
Modem or host audio card candidates have firmware information:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:09.0 8086:1040 8086:1007 Communication controller: Intel Corporation
536EP Data Fax Modem
Modem interrupt assignment and sharing:
15: 31725 IO-APIC-edge ide1
--- Bootup diagnositcs for card in PCI slot 00:09.0 ----
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===
ALSAversion 1.0.12
The audio card is not a modem hosting type.
A modem was not detected among the PCI devices:
------------------------------------------------
00:09.0 Communication controller: Intel Corporation 536EP Data Fax Modem
00:0a.0 Multimedia video controller: Zoran Corporation ZR36057PQC Video
cutting chipset (rev 02)
00:11.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc.
VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II]
(rev 74)
01:00.0 VGA compatible controller: nVidia Corporation NV28 [GeForce4 Ti
4200 AGP 8x] (rev a1)
------------------------------------------------
with USB and bridge devices not displayed.
Please provide any independent information available on your modem.
If your modem is mounted on an ISA card, scanModem could not access it.
If an alternative boot into Microsoft windows can be done, do mouse
clicks on:
Start > Settings > Control Panel > Classical View (for Window XP) >
System
> Hardware > Device Manager > Modems > Click on the + > Modem. Double
click to
expand the graphic. Manufacturer information may be displayed. For
example, CXT
stands for Conexant. Click the Diagnostics Tab. Record any hardware ID
or vendor
and device information.
Next do the Query Modem and record the ATI specifications displayed such
as:
ATI3 - Agere SoftModem Version 2.1.22
ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
Try to identify the modem setup file, with name perhaps MODEM.INF.
If may contain chipset Vendor informaton.
Checking for audio+modem support in /proc/asound/pcm
00-01: VIA 8235 : VIA 8235 : playback 1 : capture 1
00-00: VIA 8235 : VIA 8235 : playback 4 : capture 1
For candidate modem in PCI bus: 00:09.0
Class 0780: 8086:1040 Communication controller: Intel Corporation
536EP Data Fax Modem
Primary PCI_id 8086:1040
Support type needed or chipset:
scanModem could not identify the Support Type needed from diagnosics or
archives.
If an alternative boot into Microsoft windows can be done, do mouse
clicks on:
Start > Settings > Control Panel > Classical View (for Window XP) >
System
> Hardware > Device Manager > Modems > Click on the + > Modem. Double
click to
expand the graphic. Manufacturer information may be displayed. For
example, CXT
stands for Conexant. Click the Diagnostics Tab. Record any hardware ID
or vendor
and device information.
Next do the Query Modem and record the ATI specifications displayed such
as:
ATI3 - Agere SoftModem Version 2.1.22
ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
Try to identify the modem setup file, with name perhaps MODEM.INF.
If may contain chipset Vendor informaton.
Writing Intel.txt
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
/dev/.udevdb
Versions adequately match for the compiler installed: 4.1.1
and the compiler used in kernel assembly: 4.1.1
Compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.1
kernel_headers base folder /lib/modules/2.6.17-5mdv/build
Checking pppd properties:
-rwsr-xr-t 1 root root 304536 Aug 9 2006 /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)
chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
chmod a+x /usr/sbin/pppd
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/YourSystem.txt concerning other COMM channels: eth0
Which can interfere with Browser naviagation.
Don't worry about the following, it is for the 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:
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 --------
Intel modems
==============================
Vendor=8086 is Intel, Inc. producing chipsets for 536EP host controller free (HCF) modems,
537 soft modems, several AC'97 softmodem controllers and HDA (High Definition Audio) cards.
For INTEL537 and INTEL536 chipset modems, the most current support is provided at:
http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/
In 2006, Intel appears to have ceased updates for Linux. But their offical
support packages can be accessed through:
http://developer.intel.com/design/modems/support/drivers.htm
The AC'97/CNR controllers of softmodems usually do NOT use Intel software.
Rather, the modem Subsystem determines the required software support.
Subsystems with Conexant chips require hsfmodem software from http:/www.linuxant.com
Other Subsytems are currently supported by Open Source ALSA drivers plus the slmodemd helper.
The HDA cards may host softmodem chipsets, through a different bridging then the AC'97 types.
Both Conexant chip and ALSA supported chipset types have been encountered.
For the 537 class softmodems, prior to software release 2.70.95.0,
there were distinct support packages:
PCI_id SubSystem_id Older_package Comment
-------------------------------------------------------------------------------
e159:0001 8086:0003 537 TJ320 v2.0 controller
8086:1080 8086:100[7,8,A,0] 537EP 8086:1080 AC'97 controller
8086:1040 8086:1005 537SP 8086:1080 AC'97 controller
various various 537AA_secure primary AC'97 controller
over si3054 chip with SIL25 codec
si == Silicon Instruments
various various 537EA primary CNR controller
over si3038 chip with INT65 codec
--------------------------------------------------------------------------------
But all are currently supported by a single Intel-537EP package
The 537AA and EA types may be alternatively be supported by an ALSA modem driver
and the Smartlink slmodemd.
Intel-536 chipset modems have an onboard DSP (digital signal processor) chip.
They may alternatively be served by the 537EP software, with added CPU burden.
A very detailed installation report cogent to 537 type modems is at:
http://linmodems.technion.ac.il/archive-fifth/msg00541.html
For Debian like distros, a modified install script is at:
http://members.lycos.co.uk/persianlinux/downloads/intel536EP/Intel536_inst_debian
Intel 536EP Modem Driver For Fedora Core 5
from volunteer maintainer Philippe Vouters
If you have a look at 537_boot in the driver's root directory, you will
notice the device is /dev/537.
$ export MODEM_TYPE=<your 537 family type modem>
$ make 537
From a root account, you:
$ make uninstall
$ make install
$ dmesg
If you do not find any error, do proceed with the $ efax test in the
previously sent attachment. You may also recall this $ efax command
adding to the end "-t <your phone number> 537_inst". If efax answers
busy, then it does sound good. If it answers "NO DIALTONE", then check
if the modem is actually connected to a working phone line and if yes
does send your $ dmesg along with $ efax output.
If this does not work, reply with the $ efax output along with $ dmesg
output.
Note that the hamcore software is initializing with your data after a
fresh install and the modem may not be immediately responding. However
if the $ efax command works, then it should be responding on a wvdial
command.
Please do provide me with the exact command output along with $ dmesg
data. Without these, it is difficult for me to pinpoint to the actual
problem. Be also aware that in the AT+GCI=3D wvdial AT command the 3D is
for France. Read the readme.txt in the driver's root directory to find
out the correct AT+GCI command according to your country.
Also providing you attempted to install a Fedora Core 2 537EP driver
onto your Fedora Core 5 distribution, please do clean up all files.
Yours truly,
Philippe
For FC5 users under FC5, Please read prior to rebuilding the 537EP driver.
http://linmodems.org/cgi-bin/ezmlm-cgi?1:mss:23914:200607:amjpfhgkifkbjmnibmjf
<NOTICE>
Intel claiming partial source and providing binaries built on a 32-bit
Pentium aware computer, you may use the drivers ONLYon a 32-bit Linux
and a Pentium instruction set compatible processor.
The driver code also handles a SMP configuration, as found in modern
multi-core processors, such as the Opteron and Xeon processors.
</NOTICE>
1/ 536EP and 537EP installation:
First read the readme.txt file located in the detarred created directory.
Make sure your computer has all the prerequisites (kernel-devel rpm installed
in particuliar) and your /usr/src/kernels/'uname -r'/include/linux/autoconf.h
does match your processor configuration. With this, check especially for:
$ grep SMP /usr/src/kernels/'uname -r'/include/linux/autoconf.h
for CONFIG_SMP defined whereas your computer only
contains a single processor.
If you have such a mismatch, reinstall your Linux distribution from scratch.
2/ From any account, you can under the detarred created directory:
$ make clean
$ make 536
or
$ make 537
For a 537 family modem, you may have to:
$ export MODEM_TYPE=<your actual modem type>
prior to the:
$ make 537
3/ Only from a root account, you can
$ make install
or
$ make uninstall
Check with:
$ dmesg > dmesg.txt Read the dmesg.txt looking for any driver's run-time problem.
The 536EP driver has proved to work fine with efax, hylafax, wvdial, KPPP.
The 537 driver has proved to work fine on SuSE 10.1.
4/ Checking the installation.
Assuming you have a 536EP modem, you should see the following:
$ ls -l /dev/modem
lrwxrwxrwx 1 root root 10 jan 22 12:37 /dev/modem ->
/dev/536ep
$ ls -l /dev/536*
crw-rw-rw- 1 root root 240, 1 jan 22 13:08 /dev/536ep
crw-rw---- 1 root root 240, 1 jan 22 13:08 /dev/536ep0
With such /dev/536ep protection modes, your modem is ready for use by
software from any account. Such software includes efax.
Your modem being connected to a phone line, it is advised to perform the
following quick and simple check:
$ efax -v ewinchmart
wait for efax waiting for a phone call. Then abort it with
CTRL-C.
Check that driver is properly working with:
$ dmesg
5/ Testing the modem for an Internet connection with wvdial:
from a root account, gedit /etc/wvdial.conf containing information such as:
[Modem0]
Modem = /dev/modem
Baud = 115200
SetVolume = 3
Dial Command = ATDT
Init1 = ATZ
Init2 = AT+GCI=3D
Init3 = ATM1L3
Carrier Check = no
FlowControl = CRTSCTS
#Stupid Mode = yes
[Dialer tiscali]
Username = <your ISP provided user name>
Password = <your ISP provided password>
Phone = <your ISP phone number>
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Inherits = Modem0
tiscali is my Internet provider. You may replace the
string [Dialer tiscali] by
[Dialer <your provider name>].
Do not attempt to set the Baud rate to a value greater
than 115,200 bps.
Stressing TCP/IP performance tests have shown that you
will not get more overall performance, and you may cause the modem
driver to lock your computer, forcing you to power down it.
Still from a root account, test the Internet connection with the command:
$ wvdial <the provider Dialer name> &
Check if the modem correctly dials.
Check if the ppp daemon is correctly synchronizing and authenticates
you with no problem.
Providing the ppp daemon does not work correctly, then
$ kill 1%
to abort wvdial. If ppp daemon is not working properly, you might remove
in the proposed /etc/wvdial.conf file the comment on the line:
#Stupid Mode = yes
and restart
$ wvdial <the provider Dialer name> &
Check using an Internet browser, such as Firefox, that you can display
pages from the Web.
kill the wvdial program with the command:
$ kill %1
6/ Configuring with KPPP.
KPPP on Fedora Core 4 Gnome desktop can be configured clicking on
Applications->Internet->KPPP and clicking on Configure and New.
Enter the data relative to your Internet account.
For configuring the modem, in the peripheral tab:
Enter your string as the modem name.
As the peripheral device, select in the listbox: /dev/modem.
For flow control, select hardware [CRTSCTS]
End of line CR/LF
Connection speed 115200.
Do not use a lock file and select the modem response delay to
120 secondes (maximum). Unselect "wait tone before dialing" and set
"active wait" to 50 secondes.
In the modem tab, clicking on modem commands, I set my 536EP modem to
the following:
Pre-initialization delay: 100
Init String 1: ATZ
Init String 2 : <empty>
Post-initialization delay : 156
Dialing speed : 100
Response after initialization: OK
No tone detection : ATX3
Dialing string : ATDT
"Connected" Response: CONNECT
Busy Response: BUSY
No Carrier Response: NO CARRIER
No tone response: NO DIALTONE
Hangup command: +++ATH
Hangup response: OK
Modem query command: ATA
Ring response: RING
Response "Response": CONNECT
DLP response: DIGITAL LINE DETECTED
Escape string: +++
Escape response: OK
Guard time: 255
Mute/low/high volume: M0L0 M1L1 M1L3
If you freshly installed the modem and with KPPP you interrogate it
it might happen the modem does not answer ATI commands the first time.
Retrying once again, makes the modem answer.
======= end Intel section =======
