All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: linux-kernel@vger.kernel.org, ck mailing list <ck@vds.kolivas.org>
Subject: Re: 2.6.20-ck1
Date: Sun, 25 Feb 2007 21:32:14 +1100	[thread overview]
Message-ID: <200702252132.15145.kernel@kolivas.org> (raw)
In-Reply-To: <200702242334.31864.gene.heskett@gmail.com>

On Sunday 25 February 2007 15:34, Gene Heskett wrote:
> I have a problem, Con.  The patch itself works fine for me, BUT it doesn't
> update the version.h available in
> /lib/modules/2.6.20-ck1/source/include/linux to include the -ck1 in the
> reported kernel version when trying to build an fglrx driver with the
> latest ati driver builder.
> Which leaves this error message in /usr/share/fglrx/flgrx-install.log:
> [root@coyote fglrx]# cat fglrx-install.log
> [Message] Kernel Module : Trying to install a precompiled kernel module.
> [Message] Kernel Module : Precompiled kernel module version mismatched.
> [Message] Kernel Module : Found kernel module build environment,
> generating kernel module now.
> ATI module generator V 2.0
> ==========================
> initializing...
> Error:
> kernel includes at /lib/modules/2.6.20-ck1/build/include do not match
> current kernel.
> they are versioned as ""
> instead of "2.6.20-ck1".
> you might need to adjust your symlinks:
> - /usr/include
> - /usr/src/linux
> [Error] Kernel Module : Failed to compile kernel module - please consult
> readme.
> ==========================
> Unforch, the installer does not leave a readme behind that I've been able
> to find, nor does it report the error on-screen.
>
> The above files are not simlinks here on this FC6 install.  And of
> course /usr/src/linux does not exist allthough I could set it up for the
> duration of a rebuild/reinstall cycle of my script.
>
> Can we have a patch to address this?  Or should I just hardcode it since
> it will never be linked to any other later kernel?
>
> I tried that in the src tree's include/linux/version.h, but it was
> refreshed back to the original regex code by the make, so that's not
> where to do it obviously.  I've also made the simlink in /usr/src, but
> since a kernel make re-writes version.h, that didn't help.
>
> Whats next?

I've never heard of this problem before. As far as I'm aware the EXTRAVERSION 
usually is not included in version.h so it seems to be a limitation of the 
flgrx installer? That would mean the flgrx installer wouldn't work on any 
kernel with an extra version such as the -rc releases of mainline even. So 
I'm sorry but I don't really know what to do about this problem.

-- 
-ck

  reply	other threads:[~2007-02-25 10:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 10:10 2.6.20-ck1 Con Kolivas
2007-02-16 15:47 ` 2.6.20-ck1 Malte Schröder
2007-02-16 21:35 ` 2.6.20-ck1 Edouard Gomez
2007-02-16 21:45   ` 2.6.20-ck1 Edouard Gomez
2007-02-17  0:53 ` 2.6.20-ck1 Chuck Ebbert
2007-02-17  1:13   ` 2.6.20-ck1 Con Kolivas
2007-02-17  2:15     ` [ck] 2.6.20-ck1 michael chang
2007-02-17  3:17       ` Con Kolivas
2007-02-17 17:28         ` michael chang
2007-02-17 18:45         ` Chuck Ebbert
2007-02-17 21:00           ` Con Kolivas
2007-02-17 21:50             ` michael chang
2007-02-17 23:47             ` Andrew Morton
2007-02-18  0:39               ` 2.6.20-ck1 Con Kolivas
2007-02-18  0:41               ` [ck] 2.6.20-ck1 Radoslaw Szkodzinski
2007-02-18  0:45                 ` 2.6.20-ck1 Con Kolivas
2007-02-17 11:15 ` 2.6.20-ck1 Hugo Vanwoerkom
2007-02-18  2:14 ` 2.6.20-ck1 mdew .
2007-02-18  2:38   ` 2.6.20-ck1 Con Kolivas
2007-02-18  6:05     ` [ck] 2.6.20-ck1 Con Kolivas
2007-02-18  6:15     ` Rodney Gordon II
2007-02-18  6:20       ` Rodney Gordon II
2007-02-18 16:54     ` 2.6.20-ck1 Ryan M.
2007-02-18 19:00     ` [ck] 2.6.20-ck1 Ash Milsted
2007-02-24 12:12 ` 2.6.20-ck1 Fabio Comolli
2007-02-25  4:34 ` 2.6.20-ck1 Gene Heskett
2007-02-25 10:32   ` Con Kolivas [this message]
2007-02-25 16:33     ` 2.6.20-ck1 Gene Heskett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200702252132.15145.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=ck@vds.kolivas.org \
    --cc=gene.heskett@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.