Sponsored Content
Full Discussion: about Sun 9 HCL
Operating Systems Solaris about Sun 9 HCL Post 50851 by qmemo on Tuesday 4th of May 2004 09:22:00 AM
Old 05-04-2004
Java about Sun 9 HCL

Hi all I cheked the HCL of my hardware
ok first thing does it mean not seeing a dvice in the HCL that's it's not supported?
well my hardware is (x86 arch.)
My Hardware list : I Have a 1.70 intel Pentium 4 processor, 384 MB Ram, WD 40 GB Hard Disk, Aopen Riva TNT2 Model 64 VGA card
,ATAPI CD-Rom, SAMSUNG CD-R/RW, C-MEDIA Pci Card (On Board), Mother Board (Chantec)

that's for now waiting for your replyes


qmemo
 

4 More Discussions You Might Find Interesting

1. Solaris

How accurate is the HCL for Solaris 10?

I have a Sun Ultra 5 that is running Solaris 8. I believe I meet the minimum requirements for Solaris 10 but the Ultra 5 is not on the HCL. This will be my first ever Solaris upgrade so do I follow the HCL guidelines? TiA (4 Replies)
Discussion started by: PapaPark
4 Replies

2. UNIX for Advanced & Expert Users

Help: Sun Disk partitioning for Sun V240 & StorEdge 3300

Dear Sun gurus, I have Sun Fire V240 server with its StorEdge 3300 disk-array. Following are its disks appeared in format command. I have prepared its partitions thru format and metainit & metattach (may be i have made wrong steps, causing the errors below because I have done thru some document... (1 Reply)
Discussion started by: shafeeq
1 Replies

3. UNIX for Dummies Questions & Answers

Sun Solaris 10: How do I create a bootup disc? The Sun website confuses me

Hey there, I am starting a Computer Science Foundation year at the end of this month and am trying to get a little bit ahead of the game. I have always wanted to learn Unix and am currently struggling with creating a boot disc to run Solaris (I have chosen to study this) from as opposed to... (0 Replies)
Discussion started by: Jupiter
0 Replies

4. Solaris

Sun Fire 280R Sun Solaris CRT/Monitor requirements

I am new to Sun. I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor? Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies
vparefiutil(1M) 														   vparefiutil(1M)

NAME
vparefiutil - display, update, or delete HP-UX hardware path to EFI path mappings of bootable disks in the virtual partition database SYNOPSIS
db_file] hw_path] DESCRIPTION
The command displays the HP-UX hardware path to EFI path mappings that are stored in the virtual partition database. Legacy and agile hardware paths will be displayed, if available, as provided by HP-UX. If the virtual partition database is not specified, then the live database or by default is used. It can also be used to update the hw_path to EFI_path mappings from to the database. The behavior without any options is to display the HP-UX hardware path to EFI path mappings. This command is not supported on PA-RISC systems. Options and Arguments recognizes the following command line options and arguments: Specifies the alternate database from which the HP-UX hardware path to EFI path mappings need to be displayed, updated, or deleted. or live is default if this is not specified. Updates the database from the info available (from Displays the HP-UX hardware path to EFI path mapping in machine readable format. Each mapping is displayed in a separate line as follows: Deletes the HP-UX hardware path to EFI path mappings in the database. Note: In live database, this deletes only the HP-UX hardware paths owned by the vpar on which this command is executed. If this is specified, only the HP-UX hardware paths at or below the given hw_path are displayed, updated, or deleted. SECURITY RESTRICTIONS
This command is restricted to processes owned by superuser. RETURN VALUE
returns the following values: Successful completion. Error condition occurred. EXAMPLES
Display the hw_path to EFI_path mappings from the live database. # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : 2.0.0.2.0.6.0 EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.0.6.0 : 2.0.0.3.0.6.0 EFI path : Acpi(HWP0002,200)/Pci(3|0)/Scsi(Pun6,Lun0)/ HD(Part1,Sig471031FC-6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.1.2.0 : 2.0.0.3.1.2.0 EFI path : Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1kk0)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(3|0)/Scsi(Pun6,Lun0)/ HD(Part1,Sig471031FC-6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.1.2.0 : EFI path : Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/ EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1kk0)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Display the hw_path to EFI_path mappings from the alternate database in machine readable format. # vparefiutil -M -D vpdb_foo 2.0.0.2.0.6.0:Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI::2.0.0.2.0.6.0 2.0.0.3.0.6.0:Acpi(HWP0002,200)/Pci(3|0)/ Scsi(Pun6,Lkk6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::2.0.0.3.0.6.0 2.0.0.3.1.2.0:Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI::2.0.0.3.1.2.0 2.0.8.1.0.3.4.0.0.1.6:Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/ EFIHPUXHPUX.EFI::2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 2.0.12.1.0.4.1.8.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.10.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunA,Lun0)/ EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.12.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: # vparefiutil -M -D vpdb_foo 2.0.0.2.0.6.0:Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI:: 2.0.0.3.0.6.0:Acpi(HWP0002,200)/Pci(3|0)/ Scsi(Pun6,Lkk6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: 2.0.0.3.1.2.0:Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI:: 2.0.8.1.0.3.4.0.0.1.6:Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/ EFIHPUXHPUX.EFI::2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 2.0.12.1.0.4.1.8.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.10.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/ Scsi(PunA,Lun0)/EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.12.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: Delete the HP-UX hardware-path paths to EFI path mappings at or below the HP-UX hardware path 2/0/0/3 of the current vpar. # vparefiutil -d -H 2/0/0/3 # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunA,Lun0)/ EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path pdb|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI # vparefiutil -d -H 2/0/0/3 # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/ Scsi(PunA,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path pdb|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI For Serial Attach SCSI (SAS) devices, the SAS address is displayed along with the hardware path and the EFI path. Hardware path : 0.0.14.0.0.0.0.0.0.2.0 EFI path : Acpi(HPQ0002,PNP0A08,E)/Pci(0|0)/Pci(0|0)/ VenMsg(D487DDB4-008B-11D9-AFDC-001083FFCA4D)/ HD(Part1,SigC6B41C20-01BE-11DC-8000-D6217B60E588)/EFIHPUXHPUX.EFI SAS Address : 0x500000e01200d3f2 The SAS hardware path can potentially change from one OS instance to another, but the SAS address will remain the same. To locate SAS devices in different OS instances (for example, an nPar OS instance and a vPar OS instance), use the SAS address instead of the hardware path. WARNING
The option is provided only to remove the stale HP-UX hardware path to EFI path mappings. If you remove the valid HP-UX hardware path to EFI path mappings, you may not be able to load vpars. It is always better to follow the operation with a operation to update the database with the valid HP-UX hardware path to EFI path mappings available from AUTHOR
was developed by the Hewlett-Packard Company. SEE ALSO
vparadmin(1M), vparboot(1M), vparconfig(1M), vparcreate(1M), vpardump(1M), vparenv(1M), vparextract(1M), vparmodify(1M), vparreloc(1M), vparremove(1M), vparreset(1M), vparstatus(1M), vparutil(1M), privileges(5), vparresources(5), vpartition(5), vpmon(5). Itanium(R)-Based Systems vparefiutil(1M)
All times are GMT -4. The time now is 11:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy