The following has be reported by IBM LTC:
Warning message during vnc install by hvc0 or serial port
Steps to Reproduce:
1. In HMC, make the system boot to Open Firmware Prompt
2. In virtual console, type "boot /pci.../ethernet@1 vnc
3. Continue the installation process until it goes to start vnc server
Some warning message is displayed.
The VNC server now running.
Please connect to plinuxt19.ppc.cn.ibm.com:1 to begin the install...
Traceback (most recent call last):
File "/usr/bin/loadkeys", line 26, in ?
File "/usr/bin/loadkeys", line 22, in main
File "/usr/lib/anaconda/isys.py", line 229, in loadKeymap
return _isys.loadKeymap (keymap)
SystemError: (-22, 'Unknown error 4294967274')
XKB extension not present on :1
No warning message if we install the system in virtual console or
Current QU1 build (RHEL3-U1-Beta-RC-re1211.0-ppc-as-disc1-ftp.iso)
libstdc++.so.5 in stage2.img. So we make a new img file so that we can
install.The problem is caused when it call loadKeymap(gzFile stream)
9.1.1/isys/lang.c). It failed at ioctl(console, KDSKBENT, &entry).
If we boot locally with keyboard, the installer will ask us to set the
type. But if we boot from hvc0 or serial port, then the installer will
us to select it. But the gui.py will call id.keyboard.activate() to
Glen - please submit this to Red Hat. Thanks.
If you do this, what's the console type? (eg, if you were to login
after booting an installed system like this, what shows up as the tty
that you logged into?)
------ Additional Comments From firstname.lastname@example.org 2004-01-06 19:03 -------
It is hvc0 if I login from the virtual console. Because we select vnc
installation, we may connect to the system by HMC, Serial port.
----- Additional Comments From email@example.com 2004-01-19 00:13 -------
This defect still exist in the new-released RHEL3 Update1.
Made quiet in CVS
----- Additional Comments From firstname.lastname@example.org 2004-03-09 10:53 -------
So....this will be fixed in RHEL3 Update2 ? Please confirm. Thanks.
Yes, the fix is in the package being built for U2
----- Additional Comments From email@example.com 2004-03-23 07:09 -------
This defect still exist in the new-released RHEL3 Update2 Beta0316.
"install exited abnormally -- received signal 11"
----- Additional Comments From firstname.lastname@example.org 2004-04-23 09:15 -------
Will need new install media to test this. But raising to "high" so we have
visibility. Might be fixed in U2.
----- Additional Comments From email@example.com(prefers email via firstname.lastname@example.org) 2004-05-06 02:41 -------
Can someone check if U2 fixes this so we can close the bug ?
----- Additional Comments From email@example.com 2004-05-10 03:33 -------
Please verify this bug on QU2 and re-open this bug report if necessary.
----- Additional Comments From firstname.lastname@example.org 2004-06-10 23:42 -------
not fixed in U2.
********** output of HMC vterm **************
BOOTP: device /pci@400000000110/pci@2/ethernet@1
BOOTP: loc-code U0.1-P2-I2/E1
BOOTP: Cancel = ctl-C
BOOTP: wait 60 seconds for Spanning Tree ...
BOOTP S = 1
Load Addr=0x4000 Max Size=0x10000000
FINAL Packet Count = 8106
FINAL File Size = 4149809 bytes.
Elapsed time since release of system processors: 5379 mins 3 secs
zImage starting: loaded at 0x400000
Linux version 2.4.21-15.EL
console= not found, add
cmd_line is now vnc vncpassword=passwd method=nfs AUTOCONSOLE
Linux version 2.4.21-15.EL (email@example.com) (gcc version
20030502 (Red Hat Linux 3.2.3-34)) #1 SMP Thu Apr 22 00:11:22 EDT
Boot arguments: vnc vncpassword=passwd method=nfs AUTOCONSOLE
EEH: PCI Enhanced I/O Error Handling
could not set new controlling tty
trying to remount root filesystem read write... done
mounting /tmp as ramfs... done
install exited abnormally -- received signal 11
sending termination signals...done
sending kill signals...done
you may safely reboot your system
----- Additional Comments From firstname.lastname@example.org 2004-07-19 22:52 -------
This is targeted for RHEL3 QU4 (according to Mark Wisner). Thanks.
----- Additional Comments From email@example.com 2004-07-28 23:10 -------
I verified this on REHL3 U3 0722 test isos.
if I tyepd " boot /pci@400000000110/pci@2/ethernet@1 vnc vncpassword=password
method=nfs:172.30.1.140:/distros/rhel3 " at ok-prompt, I can do install via
vnc successfully. but still failed if typing
boot /pci@400000000110/pci@2/ethernet@1 vnc vncpassword=password method=nfs".
Redhat said that "method=nfs" is not a supported syntax in bug10075. So I
think we can close this bug.
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be
fixed). If any of these are still a problem, please reopen or file a new bug
against the release which they're occurring in so they can be properly tracked.