Technical article 126810

How can I get a MultiTech MT5634ZPX-PCI V.92 Internal PCI Modem to work with SCO OpenServer 6.0.0?

OpenServer 6.0.0

Written · Last revised

Problem

How can I get a MultiTech MT5634ZPX-PCI V.92 Internal PCI Modem to work with SCO OpenServer 6.0.0?

HARDWARE: MultiTech MT5634ZPX-PCI V.92 Internal PCI Modem

Solution

This is what you need to do in order to get the MultiTech MT5634ZPX-PCI V.92 Internal PCI Modem to work with SCO OpenServer 6.0.0:

In our example, we will communicate with the MultiTech MT5634ZPX-PCI Modem via COM3 (We want to keep COM1 & COM2 free for other use).

1- Make sure that you have the following installed first:

OpenServer 6 Maintenance Pack 2
http://www.sco.com/support/update/download/release.php?rid=133
oss706c supplement
http://www.sco.com/support/update/download/release.php?rid=238

The MultiTech MT5634ZPX-PCI Modem is plugged in a free PCI slot. Recommended a 32bit PCI slot. If non available, then a 64bit PCI slot.

2- With the modem installed, boot up the server and find out which resmgr key is the MultiTech MT5634ZPX PCI Modem allocated to:

# hw -v -r pci
(In our installation, we got this output: )
resmgr key   =    51
vendor id    =    0x11c1=AT&T MICROELECTRONICS
device id    =    0x0480
combining the vendor & device id == 0x11C10480
Then run "resmgr | grep 0x11C10480" to find out the IO address for
this PCI-Modem:
# resmgr | grep 0x11C10480

51 - - - 4 25 4800 48ff f9504000 f95040ff - - 4 0x11C10480 0x8007 1 - 20

the output confirms the resmgr key 51.

We see that the IRQ and IOstart address are "25" and "4800". Note this down.

3-
Edit the /etc/conf/pack.d/sync/space.c file
# cd /etc/conf/pack.d/asyc
# vi space.c

Since we will now communicate with the PCI Modem via COM3 and use IRQ 25, change the following line that referes to COM3 from:

{ 0x3e8, 5, NOTYPE, NOSTATE, 0, 0,(struct termios *)0, (struct termiox *)0, 0},

TO

{ 0x4800, 25, NOTYPE, NOSTATE, 8, 16,(struct termios *)0, (struct termiox *)0, 0},

Save the file and re-link the kernel:

# /etc/conf/bin/idbuild -B
Reboot.

4- Enter DCU and do the following to add a COM3 to the res-manager:

# dcu

--> Hardware Device configuration Page down and courser down until you reach the line that says:

Y    Unknown    25    4800    48ff    f9504000   f95040ff

Press F2 to change the "Y" to "N" then F10.

--> software Device Drivers --> Communication Card At "asyc" list press F5 for new.

and add the following values:
	Driver Name : asyc
	Device Name : Any
   ** UNIT        : 20
	IPL 	    : 9
   ** ITYPE       : 4
   ** IRQ 	    : 5
   ** IOStart     : d400
   ** IOEnd       : d4ff
   ** MemStart    : ef8eff00
   ** MemEnd      : ef8effff
	DMA         : -1
	BindCPU     :

Note: ** are the values added new. For IRQ, we added 5 and not 25, this is because DCU only allows values between 0-15. We shall later change the value from 5 to 25 in the command line.

Then press F10 for Apply & Return. then ENTER.

--> Return to DCU Main Menu --> Apply changes & Exit DCU

You will get a WARNING message telling you you need to reboot for the changes to take effect.

Now to change the IRQ from 5 to 25:

# resmgr | grep asyc
16 asyc 1 9 4 4 3f8 3ff - - - - 1 - - - 2 -
17 asyc 1 9 4 3 2f8 2ff - - - - 1 - - - 2 -
81 asyc 20 9 4 5 4800 48ff f9504000 f95040ff -1 - 0 - - - - -

The new added COM3 (asyc) has Key 81. To change the IRQ value, run the following commands:

# resmgr -k 81 -p "IRQ" -v "25"
# /etc/conf/bin/idconfupdate -f
Reboot the server.

5- After reboot, verify that the modem is recognised correclty by running:

# resmgr | grep 4800 <-- IO start address for COM3
51 asyc 20 9 4 25 4800 48ff f9504000 f95040ff -1 - 0
   - - - - -
52 - - - 4 25 4800 48ff f9504000 f95040ff - - 4 0x11C10480
   0x8007 1 - 20

regmgr Key 51 is COM3 (third asyc) and Key 52 is the MultiTech MT5634ZPX PCI Modem associated to COM3.

Note: These resmgr Keys will be different from system to system.

to test:
# stty -a </dev/tty3a

you should get the the following output:

speed 9600 baud; intr = DEL; quit = ^|; erase = ^h; kill = ^u; eof = ^d; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^q; stop = ^s; susp = ^z; dsusp = <undef>; rprnt = ^r; flush = ^o; werase = ^w; lnext = ^v; -parenb -parodd -parext cs8 -cstopb -hupcl cread clocal -loblk -ignbrk brkint -inpck -ignpar -parmrk istrip -inlcr -igncr icrnl - iuclc ixon -ixany -ixoff -imaxbel opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel tab3 isig icanon -xcase echo -echoe echok -echonl -noflsh -tostop -echoctl -echoprt -echoke -defecho -flusho -pendin -iexten -rtsxoff -ctsxon -dtrxoff -cdxon -isxoff xcibrg rcibrg tsetcoff rsetcoff -isscancode -xscancode

This output confirms that the OSR6 can connected to COM3.

6- Configure a Modem in the scoadmin modem manager.

# scoadmin modem

Do a manual configuration and choose the following from the lists:

Modem Vendor: MultiTech Systems
Modem Model:  MultiTech MT5634ZPX-PCI
Modem Port:   tty3A
Line Speed:   57600
Answer mode:  Yes or No
Save and exit.

then test the connect to modem from OSR6:

# cu -l tty3A dir
you should get a "CONNECTED".

You can now issue the "AT" modem commands. Please refer to the MultiTech MT5634ZPX-PCI manual for details on "AT" commands.

With this test, it confirms that OSr6 can connect to the modem and ready for dialout and diailin.

See also

Configuring modems
http://osr600doc.xinuos.com/en/HW_modem/CONTENTS.html
TA# 126671 - How can I get a MultiTech MT5634ZPX-PCI PCI Modem
             and Networking to work with SCO OpenServer 6.0.0
             on a DELL SC440

TA# 126812 - How can I get a MultiTech MT5634ZPX-PCI V.92 Internal PCI Modem to work with SCO UnixWare 7.1.4?

From the Xinuos technical article database, record 126810. Reproduced with permission. The original is at www.sco.com/ta/126810, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.