Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 61483 - X11 on RH 7.2 can't be installed correctly.
X11 on RH 7.2 can't be installed correctly.
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-03-20 09:47 EST by Need Real Name
Modified: 2007-04-18 12:41 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:48:36 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
it's an error trace reported by anaconda when RH7.2 fails probing monitor at setup time (2.00 KB, text/plain)
2002-03-20 09:49 EST, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2002-03-20 09:47:40 EST
Description of Problem:
RH 7.2 can't install X windows, especifically hangs probing monitor 
configuration, when RH 7.2 is installed without X conf. test, can't start X 
(startx fails) and Xconfigurator can't complete monitor configuration, after 
recognize the video card ends with an error(X Server doesn't exist).

Anaconda  reported an error trace for bug reporting, it's atached to this 

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

How Reproducible:

Install RH 7.2 on Pentium II 300 / video card : Sis 6323(i'm not sure ), 8MB 
Monitor: LG StudioWorks 44 i
and run monitor test. 
run Xconfigurator after installation.

Steps to Reproduce:

Actual Results:
hangs probing monitor configuration.

Expected Results:
show a test screen 

Additional Information:
review atached file.
Comment 1 Need Real Name 2002-03-20 09:49:23 EST
Created attachment 49144 [details]
it's an error trace reported by anaconda when RH7.2 fails probing monitor at setup time
Comment 2 Michael Fulbright 2002-03-21 12:01:21 EST
The error report seems truncated - did you attach the entire error report?
Comment 3 Need Real Name 2002-03-21 15:31:37 EST
Yes I did. Any way I send it again pasted on this email:
File: "anacdump.txt"

Traceback (innermost last):
  File "/usr/bin/anaconda", line 620, in ?
  File "/usr/lib/anaconda/gui.py", line 350, in run
  File "/usr/lib/anaconda/gui.py", line 778, in run
  File "/usr/lib/python1.5/site-packages/gtk.py", line 2608, in mainloop
  File "/usr/lib/python1.5/site-packages/gtk.py", line 125, in __call__
    ret = apply(self.func, a)
  File "/usr/lib/anaconda/iw/xconfig_gui.py", line 63, in testPressed
  File "/usr/lib/anaconda/xf86config.py", line 1012, in test
OSError: [Errno 2] No existe el fichero o el directorio

Local variables in innermost frame:
serverPath: /usr/X11R6/bin/XF86_SVGA
serverflags: None
root: /mnt/sysimage/
logFile: /tmp/X-Test.log
serverpid: 0
spawn: 0
self: <xf86config.XF86Config instance at 8343fc8>
fbmonsect: None
manmodes: {'16': ['800x600']}
args: ['/usr/X11R6/bin/XF86_SVGA', '-
xf86config', '/tmp/XF86Config.test', ':9', 'vt6']
servername: XF86_SVGA
f: <closed file '/mnt/sysimage//tmp/XF86Config.test', mode 'w' at a105408>
err: 24
# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

    RgbPath	"/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.

    FontPath   "unix/:7100"

Package Group selection status:
Base: 1
Printing Support: 0
Classic X Window System: 1
X Window System: 1
Laptop Support: 0
Spelling: 0
KDE: 1
Sound and Multimedia Support: 0
Network Support: 0
Dialup Support: 0
Messaging and Web Tools: 0
Graphics and Image Manipulation: 0
Network Server: 0
News Server: 0
NFS File Server: 0
Windows File Server: 0
Anonymous FTP Server: 0
SQL Database Server: 0
Web Server: 0
Router / Firewall: 0
DNS Name Server: 0
Network Managed Workstation: 0
Authoring and Publishing: 0
Emacs: 0
Utilities: 0
Legacy Application Support: 0
Software Development: 0
Kernel Development: 0

This is the generated X-Text.log file:

Gdk-ERROR **: BadIDChoice (invalid resource ID chosen for this connection)
  serial 799380 error_code 14 request_code 55 minor_code 0
Gdk-ERROR **: BadIDChoice (invalid resource ID chosen for this connection)
  serial 799381 error_code 14 request_code 129 minor_code 1

Well, I hope you can solve the problem.
Comment 4 Michael Fulbright 2002-03-21 16:41:16 EST
It might be possible if there were read errors during the install that the file
would be missing, as the error report says.  Are you doing a CDROM based install?
Comment 5 Need Real Name 2002-03-21 19:16:59 EST
Yes of course, I'm installing from CD-ROM.
Comment 6 Michael Fulbright 2002-03-27 01:51:47 EST
Could you please look at the error log on the floppy disk and see if there are
any errors like:

<4>hdd: irq timeout: status=0xd0 { Busy }
<4>hdd: ATAPI reset complete
<4>hdd: irq timeout: status=0xd0 { Busy }
<4>hdd: ATAPI reset complete
<4>end_request: I/O error, dev 16:40 (hdd), sector 456424
<4>hdd: irq timeout: status=0xd0 { Busy }
<4>hdd: ATAPI reset complete
<4>hdd: irq timeout: status=0xd0 { Busy }

These would indicate a bad CD.  Since the entire error log will not attach to
the bug properly I cannot verify this myself.
Comment 7 Need Real Name 2002-03-27 10:24:21 EST
No, there are not any of such errors. Moreover the floppy disk just has the 
same content pasted before on this report.
I don't think the problem would be bad CD, since I've installed correctly on 
other machine with Samsung Monitor and video card ATI.

Comment 8 Michael Fulbright 2002-03-27 14:26:12 EST
Could you run the command:

rpm -q XF86_SVGA

on the installer system and tell me the output?
Comment 9 Michael Fulbright 2002-04-25 17:21:24 EDT
Closing due to inactivity.
Comment 10 Michael Fulbright 2002-05-23 12:51:53 EDT
Closing due to inactivity - please reopen if you have additional comments to add
to this bug.
Comment 11 Red Hat Bugzilla 2006-02-21 13:48:36 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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