| View previous topic :: View next topic |
| Author |
Message |
SirronD
Tux's lil' helper
Joined: 05 Jun 2002
Posts: 100
Location: Oakland, CA
|
 Posted: Sat Feb 10, 2007 11:16 pm Post subject: emerge x11-drm fails with 2.6.20-gentoo |
 |
|
System trys to emerge x11-drm-20060608 but it fails with the 2.6.20-gentoo kernel and sources.
Problem is with "drm_stub.c" Text of emerge failure follows:
| Code: |
CC [M] /var/tmp/portage/x11-base/x11-drm-20060608/work/drm/linux-core/drm_stub.o
/var/tmp/portage/x11-base/x11-drm-20060608/work/drm/linux-core/drm_stub.c:51: error: size of array 'type name' is negative
/var/tmp/portage/x11-base/x11-drm-20060608/work/drm/linux-core/drm_stub.c: In function 'drm_get_dev':
/var/tmp/portage/x11-base/x11-drm-20060608/work/drm/linux-core/drm_stub.c:216: warning: ignoring return value of 'pci_request_regions', declared with attribute warn_unused_result
/var/tmp/portage/x11-base/x11-drm-20060608/work/drm/linux-core/drm_stub.c:219: warning: ignoring return value of 'pci_enable_device', declared with attribute warn_unused_result
make[2]: *** [/var/tmp/portage/x11-base/x11-drm-20060608/work/drm/linux-core/drm_stub.o] Error 1
make[1]: *** [_module_/var/tmp/portage/x11-base/x11-drm-20060608/work/drm/linux-core] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.20-gentoo'
make: *** [modules] Error 2
* Portage could not build the DRM modules. If you see an ACCESS DENIED error,
* this could mean that you were using an unsupported kernel build system. All
* 2.4 kernels are supported, but only 2.6 kernels at least as new as 2.6.6
* are supported.
!!! ERROR: x11-base/x11-drm-20060608 failed.
Call stack:
ebuild.sh, line 1614: Called dyn_compile
ebuild.sh, line 971: Called qa_call 'src_compile'
environment, line 4181: Called src_compile
x11-drm-20060608.ebuild, line 111: Called die_error
x11-drm-20060608.ebuild, line 235: Called die
!!! Unable to build DRM modules.
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/x11-base/x11-drm-20060608/temp/build.log'.
|
I saw some other posts on this marked "Solved" but the emerge problem is not solved. They used the kernel drm as a workaround. But the kernel drm does not perform well with my system.
Has anyone been able to emerge x11-drm with the 2.6.20-gentoo kernel?
Thanks in advance for your help. |
|
| Back to top |
|
 |
zsitvaij
n00b
Joined: 11 Jan 2006
Posts: 43
|
| Posted: Sun Feb 11, 2007 3:54 am Post subject: |
|
|
EDIT: nevermind, didn't read post fully.
Did you actually try it with 2.6.20? My mobility x700 works better with the in-kernel drivers now.
Anyway, from here:
| Quote: |
The package compile and seems to work fine with vanilla-sources-2.6.20 when I
remove offending line 51 in /drm/linux-core/drm_stub.c of x11-drm sources.
// module_param_named(debug, drm_debug, int, S_IRUGO|S_IWUGO);
Hope my help !!!
|
But also note:
| Quote: | I tried building the drm within the kernel as a module, and just ignored the
x11-drm package all together. After rebuilding the kernel and booting into it,
I was surprised to see that my little Radeon IGP 320M was able to run with DRI
enabled, AND have the Composite extension enabled. This was previously not
possible when using the x11-drm package on the 2.6.19-r5 gentoo-sources kernel.
I confirmed that DRI was infact running with "glxinfo | grep rendering", with
the output being "Direct rendering: yes". Using "xdpyinfo | grep -i composite",
it showed that the Composite extension was indeed installed and running. I was
able to use the built-in composite effects of the new XFCE4-4.4 desktop
environment under these conditions.
As I said, this was not possible when using the x11-drm package on the older
kernels. It was either use DRI, or use the Composite extensions. I did nothing
special to the setup with using the built-in kernel modules for drm and radeon.
Perhaps the version in the kernel is newer, and should be used instead of the
x11-drm packages.
Just my thoughts. I will continue running the built-in kernel modules for the
moment, as they appear to be the better choice as far as support for now. |
|
|
| Back to top |
|
|
SirronD
Tux's lil' helper
Joined: 05 Jun 2002
Posts: 100
Location: Oakland, CA
|
| Posted: Sun Feb 11, 2007 11:44 am Post subject: Thank you for the reply |
|
|
I did read those posts and I am using the kernel DRM now.
For now I just unmerged x11-drm (I don't like packages in my world that cannot emerge correctly). But all of the documentation and how-to's that I find for gentoo and DRM say to use the package as it is always kept more up-to-date than the kernel DRM.
I think that if x11-drm does not work with 2.6.20, there should be a block so that people do not try to use it with the new kernel. |
|
| Back to top |
|
|
quantumsummers
Developer
Joined: 24 Sep 2006
Posts: 100
Location: Earth
|
| Posted: Sun May 06, 2007 2:57 pm Post subject: had same error & unmasking latest x11-drm worked for me |
|
|
Hey there SirronD,
I just had the same issue so I unmasked the latest version by accepting ~x86 KEYWORD and the compile went fine.
I suggest using the Alternate Method detailed here:
(http://gentoo-wiki.com/HOWTO_Direct_rendering_on_Intel_Extreme_Graphics_%28855GM%29_chipsets)
As you didn't post your video chipset I can't say if the entire content of the post linked above will work, but just to get x11-drm that is what I have done using the same kernel (gentoo-2.6.20-r7).
Hope this helps you out!
Cheers,
QuantumSummers
_________________
QuantumSummers
Trustee & Secretary, Gentoo Foundation
"...there are no rules here -- we're trying to accomplish something."
- Thomas A. Edison
www.LiquidusTech.com |
|
| Back to top |
|
|
EasyTarget
n00b
Joined: 03 Jul 2006
Posts: 29
Location: Amsterdam, The Netherlands
|
| Posted: Thu May 10, 2007 3:58 pm Post subject: |
|
|
Well, unmasking the latest x11-base/x11-dri certainly cured this on my system, just as detailed in quantumsummers link; see the 'PCI_PRETTY' section of the troubleshooting section, here.
The masked version is 10 months newer than the unmasked one.. Works for me, high framerate and no errors. |
|
| Back to top |
|
|
quantumsummers
Developer
Joined: 24 Sep 2006
Posts: 100
Location: Earth
|
| Posted: Thu May 17, 2007 6:09 pm Post subject: Glad to hear it worked... |
|
|
Awesome EasyTarget , DRM is great when it works.
Hey SirronD, did that fix your wagon?
PLEASE EDIT the heading to state the issue is (SOLVED) if it did.
Best Regards,
QuantumSummers
_________________
QuantumSummers
Trustee & Secretary, Gentoo Foundation
"...there are no rules here -- we're trying to accomplish something."
- Thomas A. Edison
www.LiquidusTech.com |
|
| Back to top |
|
|
xurf
n00b
Joined: 10 Feb 2003
Posts: 12
Location: Reading, UK
|
| Posted: Thu Jun 28, 2007 5:58 am Post subject: |
|
|
i think i had the same compile error
| Code: |
make[2]: *** [/var/tmp/portage/x11-base/x11-drm-20060608/work/drm/linux-core/drm_stub.o] Error 1
make[1]: *** [_module_/var/tmp/portage/x11-base/x11-drm-20060608/work/drm/linux-core] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.20-gentoo-r8'
make: *** [modules] Error 2
|
this was with x11-base/x11-drm-20060608 and i have a 2.6.20 kernel.
unmasking a newer version (x11-drm-20070314) worked for me too. |
|
| Back to top |
|
|
presto
n00b
Joined: 05 Oct 2006
Posts: 14
Location: Paraná/Brazil
|
| Posted: Thu Sep 20, 2007 3:45 pm Post subject: |
|
|
I get the same problem here.
Unmasking x11-drm-20070314 works fine. |
|
| Back to top |
|
|
FBorges22
Tux's lil' helper
Joined: 14 Feb 2007
Posts: 93
Location: Earth Orbit
|
| Posted: Tue Jan 08, 2008 1:21 pm Post subject: |
|
|
| presto wrote: | I get the same problem here.
Unmasking x11-drm-20070314 works fine. |
Why this package is masked? Because the newer kernel versions that require this packare are not masked... This is really strange... |
|
| Back to top |
|
|
|
Desktop Environments
