Bug 65487

Summary: Xconfigurator fails to probe memory
Product: [Retired] Red Hat Linux Reporter: Alessandro Vioni <genoma>
Component: XconfiguratorAssignee: Mike A. Harris <mharris>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: low Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:48:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
X server log
none
XF86Config-4 none

Description Alessandro Vioni 2002-05-25 13:14:00 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc3) Gecko/20020523

Description of problem:
If i use the "Probe" option in "Screen Configuration" step of Xconfigurator, i
recive an error.

Version-Release number of selected component (if applicable):
Xconfigurator-4.10.7-1
XFree86-4.2.0-8

How reproducible:
Always

Steps to Reproduce:
1.Run Xconfigurator
2.Chose "Probe" in "Screen Configurator" step

	

Actual Results:  Error:

"There was an error detecting the video    
 ram on your card. You should try          
 configuring the video card manually."    

Additional info:

ATI Radeon Vivo 64MB DDR
Comment 1 Mike A. Harris 2002-05-26 04:33:10 UTC 
Attach your X server log and config file.
Comment 2 Alessandro Vioni 2002-05-26 09:39:24 UTC 
Created attachment 58588 [details]
X server log
Comment 3 Alessandro Vioni 2002-05-26 09:42:04 UTC 
Created attachment 58589 [details]
XF86Config-4
Comment 4 Mike A. Harris 2002-05-30 22:17:08 UTC 

*** This bug has been marked as a duplicate of 64695 ***
Comment 5 Mike A. Harris 2003-04-20 17:04:28 UTC 

*** This bug has been marked as a duplicate of 39745 ***
Comment 6 Red Hat Bugzilla 2006-02-21 18:48:58 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.