Sponsored Content
Full Discussion: T5220
Operating Systems Solaris T5220 Post 302513993 by Perderabo on Thursday 14th of April 2011 01:05:01 PM
Old 04-14-2011
I'm not sure what you mean by "virtual terminal". But I had a devil of a time getting an XVR-300x8 video card to work on a 5120. I beat on it until I got it to work, but this may not be the best way.

We make a few mods to Solaris as we install and so /etc/dt/config already exists for me. So I did: cp /usr/dt/config/Xservers /etc/dt/config/Xservers and then edited the new file to add -dev /dev/fbs/nfb0a to the last non-blank line. Then I ran: /usr/lib/fbconfig/SUNWnfb_config -res VESA_STD_1280x1024x75 and rebooted. It works for me. I have followed this procedure several times and I always get it to work.

And btw, I use Solaris 10 update 7 on our T5120's.
 

10 More Discussions You Might Find Interesting

1. Solaris

kstat on T5220

We used kstat on netra240/440 to check if the link is full duplex. So we do something like: bash-3.00# kstat -pc net bge:1::/'link_duplex'/ | cut -f2 2 The output 2 indicates the link is full duplex. This kind of check worked all right for Netra 240/440 systems. However, the nxge... (2 Replies)
Discussion started by: illcar
2 Replies

2. Solaris

ILOM and sc on T5220

I 've 2 different T5220 and both are showing different prompts when i ssh to the console. 1. Shows sc> ALOM 2. Shows -> ILOM as far as i know the T5220 comes with ILOM , so why i 'm seeing 2 different type of console for same tyep of hardware ? and i found that we... (6 Replies)
Discussion started by: fugitive
6 Replies

3. Solaris

SC on T5220 not responding

Hi, SC on one of my T5220 is not responding .. it does not show not let me type anything .. what could be the reason for it ? though when i powercycle the box from sc it shows me the system coming up but after that does not let me login thru sc sc> console -f Enter #. to return to ALOM. (2 Replies)
Discussion started by: fugitive
2 Replies

4. Solaris

LDOMs on T5220

We're just about to migrate a large application from an Enterprise 6900 to a pair of T5220s utilising LDOMs. Does anyone have any experience of LDOMs on this kit and can provide any recommendations or pitfalls to avoid? I've heard that use of LDOMs can have an impact on I/O speeds as it's all... (9 Replies)
Discussion started by: JerryHone
9 Replies

5. Solaris

T5220 server

Hi, We have two T5220 servers in our datacentre one server is showing 64 processors online and another showing 32 processors online two are newly purchased, there is no hardware faults in this server one server has 64gb memory and it shows 64 processors, and other having 32gb memory and it... (5 Replies)
Discussion started by: rajasekg
5 Replies

6. Solaris

Set up new T5220 remotely

I have a new T5220 racked at our remote office and the guys who racked it does not know how to configure the SP on the system .. is there any way i can do it remotely ? (1 Reply)
Discussion started by: fugitive
1 Replies

7. Solaris

ILOM problem on T5220

I have setup my T5220 ILOM .. and its working fine. But if my network connection is broken to the ILOM i 'm unable to login to the ILOM for few hrs .. it gives me either wrong user/passwd error and after few hrs the same user/passwd works .. what could be the reason for this and how can i resove... (3 Replies)
Discussion started by: fugitive
3 Replies

8. Solaris

Jumpstart Issues With T5220

I'm trying to use a V210 (sun4u) configured as a jumpstart server to flash install a number of T5220's (sunv4). The Facts: V210 - Solaris 10 (September 2010 Release / not patched) T5220's - Archive's created using prior (unknown) version of solaris 10. Flar -i <archive name> shows the... (6 Replies)
Discussion started by: Celtic_Monkey
6 Replies

9. Solaris

T5220

Hello guys, can anyone give me some advice on how to perform clean installation of Solaris 10 on T5220 ? I am connected with serial management port on the machine, i have the ok promt and now i should eject the dvdrom to insert Solaris dvd into and start the clean install. So how to do that... (3 Replies)
Discussion started by: tonijel
3 Replies

10. Solaris

Where are my other disks on T5220 ?

Hi, I got a (used) server to install Solaris 11 and wipe out every information on existing disks. There are 6 disks of 300GB and two disks of 146GB. I am not able to figure out, how to find out RAID (if there is any) and break it. Can anybody help me with that ? Below is configuration. I have... (18 Replies)
Discussion started by: solaris_1977
18 Replies
ICON(1) 						      General Commands Manual							   ICON(1)

NAME
icon - interpret or compile Icon programs SYNOPSIS
icont [ option ... ] file ... [ -x arg ... ] iconc [ option ... ] file ... [ -x arg ... ] DESCRIPTION
icont and iconc each convert an Icon source program into executable form. icont translates quickly and provides interpretive execution. iconc takes longer to compile but produces programs that execute faster. icont and iconc for the most part can be used interchangeably. This manual page describes both icont and iconc. Where there there are differences in usage between icont and iconc, these are noted. File Names: Files whose names end in .icn are assumed to be Icon source files. The .icn suffix may be omitted; if it is not present, it is supplied. The character - can be used to indicate an Icon source file given in standard input. Several source files can be given on the same command line; if so, they are combined to produce a single program. The name of the executable file is the base name of the first input file, formed by deleting the suffix, if present. stdin is used for source programs given in standard input. Processing: As noted in the synopsis above, icont and iconc accept options followed by file names, optionally followed by -x and arguments. If -x is given, the program is executed automatically and any following arguments are passed to it. icont: The processing performed by icont consists of two phases: translation and linking. During translation, each Icon source file is translated into an intermediate language called ucode. Two ucode files are produced for each source file, with base names from the source file and suffixes .u1 and .u2. During linking, the one or more pairs of ucode files are combined to produce a single icode file. The ucode files are deleted after the icode file is created. Processing by icont can be terminated after translation by the -c option. In this case, the ucode files are not deleted. The names of .u1 files from previous translations can be given on the icont command line. These files and the corresponding .u2 files are included in the linking phase after the translation of any source files. The suffix .u can be used in place of .u1; in this case the 1 is supplied auto- matically. Ucode files that are explicitly named are not deleted. iconc: The processing performed by iconc consists of two phases: code generation and compilation and linking. The code generation phase produces C code, consisting of a .c and a .h file, with the base name of the first source file. These files are then compiled and linked to produce an executable binary file. The C files normally are deleted after compilation and linking. Processing by iconc can be terminated after code generation by the -c option. In this case, the C files are not deleted. OPTIONS
The following options are recognized by icont and iconc: -c Stop after producing intermediate files and do not delete them. -e file Redirect standard error output to file. -f s Enable full string invocation. -o name Name the output file name. -s Suppress informative messages. Normally, both informative messages and error messages are sent to standard error output. -t Arrange for &trace to have an initial value of -1 when the program is executed and for iconc enable debugging features. -u Issue warning messages for undeclared identifiers in the program. -v i Set verbosity level of informative messages to i -E Direct the results of preprocessing to standard output and inhibit further processing. The following additional options are recognized by iconc: -f string Enable features as indicated by the letters in string: a all, equivalent to delns d enable debugging features: display(), name(), variable(), error trace back, and the effect of -f n (see below) e enable error conversion l enable large-integer arithmetic n produce code that keeps track of line numbers and file names in the source code s enable full string invocation -n string Disable specific optimizations. These are indicated by the letters in string: a all, equivalent to cest c control flow optimizations other than switch statement optimizations e expand operations in-line when reasonable (keywords are always put in-line) s optimize switch statements associated with operation invocations t type inference -p arg Pass arg on to the C compiler used by iconc -r path Use the run-time system at path, which must end with a slash. -C prg Have iconc use the C compiler given by prg ENVIRONMENT VARIABLES
When an Icon program is executed, several environment variables are examined to determine certain execution parameters. Values in paren- theses are the default values. BLKSIZE (500000) The initial size of the allocated block region, in bytes. COEXPSIZE (2000) The size, in words, of each co-expression block. DBLIST The location of data bases for iconc to search before the standard one. The value of DBLIST should be a blank-separated string of the form p1 p2 ... pn where the pi name directories. ICONCORE If set, a core dump is produced for error termination. ICONX The location of iconx, the executor for icode files, is built into an icode file when it is produced. This location can be overridden by setting the environment variable ICONX. If ICONX is set, its value is used in place of the location built into the icode file. IPATH The location of ucode files specified in link declarations for icont. IPATH is a blank-separated list of directories. The current directory is always searched first, regardless of the value of IPATH. LPATH The location of source files specified in preprocessor $include directives and in link declarations for iconc. LPATH is otherwise sim- ilar to IPATH. MSTKSIZE (10000) The size, in words, of the main interpreter stack for icont. NOERRBUF By default, &errout is buffered. If this variable is set, &errout is not buffered. QLSIZE (5000) The size, in bytes, of the region used for pointers to strings during garbage collection. STRSIZE (500000) The initial size of the string space, in bytes. TRACE The initial value of &trace. If this variable has a value, it overrides the translation-time -t option. FILES
icont Icon translator iconc Icon compiler iconx Icon executor SEE ALSO
The Icon Programming Language, Ralph E. Griswold and Madge T. Griswold, Prentice-Hall Inc., Englewood Cliffs, New Jersey, Second Edition, 1990. Version 9.1 of Icon, Ralph E. Griswold, Clinton L. Jeffery, and Gregg M. Townsend, IPD267, Department of Computer Science, The University of Arizona, 1995. Version 9 of the Icon Compiler, Ralph E. Griswold, IPD237, Department of Computer Science, The University of Arizona, 1995. icon_vt(1) LIMITATIONS AND BUGS
The icode files for the interpreter do not stand alone; the Icon run-time system (iconx) must be present. Stack overflow is checked using a heuristic that is not always effective. 1 November 1995 IPD244b ICON(1)
All times are GMT -4. The time now is 09:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy