Description of problem:
Anaconda hangs on initialisation crahing computer. Not able to switch to tty2.
Version-Release number of selected component (if applicable):
redhat 6 beta iso
Steps to Reproduce:
1.attempt graphical install
2.select local cd - anaconda starts
3.x starts (pointer available)
On a dell latitude e4200 laptop
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
Attempted net install using boot.iso
install fails at same point - anaconda manages to draw the background of first screen after Xserver starts then there is a hard crash which locks up the computer showing a white square against a black background
fedora 13 i386 anaconda 13.42 works
fedora 12 i386 anaconda 12.46 works
RHEL 6 beta x86_64 anaconda 188.8.131.52 works
RHEL 6 beta i386 anaconda 184.108.40.206 fails as descibed above
If you can get to tty2 could you copy out the /tmp/*log files and attach them here?
(In reply to comment #5)
> If you can get to tty2 could you copy out the /tmp/*log files and attach them
Computer hard locks and no alternative consoles are available
computer has to be switched off using >4seconds on power button as sysrq REISUB doesn't work either
Can you hook the system up to a serial console?
nope, no usb to serial available
Beta 2 testing as follows
Upgrade or install using 1st option still fails at same point
install using basic video driver however gets past crash point and proceeds normally
i can only surmise that the crash may be caused by the implementation of the intel video driver in the kernel of the anaconda of RHEL 6 beta2
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. **
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.
This has been stale for over 14 months and we are at RHEL6.4 now - if you can
reproduce this with recent RHEL, please file a new BZ.