Sponsored Content
Top Forums UNIX for Advanced & Expert Users Need Help , Ultra SPARC can not loading Post 302112408 by heru_90 on Wednesday 28th of March 2007 03:14:06 AM
Old 03-28-2007
Thank you Sumitpandya,

you mean my SPARC machine disk drive is broken or just my OS?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Sun Ultra sparc 60

Hello everybody!! I need your help again. I am using Sun Ultra sparc 60 machine.Follwing are the types of files getting generated in /var/tmp. "windu_sm_o aaaa,baaa,caaa,daaa" etc. I am not able to locate which application is generating these files. Can I straightway delete these files ? or... (1 Reply)
Discussion started by: vikasdeshmukh
1 Replies

2. Solaris

ultra sparc 2 no video - ok prompt access

I have an ultra sparc 2 with no video - I connect to it with hyperterm. Is there a way to get to the OK prompt? I have tried control/break and that does not work. If not is there a video card I can get to put in this box? I have Solaris 10 installed on this machine. Thanks (7 Replies)
Discussion started by: tribbles
7 Replies

3. Solaris

In Sparc Ultra 45 machine, how to enable bge1

In Sparc Ultra 45 machine, how to enable bge1 port, how to do if bge0 is down then bge1 should automatically up. Thanks & Regards (2 Replies)
Discussion started by: durgaprasadr13
2 Replies

4. Solaris

Null modem cable in Ultra sparc 10

Hi Gurus, Can I use null modem cable in Ultra sparc 10 workstation Thanks (3 Replies)
Discussion started by: kumarmani
3 Replies

5. Debian

Problem installing Debian5 on an ultra sparc machine

Comments/Problems: Machine boots from CDROM, starts SILO Version 1.4.13, display welcome message (welcome to Debian GNU/Linux lenny! built on 20081218-10:06 ). boot: Allocated 8 Megs of memory at 0x40000000 for kernel Loaded kernel version 2.6.26 Loading initial ramdisk... (3 Replies)
Discussion started by: mtk
3 Replies

6. Solaris

How much better performance is ultra SPARC IV+ 1.95GHz than 1.35GHz?

Dear Guru, My boss has a plan to upgrade cpu of server so he needs to know how much better performance(percentage) is Ultra SPARC IV+ 1.95 GHz than Ultra SPARC IV 1.35 GHz?. I am looking for documentation to reference but I didn't see anything close to my point. If who know,... (3 Replies)
Discussion started by: unitipon
3 Replies

7. Solaris

Sun Sparc Ultra 4 won't boot - disk errors

Hi all. I am seeing in one of our less-used servers that it crashed and now won't restart. I get the message 'continue with normal startup or boot into maintenance mode'. I go into maintenance and run fsck on /usr0 (mentioned in error at restart) it then reboots but goes right back to... (3 Replies)
Discussion started by: jamie_collins
3 Replies

8. Ubuntu

Sudo issues with Ubuntu 7.10 Running on a Ultra SPARC Machine

I have a Sun Blade 1000 machine that I installed Ubuntu 7.10 SPARC onto. The only user configured (configure during install) cannot use sudo. When I try to issue a command using sudo (ex. sudo apt-get install) it asks me for my password and returns the error "user not found in sudoers file". I need... (4 Replies)
Discussion started by: swilso
4 Replies

9. Solaris

How to install PGX32 on Sparc 10 Ultra?

I'm trying to install a PGX32 video card on my Sparc 10 Ultra running Solaris 10. I've got the Oracle installation guide for it and I got as far as: "4. Insert the CD-ROM labeled “GFX OpenWindows for Solaris 2” into the drive." I don't have a CD-ROM by that name and a web search for that... (21 Replies)
Discussion started by: Michele31416
21 Replies

10. Hardware

Sun Sparc Ultra 30 help

Hi all, I managed to salvage form work an old Sun Sparc Ultra 30. I have had it stored (controlled storage) for a few years and decided to get it home and boot it up. It starts up with a beep then I can hear disks spinning up, CDROM moving but nothing is displayed on the monitor. Can... (2 Replies)
Discussion started by: robbo007
2 Replies
as(1)																	     as(1)

NAME
as - assembler SYNOPSIS
SPARC as [-b] [-i] [ -K {pic,PIC}] [-L] [-m] [-n] [-o outfile] [-P] [-Dname] [-Dname=def] [-Ipath] [-Uname...] [-q] [-Qy | n] [-s] [ -S [a | b | c | l | A | B | C | L] ] [-T] [-V] [-xarch=v7 | -xarch=v8 | -xarch=v8a | -xarch=v8plus | -xarch=v8plusa | -xarch=v8plusb | -xarch=v9 | -xarch=v9a | -xarch=v9b ] [-xF] [-Y dirname] filename... as [-b] [-i] [ -K PIC] [-L] [-m] [-n] [-o outfile] [-P] [-Dname] [-Dname=def] [-Ipath] [-Uname...] [-Qy | n] [-s] [ -S [a | b | c | l | A | B | C | L] ] [-T] [-V] [ -xarch=generic64 | -xarch=amd64] [-Y dirname] [-xmodel= [ SMALL | KERNEL ]] filename... The as command creates object files from assembly language source files. Common Options The following flags are common to both SPARC and . They may be specified in any order: -b Generates extra symbol table information. -i Ignore line number information from preprocessor. -K pic | PIC Generates position-independent code. -L Saves all symbols, including temporary labels that are normally discarded to save space, in the ELF symbol table. -m Runs the m4(1) macro processor on the input to the assembler. -n Suppresses all the warnings while assembling. -o outfile Puts the output of the assembly in outfile. By default, the output file name is formed by removing the .s suffix, if there is one, from the input file name and appending a .o suffix. -P Runs cpp(1), the C preprocessor, on the files being assembled. The preprocessor is run separately on each input file, not on their con- catenation. The preprocessor output is passed to the assembler. -Dname -Dname=def When the -P option is in effect, these options are passed to the cpp(1) preprocessor without interpretation by the as command; other- wise, they are ignored. -Ipath When the -P option is in effect, this option is passed to the cpp(1) preprocessor without interpretation by the as command; otherwise, it is ignored. -Uname When the -P option is in effect, this option is passed to the cpp(1) preprocessor without interpretation by the as command; otherwise, it is ignored. -Qy | n If y is specified, this option produces the "assembler version" information in the comment section of the output object file. If n is specified, the information is suppressed. -s Places all stabs in the .stabs section. By default, stabs are placed in stabs.excl sections, which are stripped out by the static linker, ld(1), during final execution. When the -s option is used, stabs remain in the final executable because .stab sections are not stripped by the static linker. -S[a|b|c|l|A|B|C|L] Produces a disassembly of the emitted code to the standard output. Adding each of the following characters to the -S option produces: a disassembling with address b disassembling with ".bof" c disassembling with comments l disassembling with line numbers Capital letters turn the switch off for the corresponding option. -T This is a migration option for 4.x assembly files to be assembled on 5.x systems. With this option, the symbol names in 4.x assembly files will be interpreted as 5.x symbol names. -V Writes the version number of the assembler being run on the standard error output. -xF Allows function reordering by the Performance Analyzer. If you compile with the -xF option, and then run the Performance Analyzer, you can generate a map file that shows an optimized order for the functions. The subsequent link to build the executable file can be directed to use that map file by using the linker -M mapfile option. It places each function from the executable file into a separate section. -Y dirname Specify directory m4 and/or cm4def. Options for SPARC only -q Performs a quick assembly. When the -q option is used, many error checks are not performed. Note: This option disables many error checks. Use of this option to assemble handwritten assembly language is not recommended. -xarch=v7 This option instructs the assembler to accept instructions defined in the SPARC version 7 (V7) architecture. The resulting object code is in ELF format. -xarch=v8 This option instructs the assembler to accept instructions defined in the SPARC-V8 architecture, less the quad-precision floating-point instructions. The resulting object code is in ELF format. -xarch=v8a This option instructs the assembler to accept instructions defined in the SPARC-V8 architecture, less the quad-precision floating-point instructions and less the fsmuld instruction. The resulting object code is in ELF format. This is the default choice of the -xarch=options. -xarch=v8plus This option instructs the assembler to accept instructions defined in the SPARC-V9 architecture, less the quad-precision floating-point instructions. The resulting object code is in ELF format. It will not execute on a Solaris V8 system (a machine with a V8 processor). It will execute on a Solaris V8+ system. This combination is a SPARC 64-bit processor and a 32-bit OS. -xarch=v8plusa This option instructs the assembler to accept instructions defined in the SPARC-V9 architecture, less the quad-precision floating-point instructions, plus the instructions in the Visual Instruction Set (VIS). The resulting object code is in V8+ ELF format. It will not execute on a Solaris V8 system (a machine with a V8 processor). It will execute on a Solaris V8+ system -xarch=v8plusb This option enables the assembler to accept instructions defined in the SPARC-V9 architecture, plus the instructions in the Visual Instruction Set (VIS), with UltraSPARC-III extensions. The resulting object code is in V8+ ELF32 format. It executes only on an Ultra- SPARC-III processor. -xarch=v9 This option limits the instruction set to the SPARC-V9 architecture. The resulting .o object files are in 64-bit ELF format and can only be linked with other object files in the same format. The resulting executable can only be run on a 64-bit SPARC processor running 64-bit Solaris with the 64-bit kernel. -xarch=v9a This option limits the instruction set to the SPARC-V9 architecture, adding the Visual Instruction Set (VIS) and extensions specific to UltraSPARC processors. The resulting .o object files are in 64-bit ELF format and can only be linked with other object files in the same format. The resulting executable can only be run on a 64-bit SPARC processor running 64-bit Solaris with the 64-bit kernel. -xarch=v9b This option enables the assembler to accept instructions defined in the SPARC-V9 architecture, plus the Visual Instruction Set (VIS), with UltraSPARC-III extensions. The resulting .o object files are in ELF64 format and can only be linked with other V9 object files in the same format. The resulting executable can only be run on a 64-bit UltraSPARC-III pro cessor running a 64-bit Solaris operating environment with the 64-bit kernel. Options for Only --xarch=generic64 Limits the instruction set to AMD64. The resulting object code is in 64-bit ELF format. --xarch=amd64 Limits the instruction set to AMD64. The resulting object code is in 64-bit ELF format. -xmodel=[SMALL | KERNEL] For AMD64 only, generate R_X86_64_32S relocatable type for static data access under KERNEL. Otherwise, generate R_X86_64_32 under SMALL. SMALL is the default. The following operand is supported: filename Assembly language source file TMPDIR The as command normally creates temporary files in the directory /tmp. Another directory may be specified by setting the environment variable TMPDIR to the chosen directory. (If TMPDIR is not a valid directory, then as will use /tmp). By default, as creates its temporary files in /tmp. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsprot | +-----------------------------+-----------------------------+ cc(1B), cpp(1),ld(1), m4(1), nm(1), strip(1), tmpnam(3C), a.out(4), attributes(5) dbx and analyzer manual pages available with Sun Studio documentation. If the -m option, which invokes the m4(1) macro processor, is used, keywords for m4 cannot be used as symbols (variables, functions, labels) in the input file, since m4 cannot determine which keywords are assembler symbols and which keywords are real m4 macros. Whenever possible, access the assembler through a compilation system interface program such as cc(1B). All undefined symbols are treated as global. 16 Sep 2005 as(1)
All times are GMT -4. The time now is 05:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy