Sponsored Content
Full Discussion: Printing queue in rs6000
Operating Systems AIX Printing queue in rs6000 Post 302263319 by nervous on Monday 1st of December 2008 09:58:20 AM
Old 12-01-2008
Here is the output
Code:
@rs6000:/:> prtconf
ksh: prtconf:  not found.
@rs6000:/:> lsattr -El proc0
state enable  Processor state False
type  PowerPC Processor type  False

 

10 More Discussions You Might Find Interesting

1. Programming

Good IDE for C++ on RS6000/AIX

I am looking for the above Can anyone point me to a reliable product, with available support in the forseeable future ? Seeker (0 Replies)
Discussion started by: Seeker
0 Replies

2. AIX

RS6000 SSA Raid question

Hi Can I add disks on the fly to extend the capacity of an existing RAID 5 volume? It's created on a 4P Advanced SSA Raid Adapter. I need to extend a volume group, so I figured it would be easiest to extend the "physical disk" which is a RAID5 volume. Thanks. (1 Reply)
Discussion started by: osee
1 Replies

3. AIX

Printing multiple copies via remote queue

Hi all, I have an interesting problem. Using remote queues to print using jetdirect printers I am unable to get a printer to print multiple copies of a print job. command being used: lpr -P -#3 ./test (one copy prints) Also tried: enq -P -C3 ./test (same results) Any ideas? ... (6 Replies)
Discussion started by: Luck
6 Replies

4. AIX

Re-Installation of AIX 5.2 in RS6000 7026

Hi There!! I need to reinstall the operating system AIX 5.2 in a RS6000 7026/6H1 that has AIX 4.3 but I need a firmware upgrade that I dón´t know where can I obtain. - Platform firmware version 3 or later. Someone can help me please, I will be very grateful !! Thank´s. (1 Reply)
Discussion started by: terron79
1 Replies

5. AIX

New to AIX and got my hands on a RS6000 v.need help getting it on the network

So im fairly new to AIX and my knowledge is very, very limited but i got my hands on an RS6000 43P model and im trying to get it on the network so i can access it from work. I have pretty much tried everything i can/know how to do by reading up as much as i can but im still lost. I have the 43P... (2 Replies)
Discussion started by: IIIII
2 Replies

6. AIX

VNC or X Emulator on RS6000 AIX 5.2

Hello everyone, I have just joined your forum even though I have been using it on and off for couple of months now. Up until now I have been able to find any information I needed by just browsing this site or performing a Google search, but now I'm stuck!. I was hoping you could help me with... (16 Replies)
Discussion started by: juniorG
16 Replies

7. AIX

Reinstalling AIX 4.3 on IBM RS6000

Hey guys, I'm a newbie in Unix world.. Currently in my office lies an old IBM RS6000 which hasn't been maintained for a very long time. The former admin has resigned and we don't have any documentation or whatsoever regarding the old machine. All I know that it is an RS6000 is because of what's... (4 Replies)
Discussion started by: arch4ng3l
4 Replies

8. AIX

Remote printing to Linux CUPS queue

Hello all. I am setting up a queue under AIX 4.2.1 to print to a remote Linux CUPS queue. At present I can print to the queue remotely from Windows but not AIX. What I am seeing is lpstat reads the state of the remote queue but at job submission time I am getting backend exit fatal errors. The... (4 Replies)
Discussion started by: tgx
4 Replies

9. UNIX for Dummies Questions & Answers

Sco Unix printing : jobs hangs in queue - printing via lp versus hpnpf

Hi, We have a Unix 3.2v5.0.5. I installed a printer via scoadmin, HP network printer manager with network peripheral name (hostname and ipadres are in /etc/hosts). This is the configuration file : Code: root@sco1 # cat configurationBanner: on:AlwaysContent types: simpleDevice:... (0 Replies)
Discussion started by: haezeban
0 Replies

10. AIX

AIX 5.1 and RS6000

I've an old server 1996 RS6000 (Processor 604e) running AIX 5.1. It started up fine, booted up and connected on 10Mbit with my router. I used to be able to connect to it with telnet but not anymore. I know the IP is right but working with the smit tcpip options, looks like I've changed... (1 Reply)
Discussion started by: Devyn
1 Replies
prtconf(1M)															       prtconf(1M)

NAME
prtconf - print system configuration SYNOPSIS
/usr/sbin/prtconf [-V] | [-F] | [-x] | [-bpv] | [-acDPv] [dev_path] The prtconf command prints the system configuration information. The output includes the total amount of memory, and the configuration of system peripherals formatted as a device tree. If a device path is specified on the command line for those command options that can take a device path, prtconf will only display informa- tion for that device node. The following options are supported: -a Display all the ancestors device nodes, up to the root node of the device tree, for the device specified on the command line. -b Display the firmware device tree root properties for the purpose of platform identification. These properties are "name", "compat- ible", "banner-name" and "model". -c Display the device subtree rooted at the device node specified on the command line, that is, display all the children of the device node specified on the command line. -D For each system peripheral in the device tree, displays the name of the device driver used to manage the peripheral. -F Returns the device path name of the console frame buffer, if one exists. If there is no frame buffer, prtconf returns a non-zero exit code. This flag must be used by itself. It returns only the name of the console, frame buffer device or a non-zero exit code. For example, if the console frame buffer on a SUNW,Ultra-30 is ffb, the command returns: /SUNW,ffb@1e,0:ffb0. This option could be used to create a symlink for /dev/fb to the actual console device. -p Displays information derived from the device tree provided by the firmware (PROM) on SPARC platforms or the booting system on platforms.The device tree information displayed using this option is a snapshot of the initial configuration and may not accu- rately reflect reconfiguration events that occur later. -P Includes information about pseudo devices. By default, information regarding pseudo devices is omitted. -v Specifies verbose mode. -V Displays platform-dependent PROM (on SPARC platforms) or booting system (on platforms) version information. This flag must be used by itself. The output is a string. The format of the string is arbitrary and platform-dependent. -x Reports if the firmware on this system is 64-bit ready. Some existing platforms may need a firmware upgrade in order to run the 64-bit kernel. If the operation is not applicable to this platform or the firmware is already 64-bit ready, it exits silently with a return code of zero. If the operation is applicable to this platform and the firmware is not 64-bit ready, it displays a descriptive message on the standard output and exits with a non-zero return code. The hardware platform documentation contains more information about the platforms that may need a firmware upgrade in order to run the 64-bit kernel. This flag overrides all other flags and must be used by itself. The following operands are supported: dev_path The path to a target device minor node, device nexus node, or device link for which device node configuration information is displayed The following exit values are returned: 0 No error occurred. non-zero With the -F option (SPARC only), a non-zero return value means that the output device is not a frame buffer. With the -x option, a non-zero return value means that the firmware is not 64-bit ready. In all other cases, a non-zero return value means that an error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWesu | +-----------------------------+-----------------------------+ |Interface Stability |Unstable | +-----------------------------+-----------------------------+ fuser(1M), modinfo(1M), sysdef(1M), attributes(5) Sun Hardware Platform Guide SPARC Only openprom(7D) The output of the prtconf command is highly dependent on the version of the PROM installed in the system. The output will be affected in potentially all circumstances. The driver not attached message means that no driver is currently attached to that instance of the device. In general, drivers are loaded and installed (and attached to hardware instances) on demand, and when needed, and may be uninstalled and unloaded when the device is not in use. On platforms, the use of prtconf -vp provides a subset of information from prtconf -v. The value of integer properties from prtconf -vp might require byte swapping for correct interpretation. 9 Aug 2005 prtconf(1M)
All times are GMT -4. The time now is 10:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy