Recommended
In this guide, we will describe some possible causes that can cause the sudo powermt display initialization error, and then I will provide possible fixes that you can try to resolve the issue.
“There are no stupid questions” – do you know this cliché? This part of pimp-my-rig reloaded provides answers to tricky questions. Email them and I’ll post those answers here. If you have a better answer, be sure to email us about it.
Recommended
Is your PC running slow? Do you have problems starting up Windows? Don't despair! Fortect is the solution for you. This powerful and easy-to-use tool will diagnose and repair your PC, increasing system performance, optimizing memory, and improving security in the process. So don't wait - download Fortect today!
Q. I was working on an AIX host when I encountered “initialization errors”. when switching from “powermt display”. So this error occurs when running as sudo. But I felt like I was running root, hoping things would be different as superuser, but it’s not. Below are the slippages I’ve encountered.
[secure email] > sudo powermt displayInitialization error. [Secure Email] > see below.Password: [secure email] > Power DisplayInitialization error.
A. It worried me even more. The error was also saved as a superuser of type “root”. I am not very familiar with AIX per se, so I tried to use the reliable command that has always been helpful in regards to Solaris – truss. So, I hit the jackpot!
This is the result of your current order.
[protection Email] > powermt truss displayexecve ("/ usr / sbin / powermt", 0x2FF22C94, 0x2000FB38) Argument: 2__loadx (0x03480000, 0x2FF22A70, 0x00000140, 0x10000000, 0x2000033D) = 0x00000000__loadx (0x0C000000, 0xF020AABC, 0x00000000, 0xF0317004, 0xF020A460) = 0x00000000thread_init (0x0000000000000000, 0x00000000D0117CCC) meanssbrk (0x00000000) = 0x20018404vmgetinfo (0x2FF22978, 7, 16) = 0sbrk (0x00000000) matches 0x20018404vmgetinfo (0x2FF22440, 7, 16) = 0sbrk (0x00000000) matches 0x20018404sbrk (0x0000000C) = 0x20018404__libc_sbrk (0x00000000) matches 0x20018410Getrpid (-1, -1, -265185236) is 253984_getpid () = 253984getprocs (0x20018ED8, 920, 0x00000000, 0, 0xF03173B0, 1) means 1appulimit (1005, 0) equals 0x20029000_thread_self () implies 610395thread_setmystate (0x00000000, 0x2FF225D0) = 0thread_setmystate (0x2FF222C0, 0x2FF225C8) is 0_sigaction (3.0x2FF228F8, 0x2FF22908) = 0_sigaction (4.0x2FF228F8, 0x2FF22908) = 0_sigaction (5, 0x2FF228F8, 0x2FF22908) matches 0_sigaction (6, 0x2FF228F8, 0x2FF22908) = 0_sigaction (7, 0x2FF228F8, 0x2FF22908) = 0_sigaction (8, 0x2FF228F8, 0x2FF22908) means 0_sigaction (10, 0x2FF228F8, 0x2FF22908) equals 0_sigaction (11, 0x2FF228F8, 0x2FF22908) = 0_sigaction (12, 0x2FF228F8, 0x2FF22908) = 0_sigaction (36, 0x2FF228F8, 0x2FF22908) = 0_sigaction (39, 0x2FF228F8, 0x2FF22908) equals 0open ("/ unix", O_RDONLY | O_LARGEFILE) = 3kioctl (3, 22528, 0x00000000, 0x00000000) Err # 25 ENOTTYkioctl (3, 22528, 0x00000000, 0x00000000) Err # 25 ENOTTYkread (3, "01F7 005 IFC aE6 0 0 0 0" .., 4096) equals 4096klseek (3, 0, 0, 0x00000001) equals 0klseek (3, 0, 13942134, 0x00000000) equals 0kread (3, " 0 0 0 0 0 0 1 0 0 0 004" ...., 4096) = 4096klseek (3, 0, 0, 0x00000001) = 0klseek (3, 0, zero, 0x00000001) = 0klseek (3, 8, 15041308, 0x00000000) = 0kread (3, "_ _ m u n h 0 _ _ m u l" .., 4096) = 4096klseek (3, 9, 0, 0x00000001) equals 0klseek (3, 0, 13942170, 0x00000000) matches 0kread (3, " 0 0 0 0 0 0 180 0 0 0 v" ...., 4096) 4096Klseek (3, = 0.8, 0x00000001) = 0kread (3, " 0 0 0 001 XF1B8 0 0028E" ...., 4096) = 0, 4096klseek (3, 8, 0x00000001) equals 0kread (3, " 0 0 0 001 XF5 H 0 0 tE6" .., 4096) = 4096klseek (3, 0, 8, 0x00000001) = 0kread (3, " 0 0 0 001 XF8D8 0 0028E" .., 4096) matches 4096klseek (3, 0, 8, 0x00000001) equals 0kread (3, " 0 0 0 001 XFC h 0 00F12" .., 4096) = 4096klseek (3, 0, 6, 0x00000001) = 0kread (3, " 0 0 0 001 XFFF8 0 0028E" .., 4096) implies 4096klseek (3, 0, 8, 0x00000001) equals 0kread (3, " 0 0 0 001 Y0388 0 0149F" .. 4096) so = 4096klseek (3, 0, main, 0x00000001) = 0kread (3, " 0 0 0 001 Y0718 0 0028E" .., 4096) matches 0, 4096klseek (3, 8, 0x00000001) implies 0kread (3, " 0 0 0 001 Y nA8 0 0028E" .., 4096) = 4096klseek (3, 0, env. 8, 0x00000001) = " 0 0 0 001 0kread (3, Y0E 8 0 019AC ".., 4096) equals 4096klseek (3, 0, 8, 0x00000001) 0Kread (3, = " 0 0 0 001 Y11C8 0 01E
As the above error shows, powermt considered looking for the “CuDv” report, which is an ODM object. So I tried the trick I mentioned earlier in the FAQ: Path Errors in AIX ODM Commands.
[email security] > cd / etc / objrepos [Secure EmailEmail] > Power DisplaySymmetrix Exam Devices = 138Number of CLARiiON LUNs = 0Hitachi reasonable number of devices = 0Logical number of Invista devices = 0HP Vista LUNs = 0Logical amount of resources = 0HP HSx LUNs = 0================================================== = = =============================----- Host Bus Adapter --------- ------ I / O Paths ----- ------ Statistics ------### A summary of the hardware I / O paths per second per second. Total Q-IO Errors================================================== = = ============================= 0 fscsi0 optimal 138 0 - 0 0 unique fscsi2 amazing 138 8-7 0
It felt like déja vu again. But now I know that in case of errors it helps to change directory to / etc / objrepos before running privileged commands.
Speed up your PC today with this easy-to-use download.
Blad Inicjalizacji Wyswietlacza Sudo Powermt
Error De Inicializacion De Pantalla De Sudo Powermt
Sudo Powermt Display Initieringsfel
Oshibka Inicializacii Displeya Sudo Powermt
Sudo Powermt 디스플레이 초기화 오류
Erreur D Initialisation De L Affichage Sudo Powermt
Sudo Powermt Weergave Initialisatiefout
Errore Di Inizializzazione Del Display Sudo Powermt
Sudo Powermt Display Erro De Inicializacao
