Stephane wrote: > Oh this is very interesting: here is what I get with the policy command (didn't > know about it at all thanks) > > ernest:/home/stephane# apt-cache policy kernel-image-2.4.18-bf2.4 > kernel-image-2.4.18-bf2.4: > Installed: (none) You are not running the bf24 kernel. It is not installed. > I'm not sure I have a tuned kernel, I juste used a dirty patch to > make it ptrace-proof. But I'm sure I did this because apt-get wasn't > offering me to upgrade it so it was the case with the vanilla > kernel. Not sure what that means. Did you make a deb and install it? Or just 'make bzImage' install a new kernel? Sounds like that latter. In which case the package system will not have any idea of your kernel. If you did use a deb to install then you can query your system for what it is. uname -a COLUMNS=200 dpkg -l | head -n 4 COLUMNS=200 dpkg -l | grep $(uname -r) If you see something with "ii" in the first field then that is the package that is installed on your system. > I installed a kernel image once, but it seems it comes with > different options from the base kernel at least that is what I > thought because the net connection wasn't working anymore That happens if the additional modules are listed in /etc/modules. The new debian-installer will autodetect these. But for now you have to list them out manually. The '8139too' driver comes to mind as one common example. > and I had a lot of modules errors at boot. That is not normal. > I can't tell you enough details so I know this is somewhat useless, > but I thought that since kernel image wasn't using the modules I > need, I'd better to recompile a kernel myself, grabbing it straight > from ftp.kernel.org That works too. But I prefer the CRAMFS patches which Debian installs by default. But whatever. You can still build a deb with make-kpkg. See http://newbiedoc.sourceforge.net/system/kernel-pkg.html for details. Bob
Attachment:
pgpt6UwjEGhjE.pgp
Description: PGP signature