[wellylug] Kernel Compile - SUCCESS!

[Leslie Boardman]

Hooray!  Thanks for the help!  I now have sound again and also a massive
amount of confidence in the kernel-packaging scripts.  The new kernel is
in without a single hitch...yet :-) 

I ended up taking the old config, removing things even I knew I didn't
need, compiling the lot as per the sourceforge newbiedoc I found and
viola...laptop boots...check, pcmcia card still goes...
check...sound...check!  I needn't have been so paranoid (not that
paranoia is a bad thing when fiddling with stuff you don't really
understand).

There is just one more thing...

I think there is a problem with the something in the debian package for
the alsa-drivers.  The pcmcia modules ended up in
/lib/modules/2.4.18.mykernel/pcmcia/...  the alsa ones ended up in
/lib/modules/2.4.18/alsa/... and did not work until I copied them over
to lib/modules/2.4.18.mykernel/alsa/...  

Who do I tell? 

--Leslie


On Wed, 2003-09-03 at 10:34, Ewen McNeill wrote:
> In message <200309022226.KAA26546 at freddy.freeparking.co.nz>, "Leslie Boardman" writes:
> >Am I correct in thinking that If I copy the /boot/config..bf24 
> >to /usr/src/linux/.config, run make oldconfig and then run make-
> >kpkg ... I will end up with a custom kernel that is pretty much the 
> >same as the debian 2.4bf kernel?
> 
> Yup, you should end up with something pretty close.  
> 
> And then you'll have compiled your own kernel and be a "real" linux user :-) 
> 
> Compiling the alsa modules along with the kernel is certainly one of the
> easier ways to do it with make-kpkg, but I'm pretty sure that you can do
> it seperately as well by going to /usr/src/modules/alsa-driver and
> running "make -f debian/rules binary".  You may need to set KSRC to
> point at your kernel source if it's not in /usr/src/linux.  (And the
> kernel source would need to be configured to be the same as your running
> kernel.  You can probably also install the kernel-headers package and
> point it at that.)
> 
> /usr/share/doc/kernel-package/README.gz has a reasonable (brief) summary
> of make-kpkg usage.  But there's not much in the way of "what to do if
> it goes wrong" documentation alas -- it's generally a case of try to
> figure out what went wrong, "make-kpkg clean" and try again.
> 
> Ewen
> 
> -- 
> Wellington Linux Users Group Mailing List: wellylug at lists.naos.co.nz
> To Leave:  http://lists.naos.co.nz/mailman/listinfo/wellylug
> 
> 
-- 
Leslie Boardman, E: elbe at araitanga.com, ICQ:153582540 
PGP Fingerprint:EDBB E4CD C87F 528F 9998 824E 013A EE94 A27A B6D1
PGP Key Server: http://www.keyserver.net
"ignorance more frequently begets confidence than does knowledge"-Darwin