Sponsored Content
Full Discussion: IBM AIX console pseries
Operating Systems AIX IBM AIX console pseries Post 303032878 by bakunin on Monday 25th of March 2019 06:30:25 PM
Old 03-25-2019
Quote:
Originally Posted by filosophizer
1- Do I need to have the console connected during the boot process ?
No. A "console" in UNIX speech is just a terminal, save for that it is attached directly (no network in between) to the system. One common security feature is to allow root to directly login only through the console, so that logging in directly as root needs a physical access to the system in question. So, the console is like the "main" terminal, but in every other regard it is just like any other terminal.

Quote:
Originally Posted by filosophizer
2- The console previously was graphics card LFT0 and now changed to TTY0
Well, look here:



Quote:
Originally Posted by filosophizer
Code:
lai0       Defined   1a-00         GXT135P Graphics Adapter
lai1       Defined   1a-08         GXT135P Graphics Adapter
lft0       Defined                 Low Function Terminal Subsystem

The graphics adapters that were there once are simply not there any more. Either they are both broken and the system cannot configure them even so much that they are recognized (one might have become dysfunctional that way but two at the same time is improbable) or they have been removed from the system. Delete these devices (rmdev) and run cfgmgr and i suppose they will not resurface. "Defined" means the defiitions for the adapter are still in the ODM but the device isn't there any more. It it would be then it would be "available".

This seems to be a rather old hardware (i remember having two GXT135P adapters in a R/6000 Model 43P-140), so it should have a serial connector. Attach a serial console to it and start with that. Note that at some point (i don't remember exactly when) the serial characteristics went from 9600, 8,1,N to 19200, 8,1,N, so if you have no luck with 9600 baud try 19200.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Installing AIX 4.3, pseries

I'm new with UNIX, i have a pseries server from IBM and i need to install AIX 4.3, i never used wyse terminal or AIX, i need help to know how to install it, i have the server and the wyse i get in into the aixterm, over com1 but i don't know wich command use or what to do to install it..... ... (0 Replies)
Discussion started by: Juan-ito
0 Replies

2. AIX

No Graphics Output in pSeries, AIX 5.3

Hi All -- I have an old 7028-6C1 which I'm using to learn AIX. The system didn't include a graphics card, so I connected via the serial port and performed a fresh install of AIX 5L V5.3. Later, I purchased a GXT135P (2849) graphics card, and added it to the system. When I ran diag, I was able... (2 Replies)
Discussion started by: i386tech
2 Replies

3. AIX

new IBM pseries and new disks

Hello Gurus, i'm quite new person in AIX world, actually i'm SAP consultant. But due to my job faced with AIX. Trying to configure new server for installation SAP. We have 4 disks one of them (hdisk3) has VG rootvg. How i can extend rootvg with another disk? i tried: # extendvg rootvg hdisk0... (2 Replies)
Discussion started by: sapbcer
2 Replies

4. Linux

Why does they use Linux on IBM pSeries

Anyone can help me answer the question. Why does they use Linux on IBM pSeries not AIX. I can't understand why, cause AIX is the best supporting from IBM pSeries. Tks you. (3 Replies)
Discussion started by: quan0509
3 Replies

5. AIX

IBM pSeries Power5 9111-285 1,9 GHz

Hi , I am planing to buy IBM pSeries Power5 9111-285 1,9 GHz but I am confused with few things. I would be happy if you could clear it up for me ? 1.Do I have to buy some license in order to create Lpars ? 2.Do I have to buy some license in order to use HMC , micro - partiocioning , VIOS... (4 Replies)
Discussion started by: phobus
4 Replies

6. AIX

IBM AIX on IBM Eseries & x series server

Hi, I want to know whether IBM AIX can be installed on the IBM e series and x series server hardware? Thanks & Regards Arun (2 Replies)
Discussion started by: Arun.Kakarla
2 Replies

7. AIX

IBM Power Pseries Open Firmware boot / VIOS POWERVM VET CODE

Hello, I installed PowerVM IVM Virtual I/O on P-550 but later found out that the machine isn't activated for CoD VET code for virtualization. So when booted , it goes into OPEN Firmware I/O Hosting requires a hosting partition boot not permitted exit called > ok Panel shows > IO... (3 Replies)
Discussion started by: filosophizer
3 Replies

8. AIX

IBM's pSeries 570 vs a 520 vs 550

Hidey Ho Folks, Looking to buy a pServer for playing around with the IBM side of things. Looked around for a bit and notice that there is a significant price gap for the used 570's (Single Units) vs the 520's and 550's that folks are selling. Curious what to watch out for in either case? And... (6 Replies)
Discussion started by: Devyn
6 Replies

9. AIX

AIX pseries install

Hello, I'm very rookie to AIX and attempting to install AIX. I have vio ready on the machine and don't know how to install OS? Inserted Volume 1 DVD into the ROM, don't know what to do next. Searched many forum but cant find the this basic thing. Please let me know how to install AIX on this... (4 Replies)
Discussion started by: pjeedu2247
4 Replies

10. AIX

IBM Virtual Machine OS on intel x86 and x64? IBM AIX OS on IBM Virtual Machine?

Hi There, I have zero information and zero knowledge for IBM virtual machine except Amazon cloud and VMware ESXi (Only Linux OS available). Anyone could provide me the following answer - Can IBM VM been deploy on X86 and X64 (Intel Chip)? If answer is yes any chance to deploy AIX OS... (13 Replies)
Discussion started by: chenyung
13 Replies
BOOT(8) 						      System Manager's Manual							   BOOT(8)

NAME
boot - connect to the root file server SYNOPSIS
/boot [ -fkm ] [ -uusername ] [ method!fs-addr ] DESCRIPTION
Boot is the first program run after a kernel has been loaded. It connects to the file server that will serve the root, performs any authentication needed to connect to that server, and exec(2)'s the init(8) program. It is started by the kernel, never run directly by the user. See booting(8) for information about the process of loading the kernel (and boot) into memory. Once loaded, the kernel initializes its data structures and devices. It sets the two environment variables /env/cputype and /env/terminal to describe the processor. It then binds a place-holder file server, root(3), onto / and crafts an initial process whose sole function is to exec(2) /boot, a binary which is compiled into root(3). The command line passed depends on the information passed from boot ROM to kernel. On the MIPS Magnum and SGI Power Series the command line passed to boot is the same as that given to the ROM monitor. On AT&T Gnots the command line is /68020/9gnot method!server On the Nextstation , no information is passed from the boot ROM or program. The command line is /68020/9nextstation On the PC, each line in the DOS file plan9.ini of the form name=value is passed to the boot program as an environment variable with the same name and value. The command line is /386/9pc method!server Boot must determine the file server to use and a method with which to connect to it. It must also set a user name to be used as the owner of devices and all console processes and an encryption key to be used when challenged. Boot will prompt for these. Method and address are prompted for first. The prompt lists all valid methods, with the default in brackets. root is from (il, tcp, hs, local)[il]: A newline picks the default. Other possible responses are method or method!address. To aid in automatic reboot, the default is automati- cally taken on CPU servers if nothing is typed within 15 seconds. The other interactions depend on whether the system is a terminal or a CPU server. Terminal The terminal must have a username to set. If none is specified with the -u option, boot will prompt for one on the console: user: The user will also be prompted for a password to be used as an encryption key on each attach(5): password: With most methods boot can now connect to the file server. However, with the serial line methods 9600 and 19200, the actual mechanics of setting up the complete connection are too varied to put into the boot program. Instead boot lets the user set up the connection. It prints a prompt on the console and then simulates a dumb terminal between the user and the serial line: Connect to file system now, type ctrl-d when done. (Use the view or down arrow key to send a break) The user can now type at a modem or a Datakit destination please: interface to set up the connection to a TSM8 card. At Murray Hill, a user would type nj/astro/plan85 at this point. When the user types a control-D, boot stops simulating a terminal and starts the file sys- tem protocol over the serial line. Once connected, boot mounts the root file system before / and makes the connection available as #s/boot for subsequent processes to mount (see bind(2)). Boot completes by exec(2)'ing /$objtype/init -t. If the -m option is given it is also passed as an option to init. If the kernel has been built with the cache file system, cfs(4), the local disk partition /dev/[sh]d[01]cache exists, and the root file system is from a remote server, then the kernel will insert a user level cache process between the remote server and the local namespace that caches all remote accesses on the local partition. The -f flag commands cfs to reformat the cache partition. CPU Servers The user owning devices and console processes on CPU servers and that user's domain and encryption key are read from NVRAM on all machines except PC's. PC's keep the information in the disk partition /dev/[sh]d[01]nvram. If a -k option is given or if no stored information is found boot will prompt for all three items and store them. password: authid: bootes authdom: research.att.com The key is used for mutual authentication of the server and its clients. The domain and id identify the owner of the key. Once connected, boot behaves as on the terminal except for exec(2)'ing /$objtype/init -c. Booting Methods The methods available to any system depend on what was compiled into the kernel. The complete list of booting methods are listed below. cyc connect via a point-to-point fiber link using Cyclone boards. If specified, the address must be the number of the Cyclone board to be used, default 0. il connect via Ethernet using the IL protocol. tcp connect via Ethernet using the TCP protocol. This method is used only if the initial file server is on a Unix system. hs connect via Datakit using the high speed Datakit card. incon connect via Datakit using the Incon interface. 9600 connect via Datakit using the serial interface at 9600 baud. 19200 connect via Datakit using the serial interface at 19200 baud. local connect to the local file system. For the il and tcp methods, the address must be a numeric IP address. If no address is specified, a file server address will be found from another system on the network using the BOOTP protocol and the Plan 9 vendor-specific fields. For the Datakit methods, hs, 9600, 19200, and incon, the address must be specified and must be a relative path name to the file server. If no address is specified, the address Nfs is used. FILES
#s/boot SOURCE
/sys/src/9/boot SEE ALSO
root(3), bootp(8), init(8) BOOT(8)
All times are GMT -4. The time now is 01:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy