"Mark Smith" <mark.smith,AT,avcosystems,DOT,co,DOT,uk>|
RE: Cipe on Debian|
Andreas Stagl <a.stagl,AT,gmx,DOT,at>|
Wed, 27 Aug 2003 15:17:07 +0200|
"Cipe list \(E-mail\)" <cipe-l,AT,inka,DOT,de>|
thanks again for guiding me through this process!
For completeness, I'll also post my answer to the list... I'm appologizing
to those, who are not interessted in this topic.
At 10:35 27.08.2003 +0100, Mark Smith wrote:
> Just for info: "uname -r" provides the following info...
> Linux debian001 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown
That appears to be the output from "uname -a", the output from "uname -r"
Yep, you're right ;-)
> So, which one should I take... 2.4.18-13 or 2.4.18-5.... and anyhow, how
> can I find out which "minor-version" (like 5 or 13 in this example) is
> running on my sytem?
My document describes the procedure for determining the source version from
the kernel image changelog as found in
Hmmm... I don't have any "/user/share/doc/kernel*"-directory on my debian
box...?!? But anyhow, the 2.4.18-5 seems to be origin kernel-source from
the stable-branch (because the 2.4.18-13 is an update which I didn't made
so far... I guess), so I hope the 2.4.18-5 will fit.
Well, now that I have most of the required informations, I started to
follow your "HowTo". Please find below a short report and again some new
pre-1) I removed the testing source from my /etc/apt/sources.list so that I
don't have to pay attention if a packege will be taken from testing or from
1) apt-get install kernel-source-2.4.18=2.4.18-5
....downloaded the kernel-image and generates a file called
"kernel-source-2.4.18.tar.bz2" into /usr/src/
....downloaded some packages in addition (like binutils, bzip2 and so) and
during the config of binutils, it provided the following info-popup-warning:
"Kernel link failure info
You may experience problems linking older (and some newer) kernels with
this version of binutils. This is not because of a bug in the linker, but
rather a bug in the kernel source. This is being worked out and fixed by
the upstream kernel group in newer kernels, but not all of the problems may
have been fixed at this time. Older kernel versions will almost always
exhibit the problem, however, and no attempts are being made to fix those
that we know of.
There are a few work-arounds, but the most reliable is to edit the linker
script for your architecture (e.g. arch/i386/vmlinux.lds) and remove the
'*(.text.exit)' entry from the 'DISCARD' line. It will bloat the kernel
somewhat, but it should link properly."
I noticed it, but I didn't do anything regarding it. Hope that's okay.
2) cd /usr/src; bzip2 -d kernel-source-2.4.18.tar.bz2; tar -xf
.... created a directory /usr/src/kernel-source-2.4.18 with the kernel
sources in it
3) ln -s kernel-source-2.4.18 linux; cd linux; mkdir debian
.... created the suggested symbolic link
4) since there was no .config file inside the kernel-source image, I didn't
had to rename it ;-)
5) since I have a /boot/config-2.4.18-bf2.4 on my debain-box, I changed the
EXTRAVERSION in /usr/src/linux/Makefile EXTRAVERSION = -bf2.4
6) apt-get install kernel-package
.... downloads & configures some packages like kernel-package, make,
.... produced the following error-messages:
sh: gcc: command not found
dpkg-architecture: warning: Couldn't determine gcc system type, falling
back to default (native compilation)
therefore I installed the gcc package... see next point, but before this, I
deleted some files which have been generated during this failed
"make-dpkp"-try like .config, stamp-debian, conf.vars and the stuff inside
the debian directory (changelog, control, rules)
8) apt-get install gcc
.... downloads & configures gcc, cpp, ...
9) make-kpkg (again)
.... showed a part of the script (many test statements) and finaly showed
the following lines while wainting for my input:
Enable loadable module support (CONFIG_MODULES) [Y/n/?]
Set version information on all module symbols (CONFIG_MODVERSIONS) [Y/n/?]
Kernel module loader (CONFIG_KMOD) [N/y/?]
.... here, I pressed ctrl+C and got the following message (but I hope thats
usual, when pressing ctrl+C at this point):
(NEW) make: *** [oldconfig] Error 1
make: *** [stamp-kernel-configure] Interrupt
.... and finally i got a file /usr/src/linux/debian/changelog
10) As already mentioned above, I don't have any
"/user/share/doc/kernel*"-directory on my debian box... but since I
downloaded the 2.4.18-5 source-package, I changed the
"kernel-source-2.4.18-bf2.4 (10.00.Custom) unstable; urgency=low" of the
generated changelog to "kernel-source-2.4.18-bf2.4 (2.4.18-5) unstable;
11) renamed the during the "make-kpkg"-process generated .config file to
..config.old and copied /boot/config-2.4.18-bf2.4 to /usr/src/linux
12) make oldconfig dep
.... started to ask me a lot of questions... too many, because regarding
some of them, I don't know what to answer :-) ... so I abortet this process
Is it necessary to go through this questions? For example... on my Debian
box, I enabled Advanced Power Management (APM/ACPI). Do I also have to
enable this during this dialog? What will happen if I do not? Anyhow, I
will need this kernel-source only for building a cipe-module.
That's it so far.... can you please tell me, if everything's okay so far,
befor I continue?
Many thanks in advance & best regards,