Bug#387230: fglrx-kernel-src: the module build is sucessfull, but it cant be loaded by kernel

2007-01-06 Thread Thomas Hühn
Hi

I think I have the same problem, but since I'm running etch and etch doesn't 
have gcc-4.0, I'm out of luck, am I not?

Rebuilding Kernel and Driver with gcc-3.4 wouldn't help, would it?

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#387230: fglrx-kernel-src: the module build is sucessfull, but it cant be loaded by kernel

2006-09-13 Thread Fernando Cerezal
Steve Langasek wrote:
 Or, it uses whatever you specify as a compiler override using the
 appropriate environment variables.
   
Yes, but the problem is that will there be users that simplely will
follow the steps of the readme, the module will build sucessfully, but
it wil not works for them and they will not understand why.
 There is no API for passing this information to module packages; you'll have
 to do some additional work to set the corresponding compiler version in your
 environment.
Perhaps a note in the begining of the readme o in the debconf template
about how to configure this will be usefull.
I found posts in forums and mails of lists with the same problem and
without answer.
   This is not grave, because there is a workaround which is
 reasonable given that this is a -src package.
   
Sorry, i chose the options of reportbug that do the package unusefull,
since it not worked for me.

Thanks for your time.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#387230: fglrx-kernel-src: the module build is sucessfull, but it cant be loaded by kernel

2006-09-13 Thread Flavio Stanchina
Steve Langasek wrote:
 On Mon, Sep 11, 2006 at 03:26:16AM +0200, Fernando Cerezal wrote:
 The package uses gcc to build the module kernel. The latest version of
 gcc in testing is 4.1, but the package needs that gcc be a link to gcc-4.0.
 Otherwise the module builds sucessfully, but it is incompatible with the 
 prebuilts Debian kernels [...]
 
 Or, it uses whatever you specify as a compiler override using the
 appropriate environment variables.
 
 There is no API for passing this information to module packages; you'll have
 to do some additional work to set the corresponding compiler version [...]

Is there something I can do as the package maintainer?

To put it another way, I was under the impression that it's the user's
responsibility to ensure that they're compiling modules with the correct
compiler, correct kernel sources and configuration. AFAIK, no other
kernel module source package attempts to detect a mismatched compiler
version, let alone find the right one. Therefore, if this is a bug, I
would say it's a bug in the kernel build system (I'm sure Linus would
love to hear that).

-- 
Ciao, Flavio


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#387230: fglrx-kernel-src: the module build is sucessfull, but it cant be loaded by kernel

2006-09-13 Thread Steve Langasek
On Wed, Sep 13, 2006 at 04:36:00PM +0200, Flavio Stanchina wrote:
 Steve Langasek wrote:
  On Mon, Sep 11, 2006 at 03:26:16AM +0200, Fernando Cerezal wrote:
  The package uses gcc to build the module kernel. The latest version of
  gcc in testing is 4.1, but the package needs that gcc be a link to gcc-4.0.
  Otherwise the module builds sucessfully, but it is incompatible with the 
  prebuilts Debian kernels [...]

  Or, it uses whatever you specify as a compiler override using the
  appropriate environment variables.

  There is no API for passing this information to module packages; you'll have
  to do some additional work to set the corresponding compiler version [...]

 Is there something I can do as the package maintainer?

Well, you could work with the kernel team to figure out how to expose this
information in an API so that you can use it automatically in your package.
:)

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#387230: fglrx-kernel-src: the module build is sucessfull, but it cant be loaded by kernel

2006-09-12 Thread Fernando Cerezal
Package: fglrx-kernel-src
Version: 8.28.8-0.1
Severity: grave
Justification: renders package unusable

The package uses gcc to build the module kernel. The latest version of
gcc in testing is 4.1, but the package needs that gcc be a link to gcc-4.0.
Otherwise the module builds sucessfully, but it is incompatible with the 
prebuilts Debian kernels (at least with 2.6.16-2, the latest version in 
testing) and shows this in log file:

[...]
[drm] failed to load kernel module fglrx
(II) fglrx(0): [drm] drmOpen failed
(EE) fglrx(0): DRIScreenInit failed!
(WW) fglrx(0): ***
(WW) fglrx(0): * DRI initialization failed!  *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available*
(WW) fglrx(0): * *
(II) fglrx(0): FBADPhys: 0xe800 FBMappedSize: 0x0800
(II) fglrx(0): FBMM initialized for area (0,0)-(1024,8191)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1024,768) (front color
buffer - assumption)
(==) fglrx(0): Backing store disabled
[...]

Could the package verify that?

Thanks.

P.S.: For users that would can read this:
If you know what you are doing, do this:
#rm /usr/bin/gcc
#ln -s /usr/bin/gcc-4.0 gcc

Now is time to build the module like you can read in README file.

Undo the above:
#rm /usr/bin/gcc
#ln -s /usr/bin/gcc-4.1 gcc




-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable'), (20, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686-smp
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: 
LC_ALL set to [EMAIL PROTECTED])

Versions of packages fglrx-kernel-src depends on:
ii  bzip2 1.0.3-6high-quality block-sorting file co
ii  debhelper 5.0.37.3   helper programs for debian/rules
ii  make  3.81-2 The GNU version of the make util

Versions of packages fglrx-kernel-src recommends:
ii  kernel-package10.054 A utility for building Linux kerne
ii  module-assistant  0.10.6 tool to make module package creati

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#387230: fglrx-kernel-src: the module build is sucessfull, but it cant be loaded by kernel

2006-09-12 Thread Steve Langasek
severity 387230 important
thanks

On Mon, Sep 11, 2006 at 03:26:16AM +0200, Fernando Cerezal wrote:
 Package: fglrx-kernel-src
 Version: 8.28.8-0.1
 Severity: grave
 Justification: renders package unusable

 The package uses gcc to build the module kernel. The latest version of
 gcc in testing is 4.1, but the package needs that gcc be a link to gcc-4.0.
 Otherwise the module builds sucessfully, but it is incompatible with the 
 prebuilts Debian kernels (at least with 2.6.16-2, the latest version in 
 testing) and shows this in log file:

Or, it uses whatever you specify as a compiler override using the
appropriate environment variables.

There is no API for passing this information to module packages; you'll have
to do some additional work to set the corresponding compiler version in your
environment.  This is not grave, because there is a workaround which is
reasonable given that this is a -src package.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]