The following has be reported by IBM LTC:
Installation of RH AS 3.0 using Graphical installation (default) fails.
Please fill in each of the sections below.
I was trying to install in graphical mode RHAS 3.0 Beta 1 and it fails.
It shows the following information in the screen after the failure:
Running anaconda, the Red Hat Enterprise Linux system installer - please wait...
Probing for video card: Matrox Millennium G400
Probing for monitor type: Unknown monitor
Probing for mouse type: Generic - Wheel Mouse (PS/2)
Attempting to start native X server
Waiting for X server to start...log located in /tmp/X.log
1...2...3..4..5... X server started successfully.
The application 'mini-wm' lost its connection to the display :1.0;
most likely the X server was shut down or you killed/destroyed
install exited abnormally
sending termination signals...done
sending kill signals...done
you may safely reboot your system
The machine I was using is an IBM machine 6887-32U with
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
cpu MHz : 664.568
cache size : 256 KB
I was able to install 2 previous ALPHA releases of RH ES 3.0
in the same machine.
Steps to Reproduce:
1.Boot the machine with cd 1, choose graphical installation (Default)
2.put all requested info (IP address, packages, etc ....)
3.As soon as it starts installing the packages it fails and gives the error.
Installation of Linux using graphical mode fails.
Linux to be installed.
Any error messages on vt3/vt4?
correct all usage of "RH AS 3.0" to be "RHEL 3"
please also map 6887-32U to a model name so we may try to reproduce on local
------ Additional Comments From firstname.lastname@example.org 2003-07-08 11:11 -------
Looks like that may be PC 300 or PC 700 Intellistation ?
I found this page
Other 6887 are PC 750 if I search on
but I can't find 6887-32U
Aldo, can you please update comments with the name of the PC model. Thanks.
------ Additional Comments From email@example.com 2003-07-08 11:34 -------
I am sorry I Guess I incorreclty typed the typ of the machine.
It is IBM IntelliStation E Pro (Type 6867)
------ Additional Comments From firstname.lastname@example.org 2003-07-08 12:12 -------
Glen / Greg
Please tell RedHat detailed spec for machine found on this page
It appears this machine has 128MB of RAM. If you try installing by putting
'linux text' on the boot command line we can determine if the problem is due to
the graphical installation running out of RAM.
------ Additional Comments From email@example.com 2003-13-08 17:46 -------
Yes, I was abel to install this version of RH Linux using text mode.
*** This bug has been marked as a duplicate of 100453 ***
------ Additional Comments From firstname.lastname@example.org 2003-28-08 15:25 -------
I think I have hit this problem on iSeries as well. I saw the following results
on a partition running our LVT test suite:
Out of Memory: Killed process 12230 (startlvt).
Out of Memory: Killed process 12228 (lvt.nfs.local).
./startlvt: line 714: 12228 Terminated $CMD >>$RUNOUTPUT_FILE
Out of Memory: Killed process 12242 (lvt.nfs.local).
Out of Memory: Killed process 12251 (startlvt).
Out of Memory: Killed process 12244 (grep).
An error occurred at: Mon Aug 25 15:51:17 CDT 2003 -
Out of Memory: Killed process 12259 (startlvt).
./startlvt: line 549: [: -lt: unary operator expected
./startlvt: line 691: [: -ne: unary operator expected
[ PASSED ]
Out of Memory: Killed process 12266 (startlvt).
Out of Memory: Killed process 12264 (lvt.scp.local).
./startlvt: line 714: 12264 Terminated $CMD >>$RUNOUTPUT_FILE
Out of Memory: Killed process 12278 (lvt.scp.local).
Out of Memory: Killed process 12280 (grep).
Out of Memory: Killed process 912 (bash).
Red Hat Enterprise Linux release 2.9.5AS (Taroon)
Kernel 2.4.21-1.1931.2.393.ent on an ppc64
Out of Memory: Killed process 12679 (slocate.cron).
Out of Memory: Killed process 12682 (updatedb).
Out of Memory: Killed process 12783 (sshd).
Out of Memory: Killed process 13160 (slocate.cron).
Out of Memory: Killed process 13163 (updatedb).
As you can see, many of the processes started by our startlvt script were being
Here is what I saw in /proc/meminfo.
[root@doclinux root]# cat /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 743944192 738385920 5558272 0 356352 16756736
Swap: 756715520 3985408 752730112
MemTotal: 726508 kB
MemFree: 5428 kB
MemShared: 0 kB
Buffers: 348 kB
Cached: 14280 kB
SwapCached: 2084 kB
Active: 2068 kB
ActiveAnon: 752 kB
ActiveCache: 1316 kB
Inact_dirty: 740 kB
Inact_laundry: 0 kB
Inact_clean: 14024 kB
Inact_target: 3364 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 726508 kB
LowFree: 5428 kB
SwapTotal: 738980 kB
SwapFree: 735088 kB
I am going to rerun my test using the 411 kernel drop and see if I can avoid
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.