| Home | Company | Products | Support | What's New? | Contact Us |

Tech Supports & Downloads :

Tablet PC :
TTAB-A12D
TTAB-B12D
TTAB-910E

Blade Servers :
TUD-4010 Blade Server
TUD-3114 Blade Server
TUD-2016 Blade Server

Rackmount Servers :
TSS-1412 1U P4 Server
TSS-1414 1U P4 Server
TSS-1520 1U Dual Xeon
TSS-1521 1U Dual Xeon
TSS-1522 1U Dual Xeon
TSS-1523 1U Dual Xeon
TSS-2520 2U Dual Xeon
TSS-3520 3U Dual Xeon

64/32-bit :
TS-1881 1U Dual Opteron
TS-1551 1U Dual Xeon EM64T

TS-2552 2U Dual Xeon EM64T

Disk Array Storage :
DA-7300 (SATA)
DA-7200 (SATA)
DA-3000 (SCSI)
DA-3300 (IDE)
DA-6300 (IDE)

SPARC Servers :
U280R, U280R5, Blade 1000/2000
U100T, U200R, Blade 100
Other Models
SPARC/Solaris FAQ
Part-I, Part-II, Part-III

Contact Us :
Email: support@tsti.com
Tel:(510) 687-9688

Tech Support >> FAQ-Two for SPARC Solaris

 

  1. Video & Monitors
  2. Raid Subsystems
  3. Networking
  4. Hardware Misc.
    --------------------------------------------------------------------------------

Video & Monitors


--------------------------------------------------------------------------------

Setting Display Modes for TGX+ Graphics Cards (rev. 1.0)

When installing one of these cards in an SBus-compatible Solaris workstation, no drivers are required. You may simply power your system down, plug the card into an available slot, and power the system up. If you desire a display mode other than the default (1152x900x66), you may change the setting on the card or at the ok prompt as described below.

A. Setting the mode by switch.

Display Mode JSCAN Rotor JSCAN Switches
r1152x900x66 7 All switches OPEN
r1152x900x76 6 Switch 1 CLOSED; Switches 2,3 OPEN
r1024x768x60 5 Switch 2 CLOSED; Switches 1,3 OPEN
r1152x900x76 4 Switches 1,2 CLOSED; Switch 3 OPEN
r1152x900x66 3 Switch 3 CLOSED; Switches 1,2 OPEN
r1280x1024x76 2 Switches 1,3 CLOSED; Switch 2 OPEN
r1600x1280x76 1 Not supported
r1024x768x77 0 All switches CLOSED


NOTES: - TGX+ cards come equipped with either a rotor switch or DIP switches.
- Make certain that power to the system is OFF before changing switches.

B. Setting the mode at the ok prompt.

At the ok prompt type: ok setenv output-device screen:display mode
ok reset

For example: ok setenv output-device screen:r1280x1024x76
ok reset

NOTES: ok setenv output-device screen alone (without colon or display mode) will allow the hardware switch to determine the display mode. Otherwise, when the environmental variable is set at the ok prompt as above, the environmental variable will override the hardware switch.

Back to Top


Setting Display Modes for HTGX+ Graphics Cards (rev. 1.0)

When installing one of these cards in an SBus-compatible Solaris workstation, no drivers are required. You may simply power your system down, plug the card into an available slot, and power the system up. If you desire a display mode other than the default (1152x900x66), you may change the setting on the card or at the ok prompt as described below.


A. Setting the mode by switch.

Display Mode JSCAN Rotor JSCAN Switches

Display Mode JSCAN Rotor JSCAN Switches
r1152x900x66 7 All switches OPEN
r1152x900x76 6 Switch 1 CLOSED; Switches 2,3 OPEN
r1024x768x60 5 Switch 2 CLOSED; Switches 1,3 OPEN
r1152x900x76 4 Switches 1,2 CLOSED; Switch 3 OPEN
r1152x900x66 3 Switch 3 CLOSED; Switches 1,2 OPEN
r1280x1024x76 2 Switches 1,3 CLOSED; Switch 2 OPEN
r1600x1280x76 1 Switches 2,3 CLOSED; Switch 1 OPEN
r1024x768x77 0 All switches CLOSED


NOTES: - HTGX+ cards come equipped with either a rotor switch or DIP switches.
- Make certain that power to the system is OFF before changing switches.

B. Setting the mode at the ok prompt.

At the ok prompt type: ok setenv output-device screen:display mode
ok reset

For example: ok setenv output-device screen:r1280x1024x76
ok reset

NOTES: ok setenv output-device screen alone (without colon or display mode) will allow the hardware switch to determine the display mode. Otherwise, when the environmental variable is set at the ok prompt as above, the environmental variable will override the hardware switch.

Back to Top

How can I reconfigue my freme buffer cards?

PCIGX-> This card uses the SUNWm64* driver set from Sun and is configurable by using the /usr/sbin/m64config command.

PGX32-> This card uses the TSIpg* driver set from Sun for Solaris 2.7 and 2.8 for Solaris 2.6 you can find the drivers at www.techsource.com and it is configurable with the /usr/sbin/GFXconfig command.

Creator cards uses the SUNWffb* driver set and uses the /usr/sbin/ffbconfig for configuring the video card.

The Elite3D cards use the SUNWafb* driver set and the /usr/sbin/afbconfig


How to identify the graphic card in my system?

The easy way to find out what graphic card is currently configured for your system is to run the following command:
ls -al /dev/fb* what it should return is something like this:

testsystem% ls -al /dev/fb*
total 8464
lrwxrwxrwx 1 root root 40 Nov 27 17:42 /dev/fb ->
/devices/pci@1f,0/pci@1/TSI,gfxp@3:gfxp0
lrwxrwxrwx 1 root root 8 Apr 6 2000 /dev/fb0 -> fbs/m640
lrwxrwxrwx 1 root root 8 Sep 13 16:02 /dev/fb1 -> fbs/m641
lrwxrwxrwx 1 root root 9 Oct 15 17:06 /dev/fb2 -> fbs/gfxp0

/dev/fbs:
total 3
drwxr-xr-x 2 root root 512 Oct 15 17:06 .
drwxr-xr-x 13 root sys 4608 Nov 27 17:42 ..
lrwxrwxrwx 1 root root 45 Oct 15 17:06 gfxp0 ->
../../devices/pci@1f,0/pci@1/TSI,gfxp@3:gfxp0
lrwxrwxrwx 1 root root 49 Apr 6 2000 m640 ->
../../devices/pci@1f,0/pci@1/ATY,3DCHARGER@3:m640
lrwxrwxrwx 1 root root 49 Sep 13 16:02 m641 ->
../../devices/pci@1f,0/pci@1/ATY,3DCHARGER@4:m641

In this case the system is currently running the PGX32 card because the line
lrwxrwxrwx 1 root root 40 Nov 27 17:42 /dev/fb ->
/devices/pci@1f,0/pci@1/TSI,gfxp@3:gfxp0 tells us so.

FYI: UNIX IDs

UPA Bus:
Creator Series 1/2/3 (FFB), Creator3D Series 1/2/3 (FFB) UNIX ID: /dev/ffb0

PCI Frame buffer:
PGX UNIX ID: /dev/fbs/m640
PGX32 UNIX ID: /dev/fbs/gfxp0
PGX64 UNIX ID: /dev/fbs/m640
SunVideo Plus UNIX ID: /dev/olk0
Expert3D Expert3D lite UNIX ID: /dev/fbs/ifb0

Back to Top


Special notes for Sun's Frame buffer cards

Expert3D 24-Bit Color Frame Buffer card


UNIX ID: /dev/fbs/ifb0 (same ID as Expert3D Lite)


Note: On a Sun Blade 1000, do not install in PCI Slot 1 (66MHz). Install only in Slot 2, 3, or 4 (33MHz).

Please refer installation guide for detailed http//sunsolve.sun.com/data/806/806-1859/pdf/

Elite3D-m3 / Elite3D-m6 / AFB Series 1/2 24-Bit Color Frame Buffer

Operating System Notes
The minimum OS is Solaris 2.5.1 HW: 11/97 or Solaris 2.6 HW: 3/98.
The Elite3D Supplemental CD for Solaris 2.5.1 is required.
Elite3D device drivers are bundled in Solaris 2.6 Hardware: 3/98.

Board Notes
Do NOT assemble or disassemble an Elite3D-m6. The Mictor connector can be damaged during assembly and disassembly.

Ultra 10 Compatibility Notes
Elite3D-m3 is not compatible with 300MHz Module
Elite3D-m3 is not compatible with 300MHz Module


Please refer installation guide for detailed http://sunsolve.sun.com/data/805/805-4391/pdf/ or http://sunsolve.sun.com/data/805/805-3321/pdf/

PGX64 8/24-Bit Color Frame Buffer

UNIX ID: /dev/fbs/m640

Notes
The minimum OS is 2.5.1.
Option 3768 includes HD15 to DB13W3 Adapter 530-2917.
On the Ultra 60, Ultra 80, and Sun Blade 1000 systems, PGX64 cannot be installed if there is a double-wide UPA frame buffer (Elite3D m6 graphics) installed in the adjacent UPA slot.
It is suggested for Ex500 systems that at least one CPU be installed for each PGX64 card.


Please refer installation guide for detailed http://sunsolve.sun.com/data/806/806-6548/pdf/

PGX32 8/24-Bit Color Frame Buffer

UNIX ID: /dev/fbs/gfxp0

Notes
The minimum OS is 2.5.1 HW: 11/97, 2.6 HW: 3/98, and Solaris 7.
The A20/A25 OBP banner command fails with PGX32 <370-3753-03.
The E3000-6000 and E3500-E6500 require PGX32 >=370-3753-04.
Option 3668 includes HD15 to DB13W3 Adapter 530-2357 or 530-2917.
Resolutions up to 1280 × 1024 default to 8/24-bit mode.
Resolutions over 1280 × 1024 default to 8-bit mode.

Please refer installation guide for detailed http://sunsolve.sun.com/data/805/805-7770/pdf/

Back to Top


Raid Subsystems


Universal Replacement Canister.

All Tatung external RAID Arrays feature hard drives mounted in standard removable drive canisters. Current Tatung practice is to set the SCSI ID with jumpers on the back of the canister mounting frame, near the SCSI cable connector. Both the SCSI ID dial switch on the back of the removable canisters and the SCSI ID jumpers on the drives themselves should be set to ID 0 - the jumpers on the frames will set the ID properly. This means that a single removable canister with hard drive of a model matching those in the array, with IDs set to 0, can act as a universal replacement. The SCSI ID will be proper when the canister is inserted in the mounting frame, no adjustment required.

RAID Controller Default Settings.

view & edit SCSI channels -
PID=7, SID=NA for single controllers, OR
PID=7, SID=6 for redundant controllers.

view & edit Configuration parameters : Caching parameters -
Write-back cache=Disabled without battery, OR
Write-back cache=Enabled with battery installed by TSTI.

view & edit Configuration parameters : Drive-side SCSI parameters -
Periodic Drive Check Time=30 seconds,
Periodic SAF-TE Device Check Time=Disabled,
Periodic Auto-Detect Failure Drive Swap Check Time=60 seconds.

view & edit Configuration parameters : Disk Array parameters -
Rebuild Priority=Normal.

view & edit Configuration parameters : Disk Array parameters : Verification on Writes -
Verification on LD Initialization Writes=Enabled.
Verification on LD Rebuild Writes=Enabled.
Verification on Normal Drive Writes=Disabled.

view & edit Configuration parameters : Controller parameters -
Controller Name= _ _ _ _ DAF-3102 (where _ = spacebar),
OR _ _ _ _ DAF-3200
OR _ _ _ _ DAF-3202
LCD Title Display=Controller Name.
SDRAM ECC=Enabled.

Back to Top


Networking

  • Ways to turn off auto-negotiation of your NIC

Ways to turn off Auto-Negotiation of your NIC

There are several way of turning off the auto-negation on and we will go into three of the most common ways.
1)vi /kernel/drv/hme.conf and add the following lines:
set hme:hme_adv_autoneg_cap=0
set hme:hme_adv_10hdx_cap=0
set hme:hme_adv_100fdx_cap=1
set hme:hme_adv_10fdx_cap=0
set hme:hme_adv_10hdx_cap=0
2)vi /etc/system
set hme:hme_adv_autoneg_cap=0
set hme:hme_adv_100fdx_cap=1
set hme:hme_adv_100hdx_cap=0
set hme:hme_adv_10fdx_cap=0
set hme:hme_adv_10hdx_cap=0
3)use the ndd commands
ndd -set /dev/hme adv_100fdx_cap 1
ndd -set /dev/hme adv_100hdx_cap 0
ndd -set /dev/hme adv_10fdx_cap 0
ndd -set /dev/hme adv_10hdx_cap 0
ndd -set /dev/hme adv_autoneg_cap 0

These commands are similar to the how you would setup the gigabit ethernet card except for the ge.conf file and the /etc/system files would contain the following:

set ge:ge_adv_1000autoneg_cap = 0
set ge:ge_adv_1000fdx_cap = 1
set ge:ge_adv_1000hdx_cap = 0

and if you decided to set it up using the ndd the command would be:
ndd -set /dev/ge adv_1000autoneg_cap = 0
ndd -set /dev/ge adv_1000fdx_cap = 1
ndd -set /dev/ge adv_1000hdx_cap = 0

With the 280R system you will need to edit the eri.conf or the /etc/system with the eri settings like in the examples above.

Do not modify it in more than one location because you will end up confusing yourself if it starts not to work correctly.

In addition you will want to turn off the auto-negation on the switch side also.

Back to Top

Hardware Misc.

Instructions for Mounting Extendable Rails on a Rackmount Case.


Instructions for Mounting Extendable Rails on a Rackmount Case.


1. Open the rail package and identify the parts from the included drawing. On one rail assembly, pull the rails open towards the front (towards the three "finger" flanges) until both spring-mounted retainer lugs snap into place. Remove the inner-most of the three rails from the assembly by pressing its retainer lug and pulling the rail forward and free of the assembly. Remember which end of the rail is forward and which end is rearward (the spring-mounted retainer lug is toward the rear). Repeat this procedure for the other rail assembly.

2. Optional: If the rackmount case model you purchased includes beige rail-mounting side covers, remove both covers and retain the screws. This should require removing six to eight large Phillips-head screws from each side and will reveal the rail mounting area.
Required: In the rail mounting area on the side of the case, mount the inner rail you removed in Step 1. Use the screws you retained earlier in Step 2, or screws from the rail package. Make sure the rear of the rail is oriented towards the rear of the rackmount case. For some models of case, you must now mount two beige "faceplate" flanges immediately behind the handles of the case. For other models of case these flanges are "built-in" design features of the case faceplate.

3. Taking up the remaining pieces of the rail-assemblies, mount the end bracket to the rear of the outer rail as shown on the diagram. (Note that, although the exploded drawing shows the middle or "intermediate" rail disassembled from the outer rail, the middle rail was actually left extended from the front of the outer rail during Step 1.)

4. Now mount the rail assemblies to the rack. Both the front "finger" flanges and the end bracket should fit inside the vertical rails of your rack.

5. Carefully align the inner rails that are attached to your rackmount case with the extended middle rails and slide the inner rails into the middle rails. When the spring-mounted retainer lugs meet the forward edges of the middle rails you will have to depress the springs so that you can continue to slide the case back along the rail assemblies. Repeat this action when the retainer lugs snap into their places in the middle rails. You should now be able to slide the rackmount case all the way back along the rails until the faceplate flanges meet the vertical rails of your rack. Your assembly should be completely functional at this point.

6. Attach the faceplate flanges to the rails with appropriate screws so that your computer does not inadvertently slide out along the rail assembly.

Back to Top



 

 

Contact us : Phone:1-800-659-5902; email: sales@tsti.com
 Legal, Copyright & Trademark Notice