Re: FW: kernel source patching

[Kenneth Macdonald Karlsen <ken@fiona-victor.com>]

Russell wrote:

> "Chris A. Morgan" wrote:
>  
>
> > Hi List
> >
> > I'm struggling through the sea of documentation as a linux and Debian newbie.  Got Debian 3.0 installed (2.4.18-bf.2) on my Thinkpad 770 with only a few minor annoyances like no sound and some other strange functionalities.
> >
> > I want to upgrade to 2.4.19 kernel and compile it myself to perhaps get more things working.  I installed the source code from Debian CD's for 2.4.18 and downloaded a 2.4.19 patch from kernel.org.  When I applied the patch, I got a zillion FAILED messages, apparently because Debians version of the source code has been heavily patched and modified already.  How can I get clean source code to patch??  Downloading the entire source code (over 30M) on my dialup is problematic.  Would it help to just compile 2.4.18 as I have it or would that give me what I already have again?  I'm a little frustrated from weeks of just trying to get Debian functional.
> >
> > If you can help me, please reply directly since I am not subscribed to the list right now (200+ emails a day is beyond me).
> >    
>
> Don't worry that it takes a while to learn. The biggest battle
> is finding the useful places for information, which you can
> get here.
>
> This shows the 'conventional' way of kernel building:
>  http://www.tldp.org/HOWTO/Kernel-HOWTO.html
>
> The debian way is to turn the kernel source into a .deb
> package using kpkg-make:
>  /usr/share/doc/kernel-package/README.gz
>  /usr/share/doc/kernel-package/README.headers
>  /usr/share/doc/kernel-package/Rationale.gz
> then you install the generated package using dpkg -i ...,
> so that the installation system can keep track of it.
> This will also run lilo. Check that the right things
> have been done with lilo and make a rescue disk and
> backups before rebooting.
>
> Do you use midnight commander? You can read compressed .gz
> text files without having to first unzip them.
>
> You can get the latest unpatched kernels from http://www.kernel.org/
>
>  
Is there a bug?

I tried this and it fails...

Im trying to build 2.4.19 with the command:
make-kpkg --initrd  kernel_image


It fails after running through the whole process with error message that
follows.
what i do:

1. download source from mirror and extract it in /usr/local/src/
2. copy the config-2.4.18-686 from boot and give it name .config so that
i only use the new options in new kernel.
3. edit source according to reference from binutils
4 run command with the initrd option bacause my stock 2.4.18 debian
kernel uses it.

make[3]: Entering directory `/usr/local/src/linux-2.4.19/arch/i386/lib'

make[3]: Nothing to be done for `modules_install'.
make[3]: Leaving directory `/usr/local/src/linux-2.4.19/arch/i386/lib'
cd /usr/local/src/linux-2.4.19/debian/tmp-image/lib/modules/2.4.19; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b 
/usr/local/src/linux-2.4.19/debian/tmp-image -r 2.4.19; fi
depmod: *** Unresolved symbols in 
/usr/local/src/linux-2.4.19/debian/tmp-image/lib/modules/2.4.19/kernel/drivers/mtd/maps/sc520cdp.o
depmod:         mtd_concat_create_R606fc87b
depmod:         mtd_concat_destroy_R9c645004
make[2]: *** [_modinst_post] Error 1
make[2]: Leaving directory `/usr/local/src/linux-2.4.19'
make[1]: *** [real_stamp_image] Error 2
make[1]: Leaving directory `/usr/local/src/linux-2.4.19'
pingu:/usr/local/src/linux-2.4.19#

Help appreciated. Kenneth