Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

unresolved symbols in modules after kernel recompile

0 views
Skip to first unread message

Andy Smith

unread,
Jun 30, 2001, 4:33:17 PM6/30/01
to
I always recompile the kernel and have never experienced problems as a
result of it. Most of the "out of the box" kerenels do have parallel
printer support, that is true. There are other reasons to recompile
though. Sometimes you can achieve a smaller memory footprint by paring
the kernel and recompiling. I personally like to include support for
all of the drivers I will need directly in the kernel. This all but
eliminates the possibility of an essential module being improperly
loaded at boot (from my experience anyway).

The only reason a recompile is likely to break a working system is if
the kernel is misconfigured. If the kernel was recompiled without some
option that the original kernel had compiled in it could cause
problems

Andy

On 21 Nov 2000 01:43:32 GMT, un...@physics.ubc.ca (Bill Unruh) wrote:

>In <8vceuc$so9$1...@news.cis.ohio-state.edu> ree...@cis.ohio-state.edu (doug reeder) writes:
>
>
>>I'm recompiling the 2.2.12 kernel to enable support for a
>>parallel port printer. Unfortunately, this breaks everything
>>that's compiled as a modules.
>
>ALL distributions that I have every heard of support parallel port
>printers out of the box. What made you think you should recompile?
>Despite what some of the ancient and outdated howtos say, you almost
>never should recompile your kernel. You will almost always make things
>worse, rather than better.
>(Yes, it is possible to recompile one's kernel and have it work.
>)
>

Colin Walters

unread,
Jul 2, 2001, 6:30:54 AM7/2/01
to
Andy....@arvinmeritor.com (Andy Smith) writes:

> The only reason a recompile is likely to break a working system is
> if the kernel is misconfigured. If the kernel was recompiled without
> some option that the original kernel had compiled in it could cause
> problems

One piece of advice I usually give to users of the Debian GNU/Linux
system is to start from the .config used to build the installed
kernel, which is stored in /boot. That way you're less likely to
forget to install, say, your SCSI disk driver.

The other thing is to use make-kpkg, which makes building and
installing kernels a breeze, and also does nice stuff like storing
your .config in /boot.

0 new messages