Problem emerging ati-drivers (3.7.6-r1, other versions too)

Message

thundersteele · Post by **thundersteele** » Sat Apr 10, 2004 1:09 am

Hi.
My Problem:

gentoo root # emerge ati-drivers
Calculating dependencies ...done!
>>> emerge (1 of 1) media-video/ati-drivers-3.7.6-r1 to /
>>> md5 src_uri ;-) fglrx-4.3.0-3.7.6.i386.rpm
 * X11 implementation is xfree.
>>> Unpacking source...
>>> Unpacking fglrx-4.3.0-3.7.6.i386.rpm
 * Applying fglrx-2.6-vmalloc-vmaddr.patch...                             [ ok ]
>>> Source unpacked.
 * Building the DRM module...
make: Entering directory `/mnt/spare/src/linux-2.6.4-ck1'
*** Warning: Overriding SUBDIRS on the command line can cause
***          inconsistencies
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
  CC [M]  /var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/agp3.o
  CC [M]  /var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/nvidia-agp.o
  CC [M]  /var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/agpgart_be.o
  CC [M]  /var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/i7505-agp.o
  CC [M]  /var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/firegl_public.o
/var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/firegl_public.c:2248: warning: initialization from incompatible pointer type
/var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/firegl_public.c:2266: warning: initialization from incompatible pointer type
/var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/firegl_public.c:2273: warning: initialization from incompatible pointer type
/var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/firegl_public.c:2280: warning: initialization from incompatible pointer type
/var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/firegl_public.c:2289: warning: initialization from incompatible pointer type
  LD [M]  /var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/fglrx.o
ACCESS DENIED  open_wr:   /mnt/spare/src/linux-2.6.4-ck1/.tmp_versions/fglrx.mod
/bin/sh: line 1: .tmp_versions/fglrx.mod: Permission denied
  Building modules, stage 2.
  MODPOST
ACCESS DENIED  open_wr:   /mnt/spare/src/linux-2.6.4-ck1/.__modpost.cmd
/bin/sh: line 1: ./.__modpost.cmd: Permission denied
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
make: Leaving directory `/mnt/spare/src/linux-2.6.4-ck1'
 * DRM module not built
nostrip
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-media-video_-_ati-drivers-3.7.6-r1-8605.log"

open_wr:   /mnt/spare/src/linux-2.6.4-ck1/.tmp_versions/fglrx.mod
open_wr:   /mnt/spare/src/linux-2.6.4-ck1/.__modpost.cmd
--------------------------------------------------------------------------------

This occurs only with ati-drivers, 3.7.6, 3.7.6-r1, and I think with 3.2.8 and 3.7.0 I am having the same Problem.
Notice that my Kernel Sources are saved in /mnt/spare/src/..., but /usr/src is a symlink to /mnt/spare/src, so /usr/src/linux is pointing to the correct sources. I've been able to build the fglrx module manually, but make install from there also fails. I can use(and am using) the module, I just copied it over to my /lib/modules/...
This error is happening to me since about one week, I had built ati-drivers without problems several times before (3.7.0, 3.2.

. Kernel is 2.6.4-ck1 (ck-sources), but also failed with some 2.6.5 love sources (might have been a rc).

BTW: Yes, I did it as root.

The error log (nothing different from above):

Code: Select all

loki@gentoo loki $ cat /tmp/sandbox-media-video_-_ati-drivers-3.7.6-r1-8605.log open_wr:   /mnt/spare/src/linux-2.6.4-ck1/.tmp_versions/fglrx.mod
open_wr:   /mnt/spare/src/linux-2.6.4-ck1/.__modpost.cmd

Anyone an idea what could cause this problem? Is my kernel path the reason? I can build kernels from there without Problems

motub · Post by **motub** » Sat Apr 10, 2004 11:00 am

ACCESS VIOLATION suggests that something that you're trying to write to is in use (and so cannot be written to).

Did you kill X before upgrading the drivers, if you're using them atm?

I'm using 3.2.8 drivers with the generic gentoo-devel-sources kernel (2.6.3-gentoo-r1) and had no problems emerging them (but I did this during install, haven't tried to upgrade to 3.7.6 yet).

So, of course it's possible that there's some incompatibility in the patched kernel itself, but that's a research question

.

kmj0377 · Post by **kmj0377** » Sat Apr 10, 2004 1:36 pm

You might also need to temporarily change opengl to xfree:
opengl-update xfree

Blue Fox · Post by **Blue Fox** » Sat Apr 10, 2004 3:08 pm

Strange...
I lose my 3d accel, but i just do emerge -u ati-drivers

thundersteele · Post by **thundersteele** » Tue Apr 13, 2004 11:36 am

Thanx guys.
Didn't have time neither to test this nore to reply here. I will check it out, now I too remember some issue with changing back to xfree-opengl and such things. Also, stopping X first makes sense.
I'll try.

EDIT: Ebuild still not working. Don't know what to do. The Access Violation occurs somewhere in my Kernel Sources, not a location for data in use normally. Building the modules from souce with the make script that is included in the driver archive. Make install then doesn't work because the built module isn't where it is supposed to be (/lib/modules/fglrx/fglrx.2.6.4-ck.ko). If I copy it there manually, I can run make_install without Problems.

Funny Thing at all.

catscratch · Post by **catscratch** » Sun Apr 18, 2004 10:03 am

I had the same problem here starting with gentoo-dev-sources-2.6.5
removing userpriv from the FEATURES line solved it for me

thundersteele · Post by **thundersteele** » Sun Apr 18, 2004 8:39 pm

Doesn't work for me. I never had FEATURES set. I tried setting them, removing some of them, it is all the same. Perhaps you could post the output of "emerge info" to see what you have set.

TheAl · Post by **TheAl** » Mon Apr 19, 2004 9:36 am

Hum,

Me too, I've somes error ACCESS DENIED.

But, you can bypass thoses errors with the FEATURES env. (it's additive from make.global and make.conf) :

o Edit your /etc/make.global, to remove sanbox option in FEATURES.
o Edit /etc/make.conf to be sure that you don't add sandbox

Then re-emerge your package, and don't forget to reactivate sandboxing.

HTH

thundersteele · Post by **thundersteele** » Mon Apr 19, 2004 10:01 pm

Thanx, that's it.
So, the easyest workaround is to put FEATURES="-sandbox" in your make.conf. It is set as default in make.globals, but this is not the place to change it.

Well, even quicker is this one:

Code: Select all

env FEATURES="-sandbox" emerge PACKETNAME