Bug 50633 - X Customization hangs after test screen resolution
Summary: X Customization hangs after test screen resolution
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.3
Hardware: i586
OS: Linux
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-08-01 19:27 UTC by Danny Trinh
Modified: 2007-04-18 16:35 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-20 19:29:01 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Danny Trinh 2001-08-01 19:27:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt)

Description of problem:
During install Fairfax beta3 (using text mode), X customization hangs 
after I test screen resolution. The installation process can't be 

How reproducible:

Steps to Reproduce:
1.Boot from CD1, select text mode
2.At the very end of installation process, choose to customize the X, run 
test screen resolution.
3.The screen will be hung up at X Customization screen.

Actual Results:  Unable to finish installation process by using text mode. 
However, I can finish the installation process by using GUI mode.

Expected Results:  Must be able to finish the installation process with 
the ability to configure X.

Additional info:

Comment 1 Glen Foster 2001-08-01 19:37:46 UTC
What specific video hardware (controller and monitor) are you using, and can you
give us the PCI IDs for them, please?

Comment 2 Danny Trinh 2001-08-01 19:45:25 UTC
I saw this bug in two system (PE1300, PE1400). Video chipset are embeded.

 -Video Card: ATI Mach64 3D Rage IIC
 -Video RAM: 2048

 -Video card: ATI Mach64
 -Video RAM: 4096

Comment 3 Danny Trinh 2001-08-01 19:47:45 UTC
Oops, I use Dell's P780 monitor. I think this is not necessary, because there 
is no problem when I use GUI method to install.

Comment 4 Michael Fulbright 2001-08-01 20:00:57 UTC
The X configuration is the last thing done during the install. Any bootloader
and boot floppy has already been written. You should be able to reboot into the
system and run Xconfigurator to setup X.

The same code is used to test an X configuration in GUI and TUI modes.  I have
seen bad behavior of XFree86 4.x drivers from time to time.

Does it happen in text mode if you boot the installer using:

nofb text


Comment 5 Danny Trinh 2001-08-01 21:14:43 UTC
Yes, It happens in text mode if you boot the installer using:
nofb text.

Xconfigurator works OK.

Comment 6 Michael Fulbright 2001-08-06 22:14:13 UTC
Brent - 

 Please try to reproduce with our closest hardware.

Comment 7 Brent Fox 2001-08-08 20:32:50 UTC
I've tried unsuccessfully on a PowerEdge 6300 to reproduce this behavior.  It
has an embedded ATI Rage 128 graphics chip with 2048kb of RAM.  Testing the X
configuration in text mode at 16 bit color depth and 1024x768 resolution works
fine for me.  Were you trying different resolutions or color depths perhaps?

Comment 8 Brent Fox 2001-08-08 20:37:54 UTC
The following tests I tried were:
8 bit color:

16 bit color:

Comment 9 Danny Trinh 2001-08-08 21:10:35 UTC
I use 16 bit color depth and 1024x768 resolution. Only PE1300, PE1400 have this 
 -Embedded Video Card: ATI Mach64 3D Rage IIC
 -Video RAM: 2048

 -Embedded Video card: ATI Mach64
 -Video RAM: 4096

The other servers using ATI chip also, but they work fine.

Comment 10 Bill Nottingham 2001-08-09 15:38:02 UTC
Brent, msf: we have pe1300/pe1400 in the lab. Check with bobm.

Comment 11 Brent Fox 2001-08-09 19:55:33 UTC
Ok, I got a PE1400 from bobm and I could not reproduce the problem.  The
installer was unable to probe the monitor because it ran through the KVM.  The
generic monitor setting would only allow me to test at 640x480, but this worked
ok.  Then, I manually set the monitor to "Dell P991", and then I could test at
all available resolutions.  The graphics card was an ATI Mach64 with 4096 kb of
video RAM.

I don't know what else to do on this bug but resolve as 'worksforme'.

Comment 12 Danny Trinh 2001-08-13 14:15:05 UTC
I retested and duplicated this problem every time ( 3 times).
Below steps are what I did:
- Choose text mode installation.
- At the "X Customization" screen, select:
   - Default Desktop: KDE
   - Default Login: Text
- Use cursor to select "Test" button, then press Enter.
- Use mouse click on "yes"
- The "X Customization" screen come back. And It hung up.

Comment 13 Brent Fox 2001-08-13 23:16:21 UTC
I tried again with today's build on the PE1400 and again I could not reproduce.
 Everything works ok for me.  I don't know what steps to take next...

Comment 14 Bill Nottingham 2001-08-14 05:37:42 UTC
What kind of mouse?

Comment 15 Danny Trinh 2001-08-14 15:24:03 UTC
I'm using Microsoft IntelliMouse.

Comment 16 Brent Fox 2001-08-15 04:43:55 UTC
I was using a two button Dell mouse (made by Logitech).  Can you try with a
non-wheel mouse?

Comment 17 Danny Trinh 2001-08-15 15:34:35 UTC
Yes, It works. So, what's wrong with Microsoft Intellimouse?

Comment 18 Brent Fox 2001-08-15 16:06:25 UTC
I've seen this before...are you specifically selecting Microsoft IntelliMouse in
the mouse selection screen?  I've seem some IntelliMice go completely bonkers in
X if they are set to PS/2 instead of IMPS/2.
Is it a PS/2 mouse or USB?  If it's ps/2, I'm not sure there's much we can do.

Comment 19 Danny Trinh 2001-08-16 18:29:06 UTC
-Either generic mouse, or intellimouse, ---> same result.
- PS2 mouse.

Comment 20 Brent Fox 2001-08-18 15:44:30 UTC
I have three old IntelliMice at home that I'll bring to work on Monday and see
if I can duplicate this.  One is an OEM version and two are retail.  You can
tell the difference because the OEM versions are very smooth while the retail
versions have more of a matte finish.  Which does yours have?

Do you happen to know how old your mouse is?  My two retail versions say that
they are Version 1.1A.  The OEM version has no information on it.  Do you have
another IntelliMouse you could try?

Comment 21 Danny Trinh 2001-08-20 19:28:56 UTC
I have a retail version.
Any way, It seems to work with RC1. I don't know what changed between beta3 and 
RC1, but it works.
We can close this issue.

Comment 22 Brent Fox 2001-08-21 17:54:57 UTC
I guess the problem was with the X server somehow.  There weren't any changes to
anaconda that would account for differences between beta 3 and RC1.  Bugs that
just disappear always worry me, because you don't know when they'll reappear.  I
guess we'll leave this one alone, though.

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