Package: linux-source-2.6.24
Version: 2.6.24-4
Severity: normal
Hello, the hurd.
The facts I'm trying to depict here might be conveyed somehow inprecisely and,
as such, might render this bug report not as useful or
not as clear, straightforward, than expected.
The reason why I still want to inform you about the troubles I stuck upon is
that I recall different use cases where not all was so dark,
and I really think the following depiction, which I'll try to keep consice,
will prove useful.
In the following, the external modules I'm interested in ( 'my' external
modules ) refer to:
lzma squashfs aufs loop-aes nvidia-kernel[proprietary] (+ other less
useful to me)
And I always tried to build them with further invokation of module-assistant,
instead of
the --added-modules option of make-kpkg .
Here are the facts:
- My 1st intent was to build a 2.6.24 kernel with the TuxOnIce patch applied.
- I did so.
- I was unable to compile 'my' external modules.
- It run well but:
- I had a very disturbed and unREADable console. (mixed-up with initial
framebuffer mode and [usplash?] splash screen).
- Xorg X server didn't start because I had it configured to use
nvidia-kernel module which failed to compile.
- Then, I built several 'customizations' of kernel:
- 2.6.22 , 2.6.24 unpatched , 2.6.24 patched with TuxOnIce
- Several times with more or less hardware support and more or less
'software concepts' support (network QoS, ...).
What I got is:
- I had no problem with kernel 2.6.22 :
- As far as I remember, 'my' external modules always compiled.
- These modules always ended in /usr/src .
- I'm sure it is not a requirement to keep the 2.6.22 kernel build directory
(and contents)
to manage to build 'my' external modules. Just need to install the
make-kpkg -generated
kernel headers package.
- I OFTEN got problems with kernel 2.6.24 :
- I believe I at least 1 time managed to compile 'my' external modules for
2.6.24 kernel.
- I am sure that at least 1 time the resulting external modules packages
generated
by module-assistant went into the same directory where make-kpkg put my
kernel image
and kernel headers packages, instead of /usr/src like as usual, and I'm
almost certain
it was with 2.6.24 kernel.
- Most often (always?), I was unable to build 'my' external modules for
kernel 2.6.24.
- I've just made the assumption that it would have been a requirement to keep
the 2.6.24 kernel
build directory (and contents) to manage to build 'my' external modules
but, because I
was so eager to recover disk space, I didn't do it or I did it the 1
time this compilation
succeed.
How about you?
- How did you manage do provide pre-packaged external modules? (aufs,
squashfs, ...)
- Did you use the --added-modules option of make-kpkg to 'ship' these
modules, instead of
further module-assistant invokation (I always used m-a)?
Help this report will prove useful.
Sincerely,
Valentin QUEQUET
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-source-2.6.24 depends on:
hi binutils 2.18.1~cvs20080103-1 The GNU assembler, linker and bina
hi bzip2 1.0.4-3 high-quality block-sorting file co
Versions of packages linux-source-2.6.24 recommends:
hi gcc 4:4.2.2-2 The GNU C compiler
hi libc6-dev [libc-dev] 2.7-6 GNU C Library: Development Librari
hi make 3.81-3 The GNU version of the "make" util
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
