Prev: gtk-gnutella
Next: Slack 11 'dnsmasq: failed to create listening socket: Address already in use
From: tinnews on 11 Oct 2006 16:38
tinnews(a)isbd.co.uk wrote:
> > Once the system is booted, you can install the kernel you
> > just used to boot the system (present in the kernel directory of the CD)
> > and don't forget to install the modules in /extra if you used a 2.6
> > kernel (I assume you know how to install a kernel: put it in /boot and
> > configure lilo accordingly).
>
> I'm OK with the lilo bit. However I'm wondering about the modules,
> how does one know which modules are necessary? When a kernel is used
> as the install kernel does it use modules and, if so, does it install
> the modules it uses? As I said I installed using the 2.6.18 kernel so
> would prefer to go with that, presumably I can find the corresponding
> modules in /test.
>
> > If you want to use another 2.6 kernel than
> > the huge2.6 one; you will have to make an initrd as documented in
> > /boot/README.initrd (alternatively, recompile your kernel with
> > everything you need to boot builtin).
> >
> I will eventually be compiling a kernel as I want SMP support and I
> don't think the 2.6.18 kernel has that.
>
Well I've got it installed now. I suspect I must have done something
wrong during the 2.6.18 install but anyway what I just did was to
install the 2.6.17 kernel which went smoothly *and* booted OK
afterwards. Then I simply copied the 2.6.18 kernel from the CD to
/boot and added it to the lilo configuration and that boots OK too.

So all I need to do now is install the 2.6.18 kernel source and build
a kernel with networking (and rather less bloat) and I can then
actually get around to configuring my system.

Thanks for all the help.

--
Chris Green
From: Eef Hartman on 12 Oct 2006 03:27
tinnews(a)isbd.co.uk wrote:
> Well I *thought* I had installed the same kernel as was being used
> during the installation (though I must admit the dialogue that asks
> you which kernel you want to install is a little confusing so I might
> have got it wrong).

As far as I know with _any_ 2.6 kernel you have to install, BY HAND,
the corresponding "kernel-modules" package, before you can reboot.
Setup does NOT do that for you.

But I haven't tried it myself, yet (and probably won't, we normally
UPGRADE, do not do blank installs, so we've always already have GOT a
2.6 kernel to fall back on at reboot).

> would prefer to go with that, presumably I can find the corresponding
> modules in /test.

On the CD's, /testing-2.6.18 on Cd 4, and the modules package should
be called kernel-modules-2.6.<version>-i?86-*.tgz

> I will eventually be compiling a kernel as I want SMP support and I
> don't think the 2.6.18 kernel has that.

There is a 2.6.17 kernel with smp support in /extra (on the CD's: CD #2).
That one also needs "its own" modules package.
--
********************************************************************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M.Hartman(a)math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
********************************************************************
From: tinnews on 12 Oct 2006 04:12
Eef Hartman <E.J.M.Hartman(a)math.tudelft.nl> wrote:
> tinnews(a)isbd.co.uk wrote:
> > Well I *thought* I had installed the same kernel as was being used
> > during the installation (though I must admit the dialogue that asks
> > you which kernel you want to install is a little confusing so I might
> > have got it wrong).
>
> As far as I know with _any_ 2.6 kernel you have to install, BY HAND,
> the corresponding "kernel-modules" package, before you can reboot.
> Setup does NOT do that for you.
>
Doesn't seem to be so with the huge26.s kernel, I just installed that
and it then booted OK from the hard disk. Similarly the test26.s
kernel also booted without having installed the "kernel-modules"
package.

I don't see why they'd need "kernel-modules" as they are both huge
(hence the name) kernels which have everything bar the kitchen sink
compiled into them.


> On the CD's, /testing-2.6.18 on Cd 4, and the modules package should
> be called kernel-modules-2.6.<version>-i?86-*.tgz
>
Yes, I've found that now (I hadn't originally downloaded the source
CDs) and have installed all the headers, modules and source for the
2.6.18 kernel.

--
Chris Green
From: Eef Hartman on 12 Oct 2006 04:23
tinnews(a)isbd.co.uk wrote:
> Yes, I've found that now (I hadn't originally downloaded the source
> CDs) and have installed all the headers, modules and source for the
> 2.6.18 kernel.

See other discussions about installing the kernel-headers (or the
README _in_ the same dir), in general, DON'T install them unless
you want to recompile glibc too. They are normally the "version
of the kernel headers the C library was compiled WITH", the kernel
itself has its OWN version of them in the kernel-source package.
The kernel-headers package is only to compile application software,
that is using the standard library calls to interface WITH the kernel.

The sources, of course, are only needed when you want to customize
the kernel itself, OR are installing third-party kernel drivers
(like NVidia) that will need them. Note that THOSE don't use the
kernel-headers, they get the ones from "the running kernel-version
sources" itself.
--
********************************************************************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M.Hartman(a)math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
********************************************************************
From: tinnews on 12 Oct 2006 04:44
Eef Hartman <E.J.M.Hartman(a)math.tudelft.nl> wrote:
> tinnews(a)isbd.co.uk wrote:
> > Yes, I've found that now (I hadn't originally downloaded the source
> > CDs) and have installed all the headers, modules and source for the
> > 2.6.18 kernel.
>
> See other discussions about installing the kernel-headers (or the
> README _in_ the same dir), in general, DON'T install them unless
> you want to recompile glibc too. They are normally the "version
> of the kernel headers the C library was compiled WITH", the kernel
> itself has its OWN version of them in the kernel-source package.
> The kernel-headers package is only to compile application software,
> that is using the standard library calls to interface WITH the kernel.
>
Yes, I have read the warning and was aware of the issue but you have
clarified it somewhat for me, thanks.


> The sources, of course, are only needed when you want to customize
> the kernel itself, OR are installing third-party kernel drivers
> (like NVidia) that will need them. Note that THOSE don't use the
> kernel-headers, they get the ones from "the running kernel-version
> sources" itself.

This is what I will be doing as I have at least two things that need a
custom compiled kernel.

--
Chris Green
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: gtk-gnutella
Next: Slack 11 'dnsmasq: failed to create listening socket: Address already in use