On 5/1/06, maxim wexler <[EMAIL PROTECTED]> wrote:
The thing makes it to the prompt. I log in. Run uname.
Yikes! It *is* _running_ the old kernel.
BUT, it's _booting_ from the new! I checked!
I don't see how this is possible. How did you check that it is
booting the new kernel? Checking dmes
Some suggestions which you probably know, or follow, but just in case:
On Monday 01 May 2006 21:05, maxim wexler wrote:
> Ok, here's where it gets weird, at least to me:
>
> The symlink points to the new sources. When I cd
> /usr/src/linux that's where I end up.
I assume that you first check:
On Monday 01 May 2006 22:26, Toby Cubitt wrote:
> Actually, he didn't. The 2.6 series kernels don't require the "make
> modules" step.
Ok, good to know. An old school leftover :-)
Ciao
Francesco
--
Linux Version 2.6.16-gentoo-r4, Compiled #1 PREEMPT Wed Apr 26 06:59:58
CEST 2006
One 2.2G
Francesco Talamona a gentiment tapote:
> You missed a step:
> make && make modules && make modules_install
>
> Ciao
> Francescoun
>
>
I don't think so,
when you run make, your compile kernel and modules.
Then, you just have to run make modules_install.
So make && make modules_install i
On Mon, May 01, 2006 at 10:15:36PM +0200, Francesco Talamona wrote:
> On Monday 01 May 2006 22:05, maxim wexler wrote:
> > make menuconfig, then make && make modules_install
>
> You missed a step:
> make && make modules && make modules_install
Actually, he didn't. The 2.6 series kernels don't req
On Monday 01 May 2006 22:05, maxim wexler wrote:
> make
> menuconfig, then make && make modules_install
You missed a step:
make && make modules && make modules_install
Ciao
Francesco
--
Linux Version 2.6.16-gentoo-r4, Compiled #1 PREEMPT Wed Apr 26 06:59:58
CEST 2006
One 1.8GHz AMD Ath
On Monday 01 May 2006 20:33, maxim wexler wrote:
> > when I
> >
> > > ran make modules_install.
>
> ^^!
ooops. Sorry
FT
--
Linux Version 2.6.16-gentoo-r4, Compiled #1 PREEMPT Wed Apr 26 06:59:58
CEST 2006
One 1GHz AMD Athlon 64 Processor, 2GB RAM, 2007.31 Bog
--- Maurice E Johnson <[EMAIL PROTECTED]>
wrote:
> modules-update only updates for the running version.
> In order to update
> the new version, you could simply reboot to the new
> version.
Ok, here's where it gets weird, at least to me:
The symlink points to the new sources. When I cd
/usr/sr
> when I
> > ran make modules_install.
^^!
> It seems like you compiled your kernel but forgot to
> execute
> "make modules_install" step.
>
> ciao
> Francesco
>
> --
> Linux Version 2.6.16-gentoo-r4, Compiled #1 PREEMPT
> Wed Apr 26 06:59:58
> CEST 2006
> On
modules-update only updates for the running version. In order to update the new version, you could simply reboot to the new version.
On Sun, 2006-04-30 at 20:32 +0200, Francesco Talamona wrote:
On Sunday 30 April 2006 20:18, maxim wexler wrote:
> Hi group,
>
> This should be an easy fix -- i
On Sunday 30 April 2006 20:18, maxim wexler wrote:
> Hi group,
>
> This should be an easy fix -- if you already know!
>
> The reason many of my modules are not loading is
> because modprobe is looking in /lib/modules/2.6.12-r6
> and not /lib/modules/2.6.16-r3 which was filled when I
> ran make modu
11 matches
Mail list logo
