Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 287854 - radeon x850 agp not available with agpart and dri compiled into kernel
Summary: radeon x850 agp not available with agpart and dri compiled into kernel
Status: RESOLVED DUPLICATE of bug 276319
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-06 07:37 UTC by Peter
Modified: 2009-10-09 19:27 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter 2009-10-06 07:37:17 UTC
(II) RADEON(0): [drm] installed DRM signal handler
(WW) RADEON(0): [agp] AGP not available
(EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI.
(II) RADEON(0): [agp] You may want to make sure the agpgart kernel module
is loaded before the radeon kernel module.

ATI agpart as well as dri are compiled into kernel. About a year ago, this worked perfectly!  6 months ago, stopped working with an xorg or kernel update, not sure which.  There were crashes then in Qt and graphical glitches.  These have been fixed by the recent xorg update, but now Qt is ludicrously slow.

Reproducible: Always
Comment 1 Justin Lecher (RETIRED) gentoo-dev 2009-10-09 18:29:36 UTC
PLease attach 
kernel.config, 
emerge --info, 
version of ati driver, xorg server , 
Xorg.0.log, 
xorg.conf,
glxinfo output.
Comment 2 Peter 2009-10-09 18:55:13 UTC
I think actually I forgot that I posted this bug here before and it never got fixed.  There I did post all that info.  But it didn't help.  Does it ever?
Comment 3 Justin Lecher (RETIRED) gentoo-dev 2009-10-09 19:25:40 UTC
reopen to dupe
Comment 4 Justin Lecher (RETIRED) gentoo-dev 2009-10-09 19:27:15 UTC
(In reply to comment #2)
> I think actually I forgot that I posted this bug here before and it never got
> fixed.  There I did post all that info.  But it didn't help.  Does it ever?
> 

As I understand your previous report, the maintainer says it is a upstreambug and you should report it there. That's why it isn't fixed. So please report it upstream so that it could be fixed here.

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