[Pkg-fglrx-devel] fglrx library diversions result in unusable Xorg if kernel module is not built

[Mark]

On Fri, May 1, 2009 at 9:17 AM, Patrick Matthäi <pmatthaei at debian.org>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Mark schrieb:
> > For some reason, I have not (yet) succeeded in building the kernel
> > module for fglrx.  Without that, and with the diversions that other
> > fglrx-* packages apply (libGL and libdri?), X is unusable.  I get a
> > black screen; the monitor does not go into powersaving mode.  Ctrl-Alt-
> > combinations ( -Del, -Backspace, -F1, -F2, ...) do not work.  I am
> > forced to press the reset button, and the Xorg log contains nothing
> > incriminating.
>
> Yes this is the case with some chipcards.
> But what version of fglrx you are tried out and which ATI/AMD card do
> you have?


The latest - 9-4-1
Hw is Radeon HD 4670


> >
> > I compiled kernel 2.6.29 myself.  I suspect that fglrx-source's failure
> > to build either has to do with the kernel version or where/how I built
> > the kernel - I do not believe it is a bug in the package.
>
> If you are using 1:9-4-1, 2.6.29 is the only supported Kernel atm.
> What says the build-log of m-a a-i fglrx?


/usr/bin/make  -f debian/rules clean
make[1]: Entering directory `/usr/src/modules/fglrx'
dh_testroot
rm -f configure-stamp
rm -f fglrx.ko fglrx.mod.c *.o libfglrx_ip.a
rm -f .version .*.o.flags .*.o.d .*.o.cmd .*.ko.cmd
rm -rf .tmp_versions
rm -rf patch
dh_clean
make[1]: Leaving directory `/usr/src/modules/fglrx'
/usr/bin/make  -f debian/rules binary_modules
make[1]: Entering directory `/usr/src/modules/fglrx'
if [ -f /usr/src/modules/fglrx/debian/control.template ]; then \
        cat /usr/src/modules/fglrx/debian/control.template >
/usr/src/modules/fglrx/debian/control; \
    fi
dh_testdir
touch configure-stamp
dh_testdir
/usr/bin/make -C /usr/src/linux SUBDIRS=/usr/src/modules/fglrx modules
make[2]: Entering directory `/opt/src/kernel/build-2.6.29'
/usr/bin/make -C /opt/src/linux-2.6.29 O=/opt/src/kernel/build-2.6.29/.
modules
  CC [M]  /usr/src/modules/fglrx/firegl_public.o
/usr/src/modules/fglrx/firegl_public.c: In function 'KCL_GetEffectiveUid':
/usr/src/modules/fglrx/firegl_public.c:1407: error: 'struct task_struct' has
no member named 'euid'
/usr/src/modules/fglrx/firegl_public.c: In function
'KCL_PosixSecurityCapSetIPCLock':
/usr/src/modules/fglrx/firegl_public.c:1781: error: 'struct task_struct' has
no member named 'cap_effective'
/usr/src/modules/fglrx/firegl_public.c:1785: error: 'struct task_struct' has
no member named 'cap_effective'
/usr/src/modules/fglrx/firegl_public.c: In function
'KCL_MEM_VM_GetRegionPhysAddrStr':
/usr/src/modules/fglrx/firegl_public.c:3225: warning: return makes pointer
from integer without a cast
/usr/src/modules/fglrx/firegl_public.c:3226: warning: return makes pointer
from integer without a cast
/usr/src/modules/fglrx/firegl_public.c:3227: warning: return makes pointer
from integer without a cast
/usr/src/modules/fglrx/firegl_public.c:3229: warning: return makes pointer
from integer without a cast
make[5]: *** [/usr/src/modules/fglrx/firegl_public.o] Error 1
make[4]: *** [_module_/usr/src/modules/fglrx] Error 2
make[3]: *** [sub-make] Error 2
make[2]: *** [all] Error 2
make[2]: Leaving directory `/opt/src/kernel/build-2.6.29'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/usr/src/modules/fglrx'
make: *** [kdist_image] Error 2

I have gcc 4.3.3 and make 3.81

I also tried the make.sh found in modules/fglrx.
It produces errors and replaces all the source files with symlinks to files
that don't exist.
http://pastebin.com/m533c5ce3


>
> You should try out the Debian variant of Linux, I think you may miss
> some CONFIG_ options.


initrd's bug me, so I build my own kernel.
my config: http://pastebin.com/m7a71bb71

>
> > However, it would be nice if the diversions did not happen unless the
> > fglrx module existed under /lib/modules/`uname -r`.  Perhaps the
> > packages could be left unconfigured if the module doesn't exist, and the
> > diversions would be set up when the packages successfully configure?
>
> This leaves the system on upgrading in an unconfigured state where dpkg
> has to fail, which leads to much more problems.
>

True, but it was the only mechanism I could think of that would prevent this
situation.  Had I not installed fglrx-* packages immediately before that -
and ONLY those packages - I would have spent a lot of time being very
frustrated about what the ^&&%^*%#@$# could be wrong, especially since
Xorg.0.log says NOTHING about it.

So please try to find a solution! :)


>
> - --
> /*
> Mit freundlichem Gruß / With kind regards,
>  Patrick Matthäi
>  GNU/Linux Debian Developer
>
> E-Mail: pmatthaei at debian.org
>        patrick at linux-dev.org
>
> Comment:
> Always if we think we are right,
> we were maybe wrong.
> */
>

Guten Tag
Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-fglrx-devel/attachments/20090502/1a020504/attachment.htm>