| Summary: | drm_cleanup_pci unknown symbol | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Declan Moriarty <junk_mail> |
| Component: | General | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | high | ||
| Version: | unspecified | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Declan Moriarty
2006-01-28 21:07:19 UTC
I have tried this now with versions of precompiled as far back as 20051123 (to try to match in with Xorg's version) and no dice. Same error. Have you configured your kernel with built-in DRM? If you have then that's the cause of your problem. You must use a kernel without built-in DRM because it is incompatible with the DRM in the binary snapshots. Right! Kernel helped. Thanks to all who spooned me through this.
With CONFIG_DRM not set, I could (Once more) compile a kernel, and once more
compile kernel modules. Glxgears gets shot down instantly by a hardened system
with DRI, but glxinfo tells me I have DRI. I'll file a separate bug for that to
them. I haven't marked this as fixed, because you have problems.
1. Documentation is way behind, especially the website.
2. The build system is nothing short of shambolic, if my experience is
anything to go by. Sorry to nag. I checked out just about everything out of CVS
and could not go from source. I can download a tar.gz of nearly anything else
and build it to suit my system. Not DRI or Mesa. I suffered trying to get
drivers compiled.
3. There is a need for being able to pass separate CFLAGS to the kernel from
the ones used for Mesa. HLFS have this trick of putting
CFLAGS+= -my-weird-clfags-go-here
I used that with success in the linux-core/Makefile.kernel but had to do a bit
of fairly inspirational (for a user) reverse engineering to find where to put it.
4. You need to sort out the DRM kernel issues, or ask them to remove it
from the source. I'm sure they would be glad to save the weight.
Settle on one <expletive-deleted> way of building your code, and perfect that.
To hell with binary releases - That's the m$ way, and it has cost me an
unreasonable amount of effort to get this far.
/FINALLY clears off and leaves you guys alone :-)
Sorry that you had so much trouble building the source. I guess one of the fundamental problems is the number of components involved that need to match. There is no such thing as "The DRI Source". However, your experience is not what the average user should go through. They get their stuff from their distribution. What you went through is your distribution's job. As to the lack of documentation, it is unfortunately true that it doesn't always keep up with the development. However, the website is a wiki. You're welcome to improve the documentation based on your experience. But keep in mind that the intended audience is not the average user. Closing this as NOTABUG. Regards, Felix |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.