
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 Ubuntu Linux users with Intel 536 and 537 chipsets the are driver 
 installation packages available, see:
   https://help.ubuntu.com/community/DialupModemHowto/Intel537EP
   https://help.ubuntu.com/community/DialupModemHowto/Intel536EP
   with suggestions for improvements to c.marcano@gmail.com

 For INTEL537 and INTEL536 chipset modems, updated support sources are at:
   http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/ 

After downloading the most recent package and copying to your Linux partition,
Compile and install with Root permission:
$ make clean
$ make 537
$ su - root
# make install
or under Ubuntu with:
$ sudo make install

 Formal Intel support for Linux appears to have ceased updates.  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 In particuliar, the
kernel-devel package for rpm using Distros.  Check that 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 =======
