after building a custom kernel

h/w · 08-21-2003, 11:04 AM

i built the 2.4.18 kernel, and ran it - it seems to start without any problems except for the ethernet card.
the default kernel 2.2 which came with the first install had picked it up.
and i am quite sure i had selected the card during "make xconfig".
any is there anyway i can make the system detect it - either after i have booted and got into the system, or during boot?

i had followed the instructions on building custom kernels from the installation manual. the only change i made from it, was instead of getting the source pcmcia-source package, i had gotten the pre compiled .deb one, and installed that.

would that be a reason?

thanks!

johnMG · 08-21-2003, 03:36 PM

If you built your ethernet driver as a module, you might need to run modconf.

h/w · 08-21-2003, 03:37 PM

aha - ok, thnx - will look into it.
any idea bout the labelling of partitions in cfdisk?

thnx!

LSD · 08-21-2003, 07:59 PM

Quote:

Originally posted by h/w
i had followed the instructions on building custom kernels from the installation manual.

What, even to the point of making a .deb with the kernel in it? I nearly pissed myself when I read that, it's just another way for Debian users to overcomplicate something so simple as building a kernel so as to make the look "1337"-er than they really are.

johnMG · 08-21-2003, 08:40 PM

any idea bout the labelling of partitions in cfdisk?

Nope. Sorry. I used mac-fdisk on my Powerbook G3 -- and it just prompted me for a name during the process. IIRC, cfdisk was a very nice menu-driven console program. It seemed very complete...

LSD wrote:
What, even to the point of making a .deb with the kernel in it? I nearly pissed myself when I read that, it's just another way for Debian users to overcomplicate something so simple as building a kernel so as to make the look "1337"-er than they really are.

It's actually pretty nice -- once the kernel is built, it's just one step to install or remove it. Also, if you're managing multiple identical machines (as in a corporate setting) it makes lots of sense: you don't have the build the same kernel over and over, and you have a nice backout procedure incase later you discover something wrong.

redcane · 08-21-2003, 10:13 PM

Quote:

Originally posted by LSD
What, even to the point of making a .deb with the kernel in it? I nearly pissed myself when I read that, it's just another way for Debian users to overcomplicate something so simple as building a kernel so as to make the look "1337"-er than they really are.

I don't know if you've ever followed the process, but you actually only need one command to build the kernel, then one to install it. Seems easier than make dep/make mrproper/make bzimage/make modules install to me. Plus you then have a convenient package to keep in case you do another kernel build that isn't as good. Or you have more than one machine.