Bug 82428 - Graphical install fails on Latitude
Summary: Graphical install fails on Latitude
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda
Version: phoebe
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-01-22 01:25 UTC by adam.huffman
Modified: 2007-04-18 16:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-02-11 17:49:40 UTC


Attachments (Terms of Use)

Description adam.huffman 2003-01-22 01:25:33 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030115

Description of problem:
When attempting to install Phoebe2 on a Dell Latitude C800 with ATI Rage
Mobility M4 chipset, the installer fails to start an X server and runs in text
mode.  Graphical installation worked on 8.0 and Phoebe 1.

The message in /tmp/X.log was that modules glx and record could not be loaded
because they could not be found.  Then a message saying that no valid VESA modes
were found and hence there were no usable screens.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install from CDs
2.
3.
    

Actual Results:  Graphical install fails and the installer reverts to a text install

Expected Results:  Graphical install should have proceeded

Additional info:

Comment 1 Paul Jenner 2003-01-22 13:46:34 UTC
Is this a duplicate of #80384?

Comment 2 adam.huffman 2003-01-22 14:08:02 UTC
Yes, although this is with the second beta, not the first, so the problem is
still there.

Comment 3 Michael Fulbright 2003-01-22 17:29:18 UTC
Find out what the native resolution of your LCD is and add this when you boot:

linux resolution=<native resolution>

For example, if you laptop does 1024x768, use

linux resolution=1024x768

when you boot the installer.

I have a workaround for this but it is not in the latest beta.

Comment 4 Michael Fulbright 2003-02-11 17:49:40 UTC
Closing due to inactivity.

Comment 5 adam.huffman 2003-03-10 16:35:02 UTC
Just to confirm that this problem didn't occur when installing the latest beta.


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