Hans-J. Ullrich wrote:
> Sure! I did the following: Installed all needed packages, unpacked the source
> package and made a symlink /usr/src/linux to /usr/src/linux-source-3.2
>
> Patched: patch -p1 < /mypath/blah/0001ath5kxxxxxxxxxx.patch
> So I did with all patches.
>
> Then copied /boot/config-3.2.0-4-amd64 to /usr/src/linux/.config (so I got
> also
> the version, worked before in the past this way).
>
> After that make menuconfig to check.
>
> Building then: make modules, because I just wanted to build only the ath5k
> module.
>
> At last I copied the newly build module ath5k.ko and replaced it with the new
> built one.
>
> depmod -a finished all.
Thanks. The ABI of the module you built doesn't match the ABI of the
installed kernel. Here's how I'd finish from there:
scripts/config --disable DEBUG_INFO; # makes the build a lot smaller
make deb-pkg; # optionally with -j<num> for parallel build
dpkg -i ../<name of package>; # as root
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html has more
details. FWIW all ideas for making that document more useful would be
welcome --- making it easy for users to build a custom kernel is very
important since it is what makes communication with upstream possible. :)
[...]
> But my time is limited,
> as I cannot run compilatiuon at work and in the evening the time is often too
> short, to run a compilation.
Yes, no problem. When time is short, we can wait --- as long as it is
clear how long to expect for a reply, waiting doesn't interfere much
with other work.
Regards,
Jonathan
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121230221305.GA11941@elie.Belkin
