Bug 124594 – agpgart unable to determine aperture size

Bug 124594 - agpgart unable to determine aperture size

Summary:	agpgart unable to determine aperture size

Status:	CLOSED DUPLICATE of bug 124593

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	kernel (Show other bugs)
Sub Component:
Version:	2
Hardware:	i686 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Arjan van de Ven
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-05-27 15:58 EDT by Jason
Modified:	2007-11-30 17:10 EST (History)
CC List:	0 users

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

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jason 2004-05-27 15:58:11 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
Gecko/20040113

Description of problem:
I have installed FC2 on a HP Netserver LC2000.  It has a ATI Mach64 3D
Rage IIC video card.  When I boot I get the following:

agpgart: unable to determince aperture size
agpgart: agp_backend_initialize() failed
agpgart-serverworks probe of 0000:00:00.0 failed with error -22

When I use X the screen draws seem slower than they were with RedHat 9.

Version-Release number of selected component (if applicable):
kernel-smp-2.6.5-1.358.i686.rpm 

How reproducible:
Always

Steps to Reproduce:
1. install FC2
2. on a HP Netserver LC2000
3.
    

Actual Results:  I get the errors and X seems slow

Expected Results:  No errors and X should be abit faster

Additional info:

Comment 1 Jason 2004-05-27 16:02:45 EDT


*** This bug has been marked as a duplicate of 124593 ***

Comment 2 Red Hat Bugzilla 2006-02-21 14:03:50 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.