Technical article 126678

How can I get a MultiTech MT5634ZPX-PCI PCI Modem and Networking to work with SCO OpenServer 6.0.0 on a DELL SC440.

OpenServer 6.0.0

Written · Last revised

Problem

I have successfully installed SCO OpenServer 6.0.0 + MP2 on a DELL SC440.But I can't get the onboard Broadcom BCM5754 and a MultiTech MT5634ZPX-PCI PCI Modem to work with OSR6.

HARDWARE: DELL SC440
          Broadcom BCM5751 PCI-Express
          MultiTech MT5634ZPX-PCI PCI Modem

Cause

For the onboard Broadcom BCM5754 NIC, there is no SCO OpenServer 6 supported driver.

You need to plug-in a supported OSR6 NIC. In our example, we used the Broadcom BCM5751 PCI-express NIC.

Regarding the MultiTech MT5634ZPX-PCI PCI Modem, look at the SOLUTION section.

Solution

This is what you need to do in order to get the Broadcom BCM5751 PCI-Express and the MultiTech MT5634ZPX-PCI PCI Modem to work on the DELL SC440:

1- Make sure that in the DELL SC440 BIOS, the onboard Broadcom NIC BCM5754 is disabled.

2- Plug the Broadcom BCM5751 PCI-E card into PCI-express slot 1 (the top one with a small slot).

and plug the MultuTech MT5634ZPX-PCI Modem into PCI slot 5 (the bottom one, a 32-bit PCI slot).

3- Boot the DELL SC440 and install SCO OSR6 using the re-cut March 2006 OSR6 CD-1 install media:

http://www.sco.com/support/update/download/release.php?rid=161

4- Installation will detect the Broadcom BCM5751 PCI-E, configure it with the TCP/IP infos....etc.

continue installation till the end and reboot.

5-
Install OSR6 MP2 and then reboot.

6- Install OSR6 Patch OSS706b, the OpenServer 6 Maintenance Pack 2 Supplement (HIGHLY RECOMMENDED):

http://www.sco.com/support/update/download/release.php?rid=213
and then reboot.
WARNING: DO NOT INSTALL THE LATEST OSR6 NETWORK DRIVERS PACKAGE
         "nd.806d" OR ANY EARLIER RELEASES, THIS WILL CAUSE SOME
         ISSUES WITH INTERRUPT SHARING BETWEEN THE NIC CARD AND
         THE MULTITECH PCI-MODEM.
7-
find out which resmgr key is the Multi-Tech PCI Modem allocated to:
# hw -v -r pci
(In my installation, I got this output: )
resmgr key      =       32
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

32 - - - 4 16 d400 d4ff ef8eff00 ef8effff - - 4 0x11C10480 0x8007 5 - 5

the output confirms the resmgr key 32.

We see that the IRQ and IOstart address are "16" and "d400". Note this down.

8-
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 COM2 and use IRQ3, change the following line that referes to COM2 from:

{ 0x2f8, 3, NOTYPE, NOSTATE, 8, 16,(struct termios *)0, (struct termiox *)0, 0},

TO

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

NOTE: You only need to change the IO adress and IRQ.

Save the file and re-link the kernel:

# /etc/conf/bin/idbuild
Reboot.

9- Enter DCU and do the following to add a COM2 to the res-manager:

# dcu

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

Y    Unknown    16    d400    d4ff    ef8eff00   ef8effff

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 16, this is because DCU only allows values between 0-15. We shall later change the value from 5 to 16 from 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 16:

# resmgr | grep asyc
16 asyc 1 9 4 4 3f8 3ff - - - - 1 - - - 2 -
46 asyc 20 9 1 5 d400 d4ff ef8eff00 ef8effff -1 - 0 - - -
   2 -

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

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

10- After reboot, resmgr should now return the following output:

# resmgr

46 asyc 20 9 1 16 d400 d4ff ef8eff00 ef8effff -1 - 0 - - - 2 - 47 - - - 4 16 d400 d4ff ef8eff00 ef8effff - - 4 0x11C10480 0x8007 5 - 5

regmgr Key 46 is COM2 (second asyc).

to test:

run "scoadmin serial" or "mkdev serial", you should get the following serial ports listed:

Description        Unit Ports  IRQ  I/O addr
------------       ---- -----  ---  --------
Standard            1    1      4    3F8
Standard            2    1      16    D400
Exit Serial Manager.
then run
# stty -a </dev/tty2a -- 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 COM2.

11- 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:   tty2A
Line Speed:   57600
Save and exit.

then test the connect to modem from OSR6:

# cu -l tty2A 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.

12- The generic "bcme" driver for the Broadcom NIC cards that is part of the base OSr6 is release 7.5.22, which is bit outdated compared to the actual one in Broadcom website, release 9.7.0.

Therefore download the "bmce" driver ver. 9.7.0 from Broadcom website:

        http://www.broadcom.com/support/ethernet_nic/netxtreme_server.php
http://www.broadcom.com/support/ethernet_nic/driver-sla.php?driver=570x-SCO-UnixWare
Or a later one.

unpack the driver under /tmp. The package is bcme-9.7.0.pkg

first, you need to remove the Broadcom Network from the Network configuration manager:

# netcfg
and remove the list:

HW Broadcom BCM575X NetXtreme Gigabit Ethernet-PCI Slot 1 Bus 3...etc

Then exit netcfg.

Now install the new "bcme" driver 9.7.0:

# pkgadd -d /tmp/bcme-9.7.0.pkg
And replace the old one.

Now enter Network configuration manager again and add a new LAN.

# netcfg

You will see the "Broadcom BCM575X NetXtreme Gigabit Ethernet-PCI" with release 9.7.0.

Configure the TCP/IP information and then exit netcfg.

Reboot the server.

13- Now you should have a full working Network with Broadcom BCM5751 PCI-E with release 9.7.0 driver and a working MultiTech MT5634ZPX-PCI Modem on the DELL SC440.

NOTE:     The Broadcom SCO OSR6/UW7 "bcme" driver ver. 9.7.0 is at this time
          of writing the TA only vendor supported. It will be fully SCO
          supported in the near future.

From the Xinuos technical article database, record 126678. Reproduced with permission. The original is at www.sco.com/ta/126678, 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.