Description of problem:
An attempt to install RHEL 6 beta 1 using the i386 DVD fails when the installation hangs after the Probing EDD step on a DELL Optiplex 740 at latest BIOS revision.
initrd.img loads OK and says ready. The EDD probe apparently succeeds in that
it says ok, but then the installation hangs with no response to the keyboard
and no further output. It still hangs with edd=off.
The only way I was able to install was to use the argument:
as argument at install time. (I have 4 GB or RAM)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Load i386 RHEL 6 beta 1 DVD
2. Boot machine
3. Select install or upgrade
Should install without needing mem= argument.
This seems to be similar or the same as bug 538911 in fedora 12.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
This is still a problem with RHEL 6, beta 2 DVD. The error message I am seeing with RHEL 6 beta 2 DVD is:
(lots of dots)
Not enough memory to load specified image.
giving mem=4294967296 as a kernel argument still works around the problem.
This is a problem on the DELL Optiplex 740 workstation with RHEL 6 64 bit workstation / Client beta 2 DVD.
Can you attach a sosreport log to this BZ ?
Created attachment 430170 [details]
sosreport report file
Here is the sosreport report file from a Optiplex 740 workstation. It was
installed with RHEL 6 beta 2 DVD. It seems to happen with 32 bit or 64 bit install. This report ran on a 64 bit install. In order to install I had to use the mem=4294967296 as a kernel argument.
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
(In reply to comment #6)
> Created attachment 430170 [details]
> sosreport report file
> Here is the sosreport report file from a Optiplex 740 workstation. It was
> installed with RHEL 6 beta 2 DVD. It seems to happen with 32 bit or 64 bit
> install. This report ran on a 64 bit install. In order to install I had to use
> the mem=4294967296 as a kernel argument.
Are you still available to help on this issue.
If yes, would love a serial console log from the sytem. (If that is possible)
Thanks for checking on this...
I don't think its a problem with the final RHEL 6 release. I have done some installs with the Optiplex 740 with RHEL 6.0 final and it works ok. I didn't have to enter any special kernel options.
Sorry. I was wrong. This is still a problem. It turns out there is a "Optiplex 740" and a "Optiplex 740 Enhanced." I only had access in my building to a "Optiplex 740 Enhanced." But the problem is still happening on a "Optiplex 740" with the Red Hat Enterprise 6.0 install DVD. Adding the mem=4294967296 as arguments in anaconda still works as a workaround for me. (Machine has 4 GB)
The computer is connected to a monitor and keyboard / mouse (USB) so I'm not sure how to attach a serial console log from the system. can you explain what I need to do? I can try to create it.
Ok. I ordered a serial null cable online and I have the cable. What do I need to do to get the info you need to fix this? I tried opening "minicom" on another linux computer and I added "serial" to the boot options in the boot DVD for RHEL 6 but it does not appear to divert the "dots" to go to the serial port. (At least from what I can see within minicom on computer #2)
Is there some howto or instructions on how to create a serial console log? Do I need further arguments on the kernel options after pressing "tab" ?
(In reply to comment #12)
> Ok. I ordered a serial null cable online and I have the cable. What do I need
> to do to get the info you need to fix this? I tried opening "minicom" on
> another linux computer and I added "serial" to the boot options in the boot DVD
> for RHEL 6 but it does not appear to divert the "dots" to go to the serial
> port. (At least from what I can see within minicom on computer #2)
> Is there some howto or instructions on how to create a serial console log? Do I
> need further arguments on the kernel options after pressing "tab" ?
Add to the Server kernel command line :
The catcher i.e. the other end of the null modem cable you could configure minicom to open /dev/ttyS0 with the same baudrate settings.
Created attachment 483295 [details]
serial console log
I tried to do as suggested but it did not work.
Here is what I did.
I inserted a Red Hat Enterprise Linux 6 DVD and booted off of it.
I pressed "tab" when the SYSLINUX GUI came up.
I appended to the end of the arguments console=tty0 console=ttyS0,115200,8n1
and then pressed "Enter" but the dots still go to the VGA screen!
So I went ahead and installed the machine with mem=XXXXX and text keywords
and then I edited the GRUB menu at bootup and added to the kernel lines:
and this did generate output in minicomm but I'm guessing this isn't what
you were looking for, correct? (because at this point the OS has been installed with workarounds)
If someone can tell me how to do this off the DVD boot media rather than the hard disk I can try to provide the info you wanted. However if this is what was asked for then I guess this will help?
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Looks like this got fixed in RHEL 6.3 install media. Thanks!
(In reply to Gary Gatling from comment #17)
> Looks like this got fixed in RHEL 6.3 install media. Thanks!