Bug 26453 - Testing X configuration fails erroneously
Summary: Testing X configuration fails erroneously
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
Whiteboard: Florence Gold
Depends On:
TreeView+ depends on / blocked
Reported: 2001-02-07 12:12 UTC by Phil Venton
Modified: 2007-04-18 16:31 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2001-02-16 17:04:58 UTC

Attachments (Terms of Use)

Description Phil Venton 2001-02-07 12:12:46 UTC
Dual P-II 400, on QDI BrilliantIV (440BX, BIOS version 3 beta)
Diamond V770 Ultra (TNT2 ultra chipset)
Samsung SL900+ (using probed DDC syncs)
256megs RAM
6 Gig Maxtor over UDMA/33 on /dev/hdc
USB mouse (Razer Boomslang 2K)

Install parameters:
Custom install, all packages.
Automatic partitioning
X selected at 1280x1024, 24 bit.
Dual-booting with Win2K (on /dev/hda1, whole disk)

Testing the X config fails with "Explicit kill or server shutdown".
However, the resulting XF86Config-4 file is perfect, and startx (or booting
to init 5) works flawlessly post-install.

Comment 1 Michael Fulbright 2001-02-07 16:27:32 UTC
Assigning to a developer.

Comment 2 Phil Venton 2001-02-07 17:44:45 UTC
I should also mention, in case it is relevant:

The V770 has 32 megs video RAM, but anaconda detected it as 16.  I changed it to
32 from the dropdown.

I will hammer on this with some other settings when I have free time, and see
what the reproducable envelope is.

Comment 3 Brent Fox 2001-02-07 18:28:47 UTC
Can you go to VC2, run ddcprobe, and post the output?  That way we can tell how
much memory the card thinks it has.

Comment 4 Glen Foster 2001-02-08 16:01:06 UTC
We (Red Hat) should really try to resolve this before next release.

Comment 5 Tim Waugh 2001-02-09 18:04:27 UTC
You might also want to look at /tmp/XF86Config-4 (or whatever it's called after
clicking on the test button, to see what the differences are between that and
the installed Xconfigurator config file.

Comment 6 Brent Fox 2001-02-16 17:04:54 UTC
We think this has been fixed in the latest internal builds.  There was a problem
in the way we were handling memory.  Basically, testing X caused a spike in
memory usage, and the kernel was killing the X process because it thought it had
run out of memory.  Please reopen if the problem persists.

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