Bug 8129 - Upgrading Thinkpad 770Z has problems with display
Upgrading Thinkpad 770Z has problems with display
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-01-03 00:02 EST by Darren Rivey
Modified: 2015-01-07 18:40 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-24 13:17:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Darren Rivey 2000-01-03 00:02:45 EST
I am trying to upgrade a IBM Thinkpad 770Z from Redhat Linux 6.0 (fully
functional) to Redhat Linux 6.1.  The IBM Thinkpad has an unmodified
version of Redhat Linux 6.0 installed with a working XFree86 configuration
file using the SVGA X-Windows software.

I am using the most recent boot disk images (boot-RHEA-1999:044.img) and
the Redhat Linux 6.1 Standard Disk 1 in the CDROM drive.

The install stops before the X-Windows graphical display can start the
upgrade process.

pressing <ctrl><alt>F2 displays "bash#" where I can see that an X-Windows
session is runnint on tty1.

pressing <ctrl><alt>F3 displays logging details
pressing <ctrl><alt>F4 displays logging details

It is possible, on tty1, to kill the X-Windows setup by using
<ctrl><alt><backspace> and then restart the computer.

What information can I provide to help resolve this installation?
Comment 1 Jay Turner 2000-02-24 13:17:59 EST
If you are booting the installer with the "linux updates" command and you have
the CDROM in the drive when you boot, then you will indeed get a hang.  The
solution is to boot from the diskette and then wait until prompted to insert the
CDROM.  Please reopen this bug if you are seeing a different issue.

Note You need to log in before you can comment on or make changes to this bug.