ReadMe file for the
Intel® 536EP V.92 chipset Linux driver
contents:
1. License
2. Release Notes
3. Installation
4. File Descriptions
5. International Users
6. Security issues
7. Compilation issues
a. Instructions for Debian Users
b. Kernel Source
8. What is the Hamregistry?
9. What's v92 and v44?
10. Known Bugs/Issues
11. Comments, ideas, problems, fixes
-------------------------------------------------------------------------------
1. LICENSE
IMPORTANT - read the file "LICENSE.txt" for the INTEL SOFTWARE LICENSE
AGREEMENT BEFORE COPYING, INSTALLING OR USING.
also note:
The serial driver open source code located in the directory "serialdrv"
is work covered under the GNU GENERAL PUBLIC LICENSE (GPL).
The "serialdrv" directory has the GPL in the file "GPL.txt".
-------------------------------------------------------------------------------
2. Release Notes [4.25]
20 November 2001:
This release supports 2.4.x kernels.
This release has currently be tested up to 2.4.12
This release is not compatible to 2.2.x kernels.
The 424 536EP corecode binary was compiled in Mandrake 8.0 with gcc
version 2.96
THE CURRENT LIST OF DISTRIBUTIONS THAT I HAVE
TESTED AND SEEN TO WORK WITH THIS
DRIVER ARE THE FOLLOWING:
* Mandrake 8.0 with Linux 536ep version 415 and kernel 2.4.3-20mdk
-------------------------------------------------------------------------------
3. INSTALLATION
Prerequisites:
1. root access
2. bash shell to run install scripts
3. a 536EP modem
4. kernel source headers for the kernel you are running
6 steps to install
1. login as ROOT
2. extract the archive into a directory with "tar -xvf <archivename>.tgz"
3. cd into the directory it created.
4. Type: make clean
5. Type: make 536ep
6. Type: make install-536ep
The installation script has been designed for the following distributions
release versions
mandrake-release
SuSE-release
redhat-release
debian_version (including Corel)
slackware-version
conectiva-version
bluepoint-release
Unknown distributions install modules and utilities but
will not install boot scripts!.
Please examine the 536ep-inst script if you have a different distribution.
The driver is split in two. A serial driver and core driver.
The core driver must be loaded first since the serial driver depends on it.
The serial driver registers itself as character device
major number 240, minor number 1.
The serial driver takes one argument right now, which is a number to
override the default major number if you need to.
ATTENTION: if the driver compiles but the script just wont work for you.
Here are the bare minimum steps to get your modem to work.
0. log in as root.
1. insmod -f 536epcore.o
2. insmod -f 536ep.o
2a. you can start "hamregistry" at this point if you wish.
3. rm /dev/536ep
4. mknod /dev/536ep c 240 1 (note "240" is the default, if it does not
work see what /proc/devices says 536ep's major number is)
5. ln -s /dev/536ep /dev/modem
6. start a comm application like minicom and use the modem.
7. see section 3 (International Users) for info on setting the correct
country settings.
-------------------------------------------------------------------------------
4. FILE DESCRIPTIONS
536ep-inst installation script to install 536ep modules and supporting files
files copied to /lib/modules/(kernel-version)/misc
536epcore.o driver core code module
536ep.o pseudo serial driver for 536ep, depends on 536epcore.o
files copied to /etc/rc.d/... (path differes per distribution)
536ep-boot boot scrip to start and stop 536ep modules
files copied to /usr/sbin
hamregistry hamregistry is the "registry" like tool that the modem uses to
get and store persistant data such as county info and profile strings.
files copied to /etc
linhamreg.bin file that stores the initial persistant data for modem.
-------------------------------------------------------------------------------
5. INTERNATIONAL USERS
hamregistry will store the last country setting you
set in the modem.
in minicom (or equivalent comm application)
the commmand to change country setting is "AT+GCI="
the command takes a t.35 country code in hexadecimal.
below is a list of currently supported t.35 country codes.
you can also put this "AT" command in the init string of
the comm application you are using.
if you are a CTR-21 country I think you should be able to
choose a CTR-21 country on the list and be ok. but
that's no guarantee.
The same goes for countries that are "USA" compatable.
(this table also exist in the source file wwh_dflt.c that
ships with the 536epcore driver)
country code t.35 code
---------------------------
USA 1 B5
ARG 54 07
AUS 61 09
AUT 43 0A
BEL 32 0F
BOL 591 14
BRA 55 16
CHE 41 A6
CHL 56 25
CHN 86 26
COL 57 27
CYP 357 2D
DEU 49 42
DNK 45 31
DOR 47 82
ECU 593 35
ESP 34 A0
FIN 358 3C
FRA 33 3D
GBR 44 B4
GRC 30 46
HKG 852 50
IDN 62 54
IND 91 53
IRL 753 57
ISL 354 52
ISR 972 58
ITA 39 59
JPN 81 00
KOR 82 61
LIE 423 68
LUX 352 69
MEX 52 73
MYS 60 C3
NLD 31 7B
NOR 47 82
NZL 64 7E
PAK 92 84
PAN 507 85
PER 51 88
PHL 63 89
PRT 351 8B
RUS 7 B8
SAU 966 98
SGP 65 9C
SWE 46 A5
THA 66 A9
TUR 90 AE
TWN 886 26
VNM 84 BC
-------------------------------------------------------------------------------
6. Security issues
the 536ep-inst and 536ep-boot file install the files and device nodes as
root for the owner and group.
this will cause problems for those who want to user the modem to dialout
using an account other than root.
In SuSE, "dialout" is the group used to install the files and device node.
This way, anyone belonging to the "dialout" group can use the modem to dialout.
(take a look at /etc/group)
I did not want the script to allow full access of the modem to everyone without
"root" knowing.
Edit the 536ep-boot and 536ep-inst scripts to fit your needs.
-------------------------------------------------------------------------------
6. Compile issues
a. this driver will now compile with the this path:
/lib/modules/<kernel version>/build/include
the 2.4.4+ kernels says to copy the /boot/vmlinuz.version.h
over to the kernel build path. I have the makefile do this
if this file exists. You must install the kernel source
code anyways. It should be on your distribution's CD.
-------------------------------------------------------------------------------
8. What is the Hamregistry?
The hamregistery is an application that stores data for the 536ep driver onto
the disk. hamregistry stores information from the driver that needs to
persist from reboot to reboot such as you current country setting.
The 536ep-inst install script and the 536ep-boot script start this utility
automatically for you.
If this tool is not present when the driver gets used your profile,
quickconnect, and current country setting will not be saved but the driver
should still work fine. The only step that would need to be done is to make
sure that the driver is set to the correct country with
at+gci= (see section 5)
-------------------------------------------------------------------------------
9. What's v92 and v44?
a. modem on hold: (ISP and your ISP dialer must also support this)
This will allow you to pause your ppp connection to answer an incoming
call. You will need call waiting, dialer, and ISP support for this to
work. When you are done with the call you can resume your ppp connection
without having to reconnect. The AT command set for this feature exist
in the driver.
b, pcm upstream: (ISP must also support this)
This will allow faster upload speeds.
c. quickconnect:
Once you make a call to a v92 modem, your phoneline characteristics are
stored. Whenever you make a new v92 connection it will use this data
to make the call negotiation quicker (approx 10 seconds).
d. v44: (ISP must also support this)
A better compression protocol than v42 which can give you better transfer
speeds.
-------------------------------------------------------------------------------
10. Known Bugs/Issues
a. If you see this message
"536ep:rs_open: DSP did not reset. try again or restart computer"
Disable "PNP OS" in your bios. There is a problem with the driver and
linux PNP. After a time, Linux PNP will disable the card and the driver
currently can not reenable itself.
b. Be aware that the build replaces your
/lib/module/<kernver>//build/include/linux/version.h file with
/boot/vmlinuz.version.h
(this is what Linus T. told me to do with a compiler error)
c. There may be an incompatibility with DevFS. The 536ep device may be located
in /dev/tts/536ep
instead of /dev/536ep. Be aware of this and link /dev/modem to the 536ep
device that corresponds to your setup.
d. I am investigating the "unbalance IRQ" warning at this time.
e. Currently there is a problem with the 536ep driver and SuSE 7.2 ppp
connections. I have been able to get ppp connection with bellsouth
by calling this bash script and wvdial config section:
------my script----------------------
#! /bin/sh
/usr/sbin/pppd -detach lock asyncmap 00000000 \
defaultroute debug /dev/modem 57600 \
ipparam ppp0 linkname ppp0 \
noauth \
connect "/usr/bin/wvdial --chat bellsouth"
------my /etc/wvdial.conf section ---
[Dialer bellsouth]
Modem = /dev/modem
Baud = 57600
Init1 = ATZ
Inti2 = ATQ0 V1 E1 S0=0 &C1 &D2
Dial Command = ATDT
Phone = 6859500
Username = myloginname
Password = mysecretpassword
#Ask Password = 1
Stupid Mode = 0
------------------
-------------------------------------------------------------------------------
12. Comments, ideas, problems, fixes:
please contact
Dorian S. Araneda
Product Engineer,
Intel Residential Access Division (RAD)
http://developer.intel.com/design/modems/
www.intel.com www.intc.com (ticker: INTC)
110 Horizon Dr., Suite 300, Raleigh, NC 27615
other resources and information on Linux controllerless modems can be found on
http://www.linmodems.org
and
http://linmodems.technion.ac.il
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.